On Mon, Aug 17, 2009 at 4:21 AM, Joe Schaefer<joe_schae...@yahoo.com> wrote:
> ----- Original Message ----
>
>> From: David Crossley <cross...@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-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to