On Wednesday 08 March 2006 23:33, Noel J. Bergman wrote: > Daniel John Debrunner wrote: > > What makes an Apache project "umbrella-ish"?
> ASF projects are supposed to be about a community managing a project. So > the warning signs include large disjoint communities, e.g., Jakarta, the > old XML project (which, itself, was a Jakarta spin-off), etc. > One of thing things that the we need to look at is how to improve > communication across projects. Perhaps having some ontological mailing > lists would be part of a solution. > > What ideas and views do others have? I think that if we acknowledge that a community as a group of peers, working towards a common goal, then that would derive umbrellas from projects where there are distinctions of authority (and therefor work) within that community's codebase. I.e. either I am a committer on project X, or I am not. Now, that would break things up such as WS and DB, but in reality it is already happening, and the umbrella project becomes the federation of ontology. IMHO, the model is weak. I think we should strive for individual projects, no subprojects from a community perspective, and instead look for how to solve collaboration across projects, whether they are tightly coupled or not (technology wise), meaning an orthogonal collaboration view of ASF, which would guide external users as well, since project X can belong to many such views if it makes sense. Exactly which processes and tools should be employed to create such "views" are a bit early to discuss I think. Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
