Re: ASF Board Report for Aurora - Repeated Reminder for February 2019

[Stephan Erb <se...@apache.org>]

Dear ASF Board,

due to the absence of our PMC chair I would like to submit the following report.
However, as a regular PMC I am lacking the necessary permissions for the submission
methods described over here https://www.apache.org/foundation/board/reporting#how.

Please assist.

Best regards,
Stephan Erb

-------------------------

Apache Aurora is a stateless and fault tolerant service scheduler used to
schedule jobs onto Apache Mesos such as long-running services, cron jobs,
and one off tasks.

Project Status
--------------
The Apache Aurora project has seen a significant slowdown of user and
contributor activity over the most recent months. This can partially be
attributed to the overall stability and maturity of the project, but
more importantly this is due to other external projects that managed to
win the developer mindshare within the container orchestration field
(e.g., general purpose cloud providers, Kubernetes, ...).

The project might be heading towards the Apache Attic in the future,
unless the community interest increases again.

Community
---------

* Currently 21 PMC members
* Currently 22 committer
* No new PMC members added in the last 3 months. 
  Last PMC addition was Jordan Ly on Thu May 03 2018.
* No new committers added in the last 3 months. 
  Last committer addition was Renan DelValle at Sat Jan 27 2018

Issue backlog status since last report:

* 0 JIRA tickets created in the last 3 months 
* 1 JIRA tickets closed/resolved in the last 3 months 

Mailing list activity since last report:

* @dev         9 messages (127 in previous quarter) 
* @user        2 messages (13 in previous quarter) 
* @reviews     22 messages (181 in previous quarter) 
* @issues      8 messages (15 in previous quarter)


Releases
--------
Last release:
*  0.21.0 was released on Sun Sep 09 2018



On Thu, 2019-01-31 at 19:58 +0000, Phil Steitz wrote:
> Dear Aurora community,
> 
> In the governance model at the ASF the board delegates responsibility for
> managing projects to PMCs. To enable the board to provide oversight across the
> foundation, PMCs are tasked with providing the board with a quarterly
> report on the health of the project. The board has noticed that the reports
> for Aurora have been missed for a number of months.
> 
> The reports to the board are normally written by the PMC chair but all PMC
> members have an individual responsibility to ensure that a report is
> submitted. If the PMC chair is not available then any PMC member can submit
> the report. If you need help with this process, please reach out to
> board@apache.org
> 
> 
> Please ensure that a report for Aurora is submitted to the board for the
> next meeting.
> 
> If the PMC chair is not going to be available for an extended period of time
> it may make sense to rotate the PMC chair. Rotating the PMC chair does not
> mean the current chair has failed. People's situations and interests change,
> and rotation is good as it allows more people to become familiar with that
> role. Again, if assistance is required with this process, please feel free to
> reach out to 
> board@apache.org
> 
> 
> As projects mature, they will naturally reach a point where activity reduces
> to a level that the project is no longer sustainable. At Apache, projects
> reach this stage when there are no longer 3 active PMC members providing
> oversight. Projects that reach this stage are placed in the attic[1].  If
> Aurora has reached this point, please reach out to the Attic project to
> arrange transfer. On the other hand, if your project is mostly dormant but
> still has at least three active PMC members it can stay in that state for as
> long as needed. If your project is in such a state, please mention that in
> your report and verify the PMC's state at regular intervals.
> 
> Finally, if you have any questions please feel free to reach out to
> board@apache.org
> .
> 
> Thanks,
> The ASF Board
> 
> [1] (
> http://attic.apache.org/
> 

Re: ASF Board Report for Aurora - checked in for February 2019

[Shane Curcuru <as...@shanecurcuru.org>]

I've posted this to the board agenda, you're all set.  Thanks for
stepping up to ensure a report gets in.

Thinking ahead, it's fine and natural when projects start to slow down.
 What the board will want to see in the next quarter is that at least
three PMC members are still active and providing oversight for the project.

No action needed now; but when your next report is due, having three PMC
members explicitly say "I'm here!" would be helpful.

Good luck on keeping the energy!

-- 

- Shane
  Director & Member
  The Apache Software Foundation

Stephan Erb wrote on 2/1/19 5:57 PM:
> Apache Aurora is a stateless and fault tolerant service scheduler used to
> schedule jobs onto Apache Mesos such as long-running services, cron jobs,
> and one off tasks.
> 
> Project Status
> --------------
> The Apache Aurora project has seen a significant slowdown of user and
> contributor activity over the most recent months. This can partially be
> attributed to the overall stability and maturity of the project, but
> more importantly this is due to other external projects that managed to
> win the developer mindshare within the container orchestration field
> (e.g., general purpose cloud providers, Kubernetes, ...).
> 
> The project might be heading towards the Apache Attic in the future,
> unless the community interest increases again.
> 
> Community
> ---------
> 
> * Currently 21 PMC members
> * Currently 22 committer
> * No new PMC members added in the last 3 months. 
>   Last PMC addition was Jordan Ly on Thu May 03 2018.
> * No new committers added in the last 3 months. 
>   Last committer addition was Renan DelValle at Sat Jan 27 2018
> 
> Issue backlog status since last report:
> 
> * 0 JIRA tickets created in the last 3 months 
> * 1 JIRA tickets closed/resolved in the last 3 months 
> 
> Mailing list activity since last report:
> 
> * @dev         9 messages (127 in previous quarter) 
> * @user        2 messages (13 in previous quarter) 
> * @reviews     22 messages (181 in previous quarter) 
> * @issues      8 messages (15 in previous quarter)
> 
> 
> Releases
> --------
> Last release:
> *  0.21.0 was released on Sun Sep 09 2018