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 "November2013" by MarvinHumphrey
Date Thu, 14 Nov 2013 03:23:49 GMT
Dear Wiki user,

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

The "November2013" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/November2013?action=diff&rev1=55&rev2=56

Comment:
Normalize formatting.

  {{{
  Incubator PMC report for November 2013
  
- The Apache Incubator is the entry path into the ASF for projects and codebases
+ The Apache Incubator is the entry path into the ASF for projects and
- wishing to become part of the Foundation's efforts.
+ codebases wishing to become part of the Foundation's efforts.
  
  There are 36 podlings currently under incubation.
  
@@ -93, +93 @@

  
  * Miscellaneous
  
-   * Several discussion threads on project bylaws, initiated by Flex community
+   * Several discussion threads on project bylaws, initiated by Flex
-     pursuing refinement of their own, have made it clear just how difficult it
+     community pursuing refinement of their own, have made it clear just how
-     is to draft good bylaws.  A number of people expressed a desire for a set
+     difficult it is to draft good bylaws.  A number of people expressed a
-     of well-crafted, official project bylaws which all projects would
+     desire for a set of well-crafted, official project bylaws which all
-     "inherit".  Since that's hard, though, for the time being we're muddling
+     projects would "inherit".  Since that's hard, though, for the time being
-     through with patches to the existing ramshackle documentation.
+     we're muddling through with patches to the existing ramshackle
+     documentation.
  
    * The Incubator's perpetual difficulties getting podling releases approved
-     has spawned another lively discussion.  We seem to have reached agreement
+     has spawned another lively discussion.  We seem to have reached
-     that we can mitigate the problem by entrusting meritorious podling
+     agreement that we can mitigate the problem by entrusting meritorious
-     contributors with a binding vote on incubating releases; debate continues
+     podling contributors with a binding vote on incubating releases; debate
-     about what implementation to try.  At time of writing, the stratagem with
+     continues about what implementation to try.  At time of writing, the
-     the most popular support seems to be electing more podling contributors
+     stratagem with the most popular support seems to be electing more
-     directly onto the IPMC, but the thread has not yet tailed off.
+     podling contributors directly onto the IPMC, but the thread has not yet
+     tailed off.
  
  -------------------- Summary of podling reports --------------------
  
@@ -403, +405 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Make a release - progress is slow but we're getting there, expecting our first release
around the board meeting.
+   1. Make a release - progress is slow but we're getting there, expecting
+      our first release around the board meeting.
    2. Review PPMC membership and ask who's staying on board
    3. Graduate
  
@@ -462, +465 @@

  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?
  
- No changes to community.
+   No changes to community.
  
  How has the project developed since the last report?
  
- The project has been very quiet / dormant for the past quarter.
+   The project has been very quiet / dormant for the past quarter.
  
  Date of last release: 
  
@@ -478, +481 @@

  
  When were the last committers or PMC members elected?
  
- 2012-05-07
+   2012-05-07
  
  Signed-off-by: 
  
@@ -499, +502 @@

  Three most important issues to address in the move towards graduation:
  
    1. we have to finish the release of version 0.0.1 and to define the build
- environment using Jenkins
+      environment using Jenkins
    2. we have to define and implement an effective approach to manage the
- "client connections" to multiple clusters.
+      "client connections" to multiple clusters.
    3. Build Community
  
  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?
  
-  - hdt-dev has seen around 118 mails during this period
+   - hdt-dev has seen around 118 mails during this period
  
  How has the project developed since the last report?
  
-  - We released RC0 for 0.0.1 on the dev mailing list. There were some
+   - We released RC0 for 0.0.1 on the dev mailing list. There were some
- feedback points for the release process/artifacts. HDT-44, was also
+     feedback points for the release process/artifacts. HDT-44, was also
- reported for RC0. The issue  have been addressed and we can make a new RC
+     reported for RC0. The issue  have been addressed and we can make a new
- sometime soon.
+     RC sometime soon.
-  - Around 8 JIRA were filed during thing period to complete the migration
+   - Around 8 JIRA were filed during thing period to complete the migration
- of hadoop-eclipse source.
+     of hadoop-eclipse source.
  
  Date of last release:
  
@@ -528, +531 @@

  
  When were the last committers or PMC members elected?
  
-  June'2013
+  June 2013
  
  Signed-off-by: 
  
@@ -610, +613 @@

  
  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?
- Community growth has slowed but development work has continued strong. A number of people
on the project attended the International Conference on Regional Climate - CORDEX 2013 and
spoke about research that is being powered by the Open Climate Workbench.
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
- Quite a bit of development work has continued on the project. Michael Joyce pushed out the
0.3-incubating release on the October 11 which resolved about 85 issues. Denis Nadeau made
a huge contribution to the project in the obs4MIPs code base which provides a great deal of
utility to the project. Cameron Goodale added tests that run the toolkit through an entire
comparison so users can validate dependency installations and get a feel for how to use OCW.
+ 
+   Community growth has slowed but development work has continued strong. A
+   number of people on the project attended the International Conference on
+   Regional Climate - CORDEX 2013 and spoke about research that is being
+   powered by the Open Climate Workbench.
+ 
+ How has the project developed since the last report?
+ 
+   Quite a bit of development work has continued on the project. Michael
+   Joyce pushed out the 0.3-incubating release on the October 11 which
+   resolved about 85 issues. Denis Nadeau made a huge contribution to the
+   project in the obs4MIPs code base which provides a great deal of utility
+   to the project. Cameron Goodale added tests that run the toolkit through
+   an entire comparison so users can validate dependency installations and
+   get a feel for how to use OCW.
  
  Date of last release: 
  
@@ -650, +663 @@

    2. Build up the community.
    3. Make a release under Apache.
  
- 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?
  
    No
  
@@ -670, +684 @@

  
    Continuing Cordova 3.0 work to get to a stable, releasable product.
  
-   The Chrome Extension build target was removed altogether from the project, in
+   The Chrome Extension build target was removed altogether from the project,
-   an effort to simplify and streamline the building/compilation of the project
+   in an effort to simplify and streamline the building/compilation of the
-   into a usable application, and because the project has been continually
+   project into a usable application, and because the project has been
-   moving towards a [more feature-able] NodeJS backend, capable of being run in any Browser.
+   continually moving towards a [more feature-able] NodeJS backend, capable
+   of being run in any Browser.
  
  Date of last release?
  
@@ -718, +733 @@

    groups (Hive User Group, New York Hadoop User Group) with great interest.
    Sentry community hosted its first meetup in NYC. Nearly 20 people attended
    the meetup.  There was great interest and lively discussions. 
- 
  
  How has the project developed since the last report?
  
@@ -812, +826 @@

  Storm
  
  Storm is a distributed, fault-tolerant, and high-performance realtime
- computation system that provides strong guarantees on the processing of data.
+ computation system that provides strong guarantees on the processing of
+ data.
  
  Storm has been incubating since 2013-09-18.
  
  Three most important issues to address in the move towards graduation:
  
    1. Release Storm 0.9.0 with the current github process (the next release, 
-      0.9.1 will be under the Apache process -- we have promised our community a 
+      0.9.1 will be under the Apache process -- we have promised our
-      0.9.0 release prior to moving to the Apache process).
+      community a 0.9.0 release prior to moving to the Apache process).
    2. Finish bootstrapping the project, migrate github issues to JIRA.
    3. Expand the community and adding new committers.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
-    There has been a delay with some of the committers getting user accounts. 
+   There has been a delay with some of the committers getting user accounts.
-    This is an impediment to the bootstrap process.
+   This is an impediment to the bootstrap process.
  
  How has the community developed since the last report?
  
-    Several new community members have submitted contributions, but we are 
+   Several new community members have submitted contributions, but we are 
-    largely still bootstrapping the project.
+   largely still bootstrapping the project.
  
- 
  How has the project developed since the last report?
  
-    We have continued to apply bug fixes necessary for the 0.9.0 release and 
+   We have continued to apply bug fixes necessary for the 0.9.0 release and 
-    expect one more release candidate before releasing 0.9.0 and migrating to 
+   expect one more release candidate before releasing 0.9.0 and migrating to
-    the Apache process. We have adopted aspects of the apache process in 
+   the Apache process. We have adopted aspects of the apache process in 
-    anticipation of this.
+   anticipation of this.
  
-    Our dev/user mailing lists have been created and we've notified the 
+   Our dev/user mailing lists have been created and we've notified the
-    community that those lists should be used instead of the google groups list. 
+   community that those lists should be used instead of the google groups
-    We will sunset the google groups list shortly.
+   list.  We will sunset the google groups list shortly.
  
  Date of last release: 
  
@@ -854, +868 @@

  When were the last committers or PMC members elected?
  
    - N/A -- We are still bootstrapping the project.
- 
- 
  
  Signed-off-by: 
  
@@ -932, +944 @@

  
      The project is moving very quickly, but needs to make a release soon.
  
- 
  --------------------
  Usergrid
  
@@ -949, +960 @@

    2. Growing a diverse community
    3. Getting project infrastructure and codebase setup at Apache
  
- 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 at this time
  

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


Mime
View raw message