incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "January2016" by MarvinHumphrey
Date Sun, 10 Jan 2016 03:31:06 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "January2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/January2016?action=diff&rev1=72&rev2=73

Comment:
Reflow.

  How has the community developed since the last report?
  
    The community is very engaged with the development of the project.
+ 
-   We see continuous uptick in mailing list participation (1392 messages on dev@ for December,
86+ subscribers).
+   We see continuous uptick in mailing list participation (1392 messages on
+   dev@ for December, 86+ subscribers).
  
-   We have seen new contributors and work to integrate with other Apache ecosystem projects
such as Geode and NiFi.
+   We have seen new contributors and work to integrate with other Apache
+   ecosystem projects such as Geode and NiFi.
  
-   The community has been active building meetup groups in various locations: http://s.apache.org/jKT
+   The community has been active building meetup groups in various locations:
+   http://s.apache.org/jKT
+ 
    Meetup membership grew to ~1000 in less than 4 months
  
  How has the project developed since the last report?
  
    Release Malhar 3.2.0-incubating on 2015-11-16
+   Roadmap published on web site:
-   Roadmap published on web site: http://apex.incubator.apache.org/roadmap.html
+   http://apex.incubator.apache.org/roadmap.html
    JIRA migration completed for Core and Malhar.
  
    Various metrics for December are as follows:
@@ -205, +211 @@

    1 new PPMC member and 2 committers were added in December.
    PPMC and committer list was updated on the status page.
  
-   Due to omission in the incubation proposal initial committers voted to adjust PPMC membership
as per original intention.
+   Due to omission in the incubation proposal initial committers voted to
+   adjust PPMC membership as per original intention.  The vote result can be
-   The vote result can be found here:  http://s.apache.org/jeJ
+   found here:  http://s.apache.org/jeJ
  
  Signed-off-by:
  
@@ -241, +248 @@

  
    No
  
- 
  How has the community developed since the last report?
  
    Activity on the mailing lists did increase a bit.
@@ -258, +264 @@

  When were the last committers or PMC members elected?
  
    Reinhard Standtner hss been added as committer on the 2nd dec.
- 
  
  Signed-off-by:
  
@@ -327, +332 @@

  --------------------
  DataFu
  
- DataFu provides a collection of Hadoop MapReduce jobs and functions in higher
+ DataFu provides a collection of Hadoop MapReduce jobs and functions in
- level languages based on it to perform data analysis. It provides functions
+ higher level languages based on it to perform data analysis. It provides
- for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
+ functions for common statistics tasks (e.g. quantiles, sampling), PageRank,
- sessionization, and set and bag operations. DataFu also provides Hadoop jobs
+ stream sessionization, and set and bag operations. DataFu also provides
- for incremental data processing in MapReduce.
+ Hadoop jobs for incremental data processing in MapReduce.
  
  DataFu has been incubating since 2014-01-05.
  
@@ -352, +357 @@

  
  How has the project developed since the last report?
  
