incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <>
Subject Incubating with Apache Commons as champion?
Date Tue, 20 Jan 2015 14:28:27 GMT
The discussion on dev@commons about coming-to-Apache Commons-RDF
( seems to be rejecting a
temporary mailing list like rdf@commons as it is seen t be splitting
Apache Commons as a project - the ideal committer on Apache Commons is
caring about all its components (avoiding the Jakarta pitfalls).

We had not considered becoming a TLP as once the API (mainly a set of
interfaces) is settled, by then it will probably be pretty much a
quiet project except the odd maintenance patch - and also by being a
common component of several RDF projects within Apache, its best home
then would be under Commons (presumably with most of the original
committers still involved).

However the large traffic of dev@commons (~400/month) about all the
other components can be a problem for trying to engage the non-Apache
community around commons-rdf while we flesh out the API. (This has
currently been done solely through Github issues, pull requests, and
"watching" the project).

In a way we are limited by the technology of the Apache mailing lists.
(I know, I know...).

(I mentioned )

The suggestion is that Commons-RDF could be a incubator project, but
with a projected path to become part of the Apache Commons instead of
a TLP.  (I believe this path has not happened before)

So this would be using the old structure of having a champion of
Apache Commons - could this be a workable incubator project?

In a way it would be incubating just the code until API maturity
rather than the community or "Apache Way" as both of those already

In such an (old skool) setup, would it be the Commons PMC /
dev@commons who would vote over the incubating releases?

Once "graduating" it would just become a component under Apache
Commons and the community would just be dev@commons where the
committers would already be members - the dev@rdf.incubator list would
simply close.

.. and where would mentors come from? Would existing committers from
those other Apache projects (Jena, Marmotta, Clerezza) be enough - or
should it be someone from IMPC or from dev@commons?

for the whole threads :)

---------- Forwarded message ----------
From: Stian Soiland-Reyes <>
Date: 20 January 2015 at 14:06
Subject: Re: [DISCUSS][RDF] Separate mailing list for Commons RDF
To: Commons Developers List <>

Agree that maybe the the Incubator with a projected path to the
Commons could be a workable middle ground while Commons-RDF is still
"incubating" code-wise (but not community or Apache Way-wise).

No earlier project has gone through this route
( ) - this would reuse the
deprecated "Champion" project to be Apache Commons instead of
Incubator PMC in this case.

Such a proposal has some good features - I presume commons-rdf
releases would still be voted over (and thus involve) the Commons PMC
and dev@commons  (as they would after "graduating").

As an API, then Commons-RDF should not be considered stable while
being in 0.x.x-incubating anyway.

On 20 January 2015 at 13:58, Torsten Curdt <> wrote:
>>  There are several ASF projects in the
>> RDF space.  They have been through the incubator.  Please do talk to those
>> projects if you have concerns.
> I am sorry - but how are those projects relevant in this case?
> And what's so bad about the incubator? You could (maybe) later on come
> to Commons.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Stian Soiland-Reyes
Apache Taverna (incubating)

Stian Soiland-Reyes
Apache Taverna (incubating)

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

View raw message