New release?

[jacobsvante]

There's been some good changes to the code since 0.26.2 was released, like d60c3f8. What would you say @neithere about releasing 0.26.3?

[hugovk]

Here's a list of changes to master since 0.26.2:

v0.26.2...master

[cscutcher]

Been over a year now. @neithere, if you've got no time to look after the project any more that's totally understandable but just wondering whether to look elsewhere for an actively released fork. In any case thanks for all the hard work up to now.

[neithere]

Sorry for the delay, I'm afraid I really don't have time for my FOSS projects nowadays. Every PR must be properly reviewed and tested, also in the context of existing issues. Once a bunch of them has accumulated, they should be reviewed as a whole. It takes a lot of time. For a number of reasons it was not a problem before but nearly impossible (for me) right now.

I'm going to transfer one of my projects (django-autoslug) to the @jazzband organization and see if it works. If it does, I'll ask them if they want argh, too, and hand it over. That would prevent further stagnation of the project that I love but just can't take care of.

Andy

[cscutcher]

@neithere no worries! totally understandable! I hadn't heard of jazzband, they seem supercool. If it turns out they don't think argh is viable for their stewardship, and no one else is keen, then I'd be happy to look after it.

[metaperl]

so @neithere do you think argh maintainership should be turned over to @cscutcher ?

[tankorsmash]

@neithere I love argh, would love to have someone willing, like @cscutcher to take over.

[polm]

Would be great to have a new maintainer for this ❤️

[maphew]

Anyone can start maintaining a fork, make noise here (so the community knows), let @neithere know, and then he can transfer when there's the requisite combination of time and attention in his world to make that happen.

[hugovk]

If it's any motivation, Tidelift is offering ~$50/month for maintaining this library:

• https://tidelift.com/lifter/search/pypi/argh

[neithere]

Hey guys, thank you for your patience!

I'm glad to say that I'm back. Still not much free time, but at least I'm now again working 1) 100% with Python (compared to ~1% for the last six years), and 2) in a very FOSS-friendly company.

I'm going to try gradually getting Argh back in shape soon. There are lots of stale issues and PRs, forks and even maintenance offers. There are also some thoughts of my own as I've been using the library all this time and would like to fix some limitations.

It will take time to clean up the mess and outline the new roadmap. The best thing a volunteer can do to speed this up is find and tag duplicate issues and check which PRs are still relevant. This way we could at least have the simplest and most annoying issues killed off ASAP and have a fresh release before venturing into anything more interesting and complicated like mapping type annotations to argparse.