I added another quick item to chat about M2Crypto. Here's a quick overview pre-meeting so that I don't have to type all of this in channel:
We're using M2Cryto in the project, and it seems like we like it. There are two issues: a) There is a bug in its setup.py which makes it harder to install from pypi. This is actually easy to workaround - we have both a patch to M2Crypto that fixes it as well as a workaround for OpenStack. HOWEVER - trying to get the patch landed has led to the discovery that: b) M2Crypto is unmaintained. Its source code repo has received no commits in over a year and there are many outstanding bugs. Paul McMillan and I reached out to the current maintainer several weeks ago and have received no response. The reason I'm bringing this up here is that one of the possible solutions would be to take over maintenance of M2Crypto directly. I'm betting we could get added as uploaders to the PyPI project (they do have processes for taking over abandoned projects), and we could easily add it to the openstack-dev org on github and to gerrit/jenkins. Physically that should be easy - the question is whether or not it's something we'd like to get involved with (since we have the infrastructure) Other options would be to find someone who wants to take over maintenance but to not involve any of our dev resources directly on that, or to stop using it, I believe. My personal vote is to take it over and add it to openstack-dev. I think that it's actually _MOSTLY_ in good shape, so just getting outstanding patches applied and a new release cut will help both us and fedora and ubuntu. I'm happy to be part of the group of people to take care of it and to put some of the resources of my team towards it. (obviously if we decide that we don't want the project to have a role but ask a person to, I can still put resources behind it) There is a related more abstract question of how do we deal with the use of libraries which have upstreams who are unresponsive... but I don't think we need to solve the abstract question at the moment as much as we need to just figure out this one. Thanks! Monty On 01/17/2012 07:36 AM, Jonathan Bryce wrote: > I added them to the wiki. If anyone thinks of anything before tomorrow feel > free to go ahead and add it as well. See you tomorrow 2000UTC/2:00PMCST. > > On Jan 15, 2012, at 9:42 PM, Joshua McKenty wrote: > >> Two quick items: >> >> What (if anything) should we be doing as the PPB to move the >> foundation forward? Do we have an obvious role? >> >> Sanity check on Essex and the proposed release date - anyone else feel >> like giving ourselves an extra 30 days on this one (bug fixes only) >> might not be a bad call? The last thing we need is another Diablo, and >> if we're going to move the date, now would be the time. >> >> Sent from my iPhone >> >> On 2012-01-15, at 5:17 PM, Jonathan Bryce <[email protected]> wrote: >> >>> Nothing on the agenda at this point. If you've got something you'd like to >>> add, put it on the wiki or send an email before 2000 UTC tomorrow. Thanks, >>> >>> Jonathan. >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack-poc >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openstack-poc >>> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack-poc > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack-poc > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
