Vision proposal 2016: Difference between revisions

Line 46:

* to fully staff all boards, offices, and committees;

* to make XO-4s—the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop—available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;

* to ~~provide~~ a ~~step-by-step guide on~~ the ~~homepage website to setting up a 2016 vintage deployment device&mdash~~;~~one that can be purchased in quantities of 30+ for under $100 each—that covers where~~ to ~~buy them, how install Sugar on all of them at~~ the ~~time of deployment;~~

* to make a release event for the 0.110 release;

* to find and develop as a reference a new laptop for kids with~~...~~

** to track the event with https://github.com/OpenTechStrategies/streetcrm

* to find and develop as a reference a new laptop for kids with;

** required attributes

*** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)

Line 58:

Line 59:

** to make the github.com/sugarlabs organization membership a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];

* to clean up all Sugar Labs websites, starting with the wiki and issue tracker;

** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device—one that can be purchased in quantities of 30+ for under $100 each—that covers where to buy them, how install Sugar on all of them at the time of deployment;

** to find out and document on the site why past deployments moved away from Sugar Desktop;

** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);

@@ Line 46: / Line 46: @@
 * to fully staff all boards, offices, and committees;
 * to make XO-4s&mdash;the machine we aspired to build at OLPC in 2006 is available as the XO-4 laptop&mdash;available from us pre-installed with the 2016 release of Sugar individually or in batches of 20+ with 1+ school server units, so any developer can get one conveniently and any classroom-sized group anywhere can become a Local Lab with almost "1 click" like convenience if they have $X to put down;
-* to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device&mdash;one that can be purchased in quantities of 30+ for under $100 each&mdash;that covers where to buy them, how install Sugar on all of them at the time of deployment;
+* to make a release event for the 0.110 release;
-* to find and develop as a reference a new laptop for kids with...
+** to track the event with https://github.com/OpenTechStrategies/streetcrm
+* to find and develop as a reference a new laptop for kids with;
 ** required attributes
 *** a 10" screen and larger keyboard than the XO, so adults can use it too (similar to the 10" macbook pro from around 2004, or many 10" chromebooks today)
@@ Line 58: / Line 59: @@
 ** to make the github.com/sugarlabs organization membership a 'badge of honor' similar to [http://lists.sugarlabs.org/archive/iaep/2011-July/013736.html the old certificates];
 * to clean up all Sugar Labs websites, starting with the wiki and issue tracker;
+** to provide a step-by-step guide on the homepage website to setting up a 2016 vintage deployment device&mdash;one that can be purchased in quantities of 30+ for under $100 each&mdash;that covers where to buy them, how install Sugar on all of them at the time of deployment;
 ** to find out and document on the site why past deployments moved away from Sugar Desktop;
 ** to find out and document on the site why potential deployments did not choose to adopt Sugar Desktop ([http://lists.sugarlabs.org/archive/iaep/2015-March/017279.html reference]);