+1. Thanks Kam. I volunteer for the next one. Manu
Andrew Purtell <apurt...@apache.org>于2016年6月1日周三 04:53写道： > I was hoping others on the PPMC would have taken an interest in the report. > We'll tackle that next time (smile) since this is good and I need to put it > up today since I'll be out tomorrow. > > > On Tue, May 31, 2016 at 8:17 AM, Andrew Purtell <apurt...@apache.org> > wrote: > > > +1 > > > > > > On Monday, May 30, 2016, Kam Kasravi <kamkasr...@gmail.com> wrote: > > > >> GearpumpGearpump is a reactive real-time streaming engine based on the > micro-serviceActor model.Gearpump has been incubating since > 2016-03-08.Three most important issues to address in the move towards > graduation: 1. Make initial Apache branded release and release on a > regular schedule. 2. Continue to evolve community interest and support. > 3. Integrate within Beam and akka-streams frameworks.Any issues that the > Incubator PMC (IPMC) or ASF Board wish/need to beaware of? None How has > the community developed since the last report? - Good discussion on dev > mailing list related to features, bugs and logo - Increased participation > and interest from developers to provide new sources and examplesHow has > the project developed since the last report? - Package renaming > completed. - New logos submitted - reasonable number to finally vote on. > >> > >> - Continued integration within Apache Beam (Gearpump Runner). PR > submitted. > >> > >> - Continued integration within akka-streams (Gearpump Materializer). > PR submitted. > >> > >> - Release pending this month. Over a dozen JIRA's fixed. > >> > >> Date of last release: No release yet.When were the last committers or > PMC members elected? No new committers or PMC members elected > yet.Signed-off-by: [ ](gearpump) Andrew Purtell [ ](gearpump) Jarek > Jarcec Cecho [ ](gearpump) Reynold Xin [ ](gearpump) Todd Lipcon [ > ](gearpump) Xuefu Zhang > >> > >> > >> On Sat, May 28, 2016 at 10:30 AM, Kam Kasravi <kamkasr...@gmail.com> > >> wrote: > >> > >>> Will do. Thanks. > >>> > >>> > >>> On Friday, May 27, 2016 2:11 PM, Andrew Purtell <apurt...@apache.org> > >>> wrote: > >>> > >>> > >>> Thanks Kam. Please post it to dev@ as before for discussion and voting > >>> by the PPMC. Everyone should get into the habit of reviewing the board > >>> report, discussing changes if needed, or voting +1 to approve if not. > There > >>> will be another report next month, then the cadence will switch to > every > >>> three months. > >>> > >>> I might be out Wednesday the 1st when this is due so will post it the > >>> incubator wiki Tuesday just before if everyone's agreed on it. > >>> > >>> > >>> On Fri, May 27, 2016 at 1:48 PM, Kam Kasravi <kamkasr...@gmail.com> > >>> wrote: > >>> > >>> Yes, I'll get it out. > >>> > >>> On Friday, May 27, 2016 10:40 AM, Andrew Purtell < > >>> apurt...@apache.org> wrote: > >>> > >>> > >>> Volunteers? > >>> > >>> > >>> On Thu, May 26, 2016 at 5:40 PM, <johndam...@apache.org> 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, 15 June 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, June 1st). > >>> > > >>> > 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/May2016 > >>> > > >>> > 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 > >>> > > >>> > >>> > >>> > >>> -- > >>> Best regards, > >>> > >>> - Andy > >>> > >>> Problems worthy of attack prove their worth by hitting back. - Piet > Hein > >>> (via Tom White) > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> Best regards, > >>> > >>> - Andy > >>> > >>> Problems worthy of attack prove their worth by hitting back. - Piet > Hein > >>> (via Tom White) > >>> > >>> > >>> > >> > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
