Re: [pyOpenSSL] time for a fork

[Dave C. <da...@cr...>]

On Wed May  2 05:33:39 2007, gl...@di... 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:da...@cr... - xmpp:dw...@ja...
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade