Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
From: "Mattmann, Chris A (3010)" <chris.a.mattmann@jpl.nasa.gov>
To: Andreas Veithen <andreas.veithen@gmail.com>
CC: private <private@axis.apache.org>,
        "mattmann@apache.org"
	<mattmann@apache.org>,
        "legal-discuss@apache.org" <legal-discuss@apache.org>
Subject: Re: JSON License and Apache Projects
Thread-Topic: JSON License and Apache Projects
Thread-Index: AQHS0+ejjYM3Iq0SwEe96E/w/TMVtKICweSA//+MRBY=
Date: Tue, 23 May 2017 19:30:07 +0000
Message-ID: <26364C42-EFE1-47F5-A39D-F08D26AB91FB@jpl.nasa.gov>
References: <63D25F99-C5D1-4115-816B-477943FF40E3@apache.org>,<CADx4_uWBve363ZqZu++p=hvFucZvpFRfDp4zXU10XrTmmL1G7g@mail.gmail.com>
In-Reply-To: <CADx4_uWBve363ZqZu++p=hvFucZvpFRfDp4zXU10XrTmmL1G7g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
archived-at: Tue, 23 May 2017 19:30:21 -0000

Thanks it is the responsibility of PMC chairs to disseminate this informati=
on to their respective communities.

Cheers,
Chris=20

Sent from my iPhone

> On May 23, 2017, at 12:24 PM, Andreas Veithen <andreas.veithen@gmail.com>=
 wrote:
>=20
> Note that "reminding everyone" is a misleading formulation because the
> original message wasn't sent to PMCs, but only to board@apache.org,
> i.e. to PMC chairs.
>=20
> Andreas
>=20
>> On Tue, May 23, 2017 at 6:11 PM, Chris Mattmann <mattmann@apache.org> wr=
ote:
>> Dear PMCs@,
>>=20
>> Hi! As the new Legal VP, I am reminding everyone that the
>> grandfather exception for the JSON License and Apache projects
>> ended last month. As sent by Jim (our prior Legal VP) the relevant
>> text is below and I want to highlight the following statement:
>>=20
>> --
>> If you have been using it, and have done so in a *release*, AND there ha=
s
>> been NO pushback from your community/eco-system, you have a temporary
>> exclusion from the Cat-X classification thru April 30, 2017. At that poi=
nt in time,
>> ANY and ALL usage of these JSON licensed artifacts are DISALLOWED.
>> --
>>=20
>> Thank you for your consideration and attention to this
>> matter.
>>=20
>>=20
>> Cheers,
>> Chris Mattmann, VP, Legal ASF
>>=20
>>=20
>> From: Jim Jagielski <jim@jaguNET.com>
>> Reply-To: "legal-discuss@apache.org" <legal-discuss@apache.org>
>> Date: Tuesday, May 23, 2017 at 9:04 AM
>> To: legal discuss <legal-discuss@apache.org>
>> Subject: Fwd: JSON License and Apache Projects
>>=20
>>=20
>> Begin forwarded message:
>>=20
>> From: Jim Jagielski <jim@apache.org>
>> Subject: JSON License and Apache Projects
>> Date: November 23, 2016 at 9:10:39 AM EST
>> To: ASF Board <board@apache.org>
>> Reply-To: board@apache.org
>> Message-Id: <B56ABB21-9954-44CC-AA3D-693EE2BBAE5C@apache.org>
>>=20
>>=20
>> (forwarded from legal-discuss@)
>>=20
>> As some of you may know, recently the JSON License has been
>> moved to Category X (https://www.apache.org/legal/resolved#category-x).
>>=20
>> I understand that this has impacted some projects, especially
>> those in the midst of doing a release. I also understand that
>> up until now, really, there has been no real "outcry" over our
>> usage of it, especially from end-users and other consumers of
>> our projects which use it.
>>=20
>> As compelling as that is, the fact is that the JSON license
>> itself is not OSI approved and is therefore not, by definition,
>> an "Open Source license" and, as such, cannot be considered as
>> one which is acceptable as related to categories.
>>=20
>> Therefore, w/ my VP Legal hat on, I am making the following
>> statements:
>>=20
>> o No new project, sub-project or codebase, which has not
>>  used JSON licensed jars (or similar), are allowed to use
>>  them. In other words, if you haven't been using them, you
>>  aren't allowed to start. It is Cat-X.
>>=20
>> o If you have been using it, and have done so in a *release*,
>>  AND there has been NO pushback from your community/eco-system,
>>  you have a temporary exclusion from the Cat-X classification thru
>>  April 30, 2017. At that point in time, ANY and ALL usage
>>  of these JSON licensed artifacts are DISALLOWED. You must
>>  either find a suitably licensed replacement, or do without.
>>  There will be NO exceptions.
>>=20
>> o Any situation not covered by the above is an implicit
>>  DISALLOWAL of usage.
>>=20
>> Also please note that in the 2nd situation (where a temporary
>> exclusion has been granted), you MUST ensure that NOTICE explicitly
>> notifies the end-user that a JSON licensed artifact exists. They
>> may not be aware of it up to now, and that MUST be addressed.
>>=20
>> If there are any questions, please ask on the legal-discuss@a.o
>> list.
>>=20
>> --
>> Jim Jagielski
>> VP Legal Affairs
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: private-unsubscribe@axis.apache.org
>> For additional commands, e-mail: private-help@axis.apache.org
>>=20

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