Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2018-11-21 21: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.

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

Nemo

19 Sep 2018

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

 1. Grow the community
 2. Create the first Apache release
 3. Donate code to ASF

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?

 * Committers actively sent PRs and did code reviews
 * Committers actively involved in mailing lists
 * Getting contributors including a GSoC student

How has the project developed since the last report?

 * Made great progress in every aspect of the project
 * Working on the first release Almost done with the features to be
   included in the first release
 * Solidified runtime by refactoring how to handle
   tasks, stages, and jobs, and scheduling policies
 * Rule-based policy support in the compiler
 * Composition of passes
 * Added Multiple DAG submission support in a user
   program
 * Added Beam 2.6, Beam SQL support
 * Spark RDD caching support
 * Task cloning support
 * Intermediate data locality aware scheduling
 * Added a WebUI (contributed by a GSoC student),
   which we will polish

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [X] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 None yet.

When were the last committers or PPMC members elected?

 None yet.

Signed-off-by:

 [X](nemo) Davor Bonaci
    Comments: All great; active community contributing towards the first
    release.
 [X](nemo) Hyunsik Choi
    Comments:
 [X](nemo) Byung-Gon Chun
    Comments:
 [X](nemo) Jean-Baptiste Onofre
    Comments: Focusing on first release would be great, it would be a
    great milestone for the podling
 [X](nemo) Markus Weimer
    Comments: Good progress all around; but it is time for a first release
    :)
 [ ](nemo) Reynold Xin
    Comments:

IPMC/Shepherd notes:

 Our mentors mostly have been helpful and responsive.

20 Jun 2018

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

 1. Grow the community
 2. Create a first Apache release
 3. Donate code to ASF

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?

 * Committers actively involved in mailing lists
 * Committers actively started to send PRs and do code reviews

How has the project developed since the last report?

 * Progress towards supporting Spark DSL programs
 * Refactoring the Nemo runtime
 * Finishing up a paper that describes the design and
   implementation of Nemo

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [X] Initial setup
 [X] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 None yet.

When were the last committers or PPMC members elected?

 None yet.

Signed-off-by:

 [X](nemo) Davor Bonaci
    Comments: Progress is probably a bit slower than before, but still
very high. Podling is doing great.
 [ ](nemo) Hyunsik Choi
    Comments:
 [X](nemo) Byung-Gon Chun
    Comments:
 [ ](nemo) Jean-Baptiste Onofre
    Comments:
 [ ](nemo) Markus Weimer
    Comments:
 [ ](nemo) Reynold Xin
    Comments:

IPMC/Shepherd notes:
 Dave Fisher: AFAICT the SGA has not been provided and a mentor has
 advised that this can wait until graduation.
 I don't think that is correct and it is not the same as the guidance
 given to other podlings like Heron.
 See
 https://lists.apache.org/thread.html/df7040d27bc8c01ec1601476b1e465226d4b1ea
99d0e5991b977fd1c@%3Cprivate.nemo.apache.org%3E

16 May 2018

Nemo is a data processing system to flexibly control the runtime behaviors of
a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

 1. Grow the community
 2. Create a first Apache release
 3. Donate code to ASF

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?

 * Committers actively involved in mailing lists
 * Committers actively started to send PRs and do code reviews
 * PPMC accepted a GSoC student to work on Nemo web UI issues

How has the project developed since the last report?

 * Progress towards supporting Spark DSL programs
 * Optimization policy for geo-distributed data analytics
 * Optimization policy for skew handling
 * Working on a paper that describes the design and
   implementation of Nemo

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [X] Initial setup
 [X] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 None yet.

When were the last committers or PPMC members elected?

 None yet.

Signed-off-by:

 [X](nemo) Davor Bonaci
    Comments: Good progress; the podling is on track.
 [ ](nemo) Hyunsik Choi
    Comments:
 [X](nemo) Byung-Gon Chun
    Comments:
 [X](nemo) Jean-Baptiste Onofre
    Comments:
 [X](nemo) Markus Weimer
    Comments:
 [ ](nemo) Reynold Xin
    Comments:

18 Apr 2018

Nemo is a data processing system to flexibly control the runtime behaviors of
a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

 1. Grow the community
 2. Create a first Apache release
 3. Donate code to ASF

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?

 * Committers actively involved in mailing lists
 * Committers actively started to send PRs and do code reviews
 * Two committers volunteered for GSoC mentors

How has the project developed since the last report?

 * SonarCloud integrated
 * Community standards and documentation added
 * Scheduler improved by adding a new scheduling policy and making it
   reactive
 * Operator pipelining implemented
 * Experiments performed to demonstrate the benefits of Nemo
 * Blogs posted

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [x] Initial setup
 [x] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 None yet.

When were the last committers or PPMC members elected?

 None yet.

Signed-off-by:

 [X](nemo) Davor Bonaci Comments: The project is very active, moving quickly,
  and doing very well.
 [X](nemo) Hyunsik Choi Comments:
 [X](nemo) Byung-Gon Chun Comments:
 [X](nemo) Jean-Baptiste Onofre Comments:
 [ ](nemo) Markus Weimer Comments:
 [ ](nemo) Reynold Xin Comments:

21 Mar 2018

Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

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

  1.  Grow the community
  2.  Create a first Apache release
  3.  Donate code to ASF

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?

  * Committers filed ICLAs.
  * Committers enrolled in mailing lists
  * Committers enrolled in the slack channel
  * Committers used mailing lists to discuss initial setups
  * Committers started to send PRs to the apache infra

How has the project developed since the last report?

  * gitbox/github set up and code transferred from snuspl/nemo to apache/incubator-nemo
  * JIRA created and issues transferred from github to JIRA
  * web site set up
  * mailing lists set up
  * The name ‘Apache Nemo’ approved (PODLINGNAMESEARCH-139)

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  [x] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  None yet.

When were the last committers or PPMC members elected?

 None yet.

Signed-off-by:

  [X](nemo) Davor Bonaci
     Comments: The podling is moving very quickly.
  [ ](nemo) Hyunsik Choi
     Comments:
  [X](nemo) Byung-Gon Chun
     Comments:
  [X](nemo) Jean-Baptiste Onofre
     Comments:
  [ ](nemo) Markus Weimer
     Comments:
  [ ](nemo) Reynold Xin

IPMC/Shepherd notes:

  johndament:  Seeing good progress with on list communication.