I was thinking that we would/should/might follow the permissions philosophy that we have for cwiki, but allowing anyone to be a Triager would make administration of it a million times simpler. I would not have any objection to that...
CTO paul.an...@shapeblue.com www.shapeblue.com -----Original Message----- From: Niclas Hedhman <nic...@hedhman.org> Sent: 21 August 2020 07:32 To: Apache Members <memb...@apache.org> 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 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 it for "triage" then I think it will be respected. Classic reference is Subversion project, which gives a social grant to a part of the codebase, although there is no technical means to prevent a committer to mess it up. But, if they do, it is easily restored and actions can be taken depending on the nature of the reason. // Niclas On Thu, Aug 20, 2020 at 5:20 PM Paul Angus <pau...@apache.org> wrote: > 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 aren't a comitter and 'sucks to > be you'. > > Githib has introduced a 'Triage' role which bridges the gap. The > Triage role, allows issue and pull request admin, but still blocks > writing to the actual code. [1] > > I guess we'd need a mechanism to control/add contributors to the > Triage team per project, kinda like Karma for Confluence. > > I think that would be a great stepping stone for contributors to get > more involved in projects, so I'd like to gather support from other > projects and the ASF 'elders' for the principle. > > Many thanks > > Paul Angus > > [1] > https://docs.github.com/en/github/setting-up-and-managing-organization > s-and-teams/repository-permission-levels-for-an-organization > >
