No subject

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<tomeu at sugarlabs.org> wrote:
>> On Sat, Aug 22, 2009 at 16:03, Caroline Meeks<caroline at solutiongrove.com=
> wrote:
>>> hmm ok let me see if I understand.
>>> Teachers, parents etc. who may have a hard time understanding whether t=
hey
>>> are reporting a bug on Sugar, Sugar on a Stick or an activity should us=
e
>>> GetSatisfaction.
>>> SoaS Development team will use launch pad.
>>> People doing QA =A0should =A0put 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. =A0Is ther=
e an
>>> advantage to the LaunchPad questions section?
>>> I wonder if we are doing the right thing, is GetSatsfaction solving eno=
ugh
>>> problems for us to be worth it? =A0Its 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 <sebastian at 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 ou=
r
>>>> 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 ent=
er
>>>>> 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 scal=
ing.
>>>>>
>>>>>
>>>>> Thanks!
>>>>> Caroline
>>>>>
>>>>> On Thu, Aug 20, 2009 at 2:32 PM, Sebastian Dziallas <sebastian at when.c=
om
>>>>> <mailto:sebastian at when.com>> wrote:
>>>>>
>>>>> =A0 =A0Hi everybody,
>>>>>
>>>>> =A0 =A0with the imminent release of the SoaS v2 Beta in just ten days=
, I
>>>>> would
>>>>> =A0 =A0like to announce the switch to Launchpad as our bug tracker.
>>>>>
>>>>> =A0 =A0We have been evaluating an instance Luke Faraone set us up wit=
h lately
>>>>> =A0 =A0and are confident that it will fit our needs. The upcoming bet=
a
>>>>> release
>>>>> =A0 =A0is the first one intended to be used with this instance. More
>>>>> precisely,
>>>>> =A0 =A0we will use it to track bugs, as well as new features.
>>>>>
>>>>> =A0 =A0Note that this change only affects Sugar on a Stick, while the=
 core
>>>>> =A0 =A0Sugar bug tracker stays at dev.sugarlabs.org
>>>>> <http://dev.sugarlabs.org>.
>>>>>
>>>>> =A0 =A0You can access and explore it here: https://launchpad.net/soas
>>>>>
>>>>> =A0 =A0Thanks,
>>>>> =A0 =A0--Your SoaS Team
>>>>> =A0 =A0_______________________________________________
>>>>> =A0 =A0IAEP -- It's An Education Project (not a laptop project!)
>>>>> =A0 =A0IAEP at lists.sugarlabs.org <mailto:IAEP at lists.sugarlabs.org>
>>>>> =A0 =A0http://lists.sugarlabs.org/listinfo/iaep
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Caroline Meeks
>>>>> Solution Grove
>>>>> Caroline at SolutionGrove.com
>>>>>
>>>>> 617-500-3488 - Office
>>>>> 505-213-3268 - Fax
>>>
>>>
>>>
>>> --
>>> Caroline Meeks
>>> Solution Grove
>>> Caroline at SolutionGrove.com
>>>
>>> 617-500-3488 - Office
>>> 505-213-3268 - Fax
>>>
>>> _______________________________________________
>>> IAEP -- It's An Education Project (not a laptop project!)
>>> IAEP at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/iaep
>>>
>>
>>
>>
>> --
>> =ABSugar Labs is anyone who participates in improving and using Sugar.
>> What Sugar Labs does is determined by the participants.=BB - David
>> Farning
>> _______________________________________________
>> IAEP -- It's An Education Project (not a laptop project!)
>> IAEP at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/iaep
>>
>



--=20
=ABSugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.=BB - David
Farning