On 16 January 2015 at 02:49, Honza Horak <hho...@redhat.com> wrote: > There are not many guys interested in the Environment & Stacks WG on the > nomination page [2] so far, which is really shame. Don't loose your chance > to help moving Fedora forward! > > The main goal of this working group is to research and develop new or > improved methods of developing, testing, packaging and deploying software > for the Fedora community. For more concrete picture of our focus, see the > tasklist [3]. > > We might have struggled with not much real stuff done so far, but we > really need more people interested in discussions and also getting hands > dirty by hacking some proof-of-concept solutions, patches for existing > systems/tools and generally enjoying a lot of fun. > > Challenging tasks often have quite unclear specification, so some level of > own imagination and creativity is more than welcome, but being a member of > the working group is great opportunity to have *big impact on the future > look of Fedora*. > > OK I think one of the problems is that this doesn't look like it is a doing group but a talking group. By a talking group I mean that the first page comes across as "We are going to have a lot of meetings to bike shed about what we would like to see happen. We actually don't do any of that.. we just point the direction for others to go." or worse yet "The 5 year plan for growth and production will be produced by the committee in charge of 5 year plans."
For many of the people I know, that is what FPC and FESCO are already doing [even if it isn't.] It is also not something they want to be part of.. (more meetings versus more doings.) Since I very much doubt that any of these characteristics I listed above are actually what the group is trying to do... I think the committee needs to better explain what it is going to do, how it is going to do it, etc. -- Stephen J Smoogen.
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
