Please create a BZ product "Gentoo Council" similar to "Gentoo Foundation", text "Council related bugs" Default assignee: council@gentoo.org Components: only one ("unspecified"?) The bug entry template should have a checkbox to make the bug restricted to the *Council* bugzilla group. [I do hope we don't get much more "appeal bugs" in the future, but one never knows... :/)
What components should be inside? I was also thinking it would be reasonable to have something for QA as well. However, maybe it'd be more reasonable to have one product for all that stuff, and just different components inside.
(note: I haven't checked if bz can do that for different access restrictions)
(In reply to Michał Górny from comment #1) > What components should be inside? I was also thinking it would be reasonable > to have something for QA as well. However, maybe it'd be more reasonable to > have one product for all that stuff, and just different components inside. I'm not sure if this kind of reuse is useful as its not user-facing, in any case the list of initial components was specified in original description: Components: only one ("unspecified"?) I should add though, that this should be followed by a council group in BZ
Discussed again on today's council meeting and confirming Gentoo Council Product, with initial component of "unspecified", but wanting to have the possibility to add further components later.
https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Council I've also enabled the access controls for devs group, since we seem to have those in other products too. Lemme know if it works for you, or if you need anything changed.
(In reply to Michał Górny from comment #5) > https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Council > > I've also enabled the access controls for devs group, since we seem to have > those in other products too. Lemme know if it works for you, or if you need > anything changed. Looks good to me!
