Yes, the version on the wiki is the final version. I just updated it a little as I noticed I missed correcting the committers/PMC note at the end.
As far as posting on the incubator wiki, I have no idea. Is that where the final version must reside and if so, am I allowed to push it there or do I need one of the mentors to do so? If I can do it, let me know and I will push it there asap. --Tom On Tue, Dec 12, 2017 at 4:32 AM, John D. Ament <[email protected]> wrote: > So, I'm a bit confused as far as next steps. > > Is the report posted at > https://cwiki.apache.org/confluence/display/ARIATOSCA/ > Podling+Report+2017-DEC-12 > the > report we are saying should be submitted for the podling? And are you > looking for me to post it on the incubator wiki? > > John > > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron <[email protected]> wrote: > > > There actually was some in-person conversation between committers about > the > > report. But it's a good criticism -- we should make it explicitly open > and > > via the mailing list. > > > > On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau <[email protected]> > > wrote: > > > > > > > > > > > > On Dec 11, 2017, at 9:36 AM, John D. Ament <[email protected]> > > > wrote: > > > > > > > > The typical steps a podling would take: > > > > > > > > - Post a report on a common ground (e.g. email, confluence, or other) > > > > - Let others know where it is > > > > - Discuss it and get others to contribute into it > > > > - When the report comes through, post it on the incubator wiki, e.g. > > > > https://wiki.apache.org/incubator/December2017 (link changes each > > month) > > > > > > > > The report generally looks fine, but I would change it so that only > > "[X] > > > > Community building" is checked. My current comment from the wiki > still > > > > holds "Activity on list is picking up over the slack conversations. > A > > > > community member is planning to write a report, however it indicates > a > > > > corporate hierarchy issue within the project that needs to get > solved." > > > > > > > > Basically what that second sentence means is that we shouldn't be > > reliant > > > > on one person to do the report. > > > > > > Trust me, I am fully willing to share in the “fun” for the next > > > report. *) > > > > > > —Tom > > > > > > > > > > > > > > John > > > > > > > > On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <[email protected] > > > > > wrote: > > > > > > > >> > > > >> > > > >> The AriaTosca report was submitted last Thursday (at least > made > > > >> available) and is available here: > > > >> > > > >> > > > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/ > > > Podling+Report+2017-DEC-12 > > > >> < > > > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/ > > > Podling+Report+2017-DEC-12 > > > >>> > > > >> > > > >> I was not made aware of any special process for submitting > this > > > >> other than letting everyone know on the > > > >> mailer that it was being created and where it was in case folks > wanted > > > to > > > >> comment. If there is anything > > > >> else needed for this let me know. > > > >> > > > >> —Tom > > > >> > > > >> > > > >>> On Dec 10, 2017, at 9:36 AM, John D. Ament <[email protected]> > > > >> wrote: > > > >>> > > > >>> All, > > > >>> > > > >>> Below is the current draft of our report. As of now, we have 5 > > reports > > > >>> missing and 4 reports not signed off on. I hope we can get that > > > resolved > > > >>> in the next few days. I have copied those podlings impacted. > > > >>> > > > >>> Incubator PMC report for December 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 53 podlings incubating. In the month of > > November, > > > we > > > >>> executed six releases, added one IPMC member and received the > > > resignation > > > >>> of another (which is in flight until their sole podling retires). > We > > > >> added > > > >>> two podlings to our roster, have a few more in the pipeline and > have > > > one > > > >>> podling planning to graduate this month. > > > >>> > > > >>> * Community > > > >>> > > > >>> New IPMC members: > > > >>> > > > >>> - Michael Semb Wever > > > >>> > > > >>> People who left the IPMC: > > > >>> > > > >>> - Upayavira (not processed in LDAP yet) > > > >>> > > > >>> * New Podlings > > > >>> > > > >>> - Crail > > > >>> - Service Comb > > > >>> > > > >>> * Podlings that failed to report, expected next month > > > >>> > > > >>> - Amaterasu - Activity stopped late November > > > >>> - Aria Tosca > > > >>> - HTrace - 0 on list activity > > > >>> - Pony Mail - Low activity, suspect just missed. > > > >>> - Wave - Retiring > > > >>> > > > >>> * Podlings Missing sign off > > > >>> > > > >>> - Griffin > > > >>> - Myriad > > > >>> - OpenWhisk > > > >>> - Spot > > > >>> > > > >>> * Graduations > > > >>> > > > >>> The board has motions for the following: > > > >>> > > > >>> - Trafodion > > > >>> - Your podling here? > > > >>> - Your podling here? > > > >>> > > > >>> * Releases > > > >>> > > > >>> The following releases entered distribution during the month of > > > >>> November: > > > >>> > > > >>> - 2017-11-01 Apache Freemarker 2.3.27 > > > >>> - 2017-11-08 Apache Netbeans HTML4J 1.5 > > > >>> - 2017-11-15 Apache Mnemonic 0.10.0 > > > >>> - 2017-11-15 Apache MXNet 0.12.1 > > > >>> - 2017-11-18 Apache Netbeans HTML4J 1.5.1 > > > >>> - 2017-11-28 Apache Griffin 0.1.6 > > > >>> > > > >>> * IP Clearance > > > >>> > > > >>> > > > >>> > > > >>> * Legal / Trademarks > > > >>> > > > >>> > > > >>> > > > >>> * Infrastructure > > > >>> > > > >>> > > > >>> > > > >>> * Miscellaneous > > > >>> > > > >>> > > > >>> > > > >>> * Credits > > > >>> > > > >>> > > ---------------------------------------------------------------------- > > > >>> Table of Contents > > > >>> Amaterasu > > > >>> AriaTosca > > > >>> Crail > > > >>> Daffodil > > > >>> Gearpump > > > >>> Griffin > > > >>> Hivemall > > > >>> HTrace > > > >>> Myriad > > > >>> Omid > > > >>> OpenWhisk > > > >>> PageSpeed > > > >>> Pony Mail > > > >>> Pulsar > > > >>> Quickstep > > > >>> SAMOA > > > >>> SDAP > > > >>> SINGA > > > >>> Spot > > > >>> Superset > > > >>> Taverna > > > >>> Tephra > > > >>> Trafodion > > > >>> Wave > > > >>> > > > >>> > > ---------------------------------------------------------------------- > > > >>> > > > >>> -------------------- > > > >>> Amaterasu > > > >>> > > > >>> Apache Amaterasu is a framework providing continuous deployment for > > Big > > > >> Data > > > >>> pipelines. > > > >>> > > > >>> Amaterasu has been incubating since 2017-09-07. > > > >>> > > > >>> 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: > > > >>> > > > >>> [ ](amaterasu) Jean-Baptiste Onofré > > > >>> Comments: > > > >>> [ ](amaterasu) Olivier Lamy > > > >>> Comments: > > > >>> [ ](amaterasu) Davor Bonaci > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> johndament: > > > >>> The podling was moving OK until the end of November, not sure if > > it's > > > >> a > > > >>> holiday lull. > > > >>> > > > >>> -------------------- > > > >>> 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. > > > >>> 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: > > > >>> > > > >>> [ ](ariatosca) Suneel Marthi > > > >>> Comments: > > > >>> [ ](ariatosca) John D. Ament > > > >>> Comments: Activity on list is picking up over the slack > > > >>> conversations. A community member is planning to write a report, > > > however > > > >>> it indicates a corporate hierarchy issue within the project that > > needs > > > to > > > >>> get solved. > > > >>> [ ](ariatosca) Jakob Homan > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> > > > >>> > > > >>> ----------------------- > > > >>> Crail > > > >>> > > > >>> Crail is a storage platform for sharing performance critical > > > >>> data in distributed data processing jobs at very high speed. > > > >>> > > > >>> Crail has been incubating since 2017-11-01. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Finish project setup > > > >>> 2. Community building > > > >>> 3. Create a first release > > > >>> > > > >>> 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? > > > >>> > > > >>> N/A > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> * This is the first report. > > > >>> * Apache ICLA signed by all contributors from IBM Zurich Research. > > > >>> * Software Grant and Corporate Contributor License Agreement > > > >>> signed by IBM ZUrich Research representative. > > > >>> * Infrastructure setup underway (missing JIRA due to > > > >>> infrastructure issues) > > > >>> * Available Crail code to be transferred soon. > > > >>> > > > >>> 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: > > > >>> > > > >>> N/A > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> 2017-11-01 (entering incubation) > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X] (crail) Julian Hyde > > > >>> Comments: > > > >>> Project is still boot-strapping. No activity on dev > > > >>> list yet (except for preparation of this report). > > > >>> [ ] (crail) Luciano Resende > > > >>> Comments: > > > >>> [ ] (crail) Raphael Bircher > > > >>> Comments: > > > >>> > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> -------------------- > > > >>> Daffodil > > > >>> > > > >>> Apache Daffodil is an implementation of the Data Format Description > > > >>> Language (DFDL) used to convert between fixed format data and > > XML/JSON. > > > >>> > > > >>> Daffodil has been incubating since 2017-08-27. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Obtain remaining SGA from NCSA > > > >>> 2. First release as an Apache Incubator > > > >>> 3. Broadening base of contributors and building 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? > > > >>> > > > >>> - No additional committers or community growth, however activity on > > the > > > >>> dev@daffodil list has increased, with multiple design discussions, > > > >>> code reviews, and project discussions taking place. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> - All tickets from the old JIRA system were successfully > transferred > > to > > > >>> ASF JIRA > > > >>> - IBM has submitted their SGA. We are now only waiting on an SGA > from > > > >>> NCSA, who we believe is very close to submission. Once that is in, > we > > > >>> believe all necessary SGA's and CLA's will have been submitted and > we > > > >>> can begin the process of relicensing the Daffodil codebase to > Apache > > > >>> v2 and switching the package namespace to org.apache.daffodil > > > >>> - Development pace has increased, with multiple issues, commits, > and > > > >>> pull requests having gone through the new Daffodil Code Contributor > > > >>> Workflow > > > >>> - Continuous integration has been enabled via TravisCI GitHub > > > >>> Integration > > > >>> - Migrated repository to GitBox > > > >>> - A website has been developed based on the Apache Incubator > Website > > > >>> template. Still need to enable automatic building/publishing-- > > > >>> manually publishing for now. > > > >>> > > > >>> 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: > > > >>> > > > >>> - None > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> - None, same as project incubator inception > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](daffodil) John D. Ament > > > >>> Comments: Solid on list communication. Waiting on SGAs to be > > > >>> processed to relicense the code. Podling executed a non-ASF > release > > in > > > >> the > > > >>> interim. > > > >>> [X](daffodil) David Fisher > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> > > > >>> > > > >>> -------------------- > > > >>> 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. Have frequent release cycles. > > > >>> 2. Continue to evolve community interest and support. > > > >>> 3. Keep up with Apache Beam's evolving API. > > > >>> > > > >>> - 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? > > > >>> There was a company managed to deploy Gearpump on their secured > > Hadoop > > > >>> cluster. They reported some bugs occurred in their environment and > > > >>> contributed the fixes back to Gearpump community. > > > >>> > > > >>> - How has the project developed since the last report? > > > >>> 15 issues created and 9 issues resolved. > > > >>> An official Gearpump docker image was published. > > > >>> Continuous improvements for Gearpump Runner in Apache Beam were > made. > > > >>> > > > >>> Date of last release: > > > >>> 2017-07-17 > > > >>> > > > >>> > > > >>> When were the last committers or PMC members elected? > > > >>> No new committers or PMC members elected yet. > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](gearpump) Jean-Baptiste Onofré > > > >>> Comments: > > > >>> [ ](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. Continuous enhancing to provide better accuracy and profing data > > > >>> quality dimensions. > > > >>> 2. Release more dq dimensions like timeliness and completeness > based > > on > > > >>> feedbacks from community. > > > >>> 3. Onboard more user cases and grow the community. > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> > > > >>> - Apache Griffin 0.1.6-incubating released. > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> - Four new contributors on-board, some more users had contacted us > > for > > > >>> use cases. > > > >>> - Discussed and Voting to on-board some committers. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> - Active development is moving on well, 67 commits in last three > > > months. > > > >>> - Profiling measure for streaming mode has been developed. > > > >>> - Scheduler has been optimized, support flexible job scheduling. > > > >>> - UI module for profiling measure has been developed. > > > >>> - Work toward for next version to support enhanced scheduler end to > > > end, > > > >>> and support more data quality dimensions. > > > >>> > > > >>> 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-11-07 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> - Initial set of committers / PPMC. > > > >>> - Discussed and Voting to on-board some committers. > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](griffin) Kasper Sørensen > > > >>> Comments: > > > >>> [ ](griffin) Uma Maheswara Rao Gangumalla > > > >>> Comments: > > > >>> [ ](griffin) Luciano Resende > > > >>> Comments: > > > >>> [ ](griffin) Henry Saputra > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> Interesting project. Seems to be going well. No concerns. Dave > > Fisher. > > > >>> > > > >>> > > > >>> -------------------- > > > >>> 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? > > > >>> > > > >>> None > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> * Got contributions from new external contributors > > > >>> https://github.com/apache/incubator-hivemall/pull/116 > > > >>> * Github watchers/stars are gradually increasing: > > > >>> 108 stars as of Dec 6 (was 99 on Sept 6) > > > >>> * Twitter account @ApacheHivemall followers are gradually > increasing: > > > >>> 101 followers as of Dec 6 (was 87 on Sept 6) > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> * Approaching the first Apache release while the released delayed > > > >>> from Q3 to Q4. > > > >>> - Blocking issues are decreased > > > >>> https://issues.apache.org/jira/browse/HIVEMALL-21 > > > >>> - Remaining tasks are just updating Maven release scheme and > > > documents > > > >>> https://issues.apache.org/jira/browse/INFRA-15465 > > > >>> > > > >>> Since the last report, we have > > > >>> * In the last 3 months, we opened 19 JIRA issues and closed 16 > JIRA > > > >>> issues > > > >>> as seen in https://goo.gl/QFQEF5 (as of Dec 1) > > > >>> Created Resolved > > > >>> Sept 2017 3 8 > > > >>> Oct 2017 12 5 > > > >>> Nov 2017 4 3 > > > >>> * Created 14 Pull Requests and merged 21 Pull Requests between > June > > 01 > > > >>> and Aug 31. > > > >>> > > > >>> > > > >> https://github.com/apache/incubator-hivemall/pulls?q=is% > > > 3Apr%20created%3A2017-09-01..2017-11-30 > > > >>> > > > >>> > > > >> https://github.com/apache/incubator-hivemall/pulls?q=is% > > > 3Apr%20closed%3A2017-09-01..2017-11-30 > > > >>> > > > >>> 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 Q4, 2017) > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> * Oct 10: Invited Kento Nozawa as a committer > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](hivemall) Reynold Xin > > > >>> Comments: > > > >>> [X](hivemall) Markus Weimer > > > >>> Comments: > > > >>> [ ](hivemall) Xiangrui Meng > > > >>> Comments: > > > >>> [ ](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. > > > >>> 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: > > > >>> > > > >>> [ ](htrace) Jake Farrell > > > >>> Comments: > > > >>> [ ](htrace) Todd Lipcon > > > >>> Comments: > > > >>> [ ](htrace) Lewis John Mcgibbney > > > >>> Comments: > > > >>> [ ](htrace) Andrew Purtell > > > >>> Comments: > > > >>> [ ](htrace) Billie Rinaldi > > > >>> Comments: > > > >>> [ ](htrace) Michael Stack > > > >>> Comments: > > > >>> > > > >>> 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. Work on refactoring the existing code-base to take advantage of > > the > > > >>> advances > > > >>> made in the containerized orchestration space. > > > >>> 2. Make it easier for committers to get their changes reviewed and > > > >> merged. > > > >>> 3. Come up with a roadmap of features for upcoming releases and > work > > > >>> towards release 0.3 > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> Couple of committers have volunteered to drive the project forward > by > > > >>> contributing > > > >>> new features to make the project more relevant to the fast-changing > > > >>> ecosystem, vet > > > >>> releases, while improving the engagement with community. > > > >>> > > > >>> How has the community developed since the last report? > > > >>> The dev@ mailing had a discussion around retirement. No consensus. > > > >>> > > > >>> > > > >>> How has the project developed since the last report? > > > >>> There were two proposals on the mailing list about refactoring the > > > >> project > > > >>> to take > > > >>> advantage of the advances in the containerized orchestration space. > > > >>> > > > >>> Two of the committers also got together and discussed the initial > > > >> re-factor > > > >>> proposal. > > > >>> One of the committers is going to send out a write about the > refactor > > > >> plan > > > >>> to the > > > >>> dev@ mailing list for review with other committers. > > > >>> > > > >>> How would you assess the podling's maturity? > > > >>> Please feel free to add your own commentary. > > > >>> > > > >>> [x] Initial setup > > > >>> [x] 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: > > > >>> > > > >>> > > > >>> > > > >>> -------------------- > > > >>> 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 in Apache. > > > >>> > > > >>> 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? > > > >>> > > > >>> Continue integration with Apache Phoenix > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> Critical fixes on security and HBase 0.x & 1.x integration. > > > >>> HBase 0.x version being tested in prod environment at Yahoo. > > > >>> Started testing HBase version 1.x in local environments. > > > >>> > > > >>> Quarter Stats (from: 2017-09-01 to: 2017-11-30): > > > >>> > > > >>> > > > >>> +---------------------------------------------+ > > > >>> | Metric | counts | > > > >>> +---------------------------------------------+ > > > >>> | # of msgs in dev list | 53 | > > > >>> | Active Contributors (incl mentors)| 8 | > > > >>> | Jira New Issues | 5 | > > > >>> | Resolved Issues | 1 | > > > >>> | Pull Requests merged | 1 | > > > >>> | Pull Requests proposed | 2 | > > > >>> +---------------------------------------------+ > > > >>> > > > >>> 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? > > > >>> > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](omid) Alan Gates > > > >>> Comments: > > > >>> [ ](omid) Lars Hofhansl > > > >>> Comments: > > > >>> [ ](omid) Flavio P. Junqueira > > > >>> Comments: > > > >>> [ ](omid) Thejas Nair > > > >>> Comments: > > > >>> [x](omid) James Taylor > > > >>> Comments: > > > >>> > > > >>> -------------------- > > > >>> 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. Additionally, it now provides > > options > > > to > > > >>> host the platform components as Docker containers on various > > Container > > > >>> Frameworks such as Mesos, Kunernetes, and Compose. > > > >>> > > > >>> > > > >>> OpenWhisk has been incubating since 2016-11-23. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Est. release process for ZIP of source code > > > >>> 2. Increase additional company and individual Contributors to > > > maintain > > > >>> all project repos. > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > > be > > > >>> aware of? > > > >>> > > > >>> - It had been our intent to have Apache infra. to host our > staging > > > >> (and > > > >>> move it out of disparate private builds within various companies). > > > >> However, > > > >>> INFRA indicates they only typically allocate 1 VM per project for > use > > > >> with > > > >>> demos and minor things. They indicate that perhaps a corporate > > > donation > > > >> is > > > >>> in order (ala. Spark). > > > >>> - Goal: standup testing resources at Apache and utilize for > > > public > > > >>> CI and performance testing of OpenWhisk on Kubernetes > > > >>> - Needed resources: > > > >>> Minimum 5 worker node kubernetes cluster. Each worker > > nodes > > > >>> can be fairly modest (2-4 virtual cores; 4-8GB of memory) > > > >>> - Formal hand-off of OpenWhisk trademark/logo from IBM needs to > be > > > >>> executed; need to identify process for this. > > > >>> Discussion started w/ Apache legal via "legal-discuss" > mailing > > > >> list > > > >>> with subject "Trademark handoff for "OpenWhisk" name and logo". > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> - incubator-openwhisk Github stars: 2181 (+253 since last report) > > > >>> - incubator-openwhisk GitHub forks: 469 (+52 since last report) > > > >>> - dev mailing list activity continues to be active > > > >>> - The bi-weekly Zoom "Technical Interchange" continues to be > well > > > >>> received and attended. > > > >>> - Complete videos posted to OW YouTube channel and detailed > notes > > > to > > > >>> our CWIKI. > > > >>> - YouTube Channel: Apache Meetings Playlist: > > > >>> > > > >> https://www.youtube.com/watch?v=n4l9L8wyQlk&list=PLxVTI8yc_ > > > iX4qqr_45gduBFQxhSTfJ68g > > > >>> - CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting > > > >> Notes: > > > >>> > > > >> https://cwiki.apache.org/confluence/display/OPENWHISK/ > > > OpenWhisk+Technical+Interchange+Meeting+Notes > > > >>> > > > >>> New Contributors of note (not comprehensive): > > > >>> - Brendan McAddams: Red Hat: Akka expert working on creating > > separate > > > >>> Akka dispatchers for CouchDB and Kafka Clients > > > >>> - Kavitha Vallari Devara: Samsung FaaS team in "Open Service Lab > of > > > >>> Convergence Team (SW R&D Center): incubator-openwhisk organizing > > > project > > > >>> directory structure. > > > >>> - Gabriel Nicolas Avellaneda: independent. CLI contributions > > > >>> - Manjiri Tapaswi: N. Caroline State Univ. (NCSU): Fixed all > "good > > > >>> first issues" for "incubator-wskdeploy" > > > >>> - Stig Bakken, Zedge (mobile phone customization), first review > of > > PR > > > >>> in Kube repo. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> OpenWhisk general developments: > > > >>> - Reorg. of "core" openwhisk directories to better match > architecture > > > >>> - Removal of openwhisk cli and cli related test cases > > > >>> - Community agreed to Scala formatting guidelines; re-enforced via > > > github > > > >>> pre-commit hooks > > > >>> - Focus on improved per-invocation (of Actions) performance via > > logging > > > >>> and other improvements. > > > >>> - Changed default logging backend from log4j to Logback > > > >>> - Redis is now optional on deployment > > > >>> - Support for metrics streaming (via plug-in, default Kamon). > > > >>> - Continued focus in HA/Clustering enablement while continuing to > > > reduce > > > >>> reliance on Ansible for configuration. Work included: > > > >>> - Enabling Controller HA support (defaults to active cluster of > 2). > > > >>> - Enabling CouchDB clustering > > > >>> - Using ZooKeeper as persistent store for InvokerId assignment > > > >>> - Adaptive timeouts for controller and nginx > > > >>> - Programmatic lazy creation of completedN and invokerN topics > > > >>> - Certificate checking for secure mode > > > >>> - Now generating maven snapshot artifacts for some sub-projects > > > >>> - Kubernetes deployment improvements: > > > >>> - Moved Travis testing to using Minikube & more current Kubernetes > > > >> version > > > >>> (1.7.4) > > > >>> - Significant progress on supporting deploy of complete OpenWhisk > > > system > > > >>> on Kubernetes, eliminating custom containers, and streamlining > deploy > > > >>> process > > > >>> - Separation of Language runtimes into their own top-level repos. > > > >>> including: docker (SDK) runtime, pythin, nodejs, java, php, swift > > > >>> - Updates to Akka and focus on improving messaging > > > >>> - Updates to improve API Gateway resiliency > > > >>> - Nginx performance improved > > > >>> - NodeJS 6 upgraded to 6.11.4 > > > >>> - NodeJS 8 support > > > >>> - Swift 3.1.1 now default, deprecated Swift 3 > > > >>> > > > >>> openwhisk-package-deploy: > > > >>> - New repo created with proper license, docs, tests, and Travis CI > > > >>> - New action wskdeploy allows to deploy wskdeploy git repos > > > >>> - New "managed" sync support > > > >>> > > > >>> openwhisk-packages-cloudant/couchdb: > > > >>> - Update to feed action to update trigger config (dbName) > > > >>> - Update to feed action to return config and status > > > >>> > > > >>> openwhisk-packages-kafka: > > > >>> - New ability for feed action to return config and status > > > >>> - Update to feed action to update trigger config (topic) > > > >>> > > > >>> openwhisk-packages-alarms: > > > >>> - New ability for feed action to return config and status > > > >>> - New alarm trigger type interval > > > >>> - New alarm trigger type fire once > > > >>> - New StartDate and stopDate parameters for cron > > > >>> > > > >>> openwhisk-cli: > > > >>> - New canonical source after duplication removal from main repo > > > >>> - New open issues moved from main repo to CLI repo > > > >>> - New trigger feed lifecycles on `trigger get` and `trigger update` > > > >>> > > > >>> Significant. discussions (dev list): > > > >>> - Warm containers > > > >>> - Are Java actions first class citizens? > > > >>> - Git commit (accreditation) > > > >>> - Moving out runtime images and tests > > > >>> - Enablement of controller clustering > > > >>> - Invoker activation queueing proposal > > > >>> - proposal to remove trigger activations when no rules are matched > > > >>> - [Scala] code style guideline > > > >>> - NodeJS 8 support > > > >>> - Use an explicit property to define type of Whisk entity > > > >>> > > > >>> 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: > > > >>> > > > >>> Comments: > > > >>> > > > >>> Need greater variety of contributors and contributing companies > > > >>> > > > >>> Date of last release: > > > >>> > > > >>> N/A > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> None during this period > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](openwhisk) Felix Meschberger > > > >>> Comments: > > > >>> [ ](openwhisk) Isabel Drost-Fromm > > > >>> Comments: > > > >>> [ ](openwhisk) Sergio Fernández > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> -------------------- > > > >>> PageSpeed > > > >>> > > > >>> PageSpeed represents a series of open source technologies to help > > make > > > >> the > > > >>> web > > > >>> faster by rewriting web pages to reduce latency and bandwidth. > > > >>> > > > >>> PageSpeed has been incubating since 2017-09-30. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Finish project setup > > > >>> 2. Community building > > > >>> 3. Create a first release > > > >>> > > > >>> 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? > > > >>> > > > >>> - A new potential committer indicated interest in joining the > > PageSpeed > > > >>> initiative > > > >>> by maintaining the FreeBSD port he contributed and updating it to > the > > > >>> latest, and > > > >>> upstreaming required changes to support the new platform to make > > future > > > >>> updates > > > >>> easier. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> - Some technical hurdles were encountered while trying to run the > RAT > > > >> tools > > > >>> on > > > >>> the codebase. The plan is to pick this up again after the initial > > code > > > >> drop > > > >>> has been > > > >>> performed to the ASF repo. > > > >>> - We are working on getting the source code into the ASF > repository. > > > >>> - Progress was made on new features and getting the module > > distributed > > > >> more > > > >>> widely. > > > >>> > > > >>> How would you assess the podling's maturity? > > > >>> Please feel free to add your own commentary. > > > >>> > > > >>> [X] Initial setup > > > >>> [X] Working towards first release > > > >>> [X] Community building > > > >>> [ ] Nearing graduation > > > >>> [ ] Other: > > > >>> > > > >>> Date of last release: > > > >>> N/A > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> 2017-09-30 (entering incubation) > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](pagespeed) Jukka Zitting > > > >>> Comments: > > > >>> [X](pagespeed) Leif Hedstrom > > > >>> Comments: > > > >>> [ ](pagespeed) Nick Kew > > > >>> Comments: > > > >>> [ ](pagespeed) Phil Sorber > > > >>> Comments: > > > >>> > > > >>> > > > >>> 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: > > > >>> > > > >>> > > > >>> > > > >>> -------------------- > > > >>> Pulsar > > > >>> > > > >>> Pulsar is a highly scalable, low latency messaging platform running > > on > > > >>> commodity hardware. It provides simple pub-sub semantics over > topics, > > > >>> guaranteed at-least-once delivery of messages, automatic cursor > > > >> management > > > >>> for > > > >>> subscribers, and cross-datacenter replication. > > > >>> > > > >>> Pulsar has been incubating since 2017-06-01. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Grow the community with new Committers/PPMC members. > > > >>> 2. Set up a test cluster to be able to run system tests > > > >>> 3. Improve release process by having more committers taking part in > > > >>> 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? > > > >>> > > > >>> The community added 5 contributors. There is a healthy discuss on > > > issues > > > >>> related > > > >>> to development, tools and processes among the community members. > > > >>> There has been a good number of questions asked by users on the > Slack > > > >>> channel > > > >>> where there are around 33 weekly active users. > > > >>> > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> 18 authors have pushed 150 commits to master in the last 3 months. > > > >>> > > > >>> The project has made the its second release in the Apache Incubator > > on > > > >>> October 13th. > > > >>> The next release (1.21-incubating) is being voted right now in the > > dev > > > >>> mailing list. > > > >>> Several design documents with improvement proposals have been > > submitted > > > >> to > > > >>> the > > > >>> wiki and discussed in the mailing list. > > > >>> > > > >>> > > > >>> 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-10-13, 1.20.0-incubating > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> None > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](pulsar) Dave Fisher > > > >>> Comments: Seems like the podling is engaging new contributors > > mostly > > > >>> through slack channel. > > > >>> We will need to make sure that enough information is > > > >>> archived by either discussion on dev@ or > > > >>> in some other way. They are on their fourth RC in the > > > >>> current release and are doing things correctly. > > > >>> [ ](pulsar) Jim Jagielski > > > >>> Comments: > > > >>> [ ](pulsar) P. Taylor Goetz > > > >>> Comments: > > > >>> [ ](pulsar) Francis Liu > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> > > > >>> > > > >>> -------------------- > > > >>> Quickstep > > > >>> > > > >>> Quickstep is a high-performance database engine. > > > >>> > > > >>> Quickstep has been incubating since 2016-03-29. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Work on adoption of the Quickstep technology. > > > >>> 2. Continue building a developer community. > > > >>> 3. Work towards a second release. > > > >>> > > > >>> 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? > > > >>> > > > >>> There are a number of active developers working with the code base, > > > >>> who may become committers in the near future. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> A number of bug reports have been filed and features added to move > > > >>> the single-node version of the system forward. The newer features > > > >>> added to the system are accompanied by a JIRA issue. There is more > > > >>> activity on the dev mailing list, and the newer members of the > > > >>> community are involved in the discussions. > > > >>> > > > >>> 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-03-25 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> 2017-10-03 Robert Claus (committer) > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](quickstep) Konstantin Boudnik > > > >>> Comments: > > > >>> [x](quickstep) Julian Hyde > > > >>> Comments: > > > >>> Community building is this project's biggest challenge. > > > >>> Robert Claus is, I believe, the first committer outside > > > >>> of the UW team, so his appointment is good progress. > > > >>> [ ](quickstep) Roman Shaposhnik > > > >>> 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 Storm, Apache Flink, and Apache Samza. > > > >>> > > > >>> SAMOA has been incubating since 2014-12-15. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Elect new PPMC members > > > >>> 2. Enlarge the community > > > >>> 3. > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> > > > >>> None > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> > > > >>> Mailing list activity (September 2017 - November 2017): > > > >>> * @dev: 49 messages > > > >>> > > > >>> Jira issues backlog (September 2017 - November 2017): > > > >>> * Created: 5 > > > >>> * Resolved: 1 > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> * Planning a new release in the next month. > > > >>> > > > >>> * Presentation at the Flink Forward Conference from Orange's team > > > >>> > > > >>> * Integration of a new Boosting algorithm > > > >>> > > > >>> * Improved Apache Kafka support and support for JSON and Avro. > > > >>> > > > >>> * Improved SAMOA instances. > > > >>> > > > >>> 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 PPMC members elected? > > > >>> > > > >>> None > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](samoa) Alan Gates > > > >>> Comments: In response to shepherd's comments (see below) > community > > > >>> started a vote on a couple of contributors becoming committers. > > > >>> [ ](samoa) Ashutosh Chauhan > > > >>> Comments: > > > >>> [ ](samoa) Enis Soztutar > > > >>> Comments: > > > >>> [ ](samoa) Ted Dunning > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> Concerned about the lack of community growth. Very few commits this > > > year > > > >>> yet there are pull requests by contributors. > > > >>> Sent an email to private@samoa > > > >>> > > > >>> > > > >>> -------------------- > > > >>> SDAP > > > >>> > > > >>> SDAP is an integrated data analytic center for Big Science > problems. > > > >>> > > > >>> SDAP has been incubating since 2017-10-22. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> > > > >>> 1. Grow community > > > >>> 2. Make formal SDAP (Incubating) releases > > > >>> 3. Evangelize SDAP as an integrated data analytic center for Big > > > Science > > > >>> problems > > > >>> > > > >>> 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 have not formally reported before. We hope the community > > > >>> to grow once we make our first Incubating release. > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> All infrastructure and codebase(s) have successfully been > > > >>> transitioned over to the ASF. We are working to comply > > > >>> with branding, trademarks and source code. This work is ongoing. > > > >>> > > > >>> How would you assess the podling's maturity? > > > >>> Please feel free to add your own commentary. > > > >>> > > > >>> [X] 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? > > > >>> > > > >>> No new committers or PPMC have been added other than the > > > >>> original SDAP committers. > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](sdap) Jörn Rottmann > > > >>> Comments: > > > >>> [ ](sdap) Raphael Bircher > > > >>> Comments: > > > >>> [ ](sdap) Suneel Marthi > > > >>> Comments: > > > >>> [X](sdap) Lewis John McGibbney > > > >>> Comments: SDAP is doing pretty well. Branding, > > > >>> trademarks and source code compliance are the > > > >>> primary issues right now. Once these are addressed > > > >>> SDAP can focus on the first Incubating release. > > > >>> > > > >>> 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. Finish the existing jira tickets, especially the Keras API and > > > >>> Open Neural Network Exchange format. > > > >>> 2. Prepare the graduation documents and start discussion in dev@ > > list. > > > >>> > > > >>> > > > >>> 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? > > > >>> > > > >>> 1 new developer (Wengtong Li) contributed to the repository. > > > >>> 1 new committer (Moaz) joined officially. > > > >>> > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> > > > >>> 1. We fixed several bugs related to Tensor operations and > > unit-testing. > > > >>> 2. Some new issues/features are created, mainly abut supporting > > > including > > > >>> Keras API and Open Neural Network Exchange format. > > > >>> > > > >>> > > > >>> How would you assess the podling's maturity? > > > >>> > > > >>> We are discussing the graduation process and want to > > > >>> start it with one more release. > > > >>> > > > >>> > > > >>> [ ] Initial setup > > > >>> [ ] Working towards first release > > > >>> [ ] Community building > > > >>> [ ] Nearing graduation > > > >>> [ ] Other: > > > >>> > > > >>> Date of last release: > > > >>> > > > >>> 2017-06-29 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> 2017-09-01 > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](singa) Daniel Dai > > > >>> Comments: > > > >>> [X](singa) Alan Gates > > > >>> Comments: > > > >>> [ ](singa) Ted Dunning > > > >>> Comments: > > > >>> [ ](singa) Thejas Nair > > > >>> 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 DNS, 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 and 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. Build diverse community > > > >>> 2. Continue building a strong and diverse body of PPMC members for > > long > > > >>> term project continuity > > > >>> 3. Demonstrate ability to create releases > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> > > > >>> * Based on React being re-licensed under the MIT license and > > remaining > > > >>> compatible with Apache licensed projects, we have not moved forward > > on > > > >>> replacing our use of the React framework at this time. > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> * We have passed a vote on implementing an ingest re-architecture. > > > >>> * Branch for ingest re-architecture created > > > >>> https://github.com/apache/incubator-spot/tree/spot-242-ingest > > > >>> * Epic created in JIRA for ingest re-architecture > > > >>> https://issues.apache.org/jira/browse/SPOT-185 > > > >>> > > > >>> 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-09-08 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> 2017-06-02 > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](spot) Jarek Jarcec Cecho > > > >>> Comments: > > > >>> [ ](spot) Brock Noland > > > >>> Comments: > > > >>> [ ](spot) Andrei Savu > > > >>> Comments: > > > >>> [ ](spot) Uma Maheswara Rao G > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >>> > > > >>> > > > >>> > > > >>> -------------------- > > > >>> Superset > > > >>> > > > >>> Superset is an enterprise-ready web application for data > exploration, > > > >> data > > > >>> visualization and dashboarding. > > > >>> > > > >>> Superset has been incubating since 2017-05-21. > > > >>> > > > >>> Three most important issues to address in the move towards > > graduation: > > > >>> 1. Grow the community and enroll new committers. > > > >>> 2. Plan and execute our first Apache release > > > >>> 3. Make progress > > > >>> > > > >>> Any issues that the Incubator PMC or ASF Board might wish/need to > be > > > >> aware > > > >>> of? > > > >>> * We’re working on finding a way to link Jira Issues to GitHub > Issues > > > as > > > >> the > > > >>> team has a preference for using GitHub Issues for tracking. > > > >>> > > > >>> How has the community developed since the last report? > > > >>> * Organic growth of our Github contributors (184), forks (2,675), > > > >> watchers > > > >>> (888) and stars (16,969) > > > >>> * Group of active committers meeting bi-weekly from Airbnb, Lyft > and > > > >>> Twitter (Apple joining soon) > > > >>> * Slack channel for Apache Superset created at > > > >>> https://apache-superset.slack.com/ > > > >>> > > > >>> How has the project developed since the last report? > > > >>> * Committers have created initial UI/UX mocks and engineering plan > > for > > > >>> redesign of Explore and Dashboarding views > > > >>> * A healthy, constant flow of bug fixes, quality improvements and > new > > > >>> features, take a look at the project’s Pulse on Github for more > > details > > > >>> * The team has completed all of the items on the Incubation > Checklist > > > >>> > > > >>> > > > >>> How does the podling rate their own maturity. > > > >>> [ ] Initial setup > > > >>> [X] Working towards first release > > > >>> [ ] Community building > > > >>> [ ] Nearing graduation > > > >>> [ ] Other: > > > >>> > > > >>> Date of last release: No official release yet since being voted > into > > > >> Apache > > > >>> Incubation. (Planning for the first Apache release in Q2, 2018) > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> * Grace Guo - PPMC & Committer (2017-10-29) > > > >>> * Chris Williams - PPMC & Committer (2017-10-20) > > > >>> * John Bodley - PPMC & Committer (2017-10-20) > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](superset) Ashutosh Chauhan > > > >>> Comments: > > > >>> [X](superset) Luke Han > > > >>> Comments: > > > >>> [ ](superset) Jim Jagielski > > > >>> Comments: > > > >>> > > > >>> 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. Re-engage PMC to encourage regular activity > > > >>> 2. Retiring irrelevant git repositories > > > >>> 3. Graduate! > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> > > > >>> Community slow. Considering retiring, but will try one last push. > > > >>> > > > >>> > > > >>> How has the community developed since the last report? > > > >>> > > > >>> Quite a few pull requests, but need follow ups. > > > >>> Non-PPMC committers have taken more charge in release preparation. > > > >>> > > > >>> > > > >>> Email stats since 2017-09-01: > > > >>> > > > >>> dev@taverna: 29 > > > >>> users@taverna: 2 > > > >>> > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> Very slow progress towards graduation. > > > >>> Some progress towards next releases - need implicit Release Manager > > > >>> delegation. > > > >>> > > > >>> > > > >>> 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 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> > > > >>> 2016-10-20 > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [x](taverna) Andy Seaborne > > > >>> Comments: > > > >>> > > > >>> In Dec 2016, the report said "Preparing to graduate." In 2017, the > > dev@ > > > >>> list has been quiet and the last release was in 2016. > > > >>> > > > >>> While the PPMC is large, not everyone has been active in > > incubation. I > > > >> am > > > >>> worried that pushing through graduation will only result in the > same > > > >>> situation as a TLP. > > > >>> > > > >>> The community needs to consider what is the best environment for > > > Taverna. > > > >>> > > > >>> [ ](taverna) Daniel J Debrunner > > > >>> Comments: > > > >>> [ ](taverna) Marlon Pierce > > > >>> Comments: > > > >>> [x](taverna) Stian Soiland-Reyes > > > >>> Comments: I have admitted lack of leadership. I think we should > > > >>> seriously consider retiring, but only after a 6 month push towards > > > >> getting > > > >>> graduation done. > > > >>> [ ](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. > > > >>> > > > >>> Two most important issues to address in the move towards > graduation: > > > >>> > > > >>> 1. Improve community engagement > > > >>> 2. 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 > > > >>> - 18 new JIRAs filed since the last report > > > >>> - 1 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? > > > >>> > > > >>> - Tephra 0.13.0-incubating released > > > >>> - Working on 0.14.0-incubating 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 the last release: > > > >>> > > > >>> 2017-09-21 > > > >>> > > > >>> When were the last committers or PMC members elected? > > > >>> > > > >>> - None since coming to incubation > > > >>> > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [X](tephra) Alan Gates > > > >>> Comments: > > > >>> [ ](tephra) Andrew Purtell > > > >>> Comments: > > > >>> [x](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. > > > >>> 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? > > > >>> > > > >>> - New mentor added: Jacques Le Roux > > > >>> - Slowly attracting more adopters and subscribers. > > > >>> - ML postings: 37 user, 396 dev, 528 coderev, 668 issues, 533 > commits > > > >>> - Twitter: 228 followers, 73 tweets, 66 likes > > > >>> > > > >>> How has the project developed since the last report? > > > >>> > > > >>> * 115 commits from 17 contributors. > > > >>> * 95 tickets filed and 78 resolved. > > > >>> * We are working towards our next release, 2.2. Ming Liu is the > > Release > > > >>> Manager. > > > >>> > > > >>> 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: > > > >>> Request to graduate submitted to board after discussions. > > > >>> > > > >>> Date of last release: > > > >>> 2017-05-01 2.1 > > > >>> > > > >>> When were the last committers or PPMC members elected? > > > >>> 2017-03-10 > > > >>> > > > >>> Signed-off-by: > > > >>> > > > >>> [ ](trafodion) Michael Stack > > > >>> Comments: > > > >>> [X](trafodion) Jacques Le Roux > > > >>> Comments: I'm new to this poddling, but I have already seen that > > the > > > >>> activity is steady, the CI pipeline is working good > and > > > >> over > > > >>> all > > > >>> I like the responsiveness and kindness of the > community. > > > >>> Ready for graduation! > > > >>> > > > >>> 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. > > > >>> 2. > > > >>> 3. > > > >>> > > > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to > be > > > >>> aware of? > > > >>> Wave project had low levels of activity and no active > contributions. > > > The > > > >>> community discusses how to proceed with project termination. > > > >>> > > > >>> > > > >>> > > > >>> 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: > > > >>> > > > >>> [ ](wave) Upayavira > > > >>> Comments: > > > >>> [ ](wave) John D. Ament > > > >>> Comments: > > > >>> > > > >>> IPMC/Shepherd notes: > > > >> > > > >> > > > > > > > > >
