Non-responsive maintainer: sham1 #3631
Labels
No labels
Closed As
Accepted
Closed As
Duplicate
Closed As
Insufficient data
Closed As
Invalid
Closed As
Rejected
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
9 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference
fesco/tickets#3631
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
sham1
Names of package(s) with unaddressed issues
ledger
Link to non-responsive maintainer bug
https://bugzilla.redhat.com/show_bug.cgi?id=2491301
Unaddressed issues
The ledger bugs are:
This is the complete list of bugs:
All there bugs are here
Most of the bugs are a year old, a few older.
Link to mailing list post for the non-responsive maintainer process
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MYKUKPABD7MJA5R3COMRBTYUO6RIUL7B/
Affected package co-maintainers (if any)
No response
Submitter is interested in comaintaining the package(s):
Additional notes
I'm interested in the
ledgerpackage only.'This is a ticket for the Fedora's Policy for nonresponsive package maintainers.'
Non-responsive maintainer: <FAS username>to Non-responsive maintainer: sham1Hi @ankursinha, I would also be interested in co-maintaining. This ties in with some other packaging work I had done in the past with
beancount.ledgerwas a dependency, but it was out-of-date in Fedora and this held up my ability to go deeper on it, at the time.CC @sham1
sham1 is main admin of rpms/WindowMaker
sham1 has a bugzilla override on rpms/WindowMaker
sham1 is main admin of rpms/WindowMaker-extra
sham1 has a bugzilla override on rpms/WindowMaker-extra
sham1 is main admin of rpms/bubblemon
sham1 has a bugzilla override on rpms/bubblemon
sham1 is main admin of rpms/chibi-scheme
sham1 has a bugzilla override on rpms/chibi-scheme
sham1 is main admin of rpms/chicken
sham1 has a bugzilla override on rpms/chicken
sham1 is main admin of rpms/emacs-lua
sham1 has a bugzilla override on rpms/emacs-lua
sham1 is main admin of rpms/herbstluftwm
sham1 has a bugzilla override on rpms/herbstluftwm
sham1 is main admin of rpms/hsetroot
sham1 has a bugzilla override on rpms/hsetroot
sham1 is main admin of rpms/ledger
sham1 has a bugzilla override on rpms/ledger
sham1 is main admin of rpms/libdockapp
sham1 has a bugzilla override on rpms/libdockapp
sham1 is main admin of rpms/libfixposix
sham1 has a bugzilla override on rpms/libfixposix
sham1 is main admin of rpms/maildir-utils
sham1 has a bugzilla override on rpms/maildir-utils
sham1 is main admin of rpms/oksh
sham1 has a bugzilla override on rpms/oksh
sham1 is main admin of rpms/qiv
sham1 has a bugzilla override on rpms/qiv
sham1 is main admin of rpms/vis
sham1 has a bugzilla override on rpms/vis
sham1 is main admin of rpms/wmCalClock
sham1 has a bugzilla override on rpms/wmCalClock
sham1 is main admin of rpms/wmacpi
sham1 has a bugzilla override on rpms/wmacpi
sham1 is main admin of rpms/wmapmload
sham1 has a bugzilla override on rpms/wmapmload
sham1 is main admin of rpms/wmdocker
sham1 has a bugzilla override on rpms/wmdocker
sham1 is main admin of rpms/wmweather+
sham1 has a bugzilla override on rpms/wmweather+
sham1 is main admin of rpms/xss-lock
sham1 has a bugzilla override on rpms/xss-lock
+1
Per https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/#steps:
If there are no objections, in three days, @ankursinha and @jflory7 should be given admin privs on ledger. After another week, we'll ping sham1 again, and if there's still no response, we can make one of you the main admin and orphan the rest of the packages listed above.
I see no activity since July 21, 2025 in dist-git, bodhi, koji, badges, or on pagure.io: +1
+1
+1
+1
Confirmed - last activity July 21 last year, but last Bugzilla activity is ... 2 years ago, which is... not good
After three days (per the non-responsive maintainer process's special voting rules): APPROVED (+5, 0, -0)
ledger.^ is all based on https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/#steps, so this is not a separate proposal that needs to be voted on.
Admins added.
Announced in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AFF4NYSCZMHAPIHCDR4CPNI3ILPCHWYO/
Oh hello, sorry about being non-responsive. I noticed that @ankursinha as a comaintainer in
ledger, and that's wonderful. Hopefully we can get more stuff with this.I've unfortunately been a bit busy with real life stuff, but hopefully I can do more now.
@sham1, welcome back :). I guess we can close this ticket now. I'd suggest going through the list of your packages in #3631 (comment) and seeing if it makes sense to orphan any of them so you can reduce your maintenance load.
I'll second what @gotmax23 wrote: @sham1 please add comtaintainers or orphan packages. But either way, ledger situation has been addressed and we don't need to do anything here.