Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-06-21 20:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Aurora

21 Jun 2017 [Jake Farrell / Phil]

Report was filed, but display is awaiting the approval of the Board minutes.

15 Mar 2017 [Jake Farrell / Brett]

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 community has continued to see growth from new
contributors over the last quarter while working on our latest 0.17.0 release,
which was successfully released on February 6th. There has been a great
deal of open discussions on the mailing lists surrounding dynamic
reservations, rolling restarts and recently the idea of leveraging Apache
Aurora to start Apache Mesos Maintenance. The Apache
Aurora PMC also added a new committer, Santhosh Shanmugham, as
well as added a new PMC member Mehrdad Nurolahzade.

Community
---
Latest Additions:

* Committer addition: Santhosh Kumar Shanmugham, 2.9.2017
* PMC addition:       Mehrdad Nurolahzade, 2.24.2017

Issue backlog status since last report:

* Created:  50
* Resolved: 51

Mailing list activity since last report:

* @dev      124 messages
* @user     24 messages
* @reviews  1292 messages

Releases
---
Last release: Apache Aurora 0.17.0 released 02.06.2017

21 Dec 2016 [Jake Farrell / Mark]

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 community has continued to see growth from new users and
contributors over the last quarter. There has been a great deal of activity
in open code reviews with excellent community involvement. In September we
released Apache Aurora 0.16.0 and since have started discussions about our
next 0.17.0 release candidate. The next release will focus on a number of
bug fixes, stability enhancements as well as some new features outlined in
our release notes [1]

Community
---
Latest Additions:

* Committer addition: Stephan Erb, 2.3.2016
* PMC addition:       Stephan Erb, 2.3.2016

Issue backlog status since last report:

* Created:  86
* Resolved: 57

Mailing list activity since last report:

* @dev      169 messages
* @user     37 messages
* @reviews  1391 messages

Releases
---
Last release: Apache Aurora 0.16.0 released 09.28.2016


[1]: https://github.com/apache/aurora/blob/master/RELEASE-NOTES.md

21 Sep 2016 [Jake Farrell / Isabel]

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 community has continued to see growth from new users and
contributors while releasing Apache Aurora 0.15.0 and making progress on our
upcoming 0.16.0 release candidate. The upcoming  release will contain a number
of bug fixes, stability enhancements as well as updating support for Apache
Mesos 1.0.0, multiple executor support, and defaulting to using Apache Curator
for scheduler leader election. Community design discussion have started around
dynamic reservations and job update configuration.

Community
---
Latest Additions:

* PMC addition: Stephan Erb, 2.3.2016

Issue backlog status since last report:

* Created:  53
* Resolved: 35

Mailing list activity since last report:

* @dev      270 messages
* @user     73 messages
* @reviews  863 messages

Releases
---
Last release: Apache Aurora 0.15.0 released 07.06.2016
Release candidate: Apache Aurora 0.16.0 release candidate in progress

20 Jul 2016

Change the Apache Aurora Project Chair

 WHEREAS, the Board of Directors heretofore appointed Bill Farner
 to the office of Vice President, Apache Aurora, and

 WHEREAS, the Board of Directors is in receipt of the resignation of
 Bill Farner from the office of Vice President, Apache Aurora, and

 WHEREAS, the Community of the Apache Aurora project
 has chosen to recommend Jake Farrell as the successor to the
 post;

 NOW, THEREFORE, BE IT RESOLVED, that Bill Farner is relieved and
 discharged from the duties and responsibilities of the office of Vice
 President, Apache Aurora, and

 BE IT FURTHER RESOLVED, that Jake Farrell be and hereby is
 appointed to the office of Vice President, Apache Aurora, to serve in
 accordance with and subject to the direction of the Board of Directors.
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed.

 Special Order 7B, Change the Apache Aurora Project Chair, was
 approved by Unanimous Vote of the directors present.

15 Jun 2016 [Bill Farner / Isabel]

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 community has continued to see growth from new users and
contributors while working towards our upcoming 0.14.0 release. The upcoming
release will contain a number of bug fixes, stability enhancements and new
experimental features added such as Mesos GPU resource support, external
webhook support, launching tasks using filesystem image with the new Apache
Mesos unified containerizer.

