You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Joe Schaefer <jo...@yahoo.com> on 2009/08/17 04:14:33 UTC
PATCH Re: Thrift release legal issues
----- Original Message ----
> From: David Crossley <cr...@apache.org>
> To: general@incubator.apache.org
> Sent: Sunday, August 16, 2009 10:04:50 PM
> Subject: Re: Thrift release legal issues
>
> Niclas Hedhman wrote:
> > Joe Schaefer wrote:
> > >
> > > AIUI, and the way httpd does it, the LICENSE file contains all the licenses
> in
> > > the distribution, preferably in an annotated fashion so you know which
> license
> > > goes with which component. ?The NOTICE file is for any additional required
> > > Copyright statements and/or attribution notices that each license may
> require.
> >
> > I understand this to be the recommended approach, but IIRC I have seen
> > other ones, such as having the NOTICE file contain a local pointer to
> > each license in a separate file, often named accordingly, such as
> > license.bsd or in some cases license.foo (where foo is the component
> > being dependent on). I also have the impression that a single LICENSE
> > file containing all licenses with a heading of which
> > component/part/dependency is under which license, is the only
> > candidate for a unified approach and promoted heavily by many...
>
> The NOTICE file is not for that purpose. Did you mean to
> say that you have seen "LICENSE" files containing pointers?
>
> Here is one guidelines doc:
> http://incubator.apache.org/guides/releasemanagement.html#note-license-and-notice
> Would rather find something at www.apache.org legal,
> but my quick browse today did not find it.
Here's a quick patch to consider:
Index: releasemanagement.xml
===================================================================
--- releasemanagement.xml (revision 803351)
+++ releasemanagement.xml (working copy)
@@ -941,9 +941,9 @@
</p>
<p>
The artifacts and documents to which each subsidiary clause applies should be
-indicated in the document. This <a href='examples/LICENSE'>LICENSE</a>
+indicated in the LICENSE document. This <a href='examples/LICENSE'>LICENSE</a>
(courtesy of <a href='http://httpd.apache.org'>Apache HTTPD</a>) is a
-good example. The Apache License is at the top of document. The explanation
+good example. The Apache License is at the top of LICENSE document. The explanation
is clear and the files to which the licenses apply are clearly noted.
</p>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: PATCH Re: Thrift release legal issues
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Mon, Aug 17, 2009 at 4:21 AM, Joe Schaefer<jo...@yahoo.com> wrote:
> ----- Original Message ----
>
>> From: David Crossley <cr...@apache.org>
>> To: general@incubator.apache.org
>> Sent: Sunday, August 16, 2009 11:10:13 PM
>> Subject: Re: PATCH Re: Thrift release legal issues
>>
>> Joe, as far as i know, just dive in and make changes to
>> most Incubator documents.
>> http://incubator.apache.org/guides/website.html
+1
>> For the main "policy" document, there is a note at
>> http://incubator.apache.org/incubation/Incubation_Policy.html#Changing+this+Document
>> We usually pass such changes through Jira, etc.
+1
> Frankly the document in question is a bunch of intimidating
> circular gibberish. I would strongly prefer a normative document
> that doesn't allow a lot of leeway for projects to get creative
> in their compliance efforts.
-1
the incubator does not set apache release policy: the incubator guides
projects in their implemention of apache policy
> After all the primary concern of the document
> is to ensure projects meeting all the legal and formal requirements for a
> proper release.
-1
the release management documentation in the incubator are just guides.
the normative release management stuff belongs to infra and lives in
dev.
> That's boring stuff that should be written in an
> informative style, largely with a single voice, not by starting off with
> a gigantic heirarchy of categories of the sparsely collected wisdom of
> the IPMC.
>
> I'd be more than happy to burn the document down and start over again.
if you have the time to produce something better, just go for it. if
you can write a good, informative guide that applies to all projects
that's cool: project will use the guide as if it's normative. you'll
find that much easier than trying to get a load of extra policy
passed.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: PATCH Re: Thrift release legal issues
Posted by Joe Schaefer <jo...@yahoo.com>.
----- Original Message ----
> From: David Crossley <cr...@apache.org>
> To: general@incubator.apache.org
> Sent: Sunday, August 16, 2009 11:10:13 PM
> Subject: Re: PATCH Re: Thrift release legal issues
>
> Joe, as far as i know, just dive in and make changes to
> most Incubator documents.
> http://incubator.apache.org/guides/website.html
>
> For the main "policy" document, there is a note at
> http://incubator.apache.org/incubation/Incubation_Policy.html#Changing+this+Document
> We usually pass such changes through Jira, etc.
Frankly the document in question is a bunch of intimidating
circular gibberish. I would strongly prefer a normative document
that doesn't allow a lot of leeway for projects to get creative
in their compliance efforts. After all the primary concern of the document
is to ensure projects meeting all the legal and formal requirements for a
proper release. That's boring stuff that should be written in an
informative style, largely with a single voice, not by starting off with
a gigantic heirarchy of categories of the sparsely collected wisdom of
the IPMC.
I'd be more than happy to burn the document down and start over again.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: PATCH Re: Thrift release legal issues
Posted by David Crossley <cr...@apache.org>.
Joe, as far as i know, just dive in and make changes to
most Incubator documents.
http://incubator.apache.org/guides/website.html
For the main "policy" document, there is a note at
http://incubator.apache.org/incubation/Incubation_Policy.html#Changing+this+Document
We usually pass such changes through Jira, etc.
-David
Joe Schaefer wrote:
>
> Here's a quick patch to consider:
> Index: releasemanagement.xml
> ===================================================================
> --- releasemanagement.xml (revision 803351)
> +++ releasemanagement.xml (working copy)
> @@ -941,9 +941,9 @@
> </p>
> <p>
> The artifacts and documents to which each subsidiary clause applies should be
> -indicated in the document. This <a href='examples/LICENSE'>LICENSE</a>
> +indicated in the LICENSE document. This <a href='examples/LICENSE'>LICENSE</a>
> (courtesy of <a href='http://httpd.apache.org'>Apache HTTPD</a>) is a
> -good example. The Apache License is at the top of document. The explanation
> +good example. The Apache License is at the top of LICENSE document. The explanation
> is clear and the files to which the licenses apply are clearly noted.
> </p>
> </section>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org