> -----Original Message----- > From: Costin Manolache [mailto:cmanolache@;yahoo.com] > Sent: Monday, October 21, 2002 9:02 PM > To: [EMAIL PROTECTED] > Subject: What should we do about sandbox ? RE: License and copyright > issues > > > Martin Cooper wrote: > > > I found a few things not yet mentioned: > > > > 1) In codec\Metaphone.java, "Copyright 1997, William B. > Brogden", which is > > clearly a problem. > > > > 2) In scaffold, numerous instances of "Copyright (c) 2002 Synthis > > Corporation.", also clearly a problem. > > Acording to jakarta-commons rules, the sandbox is just a CVS > repository > where experiments may happen. > > I see it similar with commiters using their homes or public_html > pages on jakarta - or with the commiters cvs repository.
I don't see it that way at all. The Commons front page says of the sandbox: ----- It's a place to try out new ideas and prepare for inclusion into the Commons portion of the project or into another Jakarta project. ----- The significant part of this is the point about growing out of the sandbox. If a sandbox project aspires to be a Commons or Jakarta project, which it should (otherwise, what's it doing there?), then it should start off that way, complete with Apache licensing. What you do in your home or public_html is up to you (up to a point, I'm sure :), but that's quite different from the sandbox. > > The sandbox is open to any jakarta commiter. > > The question is: do we have to police it and monitor all forms > of activities that happen on apache servers ? Because as far as > I can see, there is no difference between a file placed by a > jakarta commiters on his public_html or home and the files > in commons-sandbox. I believe we have to "police" (don't like the term) the sandbox in the same way that we do the Commons Proper repository. Otherwise, what's the difference between the sandbox and SourceForge, other than a restriction to Jakarta committers? > > We made it very clear that sandbox code can't be released, > and the fact that it is accessible using public cvs and > viewcvs is similar with the public_html files. > > > I would propose to ask the sandbox to be removed from viewcvs > and the eventually discuss what to do about the public cvs. > As a way to protect ourself. I wouldn't mind if this is voted > down :-) A sandbox project is going to have a much harder time building a community around it if the code can't be seen from outside Apache. > > What do you think about this issue ? Any other proposed solutions ? I propose we treat the sandbox the way I believe it was intended to be - as a jumping off point for new Commons/Jakarta projects. The only difference between the sandbox and Commons Proper should be that sandbox projects are there to germinate and build a community before they grow up and are allowed to release. -- Martin Cooper > > > -- > Costin > > > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:commons-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