Bill Farner has indicated that he would like to step down as the Apache Aurora
PMC chair, discussion and vote thread for a new chair will be started soon.

Community
---
Latest Additions:

* PMC addition: Stephan Erb, 2.3.2016

Issue backlog status since last report:

* Created:   62
* Resolved:  80

Mailing list activity since last report:

* @dev    329 messages
* @user   103 messages

Releases
---
Last release: Apache Aurora 0.13.0 released 4.13.2016
Release candidate: Apache Aurora 0.14.0 release candidate vote is currently in progress

16 Mar 2016 [Bill Farner / Greg]

## Description:
  Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It
  supports running long-running services, cron jobs, and ad-hoc jobs.

## Issues:
 There are no issues requiring board attention at this time.

## Activity:
 - Significant number of contributors in recent 0.11.0 and 0.12.0 releases.
 - Positive feedback from prebuilt binary packages (including nightlies),
   signs of many users taking advantage of this to build their own.

## Health report:
 Aurora has been under active development for this period, with strong
 community engagement.  We have placed deliberate effort to build release
 notes as we iterate towards future releases, which has received positive
 feedback from users.

## PMC changes:
 - Currently 17 PMC members.
 - New PMC members:
    - Joshua Cohen was added to the PMC on Tue Dec 22 2015
    - John Sirois was added to the PMC on Sun Jan 03 2016
    - Stephan Erb was added to the PMC on Wed Feb 03 2016
    - Steve Niemitz was added to the PMC on Mon Jan 11 2016

## Committer base changes:
 - Currently 18 committers.
 - New commmitters:
    - John Sirois was added as a committer on Mon Jan 04 2016
    - Stephan Erb was added as a committer on Wed Feb 03 2016
    - Steve Niemitz was added as a committer on Tue Jan 12 2016

## Releases:
 - 0.11.0 was released on Wed Dec 23 2015
 - 0.12.0 was released on Sun Feb 07 2016

## JIRA activity:
 - 79 JIRA tickets created in the last 3 months
 - 185 JIRA tickets closed/resolved in the last 3 months

16 Dec 2015 [Bill Farner / Sam]

## Description:
 - Apache Aurora lets you use an Apache Mesos cluster as a private cloud.
   It supports running long-running services, cron jobs, and ad-hoc jobs.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - Successfully released 0.10.0, expecting 0.11.0 shortly after the new year.
 - Recent work to provide RPM/deb packages have been successful, but needs
   more towards documentation and examples.

## Health report:
 - Mail/commits/issues have been active (slightly less so than the previous
   report period, which may be attributed to end-of-year slump).

## PMC changes:
 - Currently 13 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Henry Saputra on Tue Mar 17 2015

## Committer base changes:
 - Currently 15 committers.
 - No new changes to the committer base since last report.

## Releases:
 - 0.10.0 was released on Mon Nov 16 2015

## Mailing list activity:
 - dev@aurora.apache.org:
    - 160 subscribers (up 12 in the last 3 months):
    - 281 emails sent to list (279 in previous quarter)

 - user@aurora.apache.org:
    - 42 subscribers (up 42 in the last 3 months):
    - 30 emails sent to list (0 in previous quarter)

 - announcements@aurora.apache.org:
    - 28 subscribers (up 28 in the last 3 months)

 - issues@aurora.apache.org:
    - 44 subscribers (up 7 in the last 3 months):
    - 555 emails sent to list (734 in previous quarter)

 - reviews@aurora.apache.org:
    - 38 subscribers (up 5 in the last 3 months):
    - 904 emails sent to list (1275 in previous quarter)

## JIRA activity:
 - 68 JIRA tickets created in the last 3 months
 - 64 JIRA tickets closed/resolved in the last 3 months

16 Sep 2015 [Bill Farner / Greg]

## Description:

Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It
supports running long-running services, cron jobs, and ad-hoc jobs.

## Activity:
 - Release planning underway (0.10.0)
 - Major effort recently for official installable packages (RPMs and debs)
   - released of debs for 0.9.0, close to release of RPMs
   - preparing infrastructure for nightly packages

