[EMAIL PROTECTED] wrote:
> I realize it is a small issue ( that can be resolved later or worked
> around ), but most of the emails are making the sandbox equivalent with a
> playground for untested code.

Some people may use it that way. Others may not. It is a place designed 
for tolerance and varied viewpoints. A DMZ for revolutions.

> A component that is built by a project as part of the sandbox/agora isn't
> supposed to be released to the public - because of quality concerns. Yet a
> component that is accepted by commons commiters can be released, even if
> it has a smaller set of commiters and less review.

Code or documentation cannot be released to the public directly from the 
shared CVS for *legal* concerns regarding use of the Apache brand. All 
anyone has asked is that one of subprojects using this code release it
with their own codebase. And that is all the clarified #20 says. 

"20. A CVS repository will be available to all Jakarta committers as a
workplace for new packages or other projects. Before release to the
public, code or documentation developed here must be accepted into the
Commons or sponsored by another Jakarta subproject. The sponsoring
subproject(s) will distribute the code or documentation along with the
rest of their codebase."

Again, this not just about Agora. We need to write this to apply to
everyone who might also want to use the shared CVS to promote a new
development model. Or work on any type of cross-product material,
whether for submission to the Commons or not.

Once there is Agora code on the table, it's possible that you could
setup an Agora section on the Jakarta Web site, where this code could be
distributed. There could even be an Agora CVS so you would not have to
rub shoulders with "experimental" branches. 

The point is that we are trying to make a place where ideas like Agora
can be proved, and once proved, fully deployed.

You're not getting everything you wanted for Agora. Neither Geir nor I
got everything we wanted for the Commons library. (At least not yet;-)
But that's all part of working within a group. 

The shared CVS in the Commons is not meant to be Agora. We have tried to
add language so it could be used like Agora, along with other things. At
the time, the operative phrase was "close enough".

<
http://www.mail-archive.com/library-dev@jakarta.apache.org/msg00178.html
>

> and I have a problem with arguing that
> a project that wants to release a stand-alone component out of
> sandbox needs to get the aproval of commons.

If the code were accepted into the Commons it would be moved to the
Commons CVS. The guideline is the same for everyone. 

-Ted.

Reply via email to