Changes in WidelandsHosting
Revision Differences of Revision 4
# Widelands moving away from Sourceforge.net ¶This page will help deciding on a new Hoster for the development of Widelands. ¶
¶
If you want to know why, please check the forum at http://wl.widelands.org/forum/topic/350/?page=1 ¶
¶
[TOC] ¶
¶
¶
¶
## Available Hosters ¶
¶
### Must-Have ¶
¶
* Project page ¶
* Wiki ¶
* Bugtracker ¶
* SVN ¶
* Lots of
* Not hosted in USA ¶
* Free ¶
* Download page (for package distribution) ¶
¶
¶
Hoster | Acceptable | Webpage | Forum | Wiki | Bugtracker | SVN | Maillist | Space | Country | Free | Downloads ¶
------- | -------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- ¶
Sourceforge.net |
Launchpad |
Gitorious |
¶
### Nice-To-Have ¶
¶
* Git ¶
* Translation ¶
* Import of complete SVN repository (without losing history) ¶
* run by a free organisation ¶
* hosted in Europe ¶
* No ads ¶
¶
Only hosters who are "Acceptable" in the table above ¶
¶
Hoster | Translation | Git
------- | -------- | ----------- | ----------- | ----------- | ----------- | ----------- ¶
Sourceforge.net | No | Yes | ? | ? | ? | ? ¶
Launchpad | Yes | No | ? | ? | ? | ? ¶
Gitorious | Yes |
¶
## !SirVer's toughts on a launchpad scenario. ¶
¶
I am pro for a move to launchpad mainly for the following reasons ¶
¶
* open source itself - https://launchpad.net/launchpad-project ¶
* many developers behind it ¶
* good support (as far as I needed it which was some times) ¶
* excellent bug tracker ¶
** zero page reload for bug modification ¶
** good comments for bugs (including email discussion) ¶
** a python API to automatically modify bugs ¶
** import of sf.net bugs is (theoretically) possible ¶
* good coding support ¶
** bzr (I prefer git, but bzr is much better then SVN). No wars here. ¶
** that also means many branches with cheap merging ¶
** per user branches means people can contribute without commit rights and without patches needed ¶
* Web based translation that can get automerged into the repository ¶
¶
It has some down sides. Please put more if you are aware of more: ¶
¶
* I have no Idea if mailinglists are supported. ¶
¶
### Roadmap to move ¶
¶
This is my suggestion for a Roadmap to move to Launchpad. ¶
¶
1. Moving source code ¶
I will move svn/trunk and svn/cmake into two branches on launchpad and make the official in some sense. The SVN on sf.net will then be completely disabled overnight (It will stay as read only documentation of our long, long history). We will use our tagging history in this move, which is unfortunate but can't be changed. We can restore it in branches on launchpad if we want to later on. ¶
2. Moving bugs. This will mean that first the bug tracker on sf.net will be disabled, then I export and XML file an hand it to the launchpad staff to import it for us. This means for a week or so, we won't be able to track bugs. ¶
3. Moving widelands-public. If Launchpad offers us Mailinglists, we will move them after everything is stable and set. This is so that our main communication channel stays open in case anything goes wrong. ¶
¶
So to sum up: ¶
¶
#### Phase 1 ¶
¶
Code in bzr branches on launchpad. Bugs & Mailinglists on Sf.net ¶
¶
#### Phase 2a ¶
¶
Bug trackers disabled. Export of sf.net bug trackers get imported to launchpad. ¶
¶
#### Phase 2b ¶
¶
Only Mailinglists on sf.net. ¶
¶
#### Phase 3 ¶
¶
widelands-public get's moved to launchpad. Widelands-annouce will stay around because we only announce releases over it. ¶
¶
¶
¶
¶
¶
¶
### links ¶
* [thiet ke web](http://www.url.vn), [dich vu seo](http://www.seo.url.vn), [Dang ky ten mien](http://www.tenmien.url.vn), [thoi trang han quoc](http://www.changmishop.com), [my pham Ohui](http://ohuihanquoc.vn)