coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Wow.

Long thread, little traction.


As I mentioned at the beginning regarding forked code:
            Shallow-forks of other projects should maintain the licenses of their upstream originators.

And regarding the choice of AL 2.0 over BSD:
I *have* spoken to lawyers regarding this, and the significant issue isn't what allows  or prevents what. Frankly, it's pretty much a non-issue.  The BSD relies upon implicit licensing of related IP (that is 'by virtue of not explicitly reserving those rights, we're implicitly giving them to you') Whereas the AL clearly spells it out. On balance, clarity beats brevity.

And since the spirit of the AL and the BSD is nearly identical (Do what you want, just don't cry about it to me) and the AL again is very clear about the "no crying" in clause 8, I'm happy to land on AL.

G

From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Trevor Dennis
Sent: Tuesday, May 18, 2010 10:40 PM
To: William A. Rowe Jr.
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Choice of License.


On Tue, May 18, 2010 at 10:50 PM, William A. Rowe Jr. <wmrowe@xxxxxxxxx<mailto:wmrowe@xxxxxxxxx>> wrote:
On 5/18/2010 11:10 PM, Nasser Dassi wrote:
>
> If we are talking about CoApp-compiled software, then we should adopt
> the most transparent license.  Why?  Because we are not usurping
> licensing of the source code; we are simply re-packaging the source
> code... so, broadly speaking, we should protect all other licensing
> choices by stating that COAPP-COMPILED SOFTWARE HONORS THE LICENSING
> SCHEME AS CHOSEN BY THE ORIGINAL AUTHORS.
+1!  Other than the fact that we have limited choices (GPL won't magically
become BSD in our hands), this speaks volumes to what CoApp is seeking to do,
which is honor the creation, and intent of the package authors.


I was under the impression that the license we use applied ONLY to the tools that WE create
for analyzing the projects, building the MSI files, and the CoApp Engine core.  Any work we
do for the other open source projects we package will be strictly under their original licenses.  Including
any spec files we create for those projects and pass back upstream.

Trev