After looking through the orphaned packages, I found one that looks like a good candidate for me to help with, python-cachelib, as this package is not that large and I am well-versed in Python.
I've cloned it down and worked on bringing it more up-to-date. Now that I have something passing the test suite, I thought I'd file a PR and start a discussion. I forked the project on Pagure.io, but found that even with my own personal fork, I don't seem to have commit access to it without being in the Packagers group. Is that standard? I thought the point of the fork was to allow non-packagers to use the PR mechanism as an easy mechanism for sponsors to view proposals. In any case, I decided to through it up on GitHub temporarily so I could at least create a Remote PR. https://src.fedoraproject.org/rpms/python-cachelib/pull-request/6 I am considering becoming a [co-]maintainer if needed to help keep this package in good, solid shape, however it does look like it has been adopted by topazus in the last couple of days since I started working on it. I am also working on setting up a Python 3.13 environment to debug the issue reported in bug #2251780. Thanks, -- Loren M. Lang lor...@north-winds.org http://www.north-winds.org/ Public Key: http://www.north-winds.org/lorenl_pubkey.asc Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
