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 "June2016" by MarvinHumphrey
Date Fri, 03 Jun 2016 19:05:39 GMT
Dear Wiki user,

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

The "June2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/June2016?action=diff&rev1=63&rev2=64

Comment:
Reflow.

      accepted/merged 51 PRs
    * We voted on the following matters according to Apache guidelines:
       * We voted to make all current and future committers part of the PPMC
-      * We voted in a new committer and PPMC member : Steven Yvinec-Kruyk and he accepted
+      * We voted in a new committer and PPMC member : Steven Yvinec-Kruyk and
+        he accepted
-      * We voted in a commit policy of "RTC with a +1 vote from a committer other than the
author (assuming no vetos)"
+      * We voted in a commit policy of "RTC with a +1 vote from a committer
+        other than the author (assuming no vetos)"
  
  How has the project developed since the last report?
  
-   * All resources have been created and all migrations are complete - code donation included
+   * All resources have been created and all migrations are complete - code
+     donation included
    * The website is in progress
  
  Date of last release:
@@ -200, +203 @@

  
  When were the last committers or PMC members elected?
  
-   On May 20, 1 committer/PPMC member(Steven Yvinec-Kruyk) was elected and he accepted.
+   On May 20, 1 committer/PPMC member(Steven Yvinec-Kruyk) was elected and he
+   accepted.
  
- 
  Signed-off-by:
  
-   [](airflow) Chris Nauroth
+   [ ](airflow) Chris Nauroth
    [x](airflow) Hitesh Shah
    [x](airflow) Jakob Homan
  Shepherd/Mentor notes:
@@ -226, +229 @@

  
    1. Podling name search is pending.
    2. Expand the community and add more committers.
-   3. The upcoming release for Atlas (0.7-incubating) will be nearly 6 months since the last
one. We would like to improve on this by making more frequent releases, and also encourage
the community to discuss in release roadmaps etc.
+   3. The upcoming release for Atlas (0.7-incubating) will be nearly 6 months
+      since the last one. We would like to improve on this by making more
+      frequent releases, and also encourage the community to discuss in
+      release roadmaps etc.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- No specific issues at this time to report.
+   No specific issues at this time to report.
  
- How has the community developed since the last report?
- 
-   1. The user/dev community show increasing interests. In the last two months, the average
number of messages has increased to more than 900 messages per month, from an average of 400
per month in the last report.
-   2. Around 7 contributors were added, number of contributors is at 49 currently. Community
is more widespread with more organizations participating in the project.
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
-   1. We are working towards a 0.7-incubating release around the next month. This release
will include several new features to make Atlas enterprise ready including: Authentication
and authorization support, High availability, deeper integrations with other Hadoop components
including Hive, HDFS, Falcon etc., Entity versioning, support for rolling upgrade, support
for creating business taxonomies, enhanced user interface, better performance etc.
-   2. There are more strategic contributions coming in to make the system agnostic to the
underlying graph database version, and improve horizontal scalability.
+   1. The user/dev community show increasing interests. In the last two
+      months, the average number of messages has increased to more than 900
+      messages per month, from an average of 400 per month in the last
+      report.
+   2. Around 7 contributors were added, number of contributors is at 49
+      currently. Community is more widespread with more organizations
+      participating in the project.
+ 
+ How has the project developed since the last report?
+ 
+   1. We are working towards a 0.7-incubating release around the next month.
+      This release will include several new features to make Atlas enterprise
+      ready including: Authentication and authorization support, High
+      availability, deeper integrations with other Hadoop components
+      including Hive, HDFS, Falcon etc., Entity versioning, support for
+      rolling upgrade, support for creating business taxonomies, enhanced
+      user interface, better performance etc.
+   2. There are more strategic contributions coming in to make the system
+      agnostic to the underlying graph database version, and improve
+      horizontal scalability.
-   3. A total of 216 issues were reported between April 1st 2016 and May 30th 2016. 84 have
been resolved in the same time.
+   3. A total of 216 issues were reported between April 1st 2016 and May 30th
+      2016. 84 have been resolved in the same time.
  
  Date of last release:
  
@@ -251, +271 @@

  When were the last committers or PMC members elected?
  
    1. Suma Shivaprasad was added as a PPMC member on 2016-05-03.
