Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Gav..." <gavin@16degrees.com.au>
To: <legal-discuss@apache.org>
References: <4B9ACA56.3040706@mozilla.com>
 <067201cac250$923e7760$b6bb6620$@com>
 <OF4257D102.3FCA4491-ON852576E7.005230B0-852576E7.00562976@us.ibm.com>
 <20905_1268673243_4B9E6AD6_20905_123_5_2d12b2f01003151006g1b3fbc17ib9c52d196e453e83@mail.gmail.com>
 <31917_1268673657_4B9E6C79_31917_125_1_8D6581C22F494340878EF8F6A0EBABB310BECCBE@fr0-mailmb10.res.airbus.corp>
In-Reply-To: 
 <31917_1268673657_4B9E6C79_31917_125_1_8D6581C22F494340878EF8F6A0EBABB310BECCBE@fr0-mailmb10.res.airbus.corp>
Subject: RE: updating the MPL and making it Apache compatible
Date: Tue, 16 Mar 2010 07:05:57 +1000
Message-ID: <041e01cac483$4f83d480$ee8b7d80$@com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AcrEYvQWxhH+KcJ9R0qXWSZvYwKa8AAAHazwAAfnyRA=
Content-Language: en-au


> -----Original Message-----
> From: NOIROT, Julie J [mailto:JULIE.J.NOIROT@airbus.com]
> Sent: Tuesday, 16 March 2010 3:21 AM
> To: legal-discuss@apache.org
> Subject: RE: updating the MPL and making it Apache compatible
>=20
> Sorry,
>=20
> Could you please remove my address from this discussion?
> I have subscribed last week, because I had one single question on one
> software ECCN that I did not manage to find on the website but now I
> realize that I am not really concerned by the forum discussion.
>=20
> Thanks for your understanding,
>=20
> Regards,
>=20
> Julie Noirot

Hi Julie,

You can send an email to :

legal-discuss-unsubscribe@apache.org

from your subscribed address. Just use the word 'unsubscribe' in the =
message
subject and body.
You'll get a confirmation which you can just reply and send as-is.

HTH

Gav...

>=20
> -----Original Message-----
> From: Henri Yandell [mailto:hyandell@gmail.com]
> Sent: 15 March 2010 18:06
> To: legal-discuss@apache.org
> Cc: Luis Villa
> Subject: Re: updating the MPL and making it Apache compatible
>=20
> On Mon, Mar 15, 2010 at 8:41 AM, Jeffrey Thompson <jthom@us.ibm.com>
> wrote:
> >
> > "Lawrence Rosen" <lrosen@rosenlaw.com> wrote on 03/12/2010 08:57:43
> PM:
> >
> >> RE: updating the MPL and making it Apache compatible
> >>
> >> Hi Luis,
> >>
> > ...
> >> I'm also sort of surprised that you believe there's an
> incompatibility
> >> between the Apache License 2.0 and the MPL. Apache is thrilled to
> have
> > its
> >> software incorporated into any larger works under any license =
anyone
> > wants.
> >> If we're compatible with proprietary licenses, why aren't we =
already
> >> compatible with the MPL?
> >>
> > ...
> >> I believe that the Apache License 2.0 is already one-way compatible
> with
> > MPL
> >> 1.1, and I can't imagine what you would put in your new license =
that
> > would
> >> change that situation for the worse. I'll be watching, though, just
> in
> > case.
> >> ;)
> >
> > Larry, Luis,
> >
> > Do you think that there is an opportunity to get the MPL 2-way
> compatible
> > with the Apache license?
>=20
> I'd love to see that. I was trying to think of how weak-copyleft and
> permissive could find a middle ground, but couldn't think of a
> permissively,with,some,copyleft license that could satisfy both
> philosophies.
>=20
> > As I understand it, Apache projects occasionally want to include MPL
> > licensed software, and could include binaries under Category B of
> Apache's
> > Third Party Licensing Policy. =A0Binaries are normally the only form =
of
> > distribution because source code for MPL projects can only be
> distributed
> > under the MPL, whereas binaries can be distributed under different
> terms.
> > As the policy points out, limiting the distribution to binaries
> causes some
> > practical issues, especially for scripting languages, etc.
>=20
> The direct Apache reason on the binary-only policy is that it lowers
> the risk of modifications being incorrectly managed. We have items in
> category B that don't have the binaries under different license
> option.
>=20
> We could solve this with a read-only infrastructure that manages the
> changes; but it also requires our users to setup the same type of
> infrastructure. Maybe if we someday end up with a standard approach to
> classifying licensing in projects that could be possible.
>=20
> > Under the weak copyleft principle, the source code must always be
> available
> > under the public license (in this case MPL). =A0It would be
> theoretically
> > possible to include in the next version of the MPL permission to
> distribute
> > either source or binary under different terms as long as the source
> code is
> > also available under the MPL itself. =A0The relevant question is
> whether that
> > would create too much of a problem for MPL projects.
>=20
> I think the biggest issue here is that the user of the product under
> the different license is now detached from MPL. Effectively this would
> be a 1-tier copyleft system and you could get around MPL by setting up
> a non-profit foundation who redistribute MPL under permissive
> licensing.
>=20
> It could be a clause that allows this as long as certain rights are
> removed (redistribution/modification), but that wouldn't have value
> for the community, just the proprietary end user.
>=20
> Hen
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>=20
>=20
> This mail has originated outside your organization, either from an
> external partner or the Global Internet.
> Keep this in mind if you answer this message.
>=20
>=20
>=20
>=20
> The information in this e-mail is confidential. The contents may not =
be
> disclosed or used by anyone other than the addressee. Access to this =
e-
> mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus =
immediately
> and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or
> completeness of this e-mail as it has been sent over public networks.
> If you have any concerns over the content of this message or its
> Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated
> virus scanning software but you should take whatever measures you deem
> to be appropriate to ensure that this message and any attachments are
> virus free.
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org