Re: [sugar] On the Naming of Sugar
On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > To resolve this, I am going to attempt to list a number of important, > distinct digital objects that this work has produced. I will also > introduce cutesy codenames. I hope that the Sugar developers will adopt a > clear set of distinct names, and I do not care if they choose these names > or other names. So you're saying Sugar is now suite? ;-) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Sat, May 17, 2008 at 10:34 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > Sort of. Mostly, I'm not sure I understand your intended release > timeline, so I didn't want to touch it. > > I think s/Sugar/Sucrose/ is probably a good choice here. However, I also > view a Sucrose release as little more than a pair of pointers, to a > specific version of Glucose and a specific version of Fructose. So for > example, declaring a "feature freeze" on Sucrose seems slightly weird, > because Sucrose doesn't really have any features of its own. This is not > an important point, but since I was not 100% sure what to do, I did nothing. For 0.82, I'm planning to use a single schedule for Glucose/Fructose for simplicity (we can reevalute for the next release). So I think using Fructose on the schedule make sense. I went ahead and made the change. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Pesenti Gritti wrote: | On Sat, May 17, 2008 at 1:14 PM, Marco Pesenti Gritti | <[EMAIL PROTECTED]> wrote: |> Changes I'd make to use Ben taxonomy: |> |> * In the schedule section s/Sugar/Sucrose | | Benjamin, you didn't make this change on the wiki. Intentional? Sort of. Mostly, I'm not sure I understand your intended release timeline, so I didn't want to touch it. I think s/Sugar/Sucrose/ is probably a good choice here. However, I also view a Sucrose release as little more than a pair of pointers, to a specific version of Glucose and a specific version of Fructose. So for example, declaring a "feature freeze" on Sucrose seems slightly weird, because Sucrose doesn't really have any features of its own. This is not an important point, but since I was not 100% sure what to do, I did nothing. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIL0FZUJT6e6HFtqQRAhyGAJ9yLHLIk6NY7x4bKHUJAnHutBueHQCffQg0 cuiaY09NPKpYN6E8BLBYWsI= =EMRN -END PGP SIGNATURE- ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Sat, May 17, 2008 at 1:14 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > Changes I'd make to use Ben taxonomy: > > * In the schedule section s/Sugar/Sucrose Benjamin, you didn't make this change on the wiki. Intentional? Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Fri, 2008-05-16 at 17:20 -0400, Walter Bender wrote: > I've posted your taxonomy here: > > http://wiki.sugarlabs.org/go/Taxonomy > > -walter I added a block diagram view of the software stack, also shown below. It's not the prettiest of diagrams but I hope it's a fair representation of the Sugar stack using the taxonomy suggested by Ben. The only issue I have is with the OS/Ribose layer, as I would prefer to see a platform independent Sugar stack (and the current definition of Ribose ties the OS and Bootstrap to the XO). +---+ | SWEET: The abstract design of the interface | | | +---+ +---+ | STARCH: A complete disk image for Sugar | | | | +-+ | | | SUCROSE: The interface, plus a set | | | | of demonstration activities | | | | | | | | +--+ ++ | | | | | FRUCTOSE: A set of demo | || | | | | | activities | || | | | | | | || | | | | +--+ || | | | | ++| | | | | | GLUCOSE: The base Sugar environment | | | | | | | | | | | +-+ | | | +-+ | | | | ++ | | | OPERATING SYSTEM +-+ | | | || RIBOSE | | | | || | | | | |+-+ | | | ++ | +---+ +---+ | HARDWARE | | | +---+ Regards, Ludovic ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
Tomeu Vizoso wrote: > On Fri, May 16, 2008 at 9:08 PM, Benjamin M. Schwartz > <[EMAIL PROTECTED]> wrote: > >> To resolve this, I am going to attempt to list a number of important, >> distinct digital objects that this work has produced. I will also >> introduce cutesy codenames. I hope that the Sugar developers will adopt a >> clear set of distinct names, and I do not care if they choose these names >> or other names. >> > > Excellent, we really needed this. My only (minor) concern is that so > many codenames might confuse casual observers or contributors. > > What about using some composited terms instead of a single chemical one? > > For example, instead of Sucrose, demonstration package? > > Thanks Benjamin, > > Tomeu > I don't find this taxonomy confusing and I think it's a great way to distinguish the components. Keeps with FOSS traditions too :-) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Sat, May 17, 2008 at 7:39 AM, Albert Cahalan <[EMAIL PROTECTED]> wrote: > I still like Sugar\Windows (with backwards slash of course), To deviate from the taxonomy idea, how about "Candy Glass" - an alternative name for sugar glass - the stuff they use to make the windows for movie sets when people dive through them? http://en.wikipedia.org/wiki/Sugar_glass "Although sugar glass is less dangerous than real [Windows], it can still cause injury" "although its name contains the word "sugar", it is not particularly sweet tasting; it has little flavor" :-) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Sat, May 17, 2008 at 11:27 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Fri, May 16, 2008 at 9:08 PM, Benjamin M. Schwartz > <[EMAIL PROTECTED]> wrote: >> >> To resolve this, I am going to attempt to list a number of important, >> distinct digital objects that this work has produced. I will also >> introduce cutesy codenames. I hope that the Sugar developers will adopt a >> clear set of distinct names, and I do not care if they choose these names >> or other names. > > Excellent, we really needed this. My only (minor) concern is that so > many codenames might confuse casual observers or contributors. > > What about using some composited terms instead of a single chemical one? > > For example, instead of Sucrose, demonstration package? Let's talk about a concrete case. http://wiki.sugarlabs.org/go/Roadmap Changes I'd make to use Ben taxonomy: * In the schedule section s/Sugar/Sucrose * Split the moduleset section in Glucose moduleset and Fructose moduleset. * In the tickets session s/Sugar core/Fructose. Or perhaps two items, Glucose tickets and Fructose tickets. How does it sound? Alternative proposals? Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Fri, May 16, 2008 at 9:08 PM, Benjamin M. Schwartz <[EMAIL PROTECTED]> wrote: > > To resolve this, I am going to attempt to list a number of important, > distinct digital objects that this work has produced. I will also > introduce cutesy codenames. I hope that the Sugar developers will adopt a > clear set of distinct names, and I do not care if they choose these names > or other names. Excellent, we really needed this. My only (minor) concern is that so many codenames might confuse casual observers or contributors. What about using some composited terms instead of a single chemical one? For example, instead of Sucrose, demonstration package? Thanks Benjamin, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
I still like Sugar\Windows (with backwards slash of course), but I have to admit that your naming scheme is excellent. There is an obvious name to describe "Sugar on Windows". Component: An implementation of Sweet on Windows Codename: Lead Acetate (sweeter than glucose, but bad for children) Description: Lead Acetate, also known as Sugar of Lead, is what we get when we implement Sweet on Windows XP. Lead Acetate is toxic to young brains. It causes learning disability, behavioral tendencies toward violence, and even brain damage. http://www.healthychildrenproject.org/pdf/PPLEAD.pdf http://en.wikipedia.org/wiki/Sugar_of_lead Note that this component is related to Wine. Romans used lead containers to make their Wine sweeter. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Fri, May 16, 2008 at 3:30 PM, Jameson Chema Quinn <[EMAIL PROTECTED]> wrote: > Just a note: in Spanish, "sweet" and "candy" are the same word. British English, also, where they have sweets shops rather than candy stores. > "Sweetness" > is less problematic in Spanish, and I'd guess at worst the same as "sweet" > in most languages, so I suggest trying for that. "has sweetness" is more > explicit than "is sweet" anyway. > > (This kind of problem, as well as tougher googling, can arise when your code > names are translatable.) Context is the thing. Googling for Sugar is hopeless, but xo sugar or olpc sugar work fine. -- Edward Cherlin End Poverty at a Profit by teaching children business http://www.EarthTreasury.org/ "The best way to predict the future is to invent it."--Alan Kay ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
Just a note: in Spanish, "sweet" and "candy" are the same word. "Sweetness" is less problematic in Spanish, and I'd guess at worst the same as "sweet" in most languages, so I suggest trying for that. "has sweetness" is more explicit than "is sweet" anyway. (This kind of problem, as well as tougher googling, can arise when your code names are translatable.) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Fri, May 16, 2008 at 12:08 PM, Benjamin M. Schwartz
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think Sugar has a naming problem. There are a lot of different digital
> objects being produced by this project, and referring to all of them as
> Sugar is becoming increasingly confusing. For example, the discussion
> about "Sugar on Windows" has been all but incomprehensible, because each
> author means something entirely different by the term "Sugar". Similarly,
> the recent proposals for "inclusion in Sugar" are extremely confusing,
> since these components will not be required to run Sugar.
>
> To resolve this, I am going to attempt to list a number of important,
> distinct digital objects that this work has produced. I will also
> introduce cutesy codenames. I hope that the Sugar developers will adopt a
> clear set of distinct names, and I do not care if they choose these names
> or other names.
>
> * Sweet (the taste of sugar)
> * Glucose (the fundamental, simple sugar used by all life forms)
> * Fructose (the main sugar in fruit, which is how we're supposed
> to get our sugar.)
> * Sucrose ("table sugar", the kind you buy in the store. It
> consists of glucose and fructose, combined.)
> * Ribose (the sugar used by all lifeforms to control their
> hardware, in the form of RNA. It's important, but not sweet.)
> * A starch (starch is composed of multiple sugars bonded together.)
> Description: We often distribute complete disk images for Sugar, ready to
> boot. These images are composed of multiple elements of the above stack.
> ~ For example, the current Joyride images are composed of Ribose (the
> non-graphical work) and Glucose (the shell) but not Fructose (the activity
> package).
It took me several minutes to get my mind all the way around your
analogy and be able to remember all the bits without looking. So we
would have some more explaining to do. But I like it. I can probably
find pictures of all of these molecules, and if not, we can generate
them in any of several Free Software packages.
> Each image series should be named separately, to minimize
> confusion. For cutesy codenames, we could have a development build
> ("glycogen", a starch used to produce Glucose) and a stable build
> ("cellulose", an extremely stable starch).
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFILdvCUJT6e6HFtqQRAleBAJwP4SdcydEj65jMx+0oFUQo5O23IACfcRbA
> /eEeP6Lp7k7WachUYxe3uGM=
> =jvwh
> -END PGP SIGNATURE-
> ___
> Sugar mailing list
> Sugar@lists.laptop.org
> http://lists.laptop.org/listinfo/sugar
--
Edward Cherlin
End Poverty at a Profit by teaching children business
http://www.EarthTreasury.org/
"The best way to predict the future is to invent it."--Alan Kay
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Re: [sugar] On the Naming of Sugar
On Fri, May 16, 2008 at 2:20 PM, Walter Bender <[EMAIL PROTECTED]> wrote:
> Maybe we need to adopt the late great Walter Payton, "sweetness" as
> our official mascot.
http://www.payton34.com/ Walter and Connie Payton Foundation
We could ask the Foundation if they would be interested. Organ
donations, cancer funding, and toys for underprivileged children would
fit right into our mission. Particularly in the context of Illiniois
HB 5000, The Children's Low-Cost Laptop Act, now before the Senate. I
want a poster of two Chicago South-Side children with XOs saying, "Us
haz teh bestest toyz." With Sweetness beaming on them from above.
Although we would have to explain the concepts of leet-speak and
lolcats to a lot of the public. And the lOLPCat photo on Flickr.
http://en.wikipedia.org/wiki/Walter_Payton
"Payton's legacy continues through the charitable Walter and Connie
Payton Foundation. His own appeals for greater awareness of the need
for organ donations, and after his death, his foundation's, are widely
credited with bringing national attention to the problem.[30] After
his appeal, donations in Illinois skyrocketed, and the regional organ
bank of Illinois was overwhelmed with calls.[31] In response, the City
of Chicago inserted organ donation requests into city vehicle
registration mailings in early 2000, and by August 2000, 13,000 people
had signed into the program.[32] The foundation continues to run a
program that Payton organized to donate toys to underprivileged
children across the Chicago area each Christmas.[33] The family
established the Walter Payton Cancer Fund in 2002.[34]"
> I've posted your taxonomy here:
>
> http://wiki.sugarlabs.org/go/Taxonomy
>
> -walter
>
>
>
> On Fri, May 16, 2008 at 4:14 PM, Marco Pesenti Gritti
> <[EMAIL PROTECTED]> wrote:
>> I think this is brilliant!
>>
>> Marco
>>
>> On Fri, May 16, 2008 at 9:28 PM, Frederick Grose <[EMAIL PROTECTED]> wrote:
>>> Nice carbohydrate lesson as well!
>>>
>>> --Frederick Grose
>>>
>>> On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz
>>> <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think Sugar has a naming problem. There are a lot of different digital
objects being produced by this project, and referring to all of them as
Sugar is becoming increasingly confusing. For example, the discussion
about "Sugar on Windows" has been all but incomprehensible, because each
author means something entirely different by the term "Sugar". Similarly,
the recent proposals for "inclusion in Sugar" are extremely confusing,
since these components will not be required to run Sugar.
To resolve this, I am going to attempt to list a number of important,
distinct digital objects that this work has produced. I will also
introduce cutesy codenames. I hope that the Sugar developers will adopt a
clear set of distinct names, and I do not care if they choose these names
or other names.
Component: The abstract design of the interface
Codename: Sweet (the taste of sugar)
Description: "Sweet" is the abstract design of the interface's appearance
and behavior, independent of any code actually implementing this style.
The mockups at http://wiki.laptop.org/go/Designs represent this
component's second major release, or perhaps 2.0-alpha.
Component: The base Sugar environment
Codename: Glucose (the fundamental, simple sugar used by all life forms)
Description: Glucose is the minimal system that must be added to a
standard Linux distribution in order to enable Activities to run. This
includes all the python code and graphics files that implement the shell,
as well as the Journal. Glucose's dependencies may include xorg-server,
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
marked optional by distributions. Glucose does not include any Activities
except those like the Journal that are non-optional.
Component: A set of demonstration activities
Codename: Fructose (the main sugar in fruit, which is how we're supposed
to get our sugar.)
Description: The Sugar developers will need some example set of
activities with which to demonstrate Sugar. This set is Fructose. The
packages in Fructose should be selected to make the resulting environment
as impressive as possible for a potential client or user. Packages should
therefore be stable, polished, and exercise the widest possible range of
features. Fructose may also serve as an example for people constructing
their own Activity sets.
Component: The interface, plus a set of demonstration activities
Codename: Sucrose ("table sugar", the kind you buy in the store. It
consists of glucose and fructose, combined.)
Description: Sucrose consists of both Glucose and Fructose. It therefore
represents a complete exam
Re: [sugar] On the Naming of Sugar
Maybe we need to adopt the late great Walter Payton, "sweetness" as
our official mascot.
I've posted your taxonomy here:
http://wiki.sugarlabs.org/go/Taxonomy
-walter
On Fri, May 16, 2008 at 4:14 PM, Marco Pesenti Gritti
<[EMAIL PROTECTED]> wrote:
> I think this is brilliant!
>
> Marco
>
> On Fri, May 16, 2008 at 9:28 PM, Frederick Grose <[EMAIL PROTECTED]> wrote:
>> Nice carbohydrate lesson as well!
>>
>> --Frederick Grose
>>
>> On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> I think Sugar has a naming problem. There are a lot of different digital
>>> objects being produced by this project, and referring to all of them as
>>> Sugar is becoming increasingly confusing. For example, the discussion
>>> about "Sugar on Windows" has been all but incomprehensible, because each
>>> author means something entirely different by the term "Sugar". Similarly,
>>> the recent proposals for "inclusion in Sugar" are extremely confusing,
>>> since these components will not be required to run Sugar.
>>>
>>> To resolve this, I am going to attempt to list a number of important,
>>> distinct digital objects that this work has produced. I will also
>>> introduce cutesy codenames. I hope that the Sugar developers will adopt a
>>> clear set of distinct names, and I do not care if they choose these names
>>> or other names.
>>>
>>> Component: The abstract design of the interface
>>> Codename: Sweet (the taste of sugar)
>>> Description: "Sweet" is the abstract design of the interface's appearance
>>> and behavior, independent of any code actually implementing this style.
>>> The mockups at http://wiki.laptop.org/go/Designs represent this
>>> component's second major release, or perhaps 2.0-alpha.
>>>
>>> Component: The base Sugar environment
>>> Codename: Glucose (the fundamental, simple sugar used by all life forms)
>>> Description: Glucose is the minimal system that must be added to a
>>> standard Linux distribution in order to enable Activities to run. This
>>> includes all the python code and graphics files that implement the shell,
>>> as well as the Journal. Glucose's dependencies may include xorg-server,
>>> xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
>>> marked optional by distributions. Glucose does not include any Activities
>>> except those like the Journal that are non-optional.
>>>
>>> Component: A set of demonstration activities
>>> Codename: Fructose (the main sugar in fruit, which is how we're supposed
>>> to get our sugar.)
>>> Description: The Sugar developers will need some example set of
>>> activities with which to demonstrate Sugar. This set is Fructose. The
>>> packages in Fructose should be selected to make the resulting environment
>>> as impressive as possible for a potential client or user. Packages should
>>> therefore be stable, polished, and exercise the widest possible range of
>>> features. Fructose may also serve as an example for people constructing
>>> their own Activity sets.
>>>
>>> Component: The interface, plus a set of demonstration activities
>>> Codename: Sucrose ("table sugar", the kind you buy in the store. It
>>> consists of glucose and fructose, combined.)
>>> Description: Sucrose consists of both Glucose and Fructose. It therefore
>>> represents a complete example Sugar environment, ready to be installed
>>> through a package manager. The purpose of Sucrose is so that prospective
>>> deployers can install the "sugar-sucrose" package, and immediately say
>>> "Wow! Look at all the cool capabilities that this system has!".
>>>
>>> Component: The base Linux distribution being used by Sugar
>>> Codename: Ribose (the sugar used by all lifeforms to control their
>>> hardware, in the form of RNA. It's important, but not sweet.)
>>> Description: Ribose is the set of hardware-centric software components
>>> that have been developed throughout this project. It includes the XO
>>> kernels, OHM, any init-script customizations, etc. Ribose should be
>>> construed as including all components necessary to boot the system, enough
>>> to install Glucose if it has not yet been installed.
>>>
>>> Component: A complete disk image for Sugar
>>> Codename: A starch (starch is composed of multiple sugars bonded
>>> together.)
>>> Description: We often distribute complete disk images for Sugar, ready to
>>> boot. These images are composed of multiple elements of the above stack.
>>> ~ For example, the current Joyride images are composed of Ribose (the
>>> non-graphical work) and Glucose (the shell) but not Fructose (the activity
>>> package). Each image series should be named separately, to minimize
>>> confusion. For cutesy codenames, we could have a development build
>>> ("glycogen", a starch used to produce Glucose) and a stable build
>>> ("cellulose", an extremely stable starch).
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v2.0.7 (GNU/Li
Re: [sugar] On the Naming of Sugar
I think this is brilliant!
Marco
On Fri, May 16, 2008 at 9:28 PM, Frederick Grose <[EMAIL PROTECTED]> wrote:
> Nice carbohydrate lesson as well!
>
> --Frederick Grose
>
> On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz
> <[EMAIL PROTECTED]> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I think Sugar has a naming problem. There are a lot of different digital
>> objects being produced by this project, and referring to all of them as
>> Sugar is becoming increasingly confusing. For example, the discussion
>> about "Sugar on Windows" has been all but incomprehensible, because each
>> author means something entirely different by the term "Sugar". Similarly,
>> the recent proposals for "inclusion in Sugar" are extremely confusing,
>> since these components will not be required to run Sugar.
>>
>> To resolve this, I am going to attempt to list a number of important,
>> distinct digital objects that this work has produced. I will also
>> introduce cutesy codenames. I hope that the Sugar developers will adopt a
>> clear set of distinct names, and I do not care if they choose these names
>> or other names.
>>
>> Component: The abstract design of the interface
>> Codename: Sweet (the taste of sugar)
>> Description: "Sweet" is the abstract design of the interface's appearance
>> and behavior, independent of any code actually implementing this style.
>> The mockups at http://wiki.laptop.org/go/Designs represent this
>> component's second major release, or perhaps 2.0-alpha.
>>
>> Component: The base Sugar environment
>> Codename: Glucose (the fundamental, simple sugar used by all life forms)
>> Description: Glucose is the minimal system that must be added to a
>> standard Linux distribution in order to enable Activities to run. This
>> includes all the python code and graphics files that implement the shell,
>> as well as the Journal. Glucose's dependencies may include xorg-server,
>> xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
>> marked optional by distributions. Glucose does not include any Activities
>> except those like the Journal that are non-optional.
>>
>> Component: A set of demonstration activities
>> Codename: Fructose (the main sugar in fruit, which is how we're supposed
>> to get our sugar.)
>> Description: The Sugar developers will need some example set of
>> activities with which to demonstrate Sugar. This set is Fructose. The
>> packages in Fructose should be selected to make the resulting environment
>> as impressive as possible for a potential client or user. Packages should
>> therefore be stable, polished, and exercise the widest possible range of
>> features. Fructose may also serve as an example for people constructing
>> their own Activity sets.
>>
>> Component: The interface, plus a set of demonstration activities
>> Codename: Sucrose ("table sugar", the kind you buy in the store. It
>> consists of glucose and fructose, combined.)
>> Description: Sucrose consists of both Glucose and Fructose. It therefore
>> represents a complete example Sugar environment, ready to be installed
>> through a package manager. The purpose of Sucrose is so that prospective
>> deployers can install the "sugar-sucrose" package, and immediately say
>> "Wow! Look at all the cool capabilities that this system has!".
>>
>> Component: The base Linux distribution being used by Sugar
>> Codename: Ribose (the sugar used by all lifeforms to control their
>> hardware, in the form of RNA. It's important, but not sweet.)
>> Description: Ribose is the set of hardware-centric software components
>> that have been developed throughout this project. It includes the XO
>> kernels, OHM, any init-script customizations, etc. Ribose should be
>> construed as including all components necessary to boot the system, enough
>> to install Glucose if it has not yet been installed.
>>
>> Component: A complete disk image for Sugar
>> Codename: A starch (starch is composed of multiple sugars bonded
>> together.)
>> Description: We often distribute complete disk images for Sugar, ready to
>> boot. These images are composed of multiple elements of the above stack.
>> ~ For example, the current Joyride images are composed of Ribose (the
>> non-graphical work) and Glucose (the shell) but not Fructose (the activity
>> package). Each image series should be named separately, to minimize
>> confusion. For cutesy codenames, we could have a development build
>> ("glycogen", a starch used to produce Glucose) and a stable build
>> ("cellulose", an extremely stable starch).
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.7 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iD8DBQFILdvCUJT6e6HFtqQRAleBAJwP4SdcydEj65jMx+0oFUQo5O23IACfcRbA
>> /eEeP6Lp7k7WachUYxe3uGM=
>> =jvwh
>> -END PGP SIGNATURE-
>> ___
>> Sugar mailing list
>> Sugar@lists.laptop.org
>> http://lists.laptop.org/listinfo/
Re: [sugar] On the Naming of Sugar
Nice carbohydrate lesson as well!
--Frederick Grose
On Fri, May 16, 2008 at 3:08 PM, Benjamin M. Schwartz <
[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think Sugar has a naming problem. There are a lot of different digital
> objects being produced by this project, and referring to all of them as
> Sugar is becoming increasingly confusing. For example, the discussion
> about "Sugar on Windows" has been all but incomprehensible, because each
> author means something entirely different by the term "Sugar". Similarly,
> the recent proposals for "inclusion in Sugar" are extremely confusing,
> since these components will not be required to run Sugar.
>
> To resolve this, I am going to attempt to list a number of important,
> distinct digital objects that this work has produced. I will also
> introduce cutesy codenames. I hope that the Sugar developers will adopt a
> clear set of distinct names, and I do not care if they choose these names
> or other names.
>
> Component: The abstract design of the interface
> Codename: Sweet (the taste of sugar)
> Description: "Sweet" is the abstract design of the interface's appearance
> and behavior, independent of any code actually implementing this style.
> The mockups at http://wiki.laptop.org/go/Designs represent this
> component's second major release, or perhaps 2.0-alpha.
>
> Component: The base Sugar environment
> Codename: Glucose (the fundamental, simple sugar used by all life forms)
> Description: Glucose is the minimal system that must be added to a
> standard Linux distribution in order to enable Activities to run. This
> includes all the python code and graphics files that implement the shell,
> as well as the Journal. Glucose's dependencies may include xorg-server,
> xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be
> marked optional by distributions. Glucose does not include any Activities
> except those like the Journal that are non-optional.
>
> Component: A set of demonstration activities
> Codename: Fructose (the main sugar in fruit, which is how we're supposed
> to get our sugar.)
> Description: The Sugar developers will need some example set of
> activities with which to demonstrate Sugar. This set is Fructose. The
> packages in Fructose should be selected to make the resulting environment
> as impressive as possible for a potential client or user. Packages should
> therefore be stable, polished, and exercise the widest possible range of
> features. Fructose may also serve as an example for people constructing
> their own Activity sets.
>
> Component: The interface, plus a set of demonstration activities
> Codename: Sucrose ("table sugar", the kind you buy in the store. It
> consists of glucose and fructose, combined.)
> Description: Sucrose consists of both Glucose and Fructose. It therefore
> represents a complete example Sugar environment, ready to be installed
> through a package manager. The purpose of Sucrose is so that prospective
> deployers can install the "sugar-sucrose" package, and immediately say
> "Wow! Look at all the cool capabilities that this system has!".
>
> Component: The base Linux distribution being used by Sugar
> Codename: Ribose (the sugar used by all lifeforms to control their
> hardware, in the form of RNA. It's important, but not sweet.)
> Description: Ribose is the set of hardware-centric software components
> that have been developed throughout this project. It includes the XO
> kernels, OHM, any init-script customizations, etc. Ribose should be
> construed as including all components necessary to boot the system, enough
> to install Glucose if it has not yet been installed.
>
> Component: A complete disk image for Sugar
> Codename: A starch (starch is composed of multiple sugars bonded together.)
> Description: We often distribute complete disk images for Sugar, ready to
> boot. These images are composed of multiple elements of the above stack.
> ~ For example, the current Joyride images are composed of Ribose (the
> non-graphical work) and Glucose (the shell) but not Fructose (the activity
> package). Each image series should be named separately, to minimize
> confusion. For cutesy codenames, we could have a development build
> ("glycogen", a starch used to produce Glucose) and a stable build
> ("cellulose", an extremely stable starch).
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFILdvCUJT6e6HFtqQRAleBAJwP4SdcydEj65jMx+0oFUQo5O23IACfcRbA
> /eEeP6Lp7k7WachUYxe3uGM=
> =jvwh
> -END PGP SIGNATURE-
> ___
> Sugar mailing list
> Sugar@lists.laptop.org
> http://lists.laptop.org/listinfo/sugar
>
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