## Health report:
 There has been healthy development on Aurora for this period, though we hope to
 see more growth in adoption, contributions, and committers.  There has been
 significant effort to make alternatives to Aurora (e.g. Kubernetes, Marathon)
 easy to install and use, and Aurora is relatively more complicated to evaluate.
 Packaging and better introductory documentation will our focus to address this.

## Issues:
 - There are no issues requiring board attention at this time.

## LDAP committee group/Committership changes:

 - Currently 15 committers and 13 LDAP committee group members.
 - New PMC member: Zameer Manji, 2014-01-14
 - New committer: Joshua Cohen, 2015-02-02

## Releases:

 - 0.9.0 was released on Thu Jul 23 2015

## Mailing list activity:

 - dev@aurora.apache.org:
    - 147 subscribers (up 11 in the last 3 months):
    - 293 emails sent to list (437 in previous quarter)

 - reviews@aurora.apache.org:
    - 33 subscribers (up 0 in the last 3 months):
    - 1298 emails sent to list (1419 in previous quarter)

 - issues@aurora.apache.org:
    - 37 subscribers (down -1 in the last 3 months):
    - 753 emails sent to list (844 in previous quarter)

17 Jun 2015 [Bill Farner / Jim]

Apache Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Project Status
---------
Since our last 0.8.0 release Apache Aurora has been working on bug fixes and
packaging (deb, rpm) to help users with the install process. Design
discussions for health checks have been occurring on the mailing list and
progress has started towards our next release candidate (0.9.0) and we hope to
make it available in the next two weeks.

Community
---
Latest Additions:

* PMC addition:         Zameer Manji, 2014-01-14
* Contributor addition: Joshua Cohen, 2015-02-02

Issue backlog status since last report:

* Created:   37 [1]
* Resolved:  30 [2]

Mailing list activity since last report:

* @dev      96  messages
* @reviews  447 messages

Releases
---
Last release: 0.8.0 was released on 2015-05-15

[1]: http://s.apache.org/EhX
[2]: http://s.apache.org/dfe

20 May 2015 [Bill Farner / Chris]

## Description:

Apache Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

## Activity:

- Vote for 0.8.0 release is underway
- Starting monthly cadence for events on SF Bay Area Apache Aurora Users
 Group [1]

## Issues:

None to report at this time.

## PMC/Committership changes

- New PMC member: Zameer Manji, 2014-01-14
- New committer: Joshua Cohen, 2015-02-02

## Releases

Last release: 0.7.0-incubating, Release Date: Feb 05, 2015

## Mailing list activity

- dev@aurora.apache.org:
 - 133 subscribers
 - 93 e-mails in the last month [2]

## JIRA activity

- 27 JIRA tickets created in the last month [3]
- 47 JIRA tickets closed/resolved in the last month [4]


[1] http://meetup.com/Bay-Area-Apache-Aurora-Users-Group
[2] http://s.apache.org/ytb
[3] http://s.apache.org/gmt
[4] http://s.apache.org/KIm

22 Apr 2015 [Bill Farner / Greg]

## Description:

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

## Activity:

- Graduated from the Incubator in March.
- Promising adoption increase in the last 3 months: increased dev@ and IRC
 activity, and patches from the community.
- Community activity has identified some promising candidates to add as
 committers and/or PMC members.
- Release and deprecation processes are starting to take shape, making for a
 clear development path between releases.
- 0.8.0 release is likely to be cut in April.

## Issues:

No major issues.  We endured a long bout of CI noise due to Jenkins slave
flakiness (INFRA-9019, now resolved), but continue to face a whack-a-mole of
other related issues.

## PMC/Committership changes

- New PMC member: Zameer Manji, 2014-01-14
- New committer: Joshua Cohen, 2015-02-02

## Releases

Last release: 0.7.0-incubating, Release Date: Feb 05, 2015

## Mailing list activity

- dev@aurora.apache.org:
 - 126 subscribers
 - 487 e-mails in the last 3 months [1]

## JIRA activity

- 264 JIRA tickets created in the last 3 months [2]
- 176 JIRA tickets closed/resolved in the last 3 months [3]

[1] http://s.apache.org/4uA
[2] http://s.apache.org/AT6
[3] http://s.apache.org/W6r

18 Mar 2015

