Community-led development "The Apache Way"
This was extracted (@ 2021-04-07 00: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.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
YuniKorn is a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds.
YuniKorn has been incubating since 2020-01-21.
### Three most important unfinished issues to address before graduating:
1. Gain more contributors and active committers.
2. Establish a release cadence based on roadmap.
3. Improve the ease of deployment and documentation quality.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at this point in time.
### How has the community developed since the last report?
New committer vote is in progress (delayed due to Christmas break).
Two new large features started. Driven by different parts of the
community: gang scheduling and open tracing.
New release planned for the end of January 2021 and the search for a new
release manager has started.
### How has the project developed since the last report?
Major scheduler core code update rewrite committed.
Upgrades to build tools to the latest supported tool versions.
Testing matrix updated to support latest versions of Kubernetes.
Some statistics for the report period (2020-10-01 till 2021-12-31)
JIRA: 67 created, 56 resolved
PRs: 55 opened, 58 resolved
10 unique active code contributors (cumulative for all repos)
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-08-26
### When were the last committers or PPMC members elected?
New committer vote is in progress (delayed due to Christmas break).
### Have your mentors been helpful and responsive?
Yes, review of PRs and part of the community syncs
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of.
### Signed-off-by:
- [ ] (yunikorn) Junping Du
Comments:
- [x] (yunikorn) Felix Cheung
Comments:
- [X] (yunikorn) Jason Lowe
Comments:
- [X] (yunikorn) Holden Karau
Comments:
### IPMC/Shepherd notes:
YuniKorn is a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds.
YuniKorn has been incubating since 2020-01-21.
### Three most important unfinished issues to address before graduating:
1. Gain more contributors and active committers.
2. Establish a release cadence based on roadmap.
3. Improve the ease of deployment and documentation quality.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No critical issues at this point in time.
### How has the community developed since the last report?
The community has given multiple presentations at ApacheCON@Home receiving
good feedback.
One new committer was added and multiple new contributors were added.
Discussions around new or improved functionality have been started and are
progressing in either jira or the mailing list.
### How has the project developed since the last report?
A second release was finalised and released. Planning for the next release,
based on community use cases, is well on its way for later this year.
A new website was released based on a community contribution using a new
build system. The documentation was moved from separate repos to the
website.
As part of the latest release the release tool has been improved to remove
almost all manual steps.
Some statistics for the report period (2020-07-01 till 2020-09-30)
JIRA: 166 created, 129 resolved
PRs: 69 opened, 108 resolved
13 unique active code contributors (cumulative for all repos)
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-08-26
### When were the last committers or PPMC members elected?
A new committer was voted in and accepted on 21 September 2020.
No new PPMC members.
### Have your mentors been helpful and responsive?
Yes, votes and guidance on the release
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of.
### Signed-off-by:
- [ ] (yunikorn) Junping Du
Comments:
- [X] (yunikorn) Felix Cheung
Comments:
- [X] (yunikorn) Jason Lowe
Comments:
- [X] (yunikorn) Holden Karau
Comments: I’m excited with the progress.
### IPMC/Shepherd notes:
--------------------
YuniKorn is a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds.
YuniKorn has been incubating since 2020-01-21.
### Three most important unfinished issues to address before graduating:
1. Gain more contributors and active committers.
2. Improve documentation and access to the documentation.
3. Establish a release cadence based on roadmap
### Are there any issues that the IPMC or ASF Board need to be aware of?
No critical issues at this point in time
### How has the community developed since the last report?
The community has provided new use cases and pain points which helped
shape the roadmap.
A new website build was contributed to help improve access to the
documentation.
The project has presented at two virtual conference receiving great
feedback. We're now trying to convert the feedback into an expanded
community.
### How has the project developed since the last report?
A large number of changes have been made specifically to the deployment
and testing side of the project:
- moved to full Travis CI build
- added e2e tests
- provide convenience deployment via helm charts and ASF docker hub
Beside the deployment and test changes the project has worked on
stabilising the first release and adding a number of new features.
Planning for a second release has just begun.
Some statistics for the report period (2020-04-01 till 2020-06-30)
JIRA: 194 created, 133 resolved
PRs: 197 resolved, 11 unique contributors (cumulative for all repos)
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-05-04
### When were the last committers or PPMC members elected?
A new committer was voted in and accepted on 16 June 2020.
No new PPMC members.
### Have your mentors been helpful and responsive?
Yes, votes and guidance on the release
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of
### Signed-off-by:
- [ ] (yunikorn) Junping Du
Comments:
- [X] (yunikorn) Felix Cheung
Comments:
- [X] (yunikorn) Jason Lowe
Comments:
- [ ] (yunikorn) Holden Karau
Comments:
### IPMC/Shepherd notes:
YuniKorn is a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds.
YuniKorn has been incubating since 2020-01-21.
### Three most important unfinished issues to address before graduating:
1. Gain more contributors and active committers.
2. Improve documentation and provide a roadmap.
3. Work on a steady release cadence.
### Are there any issues that the IPMC or ASF Board need to be aware of?
- No critical issues at this point in time
### How has the community developed since the last report?
The project has presented during the Flink Forward virtual conference and
received good feedback from the attendees. Interest was shown by a number
of new parties in the project.
Added 2 new contributors to the project.
### How has the project developed since the last report?
The community has been working hard on the first release of the project.
The first release v0.8.0 was released on 4th May 2020.
Steps have been made to look at a roadmap for the following releases.
The YuniKorn website is deployed and content is actively maintained.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2020-05-04 v0.8.0
### When were the last committers or PPMC members elected?
No new committers or PPMC members have been added since starting
incubation.
### Have your mentors been helpful and responsive?
Active guidance during the release prep and votes were cast during the
release on the dev@ and incubator list.
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of
### Signed-off-by:
- [X] (yunikorn) Junping Du
Comments:
- [X] (yunikorn) Felix Cheung
Comments: good work on the first release. congrats!
- [X] (yunikorn) Jason Lowe
Comments:
- [ ] (yunikorn) Holden Karau
Comments:
### IPMC/Shepherd notes:
Apache YuniKorn (incubating) is a standalone resource scheduler responsible
for scheduling batch jobs and long-running services on large scale
distributed systems running in on-premises environments as well as
different public clouds.
Yunikorn has been incubating since: 2020-01-21
### Three most important unfinished issues to address before graduating:
- Gain more contributors and active committers.
- Launch the first Apache release.
- Improve documentation and provide a roadmap.
### Are there any issues that the IPMC or ASF Board need to be aware of?
- No critical issues at this point in time
### How has the community developed since the last report?
- The community has held its first sync-up. English sync up scheduled
bi-weekly, Mandarin sync up every 4 weeks from this time forward.
- Added 3 new contributors to the project.
### How has the project developed since the last report?
- started working on the first release (version 0.8)
- notification for JIRA and GitHub setup finished
- website development has started (including build process)
### 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:
N.A.
### When were the last committers or PPMC members elected?
No new committers or PPMC members have been added since starting
incubation.
### Have your mentors been helpful and responsive?
Yes, gave guidance on email list usage and provided valuable
input during the community sync up.
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of
### Signed-off-by:
- [X] (yunikorn) Junping Du
Comments:
- [X] (yunikorn) Felix Cheung
Comments:
- [X] (yunikorn) Jason Lowe
Comments:
- [ ] (yunikorn) Holden Karau
Comments:
Comments:
### IPMC/Shepherd notes:
Apache YuniKorn (incubating) is a standalone resource scheduler responsible
for scheduling batch jobs and long-running services on large scale
distributed systems running in on-premises environments as well as
different public clouds.
Yunikorn has been incubating since: 2020-01-21
### Three most important unfinished issues to address before graduating:
- Gain more contributors and active committers.
- Launch the first Apache release.
- Improve documentation and provide a roadmap.
### Are there any issues that the IPMC or ASF Board need to be aware of?
- No critical issues at this point in time
### How has the community developed since the last report?
This is the first report for YuniKorn. Migration and setup is not fully
finialised.
### How has the project developed since the last report?
- source code repository moved to apache
- JIRA setup and configured
- community design for a new feature started
### 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:
N.A.
### When were the last committers or PPMC members elected?
No new committers or PPMC members have been added since starting
incubation.
### Have your mentors been helpful and responsive?
Yes, helped setup project page (Holden) and questions (Junping)
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of
### Signed-off-by:
- [X] (yunikorn) Junping Du
Comments:
- [x] (yunikorn) Felix Cheung
Comments:
- [X] (yunikorn) Jason Lowe
Comments:
- [ ] (yunikorn) Holden Karau
Comments:
Comments: Some projects choose to prepare a new release soon after becoming
Apache incubator project. See if YuniKorn would like to follow.
### IPMC/Shepherd notes: