Hello, Incubator community, As discussed in a recent thread on Mentoring, the draft report email provides an opportunity for cross-cutting feedback. So here goes!
The top-level report was not yet complete when the draft was sent out (and what sections were there I wrote), so I have nothing to say about that. But I have some comments in response to the podling reports for Droids, HTrace, Ripple, SAMOA, and Sirona which I hope will prove constructive. > -------------------- > Droids > > Droids aims to be an intelligent standalone robot framework that allows to > create and extend existing droids (robots). > > Droids has been incubating since 2008-10-09. > > Three most important issues to address in the move towards graduation: > > 1. Activity > 2. Name Search > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > None. > > We need to continue the name search. Branding has replied to the issue and > provided additional searches that need to performed. It is hoped that > these can be finished in the new couple weeks. > > How has the community developed since the last report? > > No change. > > How has the project developed since the last report? > > No change. > > Date of last release: > > 2012-10-15 > > When were the last committers or PMC members elected? > > 2012-05-07 > > > Signed-off-by: > > [ ](droids) Thorsten Scherler > [x](droids) Richard Frovarp > > Shepherd/Mentor notes: > > > > It's my understanding that Droids is basically a mature product with no pressing need for further development, not unlike some dormant Apache TLPs who neverthess still have PMC members hanging around able to make releases and respond to user inquiries. I think the greater IPMC ought to stay aware, though, that Droids has very, very low activity: 3 dev list emails in the last quarter (39 in the last year), no user list, and no commits since April 2013. The only thing between Droids and retirement is our deference to Richard and Thorsten. They form the potential core of a community, but it has yet to develop in 6 years of incubation. > -------------------- > HTrace > > HTrace is a tracing framework intended for use with distributed systems > written in java. > > HTrace has been incubating since 2014-11. > > Three most important issues to address in the move towards graduation: > > 1. Continue to grow the HTrace community > 2. Continue to develop and release stable HTrace incubating artifacts > 3. Continue to explore the integration of the HTrace framework into other > Apache products > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > Around January 20th HTrace successfully made the first release whilst in > the Apache Incubator. This was the outcomes of no-less than 10 release > candidates and as many VOTE's. In all every release candidate was very > well managed with HTrace community providing excellent feedback to the > release manager. Rather than then entire 10 release candidate exercise > being a pain point for the community, it appears to have strengthened all > involved. Well done HTrace. > > How has the community developed since the last report? > > It is early incubating days for HTrace. The community has attracted in > particular a new member who is doing a sterling job on a new UI for > HTrace. Additionally it should be noted that the entire > htrace-3.1.0-incubating release effort has certainly brought the existing > community on leaps and bounds. > > How has the project developed since the last report? > > The project has progressed significantly. In fact, it was highlighted on > at least one occasion that documentation supporting a release candidate > should be further clarified/improved due to the dynamic progressive nature > of the HTrace codebase. As an early incubating project this is accepted as > a positive move. > > Date of last release: > > 2015-20-01 > > When were the last committers or PMC members elected? > > ??? > > Signed-off-by: > > [X](htrace) Jake Farrell > [ ](htrace) Todd Lipcon > [X](htrace) Lewis John Mcgibbney > [ ](htrace) Andrew Purtell > [X](htrace) Billie Rinaldi > [X](htrace) Michael Stack 10 release candidates is a lot. Were the difficulties primarily the result of the community needing to develop and document its own release routines? It sounds like that was the case, which would be reasonable. But if, say, determining compliance with Apache policy a major problem, I think it would benefit the IPMC to know that. > -------------------- > Ripple > > Ripple is a browser based mobile phone emulator designed to aid in the > development of HTML5 based mobile applications. Ripple is a cross platform > and cross runtime testing/debugging tool. It currently supports such > runtimes as Cordova, WebWorks aand the Mobile Web. > > Ripple has been incubating since 2012-10-16. > > Three most important issues to address in the move towards graduation: > > 1. Ripple releases > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > The community is working on making a release of the Ripple project. > > How has the community developed since the last report? > > Community working on making a release > > How has the project developed since the last report? > > Minor user contributions > > Date of last release: > > No releases have been made. Community working on > > When were the last committers or PMC members elected? > > June 2014 > > Signed-off-by: > > [ ](ripple) Jukka Zitting > [X](ripple) Christian Grobmeier > [ ](ripple) Andrew Savory > > Shepherd/Mentor notes: > > Christian Grobmeier (grobmeier): > > Ross Gardler stepped up as a mentor. There are new active people on the > project which makes it likely to expand the committer team soon. Not that we want to get hung up on process, but it sounds like we should add Ross to the list of Ripple Mentors in podlings.xml. Would that be appropriate? And are Jukka and Andrew still active? > -------------------- > SAMOA > > SAMOA provides a collection of distributed streaming algorithms for the most > common data mining and machine learning tasks such as classification, > clustering, and regression, as well as programming abstractions to develop > new algorithms that run on top of distributed stream processing engines > (DSPEs). It features a pluggable architecture that allows it to run on > several DSPEs such as Apache Storm, Apache S4, and Apache Samza. > > SAMOA has been incubating since 2014-12-15. > > Three most important issues to address in the move towards graduation: > > 1. Create bylaws for the project > 2. Migrate documentation from the old website > 3. Start committing patches > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > None > > How has the community developed since the last report? > > We have started using the official Apache channels to discuss about SAMOA. > A couple of new people have showed up on the mailing lists. We have one > new contributor submitting patches. > > Mailing list activity (since January 2015): > > * @dev 101 messages > > Jira issues backlog (since January 2015): > > * Created: 13 > * Resolved: 2 > > How has the project developed since the last report? > > The project setup is going on nicely. We got the SGA from Yahoo and > migrated the code to the Apache git repository, enabled GitHub integration > (https://github.com/apache/incubator-samoa), migrated the website to the > Apache infrastructure and added the Incubator branding > (http://samoa.incubator.apache.org), enabled testing via Travis CI. > > Date of last release: > > None > > When were the last committers or PMC members elected? > > None > > Signed-off-by: > > [ ](samoa) Alan Gates > [ ](samoa) Ashutosh Chauhan > [ ](samoa) Enis Soztutar > [X](samoa) Ted Dunning > > Shepherd/Mentor notes: > > Justin Mclean (jmclean): > > Just starting, mentors active. I'm a little surprised to see creation of bylaws listed as the top priority for a brand new podling. Bylaws limit flexibility; I would have thought it better to wait until near graduation to perform such a task (if at all). Have other podlings done this? Is there something unusual about SAMOA? > -------------------- > Sirona > > Monitoring Solution. > > Sirona has been incubating since 2013-10-15. > > Three most important issues to address in the move towards graduation: > > 1. > 2. > 3. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > None > > How has the community developed since the last report? > > > > How has the project developed since the last report? > > Some refactoring of the UI. A contributor made some development to have > some features still working with java 1.5 > > Date of last release: > > 2014-06-26 > > When were the last committers or PMC members elected? > > > > Signed-off-by: > > [x](sirona) Olivier Lamy > [ ](sirona) Henri Gomez > [ ](sirona) Jean-Baptiste Onofre > [ ](sirona) Tammo van Lessen > [ ](sirona) Mark Struberg > > Shepherd/Mentor notes: > > Matthew B. Franklin (mfranklin): > > Lot's of code is being committed to the project, but mostly by a couple of > developers. There also does not appear to be much discussion on the list > in last period, likely due to the low number of developers. > > I recommend the podling focus on increasing the size and participation of > the community as one of the issues to address prior to graduation. This report seems incomplete. A Mentor has signed off so in deference to him I think it should be sent along to the Board, but that Sirona should be asked to report again next month and an explanatory note should be added. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
