Am 29.09.2021 um 13:49 schrieb Miro Hrončok
<mhroncok(a)redhat.com>:
Since many have moved this discussion away from this question, let me please bring back
the main reason this was posted.
Since the @java-maint-sig group is esentially non-responsive, I suggest we do the
following:
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.
The packages that fail to install and/or build will eventually die out due to the
existing processes.
Given the current situation, that seems like a sensible way to go.
However, under no circumstances should such a move be put into action unless all current
group members have been explicitly asked for their opinions.
For one thing, I think that would be simply bad practice. For another, about half of the
current 12 members seem to be dedicated to Java, (they are "only" assigned to
the 200 - 300 mostly Java core packages, not thousands of packages across the
distribution). So they are potentially the ones who are currently actively maintaining the
Fedora Java stack. They should have a say in the matter how to organise the work.
If no one responds within 1-2 weeks (which I would almost expect, unfortunately), then
this structure is clearly obsolete.