Owen, I'd strongly advise you to add Metron to reporting group 1 and make the first report in January instead of trying to rush a report in for this month. The podling reports are already past due.
John On Sun, Dec 6, 2015 at 4:50 PM <omal...@apache.org> wrote: > Author: omalley > Date: Sun Dec 6 21:50:16 2015 > New Revision: 1718228 > > URL: http://svn.apache.org/viewvc?rev=1718228&view=rev > Log: > Add Metron as new podling. > > Added: > incubator/public/trunk/content/projects/metron.xml (with props) > Modified: > incubator/public/trunk/content/podlings.xml > > Modified: incubator/public/trunk/content/podlings.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1718228&r1=1718227&r2=1718228&view=diff > > ============================================================================== > --- incubator/public/trunk/content/podlings.xml [utf-8] (original) > +++ incubator/public/trunk/content/podlings.xml [utf-8] Sun Dec 6 > 21:50:16 2015 > @@ -1278,6 +1278,18 @@ and a set of useful extensions for this > <mentor username="nslater">Noah Slater</mentor> > </mentors> > </podling> > + <podling name="Metron" status="current" resource="metron" > sponsor="Incubator" startdate="2015-12-06"> > + <description>Metron is a project dedicated to providing an > extensible and scalable advanced network security analytics tool. It has > strong foundations in the Apache Hadoop ecosystem.</description> > + <reporting group="3" monthly="true">December, January, > February</reporting> > + <champion availid="omalley">Owen O'Malley</champion> > + <mentors> > + <mentor username="billie">Billie Rinaldi</mentor> > + <mentor username="mattmann">Chris Mattmann</mentor> > + <mentor username="omalley">Owen O'Malley</mentor> > + <mentor username="ptgoetz">P. Taylor Goetz</mentor> > + <mentor username="vinodkv">Vinod Kumar Vavilapalli</mentor> > + </mentors> > + </podling> > <podling name="mod_ftp" status="graduated" resource="mod_ftp" > sponsor="HTTP Server" startdate="2005-08-06" enddate="2007-02"> > <description>FTP protocol module for Apache httpd > 2.x</description> > <resolution url="http://httpd.apache.org/mod_ftp/"/> > > Added: incubator/public/trunk/content/projects/metron.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/metron.xml?rev=1718228&view=auto > > ============================================================================== > --- incubator/public/trunk/content/projects/metron.xml (added) > +++ incubator/public/trunk/content/projects/metron.xml [utf-8] Sun Dec 6 > 21:50:16 2015 > @@ -0,0 +1,388 @@ > +<?xml version="1.0" encoding="UTF-8"?> > +<document> > + <properties> > + > + <title>Metron Incubation Status</title> > + <link href="http://purl.org/DC/elements/1.0/"; rel="schema.DC"/> > + </properties> > + <body> > + <section id="Metron+Project+Incubation+Status"> > + <title>Metron Project Incubation Status</title> > + <p>This page tracks the project status, incubator-wise. For more > general > + project status, look on the project website.</p> > + </section> > + <section id="Description"> > + <title>Description</title> > +<p>Metron integrates a variety of open source big data technologies in > +order to offer a centralized tool for security monitoring and > +analysis. Metron provides capabilities for log aggregation, full > +packet capture indexing, storage, advanced behavioral analytics and > +data enrichment, while applying the most current threat-intelligence > +information to security telemetry within a single platform.</p> > +<p> > +Metron can be divided into 4 areas: > +<ol> > +<li>A mechanism to capture, store, and normalize any type of security > +telemetry at extremely high rates. Because security telemetry is > +constantly being generated, it requires a method for ingesting the > +data at high speeds and pushing it to various processing units for > +advanced computation and analytics.</li> > +<li>Real time processing and application of enrichments such as threat > +intelligence, geolocation, and DNS information to telemetry being > +collected. The immediate application of this information to incoming > +telemetry provides the context and situational awareness, as well as > +the “who” and “where” information that is critical for investigation.</li> > +<li>Efficient information storage based on how the information will be > used: > +<ol> > + <li>Logs and telemetry are stored such that they can be efficiently > mined > + and analyzed for concise security visibility</li> > + <li>The ability to extract and reconstruct full packets helps an analyst > + answer questions such as who the true attacker was, what data was > + leaked, and where that data was sent</li> > + <li>Long-term storage not only increases visibility over time, but also > + enables advanced analytics such as machine learning techniques to be > + used to create models on the information. Incoming data can then be > + scored against these stored models for advanced anomaly detection.</li> > +</ol></li> > +<li>An interface that gives a security investigator a centralized view of > +data and alerts passed through the system. Metron’s interface presents > +alert summaries with threat intelligence and enrichment data specific > +to that alert on one single page. Furthermore, advanced search > +capabilities and full packet extraction tools are presented to the > +analyst for investigation without the need to pivot into additional > +tools.</li> > +</ol></p> > + > +<p>Big data is a natural fit for powerful security analytics. The Metron > +framework integrates a number of elements from the Hadoop ecosystem to > +provide a scalable platform for security analytics, incorporating such > +functionality as full-packet capture, stream processing, batch > +processing, real-time search, and telemetry aggregation. With Metron, > +our goal is to tie big data into security analytics and drive towards > +an extensible centralized platform to effectively enable rapid > +detection and rapid response for advanced security threats. > +</p> > + </section> > + <section id="News"> > + <title>News</title> > + <ul> > + <li>2015-12-06 Project enters incubation.</li> > + </ul> > + </section> > + <section id="Project+info"> > + <title>Project info</title> > + <ul> > + <li>link to the main website</li> > + </ul> > + <ul> > + <li>link to the page(s) that tell how to participate > (Website,Mailing > + lists,Bug tracking,Source code)</li> > + </ul> > + <ul> > + <li>link to the project status file (Committers,non-incubation > action > + items,project resources, etc)</li> > + </ul> > + <p>If the project website and code repository are not yet setup, > use the > + following table:</p> > + <table> > + <tr> > + <th>item</th> > + <th>type</th> > + <th>reference</th> > + </tr> > + <tr> > + <td>Website</td> > + <td>www</td> > + <td id="www"> > + <a href="http://metron.incubator.apache.org/";> > http://metron.incubator.apache.org/</a> > + </td> > + </tr> > + <tr> > + <td>.</td> > + <td>wiki</td> > + <td>.</td> > + </tr> > + <tr> > + <td>Mailing list</td> > + <td>dev</td> > + <td id="mail-dev"><code>dev</code><code>@</code><code> > metron.incubator.apache.org</code></td> > + </tr> > + <tr> > + <td>.</td> > + <td>commits</td> > + <td id="mail-commits"><code>commits</code><code>@</code><code> > metron.incubator.apache.org</code></td> > + </tr> > + <tr> > + <td>Bug tracking</td> > + <td>.</td> > + <td id="tracker"> > + [ provide expected link ] > + </td> > + </tr> > + <tr> > + <td>Source code</td> > + <td>Git</td> > + <td id="git"> > + <a href=" > https://git-wip-us.apache.org/repos/asf/incubator-metron.git";> > https://git-wip-us.apache.org/repos/asf/incubator-metron.git</a> > + </td> > + </tr> > + <tr> > + <td>Mentors</td> > + <td>ptgoetz</td> > + <td>P. Taylor Goetz</td> > + </tr> > + <tr> > + <td>.</td> > + <td>mattmann</td> > + <td>Chris Mattmann</td> > + </tr> > + <tr> > + <td>.</td> > + <td>omalley</td> > + <td>Owen O'Malley</td> > + </tr> > + <tr> > + <td>.</td> > + <td>billie</td> > + <td>Billie Rinaldi</td> > + </tr> > + <tr> > + <td>.</td> > + <td>vinodkv</td> > + <td>Vinod Kumar Vavilapalli</td> > + </tr> > + <tr> > + <td>Committers</td> > + <td>.</td> > + <td>.</td> > + </tr> > + <tr> > + <td>Extra</td> > + <td>.</td> > + <td>.</td> > + </tr> > + </table> > + </section> > + <section id="Incubation+status+reports"> > + <title>Incubation status reports</title> > + <ul> > + <li>none yet</li> > + </ul> > + </section> > + <section id="Incubation+work+items"> > + <title>Incubation work items</title> > + <section id="Project+Setup"> > + <title>Project Setup</title> > + <p>This is the first phase on incubation, needed to start the > project at Apache.</p> > + <p> > + <em>Item assignment is shown by the Apache id.</em> > + <em>Completed tasks are shown by the completion date > (YYYY-MM-dd).</em> > + </p> > + <section id="Identify+the+project+to+be+incubated"> > + <title>Identify the project to be incubated</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Make sure that the requested project name does not > already exist.</td> > + </tr> > + <tr> > + <td>2015-10-24</td> > + <td>If request from outside Apache to enter an existing > Apache project, > + then post a message to that project for them to decide > on acceptance. Done <a href=" > https://groups.google.com/d/msg/opensoc-support/rFlW2uSSvmU/Sw_cO-T2AAAJ > ">here</a>.</td> > + </tr> > + </table> > + </section> > + <section id="Infrastructure"> > + <title>Infrastructure</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Ask infrastructure to create source repository modules > + and grant the committers karma.</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Ask infrastructure to set up and archive mailing > lists.</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Ask infrastructure to set up issue tracker (JIRA, > Bugzilla).</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Ask infrastructure to set up wiki (Confluence, > Moin).</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Migrate the project to our infrastructure.</td> > + </tr> > + </table> > + </section> > + <section id="Interim+responsibility"> > + <title>Mentor-related responsibility/oversight</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Subscribe all Mentors on the pmc and general lists.</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Give all Mentors access to the incubator SVN repository. > + (to be done by the Incubator PMC chair or an Incubator PMC > + Member wih karma for the authorizations file)</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Tell Mentors to track progress in the file > + 'incubator/projects/{project.name}.html'</td> > + </tr> > + </table> > + </section> > + <section id="Copyright"> > + <title>Copyright</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Check and make sure that the papers that transfer > rights to the ASF > + been received. It is only necessary to transfer rights > for the > + package, the core code, and any new code produced by > the project. > + </td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Check and make sure that the files that have been > donated have been > + updated to reflect the new ASF copyright.</td> > + </tr> > + </table> > + </section> > + <section id="Verify+distribution+rights"> > + <title>Verify distribution rights</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Check and make sure that for all code included with the > distribution > + that is not under the Apache license, we have the right > to combine > + with Apache-licensed code and redistribute. > + </td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Check and make sure that all source code distributed by > the project > + is covered by one or more of the following approved > licenses: Apache, > + BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something > with essentially > + the same terms.</td> > + </tr> > + </table> > + </section> > + <section id="Establish+a+list+of+active+committers"> > + <title>Establish a list of active committers</title> > + <table> > + <tr> > + <th>date</th> > + <th>item</th> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Check that all active committers have submitted a > contributors > + agreement.</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Add all active committers in the STATUS file.</td> > + </tr> > + <tr> > + <td>....-..-..</td> > + <td>Ask root for the creation of committers' accounts on > + people.apache.org.</td> > + </tr> > + </table> > + </section> > + <section id="Project+specific"> > + <title>Project specific</title> > + <p> > + <em>Add project specific tasks here.</em> > + </p> > + </section> > + </section> > + <section id="Incubation"> > + <title>Incubation</title> > + <p>These action items have to be checked for during the whole > incubation process.</p> > + <p> > + <em>These items are not to be signed as done during incubation, > as they > + may change during incubation.</em> > + <em>They are to be looked into and described in the status > reports and > + completed in the request for incubation signoff.</em> > + </p> > + <section id="Collaborative+Development"> > + <title>Collaborative Development</title> > + <ul> > + <li>Have all of the active long-term volunteers been > identified and > + acknowledged as committers on the project? > + </li> > + <li>Are there three or more independent committers? (The > legal definition > + of independent is long and boring, but basically it means > that there > + is no binding relationship between the individuals, such > as a shared > + employer, that is capable of overriding their free will as > + individuals, directly or indirectly.)</li> > + <li>Are project decisions being made in public by the > committers?</li> > + <li>Are the decision-making guidelines published and agreed > to by all of > + the committers?</li> > + </ul> > + </section> > + <section id="Licensing+awareness"> > + <title>Licensing awareness</title> > + <ul> > + <li>Are all licensing, trademark, credit issues being taken > care of and > + acknowleged by all committers?</li> > + </ul> > + </section>:wq > + <section id="Project+Specific"> > + <title>Project Specific</title> > + <p> > + <em>Add project specific tasks here.</em> > + </p> > + </section> > + </section> > + <section id="Exit"> > + <title>Exit</title> > + <p> > + <em>Things to check for before voting the project out.</em> > + </p> > + <section > id="Organizational+acceptance+of+responsibility+for+the+project"> > + <title>Organizational acceptance of responsibility for the > project</title> > + <ul> > + <li>If graduating to an existing PMC, has the PMC voted to > accept it?</li> > + <li>If graduating to a new PMC, has the board voted to accept > it?</li> > + </ul> > + </section> > + <section id="Incubator+sign-off"> > + <title>Incubator sign-off</title> > + <ul> > + <li>Has the Incubator decided that the project has > accomplished all of > + the above tasks?</li> > + </ul> > + </section> > + </section> > + </section> > + </body> > +</document> > > Propchange: incubator/public/trunk/content/projects/metron.xml > > ------------------------------------------------------------------------------ > svn:mime-type = text/plain > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > For additional commands, e-mail: cvs-h...@incubator.apache.org > >
