Co-maintainer needed

[jorgenschaefer]

It's time to realize that I simply do not have the time to handle all the issues and feature requests that arrive for Elpy. There are currently 11 unanswered issues and PRs, and countless others that I have answered but not looked at any further. That's not a good situation. Over the years, Elpy has grown to have a sizeable user community, and I have found other things to work on, both in software and elsewhere.

I need someone to help improving Elpy.

Eventually that will also mean that this someone will also needs to take over maintainership, but that's not an immediate necessity, and I will not be gone, still available for questions and also try to help as much as my time allows.

Volunteers should start by answering issues, offering pull requests (so I can understand their priorities, coding style, etc.), and maybe even reviewing existing pull requests. We can then talk about repo access and how to proceed further.

One small hint: The hardest part of being a maintainer is saying "no" to stuff that sounds nice, but would just add way too much maintenance and usability burden for the benefit it brings.

[jorgenschaefer]

@galaunay no pressure, but maybe you are interested :-D

[rgemulla]

Another option may be to distribute work across multiple people, perhaps even multiple committers.

Personally, I'd be willing to continue to bugfix/improve the interactive Python components, as well as to test and comment on related issues and PRs. For example, I think PR #1212 is useful and ready to be integrated.

[jorgenschaefer]

Thank you. You should have an invitation e-mail. :-)

[rgemulla]

Well, thank you!

I won't merge my own PRs for now, unless they are small bugfixes only. I'd appreciate another set of eyes on the larger ones.

[jorgenschaefer]

Fair warning: It's unlikely I will be able to look at PRs for the next two weeks at least.

[rgemulla]

I don't think these things need to be rushed ;)

[galaunay]

I am indeed interested !

If @rgemulla handles the interactive shell related issues and PR, I can review the rest and send you the things that fell outside my knowledge of Elpy (hopefully not too much ?).

I think the PR/issues assignment functionality in github could be handy if we go with that kind of organization.

[rgemulla]

@galaunay: Sounds great to me! Note that I'd also appreciate a pair of eyes at the PRs I submit. I am quite confident w.r.t to the two current ones, but one never knows.

[jorgenschaefer]

Added as collaborator – thank you both so very much for your help!

[gopar]

I can look at any issues the elpy-django module has since I kinda wrote it :P And casual PR stuff. But eh, up to yall

[jorgenschaefer]

Thank you, and enjoy :-)

[vds]

I'd be happy to help with python code, if needed.

[jorgenschaefer]

Thank you! Please do feel free to look at issues and provide PRs if you see something you'd like to work on! :-)