On Thu, Jul 20, 2017 at 03:50:00PM +0000, Justin W. Flory wrote: > On 07/11/2017 11:18 AM, Paul W. Frields wrote: > > One of the things I've been working on (along with several other > > people, including mattdm, dgilmore and pingou) is sussing out Fedora > > requirements on a CI/CD pipeline. I published the results to this > > page: > > > > https://fedoraproject.org/wiki/Fedora_requirements_for_CI_and_CD > > > > Since Fedora infra is a stakeholder (along with release engineering, > > QA, etc.), my thought is this page helps us clarify requirements and > > avoid surprises down the road. Also this might be useful to show to > > e.g. FESCo as a joint policy. > > > > Rather than just editing the page willy nilly, based on the number of > > people it's already been through, it would be great if folks could use > > the "discussion" (Talk) page to suggest changes. But I have a watch > > on the page and can help resolve issues. > > > > I've fallen behind on email the past couple of weeks, but I saw this > when I was quickly scrolling through the Infrastructure list… this is > really interesting and I'd like to keep up with more updates on progress > on developing the CI/CD pipeline for Fedora. > > Is there any singular place where someone can follow along with updates > about this outside of the Infrastructure list? Or has anyone considered > writing a Community Blog article about some of these plans / ideas? Even > though I don't have a lot of feedback to contribute, I'm sure a > Community Blog article might solicit a little wider feedback and also > inform people about some of these plans, even if it's still very early > in the process. :) There's a list and channel expressly for it. This is the best jumping off point: https://fedoraproject.org/wiki/CI -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