-   * Apache DataFu 1.3.0 source release completed, which is the first release since entering
+   * Apache DataFu 1.3.0 source release completed, which is the first release
-     the Incubator.  DataFu 1.3.0 was also released to Maven.
+     since entering the Incubator.  DataFu 1.3.0 was also released to Maven.
-   * Website (http://datafu.incubator.apache.org/) has been updated with instructions
+   * Website (http://datafu.incubator.apache.org/) has been updated with
-     on how to use the source release or artifacts from Maven.
+     instructions on how to use the source release or artifacts from Maven.
  
  Date of last release:
  
@@ -394, +399 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- Nothing urgent at this moment.
+   Nothing urgent at this moment.
  
  How has the community developed since the last report?
  
-   1. We have submitted papers and applied to conferences. We worked with other open source
projects like Siddhi, Apache Ranger during December.
-   2. Dev community showed increasing interests. In Dec, there have been 878 messages on
dev@ mailing list. It is an increase of 30% mom. With more quality discussions around integration,
features and release process.
+   1. We have submitted papers and applied to conferences. We worked with
+      other open source projects like Siddhi, Apache Ranger during December.
+   2. Dev community showed increasing interests. In Dec, there have been 878
+      messages on dev@ mailing list. It is an increase of 30% mom. With more
+      quality discussions around integration, features and release process.
-   3. There were increased participation in the dev mailing list pertaining to new feature
development and roadmap.
+   3. There were increased participation in the dev mailing list pertaining
+      to new feature development and roadmap.
  
- There was a request from the community about the roadmap and clear picture of the vision.
We have published the first roadmap to the community and are working on it.
- 
+   There was a request from the community about the roadmap and clear picture
+   of the vision. We have published the first roadmap to the community and
+   are working on it.
  
  How has the project developed since the last report?
  
@@ -415, +425 @@

    2. 47 new JIRAs filed, 30 resolved (In Dec 2015)
    3. 30 code commits (In Dec 2015)
  
- 
  Date of last release:
  
- None
+   None
  
  When were the last committers or PMC members elected?
  
- None
+   None
- 
  
  Signed-off-by:
  
@@ -437, +445 @@

  
   * Activity on the dev list is healthy and trending upwards -- Julian Hyde
  
- 
  --------------------
  Fineract
  
@@ -447, +454 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1.Push the initial source code to Apache
+   1. Push the initial source code to Apache
-   2.Inform the non-technical part of the existing Mifos.org community of the change in project
structure
+   2. Inform the non-technical part of the existing Mifos.org community of
+      the change in project structure
-   3.Getting new committers up to speed on Apache processes and philosophy
+   3. Getting new committers up to speed on Apache processes and philosophy
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -458, +466 @@

  
  How has the community developed since the last report?
  
-   The project just has started. All members of the initial community are taking their first
steps into the Apache Way. The larger Mifos.org community is still operating as it was before,
and is a mix of 'clients' who use the platform and services provided by Mifos.org and partners
who leverage more on the platform and extend on it. Most partners have already been involved
and informed about the plans to become an Apache project, most of whom are part of the current
Fineract Apache community.
+   The project just has started. All members of the initial community are
+   taking their first steps into the Apache Way. The larger Mifos.org
+   community is still operating as it was before, and is a mix of 'clients'
+   who use the platform and services provided by Mifos.org and partners who
+   leverage more on the platform and extend on it. Most partners have already
+   been involved and informed about the plans to become an Apache project,
+   most of whom are part of the current Fineract Apache community.
  
  How has the project developed since the last report?
  
@@ -470, +484 @@

  
  When were the last committers or PMC members elected?
  
-   Given the early state and missing code base, no additional commiters or PMC members were
elected.
+   Given the early state and missing code base, no additional commiters or
+   PMC members were elected.
  
  Signed-off-by:
  
@@ -507, +522 @@

  
  How has the project developed since the last report?
  
-   The web site was moved over to the Apache infrastructure, and the freemarker.org
+   The web site was moved over to the Apache infrastructure, and the
-   domain was transferred to Apache too.
+   freemarker.org domain was transferred to Apache too.
  
-   Preparing for the first release from ASF, issues reported by Rat
+   Preparing for the first release from ASF, issues reported by Rat were
-   were fixed, and the build scripts were reworked to give output that conforms
+   fixed, and the build scripts were reworked to give output that conforms
    the release policy and conventions.
  
-   There were a few smaller pull requests which were all reviewed and integrated.
+   There were a few smaller pull requests which were all reviewed and
+   integrated.
  
-   As a side note, there's a yet unresolved legal/policy issue (INFRA-10787) regarding
+   As a side note, there's a yet unresolved legal/policy issue (INFRA-10787)
-   if we can use freemarker.org as the canonical domain (while it's served from the
+   regarding if we can use freemarker.org as the canonical domain (while it's
-   Apache infrastructure), or we must redirect it to freemarker.incubator.apache.org
-   (as it is now).
+   served from the Apache infrastructure), or we must redirect it to
+   freemarker.incubator.apache.org (as it is now).
  
  Date of last release:
  
@@ -553, +569 @@

  Three most important issues to address in the move towards graduation:
  
    1. Have our first Apache (incubating) release
-   2. Expanding the community to include contributors and committers outside of Pivotal.
+   2. Expanding the community to include contributors and committers outside
+      of Pivotal.
-   3. Execute and manage the project according to governance model required by the "Apache
Way"
+   3. Execute and manage the project according to governance model required
+      by the "Apache Way"
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -563, +581 @@

  
  How has the community developed since the last report?
  
- - The only item pending for the Alpha-1 release is completion of the LICENSE and NOTICE
file review (GEODE-610)
+   - The only item pending for the Alpha-1 release is completion of the
- - The Geode Clubhouse hosted a meeting covering detailed aspects of OQL/Querying on Geode
presented by Jason Huynh. Video to be published on YouTube (https://www.youtube.com/channel/UCaY2q0UlWjAgEGL7uhCLs6A)
+     LICENSE and NOTICE file review (GEODE-610)
+   - The Geode Clubhouse hosted a meeting covering detailed aspects of
+     OQL/Querying on Geode presented by Jason Huynh. Video to be published on
+     YouTube (https://www.youtube.com/channel/UCaY2q0UlWjAgEGL7uhCLs6A)
- - The new website is live and with good feedback from community, check it out!
+   - The new website is live and with good feedback from community, check it
+     out!
- - The breakdown of JIRA tickets is the following:
+   - The breakdown of JIRA tickets is the following:
  
    Q3 / 2015 - 65 created, 19 resolved.
    Q4 / 2015 - 342 created, 227 resolved.
    Q1 / 2016 - 11 created, 6 resolved.
  
- - There was a total of 66 pull requests on GitHub with 7 still open.
+   - There was a total of 66 pull requests on GitHub with 7 still open.
- - The breakdown of the mailing lists messages for October, November and December of 2015:
+   - The breakdown of the mailing lists messages for October, November and
+     December of 2015:
  
    org.apache.geode.issues       2,473
    org.apache.geode.commits      2,242
    org.apache.geode.dev  1,247
    org.apache.geode.user 169
  
- - There are now 143 subscribers on the dev and 135 on the user mailing lists.
+   - There are now 143 subscribers on the dev and 135 on the user mailing
+     lists.
- - Upcoming community events in January / 2016:
+   - Upcoming community events in January / 2016:
-    -  FOSDEM 2016 in Brussels:
+      - FOSDEM 2016 in Brussels:
-     - Taxi trip analysis (DEBS grand-challenge) with Apache Geode (incubating)
+        - Taxi trip analysis (DEBS grand-challenge) with Apache Geode
+          (incubating)
-     - Big Data meets Fast Data: an scalable hybrid real-time transactional and analytics
solution
+        - Big Data meets Fast Data: an scalable hybrid real-time
+          transactional and analytics solution
  
  How has the project developed since the last report?
  
- - GEODE-77 (about JGroups) got merged into develop making a release now possible. This was
a huge effort and now JGroups is treated like any other dependency in the project allowing
for easy updates when needed.
+   - GEODE-77 (about JGroups) got merged into develop making a release now
+     possible. This was a huge effort and now JGroups is treated like any
+     other dependency in the project allowing for easy updates when needed.
- - There is Agile Dashboard tracking the release progress:
+   - There is Agile Dashboard tracking the release progress:
  
  https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail
  
- - Builds now runs Apache RAT for license audit thanks to a Gradle plugin. (GEODE-608)
+   - Builds now runs Apache RAT for license audit thanks to a Gradle plugin.
- - Jenkins nightly build now produces source and binary artifacts. Namely apache-geode-src-1.0.0-incubating-SNAPSHOT.tar.gz
and apache-geode-1.0.0-incubating-SNAPSHOT.tar.gz
+     (GEODE-608)
+   - Jenkins nightly build now produces source and binary artifacts. Namely
+     apache-geode-src-1.0.0-incubating-SNAPSHOT.tar.gz and
+     apache-geode-1.0.0-incubating-SNAPSHOT.tar.gz
- - The code for HTTP session replication and Hibernate modules are now being merged into
develop. (GEODE-14)
+   - The code for HTTP session replication and Hibernate modules are now
- - The community did a squashathon (GEODE-409 branch) focusing to fix intermitent failures
on the CI with great results, increasing the number of Unit and Integration tests. Current
numbers are the following, by category:
- 
+     being merged into develop. (GEODE-14)
+   - The community did a squashathon (GEODE-409 branch) focusing to fix
+     intermitent failures on the CI with great results, increasing the number
+     of Unit and Integration tests. Current numbers are the following, by
+     category:
+   
    UnitTest: 1,572 tests
    IntegrationTest: 2,571 tests
    DistributedTest: 7,166 tests
@@ -608, +643 @@

  
  When were the last committers or PMC members elected?
  
- N/A
+   N/A
  
  Signed-off-by:
  
@@ -653, +688 @@

  
  How has the community developed since the last report?
  
-   1. One HAWQ Nest community meeting (topic: Data Federation with Apache HAWQ Using the
PXF Extension Framework)
+   1. One HAWQ Nest community meeting (topic: Data Federation with Apache
+      HAWQ Using the PXF Extension Framework)
       Video: http://bit.ly/HAWQNest1217, Slides: http://bit.ly/HAWQNest1217ss
    2. The community shows increasing activities. In Dev, there have
       been 494 messages on dev@/user@, compared with 459 messages in Nov.
@@ -661, +697 @@

  How has the project developed since the last report?
  
    1. Main features/improvements added include:
-      a) Improve recovery performance during some exception cases (HAWQ-241, HAWQ-232)
+      a) Improve recovery performance during some exception cases (HAWQ-241,
+         HAWQ-232)
-      b) Support writable external table executing on a specified number of virtual segment
(HAWQ-293)
+      b) Support writable external table executing on a specified number of
+         virtual segment (HAWQ-293)
-      c) Improve HAWQ resource manager resource allocation algorithm and RPC framework (HAWQ-234)
+      c) Improve HAWQ resource manager resource allocation algorithm and RPC
+         framework (HAWQ-234)
       d) Support fault injector in 2.0 (HAWQ-288)
