An OLPC Development Model

[C. Scott Ananian]

Note that the meat of this proposal was *not* aimed at @laptop.org
employees, who I assume are savvy enough to get appropriate changes
upstream.  The real point here was to outline a devel strategy that
would work for 'out of core' changes made by external developers.  So
worrying about the "complexity and maintenance costs" is kinda beside
the point: these builds aren't being created or maintained by OLPC.
They are just a mechanism to create and test worthwhile changes to the
official build, and the merge window is a mechanism to get those
changes back into the official builds.
 --scott

-- 
 ( http://cscott.net/ )