FINAL
This report has been submitted to the Board. Please do not edit further.
Incubator PMC report for January 2014
Timeline
Wed January 01 |
Podling reports due by end of day |
Sun January 05 |
Shepherd reviews due by end of day |
Sun January 05 |
Summary due by end of day |
Tue January 07 |
Mentor signoff due by end of day |
Wed January 08 |
Report submitted to Board |
Wed January 15 |
Board meeting |
Shepherd Assignments
Alan D. Cabrera |
Spark |
Alan D. Cabrera |
Usergrid |
Andrei Savu |
Olingo |
Andrei Savu |
Sirona |
Dave Fisher |
Celix |
John Ament |
BatchEE |
John Ament |
ODF Toolkit |
Justin Mclean |
Aurora |
Matthew Franklin |
Twill |
Matthew Franklin |
log4cxx2 |
Raphael Bircher |
Stratos |
Raphael Bircher |
VXQuery |
Roman Shaposhnik |
MetaModel |
Roman Shaposhnik |
Ripple |
Ross Gardler |
DeviceMap |
Suresh Marru |
Phoenix |
Suresh Marru |
Samza |
Report content
Incubator PMC report for January 2014 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are 36 podlings currently under incubation. * Community New IPMC members: (None) People who left the IPMC: (None) * New Podlings * DataFu makes it easier to solve data problems using Hadoop and higher level languages based on it. * Graduations (None) * Releases The following releases were made since the last Incubator report: Dec 16 Apache Sirona 0.1-incubating Dec 17 Apache Spark 0.8.1-incubating It took 6-21 days for the third IPMC vote to arrive. Release VOTE start Third IMPC +1 Days --------------------------------------------------------------------- Apache Sirona 0.1-incubating Nov 26 Dec 16 21 Apache Spark 0.8.1-incubating Dec 11 Dec 17 6 * IP Clearance * Apache Celix received the donation of a shared memory implementation of the remote service admin specification from Thales Nederland B.V.. * Miscellaneous * The initiative to reform release voting yielded multiple breakthroughs during this report cycle. 1. An experimental framework was approved whereby PPMC votes become binding for releases after the first if a release checklist is completed by the PPMC and approved by a Mentor. 2. A concise checklist of release requirements was assembled, where each item is required by either ASF-wide policy or Incubator policy. 3. Consensus was built for a controlled regime for relaxing policy on incubating releases under appropriate circumstances, potentially reducing the number of release candidates we force podlings to cycle through. All of this was achieved with significantly fewer emails compared with past reform attempts. * Exercising the new regime for controlled relaxation of policy, a bugfix release by Spark (0.8.1) which bundled jar files was approved by the IPMC after the podling presented a roadmap to eliminating them in the next minor point release (0.9). -------------------- Summary of podling reports -------------------- * Still getting started at the Incubator Log4cxx Phoenix * Not yet ready to graduate No release: Aurora BatchEE MetaModel Ripple Samza Twill Community growth: Celix ODF Toolkit Olingo Sirona Stratos VXQuery * Ready to graduate Spark * Did not report, expected next month DeviceMap Usergrid ---------------------------------------------------------------------- Table of Contents Aurora BatchEE Celix log4cxx2 MetaModel ODF Toolkit Olingo Phoenix Ripple Samza Sirona Spark Stratos Twill VXQuery ---------------------------------------------------------------------- -------------------- Aurora Aurora is a service scheduler used to schedule jobs onto Apache Mesos. Aurora has been incubating since 2013-10-01. Three most important issues to address in the move towards graduation: 1. First release. 2. Establish a consistent development process and release rhythm. 3. Expanding the community and adding new committers. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - Community members outside of Twitter are installing and testing the software, using the dev mailing list and IRC channel to offer feedback and seek help. - No new committers; still preparing for first release. How has the project developed since the last report? - Development work has transitioned to Apache Review Board in the open; JIRA issues still need to be transferred. - Continuous integration for Aurora set up on builds.apache.org. Date of last release: - No releases as of yet. Targeting first release for Q1. When were the last committers or PMC members elected? - No new committers; still stabilizing code and preparing for first release. Signed-off-by: [X](aurora) Jake Farrell [ ](aurora) Benjamin Hindman [ ](aurora) Chris Mattmann [X](aurora) Henry Saputra Shepherd/Mentor notes: Justin Mclean (jmclean): Project is off to a good start with lots of activity on the mailing list and in JIRA. One of the Mentors (Jake Farrell) is very active and there are no issues that need attention. -------------------- BatchEE BatchEE is a JBatch implementation with few utilities modules. BatchEE has been incubating since 2013-10-03. Three most important issues to address in the move towards graduation: 1. Release 2. Decide if BatchEE keeps integration with other frameworks or not (camel, etc) 3. Provide some more samples Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? Community itself is almost the same (but was holidays ;) but we start to get some enterprise users :). How has the project developed since the last report? Integration with other project grown. Few bugfixes were done. Date of last release: Not yet released. When were the last committers or PMC members elected? Signed-off-by: [ ](batchee) Jean-Baptiste Onofré [X](batchee) Olivier Lamy [ ](batchee) Mark Struberg Shepherd/Mentor notes: John Ament (johndament): BatchEE is a new podling, with a small team working on it currently. It's a fork of the RI for Java Batch from Java EE 7. I think short term they should focus on getting a release out there to draw in community interest; which should help build the podling more and drive feature interest. -------------------- Celix Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C. Celix has been incubating since 2010-11-02. Three most important issues to address in the move towards graduation: 1. Publish a new release (see below) 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? Together with the donation of a new Remote Services Admin we have added Bjoern Petri as committer. The work being done on the GSoC project is mostly finished but still needs some finishing up before it can be added to the repository. If the code donated by Bjoern is added to the project a new release will be made. In this release we will try to solve all remarks of the first release. A discussion concerning graduation has also been started, if this goes well, we want to start the vote on the Celix list and then ask the IPMC if Celix is ready to graduate. How has the project developed since the last report? There is a new Remote Service Admin which can be used alongside the current one. There is also the GSoC project which can be added after the second release. Altogether most work has been done to be able to make a release. Issues have been solved/closed/updated etc. Date of last release: 16-12-2012 When were the last committers or PMC members elected? 2014-01-03 Bjoern Petri elected as committer (still needs to be added to the Celix group). 2013-01-07 Roman Shaposhnik joins as a mentor. 2012-03-20 Pepijn elected as committer. Signed-off-by: [ ](celix) Marcel Offermans [ ](celix) Karl Pauls [X](celix) Roman Shaposhnik Shepherd/Mentor notes: Dave Fisher (wave): This podling is growing. They plan a release soon and let's see how that goes. When it comes time for graduation I have some concerns that this podling's community may be too small. -------------------- log4cxx2 Logging for C++ log4cxx2 has been incubating since 2013-12-09. It is a reboot of an earlier, stalled logging project with a new collection of committers. Three most important issues to address in the move towards graduation: 1. Triage on old, pre-incubation issues in JIRA and reported mailing lists with an eye towards initial re-release blockers 2. Solving those blockers on a minimal set of platforms to permit initial re-release. 3. Reengaging former user community, many of whom left as previous incarnation became dormant. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? The committers are getting acquainted with each other and the foundation. How has the project developed since the last report? This is our first report. Date of last release: 2008-04-03 was the official, pre-incubation 0.10.0 Many post-0.10.0 commits exist on trunk which we intend to get out as 0.11.x. When were the last committers or PMC members elected? N/A Signed-off-by: [X](log4cxx2) Christian Grobmeier [ ](log4cxx2) Scott Deboy Shepherd/Mentor notes: Christian Grobmeier (grobmeier): the podling is just getting started -------------------- MetaModel MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. MetaModel has been incubating since 2013-06-12. Three most important issues to address in the move towards graduation: 1. More contributors to increase diversity of the community 2. Make first release under ASF umbrella 3. Set better guidelines for procedures by setting community by-laws 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're working on making the first release under the Apache umbrella available. A first release candidate was rejected in the vote for technical reasons, but these where fixed by the second release candidate and a few JIRA entries to improve build-time validation. Various requests and questions are coming in through the dev mailing list. We believe this activity will further accelerate when our first release is available. We've been drafting a set of community by-laws, but open questions and discussions are still not settled, so this is only work-in-progress. How has the project developed since the last report? We've implemented various performance and concurrency related improvements to the working of MetaModel. Test suites have been improved to work properly on different locales, operating systems etc. Many minor changes to build configuration, license files etc., as a result of working towards a release. Date of last release: None When were the last committers or PMC members elected? June 2013 Signed-off-by: [X](metamodel) Henry Saputra [X](metamodel) Arvind Prabhakar [ ](metamodel) Matt Franklin [ ](metamodel) Noah Slater Shepherd/Mentor notes: Roman Shaposhnik (rvs): In general project seem to be on the right track with a healthy amount of community interaction happening over the mailing list and a strong desire to do a release. Two issues have caught my attention though: 1. I am not quite sure what motivated a strong drive towards having by-laws this early in the game. In my experience the focus on by-laws can, at times, put a damping factor on community growth. IOW, what I've seen in the past is that communities try to come up with by-laws when the usual process of consensus building starts to fail. Nothing actionable here for the project -- just keep this in mind. 2. The JIRA feels a bit empty for the project that has been developing for more than 6 month (grand total of 33 issues). At the same time the number of commits in the Git repo is on par with the development pace. What it tells me is that there's no strong correlation between JIRAs and commits. This raises a red flag of whether all of the changes that are committed get a proper community vetting before they go in. I couldn't find any traces of the review requests either: https://reviews.apache.org/groups/metamodel/ This in my opinion is a pretty big concern for the project. -------------------- ODF Toolkit Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents ODF Toolkit has been incubating since 2011-08-01. Three most important issues to address in the move towards graduation: 1. Grow the community in terms of committers 2. Have regular releases 3. Decide if we would like to be a top level project or join an existing project Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - How has the community developed since the last report? We received patches and issue reports from users, but no new developers. We're discussing on our dev list an initiative to take advantage of our next release to publicize the project and attract new developers. How has the project developed since the last report? Minor issues have been fixed. We are also working on an adapter for the POI API that is not yet committed but will be soon. We are planning to have a release this month. Date of last release: 2013-06-22 When were the last committers or PMC members elected? 2012-10-29 Signed-off-by: [ ](odftoolkit) Sam Ruby [ ](odftoolkit) Nick Burch [ ](odftoolkit) Yegor Kozlov Shepherd/Mentor notes: John Ament (johndament): ODF Toolkit has been incubating for a long time. Activity on their list is in frequent, but active enough that it still is running. Considering what the project is, I think the best resolution for this podling is to graduate as a sub project under something like OpenOffice or POI. -------------------- Olingo Apache Olingo provides libraries which enable developers to implement OData producers and OData consumers. While starting with an initial code base implementing OData version 2.0 it is also a clear goal to start implementing a library for OData 4.0 once the OData standard is published at OASIS. The focus within the community is currently on the Java technology but it is up to the community to discuss if other environments find interest. Olingo has been incubating since 2013-07-08. Three most important issues to address in the move towards graduation: 1. Grow community 2. n/a 3. n/a Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - n/a How has the community developed since the last report? - Committers actively worked together to make the first release. Effort was coordinated by Jira and mailing list. - Committers actively working on making the second release. Effort is coordinated by Jira and mailing list. - Committers are in mailing list contact with mentors and infrastructure to extend infrastructure setup (e.g. Wiki). - Community has grown: Additional committers, new contributors (can be seen via Jira Issues, Mailing List), but the community is still homogeneous which needs to change for graduation How has the project developed since the last report? - There is currently no feature development for OData 2.0 (stabilization phase for making the second release) - Documentation on web site is refactored and growing - There is feature development for OData 4.0 in a new repository. This new development will not be part of the second release Date of last release: 2013-10-16 When were the last committers or PMC members elected? 2013-12-05 Signed-off-by: [X](olingo) Alan Cabrera [X](olingo) Dave Fisher [X](olingo) Florian Müller -------------------- -------------------- Phoenix Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Phoenix has been incubating since 12/11/2013. Three most important issues to address in the move towards graduation: 1) Get the necessary IP clearance from Salesforce to import and re-license existing open source project under pheoenix.incubator.apache.org. 2) Get verification that our project name is acceptable [1]. 3) Perform first release out of apache incubator Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? This is our first report. No issues at this time. How has the community developed since the last report? - Questions are starting to come in on the apache dev and user mailing lists. - No new committers. How has the project developed since the last report? - The proposal committers have all been setup with Apache accounts. - Website is up [2] - Mailing lists and source repo have all set up (thanks to INFRA). - Working toward a 3.0.0 release in our existing open source project while we wait for on 1.) above. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members. [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2 [2] http://phoenix.incubator.apache.org/ Signed-off-by: [x](phoenix) Lars Hofhansl [ ](phoenix) Andrew Purtell [x](phoenix) Devaraj Das [x](phoenix) Enis Soztutar [x](phoenix) Steven Noels -------------------- 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. Fix licensing issues, specifically some of the images. 2. Build up the community. 3. Make a release under Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? We are still seeing increased non-committer participation in threads, issues, etc. Most of the recent work has been committer based. How has the project developed since the last report? Participation stable, no further news. Date of last release? N/A When were the last committers or PMC members elected? When we were inducted into Apache. Signed-off-by: [ ](ripple) Jukka Zitting [X](ripple) Christian Grobmeier [ ](ripple) Andrew Savory Shepherd/Mentor notes: Roman Shaposhnik (rvs): The project appears to be doing well -------------------- Samza Samza is a stream processing system for running continuous computation on infinite streams of data. Samza has been incubating since 2013-07-30. Three most important issues to address in the move towards graduation: 1. Bring in new community members 2. Make a release 3. Cement ASF way to community. 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? Active mailing list with questions from new users trying out the project. Virtually all answers responded to within 24 hours. Presentations given at London HUG (remote) and QCon SF to promote project. Additional presentations scheduled for user groups in Seattle and Los Angeles. Code contributions have been received from three new contributors, none of whom are affiliated with the original grantor of the code. How has the project developed since the last report? Since Oct 1, 2013, 61 issues have been opened, 32 have been resolved. There is active discussion on the JIRA over significant changes to the current code. The code is ripe for a release. Date of last release: None. When were the last committers or PMC members elected? None. Signed-off-by: [X](samza) Chris Douglas [ ](samza) Arun Murthy [X](samza) Roman Shaposhnik -------------------- Sirona Monitoring Solution java oriented. Sirona has been incubating since 2013-10-15. Three most important issues to address in the move towards graduation: 1. Stabilize the javaagent API and features. 2. Stabilize test portability/stability (if possible). 3. Get more commiters. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? In interest yes, not really in contributor (but was holidays ;). How has the project developed since the last report? The project API starts to be stable and now javaagent needs enhancements and efforts. Date of last release: 2013-17-12 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 -------------------- Spark Spark is an open source system for fast and flexible large-scale data analysis. Spark provides a general purpose runtime that supports low-latency execution in several forms. Spark has been incubating since 2013-06-19. Three most important issues to address in the move towards graduation: 1. Pretty much the only issue remaining is importing our old JIRA into Apache (https://issues.apache.org/jira/browse/INFRA-6419). Unfortunately, although we've been trying to do this since June, we haven't had much luck with it, as the INFRA people who tried to help out have been busy and software version numbers have often been incompatible (we have a hosted JIRA instance from Atlassian that they regularly update). We believe that there are some export dumps on that issue that are compatible with the ASF's current JIRA version, but if we can't get this resolved in the next 2-3 weeks, we may simply forgo importing our old issues. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? It would be really great to get a contact who can sit down with us and do the JIRA import. We're not sure who from INFRA leads these tasks. How has the community developed since the last report? We made a Spark 0.8.1 release in December, and are working on a new major release (0.9) this month. We added two new committers, Aaron Davidson and Kay Ousterhout. How has the project developed since the last report? We made the Spark 0.8.1 release mentioned above, with a number of new features detailed at http://spark.incubator.apache.org/releases/spark-release-0-8-1.html. We also have some exciting features coming up in Spark 0.9, such as support for Scala 2.10, parallel machine learning libraries in Python, and improvements to Spark Streaming. Date of last release: 2013-12-19 When were the last committers or PMC members elected? 2013-12-30 Signed-off-by: [ ](spark) Chris Mattmann [ ](spark) Paul Ramirez [ ](spark) Andrew Hart [ ](spark) Thomas Dudziak [X](spark) Suresh Marru [X](spark) Henry Saputra [X](spark) Roman Shaposhnik Shepherd/Mentor notes: Alan Cabrera (acabrera): Seems like a nice active project. IMO, there's no need to wait import to JIRA to graduate. Seems like they can graduate now. -------------------- Stratos Stratos will be a polyglot PaaS framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform- wide insight including monitoring and billing. Stratos has been incubating since 2013-06-20. Three most important issues to address in the move towards graduation: 1. Diversify the community 2. Clear trademark 3. Start Graduation 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? Two new committers & PMC members have been added to the project. (In Stratos, committers are also invited to join the PMC). Seven Google Hangouts were held in order to educate the community about the project & the technical details/architecture in the project. Conduct a Cloud BarCamp on 28th October to enable the Stratos community members as well as other Apache cloud project community members to meet up & exchange ideas & build synergy. Community members have also written several blog posts. The project has also seen a number of new contributors who have started actively participating in the project. How has the project developed since the last report? Stratos 3.0.0-incubating released. Started discussions on new architecture and start working on that. Five developer previews (Stratos 4.0.0 milestones) has been released on new architecture. Date of last release: 2013-11-15 - Stratos 3.0.0-incubating When were the last committers or PMC members elected? 2013-12-06 Signed-off-by: [x](stratos) Afkham Azeez [ ](stratos) Anthony Elder [ ](stratos) Chip Childers [ ](stratos) Marlon Pierce [ ](stratos) Mohammad Nour [ ](stratos) Noah Slater Shepherd/Mentor notes: Raphael Bircher (rbircher): The project looks realy active. Continue like this guys! -------------------- Twill Twill is an abstraction over Apache Hadoop® YARN to reduce the complexity of developing distributed applications. Twill has been incubating since 2013-11-14. Top three items to resolve before graduation: - More committers from different organizations. - IP clearance. - Regular Releases. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - Activity on the dev list up from 37 messages in November to 141 in December. - Subscribers to the dev list up from 15 to 24. - No new contributors. How has the project developed since the last report? - Website has been set up. Date of last release: - No releases as of yet. Targeting first release for January. What are the plans for the next period? - Finish IP clearance - Initial Release When were the last committers or PMC members elected? - No new committers since incubation. Signed-off-by: [ ](twill) Vinod K [ ](twill) Arun C Murthy [ ](twill) Tom White [X](twill) Patrick Hunt [ ](twill) Andrei Savu -------------------- VXQuery A standards compliant parallel XML Query processor. VXQuery has been incubating since 2009-07-06. There are no formal issues blocking graduation. The issue of off-list discussions that was identified by the mentors a few month ago has been addressed. While off-list discussions are still happening, (intermediate) results of those discussions are now regularly brought back to the list. While not a formal requirement, the current plan is to do a second incubator release before graduation to a) release the changes that accumulated while the first release was prepared and to b) have a release prepared by another RM. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No. How has the community developed since the last report? Marvin Humphrey agreed to mentor VXQuery and the project now has 3 active mentors. How has the project developed since the last report? The first incubating release has been released on Dec 6. Progress has been made on - the definition of the benchmark, on - improving the performance of the system, and on - running VXQuery on a cluster. Date of last release: 2013-12-06 When were the last committers or PMC members elected? Marvin Humphrey was added to the PPMC as a mentor in November 2013. Steven Jacobs was elected as a committer in September 2013. Signed-off-by: [ ](vxquery) Anthony Elder [ ](vxquery) Jochen Wiedmann [X](vxquery) Marvin Humphrey [ ](vxquery) Sanjiva Weerawarana [ ](vxquery) Radu Preotiuc-Pietro Shepherd/Mentor notes: Raphael Bircher (rbircher): The mailing list traffic is not very high. However, the basic discussions are on the lists. -------------------- Usergrid Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. Usergrid has been incubating since 2013-10-03. Three most important issues to address in the move towards graduation: 1. Learning the Apache Way 2. Growing a diverse community 3. Getting project infrastructure and codebase setup at Apache Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time How has the community developed since the last report? - No changes since last report How has the project developed since the last report? - We've been importing JIRA issues, which may help us gain some new committers - Contributors have been discussing the project road map - Progress has been made on migrating all package naming to org.apache.usergrid Date of last release: - No releases yet. When were the last committers or PMC members elected? - When we entered incubation Signed-off-by: [X](snoopdave) Dave Johnson [X](jfarrell) Jake Farrell [ ](jim) Jim Jagielski [X](lewismc) Lewis John Mcgibbney [x](lresende) Luciano Resende