-      e) Clean up some IP and build related issues (HAWQ-277, HAWQ-186, HAWQ-184, HAWQ-228)
+      e) Clean up some IP and build related issues (HAWQ-277, HAWQ-186,
+         HAWQ-184, HAWQ-228)
       f) Some key bug fixes for 2.0 Beta
    2. 2.0 Beta RC2 was proposed
    3. 98 new JIRAs filed, 59 resolved (In Dec 2015)
@@ -741, +781 @@

  Impala
  
  Impala is a high-performance C++ and Java SQL query engine for data stored
- in
- Apache Hadoop-based clusters.
+ in Apache Hadoop-based clusters.
  
  Impala has been incubating since 2015-12-03.
  
@@ -750, +789 @@

  
    1. Resolve any issues around use of Gerrit as code-review tool.
    2. Movement of existing JIRA / Git / wiki / e-mail resources to Apache
- equivalents
+      equivalents
    3. Initial release as incubating project.
  
  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?
  
- Slowly - Impala is still in the very early stages of incubation, and
+   Slowly - Impala is still in the very early stages of incubation, and
- performing the mechanical tasks of code movement and infrastructure setup
+   performing the mechanical tasks of code movement and infrastructure setup
- is our first priority. The holiday period in the United States has slowed
+   is our first priority. The holiday period in the United States has slowed
- this effort slightly, but we look forward to picking up pace in early 2016.
+   this effort slightly, but we look forward to picking up pace in early
- There have been no additions to the committer or PMC lists since incubation
+   2016.  There have been no additions to the committer or PMC lists since
- began.
+   incubation began.
  
  How has the project developed since the last report?
  
