www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Do the NOTICE and LICENSE files have to be at the top level of SCM?
Date Fri, 13 Sep 2013 16:37:43 GMT
On 13 September 2013 17:31, Stephen Connolly
<stephen.alan.connolly@gmail.com> wrote:
> On 13 September 2013 08:11, Kevan Miller <kevan.miller@gmail.com> wrote:
>>
>>
>> On Sep 12, 2013, at 9:33 AM, Stephen Connolly
>> <stephen.alan.connolly@gmail.com> wrote:
>>
>> > The Maven PMCs current understanding is that the answer is no. These
>> > files need to be in the source distributions published on each project's
>> > dist dir in the Apache web site.
>>
>> My answer would be yes, the files do need to be there.
>>
>> It seems like a very good practice to keep LICENSE/NOTICE files in obvious
>> places. It certainly seems helpful for our users… And yes, IMO, the files
>> should be in both our source distributions and our svn. And, finally, I'd
>> say that the most *obvious* place for these files is the root release points
>> (e.g. branches/trunk directories) of the project.
>>
>> Projects that I'm aware of have all followed this general practice. And I
>> haven't noticed that it was a terrible burden for them.
>>
>> If we need to resolve Jira's / make documentation clearer/dogmatic, we can
>> do that...
>
>
> The problem is:
>
> Projects built by Maven have *LOTS* of potential check-out points...
> basically everywhere there is a pom.xml in Subversion, that is a potential
> checkout directory...
>
> But our release roots are a lot fewer...
>
> With GIT things are easier, you'd just put the LICENSE and NOTICE files at
> the root of the git repo and be done... because you cannot checkout part of
> a GIT repository... you have to clone the whole thing or do complex things
> such that you'd kind of have to know that you might not be seeing
> everything.
>
> Subversion is much more lax.
>
> How we have traditionally solved this is by having Maven generate these
> files and put the resulting files into the source bundle (i.e. .src.tar.gz
> and .src.zip) that we put into dist (the source bundle is distinct from the
> IDE helper -sources.jar file... the source bundle is a buildable complete
> release while the -sources.jar file is just a convenience for IDE users)
>

Surely the source bundle corresponds to a part of the SVN tree?

Where one finds the POM that builds the source and packages it?

For example.

https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-compiler-plugin/

> Maintaining LICENSE and NOTICE files at every conceivable checkout root is
> just nuts.
>
> There has to be a better way

>>
>>
>> --kevan
>> ---------------------------------------------------------------------
>> 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


Mime
View raw message