On 11/02/15 08:14, Sergio Fernández wrote:
On 10/02/15 21:31, Marvin Humphrey wrote:
If Commons is OK with this, I imagine this is a fine plan -- good
enough for
entering incubation.
I also think it would be OK for the project to decide it wants to
become a
TLP. Whether the project joins Commons or becomes its own TLP won't
impact
the number of people qualified to work on it. Some Apache TLPs are
effectively in maintenance mode and have very low activity, but still
have PMC
members willing to answer user questions, make security releases and file
"still here" quarterly reports. That seems like a legitimate
aspiration for
this project.
A potential Jena destination also seems as though it would have certain
advantages, though my naive speculation is that it might be
sub-optimal in
terms of providing neutral territory for negotiating a common API for
Jena and
Sesame.
In any case it seems likely that if the project achieves its design goal,
there will be people willing to work on it as long as both Jena and
Sesame
remain viable. That makes it different from other potential "maintenance
mode" TLPs which are in danger of stagnation because they cannot renew
their
communities.
Is that take roughly accurate, Sergio et al?
Completely :-)
Yes.
Personally, I'd keep the destination open for both TLP and Apache
Commons, then see where we are at graduation time. A lot of (good)
things can happen during incubation.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