- We have performed some of the basic initial tasks for incubation -
+   We have performed some of the basic initial tasks for incubation -
- establishing wiki pages, Git repositories and accounts for the initial
+   establishing wiki pages, Git repositories and accounts for the initial
- committer set. Our next steps are:
+   committer set. Our next steps are:
  
- 1. Finalize the SGA from Cloudera
+   1. Finalize the SGA from Cloudera
- 2. Move existing @cloudera.org e-mail aliases to their @
+   2. Move existing @cloudera.org e-mail aliases to their
- impala.incubator.apache.org equivalents.
+      @impala.incubator.apache.org equivalents.
- 3. Move source code from Cloudera git repository to Apache git repo.
+   3. Move source code from Cloudera git repository to Apache git repo.
- 4. Improve out-of-box build and test experience so that community can
+   4. Improve out-of-box build and test experience so that community can
- easily evaluate release artifacts.
+      easily evaluate release artifacts.
- 5. Migrate cloudera.org JIRA tickets to issues.apache.org.
+   5. Migrate cloudera.org JIRA tickets to issues.apache.org.
  
  
  Date of last release:
@@ -788, +827 @@

  
  When were the last committers or PMC members elected?
  
- At the time of the Incubation vote, 2015-12-03.
+   At the time of the Incubation vote, 2015-12-03.
- 
- 
  
  Signed-off-by:
  
@@ -813, +850 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Move development to the Apache-hosted git repository, bug tracking, and code review.
+   1. Move development to the Apache-hosted git repository, bug tracking, and
+      code review.
    2. Build a more diverse development and user community
    3. Perform releases under the ASF
  
- 
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- None so far.
+   None so far.
  
