2019(e)ko abenduaren 9(a) 15:07:07 (CET)-(e)an, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx>-(e)k hau idatzi zuen:
On Mon, Dec 09, 2019 at 08:46:28AM -0500, Neal Gompa wrote:On Mon, Dec 9, 2019 at 8:39 AM Karsten Hopp <karsten@xxxxxxxxxx> wrote:
Hi,
We are currently working on getting rid of the git repo at fedora-scm-requests [1] which is nowadays only used to store the overrides of the default assignee in bugzilla (for example to allow different default assignee for Fedora and EPEL).
I am working on porting this mechanism to dist-git itself (much like we did for the anitya integration a few weeks ago).
We are thinking on providing a simple text field to submit FAS username or email to override the default assignee, the big question is then, who should be allowed to update this field ?
Should the main admin be able to set someone else as assignee ?
If there is already an override assignee, who should be allowed to change that ?
If there's no override assignee set, can everyone become it or is that up to the main admin of the component to decide and set ?
I think in this case, it should be the main admin who can change this.
The main admin (and infra/releng) only, or all the admins of the project?
Pierre
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
--
Julen Landa Alustiza <jlanda@xxxxxxxxxxxxxxxxx>
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
