#3529 HIGH Future : CC license support in journal, as liblicense across the XO

Zarro Boogs per Child bugtracker at laptop.org
Wed May 28 22:04:41 EDT 2008


#3529: CC license support in journal, as liblicense across the XO
--------------------------+-------------------------------------------------
  Reporter:  paulproteus  |       Owner:  marco         
      Type:  enhancement  |      Status:  new           
  Priority:  high         |   Milestone:  Future Release
 Component:  sugar        |     Version:                
Resolution:               |    Keywords:                
  Verified:  0            |    Blocking:                
 Blockedby:               |  
--------------------------+-------------------------------------------------

Comment(by gnu):

 (As an aside, tomeu's complaint that those dern outsiders are not only
 posting bug reports and feature requests, but actually ADDING FEATURES and
 POSTING PATCHES to the Sugar code, is outrageous.

 In a typical free software project, if someone contributes new features
 with actual working code, the maintainer doesn't tell them they need to
 convince somebody in the bureacracy that their feature needs to be entered
 into the priority queue for contemplation among the committee of guardians
 of the public morals.  A good maintainer either applies the patch to the
 master sources (verbatim, or with minor or major rework for quality and
 style); gives the contributor access to apply the patch themselves, based
 on the high quality of their work; or tells the contributor to rework the
 patch because of specific complaints about it (e.g. quality, style, lack
 of documentation, lack of generality, doesn't patch cleanly into current
 sources, it introduces a bug, ...).

 Sugar is never going to get anywhere with three guys working on it, if
 they refuse to include contributions from outside.

 I don't want to complain about tomeu in general, he's been very helpful
 many times.  Perhaps he had a bad day two months ago.  But reactions like
 this one are why people say that OLPC is insular and unhelpful.  The
 standard OLPC response to a bug or missing feature report is "we won't get
 around to it ourselves, but patches would be welcomed".  So when patches
 DO show up, please DO welcome them.)

-- 
Ticket URL: <http://dev.laptop.org/ticket/3529#comment:20>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list