Moving to github would involve migration a portion of the lp:divmod.org source tree, ideally without losing history, and then somehow reconciling all the branches there, as well as somehow moving all the branches that exist _here_, both of the old mis-imported pyflakes bzr mirror of the now-defunct SVN repository and the proper branches of the lp:divmod.org repository for pyflakes features.
This is a lot of work and there aren't a lot of people who can dedicate time to working on Divmod stuff. For the time being I think it would be a better use of time to educate the github contributors about the relative equivalence between github pull requests and launchpad merge proposals; the tools are really not all that different. If the people interested in contributing code can't even be bothered to learn to type "bzr lp-submit" then I suspect the code involved can't be of high enough quality to bother doing all the migration work for :). -- You received this bug notification because you are a member of Divmod- dev, which is the registrant for Pyflakes. https://bugs.launchpad.net/bugs/954470 Title: moving to github Status in Pyflakes: New Bug description: Would you guys be interested in moving to github? There is quite a lot of development there for pyflakes and it would make more sense to continue there (github is a much better place than launchpad for collaboration, IMHO). https://github.com/kevinw/pyflakes/pulls e.g. https://github.com/kevinw/pyflakes/pull/22 https://github.com/kevinw/pyflakes/pull/23 What do you think? To manage notifications about this bug go to: https://bugs.launchpad.net/pyflakes/+bug/954470/+subscriptions -- Mailing list: https://launchpad.net/~divmod-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~divmod-dev More help : https://help.launchpad.net/ListHelp
