Re: GNOME Project Organogram

["Quim Gil" <quimgil gmail com>]

Mmm but wait, at least my GNOME experience as contributor is not
dependant to the code in the repositories and the release team, as the
diagram shows.

At least board, marketing team, web team and GUADEC (or GNOME events
in general) will also run and keep running no matter which decisions
relating to code are made. They are not waiting the release team
agenda to define their actions.

I think this is relevant if you want to reflect GNOME's "project
organization structure". I guess Vicente needs to clarify a bit more
what he wants to reflect. :) For instance, from a very formal point of
view the release team or the GUADEC committee receive a "mandate" from
the Foundation, and specifically the board, and not the other way
round. Other teams depend a lot on the release team decisions. Others
go almost by their own. In the end everything is much more informal
than that, but a diagram with those "power relations" might be useful
for outsider to understand how we are supposed to get coordinated.

Fortunately, any organization can be extrapolated to many diagrams
without having just one being The Truth.

On 2/12/07, Luis Villa <luis tieguy org> wrote:
> The problem, of course, is that gnome *is* a code-centric
> organization.
--
Quim Gil /// http://desdeamericaconamor.org