Re: Users with commit rights in src.fp.o but no more in packager group

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Dne 06. 09. 22 v 0:25 Kevin Fenzi napsal(a):
On Mon, Sep 05, 2022 at 12:13:26PM +0200, Miro Hrončok wrote:
On 05. 09. 22 11:07, Vít Ondruch wrote:
Apart from that, I don't think that the pseudo-users or group ownership
would work. I saw a good amount of people giving the packages to some
groups or pseudo-users, but in turn, that meant there is nobody who
would care about such package.
+100
While that can surely happen, it can and does also happen when someone
is 'main admin' of a package. :) You can't make someone care.


Right, but we have a process to identify inactive maintainers. If there is no maintainer left, the package is orphaned. The ownership should never be moved to the group. It is much harder to identify identify packages which are assigned to certain group, because the groups often are active.

And as I said, being member of ruby-packagers-sig, it is not straight forward to remove group from packages. Even though it has admin privileges, it cannot be removed from the package by the group member. Maybe I should report this somewhere officially ...


I think the best thing we can do is match up the people who care with
the packages they care about. Using main admin as a indicator of who
cares for the package doesn't seem right to me. You can definitely have
cases of packages where multiple people work on it, or cases where just
one person does, but they aren't the main admin.


But this is typically problem of inactive maintainers. And I am looking forward to the current activity of identifying the inactive packagers. I truly believe this cleanup will help to deliver better content.



Anyhow, the only real reason we need main admin is that bugzilla needs 1
specific user to assign bugs to. Perhaps we could consider this when/if
we ever move off bugzilla.


+1


Vít



kevin

_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux