On Wed, 2010-04-28 at 16:32 -0400, Paul W. Frields wrote: > I'd like to get this to some sort of actionable conclusion. Right > now, we have two thumbs up, albeit one of them for a slightly > different idea than what we had in mind. Here's what I would want to > achieve with such a meeting: > > * Inform the Board and the community about one or two goals that one > specific team has for the next 1-2 releases to improve Fedora, > either the project or the distribution, for the entire user base, > including our current contributors. > > * Identify what that team thinks might block them from doing that, and > if possible, what the Board can do to remove those blockages. > > The Board talked about broad vision in our last meeting. As part of > that process, we agreed that it was vital to talk to teams in Fedora > about what they see as missing or lacking. If we can identify those > problems, then not only is that broad vision more likely to include > our contributors, but we can do a better job of unifying the people in > the Project around some substantial but achievable goals. And just as > importantly, *measurable* goals, even if they're as simple as "did we > produce this new system/feature/process?". I think this is definitely worth a shot, and we'll know after a couple of meetings whether we should continue/adjust/abandon the approach. -Chris _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
