Hi guys, Thanks for the email. I think I am happy with what is planned out so far. I am willing to help in every way. I will be on the channel if anyone needs me.
thanks. Kind Regards, Onuonga Frankie On Thu, Oct 24, 2013 at 6:48 PM, Sandro "red" Mathys <r...@fedoraproject.org>wrote: > On Thu, Oct 24, 2013 at 7:12 PM, Robyn Bergeron <rberg...@redhat.com> > wrote: > > > > > > ----- Original Message ----- > >> From: "Matthew Miller" <mat...@fedoraproject.org> > >> To: "Fedora Cloud SIG" <cloud@lists.fedoraproject.org> > >> Sent: Thursday, October 24, 2013 9:33:43 AM > >> Subject: Fedora Cloud Working Group (members, everyone, and what's next) > >> > >> Hello everyone. FESCo has approved the initial slate of voting members > in > >> the Fedora Cloud Working Group. That is: > >> > >> * James Antill > >> * Robyn Bergeron > >> * Joe Brockmeier > >> * Haïkel Guémar > >> * Sam Kottler > >> * Sandro Mathys > >> * Matthew Miller > >> * Frankie Onuonga > >> * Mattias Runge > >> > >> Our next two steps are to 1) document a governance model and 2) start > >> working on a product requirements document. > >> > >> As we work on these things, we'll need a place to communicate. I suggest > >> that we primarily use this list, plus chat on #fedora-cloud on > Freenode. We > >> have some geographical distribution -- I'm going to try to see if we can > >> find a time for an IRC meeting at least initially. > >> > >> This doesn't mean that we're taking over this list for just this > purpose -- > >> the Cloud SIG remains a place to talk about and work on all things > cloud, > >> and I think we can handle the overlap (especially since it's not > super-high > >> traffic). Also, as I hope I've made clear, the working group can't > possibly > >> do all of the things that needs to be done; everyone on the committee > will > >> have an active role in actually doing things, but we also will act as > >> enablers for other people's contributions. > >> > >> Unless anyone objects, or is really, really excited about doing it, I'm > >> going to start on a basic strawman governance document. Things like what > >> constitues a binding vote, how we handle succession that kind of thing. > Then > >> we can discuss and improve that. This needs to be done by November 15th, > >> although I'm kind of hoping that it'll be so uncomplicated that it won't > >> take that long. > >> > >> Likewise, I can start on a skeleton for a PRD, but if anyone in the > group > >> has more experience at doing that than I have (I come from a sysadmin > >> background, not one where I've worked on shipping products) I'll > happily and > >> immediately defer. (This, by the way, needs to be done by January > >> somethingth, which sounded a long way away when this idea was drafted > but > >> doesn't anymore when I look at the holiday calendar.) > > > > I can hack out the basic framework for a PRD, I have been through those > processes a zillion times. > > > > (Granted, my ability to actually fill it out with technical jargon that > makes any sense may be limited, but it can give us a start anyway... > normally i have come at this from the angle of making a marketing req. doc. > - "what people want to have as far as usability / functionality" and that > drives what technical bits come together in the PRD to make those wants > happen, but i am sure we can wing it.) > > Thanks Matt and Robyn, for getting these things started. Just ping the > list whenever you feel someone should look over what's already there > or fill in some technical jargon. -- Sandro > _______________________________________________ > cloud mailing list > cloud@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >
_______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
