Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Weiwei Yang]

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 
>>> 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 <
> wilfr...@apache.org> wrote:
>>> 
>>> The private@ is a moderated list. This has two issues: a
>> moderator
>>> needs to approve any message not sent by a PMC member. This will
>>> slow
>>> down the process of interaction with the reporter. It would also
>> not
>>> reach the YuniKorn committers group as not all committers are part
>>> of
>>> the PMC. Security issues should be handled and worked on by all
>>> committers not just by the PMC members.
>>> 
>>> The security notification update made to the website I think does
>>> not
>>> line up with the security guidelines referenced in the link
>> provided
>>> in the dropdown menu of the YuniKorn site [1]. In that link there
>>> is a
>>> well defined way to report security issues. If we need to enhance
>>> and
>>> extend what we do we either establish a security@ mailing list
>> and
>>> provide a static page with security related information on our
>> site
>>> or
>>> we leave it as is. My preference would be to establish a security@
>>> list and make all committers a member of that list.
>>> 
>>> I think we need to roll back the website changes part of
>>> YUNIKORN-1006
>>> [2] in PR [3] for the website.
>>> 
>>> Wilfred
>>> 
>>> [1] https://www.apache.org/security/
>>> [2] https://issues.apache.org/jira/browse/YUNIKORN-1006
>>> [3] 

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Sunil Govindan]

@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 
> > 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 <
> > > > wilfr...@apache.org> wrote:
> > > > >>
> > > > >> The private@ is a moderated list. This has two issues: a
> moderator
> > > > >> needs to approve any message not sent by a PMC member. This will
> > slow
> > > > >> down the process of interaction with the reporter. It would also
> not
> > > > >> reach the YuniKorn committers group as not all committers are part
> > of
> > > > >> the PMC. Security issues should be handled and worked on by all
> > > > >> committers not just by the PMC members.
> > > > >>
> > > > >> The security notification update made to the website I think does
> > not
> > > > >> line up with the security guidelines referenced in the link
> provided
> > > > >> in the dropdown menu of the YuniKorn site [1]. In that link there
> > is a
> > > > >> well defined way to report security issues. If we need to enhance
> > and
> > > > >> extend what we do we either establish a security@ mailing list
> and
> > > > >> provide a static page with security related information on our
> site
> > or
> > > > >> we leave it as is. My preference would be to establish a security@
> > > > >> list and make all committers a member of that list.
> > > > >>
> > > > >> I think we need to roll back the website changes part of
> > YUNIKORN-1006
> > > > >> [2] in PR [3] for the website.
> > > > >>
> > > > >> Wilfred
> > > > >>
> > > > >> [1] https://www.apache.org/security/
> > > > >> [2] https://issues.apache.org/jira/browse/YUNIKORN-1006
> > > > >> [3] https://github.com/apache/incubator-yunikorn-site/pull/105
> > > > >>
> > > > >> On Tue, 11 Jan 2022 

[jira] [Resolved] (YUNIKORN-1036) Fix why yunikorn doc format on the home page

[Chaoran Yu (Jira)]

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

Chaoran Yu resolved YUNIKORN-1036.
--
Resolution: Fixed

> Fix why yunikorn doc format on the home page
> 
>
> Key: YUNIKORN-1036
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1036
> Project: Apache YuniKorn
>  Issue Type: Sub-task
>Reporter: Weiwei Yang
>Assignee: Weiwei Yang
>Priority: Major
>  Labels: pull-request-available
>
> Currently, this is an image file, not flexible to provide different language 
> versions.



--
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

[Weiwei Yang]

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 
> 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 <
> > > wilfr...@apache.org> wrote:
> > > >>
> > > >> The private@ is a moderated list. This has two issues: a moderator
> > > >> needs to approve any message not sent by a PMC member. This will
> slow
> > > >> down the process of interaction with the reporter. It would also not
> > > >> reach the YuniKorn committers group as not all committers are part
> of
> > > >> the PMC. Security issues should be handled and worked on by all
> > > >> committers not just by the PMC members.
> > > >>
> > > >> The security notification update made to the website I think does
> not
> > > >> line up with the security guidelines referenced in the link provided
> > > >> in the dropdown menu of the YuniKorn site [1]. In that link there
> is a
> > > >> well defined way to report security issues. If we need to enhance
> and
> > > >> extend what we do we either establish a security@ mailing list and
> > > >> provide a static page with security related information on our site
> or
> > > >> we leave it as is. My preference would be to establish a security@
> > > >> list and make all committers a member of that list.
> > > >>
> > > >> I think we need to roll back the website changes part of
> YUNIKORN-1006
> > > >> [2] in PR [3] for the website.
> > > >>
> > > >> Wilfred
> > > >>
> > > >> [1] https://www.apache.org/security/
> > > >> [2] https://issues.apache.org/jira/browse/YUNIKORN-1006
> > > >> [3] https://github.com/apache/incubator-yunikorn-site/pull/105
> > > >>
> > > >> On Tue, 11 Jan 2022 at 04:45, Holden Karau 
> > > wrote:
> > > >> >
> > > >> > For "The project provides a well-documented, secure and private
> > > channel to report security issues, along with a documented way of
> > > responding to them.' the standard that I've seen used is to tell people
> > to
> > > e-mail private@ when they think they might have a security related
> > issue.
> > > I think that