On 11 February 2015 at 07:31, Marvin Humphrey <mar...@rectangular.com> wrote: > On Tue, Feb 10, 2015 at 7:21 AM, Stian Soiland-Reyes <st...@apache.org> wrote: > >> The natural path to Apache Commons Sandbox has been studied, but we >> think that in this phase of the project, which focuses on the API >> design and actively involves the developers of existing toolkits, it >> is better to have a more focused community and infrastructure. Rather >> than a new Top-Level Project, the goal is still to graduate as part of >> Apache Commons, that is when API has achieve the required maturity and >> the project goes into maintenance mode. > > 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.
I don't think it would be appropriate inside of Jena for similar reasons, although not just related to Sesame, as there are other JVM toolkits that we also want to attract in a neutral way. For similar reasons it wouldn't be appropriate within the other related Apache projects, although it will likely be used by all of them in the end (Any23/Marmotta/Stanbol/Clerezza/Taverna). > 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. Both Jena and Sesame will remain viable for a while to come IMO, based on the commercial users of both platforms and their respective communities are both well-established and active. > Is that take roughly accurate, Sergio et al? > >> === Mailing lists === >> >> * commons-rdf-dev >> * commons-rdf-commits > > Those sound like final mailing lists rather than Incubator ones. I might have > expected these instead: > > d...@commons-rdf.incubator.apache.org > comm...@commons-rdf.incubator.apache.org > > Do you expect to keep separate mailing lists after graduation, or will traffic > be shunted onto existing Commons mailing list like d...@commons.apache.org and > comm...@commons.apache.org? I would expect the level of discussion and commits to go down just after graduation, per our goal to have a stable common interface, so being then integrating into the main commons dev would be the likely channel. However, unlike previous APIs, we do have the advantage of Java-8 default methods, so we can also add to the API while maintaining backwards compatibility, so we are open for additions even after the initial version of the API is finalised. >> * Sergio Fernández (wikier dot apache dot org) >> * Andy Seaborne (andy dot apache dot org) >> * Peter Ansell (ansell dot apache dot org) >> * Stian Soiland-Reyes (stain at apache dot org) >> * Reto Gmür (reto at apache dot org) > > Lots of Apache experience in this group. Four are PMC members of at least one > Apache project. Andy and Reto are ASF Members. Andy and Sergio are both IPMC > members. Stian is a core contributor of the Taverna podling. > > You probably haven't been getting much feedback because there's a lot going on > in the Incubator right now and everybody figures that with a group like that > you're in good shape. :) > > === Champion === > > * TBD > > The Champion's main work is to help formulate the proposal. That work is > essentially done -- so it doesn't matter too much who takes that role, now. > Are Andy and Reto opting out out as a gesture of openness to Sesame? Sergio has been the Champion from the beginning, but anyone who is at the right community position from the team would be great. >> === Nominated Mentors === >> >> * Benedikt Ritter (britter at apache dot org) >> * TBD > > Benedikt is a member of the Commons PMC, but he's not a member of the IPMC nor > an Apache Member -- so although Commons input is important, unfortunately it's > not a valid nomination. > > I'd nudge newly elected IPMC member Rob Vesse, but maybe the roster is already > Jena-heavy? I don't think that is an issue. Rob Vesse would be very appropriate for that position IMO given his experience. Cheers, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
