Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Chaoran Yu 
+1.

Thanks Weiwei for putting together all the evidence showing that the
project is in good shape for graduation.

On Tue, Jan 25, 2022 at 9:43 PM Chenya Zhang 
wrote:

> +1 to graduate YuniKorn from the ASF
> incubator and become a top-level Apache project!
>
> Best,
> Chenya
>
> On Tue, Jan 25, 2022 at 9:09 PM Weiwei Yang  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
>>
>

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Chenya Zhang 
+1 to graduate YuniKorn from the ASF
incubator and become a top-level Apache project!

Best,
Chenya

On Tue, Jan 25, 2022 at 9:09 PM Weiwei Yang  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
>

Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Weiwei Yang 
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

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Weiwei Yang 
All sub-tasks under https://issues.apache.org/jira/browse/YUNIKORN-1005 are
now solved, and the name search is completed as well.
I will start a new thread for the vote.

On Tue, Jan 25, 2022 at 10:53 AM Chenya Zhang 
wrote:

> thanks Sunil! btw. I followed
> https://infra.apache.org/committer-email.html to configure my gmail
> settings to send from the apache email address. I originally used my gmail
> to subscribe to the private list and didn't receive a confirmation/error
> email. Hope others won't encounter the same problem.
>
> Best,
> Chenya
>
> On Tue, Jan 25, 2022 at 10:03 AM Sunil Govindan  wrote:
>
>> Yes. I reached out to a couple of them and added them to the list.
>> We still have a gap. Will try again.
>>
>> Thanks
>>  Sunil
>>
>> On Mon, Jan 24, 2022 at 10:45 PM Chenya Zhang <
>> chenyazhangche...@gmail.com>
>> wrote:
>>
>> > Subscribed to the private list! 3 -> 2 ? :)
>> >
>> > On Mon, Jan 24, 2022 at 6:02 PM Wilfred Spiegelenburg <
>> wilfr...@apache.org
>> > >
>> > wrote:
>> >
>> > > When you check the status page [1] you will see that a wiki is no
>> > > longer required.
>> > > We can skip adding it.
>> > >
>> > > BTW: I added Chenya to the roster that increases the PPMC members not
>> > > subscribed to 3 again after it was down to 2.
>> > >
>> > > Wilfred
>> > >
>> > > [1] https://incubator.apache.org/projects/yunikorn.html
>> > >
>> > >
>> > > On Mon, 24 Jan 2022 at 13:12, Weiwei Yang 
>> wrote:
>> > > >
>> > > > Hi Sunil
>> > > >
>> > > > I don’t think we ever have a wiki, do we still need to add that? I
>> see
>> > > some projects leave that empty as well.
>> > > >
>> > > > Sent from my iPhone
>> > > >
>> > > > > On Jan 23, 2022, at 2:07 PM, Sunil Govindan 
>> > wrote:
>> > > > >
>> > > > > @Weiwei Yang 
>> > > > > Could you please add WIKI as well to this?
>> > > > >
>> > > > > Thanks
>> > > > > Sunil
>> > > > >
>> > > > >> On Sun, Jan 23, 2022 at 1:33 PM Weiwei Yang 
>> > wrote:
>> > > > >>
>> > > > >> Thank you Felix.
>> > > > >> I have added the initial podling status file:
>> > > > >>
>> > > > >>
>> > >
>> >
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/yunikorn.yml
>> > > > >> .
>> > > > >> Please let me know if that looks good or not.
>> > > > >>
>> > > > >>> On Sat, Jan 22, 2022 at 10:18 PM Sunil Govindan <
>> sun...@apache.org
>> > >
>> > > wrote:
>> > > > >>>
>> > > > >>> I will reach out to them.
>> > > > >>>
>> > > > >>> Thanks
>> > > > >>> Sunil
>> > > > >>>
>> > > > >>> On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung <
>> > > felixcheun...@hotmail.com>
>> > > > >>> wrote:
>> > > > >>>
>> > > >  Pls add the podling status file
>> > > > 
>> > > > >>>
>> > > > >>
>> > >
>> >
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> > > > 
>> > > >  3 ppmc members have not subscribed to private@
>> > > > 
>> > > >  These can be found on
>> > > >  https://whimsy.apache.org/roster/ppmc/yunikorn
>> > > > 
>> > > >  <
>> > > > >>>
>> > > > >>
>> > >
>> >
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> > > > >
>> > > >  
>> > > >  From: Weiwei Yang 
>> > > >  Sent: Thursday, January 20, 2022 10:05:55 PM
>> > > >  To: dev@yunikorn.apache.org 
>> > > >  Cc: priv...@yunikorn.apache.org 
>> > > >  Subject: Re: Apache YuniKorn (Incubating) - Community
>> Graduation
>> > > Vote
>> > > > 
>> > > >  hi all
>> > > > 
>> > > >  Most issues under the graduation preparation JIRA YUNIKORN-1005
>> > > >   are
>> fixed.
>> > > >  The remaining one is the who-are-we web page, I am currently
>> > > collecting
>> > > >  info for that, should be done by next week.
>> > > >  Shall we start to vote now? I can start a new thread for the
>> > > community
>> > > >  voting if nobody has objections.
>> > > > 
>> > > >  On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
>> > > >  wilfr...@apache.org>
>> > > >  wrote:
>> > > > 
>> > > > > None of the security lists mentioned in the security page [1]
>> are
>> > > > > moderated. They are private lists, i.e. not openly available
>> for
>> > > > > browsing in an archive, but not moderated. Using the private@
>> > for
>> > > > > YuniKorn does not seem to line up with what other projects do
>> > > either.
>> > > > > None of the recently graduated projects mention anything like
>> > using
>> > > > > the private@ mailing list on their sites. They all have just
>> > used
>> > > > >> the
>> > > > > general security link mentioned on their site unless they
>> have a
>> > > > > specific security@ list. YuniKorn would be the one standing
>> out
>> > > from
>> > > > > what seems to be the norm.
>> > > > > Examples from the last 2 years of graduated projects using a
>> > simple
>> > > > > link or a text pointing to [1]: Pinot,

