#3918 HIGH Never A: Design Process for Making Content Available on XOs.

[Zarro Boogs per Child]

#3918: Design Process for Making Content Available on XOs.
---------------------+------------------------------------------------------
  Reporter:  mstone  |       Owner:  jg              
      Type:  task    |      Status:  new             
  Priority:  high    |   Milestone:  Never Assigned  
 Component:  distro  |     Version:                  
Resolution:          |    Keywords:  library, content
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by sj):

 This seems to be confusing two related things.  We have a current way to
 get bundles (at least activity bundles and library bundles) onto the
 laptops.  We don't have a very good way of handling package management,
 and while we need much less package management than a full-fledged
 packaging system provides, we do need core features (simple dependencies,
 maintainers, &c).

 I would split this into two tickets:
  1) we need a package management system -- as a way of finding and
 handling bundles
  2) we need to design how we packaging browsable content and interpretable
 data; our manager will need to handle more than just traditional software
 packages.

 and perhaps a third ticket about how to design the community process
 around managing any core flags used by the package manager ('stable' or
 'core', for instance)

 This should be implemented by extending an existing package manager.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3918#comment:1>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system