- 
- How has the community developed since the last report?
- 
- - The development community has remained about the same since the initial proposal, with
overall code contribution levels a bit lower than historical averages due to the end-of-year
holidays.
- - Xiaomi reported that they are now running Kudu in a production use case on ~70 nodes ingesting
10B rows/day. This is Kudu's first known production use case, and we expect continuing and
increasing participation from developers at Xiaomi.
- - To spread the word about Kudu, various community members have given a number of talks
over the last 6 weeks, including: Strata/Hadoop World (Singapore), Big Data Tech Con (Beijing),
Shanghai Streaming Meetup, Korea Big Data Think Tank (Seoul), San Francisco Spark Hackers,
The Hive Big Data Think Tank (Palo Alto), Charlotte Hadoop User Group, Cloudera World Tokyo,
Big Data Warehousing Meetup (NYC), and more.
- - Members of the Kudu community met up with Apache Drill contributors and built an initial
version of Kudu/Drill integration. We anticipate further collaboration with Drill and other
ASF TLPs.
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   - The development community has remained about the same since the initial
+     proposal, with overall code contribution levels a bit lower than
+     historical averages due to the end-of-year holidays.
+   - Xiaomi reported that they are now running Kudu in a production use case
+     on ~70 nodes ingesting 10B rows/day. This is Kudu's first known
+     production use case, and we expect continuing and increasing
+     participation from developers at Xiaomi.
+   - To spread the word about Kudu, various community members have given a
+     number of talks over the last 6 weeks, including: Strata/Hadoop World
+     (Singapore), Big Data Tech Con (Beijing), Shanghai Streaming Meetup,
+     Korea Big Data Think Tank (Seoul), San Francisco Spark Hackers, The Hive
+     Big Data Think Tank (Palo Alto), Charlotte Hadoop User Group, Cloudera
+     World Tokyo, Big Data Warehousing Meetup (NYC), and more.
+   - Members of the Kudu community met up with Apache Drill contributors and
+     built an initial version of Kudu/Drill integration. We anticipate
+     further collaboration with Drill and other ASF TLPs.
+ 
+ 
+ How has the project developed since the last report?
+ 
- This is our first report since incubation. In the past month, we've accomplished a few milestones:
+   This is our first report since incubation. In the past month, we've
+   accomplished a few milestones:
+ 
- - filed an SGA as well as ICLAs for initial committers
+   - filed an SGA as well as ICLAs for initial committers
- - granted karma, created mailing lists, and subscribed mentors/committers
+   - granted karma, created mailing lists, and subscribed mentors/committers
- - updated our web site to comply with ASF branding
+   - updated our web site to comply with ASF branding
- - filed INFRA requests to start working on git and JIRA migration (INFRA-10959, INFRA-10983)
+   - filed INFRA requests to start working on git and JIRA migration
- 
- Progress has slowed in the second half of December due to the holiday season, but we anticipate
picking momentum back up in January.
- 
+     (INFRA-10959, INFRA-10983)
+   
+   Progress has slowed in the second half of December due to the holiday
+   season, but we anticipate picking momentum back up in January.
+   
  
  Date of last release:
  
@@ -883, +935 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
-   Not sure if the project still has an official mentor assigned, after Christian
+   Not sure if the project still has an official mentor assigned, after
-   Grobmeier is not the chair of the Apache Logging Services project anymore.
+   Christian Grobmeier is not the chair of the Apache Logging Services
+   project anymore.
  
  How has the community developed since the last report?
  
@@ -925, +978 @@

  Three most important issues to address in the move towards graduation:
  
    1. Produce a first Apache (incubating) release.
-   2. Expand the community, increase dev list activity and add new committers/pmc members.
+   2. Expand the community, increase dev list activity and add new
+      committers/pmc members.
-   3. Execute and manage the project according to governance model required by the "Apache
Way”.
+   3. Execute and manage the project according to governance model required
+      by the "Apache Way”.
  
- 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?
  
-   1. Second community call held 12/18/15.  On the call Roman suggested that the MADlib community
do a 1.9 alpha release in the near term.  There was general agreement and this is planned
for January.  A Release Manager has not yet been identified.
-   2. Material technical conversations on dev mailing lists and in the appropriate JIRAs.
 E.g., 51 emails on dev in Dec.
+   1. Second community call held 12/18/15.  On the call Roman suggested that
+      the MADlib community do a 1.9 alpha release in the near term.  There
+      was general agreement and this is planned for January.  A Release
+      Manager has not yet been identified.
+   2. Material technical conversations on dev mailing lists and in the
+      appropriate JIRAs.  E.g., 51 emails on dev in Dec.
-   3. One new committer has been proposed and voting is under way on the private mailing
list.
+   3. One new committer has been proposed and voting is under way on the
-   4. Two comprehensive proposals were posted to the dev mailing list from community members.
 One relates to the addition of geographically weighted regression (GWR) algorithms.  The
