This sounds like a solid first pass to me, worth trying out for a month or so to see how it goes.
I'm also interested in helping, so put me on the list! On Jan 19, 2017 9:34 AM, "Slide" <[email protected]> wrote: > There was a discussion in the Governance Meeting yesterday [1] about > creating a Bug Triage "Team." The goal of this team would be to triage > issues on [2] to make sure that they are assigned to the correct component, > assigned to the correct developer and are actually still valid. The reason > the idea of an official "Team" was put forward would be so that those > people would have the ok to touch issues across the board. There are some > people that do this already (Daniel Beck and a few others) who most people > know, so they have some credibility already, some of the volunteers for > this may not, so we thought being part of the team would allow users have > more credibility if they are less well known to the community. > > We discussed in the meeting that we should focus on a couple of key areas > > 1) issues assigned to the core component with no assignee > 2) issues assigned to plugins that are part of the "recommended" set of > plugins for the new install wizard > 3) issues that are not assigned to anything or anyone in particular > > The outcome of a triage on a specific issue would be that the correct > component(s) and assignee were there. In addition, if possible a test to > see how reproducible the issue is. If an issue has languished for some time > and is using very old versions of Jenkins/plugin/etc, we would close the > issue (it could still be reopened if someone is still seeing the issue). > > I'd like to get some feedback on this proposal: > > 1) Do we have the correct scope planned out? > 2) Is more detail needed? > 3) Anything else you want to ask/propose? > > If you want to participate in the team, please let me know and I'll start > collecting a list of people. Please note, you don't need to be a developer > to help here, if you can create a Jenkins instance and try and reproduce > issues, that is great too, or even just getting the component(s) and > assignees in place would be very helpful. > > Thanks, > > Alex Earl > > > 1 - http://meetings.jenkins-ci.org/jenkins-meeting/2017/ > jenkins-meeting.2017-01-18-18.01.html > 2 - https://issues.jenkins-ci.org > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/CAPiUgVfuKH8SyZdg_MPDi963hLy- > HAAjfWS8HSYw3zdHLk7FNw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfuKH8SyZdg_MPDi963hLy-HAAjfWS8HSYw3zdHLk7FNw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACFfDqbu7xPEjVK3wyGEJAut3wwg8c7Mwe8%2Bk85Cwz10Mw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
