> Thanks for the participation in the discussion around moving away from > Launchpad. A lot of useful information was discovered and added to the > document that makes the decision much less clear cut. Two biggies that let me > think right now that we should stay on Launchpad for a bit longer is that > they are working on git integration (makes the bzr deprecation moot) and that > GitHub does not allow to attach arbitrary files to bug reports (savegames? > log output?).
The only advantage I see in moving right now would be running our tests with Travis. If we can make our tests run with Launchpad, there is no reason to move IMO, especially since Git might be coming. Launchpad has also just finished a server upgrade, so timeouts during branching shouldn't happen anymore. > Posting this message to two mailinglist also made me think that we really > should consolidate into one mailing list - and I suggest opening a Google > Groups for widelands development and deprecating widelands-public@sourceforge > and widelands-dev@launchpad. What do you think? I didn't even know that the Sourceforge list existed. Widelands moved away from Sourceforge a long time ago, so retiring that list is definitely a good idea. What would be the advantage of Google Groups, what features would we be actually using? Or in other words, except for posting the occasional document link to 2 mailing lists (which will be just 1 in the future), what would we get out of it? I don't use Google except for Widelands, hence I'm asking ;) > There are still some TODOs in the document that I need help with and some > sections that others need to fill in. Could you all have another quick look > over the doc and contribute information and comments as you can? > > It is here: > http://tinyurl.com/WlMoveToGithub > > Thanks, > Holger _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