second involves Bayesian analysis of binomial response models for MPP databases, which makes
extensive use of MADlib’s new matrix operations.  Both proposals are under active discussion
on the mailing list currently.
-   5. We have been accepted to present a full talk at FOSDEM 2016/Brussels in the HPC, Big
Data & Data Science Devroom on Jan 31.  The title of the talk is: "MADlib: Distributed
In-Database Machine Learning for Fun and Profit"
+      private mailing list.
+   4. Two comprehensive proposals were posted to the dev mailing list from
+      community members.  One relates to the addition of geographically
+      weighted regression (GWR) algorithms.  The second involves Bayesian
+      analysis of binomial response models for MPP databases, which makes
+      extensive use of MADlib’s new matrix operations.  Both proposals are
+      under active discussion on the mailing list currently.
+   5. We have been accepted to present a full talk at FOSDEM 2016/Brussels in
+      the HPC, Big Data & Data Science Devroom on Jan 31.  The title of the
+      talk is: "MADlib: Distributed In-Database Machine Learning for Fun and
+      Profit"
  
  How has the project developed since the last report?
  
    1. 5 JIRAs created and 4 resolved in last 30 days.
-   2. A SQL API guide has been added to the the MADlib wiki https://cwiki.apache.org/confluence/display/MADLIB/SQL+API+Guide.
+   2. A SQL API guide has been added to the the MADlib wiki
+      https://cwiki.apache.org/confluence/display/MADLIB/SQL+API+Guide.
  
  Date of last release:
  
@@ -951, +1021 @@

  
  When were the last committers or PMC members elected?
  
-   One new committer has been proposed and voting is under way on the private mailing list.
+   One new committer has been proposed and voting is under way on the private
+   mailing list.
  
  Signed-off-by:
  
@@ -966, +1037 @@

  --------------------
  Metron
  
- Metron is a project dedicated to providing an extensible and scalable advanced
+ Metron is a project dedicated to providing an extensible and scalable
- network security analytics tool. It has strong foundations in the Apache
+ advanced network security analytics tool. It has strong foundations in the
- Hadoop ecosystem.
+ Apache Hadoop ecosystem.
  
  Metron has been incubating since 2015-12-06.
  
@@ -1025, +1096 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Do a first Apache release capable of producing a downloadable RTOS image
+   1. Do a first Apache release capable of producing a downloadable RTOS
-      with support for multiple peripherals and network connectivity.
+      image with support for multiple peripherals and network connectivity.
-   2. Develop and execute policies that enable project contributors to achieve self-governance
+   2. Develop and execute policies that enable project contributors to
+      achieve self-governance
-   3. Expand community - attract new project contributors and users, grow committer base
+   3. Expand community - attract new project contributors and users, grow
+      committer base
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -1041, +1114 @@

       @commits  150+ messages
    2. Repo is being cloned and looked at by several outside parties - need
       to get all interested parties on the dev mailing list.
-   3. Participation on the @dev mailing list covered a range of topics including feature
+   3. Participation on the @dev mailing list covered a range of topics
-      implementation approaches, coding practices, website, and documentation rules discussions.
+      including feature implementation approaches, coding practices, website,
+      and documentation rules discussions.
  
- 
  How has the project developed since the last report?
  
-   1. Feature support: 2 new JIRA issues were created to facilitate feature implementation
+   1. Feature support: 2 new JIRA issues were created to facilitate feature
-      and website discussions
+      implementation and website discussions
- 
-   2. Documentation support: Two new committers have started adding material to technical
+   2. Documentation support: Two new committers have started adding material
+      to technical documentation.
-      documentation.
- 
-   3. Effort towards community growth: We have redesigned the project website to organize
and
+   3. Effort towards community growth: We have redesigned the project website
-      present content more clearly and to highlight upcoming events where the project will
have exposure.
- 
+      to organize and present content more clearly and to highlight upcoming
+      events where the project will have exposure.
-   4. Effort towards self governance: Consensus reached on how a potential contributor is
+   4. Effort towards self governance: Consensus reached on how a potential
-      accepted over time as a committer based on quality of work.
+      contributor is accepted over time as a committer based on quality of
+      work.
  
  Date of last release:
  
@@ -1091, +1163 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1.  Import the software.
+   1. Import the software.
-   2.  Sign up the developers.
+   2. Sign up the developers.
-   3.  Audit the Intellectual Property.
+   3. Audit the Intellectual Property.
  
