| Version 4 (modified by , 16 years ago) ( diff ) |
|---|
Why replace SourceForge with Launchpad?
http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities
http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html
Sourceforge was great in it's day, but hasn't kept up with the competition.
Beyond needing a host which supports Bzr, there are several good reasons for switching:
The bug tracker has been a particular source of frustration - it has poor facilities for targetting bugs at specific milestones.
This is related to there being no support for roadmaps (the Wiki is currently used for this, but it's not integrated)
The mailing lists have also had reliability problems & the web archive is a very poor access method.
Launchpad is designed to foster a more collaborative development process, which is exactly what we need.
It is designed for a world of Distributed Version Control systems & less central hierarchy.
It supports links to external systems (such as Sourceforge & Trac).
The User-focussed 'Answers' section & FAQ are potentially very useful...although right now they seem better as inspiration for how to structure our Wiki
The 'Translations' section could potentially replace Pootle?
It's main limitation is the lack of an in-built Wiki (the BluePrints/Answers/FAQ can kind-of be used to work around this).
We therefore use Trac more than LaunchPad (using the Bzr plugin).
- Can push LP bugs to Trac: https://help.launchpad.net/Bugs/TracPlugin
Launchpad is also used by Web2Py:
