[fab] Fedora Core steering committee and public weekly meetings

[Rahul]

Bill Nottingham wrote:
> Rahul (sundaram at fedoraproject.org) said: 
>> Post release critical bug fixes too.
> 
> So.... this is not done for extras - do we have a committee that disallows
> extras builds based on schedule timeframe? Should we?
> 
> Bill

If we are going to move KDE into extras and I assuming that we are 
moving with that process immediately post FC6 release, then Fedora 
Extras on media is a pre requisite to that. Moving off from a rolling 
release model would mean that the release engineering team (current or 
expanded) should handle freeze processes in extras too.

I have already stated my opinion that I would prefer a technical 
committee that covers both Fedora Core and Extras and merge FESCo into 
it. I wanted core to work as a project in a very similar public fashion 
to other sub projects before that happens as a first step but if we can 
do all at the same time, then its even better.

There are a number of other things that are tied together. Open up core, 
open up brew or just move into using plague and external build systems, 
open the compose tool or write a new one, move into a distributed SCM, 
release live cd's with a hard  disk installation feature for those who 
dont want to download all of Fedora (core+extras) as CD/DVD's and a live 
cd tool to do variations of it.  If the variations are a pure subset of 
core+extras repository it can be called Fedora <something>, otherwise not.

Fedora Project would then initially do one release of the Live CD thing 
(assuming GNOME here) and let the community do whatever other variations 
it wants. In this model, KDE wouldnt move over to extras (they wouldnt a 
extras). We can just change maintainers without a fuss and KDE SIG or 
whatever can do Fedora KDE live CD's to promote it.

In my mind, the governance model should be

                  Fedora Board
                       |
FAB(Community issues)    Fedora Technical Committee (Packaging committee 
as a subset)
                        |

        Sub project Steering Committee's


The Board lead with veto power is a non elected position within Red Hat 
(currently served by Max Spevack). Rest of the board and sub project 
steering committee's can be elected. FAB, Fedora technical and packaging 
committee is not. The Board hand picks them.

Rahul