incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <>
Subject Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Date Wed, 02 Sep 2009 17:01:50 GMT
We have concluded that umbrellas are no good, and IIRC we have visited this
line of argument in the past, and perhaps it is time again.

My line is; for the sake of the projects, keep them reasonably small. Learn
the art of TAG, create a browse system where each project with the TAG shows
up, and decide suitable endorsed tags among the PMCs or Members.

-- Cheers

On Sep 2, 2009 11:58 PM, "Emmanuel Lecharny" <> wrote:

Guillaume Nodet wrote: > > We have in this proposal a lot of people who are
not felix committers and...
Having apache committers from a project be granted commit access to another
project is not really a problem, as soon as the other project's PMC decide
what are the "rules".

The new project can also be a Felix subproject, with specific commit access
granted to a specific set of committers, if needed. I'm pretty sure that
infra can deal with such a granularity. Also the felix PMC can check that
the new committers are not committing in the other projects, if needed.

So far, this is how we did for FtpServer, SSHd and Vysper in MINA. In fact,
Vysper is still in a sandbox, but I can see the moment where it will get
out, either as a MINA subproject, or as a TLP. The biggest advantage is
that, as all the committers were already working on other projects, and as
the MINA PMC was able to check that the project was following the rules (IP,
etc), it's far easier than going through incubation.

I can see how better it could be for Aries to start as a felix subproject,
for many reasons.

> > Even, if Aries was to compete against Felix in any way, it's not a good
> enough argument.  We ...
It would be better to see Felix as a OSGi aggregator (a bit like WS or DB
are), with potentially many implementations. It would be so great if Buildr,
Ant, Maven, Archiva, Continuum, were all embedded in a Build Tools project,
instead of being one of the 70 TLP. From the user PoV, it's difficult to
know what they all are doing.

This is a bit more general than just Felix, here. We have more than 70 TLP,
and this number will continue to grow in the next few years. Why can't we
aggregate projects within categories at some point ?

> > For the independance, the only real place I know which provides OSGi >
components, not tainted ...
I'm not sure that because a project has non apache committers, it should be
started in incubator, as soon as the TLP can "educate" the project. of
course, if all the peope are non apache committers, that's a different

That being said, the best would be to first check for synergies, then think
about creating the poddling if there are not too much overlap. Be pragmatic

cordialement, regards,
Emmanuel L├ęcharny

--------------------------------------------------------------------- To
unsubscribe, e-mail: ge...

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message