+1

On Fri, Jan 28, 2022 at 12:32 AM Subru Krishnan <su...@apache.org> wrote:

> +1.
>
> On Wed, Jan 26, 2022 at 11:10 PM WenChih Lo <wenc...@apache.org> wrote:
>
> > +1
> >
> > DB Tsai <dbt...@apache.org> 於 2022年1月27日 週四 下午2:36寫道:
> >
> >> +1
> >> DB Tsai  |  https://www.dbtsai.com/  |  PGP 42E5B25A8F7A82C1
> >>
> >>
> >> On Wed, Jan 26, 2022 at 10:29 PM Akhil PB <akhi...@apache.org> wrote:
> >>
> >> > +1
> >> >
> >> > On Thu, Jan 27, 2022 at 7:29 AM Sunil Govindan <sun...@apache.org>
> >> wrote:
> >> >
> >> >> +1
> >> >>
> >> >> Sunil
> >> >>
> >> >> On Tue, Jan 25, 2022 at 9:09 PM Weiwei Yang <w...@apache.org> wrote:
> >> >>
> >> >>> Hi YuniKorn community and mentors
> >> >>>
> >> >>> Based on the discussion thread [1], after 2 years time of
> incubating,
> >> it
> >> >>> is considered that now is a good time to graduate YuniKorn from the
> >> ASF
> >> >>> incubator and become a top-level Apache project. We have reviewed
> the
> >> ASF
> >> >>> project maturity model [2] and provided some assessment of the
> >> project's
> >> >>> maturity based on the guidelines. Details are included as the
> >> following. I
> >> >>> have enough reasons to believe the project has done sustainable
> >> development
> >> >>> successfully in the Apache way. Please read this and add your vote
> by
> >> >>> replying to this email, your feedback will be much appreciated!!!
> >> Note,
> >> >>> this vote is not just for committers or PPMC members, we welcome
> >> anyone in
> >> >>> the community to vote, thanks!
> >> >>>
> >> >>> *Code, License, and Copyright*
> >> >>>
> >> >>> All code is maintained on github, under Apache 2.0 license. We have
> >> >>> reviewed all the dependencies and ensured they do not bring any
> >> license
> >> >>> issues. All the status files, license headers, and copyright are up
> >> to date.
> >> >>>
> >> >>> *Release*
> >> >>>
> >> >>> The community has released 5 releases in the past 2 years, i.e v0.8,
> >> >>> v0.9, v0.10, v0,11, and v0.12. These releases were done by 5
> different
> >> >>> release managers [3] and indicate the community can create releases
> >> >>> independently. We have also a well-documented release process,
> >> automated
> >> >>> tools to help new release managers with the process.
> >> >>>
> >> >>> *Quality*
> >> >>>
> >> >>> The community has developed a comprehensive CI/CD pipeline as a
> guard
> >> of
> >> >>> the code quality. The pipeline runs per-commit license check,
> >> code-format
> >> >>> check, code-coverage check, UT, and end-to-end tests. All these are
> >> built
> >> >>> as automated github actions, new contributors can easily trigger and
> >> view
> >> >>> results when submitting patches.
> >> >>>
> >> >>> *Community*
> >> >>>
> >> >>> The community has developed an easy-to-read homepage for the project
> >> >>> [4], the website hosts all the materials related to the project
> >> including
> >> >>> versioned documentation, user docs, developer docs, design docs,
> >> >>> performance docs. It provides the top-level navigation to the
> software
> >> >>> download page, where links to all our previous releases. It also has
> >> the
> >> >>> pages for the new contributors on-boarding with the project, such as
> >> how to
> >> >>> join community meetings, events links, etc.
> >> >>>
> >> >>> The community shows appreciation to all contributors and welcomes
> all
> >> >>> kinds of contributions (not just for code). We have built an open,
> >> diverse
> >> >>> community and gathered many people to work together. With that, we
> >> have 41
> >> >>> unique code contributors and some non-code contributors as well.
> Many
> >> of
> >> >>> them have becoming to be committers and PPMC members while working
> >> with the
> >> >>> community. There were 2 new mentors, 8 new committers, 4 new PPMC
> from
> >> >>> 6 different organizations [5] added in the incubating phase. And in
> >> total,
> >> >>> the project has 6 mentors, 23 PPMC, and 29 committers from at least
> 14
> >> >>> different organizations. All the info are generally available on the
> >> >>> project website, including some guidelines to help people become
> >> >>> committer/PPMC member [6]. Community collaboration was done in a
> >> >>> wide-public, open manner, we leverage regular bi-weekly/weekly
> >> >>> community meetings for 2 different timezones [7] and dev/user slack
> >> >>> channels, mailing lists for offline discussions.
> >> >>>
> >> >>> *Independence*
> >> >>>
> >> >>> The project was initially donated by Cloudera, but with a diverse
> open
> >> >>> source community, it has been operated as an independent project
> >> since it
> >> >>> entered into ASF incubator. The committers and PPMC members are a
> >> group of
> >> >>> passionate people from at least 14 different organizations, such as
> >> >>> Alibaba, Apple, Cloudera, Databricks, LinkedIn, Microsoft,
> Snowflake,
> >> >>> etc. The project's success is not depending on any single entity.
> >> >>>
> >> >>> [1]
> https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> >> >>> [2]
> >> >>>
> >>
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> >> >>>
> >> >>> [3] https://yunikorn.apache.org/community/download
> >> >>> [4] https://yunikorn.apache.org/
> >> >>> [5] https://incubator.apache.org/projects/yunikorn.html
> >> >>> [6] https://yunikorn.apache.org/community/people
> >> >>>
> >> >>> [6]
> >> >>>
> >>
> https://docs.google.com/document/d/165gzC7uhcKc5XDWiMYSRKBiPQBy2tDtXADUPuhGlUa0
> >> >>>
> >> >>>
> >> >>>
> >>
> >
>

Reply via email to