On Tue, 17 Aug 2010, Mike McGrath wrote: > * future planning > * features wrangling / approval > * conflict resolution > * resource allocation/requests (it'd be awesome if someone could > actually write grants for stuff....) > * OS design > * Emerging technologies (not just what goes in but what cruft we > need to cut out) > * Project growth > * Packaging / Integration guidelines Riffing on that a bit, I think there's an equal amount of optimizing and perhaps consolidating of roles when you think about some of the fuzzier parts of Fedora. For instance, why can't there be one group of people that collectively figures out a globally consistent way to handle budget requests -- whether that is for a FUDCon, a FAD, a booth at a local event, media, swag, travel funding, etc. Streamline a lot of stuff, and do a better job of making sure that people know the discretionary/day-to-day budget that Red Hat allocates to the Fedora Project can be used by *anyone* or *any group* within our community that needs a monetary investment to support or help turn ideas into reality. This is one of the things that's bumping around in my head as I think about what the future interactions between the Community Architecture team (which has a subset of Fedora-related goals and is ultimately accountable for much of Fedora's discretionary budget) and the Fedora Project's leadership. https://fedoraproject.org/wiki/Community_Architecture_goals#Fedora_Project_stewardship Rambling, Max _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
