You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myriad.apache.org by Álvaro Fernández <al...@gmail.com> on 2018/06/01 13:00:23 UTC
Re: Podling Report Reminder - June 2018
Hi Javi,
It looks OK to me :)
A.
On 31 May 2018 at 08:12, Javi Roman <jr...@gmail.com> wrote:
> Hi!
>
> Please, take a look to this month reporting draft. Feel free of
> modifying, or give any feedback.
> This will be the final report whether we will not modifications in the
> next two days.
>
> Best.
>
> [DRAFT]
>
> Myriad
>
> - Description:
>
> Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos
> together on the same cluster and allows dynamic resource allocations
> across both Hadoop and other applications running on the same physical
> data center infrastructure.
>
> Myriad has been incubating since 2015-03-01.
>
> - Three most important issues to address in the move towards graduation:
>
> 1. Grow the community and enroll new committers.
> 2. Have (more) frequent Release cycles to be compliant with the Apache
> Way. Creating roadmaps for releases with goals (new features).
> 3. Social media presence (new blog entries, conference talks).
>
>
> - Any issues that the IPMC or ASF Board wish/need to be aware of?:
>
> There are no new issues requiring board attention at this time.
>
>
> - How has the community developed since the last report:
>
> 1. Two new committers/PMC members from the last report (total 8
> committers).
> 2. Increase activity in the dev mailing list.
> 3. Twitter account with 1017 followers and daily basis activity.
> 4. Community chat channel with 7 registered user (low activity).
>
> - How has the project developed since the last report:
>
> 1. Project rebooting roadmap on going with success: https://goo.gl/2gdcrP
> 2. Resolved JIRA Issues: 11
> 3. Pull Requests merged: 8
> 4. Strong local development environment for Apache Mesos and Mesosphere
> DC/OS.
>
>
> - How does the podling rate their own maturity:
>
> [ ] Initial setup
> [ ] Working towards first release
> [X] Community building
> [ ] Nearing graduation
> [x] Other: Project rebooting in progress, retirement risk not present
> right now.
>
>
> - Date of last release:
>
>
> The 0.2.0 release was issued on Jun 29, 2016. The .3 release is
> planned for this quarter.
>
>
> - When were the last committers or PPMC members elected?:
>
> 1. 2018-05-22 New committer/PMC member Juan P. Gilaberte.
> 2. 2018-03-28 New committer/PMC member Javi Roman.
>
>
> Signed-off-by:
>
> [ ](myriad) Benjamin Hindman
> Comments:
> [ ](myriad) Danese Cooper
> Comments:
> [ ](myriad) Ted Dunning
> Comments:
>
>
> [DRAFT]
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Wed, May 30, 2018 at 1:45 AM, <jm...@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, 20 June 2018, 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 06).
> >
> > 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.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > 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/June2018
> >
> > 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
>
Re: Podling Report Reminder - June 2018
Posted by Juan P <jp...@gmail.com>.
It looks perfect.
Thank you very much.
On 1 June 2018 at 15:00, Álvaro Fernández <al...@gmail.com> wrote:
> Hi Javi,
>
> It looks OK to me :)
>
> A.
>
> On 31 May 2018 at 08:12, Javi Roman <jr...@gmail.com> wrote:
>
> > Hi!
> >
> > Please, take a look to this month reporting draft. Feel free of
> > modifying, or give any feedback.
> > This will be the final report whether we will not modifications in the
> > next two days.
> >
> > Best.
> >
> > [DRAFT]
> >
> > Myriad
> >
> > - Description:
> >
> > Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos
> > together on the same cluster and allows dynamic resource allocations
> > across both Hadoop and other applications running on the same physical
> > data center infrastructure.
> >
> > Myriad has been incubating since 2015-03-01.
> >
> > - Three most important issues to address in the move towards graduation:
> >
> > 1. Grow the community and enroll new committers.
> > 2. Have (more) frequent Release cycles to be compliant with the Apache
> > Way. Creating roadmaps for releases with goals (new features).
> > 3. Social media presence (new blog entries, conference talks).
> >
> >
> > - Any issues that the IPMC or ASF Board wish/need to be aware of?:
> >
> > There are no new issues requiring board attention at this time.
> >
> >
> > - How has the community developed since the last report:
> >
> > 1. Two new committers/PMC members from the last report (total 8
> > committers).
> > 2. Increase activity in the dev mailing list.
> > 3. Twitter account with 1017 followers and daily basis activity.
> > 4. Community chat channel with 7 registered user (low activity).
> >
> > - How has the project developed since the last report:
> >
> > 1. Project rebooting roadmap on going with success:
> https://goo.gl/2gdcrP
> > 2. Resolved JIRA Issues: 11
> > 3. Pull Requests merged: 8
> > 4. Strong local development environment for Apache Mesos and Mesosphere
> > DC/OS.
> >
> >
> > - How does the podling rate their own maturity:
> >
> > [ ] Initial setup
> > [ ] Working towards first release
> > [X] Community building
> > [ ] Nearing graduation
> > [x] Other: Project rebooting in progress, retirement risk not present
> > right now.
> >
> >
> > - Date of last release:
> >
> >
> > The 0.2.0 release was issued on Jun 29, 2016. The .3 release is
> > planned for this quarter.
> >
> >
> > - When were the last committers or PPMC members elected?:
> >
> > 1. 2018-05-22 New committer/PMC member Juan P. Gilaberte.
> > 2. 2018-03-28 New committer/PMC member Javi Roman.
> >
> >
> > Signed-off-by:
> >
> > [ ](myriad) Benjamin Hindman
> > Comments:
> > [ ](myriad) Danese Cooper
> > Comments:
> > [ ](myriad) Ted Dunning
> > Comments:
> >
> >
> > [DRAFT]
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> >
> >
> > On Wed, May 30, 2018 at 1:45 AM, <jm...@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, 20 June 2018, 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 06).
> > >
> > > 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.
> > >
> > > Candidate names should not be made public before people are actually
> > > elected, so please do not include the names of potential committers or
> > > PPMC members in your report.
> > >
> > > 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/June2018
> > >
> > > 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
> >
>