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:26:45 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=72&rev2=73

Comment:
Reflow DistributedLog, Eagle, Fluo.

  
  Three most important issues to address in the move towards graduation: 
  
- * Getting an Apache release out
+   * Getting an Apache release out
- * Improve general documentation
+   * Improve general documentation
- * Grow user base
+   * Grow user base
  
- 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? 
  
- There is currently no issue.
+   There is currently no issue.
  
  How has the community developed since the last report? 
  
- * A few people have started to report issues
+   * A few people have started to report issues
- * Some conversations have been initiated on the mailing list
+   * Some conversations have been initiated on the mailing list
- * Sijie will be present at Strata in China to present the project
+   * Sijie will be present at Strata in China to present the project
  
  How has the project developed since the last report?
  
- * The wiki has been set up (cwiki.apache.org/confluence/display/DL/)
+   * The wiki has been set up (cwiki.apache.org/confluence/display/DL/)
- * A few contributions were made to the repository on GitHub and are in the process of being
merged
+   * A few contributions were made to the repository on GitHub and are in the
+     process of being merged
- * Various mailing lists have been set up
+   * Various mailing lists have been set up
- * SGA from Twitter has been completed
+   * SGA from Twitter has been completed
- * Status page is up and we have started filling it out
+   * Status page is up and we have started filling it out
- * Most accounts of initial committers have been created
+   * Most accounts of initial committers have been created
- * Jira queue has been created (https://issues.apache.org/jira/browse/DL)
+   * Jira queue has been created (https://issues.apache.org/jira/browse/DL)
- * Repository has been created (and mirrored on GitHub)
+   * Repository has been created (and mirrored on GitHub)
  
  Signed-off-by:
  
@@ -510, +512 @@

  --------------------
  Eagle
  
- Apache Eagle (incubating) is an open source analytics solution for identifying security
and performance issues instantly on big data platforms, e.g. Apache Hadoop, Apache Spark etc.
It analyzes data activities, Yarn application, Hadoop JMX metrics and daemon logs etc., provides
state-of-the-art alert engine to identify security breach, performance issues and shows insights.
+ Apache Eagle (incubating) is an open source analytics solution for
+ identifying security and performance issues instantly on big data platforms,
+ e.g. Apache Hadoop, Apache Spark etc. It analyzes data activities, Yarn
+ application, Hadoop JMX metrics and daemon logs etc., provides
+ state-of-the-art alert engine to identify security breach, performance
+ issues and shows insights.
  
  Eagle has been incubating since 2015-10-26.
  
  Three most important issues to address in the move towards graduation:
  
-   1. Eagle community is discussing graduation and use Apache maturity assessment to measure
the gap to graduation. That should be completed, seehttps://cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessment
+   1. Eagle community is discussing graduation and use Apache maturity
+      assessment to measure the gap to graduation. That should be completed,
+      see
+      https://cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessment
  
-   2. Complete one requirement from self assessment which is to provide a well-documented
channel to report security issues, along with a documented way of responding to them.
+   2. Complete one requirement from self assessment which is to provide a
+      well-documented channel to report security issues, along with a
+      documented way of responding to them.
  
-   3. Identify other housekeeping before graduation, for example agreement on bylaws, PMC
composition etc. 
+   3. Identify other housekeeping before graduation, for example agreement on
+      bylaws, PMC composition etc. 
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
+ 
- NIL
+   NIL
  
  
  How has the community developed since the last report?
+ 
- . Presented in Apache Con, May 2016
+   - Presented in Apache Con, May 2016
- 
- . Presented in London Stratus + Hadoop, May 2016
+   - Presented in London Stratus + Hadoop, May 2016
- 
- . Presented in San Jose Hadoop Summit, June 2016
+   - Presented in San Jose Hadoop Summit, June 2016
- 
- . Presented in DTCC2016 Beijing, China, May 2016
+   - Presented in DTCC2016 Beijing, China, May 2016
- 
- . Presented in JavaCon, China, May 2016
+   - Presented in JavaCon, China, May 2016
- 
- . Presented in Hadoop Summit, San Jose, China, June 2016
+   - Presented in Hadoop Summit, San Jose, China, June 2016
- 
- . Presented in Data Asset Management Summit, Shanghai, China, July 2016
+   - Presented in Data Asset Management Summit, Shanghai, China, July 2016
  
- Communities showed continuous interest in Apache Eagle project. Some company tried to integrate
Eagle as part of whole solution and some contributed different use case to Eagle platform,
for example MapR support, Oozie monitoring support etc.
+   Communities showed continuous interest in Apache Eagle project. Some
+   company tried to integrate Eagle as part of whole solution and some
+   contributed different use case to Eagle platform, for example MapR
+   support, Oozie monitoring support etc.
  
- 
  How has the project developed since the last report?
+ 
- Technically we added more documents for user to easily use Eagle
+   Technically we added more documents for user to easily use Eagle
  
- Besides Hadoop security monitoring, we have started working on performance monitoring design
and development based on the requests from community. 
+   Besides Hadoop security monitoring, we have started working on performance
+   monitoring design and development based on the requests from community. 
  
- As we may have multiple different use cases running on top of Eagle, a design discussion
and prototype is conducted to make sure Eagle is a framework to host multiple use cases and
user will use Eagle to manage those use cases.
+   As we may have multiple different use cases running on top of Eagle, a
+   design discussion and prototype is conducted to make sure Eagle is a
+   framework to host multiple use cases and user will use Eagle to manage
+   those use cases.
  
- Alert engine is going to be decoupled from data processing so that alert engine will be
multi-tenant and easy to be used by multiple use cases by incorporating well-designed metadata.
- 
+   Alert engine is going to be decoupled from data processing so that alert
+   engine will be multi-tenant and easy to be used by multiple use cases by
+   incorporating well-designed metadata.
  
  Date of last release:
  
    2016-07-19
  
  When were the last committers or PMC members elected?
+ 
- Daniel Zhou, 2016-06-15
+   - Daniel Zhou, 2016-06-15
- Michael Wu, 2016-06-17
+   - Michael Wu, 2016-06-17
- 
  
  Signed-off-by:
  
@@ -645, +662 @@

  
  How has the project developed since the last report?
  
-   We completed refactoring of code to use Apache names.  We attempted our first
+   We completed refactoring of code to use Apache names.  We attempted our
-   release of a parent pom (for both Fluo projects) and it failed on the incubator
+   first release of a parent pom (for both Fluo projects) and it failed on
-   list.  A parent pom is a way to share build configuration among multiple
+   the incubator list.  A parent pom is a way to share build configuration
-   projects.  We plan for Fluo and Fluo Recipes to both inherit the same parent pom
-   and obtain common config for code formatting, findbugs, checkstyle rules, etc.
-   For this to work the parent pom needs to be released before the projects.
+   among multiple projects.  We plan for Fluo and Fluo Recipes to both
+   inherit the same parent pom and obtain common config for code formatting,
+   findbugs, checkstyle rules, etc.  For this to work the parent pom needs to
+   be released before the projects.
  
    The reason it failed is because members of the IPMC identified the
    following issues :
  
   * Improper linking to pre-Apache releases of Fluo from website.
-  * Branding and linking issues with fluo.io domain, fluo-io GitHub org and projects.
+  * Branding and linking issues with fluo.io domain, fluo-io GitHub org and
-    The domain name and github org were used by the project before moving to Apache.
+    projects.  The domain name and github org were used by the project before
+    moving to Apache.
  
-   This was really good feedback.  We want to remedy the issues identified and
+   This was really good feedback.  We want to remedy the issues identified
-   eliminate possible confusion around the Apache Fluo brand.  The following link
+   and eliminate possible confusion around the Apache Fluo brand.  The
-   identifies discussion of a possible way forward.
+   following link identifies discussion of a possible way forward.
  
    https://lists.apache.org/thread.html/b478645815bf7b1fee8342a21924162decc173d91c22eaf5f708a435@%3Cdev.fluo.apache.org%3E
  

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


Mime
View raw message