Hi Reto, thanks for the input. I think we are well aware of the topic you raise. I also accept that there is some perceived competition between Clerezza and Marmotta, even though I personally think in reality the systems are very different and follow different philosophies and goals. I can understand your (first) comment to the marmotta mailinglist under this light.
However, it is not true that the committers are all from Salzburg Research: we already have official contributors from three different legal entities (Salzburg Research, the startup RedLink, and our new community member Raffaele), as well as several inofficial contributors that are currently using the technology in different projects. Additionally, the funding for at least 3 years of further development has been secured and there is a contractual commitment by Salzburg Research and other organisations to invest this money into the development of Marmotta (and Stanbol). Also, if you look at the commit logs, our community is bigger and shows considerably more activity than many other Apache projects (among them Clerezza). Despite all this, I agree that we should not hurry unnecessarily and first grow a broader community and accept more members that were not part of the original founders. And I am very confident that we will be able to do this in the coming months. I therefore suggest that we remain in incubation until the next release at least, and use the time to solve remaining issues (like the outstanding legal issues regarding the NOTICE files that were discussed on general@incubator...) and recruit more community members. Greetings, Sebastian 2013/6/3 Reto Bachmann-Gmür <r...@apache.org> > On Tue, May 28, 2013 at 12:16 PM, Andy Seaborne <a...@apache.org> wrote: > > > On 27/05/13 15:27, Sergio Fernández wrote: > > > >> FMPOV is too early to think about such option. We still need to > >> demonstrate some things: stablish releases cycles, being able to publish > >> maintenance releases, grow the community, etc. > >> > >> Do you think we could be ready? Personally I'm not sure. > >> > > > > All good points, especially the transition from the original single-site > > team to the wider community of developers. > > > > Communities continue to grow and evolve after graduation. > > > In my understanding having active contributor in at least 3 geographically > and organisational distinct places is a prerequisite for graduation. > > When I look at the commits from the last months they all seem to originate > from people associated to Salzburg Research. I think it is important that > apache projects are not de-facto run by a single institution. I think the > diversity requirement also fosters integration and collaboration with other > apache projects. > > Cheers, > Reto > > > > > > The test question whether being in incubation helps in any way with those > > things or whether its merely which side of some arbitrary line the > project > > is while progressing those issues. > > > > Just after graduation is an interesting time for any project. > > > > So concretely - what more can incubation give you? > > > > Andy > > > > > > > >> > >> On 27/05/13 15:30, Andy Seaborne wrote: > >> > >>> The report for April said the top three items to address in the move > >>> towards graduation were: > >>> > >>> 1. Ingest code and clear IP. > >>> 2. A release > >>> 3. Build dev and PMC. > >>> > >>> Tick; tick; and we've added to the PPMC. > >>> > >>> So - more to do? or is next time to graduate? > >>> > >>> http://incubator.apache.org/**guides/graduation.html< > http://incubator.apache.org/guides/graduation.html> > >>> > >>> Andy > >>> > >>> > >>> > >> > > >
