Non-responsive maintainer: cleber #3659
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
3 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference
fesco/tickets#3659
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
FAS username of the non-responsive maintainer
cleber
Names of package(s) with unaddressed issues
python-avocado python-aexpect
Link to non-responsive maintainer bug
https://bugzilla.redhat.com/show_bug.cgi?id=2499900
Unaddressed issues
Link to list: Bug List
Individual bugs:
Link to mailing list post for the non-responsive maintainer process
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/6VD2262E5T33KL4PWDJGJNZFRPO3DOH7/
Affected package co-maintainers (if any)
No response
Submitter is interested in comaintaining the package(s):
Additional notes
No response
This is a ticket for the Fedora's Policy for nonresponsive package maintainers.
@crosa is not a valid FAS username.
@hpaluch-pil, if you meant, @cleber, can you please change the ticket title and description accordingly?
@gotmax23 wrote in #3659 (comment):
Ooops, you are right! I was confused that he has e-mail
Cleber Rosa <crosa@r...m>- however now I see from https://bodhi.fedoraproject.org/updates/FEDORA-2022-4ee3339f88 that he has usernamecleberNon-responsive maintainer: crosato Non-responsive maintainer: cleber+1
+1
(I set the ticket's due date to August 18, 2026, when the packages will be orphaned if we receive no response from the maintainer as per the policy)
Actually, I did the math wrong. The devel list post was sent over a week before the FESCo ticket was filed, so the timeline to mass orphan the nonresponsive maintainer's packages is (ticket filing date + two weeks). The packages should be mass orphaned tomorrow.
Per the non-responsive maintainer policy voting rules: APPROVED (+2, 0, 0)
Did you want to file a releng ticket for this?
Just found that Cleber Rosa is active on GitHub (under different nick - "clebergnu" having organization RedHat, but contributing also to projects in Avocado Group).
Link: https://github.com/clebergnu
Is anyone in Fedora/RedHat able to ping him - for clarification?
decathorpe wrote in #3659 (comment):
releng/tickets#13467
@hpaluch-pil wrote in #3659 (comment):
It seems there were multiple attempts to contact them that have not succeeded, but if anybody wants to try to contact them again, that's of course welcome. Note that this process still allows the maintainer to pick up the orphaned packages via a one-click process for 6 weeks after they are first orphaned.
This has been processed by releng --- thanks!