#6598 HIGH Update.: Activities for base build

[Zarro Boogs per Child]

#6598: Activities for base build
-----------------------+----------------------------------------------------
  Reporter:  kimquirk  |       Owner:  dgilmore
      Type:  defect    |      Status:  new     
  Priority:  high      |   Milestone:  Update.1
 Component:  distro    |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |    Blocking:          
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by walter):

 let's at least start the conversation form where we left off last summer:

 Core activities: There has been a discussion on the devel list about the
 criteria for inclusion of core activities on the laptop. We'd like to
 broaden the discussion. Some proposed "Criteria for Inclusion":

    1. Epistemological impact—to what degree does this activity positively
 impact learning? (This is of course the most important criteria.)
    2. Fun—is it fun? engaging?
    3. Quality—is the activity sufficiently robust in its implementation
 that it will not compromise the integrity or supportability of the system?
 Is the overall quality of the implementation adequate to meet our
 standards? Can the community be engaged in the process of testing and
 "certifying" and maintaining the activity?
    4. Sugarized—to what extent has the activity been integrated into
 Sugar, including UI, Journal, security, internationalization, etc.? Does
 the activity require the folding in of additional libraries and resources?
 (This has impact on robustness—positive and negative—support, bloat, and
 the overall usability, aesthetics, and perception of quality of the
 machine.)
    5. FOSS—is the activity and all of its dependencies free and open?
    6. Extensible—is the activity something the community can extend? Does
 it span multiple needs? (And does it have—or the potential of having—an
 upstream community of support?)
    7. Uniqueness—does the activity add a unique feature to the core?
    8. Expectations—does the activity meet the expectations of (children,
 teachers, parents, G1G1 audience, etc.)?
    9. Discoverable—is the core activity discoverable? (This is not to say
 that it shouldn't be hard work to fully exploit the power of an activity,
 but it should have a low barrier to entry.)

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