incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: [DRAFT] Incubator PMC Board report - March 2017
Date Mon, 06 Mar 2017 14:44:38 GMT
Pierre,

Anyone who has edit access can change.  I did not enter Trafodion's report,
hzeller did.

John

On Mon, Mar 6, 2017 at 9:40 AM Pierre Smits <pierre.smits@gmail.com> wrote:

> Hi John,
>
> I suggest that you change the setting regarding the maturity question in
> the Trafodion report
> from:
>
> Community building
>
> to:
>
> Nearing graduation
>
> The discussion on dev@trafodion.i.a.o. shows that the majority of
> reactions
> provided, on the question whether the podling is ready to graduate,
> indicate that project is ready or that respondents feel that the project
> would gain more credibility visavis adoption by users and would be able to
> attract more contributors when having the TLP status.
>
> Trafodion is facing a chicken-egg situation in that respect.
>
> Should you have any questions and/or remarks, feel free to contact me.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Mar 6, 2017 at 1:39 PM, John D. Ament <john.d.ament@gmail.com>
> wrote:
>
> > All,
> >
> > Below is the current draft of our board report.  As of writing, 5
> podlings
> > are missing, and many more need some sign offs.
> >
> > Incubator PMC report for March 2017
> >
> > 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 currently 64 podlings incubating.  In the month of February we
> > had 7 releases and no changes in IPMC roster.
> >
> > * Community
> >
> >   New IPMC members:
> >
> >   - None
> >
> >   People who left the IPMC:
> >
> >   - None
> >
> > * New Podlings
> >
> >   - Gobblin
> >
> >
> > * Podlings that failed to report, expected next month
> >
> >   - Atlas
> >   - Griffin
> >   - Pony Mail
> >   - Sirona
> >   - Weex
> >
> > * Graduations
> >
> >   The board has motions for the following:
> >
> >   - None
> >
> > * Releases
> >
> >   The following releases entered distribution during the month of
> >   February:
> >
> >   - 2017-02-02  Apache Guacamole 0.9.11
> >   - 2017-02-08  Apache SystemML 0.12.0
> >   - 2017-02-12  Apache Singa 1.1.0
> >   - 2017-02-15  Apache mynewt 1.0.0-b2
> >   - 2017-02-20  Apache RocketMQ 4.0.0
> >   - 2017-02-25  Apache Juneau 6.1.0
> >   - 2017-02-27  Apache HAWQ 2.1.0.0
> >
> > * IP Clearance
> >
> >
> >
> > * Legal / Trademarks
> >
> >   - A great discussion happened regarding the IP clearance and missing
> SGA
> > around MADLib.  It demonstrates the needs to ensure that proper
> provenance
> > is in place.
> >
> > * Infrastructure
> >
> >
> >
> > * Miscellaneous
> >
> >
> >
> > * Credits
> >
> >   - Report Manager:
> >
> > ----------------------------------------------------------------------
> >                        Table of Contents
> > AriaTosca
> > Atlas
> > Gearpump
> > Griffin
> > Hivemall
> > HTrace
> > log4cxx2
> > Mnemonic
> > MRQL
> > MXNet
> > Myriad
> > ODF Toolkit
> > Omid
> > OpenWhisk
> > Pirk
> > Pony Mail
> > Quickstep
> > Ratis
> > RocketMQ
> > SAMOA
> > Singa
> > Sirona
> > Spot
> > Streams
> > Taverna
> > Tephra
> > Trafodion
> > Wave
> > Weex
> >
> > ----------------------------------------------------------------------
> >
> > --------------------
> > AriaTosca
> >
> > ARIA TOSCA project offers an easily consumable Software Development
> > Kit(SDK)
> > and a Command Line Interface(CLI) to implement TOSCA(Topology and
> > Orchestration Specification of Cloud Applications) based solutions.
> >
> > AriaTosca has been incubating since 2016-08-27.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Grow the community and enroll new committers.
> >   2. Have frequent Release cycles to be compliant with the Apache Way.
> >   3. Update ARIA website according to ASF guideline(Include release
> process
> > for ARIA-TOSCA Project).
> >   4. Publish "How To Contribute" guide at ARIA-TOSCA Website.
> >
> >  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?
> >
> >   Most of the project discussions are now happening on mailing lists.
> >
> >  How has the project developed since the last report?
> >
> >   TOSCA parser migrated into ASF
> >   CI on Appveyor, Jenkins
> >   Sphinx documentation added to the project
> >   CLIs of workflow engine and parser coalesced
> >   TOSCA CSAR packager added
> >   APIs for workflows, operations
> >   Workflow engine task retry support
> >   Workflow engine execution cancel support
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [X] Working towards first release
> >   [] Community building
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   No release yet
> >
> > When were the last committers or PPMC members elected?
> >
> >   Project is still operating with the initial set of committers.
> >
> > Signed-off-by:
> >
> >   [X](ariatosca) Suneel Marthi
> >      Comments: Podling activity has been consistent and discussions are
> now
> > happening on the mailing lists.
> >   [X](ariatosca) John D. Ament
> >      Comments: Podling activity peaks and dives.  Would like to see more
> > on-list chatter.
> >   [ ](ariatosca) Jakob Homan
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Atlas
> >
> > Apache Atlas is a scalable and extensible set of core foundational
> > governance
> > services that enables enterprises to effectively and efficiently meet
> their
> > compliance requirements within Hadoop and allows integration with the
> > complete
> > enterprise data ecosystem
> >
> > Atlas has been incubating since 2015-05-05.
> >
> > 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?
> >
> >
> >
> > How has the community developed since the last report?
> >
> >
> >
> > How has the project developed since the last report?
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [ ](atlas) Arun Murthy
> >      Comments:
> >   [ ](atlas) Chris Douglas
> >      Comments:
> >   [ ](atlas) Jakob Homan
> >      Comments:
> >   [ ](atlas) Vinod Kumar Vavilapalli
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >   - Reminder sent.
> >
> > --------------------
> > Gearpump
> >
> > Gearpump is a reactive real-time streaming engine based on the
> > micro-service
> > Actor model.
> >
> > Gearpump has been incubating since 2016-03-08.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Release on a regular schedule.
> >   2. Continue to evolve community interest and support.
> >   3. Integrate within Apache Beam and Akka-stream frameworks.
> >
> > 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?
> >
> >  - Increased community contribution on Docker integration improvement.
> >
> >  - Applied for Google Summer of Code 2017 and we already have students
> >    interested in our project.
> >
> > How has the project developed since the last report?
> >
> >  - 34 issues created and 34 issues resolved.
> >  - Added finite stream and session windows support.
> >  - Akka-stream feature branch has been merged into master.
> >  - Continued integration within Apache Beam (Gearpump Runner).
> >    14 issues resolved.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-11-30 *and we plan to make next release in early March*.
> >
> > When were the last committers or PPMC members elected?
> >
> >  - No new committers or PMC members elected yet.
> >
> > Signed-off-by:
> >
> >   [X](gearpump) Andrew Purtell
> >      Comments:
> >   [ ](gearpump) Jarek Jarcec Cecho
> >      Comments:
> >   [ ](gearpump) Reynold Xin
> >      Comments:
> >   [ ](gearpump) Todd Lipcon
> >      Comments:
> >   [ ](gearpump) Xuefu Zhang
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Griffin
> >
> > Griffin is a open source Data Quality solution for distributed data
> systems
> > at
> > any scale in both streaming or batch data context
> >
> > Griffin has been incubating since 2016-12-05.
> >
> > 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?
> >
> >
> >
> > How has the community developed since the last report?
> >
> >
> >
> > How has the project developed since the last report?
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [ ](griffin) Kasper Sørensen
> >      Comments:
> >   [ ](griffin) Uma Maheswara Rao Gangumalla
> >      Comments:
> >   [ ](griffin) Luciano Resende
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >   - Reminder sent.
> >
> > --------------------
> > Hivemall
> >
> > Hivemall is a library for machine learning implemented as Hive
> > UDFs/UDAFs/UDTFs.
> >
> > Hivemall has been incubating since 2016-09-13.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Create the first Apache release
> >   2. Community growth (committers and users)
> >   3. Documentation improvements
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   Help would be required for IP clearance (being ready)
> >
> > How has the community developed since the last report?
> >
> >   * Merged contributions from two external contributors.
> >   * Mailing list activity (Jan-Feb): @dev: 78 messages
> >
> https://lists.apache.org/trends.html?dev@hivemall.apache.org:2017-01
> >
> https://lists.apache.org/trends.html?dev@hivemall.apache.org:2017-02
> >       - The number of messages decreased in Feb because we changed
> >         JIRA/github notification addresses to issues@hivemall.apache.org
> >   * Github watchers/stars are gradually increasing:
> >      52 stars as of Feb 28 (was 38 on Dec 26)
> >      https://github.com/apache/incubator-hivemall
> >   * Twitter account @ApacheHivemall followers are gradually increasing:
> >      52 followers as of Feb 28 (was 33 on Dec 26)
> >   * Submitted a talk to Apache BigData, Miami.
> >
> > How has the project developed since the last report?
> >
> >   Worked hard towards the first Apache release.
> >
> >   * Documentation enrichment (e.g., Hivemall on Apache Spark)
> >      http://hivemall.incubator.apache.org/userguide/
> >
> >   Since the last report (January 2017), we have
> >     * Opened 40 JIRA issues
> >     * Closed 13 JIRA issues
> >        as seen in bit.ly/hivemall-jira-may
> >     * Created 36 Pull Requests
> >
> > https://github.com/apache/incubator-hivemall/pulls?q=is%
> > 3Apr%20created%3A2017-01-01..2017-02-28
> >     * Merged 33 Pull Requests
> >
> > https://github.com/apache/incubator-hivemall/pulls?q=is%
> > 3Apr%20closed%3A2017-01-01..2017-02-28
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [x] Working towards first release
> >   [x] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   No release yet
> >   (planning the first Apache release in Q1 ~ Early Q2, 2017)
> >
> > When were the last committers or PPMC members elected?
> >
> >   None
> >
> > Signed-off-by:
> >
> >   [ ](hivemall) Reynold Xin
> >      Comments:
> >   [X](hivemall) Markus Weimer
> >      Comments:
> >   [ ](hivemall) Xiangrui Meng
> >      Comments:
> >   [X](hivemall) Daniel Dai
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > HTrace
> >
> > HTrace is a tracing framework intended for use with distributed systems
> > written in java.
> >
> > HTrace has been incubating since 2014-11-11.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Continue to grow the Apache HTrace community
> >   2. Continue to explore projects integrating Apache HTrace
> >   3. Continue to develop and release stable Apache HTrace incubating
> > artifacts
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   There are no issues requiring board attention at this time.
> >
> > How has the community developed since the last report?
> >
> >   Mailing lists have been quiet.
> >
> > How has the project developed since the last report?
> >
> >   Development has been quiet.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [x] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-10-06
> >
> > When were the last committers or PPMC members elected?
> >
> >   2016-10-03
> >
> > Signed-off-by:
> >
> >   [ ](htrace) Jake Farrell
> >      Comments:
> >   [ ](htrace) Todd Lipcon
> >      Comments:
> >   [ ](htrace) Lewis John Mcgibbney
> >      Comments:
> >   [ ](htrace) Andrew Purtell
> >      Comments:
> >   [x](htrace) Billie Rinaldi
> >      Comments:
> >   [x](htrace) Michael Stack
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > log4cxx2
> >
> > Logging for C++. N.B. This is a reboot of the Log4cxx podling which
> > previously
> > graduated.
> >
> > log4cxx2 has been incubating since 2013-12-09.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Create a release
> >   2. Activate some community
> >   3.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   There is an ongoing discussion since first quarter 2016 about how to
> deal
> >   with this project, because no release happened yet and there's only
> > little
> >   activity regarding development and support. Especially no release is a
> >   problem for incubating projects.
> >
> > How has the community developed since the last report?
> >
> >   One support question, no new project members.
> >
> > How has the project developed since the last report?
> >
> >   Robert Middleton finished his attempt to move the project to use C++
> >   smart pointers instead of the former used custom implementation. That
> >   work needs to be tested and integrated upstream, but there's no time
> plan
> >   currently on when this will be done.
> >
> > How would you assess the podling's maturity?
> >
> >   It seems this project has run its course in the incubator. The Logging
> > PMC
> >   needs to decide what to do with the project.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [X] Other: pretty much dormant
> >
> > Date of last release:
> >
> >   2008-04-03 was the last official, pre-incubation 0.10.0
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [X](log4cxx2) Ralph Goers
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Mnemonic
> >
> > Apache Mnemonic is an advanced hybrid memory storage oriented library,
> > we've proposed a non-volatile/durable Java object model and durable
> > computing service that bring many advantages to significantly improve
> > the performance of massive real-time data
> > processing/analytics. developers are able to use this library to design
> > their cache-less, SerDe-less and native-direct computing high
> > performance applications.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Apache releases: we have release version 0.4.0-incubating
> >   2. Integrated with Hadoop as Mapreduce Input/Output formatters.
> >   3. Introduced Mnemonic to potential developers and users.
> >
> > 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?
> >
> >   Our last report was in Dec. Since then
> >
> >   * Two more developers are going to contribute code.
> >   * We need to encourage more discussion on the dev list in the coming
> > months
> >
> > How has the project developed since the last report?
> >
> >   * Upgraded MemChunkHolder/MemBufferHolder to DurableChunk/DurableHolder
> >   * Provided mnemonic-hadoop-mapreduce module with testcases
> >   * and other bugfixes, features, improvements
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [*] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-01-24
> >
> > When were the last committers or PMC members elected?
> >
> >   None
> >
> > Signed-off-by:
> >
> >   [X](mnemonic) Patrick Hunt
> >      Comments:
> >
> >         One year milestone as podling this month. Community growth has
> been
> >         slow and activity dominated by one to two committers. Not clear
> how
> >         active the mentors are in helping the podling - only two mentors
> >         signed off on the report last quarter.
> >
> >   [X](mnemonic) Andrew Purtell
> >      Comments:
> >
> >         Mentors have not been active, including myself. We may want to
> >         solicit new or additional mentors for this podling.
> >
> >   [ ](mnemonic) James Taylor
> >      Comments:
> >   [ ](mnemonic) Henry Saputra
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > MRQL
> >
> > MRQL is a query processing and optimization system for large-scale,
> > distributed data analysis, built on top of Apache Hadoop, Hama, Spark,
> > Flink, and Storm.
> >
> > MRQL has been incubating since 2013-03-13.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Increase the number of active committers
> >   2. Increase adoption, expand user community, and increase user list
> > activity
> >
> > 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?
> >
> >   One new MRQL committer was accepted since our last report.  He
> developed
> >   the new evaluation mode for MRQL that runs on top of Apache Storm.
> >
> > How has the project developed since the last report?
> >
> >   There was very little activity on JIRA since our last report.  The
> >   resolved issues on JIRA included various bug fixes and performance
> >   improvements.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-03-02
> >
> > When were the last committers or PPMC members elected?
> >
> >   2016-12-22
> >
> > Signed-off-by:
> >
> >   [ ](mrql) Alan Cabrera
> >      Comments:
> >   [ ](mrql) Edward J. Yoon
> >      Comments:
> >   [ ](mrql) Mohammad Nour El-Din
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > MXNet
> >
> > A Flexible and Efficient Library for Deep Learning
> >
> > MXNet has been incubating since 2017-01-23.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Move the code and website to Apache Infrastructure.
> >   2. Establish a formal release process and schedule, allowing for
> > dependable release cycles in line with Apache development process.
> >   3.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >  PPMC to discuss adding in some community members who asked to join while
> > the Incubator vote was in progress.
> >
> > How has the community developed since the last report?
> >
> >  Project is still getting set up in Incubator.
> >
> > How has the project developed since the last report?
> >
> >  Project is still getting set up, all proposed committers have submitted
> > their ICLAs.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [X] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >  No Release yet
> >
> > When were the last committers or PPMC members elected?
> >
> >   Project is being set up with the initial set of committers.
> >
> > Signed-off-by:
> >
> >   [X](mxnet) Sebastian Schelter
> >      Comments:
> >   [X](mxnet) Suneel Marthi
> >      Comments:
> >   [X](mxnet) Markus Weimer
> >      Comments:
> >   [X](mxnet) Henri Yandell
> >      Comments: As project already exists in the public, this incubation
> is
> > about moving the development over without stopping the momentum of the
> > project, and then learning about the Apache development processes.
> Previous
> > conversations were Slack/GitHub-issue based, so making decisions on the
> > email list will be the first likely adaptation. A dependency on ZeroMQ
> will
> > be the primary discussion point for a first release at Apache.  PPMC list
> > is still low on subscriptions, with less than half of the PPMC members
> > subscribed.
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > Myriad
> >
> > Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos
> together
> > on
> > the same cluster and allows dynamic resource allocations across both
> Hadoop
> > and other applications running on the same physical data center
> > infrastructure.
> >
> > Myriad has been incubating since 2015-03-01.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Nurture dwindling developer community
> >   2. Expand Myriad user base, get feedback from production deployments
> >   3. Release new versions (0.3 in progress) with new features
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   Participation is dropping, as developers are busy with other projects.
> > When should we consider retiring from the incubator?
> >
> > How has the community developed since the last report?
> >
> >   * dev@ mailing list had 41 messages since the last report. 1 new
> user, 4
> > continuing users, 3 committers
> >   * Bi-weekly dev syncs with 0-2 participants. Most cancelled due to lack
> > of attendance. Minutes at http://s.apache.org/8kF
> >
> > How has the project developed since the last report?
> >
> >   * 1 PR and 1 JIRA closed.
> >   * PRs #95, #96 and #100 are iterating. We can do a 0.3 release after
> they
> > merge.
> >   * DC/OS Universe PR is in review, needs a walkthrough doc:
> > https://github.com/mesosphere/universe/pull/841
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-06-20 myriad-0.2.0-incubating
> >
> > When were the last committers or PPMC members elected?
> >
> >   2016-06-16 Yuliya Feldman
> >
> > Signed-off-by:
> >
> >   [ ](myriad) Benjamin Hindman
> >      Comments:
> >   [ ](myriad) Danese Cooper
> >      Comments:
> >   [ ](myriad) Ted Dunning
> >      Comments:
> >   [ ](myriad) Luciano Resende
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > 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. Get companies backing up the project as part of a commercial story,
> to
> >      get a long-term momentum
> >   2. Do recurrent releases - some semi-automation would be helpful - for
> > the
> >      3rd party users
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   We have a lack of active mentors. Sam Ruby resigned due to switch of
> >   personal focus.  Mentors have not signed the past two reports, not
> > answering
> >   on direct mail. Overworked?
> >
> >   A general issue of the project is that it 'just' a toolkit of an office
> >   file format, which in addition is far from leading on the business
> > market,
> >   so likely never being used by the mass market - a very niche product.
> >
> >   Still the toolkit seems to be working well for most common use cases,
> but
> >   is repeatedly updated by developers on changes of the ODF, like Red Hat
> >   developers enhancing the ODF validator as part of LibreOffice
> regression
> >   tests (e.g. out-of-the-box running on
> http://odf-validator.rhcloud.com/)
> >   most often quite ahead of one of the international ODF Plugfests -
> >   http://odfplugfest.org/2016-paris/programme/.
> >
> >   Since there are still some game changing features in the pipeline (e.g.
> >   collaboration) which are expected to strengthen the acceptance and
> > develop
> >   the community but on the other hand the mentorship / infrastructure of
> > the
> >   project could be better, a decision needs to be made on the future.
> >
> > How has the community developed since the last report?
> >
> >   A company stated their commitment to the ODF toolkit and works on
> >   contribution to the project.
> >
> >   We are working on the next release including the fixes and planning a
> >   follow-up release adding new features.
> >
> > How has the project developed since the last report?
> >   Problem with Windows build bots were solved.
> >
> >   Build tested with JDK 6 to 8 under Windows and Linux with JDK 8.
> >
> >   Preparing a release after a long time to allow newcomers to rely on
> >   state-of-the-art features.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [x] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2013-06-22, just started one
> >
> > When were the last committers or PPMC members elected?
> >
> >   2015-10-05 - Damjan Jovanovic for Commiter/PPMC
> >
> > Signed-off-by:
> >
> >   [ ](odftoolkit) Rob Weir
> >      Comments:
> >   [ ](odftoolkit) Nick Burch
> >      Comments:
> >   [ ](odftoolkit) Yegor Kozlov
> >      Comments:
> >
> > IPMC/Shepherd notes
> >
> >
> > --------------------
> > Omid
> >
> > Omid is a flexible, reliable, high performant and scalable ACID
> > transactional
> > framework that allows client applications to execute transactions on top
> of
> > MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
> > Snapshot Isolation guarantees on the accessed data.
> >
> > Omid has been incubating since 2016-03-28.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Boost project dissemination in the Apache community.
> >   2. Collaborate/integrate Omid with other Apache projects.
> >   3. Get positive feedback from other projects currently
> >      integrating/using Omid.
> >
> > 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?
> >
> >   Started integration with Apache Phoenix community.
> >   Omid presented in the SF HBase community event in Dec.
> >   Omid paper accepted in FAST 2017
> >
> > How has the project developed since the last report?
> >
> >   Started working in the next release.
> >   Quarter Stats (from: 2016-12-01 to: 2017-02-28):
> >
> >     +---------------------------------------------+
> >     |   Metric                          | counts  |
> >     +---------------------------------------------+
> >     | # of msgs in dev list             |   36    |
> >     | Active Contributors (incl mentors)|    6    |
> >     | Jira New Issues                   |    4    |
> >     | Resolved Issues                   |    2    |
> >     | Pull Requests merged              |    0    |
> >     | Pull Requests proposed            |    0    |
> >     +---------------------------------------------+
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-06-24
> >
> > When were the last committers or PPMC members elected?
> >
> >   At incubation acceptance (2016-03-28)
> >
> > Signed-off-by:
> >
> >   [X](omid) Alan Gates
> >      Comments: Activity on this podling remains low but it is good to
> see a
> > few issues files and resolved and the report filed on time and without
> > prodding by the mentors.
> >   [ ](omid) Lars Hofhansl
> >      Comments:
> >   [ ](omid) Flavio P. Junqueira
> >      Comments:
> >   [ ](omid) Thejas Nair
> >      Comments:
> >   [ ](omid) James Taylor
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > OpenWhisk
> >
> > OpenWhisk is an open source, distributed Serverless computing platform
> able
> > to execute application logic (Actions) in response to events (Triggers)
> > from
> > external sources (Feeds) or HTTP requests governed by conditional logic
> > (Rules). It provides a programming environment supported by a REST
> > API-based
> > Command Line Interface (CLI) along with tooling to support packaging and
> > catalog services.
> >
> > OpenWhisk has been incubating since 2016-11-23.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Moving github repos under the Apache Github Org (organization move,
> >      repository renames), first 2 repos. moved; issues identified and
> being
> > worked.
> >  2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
> >      update openwhisk.org to be Apache compliant (pre-req is repo. move
> > completion
> >      so that we can generate site via Jenkins/Apache tooling)
> >  3. Working through project incubation checklists on CWIKI
> >       Compliance Checklist for OpenWhisk.org website
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   - Travis CI takes hours to process a PR on Apache Org; whereas it takes
> > minutes under current
> >     OpenWhisk org.
> >         - The root cause is that Apache has 185 repos enable with Travis
> > [1], but only an allocation of
> >           30 concurrent builds. OpenWhisk typically needs 5 concurrent
> > build slots by itself continually.
> >   - Many of the OpenWhisk’s repos. have cross-build dependencies
> (primarily
> > for Travis CI tests)
> >     this may will cause issues as repos. are brought over 1 at a time if
> > forwarding links are not
> >     preserved by GitHub.
> >   - There may be issues with Committers in China being able
> >     to enable 2FA since it does not work with their cell phones and the
> >     alternative encryption tool seems to be blocked. Investigating with
> >     infra.
> >
> > How has the community developed since the last report?
> >
> >   - Committers have begun enable 2FA for GitHub and enable cross-
> >     authentication to their Apache accounts using GitBox.
> >   - “dev", “private” email list traffic continues to be healthy; positive
> >     discussion of a few new code feature/change topics
> >   - GitHub project “Stars” = 1144 (up from 1024 last month).
> >    - a few new contributors in package deployment tool repo.
> >    - more active discussions occurring on “dev” list.
> >   - Created new public Slack Team (openwhisk-team.slack.com). includes
> > channels:
> >     - “general” for general project questions and help
> >     - “dev” channel where notifications of all OpenWhisk GitHub Issues
> are
> > posted.
> >     - “dev-pr” channel where notifications of all OpenWhisk GitHub Pull
> > Requests are posted.
> >     = Note: all development related discussions are directed to our “dev”
> > mailing list.
> >
> > How has the project developed since the last report?
> >
> >   - Updating existing project code scan tools used in Travis CI to check
> > for ASF
> >     license header in files.
> >   - Confluence WIKI (
> > https://cwiki.apache.org/confluence/display/OPENWHISK/
> > OpenWhisk+Project+Wiki
> > )
> >     added pages for:
> >     - Accessing Apache GitHub as a Committer
> >     - GitHub How to Submit Pull Requests
> >     - Developer Best Practices
> >   - Active discussion on:
> >        - Configuration through environment vs. Consul KV
> >        - vanity urls for web actions
> >        - Exposing garbage collector for nodejs runtime
> >   - New features: webactions, official support for annotations
> >   - New repo.: https://github.com/openwhisk/openwhisk-GitHubSlackBot
> >         - This bot is designed to post updates to Slack when a GitHub
> pull
> > request is ready to merge
> >            or a list of pull requests are under review for certain days
> and
> > haven't merged.
> >   - Submissions to “dev” list for new articles, use cases (new contribs.)
> >   - New features: webactions, official support for annotations
> >   - Multiple sessions submitted for ApacheCon NA. In addition, submitted
> > for panel
> >     talk and lightning talks.
> >
> > Date of last release:
> >
> >   - No release yet
> >
> > When were the last committers or PPMC members elected?
> >
> >   - Ioana Baldini, new committer 2017-02-09
> >   - Justin Berstler, new committer 2017-02-20
> >
> > Signed-off-by:
> >
> >   [ ](openwhisk) Felix Meschberger
> >      Comments:
> >   [ ](openwhisk) Isabel Drost-Fromm
> >      Comments:
> >   [X](openwhisk) Sergio Fernández
> >      Comments: Podling still struggling with landing on ASF
> infrastructure,
> > although slowly making progress.
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Pirk
> >
> > Pirk is a framework for scalable Private Information Retrieval (PIR).
> >
> > Pirk has been incubating since 2016-06-17.
> >
> > Three most important issues to address in the move towards graduation:
> >
> > 1. Grow the community to establish diversity of background and expertise.
> > 2. Establish a formal release process and schedule, allowing for
> dependable
> > release cycles in a
> >    manner consistent with the Apache development process.
> > 3. Add to and improve the Pirk user documentation and examples both on
> the
> >    website and in the codebase
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >  Yes. The Pirk community participation and growth has stalled over the
> last
> > few months.
> >  Recently, there's been discussion on the mailing lists about retiring
> Pirk
> > for now.
> >
> >
> > How has the community developed since the last report?
> >
> >  The Pirk community has not developed since the last report - no new
> > contributors or
> >  committers have been added
> >
> > How has the project developed since the last report?
> >
> >  The project has stalled - the existing community has not been active nor
> > has the community grown.
> >
> > How would you assess the podling's maturity?
> >
> >  The podling will not be seeing any activity in the near future, and the
> > consensus has been to retire
> >  the podling for now.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [X] Other:
> >
> > Date of last release:
> >
> >   October 9, 2016
> >
> > When were the last committers or PPMC members elected?
> >
> >  Pirk elected two new committers (Tim Ellison and Suneel Marthi, both
> >  mentors) on August 18, 2016.
> >
> > Signed-off-by:
> >
> >   [x](pirk) Billie Rinaldi
> >      Comments:
> >   [x](pirk) Joe Witt
> >      Comments: As noted in the report and observed in the community
> > contributions and discussion have
> >      stalled. Discussions to prompt engagement have revealed that
> > availability to contribute for much
> >      of the original team is no longer available.  It is my opinion that
> > retirement should be pursued
> >      given the range of community growth for the past few months and
> stated
> > lack of intent to turn
> >      that around soon.
> >   [x](pirk) Josh Elser
> >      Comments: It's sad to see the discussion about the low recent
> activity
> > quickly change into a
> >      a discussion about retirement. I was hoping that the previously
> active
> > podling members would have
> >      taken some steps to grow, but it seems like their priorities have
> > shifted elsewhere. Pirk
> >      had been doing quite well and is very interesting software; it's a
> > shame to see it moving to retirement.
> >      Sounds like retirement will be pursued in the coming month.
> >   [X](pirk) Suneel Marthi
> >      Comments: Based on recent discussions on Mailing lists the consensus
> > has been to retire Pirk for now,
> >  in large part due to unavailability of the full set of initial
> committers
> > that can steer this project forward.
> >   [X](pirk) Tim Ellison
> >      Comments: Pirk had a very promising start, with the community
> > exhibiting all the right behaviors,
> >  including being able to gain consensus on an early initial release.  The
> > initial committers are critical to the
> >  future of Pirk due to their specialist knowledge, and there has not been
> > sufficient time to fully grow
> >  new members who can cover their role.  With their withdrawl it is
> > unfortunate but inevitable that Pirk
> >  be retired.  The discussion is taking place on the dev list as expected.
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > Pony Mail
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that
> > can be integrated with many email platforms.
> >
> > Pony Mail has been incubating since 2016-05-27.
> >
> > 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?
> >
> >
> >
> > How has the community developed since the last report?
> >
> >
> >
> > How has the project developed since the last report?
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [ ](ponymail) Andrew Bayer
> >      Comments:
> >   [ ](ponymail) John D. Ament
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >   - Reminder sent.
> >
> > --------------------
> > Quickstep
> >
> > Quickstep is a high-performance database engine that is designed to
> exploit
> > the full potential of hardware that is packed in modern servers. The
> > initial effort targets single-node in-memory environments.
> >
> > Quickstep has been incubating since 2016-03-29.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Building a Quickstep community.
> >   2. More adoption of the Quickstep technology.
> >   3. No releases so far.
> >
> > 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?
> >
> > Members of the community have become more aware about the release
> process.
> > The details about the release process that we plan to use are well
> > documented so that future releases will be smooth and more frequent.
> >
> > How has the project developed since the last report?
> >
> > We are working on our first release. Since the last report, we have done
> > the following:
> > * We have made several changes to the code base. Some highlights are:
> > Cleaning up the third party library code as per the Apache hygiene,
> improve
> > the code performance by adding several novel features.
> > * Preparation for release: Created scripts and step by step procedural
> > documentation for how to
> > make a Quickstep release.
> > * Scripts have been added to the main repo while documentation is on
> > confluence.
> > * We went through several release candidates.
> > * During this period, we identified some usability issues on our
> supported
> > platforms and fixed them.
> >
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [X] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> > November 2016.
> >
> >
> > Signed-off-by:
> >
> >   [ ](quickstep) Konstantin Boudnik
> >      Comments:
> >   [x](quickstep) Julian Hyde
> >      Comments: Lots of effort going into the first release - it's taken a
> >        while, but it's very welcome! The community is getting better at
> >        having discussions on the list (and not just about code). Have not
> >        seen many potential new committers so far, but the release should
> >        change that, and the project is starting to become more outward
> >        looking.
> >   [x](quickstep) Roman Shaposhnik
> >      Comments: good progress
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Ratis
> >
> > Ratis is a java implementation for RAFT consensus protocol.
> >
> > Ratis has been incubating since 2017-01-03.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Setup wiki, jenkins
> >   2. Make the first release.
> >   3. Grow the 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?
> >    - One new contributor
> >
> >
> > How has the project developed since the last report?
> >    - IP Clearance is completed (
> > https://incubator.apache.org/ip-clearance/ratis.html)
> >    - Active development started in the community. 16 commits in last
> month.
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup - Ip clearance, Git setup completed and development
> > started. Next step is to get jenkins going.
> >   [ ] Working towards first release - Working towards first snapshot
> > release. Need INFRA help for access.
> >   [ ] Community building - One new contributor
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   - None
> >
> > When were the last committers or PPMC members elected?
> >
> >   - Initial set of committers / PPMC.
> >
> > Signed-off-by:
> >
> >   [ ](ratis) Chris Nauroth
> >      Comments:
> >   [ ](ratis) Devaraj Das
> >      Comments:
> >   [ ](ratis) Jakob Homan
> >      Comments:
> >   [ ](ratis) Uma Maheswara Rao G
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > RocketMQ
> >
> > RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to
> > use
> > message-oriented middleware, especially for processing large amounts of
> > streaming data.
> >
> > RocketMQ has been incubating since 2016-11-21.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Confirm the IP review is complete. – COMPLETE
> >   2. Make our first Apache release and vote in our first committer / PMC
> >      members. –  COMPLETE
> >   3. Grow the 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?
> >
> >   * Increased mailing list activity: solutions and milestone plan are
> >     discussed and decided in mailing list.
> >   * More than 15+ new contributors from different organizations since
> >     podling.
> >   * Organized 1 hackathon in community, the attendees was more than 50+.
> > The
> >     mainly contributors have subscribe our dev mailing list and begin to
> be
> >     familiar to Apache way.
> >   * Star has increased to 516 from 0 since move repository from alibaba
> to
> >     apache.
> >   * Voted upon and invited 2 new committers in PPMC since entering
> podling.
> >
> > How has the project developed since the last report?
> >
> >   * The first release of RocketMQ as part of the Apache incubator on
> >     2017-2-22.
> >   * Since November 111 issues+ have been reported on JIRA site and 50
> have
> >     been resolved or closed. The plus are all association with the future
> >     release version. Since November 70+ pull requests have been created
> and
> >     44+ pull requests have been closed. The 3 guys review mechanism was
> to
> >     be applied, we highly value the quality of the Apache project.
> >   * Created Travis CI, Sonar and Coveralls, project infrastructure for
> >     RocketMQ. Apply JIRA agile and kanban for RocketMQ committers.
> >   * Created the website: http://rocketmq.incubator.apache.org and some
> >     necessary document have been created such as user guide, developer
> >     guide, faq, etc.
> >   * There are more than 5+ Apache project integration are decided to be
> > done
> >     in the future release, such as ignite, storm etc.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup - The initial setup went pretty well with assistance
> >       from John Ament and his Incubator documentation improvement
> efforts.
> >   [ ] Working towards first release - The podling has performed its first
> >       release as noted below
> >   [ ] Community building - Some contributors are beginning to
> participate.
> >       So far users have been slow to show up, so more effort on this
> front
> >       will be encouraged.
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-02-21
> >
> > When were the last committers or PPMC members elected?
> >
> >   27 Feb 2017 - Roman Shtykh
> >   27 Feb 2017 - Zhen Dong Liu
> >
> > Signed-off-by:
> >
> >   [X](rocketmq) Bruce Snyder
> >      Comments:
> >   [ ](rocketmq) Brian McCallister
> >      Comments:
> >   [ ](rocketmq) Willem Ning Jiang
> >      Comments:
> >   [ ](rocketmq) Luke Han
> >      Comments:
> >   [ ](rocketmq) Justin McLean
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > 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 Flink, Apache
> > Storm, Apache Apex and Apache Samza.
> >
> > SAMOA has been incubating since 2014-12-15.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Grow the developer base
> >   2. Grow the user base
> >   3. Add some more ML techniques
> >
> > 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?
> >
> >   Mailing list activity (December 2016 - February 2017):
> >   * @dev: 24 messages
> >
> >   Jira issues backlog (December 2016 - February 2017):
> >   * Created:  2
> >   * Resolved: 0
> >
> >   - We are organizing an internal workshop on SAMOA at Telefonica
> >     I+D with researchers of Orange Labs
> >
> >   - We had a presentation of Apache Samoa at Paris Machine Learning
> >     Meetup and Hamburg Machine Learning Meetup
> >
> >   - Bhupesh Chawda has presented Apache SAMOA in different venues
> >     with his presentation "Machine Learning Support in Apache Apex
> >     (Next Gen Hadoop) with Apache SAMOA"
> >
> >   - We invited edi_bice who made several contributions last
> >     spring to become a committer.
> >
> >   - We published a scientific paper using Apache Samoa and one of
> >     its machine learning techniques (Vertical Hoeffding Tree)
> >     presented in IEEE BigData Conference last December 2016.
> >
> >   - We submitted a paper on SAMOA to a post-proceedings book of the
> >     workshops MUSE/MSM 2015/2016 in the Springer LNCS/LNAI series.
> >
> > How has the project developed since the last report?
> >
> >   - We are looking into new ML techniques for development.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-09-30
> >
> > When were the last committers or PMC members elected?
> >
> >   None
> >
> > Signed-off-by:
> >
> >   [X](samoa) Alan Gates
> >      Comments: Activity on this podling remains low.  It is good to see a
> > new committer being elected.  Shouldn't that be noted in the final
> section
> > on when new committers and PMC members were elected?
> >   [ ](samoa) Ashutosh Chauhan
> >      Comments:
> >   [ ](samoa) Enis Soztutar
> >      Comments:
> >   [ ](samoa) Ted Dunning
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Singa
> >
> > Singa is a distributed deep learning platform.
> >
> > Singa has been incubating since 2015-03-17.
> >
> > Three most important issues to address in the move towards graduation:
> >  1. Improve distributed training in SINGA V1.2
> >  2. Improve the documentation and add more examples
> >  3. Attract more contributors
> >
> > 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?
> >
> >   There were  66, 60, and 43 emails from dev@ list in December 2016,
> > January 2017 and February 2017 respectively.
> >   There are 67 new commits since the last report.
> >   One new committer (Li Boon Tan) was added.
> >
> >  How has the project developed since the last report?
> >
> >  We released the V1.1 version after the last report.  The following
> > features were added after last report
> >     + Ease the installation process via Docker images, debian packages,
> > conda packages and Amazon AMI  (CPU version)
> >     + Integrate with Jenkins for automatically generating convenient
> > packages and updating the website.
> >     + Improve the model classes: adding debug mode, adding the Concat and
> > Slice layers, and supporting model loading and saving via the Snapshot
> API
> >     + Add image_tool.py for image augmentation and rafiki sub-package for
> > providing RESTFul APIs.
> >     + Enable Java binding (basic) for SINGA
> >     + Add examples pre-trained from Caffe, e.g., GoogleNet, and examples
> > pre-trained from torch, e.g. ResNet
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >    [ ] Initial setup
> >    [ ] Working towards first release
> >    [X] Community building
> >    [ ] Nearing graduation
> >    [ ] Other:
> >
> >
> > Date of last release:
> >
> >   2017-02-12
> >
> > When were the last committers or PMC members elected?
> >
> >   2017-02-26
> >
> >
> >
> > Signed-off-by:
> >
> >     [ ](singa) Daniel Dai
> >       Comments:
> >     [X](singa) Alan Gates
> >       Comments: On the maturity assessment I would say the community is
> in
> > the "Community building" phase but not far from the "Nearing graduation"
> > phase.
> >     [ ](singa) Ted Dunning
> >       Comments:
> >     [ ](singa) Thejas Nair
> >       Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> > --------------------
> > 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?
> >
> >
> >
> > How has the community developed since the last report?
> >
> >
> >
> > How has the project developed since the last report?
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [ ](sirona) Henri Gomez
> >      Comments:
> >   [ ](sirona) Jean-Baptiste Onofre
> >      Comments:
> >   [ ](sirona) Tammo van Lessen
> >      Comments:
> >   [ ](sirona) Mark Struberg
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Spot
> >
> > Apache Spot is a solution stack that provides the capability to ingest IT
> > related telemetry (network flows, domain name service information and
> proxy
> > server logs) and provide unsupervised machine learning capabilities to
> > identify suspicious activity.  The information is organized and presented
> > using operational analytics so that a security analyst can investigate
> the
> > most suspicious connections. Apache Spot is built on an open data model
> > using Apache Spark and Apache Hadoop.
> >
> > Spot has been incubating since 2016-09-23.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1.  Move infrastructure and development to ASF (code, issues, mailing
> > list, ...)
> >   2.  Build diverse community
> >   3.  Demonstrate ability to create releases
> >
> > 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?
> > Based on initial feedback, process for issues was updated on the project
> > website, with primary objective to facilitate the workflow and
> interaction
> > with Community, and having diverse ownership of them until resolution.
> > Slack channel has become very popular, however in order to adhere to ASF
> > official communications channels, those conversations that involve quick
> > question will be kept there, any extended discussion on code, pipeline,
> and
> > architecture, are being ported to Dev mail list.
> > There has been a concern to get continuous improvement of the UI on
> Apache
> > Spot, committers have been working on process to get UX interviews that
> > help to understand and address community and compliance needs.
> >
> > How has the project developed since the last report?
> > The project got a major architecture change in order to remove CSV’s,
> > offload storage from the OS file system and instead leverage HDFS (for
> > distributed architecture).
> > Per community request through JIRA issue, and in order to facilitate the
> > installation/adoption of the project for scale deployments, an
> installation
> > script consolidating the ones that were built per pipeline component has
> > been pulled to repository, it will reduce the complexity of porting files
> > and configuration variables, by having a central point of deployment.
> > Open Data Models, which serves as a framework for data sources
> > normalization, initially for ingestion, was ported through its
> > Specification to the project repository, this will bring more
> contributions
> > to facilitate the design of the NoSQL table, and then determine
> technology
> > selection through discussion and voting through mailing list.
> > February Metrics:
> >     +---------------------------------------------+
> >     |   Metric                          | counts  |
> >     +---------------------------------------------+
> >     | Active Contributors (incl mentors)|    14   |
> >     | Jira New Issues                   |    6    |
> >     | Resolved Issues                   |    1    |
> >     | Pull Requests merged              |    3    |
> >     | Pull Requests proposed            |    3    |
> >     +---------------------------------------------+
> >
> >
> > Date of last release:
> > N/A
> >
> > When were the last committers or PMC members elected?
> > Last committer was elected on 2/24
> >
> > How does the podling rate their own maturity?
> > There was a strong focus on code delivery over the last quarter, towards
> > Apache release, community adoption keeps growing, now by adding a layer
> of
> > process for opening issues and commits, plus interaction over channels
> > we're bringing contributions from others, towards Apache release.
> >
> > Signed-off-by:
> >
> >   [x](spot) Jarek Jarcec Cecho
> >      Comments:
> >   [ ](spot) Brock Noland
> >      Comments:
> >   [ ](spot) Andrei Savu
> >      Comments:
> >   [x](spot) Uma Maheswara Rao G
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Streams
> >
> > Apache Streams is a lightweight server for ActivityStreams.
> >
> > Streams has been incubating since 2012-11-20.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Community growth and PMC maturity.
> >  2. Demonstrate a consistent release schedule.
> >  3. Participation of project community within related standards-bodies
> >     and Apache projects.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >  The podling has satisfied all of the requirements as laid down in the
> > Apache
> >  Maturity Model and is ready to graduate to TLP.
> >
> >  The Apache Maturity Model Assessment for Streams can be found at:
> >
> >
> https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+
> > Assessment+for+Streams
> >
> >
> > How has the community developed since the last report?
> >
> >   Dev List
> >   60 emails sent by 14 people, divided into 27 topics.
> >
> >   Web Page
> >   844 Sessions, 631 Users, 2183 Pageviews.
> >
> > How has the project developed since the last report?
> >
> >   Source Control
> >   https://github.com/apache/incubator-streams
> >
> >   Excluding merges, 5 authors have pushed 46 commits to master. On
> master,
> > 446 files have changed and there
> >   have been 22,388 additions and 13,129 deletions.
> >
> >   https://github.com/apache/incubator-streams-examples
> >
> >   Excluding merges, 2 authors have pushed 29 commits to master and 2
> >   commits to all branches. On master, 79 files have changed and there
> >   have been 2655 additions and 2458 deletions.
> >
> >   Team presently has a 0.5-incubating release candidate out for PPMC
> voting
> > and
> >   will be pushing the same for IPMC vote the week of March 5, 2017.
> >
> >   Since September 2016, the project has had 4 releases and has been
> having
> > consistent activity.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [X] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-12-26
> >
> > When were the last committers or PPMC members elected?
> >
> >   2016-10-27: Joey Frazee elected as committer / PPMC member
> >   2016-09-28: Suneel Marthi elected as mentor / PPMC member
> >
> > Signed-off-by:
> >
> >   [X](streams) Matt Franklin
> >      Comments: The podling has a small, but invested community from
> > multiple different companies.  I agree with Suneel that we should
> >                consider graduation.
> >   [X](streams) Ate Douma
> >      Comments: Getting close to termination a little over 6 months ago
> > because of lack of activity, the podling has remarkably revived
> >                and revitalized itself, and IMO now is in good shape,
> ready
> > to graduate.
> >   [X](streams) Suneel Marthi
> >      Comments: This podling is ready to graduate and has fulfilled all
> the
> > criteria as laid down in the Apache Maturity Model Assessment.
> >                The discussion to graduate the podling can start off once
> > the in progress Streams 0.5-incubating release is through.
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Taverna
> >
> > Taverna is a domain-independent suite of tools used to design and execute
> > data-driven workflows.
> >
> > Taverna has been incubating since 2014-10-20.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Project maturity evaluation
> >   2. IP/Licence Review
> >   3. Graduate!
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   Reviewing licences and IP with a view to graduation.
> >
> >
> > https://cwiki.apache.org/confluence/display/TAVERNADEV/
> > 2016-09+License+review
> >
> > How has the community developed since the last report?
> >
> >   List has gone a bit more quiet, while activity on the
> >   Gitter chat https://gitter.im/apache/taverna
> >   has remained at same level. Need to re-focus use of
> >   mailing list and community development.
> >
> > How has the project developed since the last report?
> >
> >   Preparing maturity report, almost ready for graduation vote.
> >   Taverna has a lot of different code bases and we are reviewing
> >   what code we should remove from the repo while leaving a core set
> >   of modules for graduation.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [x] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-07-01 taverna-engine-3.1.0-incubating
> >   2016-07-01 taverna-common-activities-2.1.0-incubating
> >   2016-07-01 taverna-commandline-3.1.0-incubating
> >
> > When were the last committers or PPMC members elected?
> >
> >   2016-10-20 Committer
> >   2015-12-09 PPMC member
> >
> > Signed-off-by:
> >
> >   [x](taverna) Andy Seaborne
> >      Comments:
> >
> >         Taverna dev@ has been quiet for this reporting period. The
> podling
> >         is trying to establish which parts of the total software grant to
> >         take through the incubator process into a TLP. There are still
> > parts
> >         that have not been released or at a minimum checked for IP.
> >
> >         The active PPMC membership is low and it would be better to work
> on
> >         community growth to provide a stable PMC as a TLP.
> >
> >   [ ](taverna) Daniel J Debrunner
> >      Comments:
> >   [ ](taverna) Marlon Pierce
> >      Comments:
> >   [x](taverna) Stian Soiland-Reyes
> >      Comments:
> >         Activity has stalled a bit in the drive towards graduation, as
> some
> >         (perhaps tedious) IP review remains. Ambition levels might need
> >         adjustment, e.g. don't include all repositories in graduation to
> >         TLP.
> >
> >   [ ](taverna) Suresh Marru
> >      Comments:
> >   [ ](taverna) Suresh Srinivas
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Tephra
> >
> > Tephra is a system for providing globally consistent transactions on top
> of
> > Apache HBase and other storage engines.
> >
> > Tephra has been incubating since 2016-03-07.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Regular releases
> >   2. Improve community engagement
> >   3. Increase adoption
> >
> > 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?
> >
> >   - 1 new subscriber in dev mailing list since the last report
> >   - 25 new JIRAs filed since the last report
> >   - 0 external contributors submitted patches since the last report
> >   - 1 external contributor created a ticket in JIRA since the last report
> >
> > How has the project developed since the last report?
> >
> >   - Working on 0.11.0-incubating release
> >   - Released 0.10.0-incubating
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [x] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of the last release:
> >
> >     2016-12-16
> >
> > When were the last committers or PMC members elected?
> >
> >   - None since coming to incubation
> >
> > Signed-off-by:
> >
> >   [X](tephra) Alan Gates
> >      Comments:
> >   [X](tephra) Andrew Purtell
> >      Comments:
> >   [ ](tephra) James Taylor
> >      Comments:
> >   [ ](tephra) Lars Hofhansl
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Trafodion
> >
> > Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
> > operational workloads on Hadoop.
> >
> > Trafodion has been incubating since 2015-05-24.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Develop community and bring in more diverse contributors.
> >   2. Continue the momentum and become more integrated with the
> >      rest of the Apache community.
> >   3. Continue to create software releases.
> >
> > 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?
> >
> >   * Participation in public lists has declined slightly:
> >     503 messages in the codereview forum, 560@commits,
> >     246@dev, 871@issues and 26@user.
> >   * 217 people are following @trafodion on Twitter.
> >   * We are working towards our next release, 2.1.
> >   * Gunnar Tapper stepped down as the Release Manager on Feb. 5th
> >     and Sandhya Sundaresan volunteered on Feb. 9th to take over
> >     that role.
> >   * The community continues to be active in China, with
> >     some communications happening outside the Apache dev lists.
> >   * We had discussions about our readiness to graduate. Many
> >     people feel that we are ready, others felt that we should
> >     get more diverse contributors first.
> >
> > How has the project developed since the last report?
> >
> >   * 173 commits from 21 contributors.
> >   * 127 JIRAs filed and 112 resolved Dec 1 - Feb 27.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2016-07-07 2.0.1
> >
> > When were the last committers or PPMC members elected?
> >
> >   in August 2016
> >
> > Signed-off-by:
> >
> >   [ ](trafodion) Devaraj Das
> >      Comments:
> >   [ ](trafodion) Enis Söztutar
> >      Comments:
> >   [ ](trafodion) Michael Stack
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Wave
> >
> > A wave is a hosted, live, concurrent data structure for rich
> communication.
> > It
> > can be used like email, chat, or a document.
> >
> > Wave has been incubating since 2010-12-04.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Growing community
> >   2. Improving code base
> >
> > 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?
> >
> >   Pablo Ojanguren has accepted invitation to become committer.
> >   Community is discussing whether it have reached
> >   a sufficient level of stability to consider graduation.
> >
> > How has the project developed since the last report?
> >
> >   IP clearance got from SwellRT former copyright owners.
> >   In process to plan a release.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   March 2016
> >
> > When were the last committers or PPMC members elected?
> >
> >  December 2016
> >
> > Signed-off-by:
> >
> >   [x](wave) Upayavira
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >
> >
> > --------------------
> > Weex
> >
> > Weex is a framework for building Mobile cross-platform high performance
> UI.
> >
> > Weex has been incubating since 2016-11-30.
> >
> > 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?
> >
> >
> >
> > How has the community developed since the last report?
> >
> >
> >
> > How has the project developed since the last report?
> >
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [ ] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   XXXX-XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> >
> >
> > Signed-off-by:
> >
> >   [ ](weex) Luke Han
> >      Comments:
> >   [ ](weex) Willem Jiang
> >      Comments:
> >   [ ](weex) Stephan Ewen
> >      Comments:
> >   [ ](weex) Niclas Hedhman
> >      Comments:
> >
> > IPMC/Shepherd notes:
> >
> >   - Reminder sent.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message