[IAEP] (Please read) Re: Proposed Trac - > Launchpad migration

Luke Faraone luke at faraone.cc
Mon Nov 2 08:55:08 EST 2009

On Sun, Nov 1, 2009 at 22:36, Gary C Martin <gary at garycmartin.com> wrote:

>  * Existing bug data will be imported, but the bug numbers won't be the
>>  same.
> So the git commit messages referencing trac bug tickets will be future
> information garbage, oh joy.

As stated, there will be both a conversion table and a redirect service
available for the considerable future. We already have fragmentation between
SL bugs and OLPC bugs. Launchpad will allow us to keep our old bug numbers
Is there anything else that would make this work better for everyone?

An example of the redirection scheme:
https://launchpad.net/sugar/+bug/slbugs1534 points to a page titled "Bug
#460049 (slbugs1534)". We can change the nickname prefix to whatever we'd

>  * It will be hosted by Canonical externally, rather than by SL as Trac
>>  currently is.
>> If any of these are not to your liking, the time to speak up is now,
>> before it all happens.  :)
> Not to my liking, but if some really smart/committed folks are willing to
> do the work, have it well tested, say this is really worth the pain, and
> don't mind some folks ignoring the move for a few months... Though, I would
> first really love to see a clear explanation of why this is a good idea, and
> how the move benefits us.

To quote Bernie, our system administrator and current manager of Sugar Labs'
Trac instance:

bernie: my #1 reason for switching is that our trac instance is a wreck and
> nobody wants to maintain it.
> bernie: me less than anyone else. it's an awful application to maintain...
> especially now that it is riddled by spammers

Switching to Launchpad would free up admin time to work on improving other
services, such as ASLO <http://activities.sugarlabs.org> and the wiki.
Launchpad is already many times faster than the current Sugar Labs bug
tracker, and Canonical has committed to add capacity as the service grows.

In addition, Launchpad allows developers to manipulate bugs by email (a la
bugs.debian.org), permitting developers to choose their own workflow.

Launchpad also is better suited for multi-project collaboration, both within
Sugarlabs and with other distributions<https://edge.launchpad.net/+tour/bugs>.
We can easily track the status of bugs that affect both upstream Sugar and
the Sugar packages in, say, Ubuntu, Fedora, Debian, and Gentoo, all from the
same page.

We've been testing <https://launchpad.net/soas> Launchpad with the Sugar on
a Stick project for a few months now, and it's been working pretty well.

Finally, we would be able to migrate away from Launchpad at any time.

Luke Faraone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/iaep/attachments/20091102/1f4f8c07/attachment.htm 

More information about the IAEP mailing list