- All fairly meaningless until the Community is live at Apache.
+   All fairly meaningless until the Community is live at Apache.
  
- 
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
- 
- n/a.
- 
- How has the community developed since the last report?
- 
- n/a.
- Initial committers have been asked to sign up to the lists
- and submit ICLAs.
- 
- How has the project developed since the last report?
- 
- n/a.
- 
- Date of last release:
  
    n/a.
  
- When were the last committers or PMC members elected?
+ How has the community developed since the last report?
  
+   n/a.
+ 
+   Initial committers have been asked to sign up to the lists and submit
+   ICLAs.
+ 
+ How has the project developed since the last report?
+ 
+   n/a.
+ 
+ Date of last release:
+ 
+   n/a.
+ 
+ When were the last committers or PMC members elected?
+ 
- Initial Committers only.
+   Initial Committers only.
  
  Signed-off-by:
  
@@ -1225, +1297 @@

  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
+ supports SPARQL queries. Rya is a scalable RDF data management system built
- top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
+ on top of Accumulo. Rya uses novel storage methods, indexing schemes, and
- processing techniques that scale to billions of triples across multiple nodes.
+ query processing techniques that scale to billions of triples across
- Rya provides fast and easy access to the data through SPARQL, a conventional
- query mechanism for RDF data.
+ 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 issues to address in the move towards graduation:
  
    1. Populate the website for the project
-   2. Expand the "how to" document to explain the ways new contributors can become involved
in the project, so we increase the size of the community.
+   2. Expand the "how to" document to explain the ways new contributors can
+      become involved in the project, so we increase the size of the
+      community.
-   3. Become familiar with the release process and have a first release as part of the Apache
Foundation
+   3. Become familiar with the release process and have a first release as
+      part of the Apache Foundation
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -1246, +1321 @@

  
  How has the community developed since the last report?
  
-  * We have documented (on Confluence) and tested procedures for committers to review and
incorporate Pull Requests into the incubator-rya Apache git repository.
+   * We have documented (on Confluence) and tested procedures for committers
+     to review and incorporate Pull Requests into the incubator-rya Apache
+     git repository.
+   * The committers are becoming much more comfortable with the Apache
+     infrastructure and processes. Committers have been documenting processes
+     on Confluence, creating Jira tickets, tying these to Rya components and
+     versions, and submitting and pulling in PRs to resolve these Jira
+     tickets.
+   * The Rya user community (i.e. non-committers) have begun submitting
+     issues through Jira and the dev list.  These have become Jira tickets,
+     resolved by committers, and tested by the community.  Specifically, the
+     community submitted RYA-19, RYA-17, and RYA-6.  Committers resolved and
+     the community tested RYA-19 and RYA-17.
+   * Non-committers have also begun submitting PRs that have been
+     incorporated into the apache repo.  Specifically, RYA-13 and most of
+     RYA-7 was done by non-committers.
+   * We've started logging "beginner" Jira tickets.  These are issues that
+     we've found in Rya that a new developer could take on as a good way to
+     "get their feet wet" in the code base.
  
-  * The committers are becoming much more comfortable with the Apache infrastructure and
processes. Committers have been documenting processes on Confluence, creating Jira tickets,
tying these to Rya components and versions, and submitting and pulling in PRs to resolve these
Jira tickets.
- 
-  * The Rya user community (i.e. non-committers) have begun submitting issues through Jira
and the dev list.  These have become Jira tickets, resolved by committers, and tested by the
community.  Specifically, the community submitted RYA-19, RYA-17, and RYA-6.  Committers resolved
and the community tested RYA-19 and RYA-17.
- 
-  * Non-committers have also begun submitting PRs that have been incorporated into the apache
repo.  Specifically, RYA-13 and most of RYA-7 was done by non-committers.
- 
-  * We've started logging "beginner" Jira tickets.  These are issues that we've found in
Rya that a new developer could take on as a good way to "get their feet wet" in the code base.
- 
  How has the project developed since the last report?
  
