GNOME Bugzilla – Bug 685176
Please add a bugzilla product for the newcomers-tutorial
Last modified: 2014-03-01 15:31:05 UTC
This is a module that we are going to use for a newcomers event before and during the Boston Summit. See https://live.gnome.org/Boston2012/Newcomers We want participants to check out the newcomers-tutorial module, find the bugs, create patches, and file them in bugzilla, which is why we need this bugzilla product. Due to the somewhat special purpose of this module, there's no tarball release of newcomers-tutorial, nor will there ever be one.
Interesting idea. Who would be set as the default "maintainer" of it? Marina and you? Could you provide some description for that module? Will triaging be needed/welcome at all, os should gnome-bugsquad@ be warned to NOT triage for that product? After this is finished, will you mass-close all open tickets?
(In reply to comment #1) > Interesting idea. > Who would be set as the default "maintainer" of it? Marina and you? Setting Matthias and me as maintainers sounds good. > Could you provide some description for that module? A very simple application, using the gjs JavaScript interpreter and GTK+. It has some bugs intended to be discovered and fixed by newcomers as an exercise. > Will triaging be > needed/welcome at all, os should gnome-bugsquad@ be warned to NOT triage for > that product? After this is finished, will you mass-close all open tickets? Bugsquad should be warned NOT to triage for that product and, if possible, exclude it from any Bugzilla statistics. It is expected that duplicate bugs will be open for this module during a workshop. We will mass-close all open tickets after each workshop. (We will use this module for future workshops too.) Also, would it be possible to have a setting that allows anyone to close bugs in this product? Thanks!
(In reply to comment #2) > Bugsquad should be warned NOT to triage for that product and, if possible, > exclude it from any Bugzilla statistics. Which statistics? > Also, would it be possible to have a setting that allows anyone to close bugs > in this product? Might work by setting up a specific group and then assigning people to this group. Not sure.
(In reply to comment #3) > (In reply to comment #2) > > Bugsquad should be warned NOT to triage for that product and, if possible, > > exclude it from any Bugzilla statistics. > > Which statistics? Such as who closed how many bugs. > > Also, would it be possible to have a setting that allows anyone to close bugs > > in this product? > > Might work by setting up a specific group and then assigning people to this > group. Not sure. Ok, I'll look into it separately then after the product is created.
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > Bugsquad should be warned NOT to triage for that product and, if possible, > > > exclude it from any Bugzilla statistics. > > > > Which statistics? > > Such as who closed how many bugs. Not easily possible (at least not for me). Olav might know, but not sure if he has much time these days. > Ok, I'll look into it separately then after the product is created. Problem is that by default permissions are global, so if you have canconfirm and editbugs you can edit all tickets, no matter which product.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > (In reply to comment #2) > > > > Bugsquad should be warned NOT to triage for that product and, if possible, > > > > exclude it from any Bugzilla statistics. > > > > > > Which statistics? > > > > Such as who closed how many bugs. > > Not easily possible (at least not for me). Olav might know, but not sure if he > has much time these days. Ok. It will likely just require some change in the scripts to skip the module, but we don't need to block on that for creating the product. (We need it for the Friday newcomers event.) > > > Ok, I'll look into it separately then after the product is created. > > Problem is that by default permissions are global, so if you have canconfirm > and editbugs you can edit all tickets, no matter which product. Ok, I think we'll just not include the step for people to close the bug in the workshop then.
Product has been created. I've set you both as the maintainers. You (and any other developer of the product) can maintain the product here https://bugzilla.gnome.org/editproducts.cgi?action=edit&product=newcomers-tutorial Adjust it to your liking. You need to add at least one component (e.g. 'general') before new bugs can be filed. For any new component use newcomers-tutorial-maint@gnome.bugs as QA and default assignee. Important: Anyone interested in following all bug activity (including all maintainers) must watch above dummy user by adding it to the 'users to watch' list under Preferences->Email preferences.
Thank you! Created the 'general' component.
(In reply to comment #2 by Marina Zhurakhinskaya) > Bugsquad should be warned NOT to triage for that product and, if possible, > exclude it from any Bugzilla statistics. It is expected that duplicate bugs > will be open for this module during a workshop. We will mass-close all open > tickets after each workshop. (We will use this module for future workshops > too.) I might have missed some of this mass-closing - if tickets receive feedback or get closed at all, it seem to be the reporters themselves. Maybe this is part of the concept, but having dozens of old open tickets rotting hopefully is not...