Re: What's the right way to abandon an open source package?
Hello, On Tue, 1 Jul 2014 12:30:44 -0500 Skip Montanaro s...@python.org wrote: This is only Python-related because the package in question (lockfile at PyPI) is written in Python and hosted (at least in part) on PyPI. I have not had any interest in maintaining this package for a few years. I wrote it mostly as an exercise, and while I do happen to use it ever-so-slightly in my work, its state as of a few years ago is perfect for my modest needs. Working on it no longer scratches any itches for me. I'd much rather be out riding my bike. I'm at the point in my professional career that I no longer want to program at home after spending all day programming at work. I've tried to find people to take it over, but so far unsuccessfully. I continue to get bug reports, some from OS package maintainers or maintainers of applications which use lockfile. Lots of these people seem demanding of my time (which makes me even less interested in lockfile maintenance). Is there a correct way to abandon the damn thing? Put it on github and reply to any request with patches welcome!. That's assuming it's ok for you once a month to go thru pull request queue and press Merge or Close buttons. If that's too hard, then well, don't press those buttons - someone else will pick those pulls into one's own fork and will maintain it. Thx, Skip -- https://mail.python.org/mailman/listinfo/python-list -- Best regards, Paul mailto:pmis...@gmail.com -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
On 07/01/2014 10:30 AM, Skip Montanaro wrote: This is only Python-related because the package in question (lockfile at PyPI) is written in Python and hosted (at least in part) on PyPI. I have not had any interest in maintaining this package for a few years. I wrote it mostly as an exercise, and while I do happen to use it ever-so-slightly in my work, its state as of a few years ago is perfect for my modest needs. Working on it no longer scratches any itches for me. I'd much rather be out riding my bike. I'm at the point in my professional career that I no longer want to program at home after spending all day programming at work. I've tried to find people to take it over, but so far unsuccessfully. I continue to get bug reports, some from OS package maintainers or maintainers of applications which use lockfile. Lots of these people seem demanding of my time (which makes me even less interested in lockfile maintenance). Is there a correct way to abandon the damn thing? I'm willing to take it on. -- ~Ethan~ -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
On Tue, 01 Jul 2014 20:59:48 +0300, Paul Sokolovsky wrote: Put it on github http://nedbatchelder.com/blog/201405/github_monoculture.html Besides, do you really want to give your support to a crowd who built a replica of the Oval Office in their corporate offices? While git is a decent DVCS, almost as good as hg, there's something about git culture which attracts geek wankery. -- Steven -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
It's on github (by request from another person who didn't take it over). It's also on Google Code. I'm actually pretty naive and agnostic about these various hosting sites and their favorite revision control tools, but I don't have enough time to master all of them. I think I have a couple volunteers. Cross your fingers. Thanks, Skip On Tue, Jul 1, 2014 at 1:40 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: On Tue, 01 Jul 2014 20:59:48 +0300, Paul Sokolovsky wrote: Put it on github http://nedbatchelder.com/blog/201405/github_monoculture.html Besides, do you really want to give your support to a crowd who built a replica of the Oval Office in their corporate offices? While git is a decent DVCS, almost as good as hg, there's something about git culture which attracts geek wankery. -- Steven -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
Hello, On 01 Jul 2014 18:40:23 GMT Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: On Tue, 01 Jul 2014 20:59:48 +0300, Paul Sokolovsky wrote: Put it on github http://nedbatchelder.com/blog/201405/github_monoculture.html Everyone who (re)posts stuff like that should have mandatory N.B. of I just bought a server farm to offer an alternative. And come on, the guy asked the *easiest* way to lose an open-source package (apparently, in not an anti-social way). Besides, do you really want to give your support to a crowd who built a replica of the Oval Office in their corporate offices? While git is a decent DVCS, almost as good as hg, there's something about git culture which attracts geek wankery. You mix up git and some other things. First is github, inc.. I'm sure all that publicity is their secret plan to overthrow google and facebook. Bwahaha. Second thing is (young pythonistas, close your eyes and ears!) is Roby. That's where that slight smell of decay which bothers you comes from. Indeed, using software written in Ruby is disgusting. But if you look around, all software written for advanced git project hosting is written in Ruby - gitorious, gitlab. Steven, I hope you have plan how to resolve that situation with Python enlightment too. Until then people will use that ruby stuff, in particular github. (Ah, and if your solution is hg, sorry, that won't work - for many reasons, including CPython big startup delay :-F. Don't speak about git monoculture though - *BSD folks are still using CVS, so world is safe). -- Steven -- https://mail.python.org/mailman/listinfo/python-list -- Best regards, Paul mailto:pmis...@gmail.com -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
On Tue, Jul 1, 2014 at 1:05 PM, Paul Sokolovsky pmis...@gmail.com wrote: On 01 Jul 2014 18:40:23 GMT Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: http://nedbatchelder.com/blog/201405/github_monoculture.html Everyone who (re)posts stuff like that should have mandatory N.B. of I just bought a server farm to offer an alternative. There already are alternatives. Second thing is (young pythonistas, close your eyes and ears!) is Roby. That's where that slight smell of decay which bothers you comes from. Indeed, using software written in Ruby is disgusting. But if you look around, all software written for advanced git project hosting is written in Ruby - gitorious, gitlab. Steven, I hope you have plan how to resolve that situation with Python enlightment too. Until then people will use that ruby stuff, in particular github. Ruby has nothing to do with it. (And no, I don't think that using software written in Ruby is disgusting.) We're talking about web sites; from the user perspective, they're just neat bundles of networking protocols and the implementation language is irrelevant, as long as their needs are met. (Ah, and if your solution is hg, sorry, that won't work - for many reasons, including CPython big startup delay :-F. The warm startup delay for CPython on my box is about 17 ms. hg starts, prints its list of commands, and exits in about 44 ms. That's practically invisible to the user, unless you're using a script that involves executing hg from the shell hundreds of times, in which case you might want to consider having your script use the command server instead. Or if it's the start-up delay on the web server that you're concerned about, then set up the server to use persistent processes. -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
Skip Montanaro s...@python.org writes: I've tried to find people to take it over, but so far unsuccessfully. The principle (laid out by ESR in “The Cathedral and the Bazaar”) is: When you lose interest in a program, your last duty to it is to hand it off to a competent successor. URL:http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s02.html Whether successful or not, I can testify that Skip has been conscientious in following this principle: he has been asking parties who have demonstrated interest and/or competence for some time now to take over maintenance of the ‘lockfile’ library. I continue to get bug reports, some from OS package maintainers or maintainers of applications which use lockfile. Lots of these people seem demanding of my time (which makes me even less interested in lockfile maintenance). I don't know of any good way to make those decrease, without some other contact point for the project becoming more prominent than yours. Is there a correct way to abandon the damn thing? You have, IMO, already put in sufficient public effort to give opportunity to potential maintainers. I would say that, in the case of the ‘lockfile’ library, you have already discharged your responsibilities under the above principle; and can politely let each person know they are on their own for maintenance. -- \ “I've always wanted to be somebody, but I see now that I should | `\ have been more specific.” —Jane Wagner, via Lily Tomlin | _o__) | Ben Finney -- https://mail.python.org/mailman/listinfo/python-list
Re: What's the right way to abandon an open source package?
On 02/07/2014 00:18, Ben Finney wrote: Skip Montanaro s...@python.org writes: I've tried to find people to take it over, but so far unsuccessfully. The principle (laid out by ESR in “The Cathedral and the Bazaar”) is: When you lose interest in a program, your last duty to it is to hand it off to a competent successor. URL:http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s02.html Whether successful or not, I can testify that Skip has been conscientious in following this principle: he has been asking parties who have demonstrated interest and/or competence for some time now to take over maintenance of the ‘lockfile’ library. I continue to get bug reports, some from OS package maintainers or maintainers of applications which use lockfile. Lots of these people seem demanding of my time (which makes me even less interested in lockfile maintenance). I don't know of any good way to make those decrease, without some other contact point for the project becoming more prominent than yours. Is there a correct way to abandon the damn thing? You have, IMO, already put in sufficient public effort to give opportunity to potential maintainers. I would say that, in the case of the ‘lockfile’ library, you have already discharged your responsibilities under the above principle; and can politely let each person know they are on their own for maintenance. Very well put. Kudos to Skip and yourself :) -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- https://mail.python.org/mailman/listinfo/python-list
