time for a "Fedora Core Steering Committee"? (was Re: [fab] Fw: [Bug 174307] RPM 4.4.6 is available)

Greg DeKoenigsberg gdk at redhat.com
Mon Jul 10 17:28:37 UTC 2006


On Mon, 10 Jul 2006, Thorsten Leemhuis wrote:

> Stephen John Smoogen schrieb:
> > Sorry, I am trying to show a systematic problem with communication
> > that needs to be looked at by the board. It is a problem that has been
> > brought up internally multiple times at RH when I was there.. and your
> > answer is pretty much the stock one: "We just got this problem, and
> > have had 2 days to fix it... "
> > 
> > I am talking about a general problem with communication. [...]
> 
> Well, we have Fedora Extras, Ambassadors, Docs, Legacy -- all
> communicate in the open and have meetings on IRC. Summaries from the
> meetings get post to the list.
> 
> But Core is still a black hole. No public meetings. No real discussion,
> things just happen and even I'm sometimes wondering how/when some things
> got decided. No real informations what is happening and what's planed,
> only some small things get to the public. No influence from the Community.
> 
> In other words: Maybe it's time for a "Fedora Core Steering Committee"
> that operates similar to FESCo? E.g. regular and public IRC meetings
> (where things like this RPM sage can be brought up and discussed),
> Meeting summaries, discussions on a public list (maybe it needs to be
> operate similar to FAB, e.g. invite only and a readonly archive for the
> public?) ...? It would be okay for me if only Red Hat people are on the
> "Fedora Core Steering Committee" for now until Extras and Core get
> closer together, but such a Committee would be start into the right
> direction IMHO.

We've needed this for a long time.  IIRC, one of the goals of the initial 
board was to produce this entity.

We need an update.  :)  How's it going?

--g

-------------------------------------------------------------
Greg DeKoenigsberg || Fedora Project || fedoraproject.org
Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors
-------------------------------------------------------------




More information about the advisory-board mailing list