<div>Nice carbohydrate lesson as well!</div>
<div> </div>
<div> --Frederick Grose<br><br></div>
<div class="gmail_quote">On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz <<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote:<br>
<blockquote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid" class="gmail_quote">-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>I think Sugar has a naming problem. There are a lot of different digital<br>
objects being produced by this project, and referring to all of them as<br>Sugar is becoming increasingly confusing. For example, the discussion<br>about "Sugar on Windows" has been all but incomprehensible, because each<br>
author means something entirely different by the term "Sugar". Similarly,<br>the recent proposals for "inclusion in Sugar" are extremely confusing,<br>since these components will not be required to run Sugar.<br>
<br>To resolve this, I am going to attempt to list a number of important,<br>distinct digital objects that this work has produced. I will also<br>introduce cutesy codenames. I hope that the Sugar developers will adopt a<br>
clear set of distinct names, and I do not care if they choose these names<br>or other names.<br><br>Component: The abstract design of the interface<br>Codename: Sweet (the taste of sugar)<br>Description: "Sweet" is the abstract design of the interface's appearance<br>
and behavior, independent of any code actually implementing this style.<br>The mockups at <a href="http://wiki.laptop.org/go/Designs" target="_blank">http://wiki.laptop.org/go/Designs</a> represent this<br>component's second major release, or perhaps 2.0-alpha.<br>
<br>Component: The base Sugar environment<br>Codename: Glucose (the fundamental, simple sugar used by all life forms)<br>Description: Glucose is the minimal system that must be added to a<br>standard Linux distribution in order to enable Activities to run. This<br>
includes all the python code and graphics files that implement the shell,<br>as well as the Journal. Glucose's dependencies may include xorg-server,<br>xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br>
marked optional by distributions. Glucose does not include any Activities<br>except those like the Journal that are non-optional.<br><br>Component: A set of demonstration activities<br>Codename: Fructose (the main sugar in fruit, which is how we're supposed<br>
to get our sugar.)<br>Description: The Sugar developers will need some example set of<br>activities with which to demonstrate Sugar. This set is Fructose. The<br>packages in Fructose should be selected to make the resulting environment<br>
as impressive as possible for a potential client or user. Packages should<br>therefore be stable, polished, and exercise the widest possible range of<br>features. Fructose may also serve as an example for people constructing<br>
their own Activity sets.<br><br>Component: The interface, plus a set of demonstration activities<br>Codename: Sucrose ("table sugar", the kind you buy in the store. It<br>consists of glucose and fructose, combined.)<br>
Description: Sucrose consists of both Glucose and Fructose. It therefore<br>represents a complete example Sugar environment, ready to be installed<br>through a package manager. The purpose of Sucrose is so that prospective<br>
deployers can install the "sugar-sucrose" package, and immediately say<br>"Wow! Look at all the cool capabilities that this system has!".<br><br>Component: The base Linux distribution being used by Sugar<br>
Codename: Ribose (the sugar used by all lifeforms to control their<br>hardware, in the form of RNA. It's important, but not sweet.)<br>Description: Ribose is the set of hardware-centric software components<br>that have been developed throughout this project. It includes the XO<br>
kernels, OHM, any init-script customizations, etc. Ribose should be<br>construed as including all components necessary to boot the system, enough<br>to install Glucose if it has not yet been installed.<br><br>Component: A complete disk image for Sugar<br>
Codename: A starch (starch is composed of multiple sugars bonded together.)<br>Description: We often distribute complete disk images for Sugar, ready to<br>boot. These images are composed of multiple elements of the above stack.<br>
~ For example, the current Joyride images are composed of Ribose (the<br>non-graphical work) and Glucose (the shell) but not Fructose (the activity<br>package). Each image series should be named separately, to minimize<br>
confusion. For cutesy codenames, we could have a development build<br>("glycogen", a starch used to produce Glucose) and a stable build<br>("cellulose", an extremely stable starch).<br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.7 (GNU/Linux)<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org</a><br><br>iD8DBQFILdvCUJT6e6HFtqQRAleBAJwP4SdcydEj65jMx+0oFUQo5O23IACfcRbA<br>
/eEeP6Lp7k7WachUYxe3uGM=<br>=jvwh<br>-----END PGP SIGNATURE-----<br>_______________________________________________<br>Sugar mailing list<br><a href="mailto:Sugar@lists.laptop.org">Sugar@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/sugar" target="_blank">http://lists.laptop.org/listinfo/sugar</a><br>
</blockquote></div><br>