Alan Burlison wrote:
> What I haven't seen is any detailed explanation of what problem you are
> trying to solve by imposing a hierarchy. We don't have a hierarchy at
> the moment and that doesn't seem, to me at least, to be a problem.
We do have a hierarchy at the moment, a very rigid one - all top-level
groups are "communities", they can create second-level groups called
"projects" - which led to the creation of user groups as projects,
since we really didn't want to go through the whole formal community
creation process for each user group. The additional distinction that
only groups at the project level can have scm repositories has led to
the communities that represent Consolidations having to create Projects
just to do the thing they were created for - managing a shared code base.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
