Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F866B7D.7050301@rowe-clan.net>
Date: Thu, 12 Apr 2012 00:43:25 -0500
From: "William A. Rowe Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Re: Extraordinary OpenOffice security patch (Was: [Incubator Wiki]
 Update of "April2012" by robweir)
References: 
 <CAOFYJNb7NsegxPoWCvp8p2SnmAPrw15jk0aNxmmgt7rhNq+9RA@mail.gmail.com>
In-Reply-To: 
 <CAOFYJNb7NsegxPoWCvp8p2SnmAPrw15jk0aNxmmgt7rhNq+9RA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 4/11/2012 2:36 PM, Jukka Zitting wrote:
> 
> It should be noted though that even though the /dist/incubator/ooo
> space was used to distribute these patches, they were and are not
> officially blessed by the Incubator PMC on behalf of the ASF.
> 
> Should a similar case arise in the future, I'd prefer if a clearly
> separate area under /dist or some other place was used to prevent
> confusing these with official Apache releases.

Short of people.a.o/~luser/my-patch.tgz, I'm fairly certain that
can't happen with an incubating podling.  Everything under the space
/dist/ must exist under a PMC.  And if AOOo ever does on a broad
security patch distribution, inflicting that traffic on people.a.o,
infra will be taking names and kicking asses.

As chair, you should have been brought into this loop, but with the
change from Noel I can see how this oversight happened.  Sorry about
that.  It's probably another example why the current infrastructure
schema simply isn't plausible.


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org