I'm going to extend this by a week and cancel tomorrow's Server SIG meeting. People have been very distracted with dealing with Beta blockers and we've extended this request to a wider audience (it got picked up by certain news sources). Let's give it a little more time to percolate.
If you have thoughts, I'd really like to hear them. On Mon, Mar 26, 2018 at 8:04 AM Stephen Gallagher <sgall...@redhat.com> wrote: > Quick reminder to please send me your thoughts on this; I'll be collating > them tonight and sending them out for us to discuss tomorrow. > > > On Tue, Mar 20, 2018 at 4:58 PM Stephen Gallagher <sgall...@redhat.com> > wrote: > >> During today's Server SIG IRC meeting, we discussed plans for Fedora >> 29 and onwards. In particular, we've decided that we're probably going to >> retire the concept of "server roles" from our overall goals. Adam >> Williamson -- representing Fedora QA -- raised the point that the related >> release criteria and test goals come directly from the Fedora Server >> Product Requirements Document (PRD) . He correctly pointed out that we >> should start by revising the PRD and have that filter down ultimately into >> the release criteria. >> >> Looking at the Fedora Wiki, the Fedora Server PRD is now over four years >> old and thus is ripe for an update. To that end, we're going to start with >> a brainstorming exercise to update our Mission Statement. The current >> statement reads: >> >> Fedora Server is a common base platform with "featured server roles" >> built on top of it. We commit to produce, test, and distribute these server >> roles. >> >> Clearly, this is no longer going to work for us, since we're planning to >> retire the server role concept. So what I'd like is this: If you are >> reading this, I'd like you to send me your view of what the >> purpose/goals/efforts of Fedora Server should be over the next 2-3 years >> (or even longer). I would ask that you send your thoughts directly to me, >> not as a reply on the list. This is so as not to influence anyone else's >> answers or to start a debate before the brainstorming is concluded. I will >> gather the responses and send them back out to the list as a complete set >> on Monday. The floodgates should then open to try to find the common >> elements and start turning them into an actionable strategy (the discussion >> will also continue at the Server SIG meeting on Tuesday). >> >> Once that discussion settles down, I will take the major points we come >> to agreement on and start putting together a draft of a new Products >> Requirement Document. We can then discuss and tweak the PRD up to the >> Fedora 29 System-Wide Change Proposal deadline, at which point the Server >> SIG will submit its F29 Changes to FESCo. >> >> Thank you all in advance for your help with this. >> >> >>  >> https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-20/serversig.2018-03-20-20.00.html >>  https://fedoraproject.org/wiki/Server/Product_Requirements_Document >> >> >>
_______________________________________________ devel-announce mailing list -- email@example.com To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org