incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant elder <>
Subject Re: Making up policy on the fly
Date Thu, 20 Aug 2009 08:26:59 GMT
On Wed, Aug 19, 2009 at 8:52 PM, Joe Schaefer<> wrote:
> ----- Original Message ----
>> From: Ted Leung <>
>> To:
>> Sent: Wednesday, August 19, 2009 2:34:50 PM
>> Subject: Re: Making up policy on the fly
>> On Aug 19, 2009, at 11:17 AM, Joe Schaefer wrote:
>> > Why do we need someone to dig up a URL to believe what infrastructure people
>> have
>> > been saying consistently?  If we tell you something is best-practice, why do
>> *we*
>> > have to defend ourselves?  Why aren't the people on the IPMC actually
>> *required* to
>> > read /dev/release.html as a precondition to being put on this PMC?  Shouldn't
>> people
>> > *know* what the actual position of the foundation is before running around
>> casting
>> > foundation votes?
>> As far as I know, the only condition to being put on this PMC is that a member
>> ask to be added.   We don't have any kind of criteria to be on the PMC.  If you
>> think that we need some additional policy for that, be my guest.  As far as
>> infrastructure people needing to defend themselves:   This PMC operates by
>> quoting written ASF policy to podlings so that the podlings can do the *right*
>> thing.    It's not a matter of questioning you or anyone else on
>> infrastructure.   What we tell people is "there are rules here".  If we want to
>> be known as a fair, level-playing-field organization, those rules need to be
>> written down.    This PMC is a major part of our interface to the rest of the
>> world.  That face should be fair, consistent, repeatable, and as free of
>> frustration and controversy as possible.
> How's this for writing down the rules:

To be honest I've not heard much of the "...or at a minimum
referenced..." bit before, thats not to say other docs do not say
this, just I wasn't aware that was a minimum requirement and I think
other TLPs with separate licence files may not be doing that. Wouldn't
it be better to just get that legal JIRA about this resolved and if
the out come is "use a single LICENSE" then we just insist on that?

Also, the first sentence should probably mention something about
" long as they meet the requirements of the ASF 3rd party
licensing policies".


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message