You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@superset.apache.org by Maxime Beauchemin <ma...@gmail.com> on 2020/08/13 16:27:39 UTC
Giving our PMs and contributors triage rights on GitHub
Hi all,
It just came to my attention that GitHub added a new "triage" access level
at the repo level.
https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
In the past, we've identified that it was impossible for non-committers
(especially our PMs and contributors-that-are-not-yet-committers) to help
us triage issues, apply labels, assign reviews, close and reopen issues as
needed. It's really clear to me that we really need all the help we can get
in this area, and that not being able to involve more people into this
process hurts us, and is a clear operational downside of using the ASF
infra.
I'd like to build a case for this to become allowed by ASF infra. But
first, I'd love to see some +1s, and a list of GitHub handles for people in
our community who could make use of this feature.
More technically, I think the way to make that easy and painless would be
to add a new entry to the `.asf.yaml` file that would enable maintainers to
assign the "triage" role to whoever they see fit. For reference, here's
more context on that piece of automation I'd like to latch this onto here:
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
FYI, xposting this to general@incubator for their attention.
Max
Re: Giving our PMs and contributors triage rights on GitHub
Posted by William Barrett <wi...@preset.io>.
+1 - the PMs at Preset would be very helpful to the community if they had this level of access.
Will Barrett
Staff Software Engineer
Preset, Inc. | https://preset.io
On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <ma...@gmail.com>, wrote:
> Hi all,
>
> It just came to my attention that GitHub added a new "triage" access level
> at the repo level.
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
>
> In the past, we've identified that it was impossible for non-committers
> (especially our PMs and contributors-that-are-not-yet-committers) to help
> us triage issues, apply labels, assign reviews, close and reopen issues as
> needed. It's really clear to me that we really need all the help we can get
> in this area, and that not being able to involve more people into this
> process hurts us, and is a clear operational downside of using the ASF
> infra.
>
> I'd like to build a case for this to become allowed by ASF infra. But
> first, I'd love to see some +1s, and a list of GitHub handles for people in
> our community who could make use of this feature.
>
> More technically, I think the way to make that easy and painless would be
> to add a new entry to the `.asf.yaml` file that would enable maintainers to
> assign the "triage" role to whoever they see fit. For reference, here's
> more context on that piece of automation I'd like to latch this onto here:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> FYI, xposting this to general@incubator for their attention.
>
> Max
Re: Giving our PMs and contributors triage rights on GitHub
Posted by Bence Orlai <be...@orlai.com>.
+1 as a PM at Preset
We would like to work on a public community roadmap, for which we need to
be able to label and organize issues in the repo
- sent from my phone
On Sat, Aug 15, 2020, 12:04 PM Bogdan Kyryliuk <b....@gmail.com> wrote:
> I like the idea. It definitely be helpful to get community help on triaging
> the issues
>
> On Sat, Aug 15, 2020, 8:39 AM Junlin Chen <ju...@preset.io> wrote:
>
> > humbly asking +1. Currently, we PMs at Preset are tracking Github issues
> > Projects, Milestone and Link PR manually which is extremely inefficient.
> By
> > doing so, we are not able to provide status updates timely to
> > the community.
> >
> >
> >
> > On Thu, Aug 13, 2020 at 3:52 PM Evan Rusackas <ev...@preset.io> wrote:
> >
> > > An emphatic +1 from me! The issues could gain a huge boost from the
> added
> > > human curation, whether it's adding sensible labels, running Project
> > kanban
> > > boards, linking issues to PRs (and other relevant issues), and more. It
> > > could not only bring some order to the chaos, but help those in the
> > > community reporting issues feel like they’re being heard.
> > >
> > > Evan Rusackas
> > > ( he | him )
> > > Frontend Lead
> > > Preset | preset.io
> > > On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <
> > > maximebeauchemin@gmail.com>, wrote:
> > > > Hi all,
> > > >
> > > > It just came to my attention that GitHub added a new "triage" access
> > > level
> > > > at the repo level.
> > > >
> > https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
> > > >
> > > > In the past, we've identified that it was impossible for
> non-committers
> > > > (especially our PMs and contributors-that-are-not-yet-committers) to
> > help
> > > > us triage issues, apply labels, assign reviews, close and reopen
> issues
> > > as
> > > > needed. It's really clear to me that we really need all the help we
> can
> > > get
> > > > in this area, and that not being able to involve more people into
> this
> > > > process hurts us, and is a clear operational downside of using the
> ASF
> > > > infra.
> > > >
> > > > I'd like to build a case for this to become allowed by ASF infra. But
> > > > first, I'd love to see some +1s, and a list of GitHub handles for
> > people
> > > in
> > > > our community who could make use of this feature.
> > > >
> > > > More technically, I think the way to make that easy and painless
> would
> > be
> > > > to add a new entry to the `.asf.yaml` file that would enable
> > maintainers
> > > to
> > > > assign the "triage" role to whoever they see fit. For reference,
> here's
> > > > more context on that piece of automation I'd like to latch this onto
> > > here:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> > > >
> > > > FYI, xposting this to general@incubator for their attention.
> > > >
> > > > Max
> > >
> >
>
Re: Giving our PMs and contributors triage rights on GitHub
Posted by Bogdan Kyryliuk <b....@gmail.com>.
I like the idea. It definitely be helpful to get community help on triaging
the issues
On Sat, Aug 15, 2020, 8:39 AM Junlin Chen <ju...@preset.io> wrote:
> humbly asking +1. Currently, we PMs at Preset are tracking Github issues
> Projects, Milestone and Link PR manually which is extremely inefficient. By
> doing so, we are not able to provide status updates timely to
> the community.
>
>
>
> On Thu, Aug 13, 2020 at 3:52 PM Evan Rusackas <ev...@preset.io> wrote:
>
> > An emphatic +1 from me! The issues could gain a huge boost from the added
> > human curation, whether it's adding sensible labels, running Project
> kanban
> > boards, linking issues to PRs (and other relevant issues), and more. It
> > could not only bring some order to the chaos, but help those in the
> > community reporting issues feel like they’re being heard.
> >
> > Evan Rusackas
> > ( he | him )
> > Frontend Lead
> > Preset | preset.io
> > On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <
> > maximebeauchemin@gmail.com>, wrote:
> > > Hi all,
> > >
> > > It just came to my attention that GitHub added a new "triage" access
> > level
> > > at the repo level.
> > >
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
> > >
> > > In the past, we've identified that it was impossible for non-committers
> > > (especially our PMs and contributors-that-are-not-yet-committers) to
> help
> > > us triage issues, apply labels, assign reviews, close and reopen issues
> > as
> > > needed. It's really clear to me that we really need all the help we can
> > get
> > > in this area, and that not being able to involve more people into this
> > > process hurts us, and is a clear operational downside of using the ASF
> > > infra.
> > >
> > > I'd like to build a case for this to become allowed by ASF infra. But
> > > first, I'd love to see some +1s, and a list of GitHub handles for
> people
> > in
> > > our community who could make use of this feature.
> > >
> > > More technically, I think the way to make that easy and painless would
> be
> > > to add a new entry to the `.asf.yaml` file that would enable
> maintainers
> > to
> > > assign the "triage" role to whoever they see fit. For reference, here's
> > > more context on that piece of automation I'd like to latch this onto
> > here:
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> > >
> > > FYI, xposting this to general@incubator for their attention.
> > >
> > > Max
> >
>
Re: Giving our PMs and contributors triage rights on GitHub
Posted by Junlin Chen <ju...@preset.io>.
humbly asking +1. Currently, we PMs at Preset are tracking Github issues
Projects, Milestone and Link PR manually which is extremely inefficient. By
doing so, we are not able to provide status updates timely to
the community.
On Thu, Aug 13, 2020 at 3:52 PM Evan Rusackas <ev...@preset.io> wrote:
> An emphatic +1 from me! The issues could gain a huge boost from the added
> human curation, whether it's adding sensible labels, running Project kanban
> boards, linking issues to PRs (and other relevant issues), and more. It
> could not only bring some order to the chaos, but help those in the
> community reporting issues feel like they’re being heard.
>
> Evan Rusackas
> ( he | him )
> Frontend Lead
> Preset | preset.io
> On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <
> maximebeauchemin@gmail.com>, wrote:
> > Hi all,
> >
> > It just came to my attention that GitHub added a new "triage" access
> level
> > at the repo level.
> > https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
> >
> > In the past, we've identified that it was impossible for non-committers
> > (especially our PMs and contributors-that-are-not-yet-committers) to help
> > us triage issues, apply labels, assign reviews, close and reopen issues
> as
> > needed. It's really clear to me that we really need all the help we can
> get
> > in this area, and that not being able to involve more people into this
> > process hurts us, and is a clear operational downside of using the ASF
> > infra.
> >
> > I'd like to build a case for this to become allowed by ASF infra. But
> > first, I'd love to see some +1s, and a list of GitHub handles for people
> in
> > our community who could make use of this feature.
> >
> > More technically, I think the way to make that easy and painless would be
> > to add a new entry to the `.asf.yaml` file that would enable maintainers
> to
> > assign the "triage" role to whoever they see fit. For reference, here's
> > more context on that piece of automation I'd like to latch this onto
> here:
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> >
> > FYI, xposting this to general@incubator for their attention.
> >
> > Max
>
Re: Giving our PMs and contributors triage rights on GitHub
Posted by Evan Rusackas <ev...@preset.io>.
An emphatic +1 from me! The issues could gain a huge boost from the added human curation, whether it's adding sensible labels, running Project kanban boards, linking issues to PRs (and other relevant issues), and more. It could not only bring some order to the chaos, but help those in the community reporting issues feel like they’re being heard.
Evan Rusackas
( he | him )
Frontend Lead
Preset | preset.io
On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin <ma...@gmail.com>, wrote:
> Hi all,
>
> It just came to my attention that GitHub added a new "triage" access level
> at the repo level.
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
>
> In the past, we've identified that it was impossible for non-committers
> (especially our PMs and contributors-that-are-not-yet-committers) to help
> us triage issues, apply labels, assign reviews, close and reopen issues as
> needed. It's really clear to me that we really need all the help we can get
> in this area, and that not being able to involve more people into this
> process hurts us, and is a clear operational downside of using the ASF
> infra.
>
> I'd like to build a case for this to become allowed by ASF infra. But
> first, I'd love to see some +1s, and a list of GitHub handles for people in
> our community who could make use of this feature.
>
> More technically, I think the way to make that easy and painless would be
> to add a new entry to the `.asf.yaml` file that would enable maintainers to
> assign the "triage" role to whoever they see fit. For reference, here's
> more context on that piece of automation I'd like to latch this onto here:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> FYI, xposting this to general@incubator for their attention.
>
> Max