On Wed, Sep 29, 2021 at 1:51 PM Miro Hrončok <mhroncok(a)redhat.com> wrote:
Since the @java-maint-sig group is esentially non-responsive, I
suggest we do
the following:
Thanks for making this distinction - @java-maint-sig group is not the
same as Java SIG.
Some of the most active members of Java SIG (like me or OpenJDK
maintainers) are not
(and never were) members of @java-maint-sig.
1) We remove all BZ assignee overrides to @java-maint-sig. This is a
must.
2) We remove access of @java-maint-sig from all packages.
3) We ask the members of the group if they want to admin the list/BZ account.
3a) We give it to the volunteer.
3b) We empty the group and cancel the BZ account/list if nobody shows up.
4) We *don't orphan the packages*, they have some "de jure" maintainers.
+1 That is a good plan.
Several months ago I demoted @java-maint-sig from admin to committer
for all packages I am primary maintainer of, and I was considering
demoting it further to collaborator or ticket level, or removing
altogether as I my packages did not receive any contribution from the
group for the past months, except for a couple PRs that don't require
direct access to the packages.
--
Mikolaj Izdebski
The packages that fail to install and/or build will eventually die out due to
the existing processes.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure