Re: [IAEP] (Please read) Re: Proposed Trac - Launchpad migration
On Mon, Nov 2, 2009 at 03:36, Gary C Martin g...@garycmartin.com wrote: On 1 Nov 2009, at 22:06, Chris Ball wrote: Dear Sugar folks, This mail didn't get any replies, but it's important to know whether people agree with it before going ahead. So, please understand that: * bugs.sugarlabs.org is moving from Trac to Launchpad. Ouch, oh my that's a bolt from the blue, thanks for emailing! I had no idea this was really on the cards, just assumed it was some background noise/chatter from a few folks who never liked using trac. Personally I've ignored Launchpad as I don't have time to burn on yet another 'lets try some other misc thingamajig' cycle. FWIW, will likely ignore Launchpad for a number of months more even if we migrated yesterday. * 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. * 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. +1 to have a precise blurb explaining explicitly why this is a good thing to do. All proposals should make explicit the resoning, risks, known controversies and any issues that the submitter anticipates are relevant to the discussion. Btw, I couldn't create an account in the testing instance, no emails seem to be sent. Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] (Please read) Re: Proposed Trac - Launchpad migration
On Sun, Nov 1, 2009 at 22:36, Gary C Martin g...@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 like. * 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 distributionshttps://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. Thanks, Luke Faraone http://luke.faraone.cc ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] (Please read) Re: Proposed Trac - Launchpad migration
I have no experience with Launchpad, but am often frustrated by the performance of SL Trac. At my office we switched from Trac to Redmine for internal project development, since Trac's development seems to have slowed to a crawl. Provided a high priority is placed on migrating bug numbers and keeping links to dev.sugarlabs.org working, I'm not opposed. I'll probably take Gary's approach and let the dust settle though. Now that 0.86 is out it's probably the best time to do this. Any chance OLPC would consider moving over too, so we could have true connections between OLPC and SL bugs? -Wade On Mon, Nov 2, 2009 at 8:55 AM, Luke Faraone l...@faraone.cc wrote: On Sun, Nov 1, 2009 at 22:36, Gary C Martin g...@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 like. * 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 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. 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 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. Thanks, Luke Faraone http://luke.faraone.cc ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] (Please read) Re: Proposed Trac - Launchpad migration
On Mon, Nov 2, 2009 at 09:19, Wade Brainerd wad...@gmail.com wrote: I have no experience with Launchpad, but am often frustrated by the performance of SL Trac. At my office we switched from Trac to Redmine for internal project development, since Trac's development seems to have slowed to a crawl. Provided a high priority is placed on migrating bug numbers and keeping links to dev.sugarlabs.org working, I'm not opposed. I'll probably take Gary's approach and let the dust settle though. Now that 0.86 is out it's probably the best time to do this. I've just confirmed with our contacts at Canonical that bug aliases will be created for all the old bugs, of the form sugarlabs- or sl-. Any chance OLPC would consider moving over too, so we could have true connections between OLPC and SL bugs? I don't think it's been discussed, but I'll forward it to the OLPC VIG. It is certainly more likely if the Sugar Labs migration works well. -- Luke Faraone http://luke.faraone.cc ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] (Please read) Re: Proposed Trac - Launchpad migration
Dear Sugar folks, This mail didn't get any replies, but it's important to know whether people agree with it before going ahead. So, please understand that: * bugs.sugarlabs.org is moving from Trac to Launchpad. * Existing bug data will be imported, but the bug numbers won't be the same. * 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. :) Thanks for reading, - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] (Please read) Re: Proposed Trac - Launchpad migration
On 1 Nov 2009, at 22:06, Chris Ball wrote: Dear Sugar folks, This mail didn't get any replies, but it's important to know whether people agree with it before going ahead. So, please understand that: * bugs.sugarlabs.org is moving from Trac to Launchpad. Ouch, oh my that's a bolt from the blue, thanks for emailing! I had no idea this was really on the cards, just assumed it was some background noise/chatter from a few folks who never liked using trac. Personally I've ignored Launchpad as I don't have time to burn on yet another 'lets try some other misc thingamajig' cycle. FWIW, will likely ignore Launchpad for a number of months more even if we migrated yesterday. * 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. * 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. Regards, --Gary ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
