Re: Triage role on Github

t prefers technical barriers to > >> social barriers. > >> > >> I am strongly of the view that social barriers are better for > >> communities than technical barriers. A lot of my early contributions to > >> Tomcat were around triaging open issues. I could

Re: Triage role on Github

iers are better for >> communities than technical barriers. A lot of my early contributions to >> Tomcat were around triaging open issues. I could only do that because >> access to BZ issues was managed via social controls rather than >> technical ones. >> >> Experience

Re: Triage role on Github

gt; > > > -Original Message- > From: Niclas Hedhman > Sent: 21 August 2020 07:32 > To: Apache Members > Cc: dev@community.apache.org > Subject: Re: Triage role on Github > > This "elder" thinks this is all good, but you *could* rely more on social,

Re: Triage role on Github

I started a similar thread in general@incubator , suggesting that we could use the newish ".asf.yaml" as a place to manage the list of "triagers".

RE: Triage role on Github

-Original Message- From: Niclas Hedhman Sent: 21 August 2020 07:32 To: Apache Members Cc: dev@community.apache.org Subject: Re: Triage role on Github This "elder" thinks this is all good, but you *could* rely more on social, rather than technical, solutions to achieve what you wa

Re: Triage role on Github

On Fri, Aug 21, 2020 at 8:32 AM Niclas Hedhman wrote: > ...If the concept is introduced in a given project, where people are given > commit > rights, with the explicit expectations only to use it for "triage" then I > think it will > be respected... Great point, many projects do this with

Re: Triage role on Github

This "elder" thinks this is all good, but you *could* rely more on social, rather than technical, solutions to achieve what you want without needing Infra assistance. If the concept is introduced in a given project, where people are given commit rights, with the explicit expectations only to use

Re: Triage role on Github

> On Aug 20, 2020, at 12:48 PM, Jacques Le Roux > wrote: > > Le 20/08/2020 à 15:08, Bertrand Delacretaz a écrit : >> On Thu, Aug 20, 2020 at 3:01 PM Harbs wrote: >>> I also don’t see any harm in making triage rights open to all >> I suspect creative minds might find a way to spam us

Re: Triage role on Github

Le 20/08/2020 à 15:08, Bertrand Delacretaz a écrit : On Thu, Aug 20, 2020 at 3:01 PM Harbs wrote: I also don’t see any harm in making triage rights open to all I suspect creative minds might find a way to spam us with this if it's "open to all" ? From my experience it always ends like

Re: Triage role on Github

> > social barriers. > > > > I am strongly of the view that social barriers are better for > > communities than technical barriers. A lot of my early contributions to > > Tomcat were around triaging open issues. I could only do that because > > access to BZ iss

Re: Triage role on Github

t were around triaging open issues. I could only do that because > access to BZ issues was managed via social controls rather than > technical ones. > > Experience with BZ suggests that opening up the Github triage role to > all will attract a few idiots from time to time but they can eas

Re: Triage role on Github

On Thu, Aug 20, 2020 at 3:01 PM Harbs wrote: > > I also don’t see any harm in making triage rights open to all I suspect creative minds might find a way to spam us with this if it's "open to all" ? For our wikis I think we generally give write access to anyone who *asks on our mailing

Re: Triage role on Github

peblue.com > www.shapeblue.com > > > > > -Original Message- > From: Mark Thomas > Sent: 20 August 2020 12:07 > To: dev@community.apache.org > Subject: Re: Triage role on Github > > If you mean "grant the triage role to anyone with a GitHub account" t

RE: Triage role on Github

-Original Message- From: Mark Thomas Sent: 20 August 2020 12:07 To: dev@community.apache.org Subject: Re: Triage role on Github If you mean "grant the triage role to anyone with a GitHub account" then +1. If you mean create a new level between contributor (i.e. anyone) and committe

Re: Triage role on Github

aging open issues. I could only do that because access to BZ issues was managed via social controls rather than technical ones. Experience with BZ suggests that opening up the Github triage role to all will attract a few idiots from time to time but they can easily be banned and the benefits of attr

Re: Triage role on Github

FYI similar discusion was raised on incubator list: https://lists.apache.org/thread.html/r497c5bf9a68e631bc93274e65beb3e28b769ce21e55961407adc5d10%40%3Cgeneral.incubator.apache.org%3E Cheers, Tomek On Thu, Aug 20, 2020 at 11:20 AM Paul Angus wrote: > Hi Members, > > One of our (CloudStack)

Triage role on Github

Hi Members, One of our (CloudStack) comitters has come with a great idea to increase project contributions... Traditionally Github has been very binary, you're either a commiter and you can write to a Repo and perform Issue and Pull Request admin (like add labels, change status, etc), or you