You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by David Jumani <Da...@shapeblue.com> on 2020/10/20 08:44:07 UTC
Re: Triage Permission
Hi All,
A big thanks to everyone who supported this idea. It's working out quite well allowing community members contribute further.
I'd like to suggest that others who would like the triage permission to boldly request it. It requires community / PMC approval followed by an infra ticket raised on the apache Jira, similar to this https://issues.apache.org/jira/browse/INFRA-20855
Request and approval can be gotten by shooting out a mail mentioning your GitHub handle in the mailing list, preferably as part of this mail chain to make it easier to pass on a consolidated to the infrastructure team to reduce complications and to speed up the process.
Thanks and happy Triaging!
David
________________________________
From: Paul Angus <pa...@shapeblue.com>
Sent: Monday, September 21, 2020 3:11 PM
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Subject: RE: Triage Permission
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.angus@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
David.Jumani@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Daan Hoogland <da...@gmail.com>
Sent: 21 September 2020 10:18
To: dev <de...@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 <Da...@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.Jumani@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
--
Daan
Re: Triage Permission
Posted by Darrin Hüsselmann <Da...@shapeblue.com>.
Thanks Daan.
Regards
Darrin
________________________________
From: Daan Hoogland <da...@gmail.com>
Sent: Monday, July 19, 2021 12:12 PM
To: dev <de...@cloudstack.apache.org>
Subject: Re: Triage Permission
yes you may @Spaceman1984 (binding?) please create an infra ticket for it.
On Mon, Jul 19, 2021 at 11:59 AM Darrin Hüsselmann <
Darrin.Husselmann@shapeblue.com> wrote:
> Hi Guys,
>
> May I please have the triage permission on the cloudstack-documentation
> repo<https://github.com/apache/cloudstack-documentation> for Spaceman1984?
>
> Cheers,
> Darrin
RE: Triage Permission
Posted by Paul Angus <pa...@angus.uk.com.INVALID>.
+1
Don't forget to include a link in Pony Mail [1] of the 'agreement' to the request
[1] https://lists.apache.org/list.html?dev@cloudstack.apache.org
Kind regards
Paul Angus
-----Original Message-----
From: Daan Hoogland <da...@gmail.com>
Sent: Monday, July 19, 2021 11:12 AM
To: dev <de...@cloudstack.apache.org>
Subject: Re: Triage Permission
yes you may @Spaceman1984 (binding?) please create an infra ticket for it.
On Mon, Jul 19, 2021 at 11:59 AM Darrin Hüsselmann < Darrin.Husselmann@shapeblue.com> wrote:
> Hi Guys,
>
> May I please have the triage permission on the
> cloudstack-documentation repo<https://github.com/apache/cloudstack-documentation> for Spaceman1984?
>
> Cheers,
> Darrin
Re: Triage Permission
Posted by Daan Hoogland <da...@gmail.com>.
yes you may @Spaceman1984 (binding?) please create an infra ticket for it.
On Mon, Jul 19, 2021 at 11:59 AM Darrin Hüsselmann <
Darrin.Husselmann@shapeblue.com> wrote:
> Hi Guys,
>
> May I please have the triage permission on the cloudstack-documentation
> repo<https://github.com/apache/cloudstack-documentation> for Spaceman1984?
>
> Cheers,
> Darrin
Re: Triage Permission
Posted by Darrin Hüsselmann <Da...@shapeblue.com>.
Hi Guys,
May I please have the triage permission on the cloudstack-documentation repo<https://github.com/apache/cloudstack-documentation> for Spaceman1984?
Cheers,
Darrin
________________________________
From: David Jumani <Da...@shapeblue.com>
Sent: Tuesday, October 20, 2020 10:44 AM
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Subject: Re: Triage Permission
Hi All,
A big thanks to everyone who supported this idea. It's working out quite well allowing community members contribute further.
I'd like to suggest that others who would like the triage permission to boldly request it. It requires community / PMC approval followed by an infra ticket raised on the apache Jira, similar to this https://issues.apache.org/jira/browse/INFRA-20855
Request and approval can be gotten by shooting out a mail mentioning your GitHub handle in the mailing list, preferably as part of this mail chain to make it easier to pass on a consolidated to the infrastructure team to reduce complications and to speed up the process.
Thanks and happy Triaging!
David
________________________________
From: Paul Angus <pa...@shapeblue.com>
Sent: Monday, September 21, 2020 3:11 PM
To: dev@cloudstack.apache.org <de...@cloudstack.apache.org>
Subject: RE: Triage Permission
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.angus@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
David.Jumani@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
-----Original Message-----
From: Daan Hoogland <da...@gmail.com>
Sent: 21 September 2020 10:18
To: dev <de...@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 <Da...@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.Jumani@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
> @shapeblue
>
>
>
>
--
Daan