[IAEP] sugar on standard laptops

[Martin Langhoff]

On Wed, Jun 11, 2008 at 9:57 AM, Ivan Krstić
<krstic at solarsail.hcs.harvard.edu> wrote:
> With the SugarLabs/OLPC split, OLPC becomes a distribution vendor like Red
> Hat or Canonical. It makes complete sense to split out upstream issues for
> SugarLabs-developed software to a SugarLabs-operated bug tracker, and have a
> bugtracker at OLPC for tracking problems in OLPC's own distributions
> (builds).

Distributions have separate bugtrackers only for packages where they
are not the upstream themselves.

Separate bugtrackers adds a lot of manual management around data sync
- a real pain with not much gain when the team is the same. For
example Canonical is smart enough to use launchpad to track Bazaar's
bugs. They fund Bazaar so their are their own upstream. And they sure
know about the workload of cross-tracker bug handling (Malone tries
hard to make it easier).

If we ever get to a point where the majority of the core Sugar
development team is not related to OLPC, and there are good reasons to
split it off, it might be a good idea. Right now, it only adds a
pointless distraction, and forces additional non-productive work on
people that don't need it.

Let's keep things simple and streamlined. Life is too short.

cheers,


m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff