[SM-Discuss] project organization
lejatorn at smgl.homelinux.net
Mon Feb 13 18:29:56 EST 2006
On Mon, Feb 13, 2006 at 01:30:38PM -0800, Eric Sandall wrote:
> One possible organization (using some of the above ideas):
> Project Lead (or Council of Elders formed of all the teams)
> |-> Quality Assurance Lead (PL Assistant)
> |-> Grimoire Team (QA Assistant)
> |-> Sorcery Team (QA Assistant)
> |-> Cauldron Team (QA Assistant)
> |-> Tome Lead (PL Assistant)
> |-> Public Relations Team (Tome Assistant)
> |-> Web Team (Tome Assistant)
> |-> Server Team (Tome Assistant)
> |-> Documentation Team (Tome Assistant)
> That cuts us down to two teams (which is probably a gross
> simplification ;)), with 2 (or more) PL assistant leads, 3 QA
> assistant leads, and 4 Tome assistant leads. For the Council of Elders
> idea, all the assistants to leads and the leads would be on the
> Council (so about 10 people). Each team could sub-divide more if they
> want (e.g. grimoire would also have subdivisions for stable-rc,
> stable, and each section).
I'm still pondering about that, in one hand it doesn't seem logical to
me to have Grimoire and Sorcery as subdivisions as I consider them to be
the most important part of smgl. But on the other hand I see the
advantage of having them managed together by a higher instance.
> I think our main issue (as our poll noted) is documentation. If we
> can get our documentation (at least for the developers) updated and
> finalized that might get more consistency in commits as well as giving
> a clear definition of who is supposed to be doing what (with respect
> to what maintaining a section means, who can edit maintained or
> unmaintained sections, what bugs we need to focus on, etc.).
Totally agreed. if one thing, we need to have a clean website and a neat
wiki for proper documentation. Motivation is probably the biggest
problem here because I don't think many ppl among us find writing and
formatting wiki pages amusing.
"Monde de merde."
More information about the SM-Discuss