RE: Question about the incubator and non-ASL code

2009-04-16 Thread Noel J. Bergman
Rich Bowen wrote:

> If, hypothetically, a project was considering entering the incubator,
> and if that project had an -extras repository for community-developed
> plugins to the project, and if some of those plugins were under non-
> ASL licenses, what would be the policy?

Are they compatible or incompatible licenses?  One is a matter of policy,
the other is possibly a matter of legal necessity.

If the former, then I don't see an issue, per se, although others may object
on the grounds that everything we release should be under our license.  And
there is the risk of a slippery slope.

If the latter, well now we really should get a concrete ASF level reply from
either legal-discuss or legal-internal.

So that's my 2 coppers.

--- Noel



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Question about the incubator and non-ASL code

2009-04-16 Thread Upayavira
On Thu, 2009-04-16 at 20:13 -0400, Rich Bowen wrote:
> If, hypothetically, a project was considering entering the incubator,  
> and if that project had an -extras repository for community-developed  
> plugins to the project, and if some of those plugins were under non- 
> ASL licenses, what would be the policy? Could there be an -extras  
> repository containing non-ASL code, if that was never part of the  
> official release? Or would that be required to be housed somewhere off- 
> site in a SourceForge or GoogleCode or the like?

General practice is to have it off-site, such as SourceForge or
GoogleCode. See www.wicketstuff.org for one example.

Upayavira



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Question about the incubator and non-ASL code

2009-04-16 Thread Rich Bowen
If, hypothetically, a project was considering entering the incubator,  
and if that project had an -extras repository for community-developed  
plugins to the project, and if some of those plugins were under non- 
ASL licenses, what would be the policy? Could there be an -extras  
repository containing non-ASL code, if that was never part of the  
official release? Or would that be required to be housed somewhere off- 
site in a SourceForge or GoogleCode or the like?


--
"Reality is that which, when you stop believing in it, doesn't go  
away." (Philip K. Dick)