-   2. Hemanth Yamijala was added as a committer on 2016-04-14 and PPMC member on 2016-04-29.
+   2. Hemanth Yamijala was added as a committer on 2016-04-14 and PPMC member
+      on 2016-04-29.
  
  Signed-off-by:
  
@@ -332, +353 @@

       towards next versions of the Commons API.
    3. Re-engage and grow the Commons RDF community base.
  
- 
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
@@ -404, +424 @@

  Three most important issues to address in the move towards graduation:
  
    1. Attract new contributors.
-   2. Establish an Apache website for Fluo that makes it easy for new users and contributors
to get started.
+   2. Establish an Apache website for Fluo that makes it easy for new users
-   3. Do a release.  We should be able to start working on our first release as soon as we
are fully established on Apache infrastructure
+      and contributors to get started.
+   3. Do a release.  We should be able to start working on our first release
+      as soon as we are fully established on Apache infrastructure
  
  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?
  
-  The community is the same as when it started incubation a few weeks ago.
+   The community is the same as when it started incubation a few weeks ago.
  
  How has the project developed since the last report?
  
-  This is the first Fluo report.  We are trying to get established within Apache infrastructure.
 Mailing lists are setup.  Need to import code.  We are working with INFRA to explore using
Github for issue tracking.  See INFRA-11900.
+   This is the first Fluo report.  We are trying to get established within
+   Apache infrastructure.  Mailing lists are setup.  Need to import code.  We
+   are working with INFRA to explore using Github for issue tracking.  See
+   INFRA-11900.
  
  Date of last release:
  
@@ -470, +495 @@

  
    - Package renaming completed.
    - New logos submitted - reasonable number to finally vote on.
-   - Continued integration within Apache Beam (Gearpump Runner). PR submitted.
+   - Continued integration within Apache Beam (Gearpump Runner). PR
+     submitted.
-   - Continued integration within akka-streams (Gearpump Materializer). PR submitted.
+   - Continued integration within akka-streams (Gearpump Materializer). PR
+     submitted.
    - Release pending this month. Over a dozen JIRA's fixed.
  
  Date of last release:
@@ -501, +528 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Establish an Apache website for Gossip that makes it easy for new users and contributors
to get started.
+   1. Establish an Apache website for Gossip that makes it easy for new users
+      and contributors to get started.
-   2. Facilitate discussions and build the protocol specification and implementation
+   2. Facilitate discussions and build the protocol specification and
+      implementation
    3. Produce a usable release
  
  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?
  
-  The community is the same as when it started incubation a few weeks ago.
+   The community is the same as when it started incubation a few weeks ago.
  
  How has the project developed since the last report?
  
-  This is our first report. We have imported the code from github. We are online. We have
had good discussions on the dev list that have spawned a couple of tickets. One is in the
review stage now. Taylor has been an enormous help.
+   This is our first report. We have imported the code from github. We are
+   online. We have had good discussions on the dev list that have spawned a
+   couple of tickets. One is in the review stage now. Taylor has been an
+   enormous help.
  
  Date of last release:
  
@@ -525, +556 @@

  
  When were the last committers or PMC members elected?
  
-  Never
+   Never
  
  Signed-off-by:
  
@@ -601, +632 @@

  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?
- 
- Presentation at ApacheCon 2016 - good suggestions from Anatole Tresch in moving iota forward.
Have additional potential committer
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   Presentation at ApacheCon 2016 - good suggestions from Anatole Tresch in
+   moving iota forward. Have additional potential committer
+ 
+ How has the project developed since the last report?
+ 
- Code is now being uploaded as well as requirements documents
+   Code is now being uploaded as well as requirements documents
  
  Date of last release:
  
@@ -650, +682 @@

    project to attic unless it is able to release in the next few months. No
    release happened since then.
  
