From glyph at divmod.com Wed May 2 06:33:39 2007 From: glyph at divmod.com (glyph at divmod.com) Date: Wed, 02 May 2007 04:33:39 -0000 Subject: [pyOpenSSL] time for a fork Message-ID: <20070502043339.18153.1698484814.divmod.xquotient.214@joule.divmod.com> pyopenssl.sf.net has been moribund for almost 3 years now. Tickets like this: http://twistedmatrix.com/trac/ticket/2293 and this: http://allmydata.org/trac/tahoe/ticket/11 are starting to crop up on various projects which use pyopenssl. Personally I've discovered, investigated, worked around, and forgotten at least half a dozen pyopenssl bugs because it seems like there's no activity here. I really should have reported them, and I suspect that there are others in the same boat, not reporting bugs because they assume there's no one around to integrate patches and do a release. I have seen a few messages on this list in the last few years indicating that folks are starting to maintain some forks. Given that the maintainer seems to have moved on completely, if anyone is listening to this list, I think it's time for someone to take over maintenance, start a new website, and continue development / releases of pyopenssl somewhere else. Hopefully someone involved in such an effort could eventually get someone else to hand over the keys to the sf.net project so that the website here can be updated, but the important thing is to start pointing the community somewhere else for recent versions of pyopenssl. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at cridland.net Wed May 2 10:49:22 2007 From: dave at cridland.net (Dave Cridland) Date: Wed, 02 May 2007 09:49:22 +0100 Subject: [pyOpenSSL] time for a fork In-Reply-To: <20070502043339.18153.1698484814.divmod.xquotient.214@joule.divmod.com> References: <20070502043339.18153.1698484814.divmod.xquotient.214@joule.divmod.com> Message-ID: <4494.1178095762.629931@invsysm1> On Wed May 2 05:33:39 2007, glyph at divmod.com wrote: > Personally I've discovered, investigated, worked around, and > forgotten at least half a dozen pyopenssl bugs because it seems > like there's no activity here. I really should have reported them, > and I suspect that there are others in the same boat, not reporting > bugs because they assume there's no one around to integrate patches > and do a release. > > I've been collecting patchs and maintaining a fork, and I'm more than happy to continue. I've tried to be active in seeking out patches and applying them. (I'll look at the bugs you quote there, and see if I can sort them out). > I have seen a few messages on this list in the last few years > indicating that folks are starting to maintain some forks. Given > that the maintainer seems to have moved on completely, if anyone is > listening to this list, I think it's time for someone to take over > maintenance, start a new website, and continue development / > releases of pyopenssl somewhere else. > > I'm also happy to increase my activity in this area. I'd be happy to share the load on this. I've never done much with Python modules before, so help's always welcome. One key thing would be for a number of the key consumers of the package to "bless" one particular fork as the successor. In case you're wondering, while I'm happy if this happens to be mine, I'd be equally happy to follow consensus on this. > Hopefully someone involved in such an effort could eventually get > someone else to hand over the keys to the sf.net project so that > the website here can be updated, but the important thing is to > start pointing the community somewhere else for recent versions of > pyopenssl. That's the tricky bit - everyone comes to the SF website for PyOpenSSL, and finds it dead. This is why I feel the first step would be to enumerate the forks out there, choose one, and direct people consistently to there. Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade From glyph at divmod.com Thu May 3 00:00:59 2007 From: glyph at divmod.com (glyph at divmod.com) Date: Wed, 02 May 2007 22:00:59 -0000 Subject: [pyOpenSSL] time for a fork In-Reply-To: <4494.1178095762.629931@invsysm1> References: <20070502043339.18153.1698484814.divmod.xquotient.214@joule.divmod.com> <4494.1178095762.629931@invsysm1> Message-ID: <20070502220059.18153.981829895.divmod.xquotient.323@joule.divmod.com> On 08:49 am, dave at cridland.net wrote: >I've been collecting patchs and maintaining a fork, and I'm more than >happy to continue. I've tried to be active in seeking out patches and >applying them. (I'll look at the bugs you quote there, and see if I >can sort them out). I noticed the last few responses you sent to this list, and I hoped you'd say something like this. >One key thing would be for a number of the key consumers of the >package to "bless" one particular fork as the successor. In case >you're wondering, while I'm happy if this happens to be mine, I'd be >equally happy to follow consensus on this. Well, if I might flatter myself, Twisted is _the_ key consumer of the package ;-) and I (we) would not hesitate for a moment to "bless" your fork if you're willing to take up this responsibility. There are other parties we need to alert, though, especially the various operating system packagers for pyOpenSSL. Any of you listening? I suspect there will be some discussion of whether there should be a name- change or not, but I don't know if anyone will insist. It would, of course, make things easier if someone could figure out how to raise Martin! >That's the tricky bit - everyone comes to the SF website for >PyOpenSSL, and finds it dead. Twisted and Divmod also have an obscene amount of Google juice, so a few links on our websites should rapidly drive your site to the top of the rankings for "pyopenssl". >This is why I feel the first step would be to enumerate the forks out >there, choose one, and direct people consistently to there. I don't hear anyone else volunteering besides you :). -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at cridland.net Thu May 3 14:29:05 2007 From: dave at cridland.net (Dave Cridland) Date: Thu, 03 May 2007 13:29:05 +0100 Subject: [pyOpenSSL] time for a fork In-Reply-To: <20070502220059.18153.981829895.divmod.xquotient.323@joule.divmod.com> References: <20070502043339.18153.1698484814.divmod.xquotient.214@joule.divmod.com> <4494.1178095762.629931@invsysm1> <20070502220059.18153.981829895.divmod.xquotient.323@joule.divmod.com> Message-ID: <23594.1178195345.919192@invsysm1> On Wed May 2 23:00:59 2007, glyph at divmod.com wrote: > > On 08:49 am, dave at cridland.net wrote: >> One key thing would be for a number of the key consumers of the >> package to "bless" one particular fork as the successor. In case >> you're wondering, while I'm happy if this happens to be mine, I'd >> be >> equally happy to follow consensus on this. > > Well, if I might flatter myself, Twisted is _the_ key consumer of > the package ;-) and I (we) would not hesitate for a moment to > "bless" your fork if you're willing to take up this responsibility. > > Okay. I'll sort out some slightly more formalized structure to it in a week or so, unless anyone else wants to volunteer to maintain the fork. > There are other parties we need to alert, though, especially the > various operating system packagers for pyOpenSSL. Any of you > listening? I suspect there will be some discussion of whether > there should be a name- change or not, but I don't know if anyone > will insist. It would, of course, make things easier if someone > could figure out how to raise Martin! Yup, packagers are Most Wanted. Martin is/was the maintainer of the Debian package, too, so assuming Martin's vanished, we'll need someone entirely new there. >> That's the tricky bit - everyone comes to the SF website for >> PyOpenSSL, and finds it dead. > > Twisted and Divmod also have an obscene amount of Google juice, so > a few links on our websites should rapidly drive your site to the > top of the rankings for "pyopenssl". Right - as I say, I'll "do" a more formal site for it next week, such as its own Trac installation. (It's currently in a little corner of my site). Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade From elic at astllc.org Mon May 7 07:19:32 2007 From: elic at astllc.org (Eli Collins) Date: Mon, 07 May 2007 01:19:32 -0400 Subject: [pyOpenSSL] X509 Extension Bug Message-ID: <463EB6E4.9060501@astllc.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This is to Dave or whoever ends up maintaining the authoritative fork: I just wanted to draw your attention to a bug in the X509 Extension class which debian has applied a patch for, but seems to be missing from Dave's svn fork as of r709. The debian bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355947 The original report as well as the patch is here: http://sourceforge.net/tracker/index.php?func=detail&aid=1166109&group_id=31249&atid=401760 - -Eli Collins -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPrbkbY9ADrofCSwRAhD4AJwNGMYA1ygyIbJKVKgtee2Jj8CrfgCePYVi OaH5ejDFQJ0R3jZ0zNrS2R4= =Otu8 -----END PGP SIGNATURE-----