APAC community sync up schedule changes

2022-01-25 Thread Weiwei Yang 
FYI: the APAC community call schedule has changed to bi-weekly, please
check the latest calendar. We will use this schedule for now and may change
it back to weekly if more frequent meetings are necessary.

[jira] [Created] (YUNIKORN-1044) Publish design doc for scheduler plugin to website.

2022-01-25 Thread Craig Condit (Jira) 
Craig Condit created YUNIKORN-1044:
--

 Summary: Publish design doc for scheduler plugin to website.
 Key: YUNIKORN-1044
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1044
 Project: Apache YuniKorn
  Issue Type: Task
  Components: website
Reporter: Craig Condit
Assignee: Craig Condit


Now that YUNIKORN-971 is merged, we should update the website with the design 
document.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Chenya Zhang 
thanks Sunil! btw. I followed https://infra.apache.org/committer-email.html
to configure my gmail settings to send from the apache email address. I
originally used my gmail to subscribe to the private list and didn't
receive a confirmation/error email. Hope others won't encounter the same
problem.

Best,
Chenya

On Tue, Jan 25, 2022 at 10:03 AM Sunil Govindan  wrote:

> Yes. I reached out to a couple of them and added them to the list.
> We still have a gap. Will try again.
>
> Thanks
>  Sunil
>
> On Mon, Jan 24, 2022 at 10:45 PM Chenya Zhang  >
> wrote:
>
> > Subscribed to the private list! 3 -> 2 ? :)
> >
> > On Mon, Jan 24, 2022 at 6:02 PM Wilfred Spiegelenburg <
> wilfr...@apache.org
> > >
> > wrote:
> >
> > > When you check the status page [1] you will see that a wiki is no
> > > longer required.
> > > We can skip adding it.
> > >
> > > BTW: I added Chenya to the roster that increases the PPMC members not
> > > subscribed to 3 again after it was down to 2.
> > >
> > > Wilfred
> > >
> > > [1] https://incubator.apache.org/projects/yunikorn.html
> > >
> > >
> > > On Mon, 24 Jan 2022 at 13:12, Weiwei Yang  wrote:
> > > >
> > > > Hi Sunil
> > > >
> > > > I don’t think we ever have a wiki, do we still need to add that? I
> see
> > > some projects leave that empty as well.
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Jan 23, 2022, at 2:07 PM, Sunil Govindan 
> > wrote:
> > > > >
> > > > > @Weiwei Yang 
> > > > > Could you please add WIKI as well to this?
> > > > >
> > > > > Thanks
> > > > > Sunil
> > > > >
> > > > >> On Sun, Jan 23, 2022 at 1:33 PM Weiwei Yang 
> > wrote:
> > > > >>
> > > > >> Thank you Felix.
> > > > >> I have added the initial podling status file:
> > > > >>
> > > > >>
> > >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/yunikorn.yml
> > > > >> .
> > > > >> Please let me know if that looks good or not.
> > > > >>
> > > > >>> On Sat, Jan 22, 2022 at 10:18 PM Sunil Govindan <
> sun...@apache.org
> > >
> > > wrote:
> > > > >>>
> > > > >>> I will reach out to them.
> > > > >>>
> > > > >>> Thanks
> > > > >>> Sunil
> > > > >>>
> > > > >>> On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung <
> > > felixcheun...@hotmail.com>
> > > > >>> wrote:
> > > > >>>
> > > >  Pls add the podling status file
> > > > 
> > > > >>>
> > > > >>
> > >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > > 
> > > >  3 ppmc members have not subscribed to private@
> > > > 
> > > >  These can be found on
> > > >  https://whimsy.apache.org/roster/ppmc/yunikorn
> > > > 
> > > >  <
> > > > >>>
> > > > >>
> > >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > > >
> > > >  
> > > >  From: Weiwei Yang 
> > > >  Sent: Thursday, January 20, 2022 10:05:55 PM
> > > >  To: dev@yunikorn.apache.org 
> > > >  Cc: priv...@yunikorn.apache.org 
> > > >  Subject: Re: Apache YuniKorn (Incubating) - Community Graduation
> > > Vote
> > > > 
> > > >  hi all
> > > > 
> > > >  Most issues under the graduation preparation JIRA YUNIKORN-1005
> > > >   are
> fixed.
> > > >  The remaining one is the who-are-we web page, I am currently
> > > collecting
> > > >  info for that, should be done by next week.
> > > >  Shall we start to vote now? I can start a new thread for the
> > > community
> > > >  voting if nobody has objections.
> > > > 
> > > >  On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
> > > >  wilfr...@apache.org>
> > > >  wrote:
> > > > 
> > > > > None of the security lists mentioned in the security page [1]
> are
> > > > > moderated. They are private lists, i.e. not openly available
> for
> > > > > browsing in an archive, but not moderated. Using the private@
> > for
> > > > > YuniKorn does not seem to line up with what other projects do
> > > either.
> > > > > None of the recently graduated projects mention anything like
> > using
> > > > > the private@ mailing list on their sites. They all have just
> > used
> > > > >> the
> > > > > general security link mentioned on their site unless they have
> a
> > > > > specific security@ list. YuniKorn would be the one standing
> out
> > > from
> > > > > what seems to be the norm.
> > > > > Examples from the last 2 years of graduated projects using a
> > simple
> > > > > link or a text pointing to [1]: Pinot, Dolphinscheduler, Ratis,
> > > > > Echarts, Gobblin, TVM, Superset and Datasketches. There are
> more
> > > but
> > > > >> I
> > > > > think this provides an overview of what is expected on
> > graduation.
> > > > >
> > > > > Wilfred
> > > > >
> > > > > [1] https://www.apache.org/security/
> > > > >
> > > > > On Tue, 11 Jan 2022 at 18:21, Weiwei Yang 
> > wrote:
> > > > >>
> > > > >> Hi

