| 5 | Sourceforge was great in it's day, but hasn't kept up with the competition. |
| 6 | |
| 7 | Beyond needing a host which supports Bzr, there are several good reasons for switching: |
| 8 | |
| 9 | The bug tracker has been a particular source of frustration - it has poor facilities for targetting bugs at specific milestones.[[BR]] |
| 10 | This is related to there being no support for roadmaps (the Wiki is currently used for this, but it's not integrated) |
| 11 | |
| 12 | The mailing lists have also had reliability problems & the web archive is a very poor access method. |
| 13 | |
| 14 | Launchpad is designed to foster a more collaborative development process, which is exactly what we need.[[BR]] |
| 15 | It is designed for a world of Distributed Version Control systems & less central hierarchy.[[BR]] |
| 16 | It supports links to external systems (such as Sourceforge & Trac). |
| 17 | |
| 18 | The User-focussed 'Answers' section & FAQ are potentially very useful.[[BR]] |
| 19 | The 'Translations' section could potentially replace Pootle? |
| 20 | |
| 21 | 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). |
| 22 | |
| 23 | We therefore use Trac more than !LaunchPad (using the Bzr plugin). |
| 24 | * Can push LP bugs to Trac: https://help.launchpad.net/Bugs/TracPlugin |
| 25 | |
| 26 | Launchpad is also used by Web2Py: |
| 27 | * https://launchpad.net/web2py |