Maintainer call

[temoto]

Current state of Eventlet, IMHO:

• widely used
• has few really important problems and about hundred "would be nice to fix" ones
• no active development from "core team"
• steady rate of patches from community
• notorious for months and even years old issues and pull requests -- which is completely my fault
• if things go bad, only @jstasiak has access to merge on Github and upload releases to PyPI

I wish to leave this project. It would be good if group of people would emerge to continue active development, or at least devote more time into handling issues and patches. Please speak here to get familiar and have public clarity on future plans.

• whether you represent interests of a business
• how you think things should change (or not)
• what are you going to do about it

Please share link here with whoever you think would be interested.

There's about 12$ yearly expenditure on eventlet.net domain, new maintainer group should take it or abandon domain. Asking public for donations is bad idea.

Ping @jstasiak @nat-goodspeed @vstinner @flub

[nat-goodspeed]

I'm sorry to hear you're stepping down! You have been a good gatekeeper, in my experience.

"What am I going to do about it" - can't answer off the cuff.

[flub]

Hey, thanks for the years of great work! I'm afraid I haven't used eventlet myself for quite some time as you probably guessed from my activity.

With pytest we at some point decided to give anyone who's got one pull request merged developer access. Together with a CONTRIBUTING.txt file describing when to merge PRs it in theory gives people who care about maintenance the power to do so. This probably also needs a not too difficult RELEASEING.txt file as well. The tricky bit is pypi access as pypi does not make this easy, but apparently pytest is now released simply by pushing a git tag, not sure how much work it is to set that up.

I don't actually know if this would work, with pytest we still have 1-2 ppl driving the releases and doing the bulk of maintenance work. But it makes it easier for new people to get the maintenance they want at least in theory.

[vstinner]

Sorry, but I'm not interested to maintain eventlet.

[nat-goodspeed]

@temoto, as you might have guessed, I am a fan of, and user of, eventlet. I want it to continue to be maintained. I don't know what responsibilities that implies.

I assume it means monitoring issues and pull requests, making a judgment call on each pull request (with guidance to the submitter as needed), deciding when a new release is warranted, and ... working some kind of magic to effect a Release.

If you would explain what else is involved, and what buttons you must push to perform a release, the prospect might be less scary.

[nat-goodspeed]

Just for example, you probably had to "do something" to initiate CI testing under Python 3.7 as that version was coming up for release. What were you watching, and what did you have to do?

[temoto]

@nat-goodspeed

• on responsibilities: what you said + eventlet.net domain
• on release send me your PyPI username, then bin/release in eventlet source directory is designed for interactive dialog with confirm at each important step
• as of 2018-07 we use Travis for CI, study at https://docs.travis-ci.com/ edit config in eventlet source root .travis.yml example: 6c6cfc5#diff-354f30a63fb0907d4ad57269548329e3

[nat-goodspeed]

Thank you for scripting!
What's involved in maintaining the eventlet.net domain? I see bin/build-website.bash, and that it's invoked from bin/release, but I don't see where it's pushed to eventlet.net -- is that implicit when updating the gh-pages branch?
Is updating the documentation that way (and paying the fee) all that's required for eventlet.net?

[temoto]

@nat-goodspeed eventlet.net A records point to Github Pages and yes, push to gh-pages is single action required to deploy website.

[temoto]

ping @smerritt

[temoto]

@nat-goodspeed send me your PyPI username for release access
temotor@gmail.com

[beltran]

@temoto I've been a user of the library for some time and I'm somewhat familiar with the code. I'd be happy to help if I can.

[temoto]

@beltran thank you. Sorting out issues and pull requests is a good idea. Ping me or @jstasiak or @nat-goodspeed if you need access to github or pypi.

[nat-goodspeed]

@beltran, yes, it would be fabulous if you would sift through issues and pull requests. Which most urgently need action? What, if anything, still needs work with those?

[kashirin-alex]

@temoto
I'll be glad to be around, while so It is a question of time available in future.
On my side, I try to keep Hypertable steady Latest Changes followed Version 0.9.8.11.

While for me, Both(Eventlet and Hypertable) are at no less of importance, my project Thither.Direct runs on py(python/pypy) with eventlet and I have no reasons to change anything but only to improve further.
You are welcome to ask of anything, I'll definitely answer wither with can or cannot.

[vstinner]

@temoto: I have been asked if eventlet got a new maintainer. Sadly, I'm not sure about the answer after reading this issue. The issue is still open. Did someone show up and got the permissions to be the new maintainer?

[temoto]

@kashirin-alex no, thanks.

@vstinner new maintainers: @jstasiak and @nat-goodspeed