gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: Podling Report Reminder - June 2017
Date Fri, 09 Jun 2017 00:22:56 GMT
Ok, will do that now Manu. Thanks.

On Thu, Jun 8, 2017 at 12:06 AM, Manu Zhang <owenzhang1990@gmail.com> wrote:

> Andy, do you have more questions ? Otherwise, could you help to post and
> sign off the report ?
>
> Thanks,
> Manu
>
> On Wed, Jun 7, 2017 at 9:06 AM Manu Zhang <owenzhang1990@gmail.com> wrote:
>
> > Hi Andy,
> >
> > Updated below. Yes, #3 is not necessary for graduation. Although we've
> > made several releases but each had taken more than 3 months.
> > We need to release more frequently (#1) and the real issue blocking
> > graduation, IMHO, is #2 and the updated #3. I don't feel confident for
> > graduation
> > unless we have more contributors and more users to adopt Gearpump in the
> > coming months.
> >
> >  Gearpump
> >
> >  Gearpump is a reactive real-time streaming engine based on the
> > micro-service Actor model.
> >  Gearpump has been incubating since 2016-03-08.
> >
> >  Three most important issues to address in the move towards graduation:
> >
> >  1.  Have frequent release cycles.
> >  2. Continue to evolve community interest and support.
> >  3. Increase user adoption.
> >
> >  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware
> >  of?
> >  - None.
> >
> >
> >  - How has the community developed since the last report?
> >  - Increased community contribution on rabbitmq connector and state
> > management.
> >
> >  - How has the project developed since the last report?
> >  - 27 issues created and 24 issues resolved.
> >  - Continued integration within Apache Beam (Gearpump Runner).
> >  - Joined in GSoC 2017 project.
> >
> >  Date of last release:
> >  2017-04-19
> >
> >
> >  When were the last committers or PMC members elected?
> >  No new committers or PMC members elected yet.
> >
> >  Signed-off-by:
> >
> >  [ ](gearpump) Jean-Baptiste Onofré
> >  [ ](gearpump) Andrew Purtell
> >  [ ](gearpump) Jarek Jarcec Cecho
> >  [ ](gearpump) Reynold Xin
> >  [ ](gearpump) Todd Lipcon
> >  [ ](gearpump) Xuefu Zhang
> >
> > On Wed, Jun 7, 2017 at 3:59 AM Andrew Purtell <apurtell@apache.org>
> wrote:
> >
> >> lgtm
> >>
> >> Question:
> >> >  1. Make initial Apache branded release and release on a regular
> >> schedule.
> >>
> >> ​Want to update this? You've made a couple of releases.
> >>
> >> Have you considered how far along to graduation you think you are? Are
> the
> >> technical requirements in your item #3 necessary for graduation? Why?
> >> Isn't
> >> graduation about process and adopting ASF norms? Do you feel you need
> more
> >> time in incubation or would you consider voting on graduation soon?​
> >>
> >>
> >>
> >> On Mon, Jun 5, 2017 at 1:20 AM, Manu Zhang <owenzhang1990@gmail.com>
> >> wrote:
> >>
> >> > AFAIK, There hasn't been much progress on akka-stream integration
> since
> >> > last report.
> >> > Do you have any suggestions ?
> >> >
> >> > On Mon, Jun 5, 2017 at 4:15 PM Karol Brejna <karolbrejna@apache.org>
> >> > wrote:
> >> >
> >> > > Manu,
> >> > >
> >> > > Do we mention the effort on akka-streams integration?
> >> > >
> >> > > Otherwise, looks good.
> >> > >
> >> > > Karol
> >> > >
> >> > > On Mon, Jun 5, 2017 at 3:13 AM, Manu Zhang <owenzhang1990@gmail.com
> >
> >> > > wrote:
> >> > > > Hi all,
> >> > > >
> >> > > > Here is the Gearpump Podling Report. Please review.
> >> > > >
> >> > > >  Gearpump
> >> > > >
> >> > > >  Gearpump is a reactive real-time streaming engine based on the
> >> > > > micro-service Actor 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 Apache Beam and akka-stream frameworks.
> >> > > >
> >> > > >  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
> >> to
> >> > be
> >> > > > aware
> >> > > >  of?
> >> > > >  - None.
> >> > > >
> >> > > >
> >> > > >  - How has the community developed since the last report?
> >> > > >  - Increased community contribution on rabbitmq connector and
> state
> >> > > > management.
> >> > > >
> >> > > >  - How has the project developed since the last report?
> >> > > >  - 27 issues created and 24 issues resolved.
> >> > > >  - Continued integration within Apache Beam (Gearpump Runner).
> >> > > >  - Joined in GSoC 2017 project.
> >> > > >
> >> > > >  Date of last release:
> >> > > >  2017-04-19
> >> > > >
> >> > > >
> >> > > >  When were the last committers or PMC members elected?
> >> > > >  No new committers or PMC members elected yet.
> >> > > >
> >> > > >  Signed-off-by:
> >> > > >
> >> > > >  [ ](gearpump) Jean-Baptiste Onofré
> >> > > >  [ ](gearpump) Andrew Purtell
> >> > > >  [ ](gearpump) Jarek Jarcec Cecho
> >> > > >  [ ](gearpump) Reynold Xin
> >> > > >  [ ](gearpump) Todd Lipcon
> >> > > >  [ ](gearpump) Xuefu Zhang
> >> > > >
> >> > > > On Mon, Jun 5, 2017 at 6:19 AM <johndament@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, 21 June 2017, 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 07).
> >> > > >>
> >> > > >> 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.
> >> > > >> *   How does the podling rate their own maturity.
> >> > > >>
> >> > > >> This should be appended to the Incubator Wiki page at:
> >> > > >>
> >> > > >> https://wiki.apache.org/incubator/June2017
> >> > > >>
> >> > > >> 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
> >>
> >> If you are given a choice, you believe you have acted freely. - Raymond
> >> Teller (via Peter Watts)
> >>
> >
>



-- 
Best regards,

   - Andy

If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message