Establish the Apache Aurora Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to a framework for long-running services
 and cron jobs.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Aurora Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Aurora Project be and hereby is
 responsible for the creation and maintenance of software
 related to a framework for long-running services and cron
 jobs; and be it further

 RESOLVED, that the office of "Vice President, Apache Aurora" be
 and hereby is created, the person holding such office to
 serve at the direction of the Board of Directors as the chair
 of the Apache Aurora Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Aurora Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Aurora Project:

    * Mark Chu-Carroll <mchucarroll@apache.org>
    * Bill Farner <wfarner@apache.org>
    * Jake Farrell <jfarrell@apache.org>
    * Benjamin Hindman <benh@apache.org>
    * Suman Karumuri <mansu@apache.org>
    * Maxim Khutornenko <maxim@apache.org>
    * Dave Lester <dlester@apache.org>
    * Chris Mattmann <mattmann@apache.org>
    * David McLaughlin <dmclaughlin@apache.org>
    * Henry Saputra <hsaputra@apache.org>
    * Kevin Sweeney <kevints@apache.org>
    * Brian Wickman <wickman@apache.org>
    * Zameer Manji <zmanji@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Bill Farner
 be appointed to the office of Vice President, Apache Aurora, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache Aurora PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Aurora Project; and be it further

 RESOLVED, that the Apache Aurora Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Aurora podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Aurora podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

 Special Order 7A, Establish the Apache Aurora Project, was
 approved by Unanimous Vote of the directors present.

21 Jan 2015

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. Expanding the community's diversity and adding new committers.
 2. Third Apache release, progress being tracked in ticket AURORA-872
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 * None at this time.

How has the community developed since the last report?

 Latest Additions:

 * PMC addition:
   * David McLaughlin, 2014-08-20
 * Contributor additions: No additional contributors had code committed
   since the last report, however three new contributors currently have
   code under review that was submitted within the past 6 weeks. At least
   one of these contributions is a large feature addition, which is
   promising.

 Issue backlog status since last report (Oct 1, 2014):

 * Created:   212
 * Resolved:  177

 Mailing list activity since last report:

 * @dev      480 messages
 * @issues   1085 messages
 * @reviews  2235 messages

How has the project developed since the last report?

 * Increased participation from new contributors within the Aurora core and
   ecosystem, for example a Chef cookbook and Docker support under
   development.
 * Continued to hold weekly IRC meetings, digests sent to dev@ list
 * Large improvements to project documentation and website.

Date of last release:

 * Apache Aurora 0.6.0 (incubating) - 2014-11-21

When were the last committers or PMC members elected?

 * David McLaughlin, 2014-08-20

Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [X](aurora) Chris Mattmann
 [X](aurora) Henry Saputra

Shepherd/Mentor notes:

 P. Taylor Goetz (ptgoetz):

   Podling looks very healthy. 3 of 4 mentors engaged since last report.

15 Oct 2014

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. Second release, progress being tracked in ticket AURORA-711
 2. Establish a consistent development process and release rhythm.
 3. Expanding the community and continuing to add new committers.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time.

How has the community developed since the last report?

 Latest Additions:

 * PMC addition:           David McLaughlin, 2014-08-20
 * Contributor addition:   David McLaughlin, 2014-08-20

 Issue backlog status since last report:

 * Created:   176
 * Resolved:  151

 Mailing list activity since last report:

 * @dev      340 messages
 * @issues   774 messages
 * @reviews  1402 messages

How has the project developed since the last report?

 - IRC weekly meetings, digests sent to dev@ list
 - Automated release workflows
 - Fixing issues brought up in our first release

Date of last release:

 - Apache Aurora 0.5.0 (incubating) - 2014-08-01


Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [X](aurora) Henry Saputra

16 Jul 2014

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. First release, progress being tracked in ticket AURORA-147
 2. Establish a consistent development process and release rhythm.
 3. Expanding the community and continuing to add new committers.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time.

How has the community developed since the last report?

 Latest Additions:

 * PMC addition:           Mark Chu-Carroll, 2014-02-03
 * Contributor addition:   Mark Chu-Carroll, 2014-01-14

 Issue backlog status since last report:

 * Created:   257
 * Resolved:  161

 Mailing list activity since last report:

 * @dev      254 messages
 * issues    987 messages
 * @reviews  1487 messages

