incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "August2016" by MarvinHumphrey
Date Thu, 04 Aug 2016 17:21:32 GMT
Dear Wiki user,

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

The "August2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/August2016?action=diff&rev1=71&rev2=72

Comment:
Reflow BatchEE, Beam, CarbonData, CMDA.

  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 got several new users and interest in advanced integration (in particular our GUI).
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   We got several new users and interest in advanced integration (in
+   particular our GUI).
+ 
+ How has the project developed since the last report?
+ 
- Not much but it is quite stable and no new spec was out since last report so it behaves
as expected.
+   Not much but it is quite stable and no new spec was out since last report
+   so it behaves as expected.
  
  Date of last release:
  
@@ -205, +207 @@

  --------------------
  Beam
  
- Apache Beam is an open source, unified model and set of language-specific SDKs for defining
and executing data processing workflows, and also data ingestion and integration flows, supporting
Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Beam pipelines
simplify the mechanics of large-scale batch and streaming data processing and can run on a
number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark, and Google Cloud Dataflow
(a cloud service). Beam also brings SDKs in different languages, allowing users to easily
implement their data integration processes.
+ Apache Beam is an open source, unified model and set of language-specific
+ SDKs for defining and executing data processing workflows, and also data
+ ingestion and integration flows, supporting Enterprise Integration Patterns
+ (EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
+ mechanics of large-scale batch and streaming data processing and can run on
+ a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
+ and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
+ different languages, allowing users to easily implement their data
+ integration processes.
  
  Beam has been incubating since 2016-02-01.
  
  Three most important issues to address in the move towards graduation:
+ 
    1. Additional and continued Beam releases
    2. Grow the community of Beam users and contributors
-   3. Add to and improve upon documentation, code samples, and project website
+   3. Add to and improve upon documentation, code samples, and project
+      website
  
  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?
+ 
-  * 425 closed/merged pull requests
+   * 425 closed/merged pull requests
-  * High engagement on dev and user mailing lists (590 / 455 messages)
+   * High engagement on dev and user mailing lists (590 / 455 messages)
-  * Several public talks, articles, and videos including:
+   * Several public talks, articles, and videos including:
-   * Hadoop Summit San Jose ("Apache Beam: A Unified Model for Batch and Streaming Data Processing"
& "The Next Generation of Data Processing & OSS" )
+   * Hadoop Summit San Jose ("Apache Beam: A Unified Model for Batch and
+     Streaming Data Processing" & "The Next Generation of Data Processing &
+     OSS")
    * O’Reilly & The New Stack ("Future-proof and scale-proof your code")
    * QCon NY ("Apache Beam: The Case for Unifying Streaming API's")
    * JBCN Barcelona ("Introduction to Apache Beam")
  
  How has the project developed since the last report?
+ 
- Major developments on the project since last report include the following:
+   Major developments on the project since last report include the following:
+ 
-  * First incubating release (0.1.0-incubating)
+   * First incubating release (0.1.0-incubating)
-  * Addition of Apache Beam Python SDK
+   * Addition of Apache Beam Python SDK
-  * Addition of the Apache Gearpump runner
+   * Addition of the Apache Gearpump runner
-  * Added support for writing to Apache Kafka clusters
+   * Added support for writing to Apache Kafka clusters
-  * Added support for reading from and writing to Java Message Services, including Apache
ActiveMQ, GeronimoJMS, and RabbitMQ
+   * Added support for reading from and writing to Java Message Services,
+     including Apache ActiveMQ, GeronimoJMS, and RabbitMQ
-  * Ratified new Beam model APIs to improve efficiency and failure handling: DoFn setup,
teardown, and reuse
+   * Ratified new Beam model APIs to improve efficiency and failure handling:
+     DoFn setup, teardown, and reuse
-  * Optimized key components such as data serialization and shuffle
+   * Optimized key components such as data serialization and shuffle
-  * Continued improvements to the Flink, Spark, and Dataflow runners
+   * Continued improvements to the Flink, Spark, and Dataflow runners
-  * Continued reorganization and refactoring of the project
+   * Continued reorganization and refactoring of the project
-  * Continued improvements to documentation and testing
+   * Continued improvements to documentation and testing
  
  Date of last release:
+ 
-  * 2016/06/15 - 0.1.0-incubating
+   * 2016/06/15 - 0.1.0-incubating
-  * 2016/07/28 - 0.2.0-incubating (RC proposal sent to Incubator PMC)
+   * 2016/07/28 - 0.2.0-incubating (RC proposal sent to Incubator PMC)
  
  When were the last committers or PMC members elected?
+ 
- N/A - no changes since last report.
+   N/A - no changes since last report.
  
  Signed-off-by:
  
- [X](beam) Jean-Baptiste Onofre
+   [X](beam) Jean-Baptiste Onofre
- [ ](beam) Venkatesh Seetharam
+   [ ](beam) Venkatesh Seetharam
- [ ](beam) Bertrand Delacretaz
+   [ ](beam) Bertrand Delacretaz
- [ ](beam) Ted Dunning
+   [ ](beam) Ted Dunning
  
  Shepherd/Mentor notes:
  
@@ -322, +343 @@

  
  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 voted two new committers: Venkata Ramana and Ravindra Pesala.
+   We voted two new committers: Venkata Ramana and Ravindra Pesala.
  
- We are preparing the CarbonData website, blog posts and talks to promote CarbonData and
grow the user and dev communities.
+   We are preparing the CarbonData website, blog posts and talks to promote
+   CarbonData and grow the user and dev communities.
  
- The community activity increased: many new users started to use and test CarbonData, we
had more than 100 new issues created during July.
+   The community activity increased: many new users started to use and test
+   CarbonData, we had more than 100 new issues created during July.
  
- On the other hand, presentation material has been created and a first talk has been given:
+   On the other hand, presentation material has been created and a first talk
+   has been given:
  
- http://www.slideshare.net/liangchen18/apache-carbondatanew-high-performance-data-format-for-faster-data-analysis
+   http://www.slideshare.net/liangchen18/apache-carbondatanew-high-performance-data-format-for-faster-data-analysis
  
  How has the project developed since the last report?
  
- Code donation has been done and all resources have been created by INFRA (git, github mirror,
mailing list, Jira, ...).
+   Code donation has been done and all resources have been created by INFRA
+   (git, github mirror, mailing list, Jira, ...).
+ 
- We also created the Jenkins CI jobs.
+   We also created the Jenkins CI jobs.
  
- We are now in the process of cleanup and polishing the build and legal to prepare the first
release.
+   We are now in the process of cleanup and polishing the build and legal to
+   prepare the first release.
  
  Date of last release:
  
@@ -376, +403 @@

  
    1. Enlarge the CMDA community;
    2. Develop stable platform to allow broad contributors to turn in code;
-   3. Develop a streamline procedure to allow the entire community to develop the CMDA project
+   3. Develop a streamline procedure to allow the entire community to develop
+      the CMDA project
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- Noe.
+   Noe.
  
- How has the community developed since the last report?
- 
- In this month, the CMDA community focuses on developing the summer school program, in order
to advocate and distribute CMDA 2.0, to educate more students on our latest product, and to
attract more people to join our community. So far, we have received about 25 graduate students
who show interest and will come to our summer school to learn CMDA 2.0 product and the platform.
- 
- Meanwhile, with the great guidance from our mentors, the CMDA community has learned to run
the project from various aspects in an Apache way. Many community meetings were held to streamline
and develop our operation regulations. Here we just name a few strategies. Weekly community
meetings are arranged with pre-distributed meeting agenda. Meeting invites are sent to all
community members with open access to the weekly meetings. After each community meeting, various
contributors/groups summarize their to-do items on the community mailing list, to welcome
all community members' input. Community communication always adopts the community mailing
list as carrier. More committers join the voting group. More committers are recommended based
on their active performance in the community.
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
- We have successfully encapsulated and deployed CMDA 2.0 onto Amazon cloud environment, leveraging
docker technology to ensure scalability. Provenance engine is also deployed onto Amazon cloud
to ensure that we gather all provenance during the summer school for further study and development
of our project after the summer school.
+   In this month, the CMDA community focuses on developing the summer school
+   program, in order to advocate and distribute CMDA 2.0, to educate more
+   students on our latest product, and to attract more people to join our
+   community. So far, we have received about 25 graduate students who show
+   interest and will come to our summer school to learn CMDA 2.0 product and
+   the platform.
+ 
+   Meanwhile, with the great guidance from our mentors, the CMDA community
+   has learned to run the project from various aspects in an Apache way. Many
+   community meetings were held to streamline and develop our operation
+   regulations. Here we just name a few strategies. Weekly community meetings
+   are arranged with pre-distributed meeting agenda. Meeting invites are sent
+   to all community members with open access to the weekly meetings. After
+   each community meeting, various contributors/groups summarize their to-do
+   items on the community mailing list, to welcome all community members'
+   input. Community communication always adopts the community mailing list as
+   carrier. More committers join the voting group. More committers are
+   recommended based on their active performance in the community.
+ 
+ How has the project developed since the last report?
+ 
+   We have successfully encapsulated and deployed CMDA 2.0 onto Amazon cloud
+   environment, leveraging docker technology to ensure scalability.
+   Provenance engine is also deployed onto Amazon cloud to ensure that we
+   gather all provenance during the summer school for further study and
+   development of our project after the summer school.
  
  Date of last release:
  

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


Mime
View raw message