Hi, Here my draft. Please let me have any comments by tomorrow.
-------------------- SAMOA 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). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Roll an Apache release 2. Elect new PMC members 3. Grow the community Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Two of our current PMC members (Olivier and Matthieu) have new jobs and have declared that they will not be able to actively contribute to the project for the moment being. This leaves 4 active PMC members. How has the community developed since the last report? Mailing list activity (March-April-May 2015): * @dev 375 messages Jira issues backlog (March-April-May 2015): * Created: 14 * Resolved: 19 We have had contributions from outside the PMC. In particular, we have been collaborating with the Apache Flink community. Our main goal is still to grow the community, which is still pretty small. To achieve this goal, we are doing a large amount of dissemination work in conferences and events to promote SAMOA. How has the project developed since the last report? We are fully operational on the new infrastructure: * Completed migration of issues from old GitHub repository. * Completed migration of documentation from old wiki. * Created new Confluence wiki with roadmap and contribution instruction: https://cwiki.apache.org/confluence/display/SAMOA/Samoa+Home Main developments: * New adaptor for Flink integrated. * Simplified the website and solved several bugs. * Preparing for our first release in June. We should increase the rate of technical contribution to the project and move to less incremental ones. Codebase still need cleanup to ease adoption by new contributors. Date of last release: None, plan to have one in June. When were the last committers or PMC members elected? None -------------------- Cheers, -- Gianmarco On 1 June 2015 at 09:44, Albert Bifet <[email protected]> wrote: > Thanks! > > Albert > > On Mon, Jun 1, 2015 at 2:42 PM, Gianmarco De Francisci Morales > <[email protected]> wrote: > > Hi, > > > > This quarter's report is due in 2 days. > > I can take care of preparing a first draft. > > I'll send it on the mailing list for comments, possibly tomorrow. > > > > Cheers, > > > > -- > > Gianmarco > > > > On 29 May 2015 at 01:10, Marvin Humphrey <[email protected]> wrote: > > > >> Greetings, {podling} developers, > >> > >> The "marvin" automated report reminder script didn't fire for whatever > >> reason this week, so I'm sending out a bulk reminder manually for the 27 > >> podlings who are expected to submit a June 2015 report. Boilerplate > >> reminder text below. > >> > >> Best, > >> > >> Marvin Humphrey > >> > >> --------------- > >> > >> 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, 17 June 2015, 10:30 am PST. > >> 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, June 3rd). > >> > >> 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/June2015 > >> > >> 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 > >> > >> > >> > >> >
