Speaking with my Apache Member's hat on, the Apache ethos is to try to 'police' 
things through social controls rather than technically.

This exact topic has been discussed at Members level, and this (above) is the 
current consensus.  [sorry I'm not at liberty to share Member's email chains].  
However, this hasn't been ratified as an 'official' position, so infra are 
understandably playing it safe and only giving permissions to named people who 
have asked and been granted permission by the relevant project.

You can see this being actioned by infra here for another project:
https://issues.apache.org/jira/browse/INFRA-20853?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22triage%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

[CloudStack hat back on]

I am massive +1 on removing a barrier to people's participation.  And whatever 
controls are eventually deemed appropriate, I'm petty Zen about.


Paul

paul.an...@shapeblue.comĀ 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-----Original Message-----
From: Daan Hoogland <daan.hoogl...@gmail.com> 
Sent: 21 September 2020 10:18
To: dev <dev@cloudstack.apache.org>
Subject: Re: Triage Permission

In general, I'm fine with giving karma to any user on request for those 
abilities. I don't think a trial for a limited set of users makes sense.
And I don't think the PMC or committers will be able to control and revert on 
abuse. we'll need infra for both awarding and retracting.

On Mon, Sep 21, 2020 at 11:05 AM David Jumani <david.jum...@shapeblue.com>
wrote:

> Hi,
>
> While working with the CloudStack repository, logging issues and 
> contributing, I've noticed a long turnaround time for issues and pull 
> requests. I guess that it might have to do with the fact that only 
> committers can modify and manage them.
> To alleviate this, I'd like to propose the granting the Triage 
> permission< 
> https://docs.github.com/en/github/setting-up-and-managing-organization
> s-and-teams/repository-permission-levels-for-an-organization>
> on GitHub to some of the active members of our community.
>
>
> They can manage issues / pull requests, and add bots to automate 
> mundane tasks, without having write access to the repository.
> This would be a great stepping stone for growing the community, 
> reducing the workload on Committers and would help in keeping 
> community members and developers engaged in the project!
>
> As a trial, I'd propose the following users be granted it and based on 
> the result / feedback we can continue to add more members @shwstppr 
> @davidjumani @Pearl1594 @ACSGitBot @Spaceman1984 @sureshanaparti 
> @vladimirpetrov
>
> Thanks,
> David
>
>
> david.jum...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK 
> @shapeblue
>
>
>
>

--
Daan

Reply via email to