* Darren J Moffat <[EMAIL PROTECTED]> [2006-01-12 03:35]: > On Thu, 2006-01-12 at 10:22, Alan DuBoff wrote: > > On Wednesday 11 January 2006 09:58 am, Mark Sweeney wrote: > I see communities as being the long term high level thing and projects > being the shorter term or smaller scope things. > > I don't really care either way but it does beg why we have both projects > and communities.
Communities are the social groups representing areas of interest within the entirety of the OpenSolaris space, and will have some kind of representation in the governance process (or they do in the current draft). As a result, the preliminary process for creating community requires a reasonable amount of consensus, including a CAB endorsement. Projects are collaborative efforts that produce objects (code changes, specific documents, graphics, etc.). Projects will have code repositories, committers, etc.; communities won't. The process for requesting a project requires only two community members to agree. (The infrastructure requirements of the two groupings overlap, but having only one type of grouping leads to a very complex "leader" console that looked forbodingly difficult to implement well and to document completely.) I think your duration point will be accurate in general. - Stephen _______________________________________________ opensolaris-discuss mailing list [email protected]
