Hi Eagle Community, I have input some information in Nov status report, please provide feedback on what is left before we ask mentors to sign off.
EagleEagle is a Monitoring solution for Hadoop to instantly identify access tosensitive data, recognize attacks, malicious activities and take actions inreal time.Eagle has been incubating since 2015-10-26.Three most important issues to address in the move towards graduation: 1. Jira, PR are all populated with good description so that people can reference in the future. 2. Massive improvement on unit test, now it becomes stable and build status is closed monitored in README 3. Community has one more discussion about graduation and all are with positive feedback, and we are going through the graduation steps.Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware of? NilHow has the community developed since the last report? - Presented in conference: QCon Shanghai - More active contributors from YHD.com participate in large feature developmentHow has the project developed since the last report? - 0.5 version is being in active development. This version will include big improvement in application management and alert engine. - Job monitoring feature is ready including map/reduce and spark job - Standalone alert engine which is highly scalable and user friendly in that user does not need code to configure alerting rules - UI is completely rewritten to expose metadata to end user and user can define data source, stream and policy etc. - Cluster health monitoring is ready, including hdfs health indicator, hbase health indicator etc.Date of last release: 2016-07-19, and 0.5 release is being preparedWhen were the last committers or PMC members elected? - Jinhu Wu 2016-09-10Signed-off-by: [ ](eagle) Owen O'Malley [ ](eagle) Henry Saputra [ ](eagle) Julian Hyde [ ](eagle) P. Taylor Goetz [ ](eagle) Amareshwari SriramdasuShepherd/Mentor notes: On Wed, Oct 26, 2016 at 6:21 PM, Edward Zhang <[email protected]> wrote: > I will do this by end of this week. > > Thanks > Edward > > On Wed, Oct 26, 2016 at 4:01 PM, <[email protected]> wrote: > >> Dear podling, >> >> This email was sent by an automated system on behalf of the Apache >> Incubator PMC. It is an initial reminder to give you plenty of time to >> prepare your quarterly board report. >> >> The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT. >> The report for your podling will form a part of the Incubator PMC >> report. The Incubator PMC requires your report to be submitted 2 weeks >> before the board meeting, to allow sufficient time for review and >> submission (Wed, November 02). >> >> Please submit your report with sufficient time to allow the Incubator >> PMC, and subsequently board members to review and digest. Again, the >> very latest you should submit your report is 2 weeks prior to the board >> meeting. >> >> Thanks, >> >> The Apache Incubator PMC >> >> Submitting your Report >> >> ---------------------- >> >> Your report should contain the following: >> >> * Your project name >> * A brief description of your project, which assumes no knowledge of >> the project or necessarily of its field >> * A list of the three most important issues to address in the move >> towards graduation. >> * Any issues that the Incubator PMC or ASF Board might wish/need to be >> aware of >> * How has the community developed since the last report >> * How has the project developed since the last report. >> >> This should be appended to the Incubator Wiki page at: >> >> http://wiki.apache.org/incubator/November2016 >> >> Note: This is manually populated. You may need to wait a little before >> this page is created from a template. >> >> Mentors >> ------- >> >> Mentors should review reports for their project(s) and sign them off on >> the Incubator wiki page. Signing off reports shows that you are >> following the project - projects that are not signed may raise alarms >> for the Incubator PMC. >> >> Incubator PMC >> > >