-   The project would like to have some kind of maintenance mode within Apache,
+   The project would like to have some kind of maintenance mode within
-   where things like community growth and releases are not that important,
+   Apache, where things like community growth and releases are not that
-   as long there's a bit of support provided and "anyone" is still alive. The
+   important, as long there's a bit of support provided and "anyone" is still
-   problem with attic is the read-only state of the repo, which makes it
+   alive. The problem with attic is the read-only state of the repo, which
-   impossible to do anything (even if it's rare).
+   makes it impossible to do anything (even if it's rare).
  
  How has the community developed since the last report?
  
@@ -729, +761 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- There are no issues requiring board attention at this time
+   There are no issues requiring board attention at this time
  
- How has the community developed since the last report?
- 
- Yanping and Gary presented Mnemonic project at ApacheCon Big Data Conference. Yanping presented
at In-Memory Computing Summit. Both talks were well received. Several developers approached
us to ask additional details on how Mnemonic worked for Spark. They are interested to see
if we are able to successfully integrate Mnemonic into other projects.
- While we are focusing on develop new features, we will try to contact other projects' communities
to explore integration opportunities. As the official release is done this month, for the
next 3 months we expect integration activities will be increased.
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   Yanping and Gary presented Mnemonic project at ApacheCon Big Data
+   Conference. Yanping presented at In-Memory Computing Summit. Both talks
+   were well received. Several developers approached us to ask additional
+   details on how Mnemonic worked for Spark. They are interested to see if we
+   are able to successfully integrate Mnemonic into other projects.
+ 
+   While we are focusing on develop new features, we will try to contact
+   other projects' communities to explore integration opportunities. As the
+   official release is done this month, for the next 3 months we expect
+   integration activities will be increased.
+ 
+ How has the project developed since the last report?
+ 
- We have been focusing the first Apache release over the past weeks.
+   We have been focusing the first Apache release over the past weeks.
- We also explored ideas on design native computing layer which will further enhance durable
Java object model on large non-volatile memory.
+ 
+   We also explored ideas on design native computing layer which will further
+   enhance durable Java object model on large non-volatile memory.
  
  Date of last release:
  
@@ -748, +789 @@

  
  When were the last committers or PMC members elected?
  
- No election, the project is still in early stage of developing.
+   No election, the project is still in early stage of developing.
  
  Signed-off-by:
  
@@ -779, +820 @@

  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?
  
- There were no new developers or new committers since our last report.
+   There were no new developers or new committers since our last report.
  
  How has the project developed since the last report?
  
- We had a new release on March 2nd. It included various bug fixes and
+   We had a new release on March 2nd. It included various bug fixes and
- performance improvements. The most important new feature in the new
+   performance improvements. The most important new feature in the new
- release is support for incremental query processing in MRQL streaming,
+   release is support for incremental query processing in MRQL streaming,
- called Incremental MRQL. There was very little activity on JIRA after
+   called Incremental MRQL. There was very little activity on JIRA after the
- the release (only 4 JIRA issues were reported and fixed).
+   release (only 4 JIRA issues were reported and fixed).
  
  Date of last release:
  
@@ -814, +855 @@

  --------------------
  Myriad
  
- Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on
+ Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
- the same cluster and allows dynamic resource allocations across both Hadoop
+ on the same cluster and allows dynamic resource allocations across both
- and other applications running on the same physical data center
+ Hadoop and other applications running on the same physical data center
  infrastructure.
  
  Myriad has been incubating since 2015-03-01.
@@ -825, +866 @@

  
    1. Develop project roadmap for longer term community/user engagement.
    2. Release frequently - 0.2.0 is underway, but has taken ~6 months since
- last release.
+      last release.
    3. Expand community - users/contributors/committers.
  
  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?
+ 
    * dev@ mailing list experienced a low in March, but picked up traffic
- leading up to 0.2.0 release. 141 messages since the last report.
+     leading up to 0.2.0 release. 141 messages since the last report.
    * 5 new members on the dev@ mailing list. 2 new contributors.
    * Myriad was presented at ApacheCon Vancouver and at couple of other
- meetups. Talks submitted at various conferences.
+     meetups. Talks submitted at various conferences.
    * Bi-weekly dev syncs happening steadily. Approx. 4-7 members
- participate. Minutes at http://s.apache.org/8kF
+     participate. Minutes at http://s.apache.org/8kF
  
  How has the project developed since the last report?
+ 
    * Myriad 0.2.0 out for PPMC voting. DarinJ is driving the release.
    * 12 commits since 4/1.
    * 13 JIRAs fixed/resolved.
@@ -870, +913 @@

  --------------------
  Omid
  
- Omid is a flexible, reliable, high performant and scalable ACID transactional
+ Omid is a flexible, reliable, high performant and scalable ACID
- framework that allows client applications to execute transactions on top of
- MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
+ transactional framework that allows client applications to execute
+ transactions on top of MVCC key/value-based NoSQL datastores (currently
- Snapshot Isolation guarantees on the accessed data.
+ Apache HBase) providing Snapshot Isolation guarantees on the accessed data.
  
  Omid has been incubating since 2016-03-28.
  
  Three most important issues to address in the move towards graduation:
  
-   1. Code and documentation successfully moved into the Apache infrastructure 
+   1. Code and documentation successfully moved into the Apache
+      infrastructure (See
-      (See https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git & http://omid.incubator.apache.org/)
+      https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git &
+      http://omid.incubator.apache.org/)
+   2. Prepared release guide
-   2. Prepared release guide (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+process),

+      (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+process), 
+      first release (0.8.2) under Apache
-      first release (0.8.2) under Apache (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+0.8.2.0)

+      (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+0.8.2.0) 
       and upload binaries to Maven Central
    3. Active collaboration started with another Apache community: Apache Hive
  
@@ -895, +942 @@

  
    * Talk submitted to Hadoop Summit. It was accepted and will be 
      presented on 2016-06-29
-   * The Hive community is using Omid to integrate with HBase for their metastore requirements
+   * The Hive community is using Omid to integrate with HBase for their
+     metastore requirements
-   * First contact with the Apache Phoenix community for a possible integration of Omid as
+   * First contact with the Apache Phoenix community for a possible
-     a transaction manager for the SQL layer Phoenix provides
+     integration of Omid as a transaction manager for the SQL layer Phoenix
+     provides
-   * Quarter Stats (from: 2016-05-17 -project moved into Apache- to: 2016-06-03):
+   * Quarter Stats (from: 2016-05-17 -project moved into Apache- to:
+     2016-06-03):
      +---------------------------------------------+
      |   Metric                          | counts  |
      +---------------------------------------------+
@@ -950, +1000 @@

  
  Three most important issues to address in the move towards graduation:
  
- 1. Increasing community involvement: We are focusing on getting
+   1. Increasing community involvement: We are focusing on getting
+      information published on the website to aid the acquisition and
+      orientation of new contributors, as well increasing the number of
+      committers, in order to reduce individual member workload, reduce
+      reliance on any particular member, and to increase project velocity.
+      David Ash was voted in as a committer last month.  There are several
- information
- published on the website to aid the acquisition and orientation of new
- contributors,
- as well increasing the number of committers, in order to reduce
- individual member
- workload, reduce reliance on any particular member, and to increase
- project velocity. David Ash was voted in as a committer last month.
- There are several other committers that may be added in the near future.
+      other committers that may be added in the near future.
- 
- 2. Merging the source code from AT&T, JP Morgan and Oracle and creating
+   2. Merging the source code from AT&T, JP Morgan and Oracle and creating
- POMs. AT&T and JP Morgan source code has been merged and POMs created,
+      POMs. AT&T and JP Morgan source code has been merged and POMs created,
- it needs uploading into the Apache repository. AT&T and JP Morgan ICLAs were received,
but Oracle is taking more time. The IP clearance is on it's way.
- 
+      it needs uploading into the Apache repository. AT&T and JP Morgan ICLAs
+      were received, but Oracle is taking more time. The IP clearance is on
+      it's way.
- 3. Get our first release done.
+   3. Get our first release done.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- None. The efforts to revive the project seem to be paying off and discussions are gaining
traction.
+   None. The efforts to revive the project seem to be paying off and
+   discussions are gaining traction.
  
- How has the community developed since the last report?
- 
- Pam Dragosh, David Ash and Ajith Nair are the active committers at this point. The project
intends to reboot the PPMC which may include removing
- some of the initial commiters who are no longer active. There are, however, several contributors
who could be potentially added as committers in the future.
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   Pam Dragosh, David Ash and Ajith Nair are the active committers at this
+   point. The project intends to reboot the PPMC which may include removing
+   some of the initial commiters who are no longer active. There are,
+   however, several contributors who could be potentially added as committers
+   in the future.
+ 
+ How has the project developed since the last report?
+ 
- 1. Ongoing collective effort to improve project documentation, marketing material for better
visbility and adoption.
+   1. Ongoing collective effort to improve project documentation, marketing
+      material for better visbility and adoption.
- 2. A pending contribution towards PEP implementation is being reviewed and we plan to merge
in these changes soon.
+   2. A pending contribution towards PEP implementation is being reviewed and
- 3. We are looking into design feedback/comments from Nextlabs - a XACML service provider.
We hope to incorporate many of these in the coming weeks.
+      we plan to merge in these changes soon.
+   3. We are looking into design feedback/comments from Nextlabs - a XACML
+      service provider. We hope to incorporate many of these in the coming
+      weeks.
  
  Date of last release:
  
@@ -1019, +1075 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- None at present.
+   None at present.
  
- 
  How has the community developed since the last report?
  
- Just getting started with bootstrapping the podling.
+   Just getting started with bootstrapping the podling.  Mailing lists have
+   been set up, temporary web site and code repositories ditto. We are
- Mailing lists have been set up, temporary web site and
- code repositories ditto. We are working on onboarding
- the new non-Apache committers in the community and
+   working on onboarding the new non-Apache committers in the community and
- having people familiarize themselves with the project.
+   having people familiarize themselves with the project.
  
- 
  How has the project developed since the last report?
+ 
- N/A
+   N/A
- 
  
  Date of last release:
  
    XXXX-XX-XX
  
  When were the last committers or PMC members elected?
+ 
- No new committers have been elected just yet, as we
+   No new committers have been elected just yet, as we just got started.
- just got started.
- 
  
  Signed-off-by:
  
@@ -1083, +1135 @@

  How has the community developed since the last report?
  
    We have added two new committers and PPMC members, Kathy Saunders and
-   Queenie Ma. Kathy has taken the lead on the name search process for Quarks,
+   Queenie Ma. Kathy has taken the lead on the name search process for
-   and her positive attitude and helpfulness are an incredible asset for the
+   Quarks, and her positive attitude and helpfulness are an incredible asset
-   Quarks community. Queenie has contributed content to the website and is a
+   for the Quarks community. Queenie has contributed content to the website
-   frequent participant in community discussions. The Quarks community is still
+   and is a frequent participant in community discussions. The Quarks
-   small, as Quarks has just recently incubated, therefore we aim to continue
+   community is still small, as Quarks has just recently incubated, therefore
-   growing our list in the near future.
+   we aim to continue growing our list in the near future.
  
  How has the project developed since the last report?
  
@@ -1123, +1175 @@

  --------------------
  Quickstep
  
- Modern servers pack enough storage and computing power that just a decade ago was spread
across a modest-sized cluster. Given that we are on a technological path to continue to increase
the storage and compute densities of individual server nodes, we must complement methods that
focus on '''scaling-out''' by also developing methods to '''scale-in''' to fully exploit the
hardware capabilities that is packed in each server node. The initial phase of the Quickstep
project focuses on this scaling-in aspect. Quickstep uses novel methods for organizing data
(including columnar and hybrid storage organization), template metaprogramming for vectorized
query execution, and a query execution paradigm that separate control-flow from data-flow.
Collectively, these methods achieve high performance on contemporary servers with multi-socket,
multi-core processors and large main memory configurations. To keep the project focused, the
project’s initial target is interactive in-memory data warehousing workloads in single-node
settings. In the near future we plan to expand from this initial single-node focus to a distributed
setting. Early results indicate that Quickstep is over an order-of-magnitude faster than existing
platforms including Spark 2.0 and PostgreSQL 9.6 Beta1 (that now has parallel query processing).

+ Modern servers pack enough storage and computing power that just a decade
+ ago was spread across a modest-sized cluster. Given that we are on a
+ technological path to continue to increase the storage and compute densities
+ of individual server nodes, we must complement methods that focus on
+ '''scaling-out''' by also developing methods to '''scale-in''' to fully
+ exploit the hardware capabilities that is packed in each server node. The
+ initial phase of the Quickstep project focuses on this scaling-in aspect.
+ Quickstep uses novel methods for organizing data (including columnar and
+ hybrid storage organization), template metaprogramming for vectorized query
+ execution, and a query execution paradigm that separate control-flow from
+ data-flow. Collectively, these methods achieve high performance on
+ contemporary servers with multi-socket, multi-core processors and large main
+ memory configurations. To keep the project focused, the project’s initial
+ target is interactive in-memory data warehousing workloads in single-node
+ settings. In the near future we plan to expand from this initial single-node
+ focus to a distributed setting. Early results indicate that Quickstep is
+ over an order-of-magnitude faster than existing platforms including Spark
+ 2.0 and PostgreSQL 9.6 Beta1 (that now has parallel query processing). 
  
  Quickstep has been incubating since 2016-03-29.
  
@@ -1136, +1205 @@

  
  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?
- We were incubated into Apache recently, and the developers are actively learning about the
Apache way from our mentors.
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
+ 
+   We were incubated into Apache recently, and the developers are actively
+   learning about the Apache way from our mentors.
+ 
+ How has the project developed since the last report?
+ 
- We have fully transitioned to the ASF for all development work. 
+   We have fully transitioned to the ASF for all development work. 
- 
  
  Date of last release: 
  
@@ -1164, +1236 @@

      Getting development onto ASF git took a while, but I think we're there.
      I'll work with the project to refine the "Acquire early adopters" goal
      into more concrete outreach steps.
- 
  
  --------------------
  Ranger
@@ -1204, +1275 @@

    2. Members have been working on a next major release of 0.6.0
       a. Working on fixing bugs in the current 0.6.0 features
       
- 
  Date  of last release:
  
    May-31-2016
@@ -1231, +1301 @@

  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 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 Flink, and Apache Samza.
+ several DSPEs such as Apache Storm, Apache Flink, and Apache Samza.
  
  SAMOA has been incubating since 2014-12-15.
  
@@ -1246, +1316 @@

  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?
  
- Mailing list activity (March 2016 - May 2016):
+   Mailing list activity (March 2016 - May 2016):
    * @dev: 202 messages
  
    Jira issues backlog (March 2016 - May 2016):
    * Created:  3
    * Resolved: 9
  
- We have a number of new users showing up on the mailing list, which is
+   We have a number of new users showing up on the mailing list, which is
- encouraging.
+   encouraging.
  
  How has the project developed since the last report?
  
- After the decision taken by the community to drop support for S4, we removed
+   After the decision taken by the community to drop support for S4, we
- the support for S4. We fixed automatic build issues, we simplified
+   removed the support for S4. We fixed automatic build issues, we simplified
- input from HDFS, and we worked on adding support for Apache Gearpump.
+   input from HDFS, and we worked on adding support for Apache Gearpump.  Two
- Two talks were given to advertise Apache SAMOA, one at ApacheCon NA
+   talks were given to advertise Apache SAMOA, one at ApacheCon NA Big Data
- Big Data by Nicolas Kourtellis, and another one at the "J on the beach"
+   by Nicolas Kourtellis, and another one at the "J on the beach" conference
- conference by Albert Bifet.
+   by Albert Bifet.
  
  Date of last release:
  
@@ -1297, +1367 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Grow the community. We anticipate stronger growth of the community when the upcoming,
major release (v1.0) is available. SINGA v1.0 will have new programming abstractions and be
able to run on heterogeneous hardware (e.g., using Cuda and OpenCL). It will also have improved
usability in terms of installation and training new models, etc (see details below).
+   1. Grow the community. We anticipate stronger growth of the community when
+      the upcoming, major release (v1.0) is available. SINGA v1.0 will have
+      new programming abstractions and be able to run on heterogeneous
+      hardware (e.g., using Cuda and OpenCL). It will also have improved
+      usability in terms of installation and training new models, etc (see
+      details below).
-   2. Clean and improve existing documentations. We plan to replace the website template
with a better one.
+   2. Clean and improve existing documentations. We plan to replace the
+      website template with a better one.
    3. Focus on Rafiki --- SINGA-based deep learning as a service.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -1306, +1382 @@

  
    No
  
- 
  How has the community developed since the last report?
  
    The Github repository has scored 602 stars and 205 forks.
+ 
-   There were 107, 73 and 37 emails from dev@ list in March 2016, April 2016 and May 2016
respectively.
+   There were 107, 73 and 37 emails from dev@ list in March 2016, April 2016
+   and May 2016 respectively.
+ 
    There were 9, 35, and 30 commits in March 2016, April 2016 and May 2016.
  
- 
  How has the project developed since the last report?
  
-   In April 2016, we released our third version, i.e. v0.3.0, with the following major features:
+   In April 2016, we released our third version, i.e. v0.3.0, with the
+   following major features:
+ 
-       * Training on GPU cluster
+   * Training on GPU cluster
-       * Python wrapper improvements
+   * Python wrapper improvements
-       * New SGD updaters
+   * New SGD updaters
-       * Remove several dependencies for single node training.
+   * Remove several dependencies for single node training.
-       * Heterogeneous training with CPU and GPU.
+   * Heterogeneous training with CPU and GPU.
-       * Support cuDNNv4.
+   * Support cuDNNv4.
  
-   In May, we started working on the first major release (v1.0) with the following notable
features(http://singa.apache.org/develop/schedule.html):
+   In May, we started working on the first major release (v1.0) with the
+   following notable features(http://singa.apache.org/develop/schedule.html):
+ 
-     * Cross-platform
+   * Cross-platform
-     * Support heterogeneous hardware: CUDA, OpenCL
+   * Support heterogeneous hardware: CUDA, OpenCL
-     * Enhance programming abstraction, focusing on Tensor as core abstraction.
+   * Enhance programming abstraction, focusing on Tensor as core abstraction.
-     * Python binding, cloud integration (Spark, Hadoop, etc.)
+   * Python binding, cloud integration (Spark, Hadoop, etc.)
-     * Runtime optimization.
+   * Runtime optimization.
  
-   We are working on a system called Rafiki which uses SINGA to provide deep learning as
a service and has the following features:
+   We are working on a system called Rafiki which uses SINGA to provide deep
+   learning as a service and has the following features:
+ 
-     * Sharing of pre-training models
+   * Sharing of pre-training models
-     * Visualizing training progress
+   * Visualizing training progress
-     * Configuring model via GUI (web browsers)
+   * Configuring model via GUI (web browsers)
  
  Date of last release:
  
@@ -1361, +1444 @@

  
  Apache Streams (incubating) unifies a diverse world of digital profiles
  and online activities into common formats and vocabularies, and makes
- these datasets accessible across a variety of databases, devices,
+ these datasets accessible across a variety of databases, devices, and
- and platforms for streaming, browsing, search, sharing, and analytics use-cases.
+ platforms for streaming, browsing, search, sharing, and analytics use-cases.
  
  Streams has been incubating since 2012-11-20.
  
@@ -1370, +1453 @@

  
    1. Community growth and PMC maturity.
    2. Demonstrate a consistent release schedule.
-   3. Participation of project community within related standards-bodies and Apache projects.
+   3. Participation of project community within related standards-bodies and
+      Apache projects.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- # of contributors submitting and reviewing pull requests and participating in discussions
is still too low.
+   # of contributors submitting and reviewing pull requests and participating
+   in discussions is still too low.  Getting the attention of developers who
- Getting the attention of developers who work with social datasets and highlighting the ways
that adopting
+   work with social datasets and highlighting the ways that adopting and
- and contributing to streams could provide value for their projects remains our biggest challenge
and
+   contributing to streams could provide value for their projects remains our
- opportunity in community growth.
+   biggest challenge and opportunity in community growth.
  
  How has the community developed since the last report?
  
- Several recently in-active project contributors participated again this quarter.
+   Several recently in-active project contributors participated again this
+   quarter.
  
  How has the project developed since the last report?
  
- http://streams.incubator.apache.org has been completely overhauled, and following several
talks given
+   http://streams.incubator.apache.org has been completely overhauled, and
- at ApacheCon NA 2016, a new blog post, and a renewed focus on marketing we’re beginning
to see a payoff
+   following several talks given at ApacheCon NA 2016, a new blog post, and a
+   renewed focus on marketing we’re beginning to see a payoff in the form of
- in the form of a consistent level of unique visitors, according to google analytics.
+   a consistent level of unique visitors, according to google analytics.
  
  25 Issues resolved + 4 Issues resolved by open pull requests
  
@@ -1434, +1521 @@

  
    Lack of active mentors - would appreciate another volunteer.
  
- 
  How has the community developed since the last report?
  
    Two new GSOC students now active.
@@ -1445, +1531 @@

    further encouragement and guidance to submit regular pull
    requests.
  
- 
    dev@taverna mailing lists stats:
  
    Mar 2016: 312
    Apr 2016: 102
    May 2015: 184
  
- 
    users@taverna:
  
    Mar 2016: 12
    Apr 2016: 6
    May 2015: 1
  
- 
    JIRA issues over last 90 days:
  
    49 created
    25 resolved
- 
  
  How has the project developed since the last report?
  
@@ -1480, +1562 @@

    this component should probably be the development
    focus after GSOC.
  
- 
  Date of last release:
  
    2016-03-11 taverna-osgi-0.2.1-incubating
@@ -1490, +1571 @@

    taverna-engine, taverna-common-activities, taverna-commandline
    https://lists.apache.org/thread.html/Zpt11soyc7qf2so
  
- 
  When were the last committers or PMC members elected?
  
    2015-12-04
- 
  
  Signed-off-by:
  
@@ -1530, +1609 @@

  
  How has the community developed since the last report?
  
-   1) Apache Tephra now powers ACID transactions in Apache Phoenix (since v4.7.0).
+   1) Apache Tephra now powers ACID transactions in Apache Phoenix (since
+      v4.7.0).
-   2) We presented Apache Tephra as a part of the Apache Phoenix talk at HBaseCon 2016.
+   2) We presented Apache Tephra as a part of the Apache Phoenix talk at
+      HBaseCon 2016.
-   3) We also presented a more elaborate version of the above talk at PhoenixCon 2016.
+   3) We also presented a more elaborate version of the above talk at
+      PhoenixCon 2016.
    4) We are making progress towards setting up of Project page.
  
  How has the project developed since the last report?
  
    1) We had our first release (0.8.0-incubating) since incubation.
