Community
Participate
Working Groups
Committers have the ability to "triage" bugs in some ways that Eclipse contributors can not. And, that's good and necessary. For example, committers can change priorities, severity, component and close bugs opened by others, etc. so you just can't have anyone doing those things. But, occasionally, Projects would like to authorize someone to have this "bug-triage" ability, but not make them a committer. A committer is thought to be a role where they contribute Intellectual Property via CVS commits, etc., whereas these bug-triage contributors do not need to commit to cvs, though they do a lot of testing and/or verification of bugs for the project. So, we (the Tools PMC, specifically) would like our Eclipse infrastructure enhanced to allow this type of extra permission. While there's probably several ways to solve this (and probably several infrastructure issues I am not aware of), I'd see that solution including the following characteristics: Ability for a Project Lead or PMC member to submit, and authorize this enhanced bugzilla capability. (That is, no "vote" is required, but instead an properly authorized person can do it). Similar for removing or revoking this enhanced capability. Ideally some mechanism to list those that have this bug-triage permission, that are also not committers (that is, so identifies this specific group of people). Ideally, longer term perhaps, some query to see when the "last modification" was done by the person with bug-triage permissions. This would be useful when doing some audit of who was authorized, but no longer actively doing the job, so that the list will be easier to keep accurate over the years.
+1
1+ I am pretty sure there was an email thread that agreed that webmaster could do this work. Can you confirm?
If there are no objections from Bjorn in doing this, there is a minimal amount of tweaking I'd need to do to some of our internal tools. At the very least, I'd like to keep track of who is empowered this way. Adding a dependency to Bugzilla 3.2. If I'm going to hack stuff, I might as well target the latest release. Bjorn: do I have your blessing to do this?
(In reply to comment #4) > Bjorn: do I have your blessing to do this? If that's what people want, ok.
I've created a Bugzilla group called BugTriage, and this group can edit bugs. To keep this simple, just send me (webmaster) a list of email addresses you'd like in this group. We'll keep track of it internally. Does that sound reasonable?
(In reply to comment #7) > > Does that sound reasonable? Yes. (Who says old bugs don't get addressed :)
I think we can move this to "fixed" ... with maybe one more action. Where will this be documented? Some infrastructure wiki? Once that's done, perhaps a note to "committers list"? (Or, if you'd prefer just word of mouth, and use this bug as documentation, then I guess can just be closed as fixed). Thanks.
http://wiki.eclipse.org/Bug_Reporting_FAQ#Bug_Editing_and_Triage That document is linked from the main Development resources doc: http://wiki.eclipse.org/Development_Resources (In reply to comment #9) > perhaps a note to "committers list"? I think that would be great if it's not sent by 'me'. If another committer sends it, it will likely be read :-)
(In reply to comment #10) > (In reply to comment #9) > > perhaps a note to "committers list"? > > I think that would be great if it's not sent by 'me'. If another committer > sends it, it will likely be read :-) I'll send one (I'm sure people read your posts and mail, Denis ... at least as much as they read anyone's :) I'll send the following soon, unless there's (real) quick comments for suggestions/improvements. = = = = Subject: Do you know anyone who wants to triage bugs they do not own? And, no, I am not actually asking for volunteers ... yet :). But I did want to make committers aware of a new process and policy that allows non-committers to be authorized to be "bug triage specialists". This doesn't come up often, but occasionally non-committers have volunteered (or been assigned) to do some heavy duty bug triage over a long period of time. For example, they may want or need to go through a several hundred old bugs to test if they are still reproducible on current releases. If they are, they may want to make some changes to the bug that normally only committers or owners can make (such as, move to a new component or change assignee field). Or if the bug is not reproducible, they may want to close the bug as "worksforme". In some cases of course, people playing this role may deserve to be full fledged committers. But in other cases, the people doing this work may not have the background, history, experience, or desire to be a committer on each and every project for which they triage bugs. And if they are not accessing code repositories, contributing Intellectual Property, or contributing to the decisions and direction of the project, there is no need for the relatively heavy weight process of them becoming a committer. So, there is a new lighter-weight process to get "BugTriage" authorization. See http://wiki.eclipse.org/Bug_Reporting_FAQ#Bug_Editing_and_Triage. While the details and circumstances of using this will vary from project to project, this is intended to be used primarily for cases where people are spending lots of time doing this type of triage work, over a long period of time, and have earned the trust of committers they work closely with. Anyone and everyone is still very welcome and encouraged to triage what ever bugs they want, in the traditional way, simply commenting in the bug whatever results were found, and recommendations for changes to appropriate fields. If someone is doing only a few dozen bugs for only several weeks, this traditional method works fine. But, if they are doing this many hours each week over many months, they deserve the recognition, permissions, and efficiency this new authorization can give. If questions, please check with your Project Lead, PMC, or ask in bug 265880 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=265880). Thanks,
