Carsten Ziegeler wrote:
>Ok, can someone of the PMC clarify this.
>
>We should not use the cocoon cvs for cocoon-apps, so a
>separate cvs is the way to go. I don't want to give all
>'cocoon-apps' committers also access to cocoon itself.
>So it must be separated.
>
>
Exactly. Jakarta-lucene is ALREADY doing this with lucene-scratchpad.
(it actually
serves the same purpose as cocon-apps rather than a general scratchpad).
committers
to the lucene-scratchpad are NOT committers to Lucene (necessarily)
>I think currently, the easiest solution is to start
>a project on sourceforge etc.
>
>
-1 - that would defeat the objective
-Andy
>Carsten
>
>
>
>>-----Original Message-----
>>From: Steven Noels [mailto:stevenn@outerthought.org]
>>Sent: Thursday, August 08, 2002 2:43 PM
>>To: cocoon-dev@xml.apache.org
>>Subject: Re: [PROPOSAL] Cocoon-apps CVS module
>>
>>
>>Andrew C. Oliver wrote:
>>
>>
>>
>>>I'd like to see a seperate CVS module (irrelevant of Cocoblog) for
>>>cocoon-apps. Which is for sample applications
>>>using cocoon. The bar for giving people commit access would be lower
>>>than the core. The main purpose would be
>>>to encourage folks to write example apps. Such usage example would be
>>>REALLY useful to me.
>>>
>>>
>>Please remember that you will need to provide *every* cocoon-app
>>committer with commit rights for that module. From
>>http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt?rev=HEAD&c
>>ontent-type=text/vnd.viewcvs-markup,
>>I gather it will be pretty debatable whether we want this or not.
>>
>>Warning: I'm not being the Apache commit status elitist here (I'm just a
>>neighbourhood Forrest committer anyhow), but I believe cocoon-apps
>>should be regarded as an xml.apache.org subproject, *or* that the PMC
>>should come up with a solution.
>>
>>Anyway, I shouldn't be posting anymore since I want to go home early
>>today, and I'll be off-list for two weeks anyhow. Just make sure that we
>>are able to live with the consequences of our decisions. We already have
>>a Hall of Fame of considerable weight
>>(http://xml.apache.org/cocoon/who.html), not sure whether we want to
>>open up the gates for *everybody* who comes up with some Cocoon-based
>>app. Even so, there should be rules laid out - *prior* to moving forward.
>>
>></Steven>
>>--
>>Steven Noels http://outerthought.org/
>>Outerthought - Open Source, Java & XML Competence Support Center
>>stevenn@outerthought.org stevenn@apache.org
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
|