How has the project developed since the last report?

 - IRC weekly meetings, digests sent to dev@ list
 - Automating release workflows
 - Fixing issues brought up in our first release candidate

Date of last release:

 - No releases as of yet. We have created our first release candidate,
   0.5.0-rc0, and working to fix issues found within it. 0.5.0-rc1
   being targeted within the next week


Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [X](aurora) Henry Saputra

16 Apr 2014

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. First release, progress being tracked in ticket AURORA-147
 2. Establish a consistent development process and release rhythm.
 3. Expanding the community and continuing to add new committers.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time.

How has the community developed since the last report?

 Latest Additions:

 * PMC addition:           Mark Chu-Carroll, 2014-02-03
                           Jake Farrell, 2014-01-23
 * Contributor addition:   Mark Chu-Carroll, 2014-01-14

 Issue backlog status since last report:

 * Created:   296 (includes initial import)
 * Resolved:  141

 Mailing list activity since last report:

 * @dev      624 messages
 * issues    503 messages
 * @reviews  1499 messages

How has the project developed since the last report?

 - Jira issues have been imported to issues.apache.org
 - Documented contributing guide and committers workflow
 - Automating release workflows and preparing for our first release
   candidate

Date of last release:

 - No releases as of yet. Targeting first release within the next couple
   weeks.


Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [X](aurora) Henry Saputra

15 Jan 2014

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. First release.
 2. Establish a consistent development process and release rhythm.
 3. Expanding the community and adding new committers.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time.

How has the community developed since the last report?

 - Community members outside of Twitter are installing and testing the
   software, using the dev mailing list and IRC channel to offer feedback
   and seek help.
 - No new committers; still preparing for first release.

How has the project developed since the last report?

 - Development work has transitioned to Apache Review Board in the open;
   JIRA issues still need to be transferred.
 - Continuous integration for Aurora set up on builds.apache.org.

Date of last release:

 - No releases as of yet. Targeting first release for Q1.

When were the last committers or PMC members elected?

 - No new committers; still stabilizing code and preparing for first
   release.

Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [X](aurora) Henry Saputra

Shepherd/Mentor notes:

 Justin Mclean (jmclean):

   Project is off to a good start with lots of activity on the mailing list
   and in JIRA. One of the Mentors (Jake Farrell) is very active and there
   are no issues that need attention.

18 Dec 2013

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues to address in the move towards graduation:

 1. First release.
 2. Establish a consistent development process and release rhythm.
 3. Expanding the community and adding new committers.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time.

How has the community developed since the last report?

 - Finish bootstrapping project, IP clearance, initial website.
 - Announcement and live demo at first #MesosTownhall.

How has the project developed since the last report?

 - Code has been approved and migrated to Apache, complete with (scrubbed)
   commit history.
 - Development work has continued inside of Twitter, but will now begin
   moving to the open.

Date of last release:

 - No releases as of yet. Targeting first release for mid-January.

When were the last committers or PMC members elected?

 - No new committers; still stabilizing code and preparing for first
   release.

Signed-off-by:

 [x](aurora) Jake Farrell
 [x](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [x](aurora) Henry Saputra

Shepherd notes:

 Jake Farrell (jfarrell):

   For Aurora everything is progressing nicely.  All initial setup and on
   boarding is completed and development has started using ASF
   infrastructure (jira/reviewboard/etc).  No blockers or issues at this
   time.

20 Nov 2013

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

Aurora has been incubating since 2013-10-01.

Three most important issues

 - Finish bootstrapping project, IP clearance, initial website
 - Expanding the community and adding new committers
 - 1st release

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 - None at this time

How has the community developed since the last report?

 - All initial committers have submitted ICLAs and the accounts have been
   created. The mailing lists have been setup and we have started using
   them for communication.

How has the project developed since the last report?

 - We have setup the incubator status page and are working with
   infrastructure to get everything setup, more details are available in
   INFRA-6819.

Date of last release

 - No releases as of yet. Working on IP clearance.

When were the last committers or PMC members elected?

 - N/A, still bootstrapping the project.

Signed-off-by:

 [X](aurora) Jake Farrell
 [ ](aurora) Benjamin Hindman
 [ ](aurora) Chris Mattmann
 [X](aurora) Henry Saputra