[jira] [Resolved] (YUNIKORN-1043) Minor fix on the people page

2022-01-25 Thread Weiwei Yang (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiwei Yang resolved YUNIKORN-1043.
---
Fix Version/s: 1.0.0
 Assignee: Weiwei Yang
   Resolution: Fixed

> Minor fix on the people page
> 
>
> Key: YUNIKORN-1043
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1043
> Project: Apache YuniKorn
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Major
> Fix For: 1.0.0
>
>
> A minor issue is found and needs to be fixed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

[jira] [Created] (YUNIKORN-1043) Minor fix on the people page

2022-01-25 Thread Weiwei Yang (Jira) 
Weiwei Yang created YUNIKORN-1043:
-

 Summary: Minor fix on the people page
 Key: YUNIKORN-1043
 URL: https://issues.apache.org/jira/browse/YUNIKORN-1043
 Project: Apache YuniKorn
  Issue Type: Sub-task
  Components: documentation
Reporter: Weiwei Yang


A minor issue is found and needs to be fixed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

2022-01-25 Thread Sunil Govindan 
Yes. I reached out to a couple of them and added them to the list.
We still have a gap. Will try again.

Thanks
 Sunil

On Mon, Jan 24, 2022 at 10:45 PM Chenya Zhang 
wrote:

> Subscribed to the private list! 3 -> 2 ? :)
>
> On Mon, Jan 24, 2022 at 6:02 PM Wilfred Spiegelenburg  >
> wrote:
>
> > When you check the status page [1] you will see that a wiki is no
> > longer required.
> > We can skip adding it.
> >
> > BTW: I added Chenya to the roster that increases the PPMC members not
> > subscribed to 3 again after it was down to 2.
> >
> > Wilfred
> >
> > [1] https://incubator.apache.org/projects/yunikorn.html
> >
> >
> > On Mon, 24 Jan 2022 at 13:12, Weiwei Yang  wrote:
> > >
> > > Hi Sunil
> > >
> > > I don’t think we ever have a wiki, do we still need to add that? I see
> > some projects leave that empty as well.
> > >
> > > Sent from my iPhone
> > >
> > > > On Jan 23, 2022, at 2:07 PM, Sunil Govindan 
> wrote:
> > > >
> > > > @Weiwei Yang 
> > > > Could you please add WIKI as well to this?
> > > >
> > > > Thanks
> > > > Sunil
> > > >
> > > >> On Sun, Jan 23, 2022 at 1:33 PM Weiwei Yang 
> wrote:
> > > >>
> > > >> Thank you Felix.
> > > >> I have added the initial podling status file:
> > > >>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/yunikorn.yml
> > > >> .
> > > >> Please let me know if that looks good or not.
> > > >>
> > > >>> On Sat, Jan 22, 2022 at 10:18 PM Sunil Govindan  >
> > wrote:
> > > >>>
> > > >>> I will reach out to them.
> > > >>>
> > > >>> Thanks
> > > >>> Sunil
> > > >>>
> > > >>> On Sat, Jan 22, 2022 at 9:00 PM Felix Cheung <
> > felixcheun...@hotmail.com>
> > > >>> wrote:
> > > >>>
> > >  Pls add the podling status file
> > > 
> > > >>>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > 
> > >  3 ppmc members have not subscribed to private@
> > > 
> > >  These can be found on
> > >  https://whimsy.apache.org/roster/ppmc/yunikorn
> > > 
> > >  <
> > > >>>
> > > >>
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > > >
> > >  
> > >  From: Weiwei Yang 
> > >  Sent: Thursday, January 20, 2022 10:05:55 PM
> > >  To: dev@yunikorn.apache.org 
> > >  Cc: priv...@yunikorn.apache.org 
> > >  Subject: Re: Apache YuniKorn (Incubating) - Community Graduation
> > Vote
> > > 
> > >  hi all
> > > 
> > >  Most issues under the graduation preparation JIRA YUNIKORN-1005
> > >   are fixed.
> > >  The remaining one is the who-are-we web page, I am currently
> > collecting
> > >  info for that, should be done by next week.
> > >  Shall we start to vote now? I can start a new thread for the
> > community
> > >  voting if nobody has objections.
> > > 
> > >  On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg <
> > >  wilfr...@apache.org>
> > >  wrote:
> > > 
> > > > None of the security lists mentioned in the security page [1] are
> > > > moderated. They are private lists, i.e. not openly available for
> > > > browsing in an archive, but not moderated. Using the private@
> for
> > > > YuniKorn does not seem to line up with what other projects do
> > either.
> > > > None of the recently graduated projects mention anything like
> using
> > > > the private@ mailing list on their sites. They all have just
> used
> > > >> the
> > > > general security link mentioned on their site unless they have a
> > > > specific security@ list. YuniKorn would be the one standing out
> > from
> > > > what seems to be the norm.
> > > > Examples from the last 2 years of graduated projects using a
> simple
> > > > link or a text pointing to [1]: Pinot, Dolphinscheduler, Ratis,
> > > > Echarts, Gobblin, TVM, Superset and Datasketches. There are more
> > but
> > > >> I
> > > > think this provides an overview of what is expected on
> graduation.
> > > >
> > > > Wilfred
> > > >
> > > > [1] https://www.apache.org/security/
> > > >
> > > > On Tue, 11 Jan 2022 at 18:21, Weiwei Yang 
> wrote:
> > > >>
> > > >> Hi Wilfred
> > > >>
> > > >> Adding a security@ mailing list sounds like a good idea, but I
> do
> > > >>> not
> > > > think that is required in the current stage.
> > > >> We can do that post-graduate. For now, the Apache security doc
> > said
> > > >>
> > > >>> We strongly encourage you to report potential security
> > >  vulnerabilities
> > > > to one of our private security mailing lists first, before
> > disclosing
> > >  them
> > > > in a public forum.
> > > >>
> > > >> I do not see any issue if we use our private@ mailing list for
> > > >> this
> > > > purpose.
> > > >>
> > > >> On Mon, Jan 10, 2022 at 11:01 PM Wilfred Spiegelenburg <
> > > >

[jira] [Resolved] (YUNIKORN-1021) Add committer/PPMC user list on the website

2022-01-25 Thread Weiwei Yang (Jira) 


 [ 
https://issues.apache.org/jira/browse/YUNIKORN-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiwei Yang resolved YUNIKORN-1021.
---
Fix Version/s: 1.0.0
   Resolution: Fixed

> Add committer/PPMC user list on the website
> ---
>
> Key: YUNIKORN-1021
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1021
> Project: Apache YuniKorn
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.0.0
>
>
> It would be good if we can have all committers/PPMC members and their 
> organization on the website. We can add "Who we are" under the community tab.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org