Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rgardler@opendirective.com
 designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FC79BA7.1060707@apache.org>
References: <1338428718.42092.YahooMailClassic@web113506.mail.gq1.yahoo.com>
	<4FC75BEA.1070808@a-w-f.de>
	<CAKQbXgB3Rs4UJ2=BVbU8BdR4kED671=WSViO2VeM1pxccJ9udQ@mail.gmail.com>
	<4FC790BE.3050008@googlemail.com>
	<4FC79BA7.1060707@apache.org>
Date: Fri, 1 Jun 2012 08:47:44 +0100
Message-ID: 
 <CAKQbXgCXRVHLVe3rrOPp0NZLD-aitQ6XQk+jtrAjzfW-RLtF6g@mail.gmail.com>
Subject: Re: Moving Category-B tarballs (was Re: [PROPOSAL] Starting the
 graduation process)
From: Ross Gardler <rgardler@opendirective.com>
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6d58cff5c9b8f04c16466d7

--0016e6d58cff5c9b8f04c16466d7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sent from my mobile device, please forgive errors and brevity.
On May 31, 2012 5:26 PM, "Pedro Giffuni" <pfg@apache.org> wrote:
>
> Hi J=FCrgen;
>
> Let me clarify some issues too ...
>
> On 05/31/12 10:39, J=FCrgen Schmidt wrote:
>>
>> ...
>>

...

>
>> 6. we agreed to upstream changes to external libs where possible and
>> necessary. And we agreed to improve the workflow to use the tar-balls
>> from their original source where possible over time and where we can
>> rely on the overall availability (e.g. dependencies to Apache libs, etc.=
)
>>
> Yes. Most of them are just uninteresting upstream.

This is the part that really bothers me. There is a world of difference
between providing unmodified cat-b sources and providing modified cat-b
sources. The ASF only releases software under the ALv2. If any of these
cat-b sources have modifications they cannot, IMHO, be managed by the ASF
unless specific approval for an exception to policy is sought.

If there are no modifications the position is much less clear, but still
needs examination.

> I admit this is very clear. I don't expect such development to be
> a requirement for graduation but the transitory situation of a source
> release that depends on carrying category-B tarballs in SVN now is
> not really acceptable.

I do expect this to be sorted out before graduation.

That might be as simple as getting clarity on the policy, it might be more
than that. However, as a mentor I am uncertain about the practice adopted
here and as such will not encourage the IPMC to vote for graduation until
someone in the PPMC gets clarity.

As a mentor I'm not going to do it. I've been asked to stop doing stuff for
the community and let it manage its own afairs, and I'm happy to do so.

Ross

--0016e6d58cff5c9b8f04c16466d7--