On Sun, Aug 23, 2009 at 11:11, Rafael Enrique Ortiz Guerrero<dir...@gmail.com> wrote: > i'm not sure if we have to split soas and sugar bug trackers yet, if > is usability and a better performance we are looking, and if lauchpad > is better for that purpose we can translate all our bug infrastructure > there.. IMHO we shouldn't split bug trackers between sugar and it's > projects.
>From my personal POV, the problem is that when I have to triage Sugar bugs, I have to wade through hundreds of non-Sugar bugs. And when people start using Sugar on other platforms than OLPC and SoaS, I don't really want to have to wade through these non-Sugar bugs for each of those platforms (broadcom or poulsbo driver support, for example). If each of our (sub)projects perform well at their core competences, each of them will be able to attract new contributos to deal with the overhead of separated process and infrastructure. But if we keep focusing responsibilities on the same small set of core people, we won't perform well and our contributor base won't expand. Regards, Tomeu > > > Rafael Ortiz > > > > On Sun, Aug 23, 2009 at 2:06 AM, Tomeu Vizoso<to...@sugarlabs.org> wrote: >> On Sat, Aug 22, 2009 at 16:03, Caroline Meeks<carol...@solutiongrove.com> >> wrote: >>> hmm ok let me see if I understand. >>> Teachers, parents etc. who may have a hard time understanding whether they >>> are reporting a bug on Sugar, Sugar on a Stick or an activity should use >>> GetSatisfaction. >>> SoaS Development team will use launch pad. >>> People doing QA should put bugs into dev unless its a sugar on a stick >>> only issue. >> >> Are we sure about this? Some bugs won't be clear where do they really >> belong until a developer looks at it, and SoaS people may also like >> tracking sugar-only bugs on their bugtracker. For example, Ubuntu >> tracks Debian bugs on their bugtracker and Fedora tracks GNOME, X, >> etc. >> >> Also, normally a bug in a downstream is not closed when upstream fixes >> it, but when it gets into a release on that downstream. Which is the >> biggest reason for splitting bug trackers, IMO. >> >> Regards, >> >> Tomeu >> >>> Is that a correct restatement of what you want? >>> I wonder if all questions should just go to GetSatisfaction. Is there an >>> advantage to the LaunchPad questions section? >>> I wonder if we are doing the right thing, is GetSatsfaction solving enough >>> problems for us to be worth it? Its nice but it is yet another site...Does >>> Launchpad have a Spanish UI available? >>> >>> On Sat, Aug 22, 2009 at 9:51 AM, Sebastian Dziallas <sebast...@when.com> >>> wrote: >>>> >>>> Hi Caroline, >>>> >>>> here's what I discussed with Luke over IRC. >>>> >>>> * Questions related to SoaS: Launchpad Answers Section >>>> * Issues encountered on SoaS (stressing "issues" here): Launchpad Bug >>>> Tracker (we can link a bug also to reports at other bug trackers!) >>>> * Feature Requests which target Sugar directly should go to >>>> dev.sugarlabs.org. >>>> >>>> Following this strategy, GetSatisfaction would be more intended for >>>> general end-user support, meaning people who run Sugar on >>>> no-matter-which-platform-or-distro. Launchpad should be SoaS-specific. >>>> >>>> I'll take some time today to put bugs into Launchpad and to migrate our >>>> feature list for v2 over there, too. >>>> >>>> --Sebastian >>>> >>>> Caroline Meeks wrote: >>>>> >>>>> Where do you want teachers interacting with you? Do you want me, and >>>>> people I give clues to, to put questions into Launchpad or >>>>> GetSatisfaction? >>>>> >>>>> Do you want me >>>>> and others to try to guess if a bug is SoaS or Sugar or should we enter >>>>> into Launchpad >>>>> if we are using SoaS and let you decide to move it? >>>>> >>>>> What about activity related issues? >>>>> >>>>> What about activity related issues on SoaS, like an activity not scaling. >>>>> >>>>> >>>>> Thanks! >>>>> Caroline >>>>> >>>>> On Thu, Aug 20, 2009 at 2:32 PM, Sebastian Dziallas <sebast...@when.com >>>>> <mailto:sebast...@when.com>> wrote: >>>>> >>>>> Hi everybody, >>>>> >>>>> with the imminent release of the SoaS v2 Beta in just ten days, I >>>>> would >>>>> like to announce the switch to Launchpad as our bug tracker. >>>>> >>>>> We have been evaluating an instance Luke Faraone set us up with lately >>>>> and are confident that it will fit our needs. The upcoming beta >>>>> release >>>>> is the first one intended to be used with this instance. More >>>>> precisely, >>>>> we will use it to track bugs, as well as new features. >>>>> >>>>> Note that this change only affects Sugar on a Stick, while the core >>>>> Sugar bug tracker stays at dev.sugarlabs.org >>>>> <http://dev.sugarlabs.org>. >>>>> >>>>> You can access and explore it here: https://launchpad.net/soas >>>>> >>>>> Thanks, >>>>> --Your SoaS Team >>>>> _______________________________________________ >>>>> IAEP -- It's An Education Project (not a laptop project!) >>>>> i...@lists.sugarlabs.org <mailto:IAEP@lists.sugarlabs.org> >>>>> http://lists.sugarlabs.org/listinfo/iaep >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Caroline Meeks >>>>> Solution Grove >>>>> carol...@solutiongrove.com >>>>> >>>>> 617-500-3488 - Office >>>>> 505-213-3268 - Fax >>> >>> >>> >>> -- >>> Caroline Meeks >>> Solution Grove >>> carol...@solutiongrove.com >>> >>> 617-500-3488 - Office >>> 505-213-3268 - Fax >>> >>> _______________________________________________ >>> IAEP -- It's An Education Project (not a laptop project!) >>> IAEP@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/iaep >>> >> >> >> >> -- >> «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 >> > -- «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
