Stefano Mazzocchi <[EMAIL PROTECTED]> writes: [ I want to preface my comments by first thanking you for [EMAIL PROTECTED] Secondly, at the moment I'm inclined to affirm your proposal, but I need to develop some guiding criterion on which to base a vote. I don't want to be in a position where I feel obligated vote "+1" on every similar request, especially when I have no feeling for how many of them are coming :-) ]
[...] > Unfortunately, the ASF members thought that the same model could well > apply to projects which did not release software directly (unlike HTTPD > did) and decided to use the same model for jakarta and xml (which don't > release software directly, but add another level of indirection with > subprojects). Can you describe the current release process for cocoon, emphasizing the problems with the current system? Is there a public document that chronicles the issues? [...] > In order to avoid stupid PMC elections, I'll be in favor of having the > PMC composed by *all* committers that ask to be part of it. This to > imply that committers and legal protector share the same duties and > priviledges. How many cocoon committers are there right now? [...] > 3) what does it mean for Cocoon? > > Being a project allows us to host several different incubation-stage > efforts underneath. Cocoblog, wyona, forrest, cocoon-related IDE > plugins could be possible additions. Of course, with the idea of > promoting them as top-level projects when they are successful from a > community perspective. How will the cocoon PMC be better positioned to address the needs of such "subprojects" than the current jakarta/xml PMC? How do you foresee cocoon's PMC addressing the current troubles with subproject releases? [...] > 5) isn't this unfair against the other sub-projects that remain > contained, therefore with less visibility? > > I don't know. Here I'm just stating the intention to move Cocoon to > top-level and I know the ASF board is very open to projects willing to > move out of their containers. > > But the ASF will *NOT* force projects to take this action. If other > communities feel they should deserve top-level projects, they should > make a proposal like this and ask the board instead of complaining > with us that we do it. Among jakarta/xml projects, how widespread is the desire to abandon the container PMC? Have there been other reorganization attempts in the past? -- Joe Schaefer
