You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Eric Sammer <es...@cloudera.com> on 2011/06/01 04:57:26 UTC
Policy for BUILD and CHANGES files in podling releases
Incubators:
I can't find an appropriate policy on the licensing requirements of
ancillary files like BUILD or CHANGES files that are commonly distributed
with releases. I'm specifically looking at the somewhat vague and confusing
http://incubator.apache.org/guides/releasemanagement.html but also
http://www.apache.org/legal/src-headers.html. I did find:
"Does this apply to documentation files included in a release?"
Yes.
...(in the context of license headers) in the src-headers.html doc, but if
that's the case, it doesn't look like many projects adhere to it. Ironically
enough, the RAT project (which is what I'm using from our maven build) is
what caught this and has the same files with no license headers.
Any direction is appreciated.
Thanks!
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: Policy for BUILD and CHANGES files in podling releases
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Wed, Jun 1, 2011 at 9:59 PM, ant elder <an...@gmail.com> wrote:
> On Wed, Jun 1, 2011 at 3:06 PM, Robert Burrell Donkin
> <ro...@gmail.com> wrote:
<snip>
>> (IMHO BUILDING and CHANGES are corner cases. I incline towards adding
>> license headers unless they are clearly trivial.)
>>
>
> I respectfully disagree on that one,
:-)
yep - this is one issue where there's no clear consensus
> i know a few projects do have the
> license header on all their README, BUILDING, CHANGES etc type doc
> files but i think the vast majority don't, and having the first thing
> a new user sees when opening a README be a lot of legal text doesn't
> seem very user friendly to me. So IMHO leave out the header until
> there is some explicit policy saying it must be there. And be in good
> company - [1], [2], [3] etc.
which sums up the other major point of view :-)
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Policy for BUILD and CHANGES files in podling releases
Posted by ant elder <an...@gmail.com>.
On Wed, Jun 1, 2011 at 3:06 PM, Robert Burrell Donkin
<ro...@gmail.com> wrote:
> On Wed, Jun 1, 2011 at 3:57 AM, Eric Sammer <es...@cloudera.com> wrote:
>> Incubators:
>>
>> I can't find an appropriate policy on the licensing requirements of
>> ancillary files like BUILD or CHANGES files that are commonly distributed
>> with releases. I'm specifically looking at the somewhat vague and confusing
>> http://incubator.apache.org/guides/releasemanagement.html
>
> (Unfinished might be a better description. Patches appreciated ;-)
>
>> but also http://www.apache.org/legal/src-headers.html. I did find:
>>
>> "Does this apply to documentation files included in a release?"
>> Yes.
>
> legal-discuss [1] is the right list for questions like this and that
> community maintains that documentation. it's a low traffic list. to
> get a canonical answer, ask there and ask for this case to be more
> clearly documented.
>
> (IMHO BUILDING and CHANGES are corner cases. I incline towards adding
> license headers unless they are clearly trivial.)
>
I respectfully disagree on that one, i know a few projects do have the
license header on all their README, BUILDING, CHANGES etc type doc
files but i think the vast majority don't, and having the first thing
a new user sees when opening a README be a lot of legal text doesn't
seem very user friendly to me. So IMHO leave out the header until
there is some explicit policy saying it must be there. And be in good
company - [1], [2], [3] etc.
...ant
[1] https://svn.apache.org/repos/asf/httpd/httpd/tags/2.3.9/README
[2] https://svn.apache.org/repos/asf/httpd/httpd/tags/2.3.9/INSTALL
[3] https://svn.apache.org/repos/asf/httpd/httpd/tags/2.3.9/CHANGES
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Policy for BUILD and CHANGES files in podling releases
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Wed, Jun 1, 2011 at 3:57 AM, Eric Sammer <es...@cloudera.com> wrote:
> Incubators:
>
> I can't find an appropriate policy on the licensing requirements of
> ancillary files like BUILD or CHANGES files that are commonly distributed
> with releases. I'm specifically looking at the somewhat vague and confusing
> http://incubator.apache.org/guides/releasemanagement.html
(Unfinished might be a better description. Patches appreciated ;-)
> but also http://www.apache.org/legal/src-headers.html. I did find:
>
> "Does this apply to documentation files included in a release?"
> Yes.
legal-discuss [1] is the right list for questions like this and that
community maintains that documentation. it's a low traffic list. to
get a canonical answer, ask there and ask for this case to be more
clearly documented.
(IMHO BUILDING and CHANGES are corner cases. I incline towards adding
license headers unless they are clearly trivial.)
> ...(in the context of license headers) in the src-headers.html doc, but if
> that's the case, it doesn't look like many projects adhere to it. Ironically
> enough, the RAT project (which is what I'm using from our maven build) is
> what caught this and has the same files with no license headers.
Rat is best viewed as a comprehension tool - it helps to find
questions that need answering
Robert
[1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org