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/05/08 15:37:07 UTC
[Incubator Wiki] Update of "May2016" by MarvinHumphrey
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.
The "May2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/May2016?action=diff&rev1=63&rev2=64
Comment:
Reflow, add bullets.
* Infrastructure
- - Kudos to the infra team for assisting with troubleshooting the new Marvin Jr. Podling reminder email script.
+ - Kudos to the infra team for assisting with troubleshooting the new
+ Marvin Jr. Podling reminder email script.
* Miscellaneous
@@ -112, +113 @@
* Still getting started at the Incubator
- Airflow
+ - Airflow
- Beam
+ - Beam
- Gearpump
+ - Gearpump
- Mnemonic
+ - Mnemonic
- Quickstep
+ - Quickstep
- Tephra
+ - Tephra
* Not yet ready to graduate
No release:
- Fineract
+ - Fineract
- Guacamole
+ - Guacamole
- S2Graph
+ - S2Graph
- Toree
+ - Toree
Community growth:
- Blur
+ - Blur
- Eagle
+ - Eagle
- Joshua
+ - Joshua
- Kudu
+ - Kudu
- OpenAz
+ - OpenAz
- Quarks
+ - Quarks
- Slider
+ - Slider
- SystemML
+ - SystemML
- Tamaya
+ - Tamaya
- TinkerPop
+ - TinkerPop
- Twill
+ - Twill
- Unomi
+ - Unomi
-
* Ready to graduate
@@ -153, +153 @@
* Did not report, expected next month
- Climate Model Diagnostic Analyzer
+ - Climate Model Diagnostic Analyzer
- iota
+ - iota
-
----------------------------------------------------------------------
Table of Contents
@@ -331, +330 @@
How has the project developed since the last report?
- Software bug fixes and performance enhancements.
- - An announcement was made of a production release of Apache Blur (very cool!)
+ - An announcement was made of a production release of Apache Blur (very
+ cool!)
http://mail-archives.apache.org/mod_mbox/incubator-blur-user/201604.mbox/%3CCAGW2whTUEFLYCUeyAdT3_KH9FczdrBJ6SLV3YMuuSA-4XBfR%3DA%40mail.gmail.com%3E
Date of last release:
@@ -484, +484 @@
Three most important issues to address in the move towards graduation:
- 1. Finalizing the initial release
+ 1. Finalizing the initial release
- 2. Addressing with the VP of Legal our Hibernate dependency and how to remedy (removal, exception, etc.)
+ 2. Addressing with the VP of Legal our Hibernate dependency and how to
- 3. Continue to encourage participation in Fineract collaboration and communication infrastructure by bringing offline interactions online and directing collaboration to occur in right channels.
+ remedy (removal, exception, etc.)
+ 3. Continue to encourage participation in Fineract collaboration and
+ communication infrastructure by bringing offline interactions online
+ and directing collaboration to occur in right channels.
- 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
+ None
How has the community developed since the last report?
- Participated in and selected one intern for Google Summer of Code working on the India Unified Payments Interface.
- Community members attended LinuxFest Northwest in Bellingham, WA and encouraged developers to get involved in the Apache Fineract community.
- Discussion of requirements is taking place via mailing lists for major enhancements community is anticipating over next quarter.
+ - Participated in and selected one intern for Google Summer of Code
+ working on the India Unified Payments Interface.
+ - Community members attended LinuxFest Northwest in Bellingham, WA and
+ encouraged developers to get involved in the Apache Fineract community.
+ - Discussion of requirements is taking place via mailing lists for major
+ enhancements community is anticipating over next quarter.
How has the project developed since the last report?
- More communications are happening on the appropriate lists as we have been directing conversations to happen in the public mailing lists and outside of previous community silos.
+ More communications are happening on the appropriate lists as we have been
+ directing conversations to happen in the public mailing lists and outside
+ of previous community silos.
Date of last release:
- N/A
+ N/A
When were the last committers or PMC members elected?
- N/A
+ N/A
Shepherd/Mentor notes:
@@ -534, +543 @@
How has the community developed since the last report?
- High amount of activity and discussion on dev mailing list (april 604)
+ - High amount of activity and discussion on dev mailing list (april 604)
- Increased participation and interest from developers to provide new sources and examples
+ - Increased participation and interest from developers to provide new
+ sources and examples
How has the project developed since the last report?
- All outstanding issues from old github repo have been reopened as JIRAs.
+ - All outstanding issues from old github repo have been reopened as JIRAs.
- All prior merges in old repo have been converted to PR's and merged to master within apache gearpump repo.
+ - All prior merges in old repo have been converted to PR's and merged to
+ master within apache gearpump repo.
- Branded apache website is completed and reviewed. Publishing to https://s.apache.org/T86l
+ - Branded apache website is completed and reviewed. Publishing to
+ https://s.apache.org/T86l
- INFRA tickets required to publish to repository.apache.org completed, travis build scripts updated
+ - INFRA tickets required to publish to repository.apache.org completed,
+ travis build scripts updated
Date of last release:
@@ -626, +639 @@
Shepherd/Mentor notes:
- jbonofre: Frode's account should be OK now. For the Jira, the difficulty was that the project wanted to import existing Jira content. Not sure it's a good idea as bunch of users don't exist in the Apache Jira and there's lot of "noise". I would recommend to start by creating the highest priority tasks and issues in the Apache Jira.
+ Jean-Baptiste Onofre (jbonofre):
+
+ Frode's account should be OK now. For the Jira, the difficulty was that
+ the project wanted to import existing Jira content. Not sure it's a good
+ idea as bunch of users don't exist in the Apache Jira and there's lot of
+ "noise". I would recommend to start by creating the highest priority
+ tasks and issues in the Apache Jira.
--------------------
@@ -691, +710 @@
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?
-
- Joshua is being represented at ApacheCon. Currently one
- presentation is taking place in addition to a meetup.
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
+ Joshua is being represented at ApacheCon. Currently one presentation is
+ taking place in addition to a meetup.
+
+ How has the project developed since the last report?
+
- The project team have been working on development code
+ The project team have been working on development code as well as official
+ branding. All infrastructure has been migrated over to Apache. We are
+ aiming for our first release some time after ApacheCon.
- as well as official branding. All infrastructure has been
- migrated over to Apache. We are aiming for our first release
- some time after ApacheCon.
Date of last release:
@@ -711, +729 @@
When were the last committers or PMC members elected?
- Kellen Sunderland and Felix Hieber joined the PPMC and
+ Kellen Sunderland and Felix Hieber joined the PPMC and as committers on
- as committers on April 11th, 2016.
+ April 11th, 2016.
Signed-off-by:
@@ -743, +761 @@
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 PPMC invited Binglin Chang as a new committer and PPMC member. Binglin
- has continued to increase his involvement and some of his colleagues are now
+ has continued to increase his involvement and some of his colleagues are
- becoming more involved as well.
+ now becoming more involved as well.
Since the last report, we had contributions from several new contributors,
including five new contributors from outside Cloudera (the initial code
- grantor). Of those, two were substantial pieces of new functionality: a new
+ grantor). Of those, two were substantial pieces of new functionality: a
- sink to ingest data from Apache Flume, and an improved integration with
+ new sink to ingest data from Apache Flume, and an improved integration
- Apache Spark. We hope that the authors of these contributions will continue
+ with Apache Spark. We hope that the authors of these contributions will
- to be involved in the community and grow into committers.
+ continue to be involved in the community and grow into committers.
- In March, one of our mentors approached the development community with some
+ In March, one of our mentors approached the development community with
- ideas to make the project more approachable for developers. As a result
+ some ideas to make the project more approachable for developers. As a
- of this, we've been working on a few action items:
+ result of this, we've been working on a few action items:
- 1) We started a project blog and have been posting weekly updates on development
+ 1) We started a project blog and have been posting weekly updates on
- progress as well as more detailed posts on new features or project news.
+ development progress as well as more detailed posts on new features or
- We've heard from community members that this is an easy way to track
+ project news. We've heard from community members that this is an easy
- the project without subscribing to high-volume dev lists.
+ way to track the project without subscribing to high-volume dev lists.
- 2) Our dev@ list is currently very noisy with a lot of code review comments.
+ 2) Our dev@ list is currently very noisy with a lot of code review
- For more casual contributors this can be overwhelming as code review
+ comments. For more casual contributors this can be overwhelming as
- is intermingled with higher level project discussions. The community
+ code review is intermingled with higher level project discussions. The
- discussed the issue and decided to split the code review traffic to a new
+ community discussed the issue and decided to split the code review
- mailing list (currently awaiting infra to create it)
+ traffic to a new mailing list (currently awaiting infra to create it)
- 3) We've started an informal policy of emailing the dev list with a heads-up
+ 3) We've started an informal policy of emailing the dev list with a
- whenever any new larger feature first shows up on gerrit or JIRA, to make it
+ heads-up whenever any new larger feature first shows up on gerrit or
- easier for people to give input on large items without having to see every
- bug fix or small improvement. For example, whenever design discussion starts
- on a new feature, the contributor sends a 'heads-up' email to dev@.
+ JIRA, to make it easier for people to give input on large items without
+ having to see every bug fix or small improvement. For example, whenever
+ design discussion starts on a new feature, the contributor sends a
+ 'heads-up' email to dev@.
Development activity continues to be healthy. Mailing list traffic for the
dev list in April and May was similar to the preceding months. Patch
contribution level is also fairly stable (50-80 commits/month) with lulls
around releases as people focus on release testing, documentation, etc.
- User mailing list traffic is steadily increasing in quantity and diversity:
+ User mailing list traffic is steadily increasing in quantity and
- 108 messages in April vs 51 in March, 40 in Feb. April saw 26 distinct people
+ diversity: 108 messages in April vs 51 in March, 40 in Feb. April saw 26
- contribute to the user list discussion vs 15 in Feb. Website traffic also
- indicates growing interest, with April having 30% more traffic than Feb.
+ distinct people contribute to the user list discussion vs 15 in Feb.
+ Website traffic also indicates growing interest, with April having 30%
+ more traffic than Feb.
- In the last two months, Kudu-related talks were delivered in San Francisco,
+ In the last two months, Kudu-related talks were delivered in San
- San Jose, Beijing, Boston, DC, Detroit, London, and Dublin. More talks
+ Francisco, San Jose, Beijing, Boston, DC, Detroit, London, and Dublin.
- are scheduled for the upcoming months at ApacheCon Big Data, Strata/Hadoop World,
+ More talks are scheduled for the upcoming months at ApacheCon Big Data,
- Berlin Buzzwords, and various local meetups.
+ Strata/Hadoop World, Berlin Buzzwords, and various local meetups.
-
How has the project developed since the last report?
Since the last report, we've accomplished the following milestones:
- We released Apache Kudu 0.7.1-incubating on 3/9/2016 to fix a few issues
- found in the 0.7.0 release.
+ found in the 0.7.0 release.
- We released Apache Kudu 0.8.0-incubating on 4/10/2016 with various new
- features and improvements.
+ features and improvements.
-
Date of last release:
April 10, 2016: Apache Kudu 0.8.0-incubating
-
When were the last committers or PMC members elected?
- Binglin Chang was added as a committer and PPMC member on April 4, 2016.
-
Signed-off-by:
@@ -856, +871 @@
Three most important issues to address in the move towards graduation:
1. Apache releases: we are preparing 0.1.0 release
- 2. Expand and build strong community, keep active dev list discussions, adding new contributors
+ 2. Expand and build strong community, keep active dev list discussions,
+ adding new contributors
- a. Mnemonic website is up: http://mnemonic.incubator.apache.org/
+ a. Mnemonic website is up: http://mnemonic.incubator.apache.org/
+ b. Mnemonic cwiki is up:
- b. Mnemonic cwiki is up: https://cwiki.apache.org/confluence/display/MNEMONIC/Apache+Mnemonic+Home
+ https://cwiki.apache.org/confluence/display/MNEMONIC/Apache+Mnemonic+Home
3. Develop new features: We are working in Native computing layer design.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -868, +885 @@
How has the community developed since the last report?
- 1. We completed setting up infrastructure. Both project website and cwiki are up running. We are working on adding contents and documentation to the sites so new contributors and community members can get better view of what this project is and how to get involved.
- 2. We realized, unlike other application level projects, library (or API) projects traditionally had less contributors until certain amount of adopters successfully integrated those libraries. We plan to help some integrations, such as HBase, Arrow, etc. after our first official code release.
+ 1. We completed setting up infrastructure. Both project website and cwiki
+ are up running. We are working on adding contents and documentation to
+ the sites so new contributors and community members can get better view
+ of what this project is and how to get involved.
+ 2. We realized, unlike other application level projects, library (or API)
+ projects traditionally had less contributors until certain amount of
+ adopters successfully integrated those libraries. We plan to help some
+ integrations, such as HBase, Arrow, etc. after our first official code
+ release.
3. We submitted 2 proposals for Strata Hadoop World NYC.
- 4. We will present Mnemonic project in upcoming ApacheCon Big Data conference on 5/11.
+ 4. We will present Mnemonic project in upcoming ApacheCon Big Data
+ conference on 5/11.
-
How has the project developed since the last report?
- We are designing the native computing infrastructure, built native computing interface code.
+ We are designing the native computing infrastructure, built native
+ computing interface code.
+
- In preparing first official release:
+ In preparing first official release:
+
- 1. Defined coding guidelines for the project. Reformatted all code based on defined coding style.
+ 1. Defined coding guidelines for the project. Reformatted all code based
+ on defined coding style.
2. Added the checkstyle to automate the checking process.
3. Formalized the names of annotations, classes and methods.
4. Removed the dependency of property mnemonic.core.version.
@@ -893, +921 @@
No election, since the project is still in early stage of developing.
-
Signed-off-by:
[X](mnemonic) Patrick Hunt
@@ -915, +942 @@
Three most important issues to address in the move towards graduation:
- 1. Increasing community involvement: We are focusing on getting information
+ 1. Increasing community involvement: We are focusing on getting
- published on the website to aid the acquisition and orientation of new
+ information published on the website to aid the acquisition and
- contributors, as well increasing the number of committers, in order to reduce individual
+ orientation of new contributors, as well increasing the number of
+ committers, in order to reduce individual member workload, reduce
- member workload, reduce reliance on any particular member, and to increase project
+ reliance on any particular member, and to increase project velocity.
- velocity.
2. Merging the source code from AT&T, JP Morgan and Oracle and creating
- POM's. AT&T and JP Morgan source code has been merged and POM's created,
+ POM's. AT&T and JP Morgan source code has been merged and POM's
- it needs uploading into the Apache repository.
+ created, it needs uploading into the Apache repository.
3. Get our first release done.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -947, +974 @@
How has the project developed since the last report?
We have merged in a port of the administrative portion of AT&T's
- contributed code, which was the last remaining piece of that code base. More work
+ contributed code, which was the last remaining piece of that code base.
- needs to be done on this front, but it's a major part of the code base and this
+ More work needs to be done on this front, but it's a major part of the
- is a good start toward making it happen.
+ code base and this is a good start toward making it happen.
We have also merged a fix for configuration and policy files, which
- updated class names and removed duplicate xml declarations from policy files.
+ updated class names and removed duplicate xml declarations from policy
+ files.
Date of last release:
@@ -964, +992 @@
We have several interested folks in working on the project:
- Yannick Grignon
+ - Yannick Grignon
- Farasath Ahamed
+ - Farasath Ahamed
- Inge Olaisen
+ - Inge Olaisen
- Carlos Perez
+ - Carlos Perez
- Remon Sinnema
+ - Remon Sinnema
Signed-off-by:
@@ -1038, +1066 @@
[X](quarks) Katherine Marsden
[ ](quarks) Justin Mclean
-
Shepherd/Mentor notes:
@@ -1094, +1121 @@
Most of the initial committers have submitted CLAs and joined the
mailing lists, and activity on the dev list is looking healthy.
-
--------------------
S2Graph
@@ -1117, +1143 @@
How has the community developed since the last report?
- * There has been concerns about s2graph community, and we have decided that committers in the same company will avoid face-to-face discussion and start out on the dev mailing list. we opened up 11 discussions on the dev mailing list afterwards.
+ * There has been concerns about s2graph community, and we have decided
+ that committers in the same company will avoid face-to-face discussion
+ and start out on the dev mailing list. we opened up 11 discussions on
+ the dev mailing list afterwards.
- * There are two new contributors, one is working on packaging and other is working on bug fix.
+ * There are two new contributors, one is working on packaging and other is
+ working on bug fix.
* We will present about Apache S2Graph in apache-big-data-north-america.
How has the project developed since the last report?
@@ -1126, +1156 @@
* We started out the discussion on first release plan and project road map.
* We opened up the discussion on the project logo.
* 45 issues are created, 31 issues are resolved, 34 commits merged.
- * We deprecated our old github repository under kakao and made it point to ASF github repository.
+ * We deprecated our old github repository under kakao and made it point to
+ ASF github repository.
Date of last release:
@@ -1253, +1284 @@
Our mailing list from February through April had 199 messages involving
topics such as algorithms, DML functionality, usability, and bug fixes. In
- addition, we have had many discussions on our JIRA site and in pull request
+ addition, we have had many discussions on our JIRA site and in pull
- conversations. Fred Reiss presented at Spark Summit East on February 17 about
+ request conversations. Fred Reiss presented at Spark Summit East on
- SystemML internals. Berthold Reinwald spoke at the Spark Technology Center on
- March 9 about scalable machine learning with SystemML. Niketan Pansare spoke
- on April 28 at Datapalooza in Austin and on April 29 at Rice University about
- declarative machine learning at scale with SystemML. Researchers in Germany
- are working to add Flink as an additional SystemML backend. On GitHub, the
- project has been starred 267 times and forked 92 times. We have gained two
- new contributors since February 1st.
+ February 17 about SystemML internals. Berthold Reinwald spoke at the Spark
+ Technology Center on March 9 about scalable machine learning with
+ SystemML. Niketan Pansare spoke on April 28 at Datapalooza in Austin and
+ on April 29 at Rice University about declarative machine learning at scale
+ with SystemML. Researchers in Germany are working to add Flink as an
+ additional SystemML backend. On GitHub, the project has been starred 267
+ times and forked 92 times. We have gained two new contributors since
+ February 1st.
How has the project developed since the last report?
We produced our first Apache release, version 0.9.0-incubating. Numerous
additions have been made to the project, including core functionality,
usability improvements, and documentation. The project has had 204 commits
- since February 1. In the same time frame, 155 new issues have been reported
+ since February 1. In the same time frame, 155 new issues have been
- on our JIRA site and 77 issues have been resolved. 114 pull requests opened
+ reported on our JIRA site and 77 issues have been resolved. 114 pull
- since Febrary 1 have been closed. We are preparing to produce our second
+ requests opened since Febrary 1 have been closed. We are preparing to
- incubator release.
+ produce our second incubator release.
Date of last release:
@@ -1280, +1312 @@
When were the last committers or PMC members elected?
NONE
-
Signed-off-by:
@@ -1315, +1346 @@
There are no such items.
-
How has the community developed since the last report?
- We elected a new committer.
- - Some people expressed their interest to use
+ - Some people expressed their interest to use Tamaya in their projects.
- Tamaya in their projects.
-
How has the project developed since the last report?
- Release 0.2-incubating has been released.
- - New features based on community input have been
+ - New features based on community input have been added to the roadmap.
- added to the roadmap.
-
Date of last release:
@@ -1336, +1362 @@
When were the last committers or PMC members elected?
- Philipp Ottlinger has been elected on 2016-04-22
+ Philipp Ottlinger has been elected on 2016-04-22 as new committer.
- as new committer.
-
-
-
Signed-off-by:
@@ -1423, +1445 @@
How has the community developed since the last report?
- We have 4 new committers: Ketrina Yim, Pieter Martin, Jean-Baptiste Musso, and Michael Pollmeier
+ We have 4 new committers: Ketrina Yim, Pieter Martin, Jean-Baptiste Musso,
+ and Michael Pollmeier
How has the project developed since the last report?
- Since the last status report, 172 new JIRA issues have been created and 126
+ Since the last status report, 172 new JIRA issues have been created and
- have been resolved. Open discussions of the project related activities and decisions
+ 126 have been resolved. Open discussions of the project related
- continue on the TinkerPop dev mailing list. The committer count has been growing
- and various other TinkerPop community members have shown an increased amount
- of participation on tickets and in discussion. Excellent work is being performed by
+ activities and decisions continue on the TinkerPop dev mailing list. The
+ committer count has been growing and various other TinkerPop community
+ members have shown an increased amount of participation on tickets and in
+ discussion. Excellent work is being performed by a variety of folks on a
- a variety of folks on a consistent basis that has resulted in two releases since the last report.
+ consistent basis that has resulted in two releases since the last report.
- Over the past few months, work was performed to stand up a new DataStax hosted website,
+ Over the past few months, work was performed to stand up a new DataStax
- Planet TinkerPop. This raised concerns in the Apache community and it was determined
- that the best course of action was to request that Planet TinkerPop be taken down, and
+ hosted website, Planet TinkerPop. This raised concerns in the Apache
+ community and it was determined that the best course of action was to
+ request that Planet TinkerPop be taken down, and some of the
- some of the vendor-neutral TinkerPop content be donated to TinkerPop for
+ vendor-neutral TinkerPop content be donated to TinkerPop for usage on the
- usage on the TinkerPop incubator site. Efforts were made to avoid running afoul
+ TinkerPop incubator site. Efforts were made to avoid running afoul of
- of Apache guidelines prior to the Planet TinkerPop launch, but the PPMC
+ Apache guidelines prior to the Planet TinkerPop launch, but the PPMC did
- did not have a complete understanding of Apache brand management expectations.
+ not have a complete understanding of Apache brand management expectations.
- Over the past weeks, the transition of DataStax donated content to the TinkerPop site
+ Over the past weeks, the transition of DataStax donated content to the
- has been completed. In the process, the PPMC has received guidance and
+ TinkerPop site has been completed. In the process, the PPMC has received
- clarification from mentors and the wider Apache community. We feel that the Apache
+ guidance and clarification from mentors and the wider Apache community.
- TinkerPop site is stronger now than ever and will continue to serve as a great
- vendor neutral resource going forward. The lessons learned throughout this process
- will serve the TinkerPop PPMC well going forward.
+ We feel that the Apache TinkerPop site is stronger now than ever and will
+ continue to serve as a great vendor neutral resource going forward. The
+ lessons learned throughout this process will serve the TinkerPop PPMC well
+ going forward.
Since the last status report, 166 new JIRA issues have been created and
- 127 have been resolved. Open discussions of project related activities and decisions continue
+ 127 have been resolved. Open discussions of project related activities
- on the TinkerPop dev mailing list.
+ and decisions continue on the TinkerPop dev mailing list.
Date of last release(s):
+
* 2016-04-21 - Apache TinkerPop 3.1.2
* 2016-04-21 - Apache TinkerPop 3.2.0
@@ -1478, +1505 @@
Shepherd/Mentor notes:
+ Daniel Gruno (humbedooh):
+
- Daniel Gruno: I am satisfied that the issues raised last month have been amicably resolved.
+ I am satisfied that the issues raised last month have been amicably
+ resolved.
--------------------
Toree
@@ -1515, +1545 @@
How has the project developed since the last report?
- 1. Contrinue working with JeroMQ community to further their transition into
+ 1. Contrinue working with JeroMQ community to further their transition
- MPL v2 and away from LGPL. 3 committers to go.
+ into MPL v2 and away from LGPL. 3 committers to go.
- 2. Substantial effort in our build system to make Apache compliant releases.
+ 2. Substantial effort in our build system to make Apache compliant
+ releases.
3. Addressing issues opened by community
Date of last release:
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org