Maintenance help?

[iloveitaly]

It's always a pain when users reach out asking for updates but never offer to help with maintenance. It looks like there are some open PRs that would be great to merge in, and you've probably moved on to other things.

I'd love to help with maintenance if you are open to it. Let me know if you are interested!

[iloveitaly]

Friendly ping here :)

[edgarrmondragon]

Unfortunately the org seems inactive in the channels listed in http://litl.com/contact.html, for example on X/Twitter they were last active on 2016.

@bgreen-litl doesn't seem active either

[iloveitaly]

Yeah, you are right—still would love to take over the repo vs fork. Forks never work out well for the community.

[edgarrmondragon]

backoff is still the 140th most downloaded package from PyPI¹ so I think we should start thinking about forking 😕

Footnotes

1. https://hugovk.github.io/top-pypi-packages/ ↩

[edgarrmondragon]

So, is anyone interested in helping to maintain a fork? 😅

[iloveitaly]

I've been chatting with Bob Green over email. He's open to merging some of the PRs and continuing to maintain this fork!

[gaby]

@iloveitaly Thank you! Looking forward.

[mattseymour]

I have a fork of this repo called re-engage https://github.com/mattseymour/re-engage which I am going to pick up for changes and fixes for personal use and other changes if people want them. But completely agree that forks are always.... interesting.

I would like to see this repo continue to get some love and attention. But if the repo is not going to be updated or the update process is sporadic there are two options I would like to current maintainer to think about

1. Moving this project to a new home (like Jazzband is to Django)where it's a community effort.
   Or...
2. Add a couple of contributors who can push the project forwards and have permissions to release to pypi.

The being able to release to Pypi is important as if people cannot do this then usage will be low.

[edgarrmondragon]

I've been chatting with Bob Green over email. He's open to merging some of the PRs and continuing to maintain this fork!

@iloveitaly I'm curious, did that go anywhere?

[iloveitaly]

Went silent on me, let me drop him another note.

[marrrcin]

Any update @iloveitaly ? 👀

[edgarrmondragon]

I've got started with edgarrmondragon#1. I'm not sure I'll be able to be significantly responsive, but I think it's possible to apply for PEP 541 if we get some momentum and improvements in a fork.

[gaby]

I've got started with edgarrmondragon#1. I'm not sure I'll be able to be significantly responsive, but I think it's possible to apply for PEP 541 if we get some momentum and improvements in a fork.

We don't need a fork that will get abandoned months in. We need maintainers on this repo

[gaby]

@bgreen-litl We need an update regarding maintainance, adding maintainers or transfering the project to another Org. Thanks

[edgarrmondragon]

I've got started with edgarrmondragon#1. I'm not sure I'll be able to be significantly responsive, but I think it's possible to apply for PEP 541 if we get some momentum and improvements in a fork.

We don't need a fork that will get abandoned months in. We need maintainers on this repo

I agree, but we haven't seen success in that direction 😔

[funkyfuture]

mind, that there's stamina that is probably an easy to integrate replacement for backoff.

[iloveitaly]

Let me ping again! No response yet.

[MichaelLan]

I also want to ping!

[Mark90]

After researching retry libraries I landed on backoff which is an intuitive fit in terms of code and documentation. I saw the last release was from 2022, which for a library with no dependencies should be fine. But if the maintainer(s) is/are AWOL then that's a different matter. I'll still probably just try it.

What long-term decision are most people leaning towards?

I agree making a fork is not great as you lose the name of the package, the issue/PR/release history, etc.

[iloveitaly]

Still trying to get another response from Bob, would love to just maintain this library and keep it going.