You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@incubator.apache.org by Apache Wiki <wi...@apache.org> on 2016/09/09 21:15:39 UTC
[Incubator Wiki] Update of "September2016" by MarvinHumphrey
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.
The "September2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/September2016?action=diff&rev1=70&rev2=71
Comment:
Reflow.
Three most important issues to address in the move towards graduation:
- 1. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process.
+ 1. Establish a formal release process and schedule, allowing for dependable
+ release cycles in a manner consistent with the Apache development
+ process.
2. Grow the community around the project.
- 3. Migrate existing users to apache mailing lists, redirect the present external project links to Apache.
+ 3. Migrate existing users to apache mailing lists, redirect the present
+ external project links to Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -187, +190 @@
Received Software Grant Agreement (SGA) from Gigaspaces.
- The mailing lists, Jira, Github Repo, Incubator podling, Confluence Wiki have been setup for the project.
+ The mailing lists, Jira, Github Repo, Incubator podling, Confluence Wiki
+ have been setup for the project.
How has the project developed since the last report?
@@ -200, +204 @@
When were the last committers or PMC members elected?
- Project is being established in incubator with the proposed initial set of committers.
+ Project is being established in incubator with the proposed initial set of
+ committers.
Signed-off-by:
@@ -217, +222 @@
Apache Atlas is a scalable and extensible set of core foundational governance
services that enables enterprises to effectively and efficiently meet their
- compliance requirements within Hadoop and allows integration with the complete
+ compliance requirements within Hadoop and allows integration with the
- enterprise data ecosystem
+ complete enterprise data ecosystem.
Atlas has been incubating since 2015-05-05.
Three most important issues to address in the move towards graduation:
- 1. Podling name search is pending.
+ 1. Podling name search is pending.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -233, +238 @@
How has the community developed since the last report?
- 1. We have added 4 new committers since the last report from different
+ 1. We have added 4 new committers since the last report from different
- organizations. Around 15 new contributors were added since the last report.
+ organizations. Around 15 new contributors were added since the last
- The current number of contributors is around 60.
+ report. The current number of contributors is around 60.
2. The activity on the atlas-dev mailing list stands at around 900 messages
- per month between June and August. [1]
+ per month between June and August. [1]
How has the project developed since the last report?
@@ -249, +254 @@
versioning, support for creating business taxonomies, enhanced
user interface, better performance etc.
2. Work is proceeding in 0.8-incubating to stabilize many of these
- features and also add several strategic improvements including
+ features and also add several strategic improvements including
- abstractions to the underlying graph database to make it easier
+ abstractions to the underlying graph database to make it easier
- to move to later versions, rolling upgrades, etc.
+ to move to later versions, rolling upgrades, etc.
- 3. A total of 302 issues were reported between June 1st 2016 and August 31st
+ 3. A total of 302 issues were reported between June 1st 2016 and August
- 2016. 266 issues were resolved in the same time frame [2],[3]
+ 31st 2016. 266 issues were resolved in the same time frame [2],[3]
-
Date of last release:
- 2016-07-09: 07-incubating [4]
+ 2016-07-09: 07-incubating [4]
When were the last committers or PMC members elected?
1. The PPMC voted and elected 4 new members as committers to
- the project on 2016-07-05: Tom Beerbower, Keval Bhatt, David
+ the project on 2016-07-05: Tom Beerbower, Keval Bhatt, David
- Kantor and Darshan Kumar.
+ Kantor and Darshan Kumar.
[1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/
[2] https://issues.apache.org/jira/browse/ATLAS-1149?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-06-01%20AND%20created%20%3C%3D%202016-08-31
[3] https://issues.apache.org/jira/browse/ATLAS-775?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%202016-06-01%20AND%20resolved%20%3C%3D%202016-08-31
- [4]
- https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3CCAAbv78fuzCv51E4Pn8fg7nwkJyOUQo9z2WNhsiz2EstbTvj1Gw@mail.gmail.com%3E
+ [4] https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3CCAAbv78fuzCv51E4Pn8fg7nwkJyOUQo9z2WNhsiz2EstbTvj1Gw@mail.gmail.com%3E
-
Signed-off-by:
@@ -303, +305 @@
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
+ None
How has the community developed since the last report?
- The community activity increased: many new users started to use and
+ The community activity increased: many new users started to use and
- test CarbonData, we had more than 100 new issues created during Aug; One
+ test CarbonData, we had more than 100 new issues created during Aug; One
- user formally deployed CarbonData to their business system, the
+ user formally deployed CarbonData to their business system, the
- query efficiency speeded up 50 times (the user is the biggest internet
+ query efficiency speeded up 50 times (the user is the biggest internet
- finance company in China)
+ finance company in China)
How has the project developed since the last report?
@@ -479, +481 @@
--------------------
Edgent
- Apache Edgent is a programming model and micro-kernel style runtime that can
+ Apache Edgent is a programming model and micro-kernel style runtime that
- be embedded in gateways and small footprint edge devices enabling local,
+ can be embedded in gateways and small footprint edge devices enabling
- real-time, analytics on the continuous streams of data coming from
+ local, real-time, analytics on the continuous streams of data coming from
equipment, vehicles, systems, appliances, devices and sensors of all kinds
(for example, Raspberry Pis or smart phones). Working in conjunction with
centralized analytic systems, Apache Edgent provides efficient and timely
@@ -491, +493 @@
Three most important issues to address in the move towards graduation:
- 1. Create and expand a diverse community of contributors and committers around Edgent project
+ 1. Create and expand a diverse community of contributors and committers
+ around Edgent project
- 2. Set up new build system, allowing us to remove code dependencies from our repository
+ 2. Set up new build system, allowing us to remove code dependencies from
+ our repository
3. Create the first Apache release of Edgent
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -502, +506 @@
How has the community developed since the last report?
- Significant progress has been made on a new build system, using Gradle. One of the goals
+ Significant progress has been made on a new build system, using Gradle.
- is to remove third party code, so we can work toward a release.
+ One of the goals is to remove third party code, so we can work toward a
+ release.
- The community has been active and participating in voting. Heavy commit activity, but light
+ The community has been active and participating in voting. Heavy commit
- Jira activity, recently as the name change was implemented in the code, documentation and web site.
+ activity, but light Jira activity, recently as the name change was
+ implemented in the code, documentation and web site.
How has the project developed since the last report?
- According to JIRA, the project has added the following:
+ According to JIRA, the project has added the following:
- * June: 29 new issues; 22 issues resolved.
+ * June: 29 new issues; 22 issues resolved.
- * July: 20 new issues; 15 issues resolved.
+ * July: 20 new issues; 15 issues resolved.
- * August: 7 new issues; 7 issues resolved.
+ * August: 7 new issues; 7 issues resolved.
- August activity was largely build and renaming activities, tracked under a few Jira issues.
+ August activity was largely build and renaming activities, tracked under a
+ few Jira issues.
-
- The name for the project was changed from Apache Quarks to Apache Edgent. The new name went
+ The name for the project was changed from Apache Quarks to Apache Edgent.
- through a suitable name search and was approved. The infrastructure, code and documentation changes
- have been completed.
+ The new name went through a suitable name search and was approved. The
+ infrastructure, code and documentation changes have been completed.
- A logo was voted on and chosen, and a wiki was set up for the Edgent community.
+ A logo was voted on and chosen, and a wiki was set up for the Edgent
+ community.
Date of last release:
- We have not created an Apache release as of yet. We need to complete build changes and licensing
+ We have not created an Apache release as of yet. We need to complete build
- work to create a release.
+ changes and licensing work to create a release.
When were the last committers or PMC members elected?
- In May, we added two new committers and PPMC members, Kathy Saunders and Queenie Ma.
+ In May, we added two new committers and PPMC members, Kathy Saunders and
+ Queenie Ma.
Signed-off-by:
@@ -554, +562 @@
Three most important issues to address in the move towards graduation:
- 1. Getting a first release out – we are still inhibited by Hibernate issues which are more deeply rooted than we realized.
+ 1. Getting a first release out – we are still inhibited by Hibernate issues
- 2. Moving the community from the Mifos infrastructure to the Apache infrastructure – most discussions are taking place out of public view.
- 3. Resolving the questions around introduction of a rework of the original code – in particular repository/infrastructure/release questions which result from the microservice architecture.
+ which are more deeply rooted than we realized.
+ 2. Moving the community from the Mifos infrastructure to the Apache
+ infrastructure – most discussions are taking place out of public view.
+ 3. Resolving the questions around introduction of a rework of the original
+ code – in particular repository/infrastructure/release questions which
+ result from the microservice architecture.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- The person who creates and submits the board reports will cease to perform this task until the code rework is ready to be introduced to the community. It is possible that this will endanger the board reports.
+ The person who creates and submits the board reports will cease to perform
+ this task until the code rework is ready to be introduced to the community.
+ It is possible that this will endanger the board reports.
-
- How has the community developed since the last report?
-
- Several prospective new committers have recently joined the Mifos community through Google Summer of Code and as new partners that we are working to add as committers to the Apache Fineract.
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
- We have tried and failed to produce an apache release again. A release was produced by the mifos community outside of apache and announced on the apache fineract user list.
+ Several prospective new committers have recently joined the Mifos community
+ through Google Summer of Code and as new partners that we are working to
+ add as committers to the Apache Fineract.
- The release included work intended to move us closer to apache policies. In particular, the removal of Hibernate annotations from the code uncovered a circular dependency in the data structure which was not caught in testing. Two production systems from early adopters are out-of-service today.
+ How has the project developed since the last report?
+
+ We have tried and failed to produce an apache release again. A release was
+ produced by the mifos community outside of apache and announced on the
+ apache fineract user list.
+
+ The release included work intended to move us closer to apache policies.
+ In particular, the removal of Hibernate annotations from the code uncovered
+ a circular dependency in the data structure which was not caught in
+ testing. Two production systems from early adopters are out-of-service
+ today.
Date of last release:
@@ -581, +602 @@
When were the last committers or PMC members elected?
- Jim Jagielski was added as a mentor.
+ Jim Jagielski was added as a mentor.
Signed-off-by:
@@ -620, +641 @@
How has the project developed since the last report?
We released Apache Gearpump 0.8.1-incubating, which is Gearpump's first
- release as an Apache incubator project.
+ release as an Apache incubator project.
Integration within Apache Beam (Gearpump Runner) has been merged into a
- feature branch.
+ feature branch.
Continued integration within akka-streams (Gearpump Materializer). Three
- PRs committed.
+ PRs committed.
28 issues created and 18 resolved.
@@ -636, +657 @@
When were the last committers or PMC members elected?
- No new committers or PMC members elected yet.
+ No new committers or PMC members elected yet.
Signed-off-by:
@@ -648, +669 @@
Shepherd/Mentor notes:
- Justin Mclean: PPMC are looking for additional mentors.
+ Justin Mclean: PPMC are looking for additional mentors.
--------------------
HTrace
- Apache HTrace is a tracing framework intended for use with distributed systems
+ Apache HTrace is a tracing framework intended for use with distributed
- written in java.
+ systems written in java.
Apache HTrace has been incubating since 2014-11-11.
@@ -662, +683 @@
1. Continue to grow the Apache HTrace community
2. Continue to explore projects integrating Apache HTrace
- 3. Continue to develop and release stable Apache HTrace incubating artifacts
+ 3. Continue to develop and release stable Apache HTrace incubating
+ artifacts
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -671, +693 @@
How has the community developed since the last report?
- * The dev@htrace mailing list continues to see new comers which is great.
+ * The dev@htrace mailing list continues to see new comers which is great.
- * Although a GSoC-related project was not successfully completed, the
+ * Although a GSoC-related project was not successfully completed, the
- Apache Kudu and Apache HTrace communities have made contact. This is
+ Apache Kudu and Apache HTrace communities have made contact. This is
- part of the drive to have more projects integrate Apache HTrace.
+ part of the drive to have more projects integrate Apache HTrace.
How has the project developed since the last report?
- * A discussion thread is currently ongoing to release HTrace 4.2. This
+ * A discussion thread is currently ongoing to release HTrace 4.2. This
- will include over 40 issues addressed and may even be our last incubating
+ will include over 40 issues addressed and may even be our last incubating
- release before we attempt to graduate.
+ release before we attempt to graduate.
Date of last release:
@@ -689, +711 @@
When were the last committers or PMC members elected?
* None this period. Last added committer: Abraham Elmahrek - 2.11.15
-
Signed-off-by:
@@ -716, +737 @@
Three most important issues to address in the move towards graduation:
1. Build up community with non-IBM and non-Salesforce contributors.
- 2. Release a version of the product to spark external interest in the project.
+ 2. Release a version of the product to spark external interest in the
+ project.
3. Need to determine where built libraries will be hosted for download.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -759, +781 @@
--------------------
log4cxx2
- Logging for C++. N.B. This is a reboot of the Log4cxx podling which previously
+ Logging for C++. N.B. This is a reboot of the Log4cxx podling which
- graduated.
+ previously graduated.
log4cxx2 has been incubating since 2013-12-09.
@@ -778, +800 @@
release happened since then.
There was a discussion about some kind of "maintenance mode" where releases
- and community growth doesn't matter much. As that mode doesn't exist, it has
+ and community growth doesn't matter much. As that mode doesn't exist, it
- been suggested to release, graduate from incubator and just live along other
+ has been suggested to release, graduate from incubator and just live along
- logging projects and in a comparable state like log4cxx.
+ other logging projects and in a comparable state like log4cxx.
- Currently it seems that there's only one official project member with commit
+ Currently it seems that there's only one official project member with
- access left answering mails. Even though that member and some contributors
+ commit access left answering mails. Even though that member and some
- worked on being able to create a release in the past, contrary to
+ contributors worked on being able to create a release in the past, contrary
- expectations that project member didn't find the time to deal with a release
+ to expectations that project member didn't find the time to deal with a
- as necessary.
+ release as necessary.
It seems most likely that if a release doesn't happen until the next report
is due, it won't at all anymore. At least not by that one left member.
How has the community developed since the last report?
- One new contributor took quite some time to look and fix the release process.
+ One new contributor took quite some time to look and fix the release
- Two support mails from users, no new project members.
+ process. Two support mails from users, no new project members.
How has the project developed since the last report?
@@ -824, +846 @@
--------------------
Mnemonic
- Apache Mnemonic is an advanced hybrid memory storage oriented library, we've proposed a non-volatile/durable
+ Apache Mnemonic is an advanced hybrid memory storage oriented library, we've
- Java object model and durable computing service that bring several advantages to significantly
+ proposed a non-volatile/durable Java object model and durable computing
+ service that bring several advantages to significantly improve the
- improve the performance of massive real-time data processing/analytics. developers are able
+ performance of massive real-time data processing/analytics. developers are
- to use this library to design their cache-less and SerDe-less high performance applications.
+ able to use this library to design their cache-less and SerDe-less high
+ performance applications.
Three most important issues to address in the move towards graduation:
1. Apache releases: we have release version 0.2.0-incubating
2. Encouraging community participation and contribution
- 3. Invented Durable Computing Model and Service on top of Durable Object Model
+ 3. Invented Durable Computing Model and Service on top of Durable Object
+ Model
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -844, +869 @@
Our last report was in April. Since then
- * Twelve new contributors have joined and seven contributors have submitted their patches.
+ * Twelve new contributors have joined and seven contributors have submitted
+ their patches.
* We need to encourage more discussion on the dev list in the coming months
How has the project developed since the last report?
@@ -891, +917 @@
Three most important issues to address in the move towards graduation:
1. Increase the number of active committers
- 2. Increase adoption, expand user community, and increase user list activity
+ 2. Increase adoption, expand user community, and increase user list
+ activity
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No
+ No
How has the community developed since the last report?
- There were no new developers or new committers since our last report.
+ There were no new developers or new committers since our last report.
- There are two UTA students who are developing code for the MRQL
+ There are two UTA students who are developing code for the MRQL project as
+ part of their Master's thesis, but they have not participated in the MRQL
+ community yet. One is working on implementing MRQL streaming with Apache
+ Storm and he is scheduled to complete it by the end of the year. The other
+ student is working on MRQL data visualization.
- project as part of their Master's thesis, but they have not
- participated in the MRQL community yet. One is working on implementing
- MRQL streaming with Apache Storm and he is scheduled to complete it by
- the end of the year. The other student is working on MRQL data
- visualization.
How has the project developed since the last report?
- There were 8 JIRA issues reported from which 6 have already been
+ There were 8 JIRA issues reported from which 6 have already been resolved.
- resolved. The main work during this period was on algebra-based and
+ The main work during this period was on algebra-based and source-level
- source-level debugging of MRQL queries. Basically, MRQL query results
+ debugging of MRQL queries. Basically, MRQL query results are annotated
- are annotated with lineage information that links each result value
+ with lineage information that links each result value with the input data
+ that were used to calculate the value. We hope that this debugger will be
+ a valuable tool for developing and understanding MRQL queries.
- with the input data that were used to calculate the value. We hope
- that this debugger will be a valuable tool for developing and
- understanding MRQL queries.
Date of last release:
@@ -938, +963 @@
--------------------
Myriad
- Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on
+ Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
- the same cluster and allows dynamic resource allocations across both Hadoop
+ on the same cluster and allows dynamic resource allocations across both
- and other applications running on the same physical data center
+ Hadoop and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
@@ -954, +979 @@
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None.
+ None.
How has the community developed since the last report?
- * dev@ mailing list picked up traffic (153 messages in June) around the 0.2.0 release. 236 messages since the last report.
+ * dev@ mailing list picked up traffic (153 messages in June) around the
+ 0.2.0 release. 236 messages since the last report.
- * 6 new members on the dev@ mailing list. 3 new patch contributors.
+ * 6 new members on the dev@ mailing list. 3 new patch contributors.
- * Bi-weekly dev syncs with 2-5 participants. Some cancelled due to lack of attendance. Minutes at http://s.apache.org/8kF
+ * Bi-weekly dev syncs with 2-5 participants. Some cancelled due to lack of
+ attendance. Minutes at http://s.apache.org/8kF
- * Myriad to be presented at HadoopWorld/Strata NYC and a talk submitted for ApacheCon BigData EU.
+ * Myriad to be presented at HadoopWorld/Strata NYC and a talk submitted for
+ ApacheCon BigData EU.
How has the project developed since the last report?
- * Myriad 0.2.0 released. Myriad 0.3.0 in development/planning.
+ * Myriad 0.2.0 released. Myriad 0.3.0 in development/planning.
- * 10 commits since 6/1. 8 JIRAs resolved.
+ * 10 commits since 6/1. 8 JIRAs resolved.
Date of last release:
@@ -1001, +1029 @@
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
- 3. Get positive feedback from other projects currently integrating/using Omid.
+ 3. Get positive feedback from other projects currently integrating/using
+ Omid.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- N/A
+ N/A
How has the community developed since the last report?
- * Omid presented at Hadoop Summit 2016 in San Jose. Some attendants manifested
+ * Omid presented at Hadoop Summit 2016 in San Jose. Some attendants
- interest and asked for future plans of integrating Omid with Apache Phoenix.
+ manifested interest and asked for future plans of integrating Omid with
+ Apache Phoenix.
- * First contact with Apache DistributedLog community for a possible integration
+ * First contact with Apache DistributedLog community for a possible
- with Omid.
+ integration with Omid.
- * Blog entry on Apache Omid ready to be published in Yahoo's hadoop blog site.
+ * Blog entry on Apache Omid ready to be published in Yahoo's hadoop blog
+ site.
* Quarter Stats (from: 2016-06-01 to: 2016-08-31):
+---------------------------------------------+
| Metric | counts |
@@ -1029, +1060 @@
How has the project developed since the last report?
- First version of Omid released under the Apache incubator program. It has also been
+ First version of Omid released under the Apache incubator program. It has
- integrated with the Apache Hive project.
+ also been integrated with the Apache Hive project.
Date of last release:
@@ -1038, +1069 @@
When were the last committers or PMC members elected?
- At incubation acceptance (2016-03-28)
+ At incubation acceptance (2016-03-28)
Signed-off-by:
@@ -1057, +1088 @@
Pirk is a framework for scalable Private Information Retrieval (PIR).
- Pirk has been incubating since 2016-06-17. The initial code for Pirk was granted on 2016-07-11.
+ Pirk has been incubating since 2016-06-17. The initial code for Pirk was
+ granted on 2016-07-11.
Three most important issues to address in the move towards graduation:
1. Grow the community to establish diversity of background and expertise.
-
- 2. Establish a formal release process and schedule, allowing for dependable release cycles in a manner consistent with the Apache development process.
-
+ 2. Establish a formal release process and schedule, allowing for dependable
+ release cycles in a manner consistent with the Apache development
+ process.
- 3. Add to and improve the Pirk user documentation and examples both on the website and in the codebase
+ 3. Add to and improve the Pirk user documentation and examples both on the
+ website and in the codebase
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None.
+ None.
- How has the community developed since the last report?
-
- We have officially welcomed two new committers (Tim Ellison and Suneel Marthi, both also mentors). The mailing list activity, pull requests, and page views to the Apache Pirk website (via Google Analytics) have also greatly increased since the last report.
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
- The project completed it's first release, 0.1.0-incubating, since the last report and provided a release guide on its website documenting the process. Additionally, the project has ensured that all dependencies are compliant with the Apache License version 2.0 and that all code and documentation artifacts have the correct Apache licensing markings and notice. The project has also undertaken a refactor of some of the initial packages and provided initial streaming implementations.
+ We have officially welcomed two new committers (Tim Ellison and Suneel
+ Marthi, both also mentors). The mailing list activity, pull requests, and
+ page views to the Apache Pirk website (via Google Analytics) have also
+ greatly increased since the last report.
+
+ How has the project developed since the last report?
+
+ The project completed it's first release, 0.1.0-incubating, since the last
+ report and provided a release guide on its website documenting the process.
+ Additionally, the project has ensured that all dependencies are compliant
+ with the Apache License version 2.0 and that all code and documentation
+ artifacts have the correct Apache licensing markings and notice. The
+ project has also undertaken a refactor of some of the initial packages and
+ provided initial streaming implementations.
Date of last release:
@@ -1086, +1128 @@
When were the last committers or PMC members elected?
- Pirk elected two new committers (Tim Ellison and Suneel Marthi, both mentors) on August 18, 2016.
+ Pirk elected two new committers (Tim Ellison and Suneel Marthi, both
+ mentors) on August 18, 2016.
Signed-off-by:
@@ -1119, +1162 @@
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
+ None
-
How has the community developed since the last report?
- Slight uptick in active members of the community, we now count roughly 10 active people
+ Slight uptick in active members of the community, we now count roughly 10
- participating either on the mailing list or IRC.
+ active people participating either on the mailing list or IRC.
How has the project developed since the last report?
- Work has begun on a redesign of the UI, allowing for contributions more easily.
+ Work has begun on a redesign of the UI, allowing for contributions more
- This is codenamed 'coffee and cake', and is expected to reach a usable phase in
+ easily. This is codenamed 'coffee and cake', and is expected to reach a
- a month or two.
+ usable phase in a month or two.
Date of last release:
@@ -1139, +1181 @@
When were the last committers or PMC members elected?
- None since inception. See graduation info point 1.
+ None since inception. See graduation info point 1. The codebase needs to
- The codebase needs to be more accessible before contributions can occur.
+ be more accessible before contributions can occur.
Signed-off-by:
@@ -1159, +1201 @@
production-ready predictive services for various kinds of machine learning
tasks.
- PredictionIO has been incubating since 2016-05-26. The initial code for PredictionIO was
+ PredictionIO has been incubating since 2016-05-26. The initial code for
- granted on 2016-06-16. A second grant of PredictionIO Templates is in the works and anticipated to be complete in September 2016.
+ PredictionIO was granted on 2016-06-16. A second grant of PredictionIO
+ Templates is in the works and anticipated to be complete in September 2016.
Three most important issues to address in the move towards graduation:
- 1. Establish a formal release schedule and process, allowing for dependable release cycles in a manner consistent with the Apache way.
+ 1. Establish a formal release schedule and process, allowing for dependable
+ release cycles in a manner consistent with the Apache way.
2. Grow the community to establish diversity of background.
- 3. Transition remaining former PredictionIO users from google-groups to ASF mailing lists.
+ 3. Transition remaining former PredictionIO users from google-groups to ASF
+ mailing lists.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
+ None
How has the community developed since the last report?
- 1. Users have begun to migrate from the old Google group to the Apache user list
+ 1. Users have begun to migrate from the old Google group to the Apache user
+ list
- 2. Three new contributors have become active and have been making consistently acceptable contributions
+ 2. Three new contributors have become active and have been making
- and are on path to becoming committers.
+ consistently acceptable contributions and are on path to becoming
+ committers.
How has the project developed since the last report?
- 1. The old Prediction.io docs site has been migrated to http://predictionio.incubator.apache.org
+ 1. The old Prediction.io docs site has been migrated to
+ http://predictionio.incubator.apache.org
- 2. About seven templates from the original PredictionIO have been ported to Apache PredictionIO,
+ 2. About seven templates from the original PredictionIO have been ported to
- pending a decision on a 2nd grant. The pending 2nd grant will not block a PredictionIO release.
+ Apache PredictionIO, pending a decision on a 2nd grant. The pending 2nd
+ grant will not block a PredictionIO release.
Date of last release:
- No releases have been made yet. Present activities are focussed towards a planned first Apache Release in September 2016.
+ No releases have been made yet. Present activities are focussed towards a
+ planned first Apache Release in September 2016.
When were the last committers or PMC members elected?
- Paul Li was elected as committer and PMC member on Aug 30, 2016.
+ Paul Li was elected as committer and PMC member on Aug 30, 2016.
Signed-off-by:
@@ -1253, +1303 @@
--------------------
Ranger
- The Ranger project is a framework to enable, monitor and manage comprehensive data security across the Hadoop platform.
+ The Ranger project is a framework to enable, monitor and manage comprehensive
+ data security across the Hadoop platform.
Ranger has been incubating since 2014-07-24.
Three most important issues to address in the move towards graduation:
1. Increase the community participants for Apache Ranger
- 2. Re-organize documentation for easier access to end-users, new users and contributors.
+ 2. Re-organize documentation for easier access to end-users, new users and
+ contributors.
3. Integration of Apache Ranger with other Apache Initiatives
- Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+ 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?
@@ -1280, +1334 @@
3. Adding more community members to involve in Apache Ranger
* Added new contributors: Suneel Marthi
- * Apache Hawq community is working with Ranger to build a authorization engine for Apache Hawq (RANGER-782)
+ * Apache Hawq community is working with Ranger to build a
+ authorization engine for Apache Hawq (RANGER-782)
How has the project developed since the last report?
@@ -1294, +1349 @@
a. Working on scoping of the release and features
Date of last release:
+
August-20-2016
When were the last committers or PMC members elected?
+
1. Gautam Borad has been added as committer on June-29-2015
Signed-off-by:
@@ -1307, +1364 @@
[X](ranger) Jakob Homan
[ ](ranger) Owen O'Malley
-
Shepherd/Mentor notes:
@@ -1317, +1373 @@
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
+ clustering, and regression, as well as programming abstractions to develop
- algorithms that run on top of distributed stream processing engines (DSPEs).
+ new algorithms that run on top of distributed stream processing engines
- It features a pluggable architecture that allows it to run on several DSPEs
+ (DSPEs). It features a pluggable architecture that allows it to run on
- such as Apache Storm, Apache S4, and Apache Samza.
+ several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
SAMOA has been incubating since 2014-12-15.
@@ -1349, +1405 @@
How has the project developed since the last report?
We have been preparing a second release of the project, which was delayed
- due to some minor issues in the RC and then the summer break for most developers.
+ due to some minor issues in the RC and then the summer break for most
-
+ developers.
Date of last release:
@@ -1384, +1440 @@
to the user community
2. Completing the initial build on our website(s) (in progress)
3. Consolidating our Quick Start deployment guides on Apache infrastructure
- (Confluence, website) that allow for an end-to-end deployment of data collection
+ (Confluence, website) that allow for an end-to-end deployment of data
- services with containers for assets (Docker Images) for speedy deployment (in progress)
+ collection services with containers for assets (Docker Images) for
+ speedy deployment (in progress)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No
+ No
How has the community developed since the last report?
- 1. Community members have been working with DoD and Industry partners to bring
+ 1. Community members have been working with DoD and Industry partners to
- them on as contributors to the project (ex. Other industry leaders in HCI/UX
+ bring them on as contributors to the project (ex. Other industry leaders
- offerings for DoD have begun offering SensSoft products as part of their
+ in HCI/UX offerings for DoD have begun offering SensSoft products as
- technical offerings).
+ part of their technical offerings).
2. The community has established a Twitter feed (@ApacheSensSoft) and are
growing our community by following others (e.g., Kitware, etc.)
3. Community members from Draper Labs have made arrangements to present at
- uie21 and the emetrics summit as exhibitors to capture community followers
+ uie21 and the emetrics summit as exhibitors to capture community
- in the UI/UX and business analytics communities.
+ followers in the UI/UX and business analytics communities.
How has the project developed since the last report?
1. The transition to Apache Infrastructure is complete!!!
2. We have moved over all our development tickets into Apache Jira. All
development is now taking place @Apache which is great.
- 3. We are working on new patches and version releases for TAP, UserAle.js, Distill
+ 3. We are working on new patches and version releases for TAP, UserAle.js,
- products (sub projects under SENSSOFT), which will now be visible through commits.
+ Distill products (sub projects under SENSSOFT), which will now be
+ visible through commits.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- N/A
+ N/A
Signed-off-by:
@@ -1446, +1504 @@
Singa has been incubating since 2015-03-17.
Three most important issues to address in the move towards graduation:
+
- 1. Grow the community. One committer was added in July, more would be nominated soon after releasing V1.0.
+ 1. Grow the community. One committer was added in July, more would be
+ nominated soon after releasing V1.0. We are also expanding the user
- We are also expanding the user base by participating in meetups of local organizations, including PyDataSG.
+ base by participating in meetups of local organizations, including
- 2. Optimize V1 release in terms of memory and efficiency for both stand-alone training and distributed training.
+ PyDataSG.
+ 2. Optimize V1 release in terms of memory and efficiency for both
+ stand-alone training and distributed training.
- 3. Add more examples and tutorials to attract users, including deployment on Android phones.
+ 3. Add more examples and tutorials to attract users, including deployment
+ on Android phones.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No
+ No
-
- How has the community developed since the last report?
-
- There were 187, 100 and 69 emails from dev@ list in June 2016, July 2016 and August 2016 respectively.
- The number of commits has increased 50% (about 200 commits) since last report.
- One new committer was added.
-
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
+ There were 187, 100 and 69 emails from dev@ list in June 2016, July 2016
+ and August 2016 respectively. The number of commits has increased 50%
+ (about 200 commits) since last report. One new committer was added.
+
+ How has the project developed since the last report?
+
- We have been working on V1.0 since the last release. The vote for releasing V1.0 has been sent to the general mailing list.
+ We have been working on V1.0 since the last release. The vote for releasing
+ V1.0 has been sent to the general mailing list.
- The new version has major improvements in term of programming abstraction and usability. Some features are listed here,
+ The new version has major improvements in term of programming abstraction
+ and usability. Some features are listed here,
+
- * Support heterogeneous hardware: CPP for CPU, CUDA for Nvidia GPU, OpenCL for other devices (including AMD GPUs)
+ * Support heterogeneous hardware: CPP for CPU, CUDA for Nvidia GPU, OpenCL
+ for other devices (including AMD GPUs)
* New programming abstractions supporting complex deep learning models
* Re-write the Python binding and provide running examples
* Cross-platform (Linux and Mac OSX)
@@ -1509, +1574 @@
1. Community growth and PMC maturity.
2. Demonstrate a consistent release schedule.
- 3. Participation of project community within related standards-bodies and Apache projects.
+ 3. Participation of project community within related standards-bodies and
+ Apache projects.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -1533, +1599 @@
When were the last committers or PMC members elected?
2015-02-23: Robert Douglas elected as committer / PMC member
-
Signed-off-by:
@@ -1542, +1607 @@
[ ](streams) Craig McClanahan
Shepherd/Mentor notes:
+
[Ate Douma] As indicated in the report, the activity and community
of the project has dwindled down to practically zero.
As a consequence I've now raised the question on the dev list if
@@ -1549, +1615 @@
activity and interest from the community, I expect an actual vote
to retire before the next board report.
-
--------------------
Tamaya
@@ -1614, +1679 @@
2. Complete IP/license review of unreleased repositories
3. Further engaging user/devops community
-
-
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Preparing to graduate.
-
-
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
@@ -1644, +1705 @@
We have however identified the need for a License Review of the remaining
git repositories that have not yet been formally released through the
- Apache Incubator (e.g. to ensure ASF file headers), which we are now completing:
+ Apache Incubator (e.g. to ensure ASF file headers), which we are now
+ completing:
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review
- We might consider not including all of these repositories as we move towards
+ We might consider not including all of these repositories as we move
+ towards graduation - we already have an alternative home
+ https://github.com/taverna-extras for dormant extensions.
- graduation - we already have an alternative home https://github.com/taverna-extras
- for dormant extensions.
-
dev@taverna mailing lists stats:
@@ -1738, +1799 @@
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- - None at this time.
+ - None at this time.
How has the community developed since the last report?
- - 12 subscribers in dev mailing list
+ - 12 subscribers in dev mailing list
- - 5 new JIRAs filed since last report
+ - 5 new JIRAs filed since last report
- - 2 new contributors submitted patches
+ - 2 new contributors submitted patches
How has the project developed since the last report?
- - Working on 0.9.0 release
+ - Working on 0.9.0 release
Date of last release:
@@ -1756, +1817 @@
When were the last committers or PMC members elected?
- - None since coming to incubation
+ - None since coming to incubation
Signed-off-by:
@@ -1782, +1843 @@
Three most important issues to address in the move towards graduation:
- 1. Resolve LGPL dependency: Great news! The team has just merged a PR and removed the LGPL license in favor of MPL (https://github.com/zeromq/jeromq/pull/358)
+ 1. Resolve LGPL dependency: Great news! The team has just merged a PR and
+ removed the LGPL license in favor of MPL
+ (https://github.com/zeromq/jeromq/pull/358)
- 2. Make a release: 0.1.x branch should be ready for release. Master has moved to start support for Spark 2.0
+ 2. Make a release: 0.1.x branch should be ready for release. Master has
+ moved to start support for Spark 2.0
3. Grow a diverse community: We should put some emphasis on growing the
community and making it diverse (the rule is at least three independent
- contributors) We have 1 major independent contributor (mariusvniekerk) and at least 2 minor ones (https://github.com/apache/incubator-toree/graphs/contributors)
+ contributors) We have 1 major independent contributor (mariusvniekerk)
+ and at least 2 minor ones
+ (https://github.com/apache/incubator-toree/graphs/contributors)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- TOREE-262 - Progress on removal of LGPL dependency - Awaiting MPL release of JeroMQ. Will update branches to remove caveats re: LGPL once the JeroMQ release is available.
+ TOREE-262 - Progress on removal of LGPL dependency - Awaiting MPL release
+ of JeroMQ. Will update branches to remove caveats re: LGPL once the JeroMQ
+ release is available.
How has the community developed since the last report?
@@ -1799, +1867 @@
2. Still working on transitioning users from Spark Kernel project into
Toree. Making significant progress here.
3. More external contributions being made. Community member 2mariusvniekerk
- key in porting Toree to work on Spark 2.0. Sitting on PR 56. Working with committer to finish up some details and will merge when ready. This is a significant contribution.
+ key in porting Toree to work on Spark 2.0. Sitting on PR 56. Working
+ with committer to finish up some details and will merge when ready. This
+ is a significant contribution.
How has the project developed since the last report?
@@ -1821, +1891 @@
[ ](toree) Hitesh Shah
[ ](toree) Julien Le Dem
-
--------------------
Traffic Control
@@ -1832, +1901 @@
Three most important issues to address in the move towards graduation:
- 1. Software grant from Comcast and others active in the current
+ 1. Software grant from Comcast and others active in the current
- github.com/Comcast project to ASF. Discussion between Comcast and ASF
+ github.com/Comcast project to ASF. Discussion between Comcast and ASF
- legal on-going, this is blocking all other progress.
+ legal on-going, this is blocking all other progress.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- See above issue 1.
+ See above issue 1.
How has the community developed since the last report?
- Established apache.org accounts for all of the initial committers.
+ Established apache.org accounts for all of the initial committers.
How has the project developed since the last report?
- - Setup git repo and mailing lists.
+ - Setup git repo and mailing lists.
- - Started Software Grant process.
+ - Started Software Grant process.
Date of last release:
- We released 1.6.0 on 2016-07-29 under the old process, because the release
+ We released 1.6.0 on 2016-07-29 under the old process, because the release
- process (candidates and votes) had already started before our official
+ process (candidates and votes) had already started before our official
- entry in the incubator. We have started release 1.7.0 under the old process
+ entry in the incubator. We have started release 1.7.0 under the old process
- as well, since we don't have the necessary ASF infrastructure in place, and
+ as well, since we don't have the necessary ASF infrastructure in place, and
- this is pending the SGA.
+ this is pending the SGA.
When were the last committers or PMC members elected?
- 2016-07-12 - initial committer list.
+ 2016-07-12 - initial committer list.
Signed-off-by:
@@ -1962, +2031 @@
None.
-
How has the community developed since the last report?
- - We have ongoing community discussion about how to bring in new developers to
+ - We have ongoing community discussion about how to bring in new developers
- ensure sustainability of the project.
+ to ensure sustainability of the project.
+
- A votation session has been scheduled (Sept 28th) to decide if Wave's fork
+ A votation session has been scheduled (Sept 28th) to decide if Wave's fork
- Swellrt is brought/merged into Wave. This would bring SwellRT active
+ Swellrt is brought/merged into Wave. This would bring SwellRT active
- developers into Wave and it could facilitate use of Wave by new developers
+ developers into Wave and it could facilitate use of Wave by new developers
- thanks to a new API, removing GWT legacy code.
+ thanks to a new API, removing GWT legacy code.
How has the project developed since the last report?
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org