Could i suggest that rather than just 15-20 people [or whatever the number is eventually] with responsibility for a module ... that we create a hierarchy. That way the core CC people at the top still know what is happening in the project over all.
So we can break the project 4 or 5 main areas with an original CC member given primacy in each of those. These main areas could be broken down further and the CC member would delegate to new volunteers in which he has trust. He might choose from those submitting patches or forum support in a particular area and solicit them to help as a CC member!? Eventually as the project matures & grows I could imagine a situation where the original CC member might delegate the actual ability to delegate to his leutentant themselves! This way we keep small teams perhaps [within small teams [within small team]]] ... and yet still keep the ability to manage an army of people - does this make sense? As I write army I think I guess this is precisely how an army is orgamised??? so much for my bright idea I'm only a few thousand years to late with the idea :)
- While i welcome the astounding Colin Rooney (what else can i say? We cannot afford to pay him in another kind) to our esteemed CC (again, what else..), i like to comment slightly on Carlos (me think this unsigned piece is from him) 'army' hierarchy.
- Me think Carlos descended from Alexander the Great. Just that i m from the Mongols. Me do not follow hierarchy. Me smashed thru hierarchy. *sniggers* Red1 20:19, 2 April 2007 (EDT)
- Speaking of Mongol invasions, [The White Stag] is a beautiful telling of an ancient oral tradition of the origin of the Huns and Mongols. SDGathman 21:43, 2 April 2007 (EDT)
- Thanks SDGathman for the WhiteStag, didnt notice your post until now. So i thanked right away when i could - Red1 20:50, 6 May 2007 (EDT)
Since Postgres / DB Independence is a formidable and tricky but challenging journey, should we have a new subforum called "PostGreSQL / DB Ports" ? - Red1 06:00, 6 May 2007 (EDT)