Repository navigation
Discussion: Moving to a new maintainer. #95
Description
For a variety of reasons that are ultimately unimportant, I have not been able to find any attention for maintaining this package. I've recently had an offer from Morgan Fainberg to take over maintenance of the package. That proposal includes importing it into the OpenStack CI infrastructure for testing and development. That would remove it from Github, as I understand it, and use the review.openstack.org gerrit instance, and releasing it on pypi.
If anyone has an opinion on this, please comment here.
Activity
tempusfrangit commentedon May 26, 2016
As an additional point, there would still be a git replica in github but it would be under the OpenStack organization (https://github.com/openstack/python-memcached or similar). The changes would be:
From a standpoint of what we're looking to do with this module if it is taken over:
Reasons for why I have offered to take this over are simple. Pylibmc is very good, but is based in c-bindings, which means we have extra work in openstack due to the way we use eventlet and greenlet. The other options are bmemcached and pymemcached. Both of the alternatives are much more complex to use. I also know that some distributions have issues with convergence of "client" libraries in their main repositories, so keeping the options to a single case in "main" is important.
I am happy to answer/discuss any questions or concerns here before taking this over. Thanks for the open discussion!
thomasgoirand commentedon May 26, 2016
Hi Sean. I very much appreciate your openness to switching maintainer. We get busy and our attention may go away, it's important to recognize it so that projects can move ahead for those who care. I can assure you that you'll be happy of the work being done within OpenStack, and also the git review workflow is super nice.
stevemar commentedon May 26, 2016
FWIW, I work with @morganfainberg very closely and am also volunteering my time to maintaining the project and addressing some of the open issues/PRs.
linsomniac commentedon Jun 6, 2016
I'm going to call this discussion closed. I'll take a look and see if there's anything else I can move into the base repo, and then I'm going to ask Morgan to start the process of migrating it. We had a discussion at PyCon about the process.
tempusfrangit commentedon Jun 6, 2016
I'll start the process of getting the bits in place for moving this to the openstack infrastructure.
I'll propose a PR here once that is ready to link to the new authoratative locations and redirect back to LaunchPad for bugs.
A couple things I'll need:
I expect I'll have the import bits pushed to a forked copy in the next day or so, and it imported to openstack-infra by the end of the week provided we have no hiccups.
A new release of python-memcached will not be pushed from the openstack infra immediately, so we might want to push with the current fixes added over the last week before the import.
I also want to say thanks @linsomniac for maintaining this library as long as you have! :) I'm happy we can continue it!
Make sure nothing but Unicode goes into the markup cache
tempusfrangit commentedon Nov 29, 2016
Revisiting this conversation. I know it dropped off the radar (some emails I think were lost - and I got a bit swamped, now revisiting directly).
Sean, are you willing to continue with this transition?
timgraham commentedon Dec 2, 2016
What advantage does moving testing, issues, etc. to OpenStack provide? Are there problems with the current setup on GitHub? Speaking personally, nearly all the Python libraries (mainly Django related) use GitHub so it's a familiar interface. I don't think I've contributed to anything that uses OpenStack.
timgraham commentedon Dec 14, 2016
One option is moving to the Jazzband organization. I would like to help maintain things in at least the short term to solve issues/regressions that affect Django.
Switch from abandoned python-memcached to pylibmc
Switch from abandoned python-memcached to pylibmc
samupl commentedon Mar 26, 2019
@morganfainberg @linsomniac Have you been able to come to a conclusion about this? I see there are people willing to contribute (including me), but without a maintainer there's a lot of issues and PR that are left unattended.
codingjoe commentedon Nov 25, 2019
I agree with @timgraham that @jazzband would be an option. However, I am not sure if we need two synchronous clients going forward. https://github.com/pinterest/pymemcache is backed by a major corporation, and I am always happy, when companies pay their developers to do open source code.
Truth is, since Pintrest is already spending money on maintaining
pymemcache, I'd rather spend my free time on other projects.bitcity commentedon Aug 18, 2020
This is an officially recommended client for Django and it would be great to have it back to an active development stage (e.g with jazzband / @timgraham ).
Relevant discussions for using pinterest/pymemcache with Django :
ngnpope commentedon Nov 11, 2020
@linsomniac Just raising the issue of maintainership here again. Would you be prepared to move this project to the Jazzband organisation as recommended by a number of others above?