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 "February2015" by MarvinHumphrey
Date Sat, 07 Feb 2015 02:16:41 GMT
Dear Wiki user,

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

The "February2015" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/February2015?action=diff&rev1=58&rev2=59

Comment:
Normalize formatting. (whitespace, URLs)

  {{{
  Incubator PMC report for February 2015
  
- 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.
  
  < narrative >
  
@@ -209, +209 @@

  
  How has the project developed since the last report?
  
- The majority of effort has been around stabilization for the upcoming
+   The majority of effort has been around stabilization for the upcoming
- release.
+   release.
  
- We're pleased to have seen some new folks show up and contribute bug
+   We're pleased to have seen some new folks show up and contribute bug
- reports and patches.
+   reports and patches.
  
  Date of last release:
  
@@ -237, +237 @@

  Corinthia
  
  Corinthia is a toolkit/application for converting between and editing common
- office file formats, with an initial focus on word processing. It is designed
+ office file formats, with an initial focus on word processing. It is
- to cater for multiple classes of platforms - desktop, web, and mobile - and
+ designed to cater for multiple classes of platforms - desktop, web, and
- relies heavily on web technologies such as HTML, CSS, and JavaScript for
+ mobile - and relies heavily on web technologies such as HTML, CSS, and
- representing and manipulating documents. The toolkit is small, portable, and
+ JavaScript for representing and manipulating documents. The toolkit is
- flexible, with minimal dependencies. The target audience is developers wishing
- to include office viewing, conversion, and editing functionality into their
- applications.
+ small, portable, and flexible, with minimal dependencies. The target
+ audience is developers wishing to include office viewing, conversion, and
+ editing functionality into their applications.
  
  Corinthia has been incubating since 2014-12-08.
  
@@ -261, +261 @@

  
  How has the community developed since the last report?
  
- January has been a rather quit month, Dave Fisher joined as PPM/Committer (was Mentor)
+   January has been a rather quit month, Dave Fisher joined as PPM/Committer
+   (was Mentor)
  
  
  How has the project developed since the last report?
  
- Work is progressing on restructuring the filter development and 64bit testing is ongoing
+   Work is progressing on restructuring the filter development and 64bit
+   testing is ongoing
  
- research of similar program has been structured in jira issues.
+   research of similar program has been structured in jira issues.
  
  Date of last release:
  
@@ -276, +278 @@

  
  When were the last committers or PMC members elected?
  
- 2015-01-17 Dave Fisher added as PPMC/Committer
+   2015-01-17 Dave Fisher added as PPMC/Committer
- 
  
  Signed-off-by:
  
@@ -305, +306 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- None. 
+   None. 
  
- We need to continue the name search. Branding has replied to the issue
+   We need to continue the name search. Branding has replied to the issue and
- and provided additional searches that need to performed. It is hoped
+   provided additional searches that need to performed. It is hoped that
- that these can be finished in the new couple weeks.
+   these can be finished in the new couple weeks.
  
  How has the community developed since the last report?
  
@@ -350, +351 @@

  
    1. Continue to grow the HTrace community
    2. Continue to develop and release stable HTrace incubating artifacts
-   3. Continue to explore the integration of the HTrace framework into other Apache products
+   3. Continue to explore the integration of the HTrace framework into other
+      Apache products
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- Around January 20th HTrace successfully made the first release whilst in the Apache Incubator.
+   Around January 20th HTrace successfully made the first release whilst in
- This was the outcomes of no-less than 10 release candidates and as many VOTE's.
- In all every release candidate was very well managed with HTrace community providing
+   the Apache Incubator.  This was the outcomes of no-less than 10 release
+   candidates and as many VOTE's.  In all every release candidate was very
+   well managed with HTrace community providing excellent feedback to the
- excellent feedback to the release manager. Rather than then entire 10 release candidate
exercise
+   release manager. Rather than then entire 10 release candidate exercise
- being a pain point for the community, it appears to have strengthened all involved. Well
done
+   being a pain point for the community, it appears to have strengthened all
- HTrace.
+   involved. Well done HTrace.
  
- How has the community developed since the last report?
- 
- It is early incubating days for HTrace. The community has attracted in particular a new
member
- who is doing a sterling job on a new UI for HTrace. Additionally it should be noted that
- the entire htrace-3.1.0-incubating release effort
- has certainly brought the existing community on leaps and bounds.
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   It is early incubating days for HTrace. The community has attracted in
+   particular a new member who is doing a sterling job on a new UI for
+   HTrace. Additionally it should be noted that the entire
+   htrace-3.1.0-incubating release effort has certainly brought the existing
+   community on leaps and bounds.
+ 
+ How has the project developed since the last report?
+ 
- The project has progressed significantly. In fact, it was highlighted on at least one
+   The project has progressed significantly. In fact, it was highlighted on
- occasion that documentation supporting a release candidate should be further clarified/improved
- due to the dynamic progressive nature of the HTrace codebase. As an early incubating project
- this is accepted as a positive move.
+   at least one occasion that documentation supporting a release candidate
+   should be further clarified/improved due to the dynamic progressive nature
+   of the HTrace codebase. As an early incubating project this is accepted as
+   a positive move.
  
  Date of last release:
  
@@ -382, +387 @@

  
  When were the last committers or PMC members elected?
  
- ???
+   ???
  
  Signed-off-by:
  
@@ -418, +423 @@

  
  How has the community developed since the last report?
  
-   1. Kylin topic has been confirmed to present at Strata+Hadoop World 2015 London, 
+   1. Kylin topic has been confirmed to present at Strata+Hadoop World 2015
- also proposed to HBaseCon, Hadoop Summit and Big Data Technology Conference 2015 Beijing
+      London, also proposed to HBaseCon, Hadoop Summit and Big Data
+      Technology Conference 2015 Beijing
    2. Offical twitter account created: @ApacheKylin 
-     * Followers 173
+      * Followers 173
    3. Issue backlog status since last report:
-     * Created:   587 (including imported from github.com)
+      * Created:   587 (including imported from github.com)
-     * Resolved:  283 (including imported from github.com)
+      * Resolved:  283 (including imported from github.com)
    4. Mailing list activity since last report:
-     * @dev      227 messages
+      * @dev      227 messages
    5. Github activity:
-     * Star 405
+      * Star 405
-     * Fork 172
+      * Fork 172
-     * Contributors 17
+      * Contributors 17
  
  How has the project developed since the last report?
  
    1. Kylin website is available on http://kylin.incubator.apache.org
-   2. Making changes in build and packaging with respect to apache release process
+   2. Making changes in build and packaging with respect to apache release
+      process
-   3. Development are happening on v0.7.1 version which we are preparing for first release.
+   3. Development are happening on v0.7.1 version which we are preparing for
+      first release.
  
  Date of last release:
  
@@ -456, +464 @@

  
  
  
+ --------------------
  Lens
  
  Lens is a platform that enables multi-dimensional queries in a unified way
@@ -467, +476 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Make the first release from apache: the 2.0-incubating release is in progress
+   1. Make the first release from apache: the 2.0-incubating release is in
+       progress
    2. Reach out to people through presentations and blogs
    3. Establish whether "Apache Lens" is a suitable name
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
-   Establish whether "Apache Lens" is a suitable name via PODLINGNAMESEARCH-63
+   Establish whether "Apache Lens" is a suitable name via
+   PODLINGNAMESEARCH-63
  
  How has the community developed since the last report?
  
@@ -484, +495 @@

  How has the project developed since the last report?
  
   * Main activities include
-    ** Stabilizing the api and code for first stable release
+    * Stabilizing the api and code for first stable release
-    ** Doing changes in build and packaging with respect to apache release process
+    * Doing changes in build and packaging with respect to apache release
+      process
-    ** Setting up regression suite for the project
+    * Setting up regression suite for the project
   * Mailing list activity :
-  ** Dev via http://mail-archives.apache.org/mod_mbox/incubator-lens-dev/
+    * Dev
-  *** Janauary - 1011 messsages
+      * Janauary - 1011 messsages
-  ** Commits via http://mail-archives.apache.org/mod_mbox/incubator-lens-commits/
+    * Commits
-  *** January - 43 messages
+      * January - 43 messages
-  ** User mailing list activity - None
+    * User mailing list activity - None
  
-  * Issues 70 created and 46 resolved via 30 day summary from https://issues.apache.org/jira/browse/LENS/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
+  * Issues 70 created and 46 resolved via 30 day summary from LENS Jira.
  
+ Date of last release:
+ 
- Date of last release: NONE.  2.0.0-incubating release process is in progress.
+   NONE.  2.0.0-incubating release process is in progress.
  
- 
- When were the last committers or PMC members elected? 2014-12-24
+ When were the last committers or PMC members elected?
  
+   2014-12-24
  
  Signed-off-by:
  
@@ -522, +536 @@

  Three most important issues to address in the move towards graduation:
  
    1. Grow our community.
-   2. Establish rhythm for releases, review processes, and document how to most effectively
bring on new committers.
+   2. Establish rhythm for releases, review processes, and document how to
+      most effectively bring on new committers.
    3. Update our release process with items learned from initial release.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -534, +549 @@

  
    We have a new PPMC member - Jenn Barnabee.
  
-   We continue to receive patches, code ideas, and bug reports from the community.  Notable
+   We continue to receive patches, code ideas, and bug reports from the
-   contributions during this reporting period outside the PPMC and committer base include
a
+   community.  Notable contributions during this reporting period outside the
+   PPMC and committer base include a new website design, code which will
-   new website design, code which will automate much of the documentation production, and
refactoring to improve code reuse.
+   automate much of the documentation production, and refactoring to improve
+   code reuse.
  
-   The dev mailing list has grown from 62 to 80 in the last report (commits has grown to
29).
+   The dev mailing list has grown from 62 to 80 in the last report (commits
+   has grown to 29).
  
  How has the project developed since the last report?
  
-   We have successfully produced our first release within the Apache Incubator!
+   We have successfully produced our first release within the Apache
+   Incubator!
  
  Date of last release:
  
@@ -570, +589 @@

      Apache. Excellent job honing the release process and keeping
      up the momentum with the Release Candidates.
  
- 
  --------------------
  NPanday
  
@@ -619, +637 @@

  REEF
  
  REEF (Retainable Evaluator Execution Framework) is a scale-out computing
- fabric that eases the development of Big Data applications on top of resource
+ fabric that eases the development of Big Data applications on top of
- managers such as Apache YARN and Mesos.
+ resource managers such as Apache YARN and Mesos.
  
  REEF has been incubating since 2014-08-12.
  
@@ -683, +701 @@

  
  Ripple is a browser based mobile phone emulator designed to aid in the
  development of HTML5 based mobile applications.  Ripple is a cross platform
- and cross runtime testing/debugging tool. It currently supports such runtimes
+ and cross runtime testing/debugging tool. It currently supports such
- as Cordova, WebWorks aand the Mobile Web.
+ runtimes as Cordova, WebWorks aand the Mobile Web.
  
  Ripple has been incubating since 2012-10-16.
  
@@ -730, +748 @@

  
  SAMOA provides a collection of distributed streaming algorithms for the most
  common data mining and machine learning tasks such as classification,
- clustering, and regression, as well as programming abstractions to develop new
+ clustering, and regression, as well as programming abstractions to develop
- algorithms that run on top of distributed stream processing engines (DSPEs).
+ new algorithms that run on top of distributed stream processing engines
- It features a pluggable architecture that allows it to run on several DSPEs
+ (DSPEs).  It features a pluggable architecture that allows it to run on
- such as Apache Storm, Apache S4, and Apache Samza.
+ several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
  
  SAMOA has been incubating since 2014-12-15.
  
@@ -746, +764 @@

  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?
  
- We have started using the official Apache channels to discuss about SAMOA.
+   We have started using the official Apache channels to discuss about SAMOA.
- A couple of new people have showed up on the mailing lists.
+   A couple of new people have showed up on the mailing lists.  We have one
- We have one new contributor submitting patches.
+   new contributor submitting patches.
  
- Mailing list activity (since January 2015):
+   Mailing list activity (since January 2015):
+ 
- * @dev      101 messages
+   * @dev      101 messages
  
- Jira issues backlog (since January 2015):
+   Jira issues backlog (since January 2015):
+ 
- * Created:  13
+   * Created:  13
- * Resolved: 2
+   * Resolved: 2
  
  How has the project developed since the last report?
  
- The project setup is going on nicely.
- We got the SGA from Yahoo and migrated the code to the Apache git repository,
- enabled GitHub integration (https://github.com/apache/incubator-samoa),
- migrated the website to the Apache infrastructure and added the Incubator branding (http://samoa.incubator.apache.org),
- enabled testing via Travis CI.
+   The project setup is going on nicely.  We got the SGA from Yahoo and
+   migrated the code to the Apache git repository, enabled GitHub integration
+   (https://github.com/apache/incubator-samoa), migrated the website to the
+   Apache infrastructure and added the Incubator branding
+   (http://samoa.incubator.apache.org), enabled testing via Travis CI.
  
  Date of last release:
  
- None
+   None
  
  When were the last committers or PMC members elected?
  
- None
+   None
  
  Signed-off-by:
  
@@ -804, +824 @@

  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?
- 
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
- Some refactoring of the UI.
- A contributor made some development to have some features still working with java 1.5
+ 
+ 
+ How has the project developed since the last report?
+ 
+   Some refactoring of the UI.  A contributor made some development to have
+   some features still working with java 1.5
  
  Date of last release:
  
@@ -846, +866 @@

  Three most important issues to address in the move towards graduation:
  
    1. Building a diverse developer and user community
-   2. Achieving broader adoption of the existing code and slider-deployable applications
(examples: HBase, Accumulo)
+   2. Achieving broader adoption of the existing code and slider-deployable
+      applications (examples: HBase, Accumulo)
-   3. Making slider better at deploying other applications, so improving takeup.
+   3. Making slider better at deploying other applications, so improving
+      takeup.
  
  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?
- 
- We're getting more people on the mailing list asking for improvements; anyone with a patch
is being helped to get it in. That builds up the developer base and is intended to move it
from a single team to one distributed community development.
- As we grow, we're proposing moving from a single slider developer list to:a separate user
mailing list, and a third list for the JIRA/svn/git events. This will focus the developer
list around discussion, with a user list to help build that user community. We do of course
expect developers to also subscribe to the user list.
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
- We've done a source-only release in November, 0.60.0-incubating, in sync with features in
Hadoop 2.6, with a binary packing version, 0.61.0-incubating has just been voted for release
(3-feb 2015); the incubator vote is now pending. It was nice to see tests and a vote on the
release from an external user & patch submitter -community engagement includes things
like this.
+   We're getting more people on the mailing list asking for improvements;
+   anyone with a patch is being helped to get it in. That builds up the
+   developer base and is intended to move it from a single team to one
+   distributed community development.  As we grow, we're proposing moving
+   from a single slider developer list to:a separate user mailing list, and a
+   third list for the JIRA/svn/git events. This will focus the developer list
+   around discussion, with a user list to help build that user community. We
+   do of course expect developers to also subscribe to the user list.
  
- A new release, 0.70 is being created with the release planned mid-February. This will include
improved features and fixes —especially those reported by users of the 0.60 release. For
example, one group wanted short-lived applications on secure clusters, instances where Slider
does not need to worry about keytab expiry. Another need of people writing slider-deployed
applications was for a placement policy of "only ever ask for component placement where instances
were before"; this is needed for Kafka.
+ How has the project developed since the last report?
  
- Some of the feature requests are quite "ambitious", especially those related to deployed
components providing information back to the Web/REST GUIs, and extending the configuration
model to include: more on-target-machine configuration, per-instance configuration and better
strategies for placing components within the YARN cluster. These requests do represent real
needs; even if they are long term features we need to think about how to get there.
+   We've done a source-only release in November, 0.60.0-incubating, in sync
+   with features in Hadoop 2.6, with a binary packing version,
+   0.61.0-incubating has just been voted for release (3-feb 2015); the
+   incubator vote is now pending. It was nice to see tests and a vote on the
+   release from an external user & patch submitter -community engagement
+   includes things like this.
  
- We're discussing supplementing the dev@ mailing list with issues@ and user@ lists; the issues
list for all JIRA updates -creation and completion would still go to the developer list. This
is to separate the noise of JIRA-centric development from a developer list focused on broader
application features and building a community. We don't want to scare people off from too
much JIRA, or worse: lose what they have to say in the emails. Similarly, the user@ list is
where we want to encourage users. The original rationale for a single list was "one single
community discussion", but it's not clear its worked out that way.
+   A new release, 0.70 is being created with the release planned
+   mid-February. This will include improved features and fixes —especially
+   those reported by users of the 0.60 release. For example, one group wanted
+   short-lived applications on secure clusters, instances where Slider does
+   not need to worry about keytab expiry. Another need of people writing
+   slider-deployed applications was for a placement policy of "only ever ask
+   for component placement where instances were before"; this is needed for
+   Kafka.
  
+   Some of the feature requests are quite "ambitious", especially those
+   related to deployed components providing information back to the Web/REST
+   GUIs, and extending the configuration model to include: more
+   on-target-machine configuration, per-instance configuration and better
+   strategies for placing components within the YARN cluster. These requests
+   do represent real needs; even if they are long term features we need to
+   think about how to get there.
+ 
+   We're discussing supplementing the dev@ mailing list with issues@ and
+   user@ lists; the issues list for all JIRA updates -creation and completion
+   would still go to the developer list. This is to separate the noise of
+   JIRA-centric development from a developer list focused on broader
+   application features and building a community. We don't want to scare
+   people off from too much JIRA, or worse: lose what they have to say in the
+   emails. Similarly, the user@ list is where we want to encourage users. The
+   original rationale for a single list was "one single community
+   discussion", but it's not clear its worked out that way.
  
  Date of last release:
  
@@ -878, +930 @@

  
  When were the last committers or PMC members elected?
  
- September 2014, new committer, Gour Saha (works at hortonworks)
+   September 2014, new committer, Gour Saha (works at hortonworks)
  
  Signed-off-by:
  
@@ -910, +962 @@

  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?
  
-  Reinhard Sandtner was successfully elected to join as a new committer, PPMC member.
+   Reinhard Sandtner was successfully elected to join as a new committer,
-  During Zurich Hackergarten we implemented the backport of the current Java 8
+   PPMC member.  During Zurich Hackergarten we implemented the backport of
-  core implementation. 
+   the current Java 8 core implementation. 
  
  How has the project developed since the last report?
  
-  We identified a minimalistic but extendible API. Basic implementation work for
+   We identified a minimalistic but extendible API. Basic implementation work
-  Java 8 and Java 7 is ongoing, but makes overall good progress.
+   for Java 8 and Java 7 is ongoing, but makes overall good progress.
  
  Date of last release:
  
@@ -956, +1008 @@

    2. Release - understand/document release process
    3. Grow community -- need to move forward from bootstrapping/IP issues
  
- 
  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?
@@ -1006, +1056 @@

  
  Shepherd/Mentor notes:
  
+   Andy Seaborne (andy):
+   
- andy: Taverna remained on the monthly reporting cycle because the Software Grant
+     Taverna remained on the monthly reporting cycle because the Software
-       had not been received.  If it arrives as per schedule, Taverna can go onto
+     Grant had not been received.  If it arrives as per schedule, Taverna can
-       its normal reporting cycle.
+     go onto its normal reporting cycle.
  
- Drew Farris (drew):
+   Drew Farris (drew):
  
-       Podling is active, 2 mentors participating on the mailing lists.
+     Podling is active, 2 mentors participating on the mailing lists.
  
  --------------------
  TinkerPop
@@ -1030, +1082 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- We have been hanging on the software grant approval for a week now. Be good to get that
knocked out so we can move forward.
+   We have been hanging on the software grant approval for a week now. Be
+   good to get that knocked out so we can move forward.
  
- How has the community developed since the last report?
- 
- N/A
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
- N/A
+   N/A
  
+ How has the project developed since the last report?
+ 
+   N/A
  
  Date of last release:
  
@@ -1064, +1116 @@

  --------------------
  Twill
  
- Twill is an abstraction over Apache Hadoop YARN that reduces the complexity of
+ Twill is an abstraction over Apache Hadoop YARN that reduces the complexity
- developing distributed applications, allowing developers to focus more on
+ of developing distributed applications, allowing developers to focus more on
  their business logic
  
  Twill has been incubating since 2013-11-14.
@@ -1076, +1128 @@

    2. Regular releases.
    3. Increase adoption.
  
- 
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
    - None at this time.
- 
  
  How has the community developed since the last report?
  
@@ -1089, +1139 @@

    - 12 JIRA issues resolved since last report (2014-11-01)
    - 3 new contributors submitted patches
  
- 
  How has the project developed since the last report?
  
    - Version 0.4.1-incubating RC3 being voted upon
  
- 
  Date of last release:
  
    - 2014-11-17: 0.4.0-incubating
  
- 
  When were the last committers or PMC members elected?
  
    - No new committers since incubation.
- 
  
  Signed-off-by:
  
@@ -1130, +1176 @@

    3. Complete PODLINGNAMESEARCH-64
  
  
- 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?
  
-   We've received several patches from contributors outside of the initial committers list.
+   We've received several patches from contributors outside of the initial
-   They are also participating in some discussions @dev
+   committers list.  They are also participating in some discussions @dev
- 
  
  How has the project developed since the last report?
  
    All code base is ready to be migrated.
  
-   The project is waiting for the Software Grant from NFLabs legal department.
+   The project is waiting for the Software Grant from NFLabs legal
+   department.
  
-   Major features implemented are: custom Zeppelin interpreters-to-note binding and dynamic
.jar dependency loading
+   Major features implemented are: custom Zeppelin interpreters-to-note
+   binding and dynamic .jar dependency loading
  
  Date of last release:
  
@@ -1155, +1203 @@

  When were the last committers or PMC members elected?
  
    None since incubation
- 
  
  Signed-off-by:
  

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


Mime
View raw message