-  * We've completed adding the Apache license headers and added license header verification
to the project's build.
+   * We've completed adding the Apache license headers and added license
- 
+     header verification to the project's build.
-  * Resolved a handful of issues that users have encountered.
+   * Resolved a handful of issues that users have encountered.
- 
-  * Committed features: Delete support for secondary indices, more efficient Mongo Core and
Geo indexing.
+   * Committed features: Delete support for secondary indices, more efficient
- 
+   * Mongo Core and Geo indexing.
-  * Still working on creating a website for the project.
+   * Still working on creating a website for the project.
- 
-  * Working on deploying artifacts onto Maven
+   * Working on deploying artifacts onto Maven
- 
-  * Working on creating a quick-start VM for users to try out Rya.
+   * Working on creating a quick-start VM for users to try out Rya.
  
  Date of last release:
  
@@ -1307, +1389 @@

  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?
-  * Project infrastructures (i.e., jira, wiki, mailing list and git repository) setup has
been completed, and the site and the source code are moved to the Apache infrastructure.
+ 
+   * Project infrastructures (i.e., jira, wiki, mailing list and git
+     repository) setup has been completed, and the site and the source code
+     are moved to the Apache infrastructure.
-  * All members have submitted necessary CLAs.
+   * All members have submitted necessary CLAs.
-  * SGA have submitted from Kakao.
+   * SGA have submitted from Kakao.
-  * There have been no new committers or PPMC members elected.
+   * There have been no new committers or PPMC members elected.
-  * We are discussing the development workflow and the code review policy.
+   * We are discussing the development workflow and the code review policy.
  
  How has the project developed since the last report?
+ 
-  * We are applying ALv2 header to all files and rat-plugin to audit them.
+   * We are applying ALv2 header to all files and rat-plugin to audit them.
  
- 
  Date of last release:
  
- No yet
+   No yet
  
  When were the last committers or PMC members elected?
  
- No
+   No
  
  Signed-off-by:
  
@@ -1354, +1439 @@

  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?
  
- No change
+   No change
  
  How has the project developed since the last report?
  
- Several fixes have been done and enhancements in instrumentation side.
+   Several fixes have been done and enhancements in instrumentation side.
  
  Date of last release:
  
@@ -1390, +1474 @@

  
  SystemML provides declarative large-scale machine learning (ML) that aims at
  flexible specification of ML algorithms and automatic generation of hybrid
- runtime plans ranging from single node, in-memory computations, to distributed
+ runtime plans ranging from single node, in-memory computations, to
- computations such as Apache Hadoop MapReduce and Apache Spark.
+ distributed computations such as Apache Hadoop MapReduce and Apache Spark.
  
  SystemML has been incubating since 2015-11-02.
  
@@ -1418, +1502 @@

    Users have asked several excellent questions on the dev list, and existing
    committers are actively helping these users. The project is receiving pull
    requests from contributors, committers have discussed these pull requests
-   with their contributors, and contributions have been merged into the project.
+   with their contributors, and contributions have been merged into the
-   Matthias Boehm has presented talks regarding the SystemML Optimizer at
+   project.  Matthias Boehm has presented talks regarding the SystemML
-   TU Dresden, HTW Dresden, and TU Berlin. Fred Reiss presented a talk on
+   Optimizer at TU Dresden, HTW Dresden, and TU Berlin. Fred Reiss presented
-   Dec 8th.
+   a talk on Dec 8th.
  
  How has the project developed since the last report?
  
@@ -1474, +1558 @@

  
  How has the community developed since the last report?
  
-   We got feedbacks from users and interested people. A good sign is that the 1.0.0-incubating
release has been voted
+   We got feedbacks from users and interested people. A good sign is that the
+   1.0.0-incubating release has been voted by people outside of the initial
-   by people outside of the initial committer set (even if the release vote didn't pass).
+   committer set (even if the release vote didn't pass).
  
  How has the project developed since the last report?
  
-   We did improvement on the website, and on the code. Our focus was on Unomi 1.0.0-incubating
release.
+   We did improvement on the website, and on the code. Our focus was on Unomi
-   Unfortunately, a couple of issues (missing src assembly especially) blocked the vote.
We are fixing those issues
+   1.0.0-incubating release.  Unfortunately, a couple of issues (missing src
+   assembly especially) blocked the vote. We are fixing those issues to
-   to submit a take 2 on 1.0.0-incubating release.
+   submit a take 2 on 1.0.0-incubating release.
  
  Date of last release:
  
-   Unomi 1.0.0-incubating has been proposed to vote, but due to a couple of issue it has
been declined.
+   Unomi 1.0.0-incubating has been proposed to vote, but due to a couple of
-   We are working to submit a take 2 on 1.0.0-incubating.
+   issue it has been declined.  We are working to submit a take 2 on
+   1.0.0-incubating.
  
  When were the last committers or PMC members elected?
  


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message