Topic: Move Website to GitHub
GunChleoc![]() Topic Opener |
Posted at: 2019-09-04, 17:04
I am moving the issues to GitHub right now. The second step will be ti import the branches. I am currently getting an error, so I'll probably move those branch by branch. Please have a look at the list at https://code.launchpad.net/widelands-website and mark any of your branches that you will not be working on any more as "abandoned". Busy indexing nil values ![]() ![]() |
GunChleoc![]() Topic Opener |
Posted at: 2019-09-04, 17:43
Issues have been moved to https://github.com/widelands/widelands-website/issues, but I haven't double-checked them yet. We will definitely need to clean up the labels. We should also link up the new bugs from the old bugs in Launchpad, i can take care of that. Test export of the branches ist at https://github.com/gunchleoc/widelands-website - This ran through pretty fast after I found the configuration problem that I had with the tool, so I'll do it again once the branches have been cleaned up and I get the OK from the currently active website developers so it won't interfere with their work. Edited: 2019-09-06, 08:26
Busy indexing nil values ![]() ![]() |
kaputtnik![]() |
Posted at: 2019-09-04, 19:12
Abandoned all of my old branches. Trimardio should check his branches. Branches from any other users couldn't be changed, and they are very old and shouldn't be moved also. Dammn, now i have to struggle wit the Github workflow .... Any idea how to exchange bazaar with github on the server? Do we need to set up the whole website again? Fight simulator for Widelands: ![]() ![]() |
GunChleoc![]() Topic Opener |
Posted at: 2019-09-04, 22:59
I have started a documentation page on the wiki https://www.widelands.org/wiki/GitPrimer/ - everybody is welcome to edit it and add more info. The GitHub help is also pretty useful. @Trimardio tell me when is a good time to do the move, so you won't end up with local changes on your machine that won't make it over. Edited: 2019-09-04, 23:04
Busy indexing nil values ![]() ![]() |
GunChleoc![]() Topic Opener |
Posted at: 2019-09-06, 16:03
We won't have the separate priority settings that we used to have on Launchpad, so I have created a milestone that can be used to prioritize issues. I have also cleaned up the labels. Shall we create 1 label per Django module? Busy indexing nil values ![]() ![]() |
WorldSavior![]() |
Posted at: 2019-09-06, 19:44
Hm... And what again is the motivation for moving to this Microsoft platform? Wanted to save the world, then I got widetracked ![]() ![]() |
trimard![]() |
Posted at: 2019-09-06, 20:54
Microsoft just bought it. But the core of the website was developped by good people don't worry I see several avantages (though I never participated in the discussion about it)
![]() ![]() |
Tino |
Posted at: 2019-09-07, 07:03
Launchpad/Bazaar has not been updated for years. There is not even a recent bzr client software for Windows OS... And don't mix GIT and GitHub.com. GIT is definitely better than bzr, and while there are many alternatives to GitHub incl. Self hosting, GitHub is just the most used, common known Git hosting platform. Great work, Gun! ![]() ![]() |
GunChleoc![]() Topic Opener |
Posted at: 2019-09-07, 08:08
We looked into alternative hosting for Git, but GitHub is the only site that inegrates with Travis. So, we have already been depending on GitHUb for a few years now anyway. At the moment, SirVer has a bot running on a Raspi that pushes branches to GitHub for us, but it's by necassity a very dirty hack and therefore prone to crash. I am fond of Bazaar too, but as Tino said, their maintenance has seriously fallen behind. If the current owners if the GitHub site should cause us any problems in the future, there is always the option to rethink our choice and move again then. Widelands has been moved before, by the way (off SourceForge because we had an Iranian contributor who was not allowed to participate due to USA's empargo on encryption). BTW there is also an initiative by FreeGameDev for FLOSS Git hosting, but Widelands is far too big for them. Edited: 2019-09-07, 08:08
Busy indexing nil values ![]() ![]() |
trimard![]() |
Posted at: 2019-09-07, 17:59
Can we already add new issues and push in the github interface? We need to change bzrignore to gitignore notably. It's literally the same file except maybe a mention of pycache which I don't know why wasn't in the bzrignore ![]() ![]() |