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 "July2014" by JoeBrockmeier
Date Tue, 08 Jul 2014 23:01:10 GMT
Dear Wiki user,

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

The "July2014" page has been changed by JoeBrockmeier:
https://wiki.apache.org/incubator/July2014?action=diff&rev1=45&rev2=46

Comment:
Editorial and formatting changes. Really hoping this didn't make things worse than better...

  {{{
  Incubator PMC report for July 2014
  
- 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 currently 34 podlings under incubation, with three votes to graduate as 
+ There are currently 34 podlings under incubation, with three votes to 
- the report is being closed. The Tez and Celix VOTEs have passed, and VXQuery is still 
+ graduate as the report is being closed. The Tez and Celix VOTEs have passed, 
- underway. S4 has voted to retire, but the retirement tasks have not yet been 
+ and VXQuery is still underway. S4 has voted to retire, but the retirement 
- finished. Fleece has joined the incubator, as of 9 June 2014.
+ tasks have not yet been finished. Fleece has joined the incubator, as of 9 
+ June 2014.
  
  * Community
  
@@ -77, +78 @@

  * Miscellaneous
  
      S4 voted to retire. SGA received for Optiq from DynamoBI Corporation. 
-     Discussion about exit criteria for podlings, including a suggested set of
+     Discussion about exit criteria for podlings, including a suggested set 
-     criteria that would trigger a VOTE to retire if a podling is not active
+     of criteria that would trigger a VOTE to retire if a podling is not 
-     enough. Consensus not yet reached. Stratos has graduated but still needs
+     active enough. Consensus not yet reached. Stratos has graduated but 
-     to finish graduation tasks.
+     still needs to finish graduation tasks.
  
  -------------------- Summary of podling reports --------------------
  
@@ -262, +263 @@

  --------------------
  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.
  
@@ -316, +317 @@

  
  Apache DeviceMap is a data repository containing device information, images
  and other relevant information for all sorts of mobile devices, e.g.
- smartphones and tablets. While the focus is initially on that data, APIs will
+ smartphones and tablets. While the focus is initially on that data, APIs 
- also be created to use and manage it.
+ will also be created to use and manage it.
  
  DeviceMap has been incubating since 2012-01-03.
  
@@ -329, +330 @@

   2. Challenge #2: make a release
   3. Challenge #3: form a PMC with 4-5 members to graduate
  
- Those should really not be challenges but at this point that felt like an appropriate
+ Those should really not be challenges but at this point that felt like an 
- way of indicating the importance of those actions. There's already promising responses,
- we'll see if those translate into concrete actions.
+ appropriate way of indicating the importance of those actions. There's 
+ already promising responses, we'll see if those translate into concrete 
+ actions.
  
- Apart from that there's been some good discussions in the last weeks, but no concrete
+ Apart from that there's been some good discussions in the last weeks, but no 
- results yet.
+ concrete results yet.
  
  Best is probably to evaluate the progress on the above challenges next month
  to make a decision about the future of the project.
@@ -355, +357 @@

  
  Shepherd/Mentor notes:
  
- (rvs) The report is missing. This on-n-off seems to continue with the project. I know that
+ (rvs) The report is missing. This on-n-off seems to continue with the 
- some of the mentors are recommending giving it more time, but it seems like we need
- to establish some metrics to at least get the community in shape to do the basics (like
- reporting and releasing). Without any kind of forcing function I am not sure what the
- future for this project really is.
+ project. I know that some of the mentors are recommending giving it more 
+ time, but it seems like we need to establish some metrics to at least get 
+ the community in shape to do the basics (like reporting and releasing). 
+ Without any kind of forcing function I am not sure what the future for this 
+ project really is.
  
  (bdelacretaz) Agreed - I have now provided a mentor report above.
  
@@ -417, +420 @@

  
  Flink is an open source system for expressive, declarative, fast, and
  efficient data analysis. Flink combines the scalability and programming
- flexibility of distributed MapReduce-like platforms with the efficiency, out-
+ flexibility of distributed MapReduce-like platforms with the efficiency, 
- of-core execution, and query optimization capabilities found in parallel
+ out-of-core execution, and query optimization capabilities found in parallel
  databases. Flink was originally known as Stratosphere when it entered the
  Incubator.
  
@@ -426, +429 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. The new name ("Flink") has still not been confirmed by the trademark team.
+   1. The new name ("Flink") has still not been confirmed by the trademark 
+      team.
    2. Setup of release infrastructure and first release
    3. Continue with community growth
  
- Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+ Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware 
+ of?
  
    None.
  
  How has the community developed since the last report?
  
-   Two presentations (Meetup in Nice by a committer, one in Budapest by a contributor), new
users are showing up on the mailing list and on JIRA.
+   Two presentations (Meetup in Nice by a committer, one in Budapest by a 
+   contributor), new users are showing up on the mailing list and on JIRA.
  
  How has the project developed since the last report?
  
-   Most of the infrastructure setup has been done. Users start using the new mailing lists.
+   Most of the infrastructure setup has been done. Users start using the new
-   In the last month, 21 authors have pushed 120 commits to master. On master, 910 files
have changed and there have been 74,313 additions and 37,094 deletions.
+   mailing lists.
+   In the last month, 21 authors have pushed 120 commits to master. On 
+   master, 910 files have changed and there have been 74,313 additions and 
+   37,094 deletions.
  
  Date of last release:
  
@@ -476, +485 @@

  
  Community Developement:
  Apache Kalumet 0.6-incubating version has been released.
- However, due to some misunderstanding, the release vote has not been completed by 3 IPMC.
+ However, due to some misunderstanding, the release vote has not been
- Especially, some legal files issues have been raised.
+ completed by 3 IPMC.  Especially, some legal files issues have been raised.
- We are preparing a 0.6.1-incubating release to fix the legal files and submit to IPMC vote.
+ We are preparing a 0.6.1-incubating release to fix the legal files and
- We are in the way of promoting the documentation on the website.
+ submit to IPMC vote.  We are in the way of promoting the documentation
+ on the website.
  
  Project Development:
- We are preparing the 0.6.1-incubating (plan for July, 14) to fix the legal files issues
raised on 0.6-incubating release and have a complete IPMC vote.
+ We are preparing the 0.6.1-incubating (plan for July, 14) to fix the
+ legal files issues raised on 0.6-incubating release and have a complete
+ IPMC vote.
  We are preparing the 0.7-incubating release with the development changes.
  
  Local branches have been created containing:
@@ -491, +503 @@

  These local branches will be merged on the 0.7-incubating branch (master).
  
  Before Graduation:
-    - The documentation has been updated and aligned with the 0.6-incubating release. The
documentation will be promoted on the website and "linked" in announcement e-mails as soon
as the 0.6.1-incubating release has been voted.
-    - The 0.7-incubating release will fix the graduation issue, especially in term of license
(removal of Echo2 framework for the UI).
+    - The documentation has been updated and aligned with the 0.6-incubating
+    release. The documentation will be promoted on the website and "linked"
+    in announcement e-mails as soon as the 0.6.1-incubating release has
+    been voted.
+    - The 0.7-incubating release will fix the graduation issue, especially
+    in term of license (removal of Echo2 framework for the UI).
  
  Post Graduation:
-   - Kalumet scripts. It's the extension of the "software" concept globally to all Kalumet
resources. It will allow users to create custom deployment/update plan, with a set of fine-grained
steps.
+   - Kalumet scripts. It's the extension of the "software" concept
+   globally to all Kalumet resources. It will allow users to create custom
+   deployment/update plan, with a set of fine-grained steps.
  
- 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 so far.
  
@@ -549, +568 @@

  
    A few new people have started to work actively on the mailing list.
    It is still a small community, and growth is needed.
-   On the positive side we do see certain new individuals starting to contribute continuously
to the project.
+   On the positive side we do see certain new individuals starting to
+   contribute continuously to the project.
  
-   We have been working on blogging, tweeting etc. to create more out-going communication
about MetaModel.
+   We have been working on blogging, tweeting etc. to create more out-going
+   communication about MetaModel.
    We feel that more of such activity is needed.
  
  How has the project developed since the last report?
  
    Apache MetaModel 4.1.0-incubating was released on Jan 21.
-   This time with a new release engineer, which meant that the release instructions were
re-iterated and updated.
+   This time with a new release engineer, which meant that the release
+   instructions were re-iterated and updated.
  
-   Communication on mailing list is improving and we see more diversity of requests.
+   Communication on mailing list is improving and we see more diversity
-   For instance, connectivity to Hadoop and HBase was previously not very active but now
it's is taking a good share of the focus.
+   of requests.
+   For instance, connectivity to Hadoop and HBase was previously not very
+   active but now it's is taking a good share of the focus.
  
  Date of last release:
  
@@ -591, +615 @@

  NPanday has been incubating since 2010-08-13.
  
  Since the last report in April, a few obstacles have been removed:
-  - the status page was updated with the current podling state and correct mentors
+  - the status page was updated with the current podling state and correct
+  mentors
   - svnpubsub was enabled so the website can be updated again
   - a number of JIRA issues have been cleaned up to prepare for the release
  
  Not blocking, but outstanding things to do:
   - resolve issues with Jenkins builds with infrastructure
-  - finish closing out JIRA issues that have been partially finished for release
+  - finish closing out JIRA issues that have been partially finished
+  for release
-  - apply suitable patches that have been overlooked in the past and try to reconnect with
contributors
+  - apply suitable patches that have been overlooked in the past and try
+  to reconnect with contributors
  
  Three most important issues to address in the move towards graduation:
  
-   1. Ship the changes on trunk as a release and make it easier for new users to get up to
speed when interested in the project
-   2. Get a critical mass of committers/PPMC members that can respond to contributors, apply
patches, nominate committers, and vote on releases
+   1. Ship the changes on trunk as a release and make it easier for new
+   users to get up to speed when interested in the project
+   2. Get a critical mass of committers/PPMC members that can respond to
+   contributors, apply patches, nominate committers, and vote on releases
    3. Provide guidance on how to get involved in contributing
  
- The incubator is already aware of the low level of activity, that many of the PPMC are now
disengaged and lack of mentors for the project. Konstantin Boudnik has put his hand up to
help out and that discussion is in progress.
+ The incubator is already aware of the low level of activity, that many of
+ the PPMC are now disengaged and lack of mentors for the project. Konstantin
+ Boudnik has put his hand up to help out and that discussion is in progress.
  
- There continues to be interest in a new release from users, and new interest from some in
making contributions that continue to be followed up.
+ There continues to be interest in a new release from users, and new
+ interest from some in making contributions that continue to be followed up.
  
  Date of last release:
  
    2011-05-16
  
- The last committer was added on 2011-04-19. There have not been any PPMC additions since
inception.
+ The last committer was added on 2011-04-19. There have not been any PPMC
+ additions since inception.
  
  Signed-off-by:
  
@@ -767, +800 @@

  
  Three most important issues
  
-   - Finish bootstrapping project(completed), IP clearance (completed), initial website (in
progress)
+   - Finish bootstrapping project(completed), IP clearance (completed),
+   initial website (in progress)
    - Expanding the community and adding new committers
    - 1st release
  
@@ -795, +829 @@

    - All bootstrap tickets have been completed and status page updated
      - Mailing lists created, Jira setup, Code imported
    - Jira issues starting to be imported to issues.apache.org
-   - Website in the works and will be available soon, infra for this is all ready setup
+   - Website in the works and will be available soon, infra for this is
+   all ready setup
    - Working on documenting contributing guide and committers workflow
-     - We have now setup the mechanisms to accept contributions through the Apache
+     - We have now setup the mechanisms to accept contributions through
-       Github and have already accepted one external contribution.
+     the Apache Github and have already accepted one external contribution.
  
  Date of last release:
  
@@ -833, +868 @@

  The overall decision of what to do with Ripple as an ASF project, and
  whether it can become a sub-project of Cordova is still under discussion.
  
- Additionally, there are discussion threads proposing how to more tightly integrate
+ Additionally, there are discussion threads proposing how to more tightly
- and use Ripple within Cordova.
+ integrate and use Ripple within Cordova.
  
  How has the community developed since the last report?
  
@@ -866, +901 @@

  S4
  
  S4 (Simple Scalable Streaming System) is a general-purpose, distributed,
- scalable, partially fault-tolerant, pluggable platform that allows programmers
+ scalable, partially fault-tolerant, pluggable platform that allows
- to easily develop applications for processing continuous, unbounded streams of
+ programmers to easily develop applications for processing continuous,
- data.
+ unbounded streams of data.
  
  S4 has been incubating since 2011-09-26.
  
@@ -929, +964 @@

  
  How has the community developed since the last report?
  
-   Voted in two new committers/PPMC members, both from outside of the original code contributor.
 Martin Kleppmann presented on the project at Berlin Buzzwords, Sriram Subramanian will be
presenting in Seattle in August.
+   Voted in two new committers/PPMC members, both from outside of the
+   original code contributor.  Martin Kleppmann presented on the project
+   at Berlin Buzzwords, Sriram Subramanian will be presenting in Seattle
+   in August.
  
  How has the project developed since the last report?
  
-   Currently in middle of first incubator release.  94 issues opened in since last reporting
window, 86 resolved.
+   Currently in middle of first incubator release.  94 issues opened in
+   since last reporting window, 86 resolved.
  
  Date of last release:
  
-   Vote for 0.7.0 release has just passed in podling, now being run in Incubator.
+   Vote for 0.7.0 release has just passed in podling, now being run in
+   Incubator.
  
  When were the last committers or PMC members elected?
  
@@ -976, +1016 @@

  
  How has the community developed since the last report?
  
-  * We've made our first ASF-based release and are starting to get people discussing it on
our dev list -our sole mailing list to date. This shows some take up, but it also identifies
the challenge in diagnosing problems. We need to provide more application-side diagnostics
to help both users and ourselves.
+  * We've made our first ASF-based release and are starting to get people
+  discussing it on our dev list -our sole mailing list to date. This
+  shows some take up, but it also identifies the challenge in diagnosing
+  problems. We need to provide more application-side diagnostics to help
+  both users and ourselves.
  
  How has the project developed since the last report?
  
  
-  * As stated, we've made our first ASF release. We plan to do this monthly for the next
few months, to get our release process refined, as
+  * As stated, we've made our first ASF release. We plan to do this
+  monthly for the next few months, to get our release process refined,
- we as evolve the application from users' experiences.
+  as we as evolve the application from users' experiences.
-  * We've fully migrated to the ASF JIRA server, and have been cross-filing issues with sibling
Apache projects -notably YARN- so helping gain awareness of us and our needs. So far the other
projects have been very helpful.
-  * We're trying to contribute some of our changes back into the Hadoop and Bigtop projects
-our workflow YARN services and service launcher to Hadoop; improvements to the test runner
shell for Bigtop. These will spread the benefits of these features, and tighten our relationship
with those projects on which we depend.
+  * We've fully migrated to the ASF JIRA server, and have been cross-filing
+  issues with sibling Apache projects -notably YARN- so helping gain
+  awareness of us and our needs. So far the other projects have been
+  very helpful.
+  * We're trying to contribute some of our changes back into the Hadoop
+  and Bigtop projects -our workflow YARN services and service launcher
+  to Hadoop; improvements to the test runner shell for Bigtop. These will
+  spread the benefits of these features, and tighten our relationship with
+  those projects on which we depend.
  
  
  Date of last release:
@@ -1018, +1070 @@

    2. Resolve relationship with Apache in general
    3. Continue to grow community
  
- 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?
  
- Recently, Usergrid has been through the wars with regards to its development ethos, entire
development process and most importantly code commit process. The latter has been an issue
which resulted in one particular Apache Member having his account temporarily disabled, and
a new contributor workflow that the project believes does satisfy board and infrastructure
requirements:
+ Recently, Usergrid has been through the wars with regards to its
+ development ethos, entire development process and most importantly
+ code commit process. The latter has been an issue which resulted in one
+ particular Apache Member having his account temporarily disabled, and
+ a new contributor workflow that the project believes does satisfy board
+ and infrastructure requirements:
  
      https://cwiki.apache.org/confluence/display/usergrid/Usergrid+Contribution+Workflow
  
- It has not been an easy month for Usergrid however the community spirit is higher than it
ever has been and the community is in a strong position to meet Incubator criteria. An extremely
positive note here is that the Usergrid community has been actively expanding throughout the
above process. This is something we can all learn from.
+ It has not been an easy month for Usergrid however the community spirit is
+ higher than it ever has been and the community is in a strong position
+ to meet Incubator criteria. An extremely positive note here is that
+ the Usergrid community has been actively expanding throughout the above
+ process. This is something we can all learn from.
  
  How has the community developed since the last report?
  
- The Usergrid community has been growing steadily and very encouragingly based on community
VOTE's. We welcome contributions to Usergrid. Most importantly, many members of the existing
Usergrid PPMC have been (extremely) actively involved in Usergrid's dissemination and expansion.
+ The Usergrid community has been growing steadily and very encouragingly
+ based on community VOTE's. We welcome contributions to Usergrid. Most
+ importantly, many members of the existing Usergrid PPMC have been
+ (extremely) actively involved in Usergrid's dissemination and expansion.
  
   * 74 subscribed to dev@
  
  How has the project developed since the last report?
  
- Many, many commits. Usergrid is very healthy with regards to its development. What needs
to be addressed however is the following:
+ Many, many commits. Usergrid is very healthy with regards to its
+ development. What needs to be addressed however is the following:
  
   * Resolve commit process... MAJOR
   * Reflect commit messages to commit@
  
  Date of last release:
  
-   Usergrid (incubating) has not made an official release as of date. The community areactively
working towards a release for 1.0.
+   Usergrid (incubating) has not made an official release as of date. The
+   community areactively working towards a release for 1.0.
  
  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