casperdcl/git-fame

Project is abandoned

Opened this issue · 3 comments

jaraco commented

I've started out using git-fame as a part of the solution for the Coherent Build System, but I'm noticing that there's not been much maintenance activity on the project in 9 months. That's okay, of course, but if this project isn't maintained, I'll need to figure out an alternative strategy (fork, re-implement). I'd much rather contribute to this project.

If you're considering stepping back from the project, would you consider handing it off to someone else? I'd be happy to own or co-own the project. If you're interested in that, let me know what sorts of constraints or guard rails you'd like. If you're ready to go, please add me to the PyPI project and consider transferring the repository to /coherent-oss (similar to /jazzband where we can share custody).

Thanks for creating git-fame and let me know how I (or others) can help.

jaraco commented

Looking at the tags, the last release was made more than a year ago, the latest commit was last year, and in a couple of places (here and #96), I've pinged the maintainer for a status update on the project. Given the lack of response, I've concluded the project is abandoned, and I'll seek to take over maintenance in PyPI.

casperdcl commented

Thanks for your interest in helping maintain open source package(s)!

In this case I don't think you've garnered enough cred (à la https://gist.cdcl.ml/oss-takeover) though 🙃

jaraco commented

Thanks for introducing me to oss-takeover. I'm new to that, and it makes sense.

Although I don't have a lot of cred in this package, I do maintain literally hundreds of packages in the Python ecosystem utilizing an innovative skeleton to make such mass project maintenance more scalable. So although I don't have the cred here, I have established a reputation for maintaining many packages in the Python ecosystem.

I would be considerate of the package and strive to leave the system in a better state than I found it, including pulling broken releases (if any) and being responsive to emergent concerns following any release.

And of course, should you be willing to share the project, I would of course defer to your judgement when it comes to any conflict. That is, should you wish to remain active in the project, you would still be principal on it. I'm less looking to take over than I am to take responsibility and help keep the project maintained.

Let me know if that changes your perspective. If not, feel free to close.

And again, thanks for creating this project and for stepping back up to work on it.