Community-led development "The Apache Way"
This was extracted (@ 2022-08-17 16: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).
Report was filed, but display is awaiting the approval of the Board minutes.
## Description: The mission of Apache YuniKorn is the creation and maintenance of software related to 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 ## Issues: This are no issues requiring board attention ## Membership Data: Apache YuniKorn was founded 2022-03-15 (2 months ago) There are currently 29 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quater: - new PMC member: Manikanda R ## Project Activity: Apache YuniKorn has released v1.0 on 05/06/2022, this is the first major release after the project graduated as a TLP. Users are updating to the new version, there were some minor issues reported, but overall this is a stable, production-ready release for our community users. Other activities: - YuniKorn PMCs worked with Apache marketing team and got the press release annoucement out on 05/16/2022. - Folks from YuniKorn PMCs have been presented 2 sessions in the KubeConf held in Spain 05/16/2022-05/20/2022. - YuniKorn community is discussing the plan for 1.1.0 release. ## Community Health: Overall the community is healthy and evolving on the right path. The 1.0 release was a major release with lots of code changes, the community has spent tramenderous effort to optimize the code base, and make the project easier to contribute & maintain. We are seeing new contributors contributing to the project, we see 3 new code contributors in the past quater, and the PMC group is having a discussion to add a new committer.
## Description: The mission of Apache YuniKorn is the creation and maintenance of software related to 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 ## Issues: There is no issues requiring board attention. ## Membership Data: Apache YuniKorn was founded 2022-03-15 (2 months ago) There are currently 29 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: Development activity: - The community just published 1.0.0 release (05/04/2022). This is a huge milestone with a tone of improvements, and a new deployment model now is supported. - The community had a meeting to discuss the roadmap for 1.1 and 1.2. And the target release time frame for 1.1 is Aug, 2022. Also the community might want to release a 1.0.1 version for bug fixes if we see major production issues. ## Community Health: There were 15+ active committers and contributors who contributed to the 1.0.0 release. And we see more users are starting to trying yunikorn, and trying to get help from our slack channel or mailing list. Overall the community health is good. This month, 2 PPMC member will present a session on KubeConf, and next month 2 other PPMC member will present a session on Spark AI Summit. PPMC members are also preparing to submit talks for the comming ApacheConf.
## Description: Apache YuniKorn is a cloud-native, standalone resource scheduler for batch jobs and long-running services on large scale distributed systems, that solve the resource scheduling problems for Big Data and Machine Learning workloads. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache YuniKorn was founded 2022-03-15 (16 days ago) There are currently 29 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 4:3. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: The community is working on the post-graduate tasks, following the Apache document to do proper hand-over. Including moving resources, updating UI and the website, doc clearance, etc. At present, all the major tasks are done. The community is preparing for the 1.0.0 release, and the target release date is end of Apr 2022. And we will be busy with the release tasks in the next few weeks. The release manager is appointed. The community started the discussion about post-1.0 features and roadmap, we have a draft list of features people are interested in. The community will work with all the people in the dev channel to prioritize and further figure out the plan for these features. The community will give conference talks on the coming Spark Summit and KubeConf. ## Community Health: Community activities are pretty healthy, the PRs are raised up reguarly from different orgs, and people are actively helping to review and reduce the backlog. The major issues plannedfor 1.0.0 release are mostly done. There are 4 new contributors who recently started to contribute in the project, and they did reach out to the community in the proper way, via our community sync up meeting, and slack channels. They are interested in working on different area in the project. There is a volunteer currently working on translating the web-site into Chinese, in order to provide the Chinese version of the doc. Part of the doc is already online, we are working together to move this forward.
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 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. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache YuniKorn Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache YuniKorn Project be and hereby is responsible for the creation and maintenance of software related to 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; and be it further RESOLVED, that the office of "Vice President, Apache YuniKorn" 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 YuniKorn Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache YuniKorn 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 YuniKorn Project: * Akhil PB <akhilpb@apache.org> * Arun Suresh <asuresh@apache.org> * Carlo Curino <curino@apache.org> * Chaoran Yu <yuchaoran@apache.org> * Chenya Zhang <chenya@apache.org> * Craig Condit <ccondit@apache.org> * DB Tsai <dbtsai@apache.org> * Felix Cheung <felixcheung@apache.org> * Holden Karau <holden@apache.org> * Jason Darrell Lowe <jlowe@apache.org> * Jonathan Hung <jhung@apache.org> * Junping Du <junping_du@apache.org> * Kinga Marton <kmarton@apache.org> * Konstantinos Karanasos <kkaranasos@apache.org> * Luciano Resende <lresende@apache.org> * Subramaniam Krishnan <subru@apache.org> * Sunil G <sunilg@apache.org> * Tao Yang <taoyang@apache.org> * Vinod Kumar Vavilapalli <vinodkv@apache.org> * Wangda Tan <wangda@apache.org> * Wei-Chiu Chuang <weichiu@apache.org> * Weiwei Yang <wwei@apache.org> * Wilfred Spiegelenburg <wilfreds@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Weiwei Yang be appointed to the office of Vice President, Apache YuniKorn, 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 Apache YuniKorn Project be and hereby is tasked with the migration and rationalization of the Apache Incubator YuniKorn podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator YuniKorn podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7D, Establish the Apache YuniKorn Project, was approved by Unanimous Vote of the directors present.
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. Increase the number of contributors and committers.
2. Improve the ease of deployment and provide upgrade support.
3. Release process and planning improvements.
### 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?
Two new mentors added. A new PPMC member and committer added.
Two new committers were invited and have accepted but not announced yet.
Multiple new contributors added to the community.
Released v0.12.1, work on v1.0.0 is in progress.
### How has the project developed since the last report?
Working towards a v1.0 release. Major changes planned for the release to
limit tech debt in the future.
Some statistics for the report period (2021-10-01 till 2021-12-31):
JIRA: 121 created, 115 resolved
PRs: 105 opened, 102 resolved
18 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
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2021-12-26
### When were the last committers or PPMC members elected?
2021-12-21 & 2021-12-23 committers elected
2021-12-18 PPMC member elected
### Have your mentors been helpful and responsive?
Yes
### 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:
- [X] (yunikorn) Holden Karau
Comments:
- [X] (yunikorn) Wei-Chiu Chuang
Comments:
- [X] (yunikorn) Luciano Resende
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. Increase the number of contributors and committers.
2. Plan feature to release mapping.
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?
Two new committers added, multiple new contributors added to the
community.
Released v0.11.0, work on v1.0.0 is in progress.
### How has the project developed since the last report?
Working towards a v1.0 release. Scheduler interface changes are planned
to simplify the code.
Improved node sorting code. Performance tests showing a major improvement
and large advantage over the default Kubernetes scheduler. A performance
blog is in preparation.
Blog published (3rd party) on gang scheduling.
Some statistics for the report period (2021-07-01 till 2021-09-30):
JIRA: 141 created, 118 resolved
PRs: 125 opened, 122 resolved
17 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
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2021-08-27
### When were the last committers or PPMC members elected?
2021-08-26 & 2021-09-22 committers added
### Have your mentors been helpful and responsive?
Yes
### 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:
- [X] (lresende) Luciano Resende
Comments: One of the important aspects of
community building is reaching out to the
folks in the community, I would have expected
to see a mention about the planned meetup in the
report -> https://yunikorn.apache.org/community/events
### 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. Release regularly, split large changes over multiple releases.
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?
Added one new committer and several new contributors.
Elected a new PPMC member.
Finalising the next release v0.11, planning for release v1.0.
### How has the project developed since the last report?
Stabilising the previous release major features (gang scheduling).
Upgrading protobuf build and dependency for the scheduler interface.
Implemented a new REST interface. The interface changes are all in
preparation for a v1.0 release which is in planning.
Some statistics for the report period (2021-04-01 till 2021-06-30):
JIRA: 105 created, 112 resolved
PRs: 65 opened, 70 resolved
11 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:
2021-04-09
### When were the last committers or PPMC members elected?
2021-07-07 committer and PPMC member added
### Have your mentors been helpful and responsive?
yes
### 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. Release regularly, split large changes over multiple releases.
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?
Added one new committer, and several new contributors.
Delivered two large features in new release v0.10.
Release v0.10 has been approved by the community and is up for a vote in
the
IPMC.
### How has the project developed since the last report?
New release with a new release manager (3rd for 3 releases) voted on by
community. Voting thread just created for a IPMC vote.
Major new functionality gang scheduling delivered.
New community members tested pre-release code and were active in the
development phase.
Some statistics for the report period (2021-01-01 till 2021-03-31):
JIRA: 125 created, 99 resolved
PRs: 86 opened, 84 resolved
12 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?
2021-02-04 committer added
### Have your mentors been helpful and responsive?
yes
### 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 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: