Incubator PMC report for April 2019
** FINAL DO NOT EDIT **
Timeline
Wed April 03 | Podling reports due by end of day |
Sun April 07 | Shepherd reviews due by end of day |
Sun April 07 | Summary due by end of day |
Tue April 09 | Mentor signoff due by end of day |
Wed April 10 | Report submitted to Board |
Wed April 17 | Board meeting |
...
Dave Fisher | Annotator | ||
Dave Fisher | Warble | ||
Drew Farris | Livy | ||
Drew Farris | TVM | ||
Justin Mclean | Amaterasu | ||
P. Taylor Goetz | Gobblin | ||
P. Taylor Goetz | Spot | ||
P. Taylor Goetz | Taverna | ||
Timothy Chen | BatchEE | ||
Timothy Chen | Hudi Timothy Chen | MXNet | |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0c8230d6747d7c3c-64bbbf1c-491a4cbc-a3beb334-21550e53729513c6d0aa5d9e"><ac:plain-text-body><![CDATA[ | [none] | Milagro NetBeans | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f74590713ce33195-ef3509c9-48924b28-9fa99c9a-1a17280b4409dc5ffbbbf373"><ac:plain-text-body><![CDATA[ | [none] | NetBeans PLC4X | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5a8bf309a44457ec-e40492f0-47ef4fb8-9804b8a9-dcbb4cbda35894ee55d98d8a"><ac:plain-text-body><![CDATA[ | [none] | PLC4X Rya | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3b58b34b8465e19c-7a6f408f-4fbf403a-b28cbb5d-9f1af326a47245a16f6f4850"><ac:plain-text-body><![CDATA[ | [none] | Rya SensSoft | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="673be950f0427d9e-31c1a83e-4ec8424d-9a3d89ea-f10dcbd037a21ca0b1dc4ce0"><ac:plain-text-body><![CDATA[ | [none] | SensSoft Training | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3a48f9a34493b2ed-ed3ad091-49104941-8f97a1f2-155bc13097799643cac6bef5"><ac:plain-text-body><![CDATA[ | [none] | Training Weex | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="cb7ed02b-e837-4f56-a980-507e21c85b71"><ac:plain-text-body><![CDATA[ | [none] | Weex | ]]></ac:plain-text-body></ac:structured-macro> |
Report content
Report content
No Format |
---|
Incubator PMC report for April |
No Format |
Incubator PMC report for April 2019 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. <There narrative > * Community New IPMC members: People who left the IPMC: * New Podlings * Podlings that failed to report, expected next month * Graduations The board has motions for the following: - Your podling here? - Your podling here? * Releases The following releases entered distribution during the month of March: * IP Clearance * Legal / Trademarks * Infrastructure * Miscellaneous * Credits ---------------------------------------------------------------------- Table of Contents Amaterasu Annotator BatchEE Gobblin Hudi Livy Milagro MXNet NetBeans PLC4X Rya SensSoft Spot Taverna Training TVM Warble Weex ---------------------------------------------------------------------- -------------------- Amaterasu Apache Amaterasu is a framework providing continuous deployment for Big Data pipelines. Amaterasu has been incubating since 2017-09-07. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](amaterasu) Jean-Baptiste Onofré Comments: [ ](amaterasu) Olivier Lamy Comments: [ ](amaterasu) Davor Bonaciare presently 53 podlings incubating. During the month of March, podlings executed 10 distinct releases. We added two new IPMC members and no IPMC members retired. We have three new podlings this month, Apache DataSketches and Apache Tuweni and Apache TVM. No projects graduated last month but several podlings are heading towards graduation in the next few months. All three of the podlings that failed to report last month submitted a report this month. Two podlings have not submitted reports and will be asked to report next month. They are: - Milagro - MXNet Spot failed to get sign off from its single mentor and will be asked to report next month. There was no IP clearance(s). ECharts still has several issues that are outstanding (including the echarts baidu website) and it's probably time to discuss how to resolve this on the IPMC list. Skywalking, on its second attempt, had a number of difficulties in cleaning up rosters and getting PPMC members onto the private mailing list after they proposed to graduate. Having a pre-graduation checklist may be useful to make this process easier. A shiny new Podling clutch page (and a new process behind it) have been updated and changed to improve tracking of podlings progress. The incubator is providing a new service to podlings to provide feedback on releases. Podlings can bring up a discuss thread asking for feedback on a release candidate rather than asking for it in a vote thread. The release management documentation was updated to make it clear what to do about non-ASF releases and encourage podings to bring those in line with ASF release and distribution policy over time. Having a smaller IPMC was discussed, it was suggested that anyone not signed up to the private list to be removed from the IPMC. This was looked into and people who make infrequent contributors are still helpful and make useful contributions. What seems less helpful in some cases is "drive-by" comments and the involvement of uninformed people on this list. Mentors are being actively encouraged to vote on their podling releases, so that the VOTEs show up on the general@ list with 3 +1 IPMC votes. Incubator wiki is being deprecated, we've tried to migrate via the self help migration tool but it has failed every time. There is a risk that it will not be transferred by the deadline. This may have an impact on submitting the next report to the board. A large number of incubator pages have been updated to be simpler and remove policy content that is explained elsewhere at the ASF. More is still needed to be done here and it's an ongoing process. An incubator cookbook has been created, which single page of explanations and links that cover all phases of incubation and should become the central point for all questions related to incubation. There are other ongoing conversations about further changes to the IPMC and how it operates. A couple of these conversations happened on the incubator private list (and other lists) when they should probably be on the general list so that all interested people can read and contribute. * Community New IPMC members: - Kanchana Welagedara - Krzysztof Sobkowiak People who left the IPMC: None. Luke Han resigned from mentoring 4 podlings. * New Podlings - DataSketches - Tuweni - TVM * Podlings that failed to report, expected next month are listed above * Graduations The board has motions for the following: - NetBeans - PLC4X - Skywalking * Releases The following releases entered distribution during the month of March: - Echarts 4.2.1 - Dubbo 2.7.1 - Zipkin Brave for Apache Cassandra version 0.10.2 - Pony Mail 0.11 - Apache Myriad 0.3.0 - PLC4X 0.3.1 - Apache Pinot 0.1.0 - Apache Dubbo 2.6.6 - NetBeans parent 1 - OpenWhisk CLI 0.10.0 * IP Clearance None * Legal / Trademarks N/A * Infrastructure N/A * Miscellaneous - Discussion on withdrawing from Incubator - Include Incubator as part of community track at ApacheCon NA - A few podling distribution areas needed cleaning up included removing some graduated and retired podlings - SensSoft change its name to Flagon ---------------------------------------------------------------------- Table of Contents Amaterasu Annotator BatchEE Gobblin Hudi Livy NetBeans PLC4X Rya SensSoft Spot Taverna Training TVM Warble Weex ---------------------------------------------------------------------- -------------------- Amaterasu Apache Amaterasu is a framework providing configuration management and deployment for Big Data Pipelines. It provides the following capabilities: Continuous integration tools to package pipelines and run tests. A repository to store those packaged applications: the applications repository. A repository to store the pipelines, and engine configuration (for instance, the location of the Spark master, etc.): per environment - the configuration repository. A dashboard to monitor the pipelines. A DSL and integration hooks allowing third parties to easily integrate. Amaterasu has been incubating since 2017-09-07. Three most important issues to address in the move towards graduation: 1. Grow up user and contributor communities 2. Prepare documentation Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There is still concern regarding the progress of the project. The community tries to address this by making the project more accessible. The first major step is releasing the documentation and simplifying the install process. In addition, we are working closely with some of the newer contributors to mentor them and help them be more productive. How has the community developed since the last report? Since the last report, we have been focusing on the next release with strong focus building the documentation which we hope will help with adoption. We are still working with a couple of organizations on their use case, hopefully, those could become a public use cases soon. How has the project developed since the last report? * 11 pull requests by 4 contributors have been opened since the last report. Out of those 2 have been closed, 1 is awaiting fixes and the rest have been merged. * Documentation has been progressing and is due for the upcoming release. Date of the last release: 12 July 2018 When were the last committers or PMC members elected? N/A Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. N/A Signed-off-by: [X](amaterasu) Jean-Baptiste Onofré Comments: [X](amaterasu) Olivier Lamy Comments: [X](amaterasu) Davor Bonaci Comments: the activity in the project is not indicative of a thriving project. IPMC/Shepherd notes: -------------------- Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator has been incubating since 2016-08-30. Three most important unfinished issues to address before graduating: 1. Release initial versions 2. Add more active contributors 3. Community growth in general Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Community growth for our project has been much slower than expected. We are aiming to ship a release and add at least one committer prior to the next board report. We will also be discussing the project's scope and future and trying one last time to (re)build the interest and community we'd had during the W3C's Web Annotation Working Group days (and the time prior when Annotator.js and Open Annotation were in full swing). How has the community developed since the last report? The immediate Apache Annotator community has remained quiet, but interest in Web Annotations (and surrounding technology/specs) has increased. We hope to tap into some of that new activity in this second quarter of 2019. Additionally, we hope to do further community outreach in person at the upcoming I Annotate event in May: http://iannotate.org/ How has the project developed since the last report? Code and community show minimal (if any) progress. The projects focus may be too narrow or the audience for our current DOM libraries may be too small to achieve frequent activity at this point. We did begin an effort to expand the scope of the project slightly to include server-side code and Web Annotation Data Model testing, but interest so far has remained minimal. 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? Last committer was added in August. That same committer is now on the PMC as of November. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. We did welcome our two new mentors, but have not had follow-up conversations as a community to (re)focus the group since then. We hope to change that in the coming weeks as we look toward promoting the project again at the upcoming I Annotate 2019 conference. Signed-off-by: [*](annotator) Nick Kew Comments: Not really anything to add to the above. [ ](annotator) Steve Blackmon Comments: [ ](annotator) Tommaso Teofili Comments: IPMC/Shepherd notes: Dave Fisher: This looks like a reasonable assessment of activity. Let's see if community engagement increases after the event in May. The July report looks like the point to make a decision ... -------------------- BatchEE BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification. BatchEE has been incubating since 2013-10-03. Three most important unfinished issues to address before graduating: 1. We didn't manage to graduate 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Graduation is stucked How has the community developed since the last report? Community is stable How has the project developed since the last report? Not much since there is no new release of the specification. 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: toward the exit of incubator in favor of Geronimo (as a subproject) Date of last release: 2017-12-01 When were the last committers or PPMC members elected? 2015-12-01 Reinhard Sandtner Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [X](batchee) Jean-Baptiste Onofré Comments: [X](batchee) Olivier Lamy Comments: [ ](batchee) Mark Struberg Comments: IPMC/Shepherd notes: -------------------- Gobblin Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. Gobblin has been incubating since 2017-02-23. Three most important issues to address in the move towards graduation: Nothing at this time. 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? * 53% of commits were from non-committer contributors. * Another committer was voted it, building a healthy cadence of contributors stepping up and being voted in as committers. * Email stats since last report: user@gobblin.incubator.apache.org : 30 dev@gobblin.incubator.apache.org : 692 * There have been 53 Commits since last report: git log --format='%ci' | grep -cE '((2019-0(1|2|3|4)))' * 28 ie. 53% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '((2019-0(1|2|3|4)))'| cut -d ' ' -f 1 | sort | uniq -c | sort -n * After ApacheCon NA 2018, CrunchConf Budapest 2018, community is planning to present in ApacheCon NA 2019, ApacheCon EU 2019. How has the project developed since the last report? * Enhancement to GaaS scheduler (more features like query for last k flow executions, explain query, auto state store cleanup, Azkaban client improvement, etc.). * Watermark manager improvements for streaming use-cases. * Lineage support for filesystem based sources. * Job catalog memory usage optimizations. * New versioning strategy for config based datasets in Distcp. * Dynamic mappers support. * Pluggable format-specific components in Gobblin compaction. * ORC based Gobblin compaction. 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: 2018-12-09 When were the last committers or PPMC members elected? Sudarshan Vasudevan in January, 2019. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes. Signed-off-by: [X](gobblin) Jean-Baptiste Onofre Comments: [X](gobblin) Olivier Lamy Comments: Very healthy project with a lot of activities! [X](gobblin) Jim Jagielski Comments: IPMC/Shepherd notes: -------------------- Hudi Hudi provides atomic upserts and incremental data streams on Big Data Hudi has been incubating since 2019-01-17. Three most important unfinished issues to address before graduating: 1. Make frequent releases as per Apache guidelines 2. Grow community 3. Complete SGA, transfer code to ASF infra Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * PODLINGNAMESEARCH-162 has been completed, but is not reflected on Whimsy * SGA process has been delayed due to inability to quickly interact with ASF legal counsel. Help expediting this communication would help a lot to get the SGA done by Uber. How has the community developed since the last report? - Project source code/docs/issue management all now hosted on apache infrastructure - HIP, a process for proposing large changes to the project has been formalized by the community - 30+ new threads on dev ML, with ~10 non-PPMC contributors How has the project developed since the last report? 1. Code has been moved over to apache/incubator-hudi 2. hudi.apache.org site has been restructured and simplified for community consumption 3. Hudi Improvement Plan (based off Apache Kafka KIP) ratified and formalized. Few first HIPs written 4. Submitted a Hudi talk abstract for Kafka Summit 2019 5. ~20 PRs merged 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: Project still being established in Incubator When were the last committers or PPMC members elected? No new committers since incubation. Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes. Mentors are continuing to help us make things better Signed-off-by: [X](hudi) Thomas Weise Comments: [X](hudi) Luciano Resende Comments: The podling is claiming 'Initial Setup'. What is still missing? Any help required from mentors ? [ ](hudi) Kishore Gopalakrishnan Comments: [X](hudi) Suneel Marthi Comments: IPMC/Shepherd notes: -------------------- Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. 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 user email list has kept a consistent flow of discussion around the project. How has the project developed since the last report? Version 0.6 was released How would you assess the podling's maturity? Mailing lists and project development follow the Apache way. The user community is active but lately the rate of change in the project code is lower. This may not be a cause for concern since it might indicate relative maturity in achieving the desired functionality of the project. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2019-04-02 When were the last committers or PPMC members elected? 2019-01-22 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Our mentors are regularly quick to respond on the dev list when addressed. Signed-off-by: [x](livy) Bikas Saha Comments: [ ](livy) Brock Noland Comments: [x](livy) Luciano Resende Comments: [X](livy) Jean-Baptiste Onofre Comments: IPMC/Shepherd notes: Justin Mclean: Asked the podling to provide more detail. -------------------- NetBeans NetBeans is a development environment, tooling platform and application framework. NetBeans has been incubating since 2016-10-01. Three most important unfinished issues to address before graduating: 1. Resolution discussion on PPMC mailing list. 2. Resolution discussion on IPMC mailing list. 3. Top level project vote thread on IPMC mailing list. 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? - Presented status of Apache NetBeans at FOSDEM 2019: https://fosdem.org/2019/schedule/track/free_tools_and_editors/ - Currently 667 (651 in last report) on Apache NetBeans users mailing list and 451 (455 in last report) on Apache NetBeans dev mailing list. How has the project developed since the last report? - Released Apache NetBeans 11.0. - Completed maturity model for graduation: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Maturity+Model+A ssessment+for+NetBeans - Cleaned up the committer/PPMC roster: https://cwiki.apache.org/confluence/display/NETBEANS/Realistic+PMC+Roster - Discussed and voted, with success, on a PMC chair for after graduation to top level project: https://s.apache.org/07Jh - Discussed and voted, with success, on becoming a top level project with 64 "+1" votes and no "0" or "-1" votes: https://s.apache.org/uvuz How would you assess the podling's maturity? [ ] Initial setup [ ] Working towards first release [ ] Community building [ X ] Nearing graduation [ ] Other: Date of last release: 2019-04-04 Apache NetBeans (incubating) 11.0 final release When were the last committers or PPMC members elected? * PPMC member Simon Phipps elected on March 28, 2019 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, helpful and responsive. Signed-off-by: [X](netbeans) Ate Douma Comments: NetBeans has a large, healthy and active community, and group of committers and PPMC, which is ready to take on the responsibility to manage themselves as TLP: time to graduate! [x](netbeans) Bertrand Delacretaz Comments: NetBeans is ready to graduate, the IPMC graduation vote should start soon. [x](netbeans) Daniel Gruno Comments: Let's graduate :) [ ](netbeans) Mark Struberg Comments: IPMC/Shepherd notes: -------------------- PLC4X Annotator Annotator provides annotation enabling code for browsers, servers, and humans. Annotator PLC4X is a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. PLC4X has been incubating since 20162017-0812-3018. Three most important unfinished issues to address before graduating: 1. Vote on graduation on 2. IPMC general 3.list Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has theNot communityat developed since the last report? moment. How has the projectcommunity 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 [Previously ]added Community building [ ] Nearing graduationPPMC/Committers have setup and the onboarding process [has ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](annotator) Nick Kew Comments: [ ](annotator) Steve Blackmon Comments: [ ](annotator) Tommaso Teofili Comments: IPMC/Shepherd notes: -------------------- BatchEE BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification. BatchEE has been incubating since 2013-10-03. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](batchee) Jean-Baptiste Onofré Comments: [ ](batchee) Olivier Lamy Comments: [ ](batchee) Mark Struberg Comments: IPMC/Shepherd notes: -------------------- Gobblin Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. Gobblin has been incubating since 2017-02-23. Three most important unfinished issues to address before graduating: 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? been pretty successful. One new name has showed up on the list demonstrating willingness to help with the website and documentation. Now in total 3 people have demonstrated the ability to perform releases. We are currently tying up some loose ends and preparing everything to start the graduation vote in the next few weeks. All of this has been consuming quite some time. We have had a meetup in Nürtingen on 15th of February which a great part of the active PPMC and committers attended. Beyond that on 21th of February Christofer had a talk on PLC4X at EURegJug in Aachen, on 8th of March in Solingen. Numbers: - Releases: - 0.3.0 RC2: 05.02.2019 (RM: Julian Feinauer) - 0.3.1 RC1: 13.03.2019 (RM: Julian Feinauer, but Tim Mitsch actually did it) - Mailing-list Subscriptions: 43 (up by 1) - Twitter followers: 132 (up by 18) - GitHub stars: 52 (up by 10) How has the project developed since the last report? Christofer is working hard on implementing a first POC for a tooling to generate drivers from DFDL and SCXML specifications, which will greatly simplify driver implementation as well as make it possible to generate drivers for multiple target languages, such as C++. No new POCs have been performed this period however another company has shifted to using PLC4X as main integration platform in their analytics software. Also a consortium of 3 companies and the ISW from Stuttgart University received a positive response to a project proposal that was supported for the funding program "KMU Innovativ" at BMBF German ministry of education and research. PLC4X will play an important role in the project for communication with industrial controllers and will be integrated by the industrial partner pragmatic minds GmbH which is represented in the (P)PMC by Julian Feinauer. 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: XXXX2019-XX-XX03-13 0.3.1 RC1 When were the last committers or PPMC members elected? 2019-02-04 Tim Mitsch (PPMC and committer) Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. They have been very helpful. Especially regarding questions about graduating, Justin has been particularly helpful in pointing out some missing things. Signed-off-by: [ X](gobblinplc4x) Jean-BaptisteGreg OnofreTrasuk Comments: [ X](gobblinplc4x) OlivierJustin LamyMclean Comments: [ X](gobblinplc4x) JimStefan JagielskiBodewig Comments: IPMC/Shepherd notes: -------------------- Rya Rya (pronounced "ree- Hudi Hudi provides atomic upserts and incremental data streams on Big Data Hudiuh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Accumulo. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data. Rya has been incubating since 20192015-0109-1718. Three most important unfinished issues to address before graduating: 1. Working through the 2. graduation procedure 3steps. 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? No 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](hudi) Thomas Weise Comments: [ ](hudi) Luciano Resende Comments: [ ](hudi) Kishore Gopalakrishnan Comments: [ ](hudi) Suneel Marthi Comments: IPMC/Shepherd notes: -------------------- Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? How has the project developed since the last report? Voting on the next 0.6 release How would you assess the podling's maturity? Mailing lists and project development follow the Apache way. The user community is active but lately the rate of change in the project code is lower. This may not be a cause for concern since it might indicate relative maturity in achieving the desired functionality of the project. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [x](livy) Bikas Saha Comments: [ ](livy) Brock Noland Comments: [ ](livy) Luciano Resende Comments: [ ](livy) Jean-Baptiste Onofre Comments: IPMC/Shepherd notes: -------------------- Milagro Distributed Cryptography; M-Pin protocol for Identity and Trust Milagro has been incubating since 2015-12-21. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](milagro) Nick Kew Comments: IPMC/Shepherd notes: -------------------- MXNet A Flexible and Efficient Library for Deep Learning MXNet has been incubating since 2017-01-23. Three most important unfinished issues to address before graduating: 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 [ community developed since the last report? * The community is moving towards graduation: name search completed, project status file updated, the Apache Project maturity model evaluation almost done * PPMC member Adina Crainiceanu presented "Apache Rya - A Scalable RDF Triple Store" talk at Apache Roadshow DC, March 25th, 2019 How has the project developed since the last report? * upgraded SPARQL endpoint under review 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: 2018-03-04 When were the last committers or PPMC members elected? * PPMC member Caleb Meier elected on Jan 3rd, 2017 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Our two mentors are helpful and responsive. Signed-off-by: [x](rya) Josh Elser Comments: Ready to graduate [x](rya) Billie Rinaldi Comments: IPMC/Shepherd notes: -------------------- SensSoft Apache SensSoft is a generalized user behavioral logging platform for web pages and thin-client applications Apache SensSoft has been incubating since 2016-07-13. Three most important issues to address in the move towards graduation: 1. Grow the Apache SensSoft (Incubating) Committer/Community Base. 2. Complete our Podling name change 3. Complete the issues highlighted at the SensSoft Roadmap [1] Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? * We have completed our PODLINGNAMESEARCH workflow and our new name Apache Flagon has been approved by VP of marketing [2]. * We have posted tickets to change the name of our core assets (JIRA, Website, GitBox Repos) [3], to coincide with changing website text, other content-based references to Apache SensSoft. * We are preparing for additional releases, immediately following our full transition to the Apache Flagon Namesake (UserALE.js v. 2.0.0, 2.1.0; poss. Flagon 1.0.0). How has the community developed since the last report? * The community has been: - discussing reaching out to other open source projects to identify other potential communities (analytical technologies) to drive developments, as well as increase interest in the Podling. - discussing research applications with university research labs in machine learning and social computing. - discussing adoption of the technology with interested entities and identifying/eliminating barriers to adoption. - updating documentation on wiki and READMEs to improve community growth How has the project developed since the last report? * Project maturity roadmaps (Wiki) and version release plans (JIRA) continue to be maintained. * JIRA boards continue to be maintained * Core products have been maintained for modernization and for security posture. * New features have been added to enhance adoption and make Apache SensSoft competitive with open-source business analytics services (e.g., OWA). How would you assess the podling's maturity? Please feel free to add your own commentary. * Despite challenges posed by dispersion of the original committers, the project is finding its footing again and continues to be desirable for consumption and relevant amidst alternatives. The impending name change is an opportunity for rebranding and acceleration of community growth. [X] Initial setup [X] Working towards first release [ X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX2018-XX03-XX14 When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are thingsArthi falling throughVezhavendan thewas cracks?added Into theCommitter latterbase case, please list any open issues that need to be addressed. Signed-off-by:on 2017-01-24 Dave Meikle was added to PPMC on 2018-11-24 [ ](mxnet) Sebastian Schelter Comments: [ ](mxnet) Henri Yandell Comments: [ ](mxnet) Markus Weimer Comments: [ ](mxnet) Jim Jagielski Comments: [ ](mxnet) Michael Wall Comments: [ ](mxnet) Bob Paulin Comments: [ ](mxnet) Jason Dai Comments: IPMC/Shepherd notes: -------------------- NetBeans NetBeans is a development environment, tooling platform and application framework. NetBeans has been incubating since 2016-10-01. Three most important unfinished issues to address before graduating: 1. Resolution discussion on PPMC mailing list. 2. Resolution discussion on IPMC mailing list. 3. Top level project vote thread on IPMC mailing list. 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? - Discussed and voted, with success, in the PPMC on becoming a top level project with 64 "+1" votes and no "0" or "-1" votes. - Currently 667 (651 in last report) on Apache NetBeans users mailing list and 451 (455 in last report) on Apache NetBeans dev mailing list. 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 [ X ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, helpful and responsive. Signed-off-by: [ ](netbeans) Ate Douma Comments: [ ](netbeans) Bertrand Delacretaz Comments: [ ](netbeans) Daniel Gruno Comments: [ ](netbeans) Mark Struberg Comments: IPMC/Shepherd notes: -------------------- PLC4X PLC4X is a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. PLC4X has been incubating since 2017-12-18. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](plc4x) Greg Trasuk Comments: [ ](plc4x) Justin Mclean Comments: [ ](plc4x) Stefan Bodewig Comments: IPMC/Shepherd notes: -------------------- Rya Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Accumulo. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data. Rya has been incubating since 2015-09-18. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](rya) Josh Elser Comments: [ ](rya) Billie RinaldiAtri Sharma was added to PPMC on 2018-11-24 Have your mentors been helpful and responsive or are things falling through the cracks? * Lewis McGibbney has been extremely helpful and has actively participated in our PODLINGNAMESEARCH. * Dave Meikle has actively participated in our PODLINGNAMESEARCH process and has pledged to assist in growing the community following a determination of our PODLINGNAMESEARCH results. * Atri Sharma has offered his mentorship, but is not yet elected to IPMC, and has not been able to offer binding votes. Signed-off-by: [ ](senssoft) Lewis John McGibbney Comments: [X](senssoft) Dave Meikle Comments: [ ](senssoft) Atri Sharma Comments: [1] https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps <https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps> [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154 <https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154> [3] https://issues.apache.org/jira/browse/INFRA-18100 <https://issues.apache.org/jira/browse/INFRA-18100> IPMC/Shepherd notes: -------------------- Spot Apache Spot is a platform for network telemetry built on an open data model and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important unfinished issues to address before graduating: 1. Revive community activity (Discussion in mailing lists, increase frequency of commits) 2. Make it easier for Devs to contribute to the project (e.g. documentation, framework). 3. Developing a workflow in Spot that allows for intuitive analytics. 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? Unfortunately there has not been much more community activity. However, we are need of more committers as there are only a couple of active committers at this time. This creates a bottleneck which makes it hard for the community to grow in interest. How has the project developed since the last report? A few members have been looking into merging one of the major branches that the community has been waiting on into master. This should avoid a lot of confusion among new community members in the future. 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: 2017-09-08 When were the last committers or PPMC members elected? 2018-01-18 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes our single mentor is responsive, however we only have one and may need 1 more to help. Signed-off-by: [ ](spot) Uma Maheswara Rao G 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 unfinished issues to address before graduating: 1. Re-engage PPMC members 2. Release IP-fixed repositories 3. Graduate! 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? Gone quiet after Christmas. More of PPMC member activity would be desired. Lately more user questions than developer threads. How has the project developed since the last report? Moved Git repositories to GitHub via GitBox Previous IP/licensing issues now resolved. Pending release of updated git repositories. 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 [x] Nearing graduation [ ] Other: Date of last release: 2018-01-18 When were the last committers or PPMC members elected? 2018-02-26 (PPMC) Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Down to one active mentor. Thanks to retiring mentor Andy for his consistent and helpful effort since incubation. Signed-off-by: [ ](taverna) Marlon Pierce Comments: [x](taverna) Stian Soiland-Reyes Comments: Need a bit of push to do the remaining releases after fixing IP issues. [ ](taverna) Suresh Srinivas Comments: IPMC/Shepherd notes: ------------------------ SensSoft SensSoft is a software tool usability testing platform SensSoft The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects. Training has been incubating since 20162019-0702-1321. Three most important unfinished issues to address before graduatingin the move towards graduation: 1. Agree upon underlying technology stack and architecture for training content 2. Develop first training topic contents 3. Set up our contribution process 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? - no critical issues at this point in time How has the projectcommunity developed since the last report? How would you- assessThe theproject 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](senssoft) Lewis John McGibbney Comments: [ ](senssoft) David Meikle Comments: [ ](senssoft) Atri Sharma Comments: IPMC/Shepherd notes: -------------------- Spot Apache Spot is a platform for network telemetry built on an open data model and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important unfinished issues to address before graduating: 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? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](spot) Uma Maheswara Rao G 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 unfinished issues to address before graduating: 1. Re-engage PPMC members 2. Release IP-fixed repositories 3. Graduate! 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? Gone quiet after Christmas. More of PPMC member activity would be desired. Lately more user questions than developer threads. How has the project developed since the last report? Moved Git repositories to GitHub via GitBox Previous IP/licensing issues now resolved. Pending release of updated git repositories. 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 [x] Nearing graduation [ ] Other: Date of last release: 2018-01-18 When were the last committers or PPMC members elected? 2018-02-26 (PPMC) Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Down to one active mentor. Thanks to retiring mentor Andy for his consistent and helpful effort since incubation. Signed-off-by: [ ](taverna) Marlon Pierce Comments: [x](taverna) Stian Soiland-Reyes Comments: Need a bit of push to do the remaining releases after fixing IP issues. [ ](taverna) Suresh Srinivas Comments: IPMC/Shepherd notes: -------------------- Training The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non- Apache target projects. Training has been incubating since 2019-02-21. Three most important unfinished issues to address before graduating: 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? has been set up recently, so there is an initial activation/development towards a community. - The dev mailing list is active. Total number of posts in March were 160 (+48 from March). Total number of subscribers is 28 (+3 from last month). How has the project developed since the last report? - This is our first report covering a full month - We have decided on a Website technology and we have had our first few commits (LICENSE, README etc.) - The scope of the project deliverables, core procedures, details regarding website, and code management are still under discussion - First offers of content donations have been made - We welcomed our first regular contributor to the mailing list from outside of the original list of contributors - There are plans to talk about the project at both ApacheCons this year There are lots of parallel discussions happening. We have made some initial decisions (e.g. website) but there are lots of topics still left to be discussed. The major one is on whether or not to chose a canonical technology into which we want to convert our training material and the organization thereof (e.g. multilingual content and acceptance of material in different formats e.g. PowerPoint, Google Slides). The project is a bit different from most others which come with existing code bases, existing communities. We have to start from "first principles" so it's not unexpected that this takes a while. How would you assess the podling's maturity? [x] Initial setup [ ] 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? n.a. Signed-off-by: [X](training) Justin Mclean Comments: [ ](training) Craig Russell Comments: [X](training) Christofer Dutz Comments: [x](training) Lars Francke Comments: IPMC/Shepherd notes: -------------------- TVM TVM is a full stack open deep learning compiler stack for CPUs, GPUs, and specialized accelerators. It aims to close the gap between the productivity- focused deep learning frameworks, and the performance- or efficiency-oriented hardware backends. TVM has been incubating since 2019-03-06. Three most important unfinished issues to address before graduating: 1. Finish the IP clearance 2. Make the first Apache release 3. Continue to 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? - TVM PMC has been fully transitioned to private@ - The development conversations are mirrored to dev@ - TVM community has welcomed two new committers in the past month See more in https://github.com/dmlc/tvm/search?q=COMMUNITY&type=Issues NOTE: due to the transition, the vote of the new committers were done in the pre-apache PMC private list with our mentors as observers. We are doing procedural votes to bring these committers formally to Apache soon. How has the project developed since the last report? In the past month, 47 contributors have pushed 138 commits. On master, 480 files have changed and there have been 18,529 additions and 4,290 deletions. See details in our monthly report Mar: https://discuss.tvm.ai/t/tvm-monthly-march-2019/2083/2 Feb: https://discuss.tvm.ai/t/tvm-monthly-feb-2019/1801 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: XXXX-XX-XX None yet When were the last committers or PPMC members elected? 2019 Mar 15 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Mentors are very helpful in helping to set up the podling and provide helpful guidances. Signed-off-by: [X](tvm) Byung-Gon Chun Comments: [X](trainingtvm) CraigSebastian RussellSchelter Comments: [X](tvm) Henry Saputra Comments: [X](trainingtvm) ChristoferTimothy DutzChen Comments: [ X](trainingtvm) JustinFurkan McleanKamaci Comments: [ X](trainingtvm) LarsMarkus FranckeWeimer Comments: IPMC/Shepherd notes: -------------------- TVMWarble TVM is a fulldistributed stackendpoint openmonitoring deepsolution learningwhere compilerthe stackagent foris CPUs,hosted GPUs,on andyour specializedown acceleratorshardware. Warble Ithas aimsbeen toincubating close the gap between the productivity- focused deep learning frameworks, and the performance- or efficiency-oriented hardware backends. TVM has been incubating since 2019-03-06. Three most important unfinished issues to address before graduating: 1. 2since 2018-06-11. Three most important unfinished issues to address before graduating: 1. Engage initial committers. 2. Set core design and feature set, avoid creep of new features before the core is complete. 3. Expand committers and community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No issues other than our slow movement and missed board reports. How has the community developed since the last report? NA 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 [Dev ]has Workingstalled towardsas firstwe release try to [engage ]committers. CommunityThis buildingcode was [donated ]to Nearingthe graduation ASF as [it ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Signed-off-by: [ ](tvm) Byung-Gon Chun Comments: [ ](tvm) Sebastian Schelter Comments: [ ](tvm) Henry Saputra Comments: [ ](tvm) Timothy Chen Comments: [ ](tvm) Furkan Kamaci Comments: IPMC/Shepherd notes: -------------------- Warble a distributed endpoint monitoring solution where the agent is hosted on your own hardware. Warble has been incubating since 2018-06-11. Three most important unfinished issues to address before graduating: 1. Engage initial committers. 2. Set core design and feature set, avoid creep of new features before the core is complete. 3. Expand committers and community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No issues other than our slow movement and missed board reports. How has the community developed since the last report? NA How has the project developed since the last report? Dev has stalled as we try to engage committers. This code was donated to the ASF as it was a 3rd Party Infra tool. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? NA Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. NA Signed-off-by: [ ](warble) Daniel Takamori Comments: [X](warble) Chris Lambertus 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 unfinished issues to address before graduating: 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? was a 3rd Party Infra tool. How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: XXXX-XX-XX When were the last committers or PPMC members elected? NA Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. NA Signed-off-by: [ ](warble) Daniel Takamori Comments: [X](warble) Chris Lambertus Comments: IPMC/Shepherd notes: Dave Fisher: This podling is around a system for monitoring services that the Infrastructure team is looking into. It is really going very slowly. The proof will be in whether interest develops beyond the Infra team. It may be worth discussing in the IPMC the best way to handle these kinds of bespoke projects. Is Warble (and maybe Pony Mail) more a Lab project? -------------------- Weex Weex is a framework for building Mobile cross-platform high performance UI. Weex has been incubating since 2016-11-30. Three most important unfinished issues to address before graduating: 1. Third party plugins like weex-toolkit is not part of Apache Weex, and they may violate the trademark / copyright of ASF 2. The release procedure for Weex is not documented clearly. 3. More active committers and PPMC members should be invited into the community. 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? 1. There are two new committers for Weex, e.g. He Ling and Darin726. 2. We have a new mentor : Jan Piotrowski 3. The mailing list for weex community is getting better, as we have 28 mailing threads in dev@weex.apache.org How has the project developed since the last report? 1. We launched new website for Weex. 2. We merged and closed 144 Github PRs 3. We had 212 Github issues created and 145 of them are solved. 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: XXXX2018-XX-XX12-10 (v0.20.0) When were the last committers or PPMC members elected? 2019-03-06 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Yes, I think we have achieved lots of progress with their help in these month. Signed-off-by: [ ](weex) Willem Ning Jiang Comments: [ x](weex) Myrle Krantz Comments: [ ](weex) Jan Piotrowski Comments: IPMC/Shepherd notes: |