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 "August2016" by JigneshPatel
Date Wed, 03 Aug 2016 20:16:05 GMT
Dear Wiki user,

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

The "August2016" page has been changed by JigneshPatel:
https://wiki.apache.org/incubator/August2016?action=diff&rev1=30&rev2=31

  = Incubator PMC report for August 2016 =
- 
  === Timeline ===
  ||Wed August 03 ||Podling reports due by end of day ||
  ||Sun August 07 ||Shepherd reviews due by end of day ||
@@ -41, +40 @@

  ||[none] ||Toree ||
  ||[none] ||Traffic Control ||
  ||[none] ||iota ||
+ 
  
  === Report content ===
  {{{
@@ -241, +241 @@

   * Continued improvements to documentation and testing
  
  Date of last release:
-  * 2016/06/15 - 0.1.0-incubating 
+  * 2016/06/15 - 0.1.0-incubating
   * 2016/07/28 - 0.2.0-incubating (RC proposal sent to Incubator PMC)
  
  When were the last committers or PMC members elected?
@@ -333, +333 @@

  
  The community activity increased: many new users started to use and test CarbonData, we
had more than 100 new issues created during July.
  
- On the other hand, presentation material has been created and a first talk has been given:

+ On the other hand, presentation material has been created and a first talk has been given:
  
  http://www.slideshare.net/liangchen18/apache-carbondatanew-high-performance-data-format-for-faster-data-analysis
  
@@ -576, +576 @@

  
    We completed refactoring of code to use Apache names.  We attempted our first
    release of a parent pom (for both Fluo projects) and it failed on the incubator
-   list.  A parent pom is a way to share build configuration among multiple 
+   list.  A parent pom is a way to share build configuration among multiple
    projects.  We plan for Fluo and Fluo Recipes to both inherit the same parent pom
    and obtain common config for code formatting, findbugs, checkstyle rules, etc.
    For this to work the parent pom needs to be released before the projects.
@@ -585, +585 @@

    following issues :
  
   * Improper linking to pre-Apache releases of Fluo from website.
-  * Branding and linking issues with fluo.io domain, fluo-io GitHub org and projects. 
+  * Branding and linking issues with fluo.io domain, fluo-io GitHub org and projects.
     The domain name and github org were used by the project before moving to Apache.
  
-   This was really good feedback.  We want to remedy the issues identified and 
+   This was really good feedback.  We want to remedy the issues identified and
    eliminate possible confusion around the Apache Fluo brand.  The following link
-   identifies discussion of a possible way forward. 
+   identifies discussion of a possible way forward.
  
    https://lists.apache.org/thread.html/b478645815bf7b1fee8342a21924162decc173d91c22eaf5f708a435@%3Cdev.fluo.apache.org%3E
  
@@ -734, +734 @@

  
  Three most important issues to address in the move towards graduation:
  
- 1. Building a community now that we have completed source code upload of 
+ 1. Building a community now that we have completed source code upload of
- one for the main components of the system. 
+ one for the main components of the system.
- 2. Moving towards an initial release before the end of the year 
+ 2. Moving towards an initial release before the end of the year
  3. Working on IP clearance for the release
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -751, +751 @@

  
  How has the project developed since the last report?
  
- We continue to improve (the Fey 
+ We continue to improve (the Fey
  engine) we have added tests for the core engine and documentation for the engine and the
component set.
  
  Date of last release:
@@ -760, +760 @@

  
  When were the last committers or PMC members elected?
  
- At the start of the project. 
+ At the start of the project.
  
  Signed-off-by:
  
@@ -839, +839 @@

  Three most important issues to address in the move towards graduation:
  
    1. Build up community with non-IBM and non-Salesforce contributors.
-   2. Finish creating website. 
+   2. Finish creating website.
    3. Finish populating Git repo.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -848, +848 @@

    None.
  
  How has the community developed since the last report?
-   
+ 
-   Currently only two of the original proposers have gone through the process of getting
commit approval.  
+   Currently only two of the original proposers have gone through the process of getting
commit approval.
    Some of the Salesforce proposers have been busy with their release schedule.  Others need
to be bugged to finish up the paperwork.
  
  How has the project developed since the last report?
  
    Grant from IBM Corporation for Juno (Apache Juneau) has been received by the ASF.
-   
+ 
    The Juno codebase has been uploaded to the Git repository.  We're still in the process
of cleaning it up and converting to using Maven for builds.
  
    Work has been done on the website, although build issues appear to be preventing it from
being fully deployed.
@@ -948, +948 @@

  
  How has the community developed since the last report?
  
- The mailing list activity, pull requests, and page views to the Apache Pirk website (via
Google Analytics) have greatly increased since the last report. 
+ The mailing list activity, pull requests, and page views to the Apache Pirk website (via
Google Analytics) have greatly increased since the last report.
  
  How has the project developed since the last report?
  
- 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 more robust support for user interaction. 
+ 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 more robust support for user interaction.
  
  Date of last release:
  
@@ -1034, +1034 @@

  
    1. Establish a formal release schedule and process, allowing for dependable release cycles
consistent with the Apache way.
    2. Grow the community to establish diversity
-   3. Transition of present PredictionIO users from google-groups to ASF mailing lists. 

+   3. Transition of present 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?
@@ -1126, +1126 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1.
-   2.
-   3.
+   1. Acquire early adopters.
+   2. Continue to build the developer community.
+   3. Create an ASF release.
  
  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?
- 
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
+   1. Added two new members to the (core) Committers group.
+   2. Added one new member to the Contributor group.
+   3. Started discussions for a community and governance structure. Initial proposal has
been circulated the project developer list.
  
+ How has the project developed since the last report?
+   1. We have closed over 40 pull requests.
+   2. Created a website.
+   3. Created a getting started guide.
+   4. Started work on cleaning up the entire repository to have licensing and copyrights
in line with ASF projects.
  
  
  Date of last release:
  
-   XXXX-XX-XX
+   No release yet.
  
  When were the last committers or PMC members elected?
  
+ N/A
  
  
  Signed-off-by:
@@ -1189, +1194 @@

    * Made plans to integrate with Apache TinkerPop in order to reach a wider audience (S2GRAPH-72)
  
    * Discussion with Apache Zepplin regarding joint meet-ups at Seoul
-   
+ 
    * 3 inquiries from user mailing list
-   
+ 
    * Submit paper to INFOCOM 2017
  
  How has the project developed since the last report?
  
-   * We decided project logo. 
+   * We decided project logo.
  
-   * Project website is up. 
+   * Project website is up.
  
    * Working on issues on providing package for distribution.
  
    * 20 issues are created, 18 issues are resolved.
-   
+ 
    * Working on first release(S2GRAPH-86)
  
  Date of last release:
@@ -1246, +1251 @@

  
  How has the project developed since the last report?
  
- Development has been going on outside of The ASF while we wait on sending 
+ Development has been going on outside of The ASF while we wait on sending
  relevant documents to secretary@
  
  Date of last release:
@@ -1595, +1600 @@

    [X](unomi) Jean-Baptiste Onofré
    [ ](unomi) Bertrand Delacretaz
    [ ](unomi) Chris Mattmann
- 
  }}}
  

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


Mime
View raw message