-   2) We have added support for Apache HBase v1.2 in the latest release (0.8.0-incubating).
+   2) We have added support for Apache HBase v1.2 in the latest release
+      (0.8.0-incubating).
  
  Date of last release:
  
@@ -1595, +1678 @@

  
  How has the project developed since the last report?
  
-   1. Contrinue working with JeroMQ community to further their transition into
+   1. Contrinue working with JeroMQ community to further their transition
-      MPL v2 and away from LGPL. 3 committers to go.
+      into MPL v2 and away from LGPL. 3 committers to go.
-   2. Substantial effort in our build system to make Apache compliant releases.
+   2. Substantial effort in our build system to make Apache compliant
+      releases.
    3. Addressing issues opened by community
  
  Date of last release:
@@ -1614, +1698 @@

    [ ](toree) Reynold Xin
    [ ](toree) Hitesh Shah
    [ ](toree) Julien Le Dem
- 
  
  --------------------
  Trafodion
@@ -1631, +1714 @@

       support for Apache HBase 1.x without a commercial distribution.
    3. Continue the momentum and become more integrated with the
       rest of the Apache community.
- 
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -1666, +1748 @@

    The last PMC members were announced in November 2015.
    We expect to add an additional committer soon.
  
- 
  Signed-off-by:
  
    [ ](trafodion) Devaraj Das
@@ -1680, +1761 @@

  --------------------
  Wave
  
- A wave is a hosted, live, concurrent data structure for rich communication. It
+ A wave is a hosted, live, concurrent data structure for rich communication.
- can be used like email, chat, or a document.
+ It can be used like email, chat, or a document.
  
  Wave has been incubating since 2010-12-04.
  
@@ -1692, +1773 @@

  
  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 had a few discussions regarding technical developments.
+   - We had a few discussions regarding technical developments.
  
- 
  How has the project developed since the last report?
+ 
- - Made some code improvements
+   - Made some code improvements
- - Introduced GitHub based pull requests as accepted way for change submissions.
+   - Introduced GitHub based pull requests as accepted way for change
+     submissions.
  
- 
  Date of last release:
  
-  March 2016
+   March 2016
  
  When were the last committers or PMC members elected?
  
- February 2016
+   February 2016
  
  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