Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Received-SPF: error (nike.apache.org: local policy)
Message-ID: <553E05CA.4000107@nosphere.org>
Date: Mon, 27 Apr 2015 11:47:54 +0200
From: Paul Merlin <paul@nosphere.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: dev@zest.apache.org
Subject: NOTICE
Content-Type: multipart/alternative;
 boundary="------------000105040107050606070802"

--------------000105040107050606070802
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Gang,

I started to dig into ZEST-15.

I'm first looking into NOTICE files.
There are lots of other issues (headers, gradle wrapper, crypto etc...)
but I'm handling them one at a time.


>From what I understand at http://www.apache.org/dev/licensing-howto.html :

- Only one NOTICE file per released distribution is mandatory
- Only *bundled* dependencies needs to be scrutined

So, if we don't bundle any dependencies in our release distributions,
NOTICE file should remain pretty simple.

I looked at releases of other Apache TLPs like Samza, DeltaSpike and a
few others at http://dist.apache.org/ and most of the JVM based projects
only release a source distribution there.
Then they publish JARs to maven repositories without LICENSE/NOTICE files.

I'd lean towards doing the very same. That is releasing a sources-only
distribution (with proper LICENSE/NOTICE files) and pushing artifacts to
repositories once the release is voted.

WDYT?

Cheers

/Paul


--------------000105040107050606070802--