Talk:Sugar on a Stick: Difference between revisions

(40 intermediate revisions by 6 users not shown)

Line 1:

==Installation==

While it is easy to find the download instructions, the non-GUI [[Sugar_on_a_Stick/Installation/Variations|installation]] instructions are hard to find [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations#livecd-iso-to-disk_script][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations#liveusb-creator_from_command_line_in_terminal]and I don't know where the GUI instructions are.[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation] --[[User:Walter|Walter]] 21:28, 4 June 2010 (EDT)

==[[Sugar on a Stick/FAQ]]==

See [[Sugar on a Stick/FAQ]] and [[Talk:Sugar on a Stick/FAQ]]. For older versions of this page, see [[/Archive]].

There's a lot going on in [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019311.html this thread]; here is my attempt to summarize discussions so far. If I've missed or misstated anything, please correct me. [[User:Mchua|Mchua]] 05:35, 21 September 2009 (UTC)

There's a lot going on in [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019311.html this thread]; here is my attempt to summarize discussions so far. If I've missed or misstated anything, please correct me. Last updated by [[User:Mchua|Mchua]] 04:14, 24 September 2009 (UTC)

== What are we talking about? ==

Line 13:

Line 16:

SoaS is a Linux-based, Sugar-running, delivered-on-a-thumbdrive distribution focused on customizability, deployability, and local support, and meant for 1-to-1 use in schools.

The term is currently ~~a trademark owned by SL and~~ used to refer ~~colloquially~~ to several things:

The term is currently used colloquially to refer to several things:

* the code, based on Fedora, that Sebastian has been working on (...for lack of a better descriptor)

Line 21:

Line 24:

== Proposed next steps ==

=== ~~Make a~~ SoaS ~~mailing list~~ ===

=== Formalize what SL project status means for SoaS spins ===

~~Support:~~

* SoaS discussions are often SoaS-specific and treat "Sugar" as an upstream; the details of development for one do not necessarily matter for the other, so splitting into two separate lists may help people manage their inbox traffic better.

* There are sufficient numbers of people (including several key SoaS developers) interested in a SoaS-specific list to enable good working conversations to be had there.

~~Concerns:~~

* The membership of an SoaS list overlaps heavily with the existing iaep and sugar-devel lists, so a new list to reach everyone may not be needed.

* Splitting off a separate list might create overly segregated conversations with less total momentum than if we all continued on iaep and sugar-devel.

~~Who decides:~~

~~This is unclear. Is it Bernie, as head of Infrastructure? Is it SLOBs, as part of granting SoaS a particular status?~~

~~=== Formalize~~ a SoaS ~~development team ===~~

SoaS development and Sugar platform development are two separate projects done by different groups; one for Sugar platform development and one for each SoaS spin. There is currently only one active SoaS spin, and it is the Fedora-based project being driven by Sebastian Dziallas, for a current grand total of 2 project groups; however, there may be other SoaS spins in the future.

~~This~~ means ~~acknowledging that SoaS development and Sugar platform development are not the same thing, and that they are done by two different groups (which may have many overlapping members). The creation of~~ a ~~mailing list~~ is ~~seen as part of this separation of project identities~~.

Exactly what it means to be a SL project is still an open question.

~~Exactly how~~ these ~~groups will operate, what~~ the ~~relationship between them will be~~, ~~how they will be governed~~, what ~~tools they will use where~~, etc. ~~are still open questions with varying opinions on each topic; however, it~~ does ~~not seem~~ that ~~anyone has objected to~~ the ~~notion that SoaS~~ and the ~~Sugar Platform are two (highly related) projects, not one.~~

# What are the criteria a SL project must meet (including requirements for ongoing engagement/contribution)?

# How does something become a SL project?

## Who determines whether a project meets these criteria?

## How do they make that determination?

## Is there a schedule and/or timeline for this determination?

## How does someone initiate the process for requesting SL project status, and who can do so?

## What happens if it is determined that a project does not meet these criteria?

# How does a SL project become not a SL project, and for what reasons might this happen?

# What benefits (mailing list, etc.) does a SL project get?

# How can all of the above answers be amended if needed in the future?

# What is the list of current projects that we are considering including in the initial "this is a SL project" approval round, and what do these projects have to do in order to be approved for the criteria?

Who decides:

~~This is unclear~~.

These decisions need to ultimately be ratified by SLOBs. It's been suggested that Sebastian's Fedora-based SoaS spin be the test case for the first "SL project," so it makes sense to start out on the SoaS mailing list to come up with a set of proposed answers to these questions that will work for the projects themselves, then ask SLOBs to formalize them (with more discussion/modification if need be).

=== Determine what "Sugar on a Stick" refers to ===

Line 54:

Line 56:

Who decides:

~~SLOBs, or a~~ decision panel convened by SLOBs (the latter is happening now).

A decision panel convened by the SLOBs (the latter is happening now), with strong input from both the current "SoaS" team and the Marketing team. See [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019548.html this mailing list thread calling for discussion panel volunteers].

==~~= Determine what "the code Sebastian is working on" is called =~~==

== Completed next steps ==

~~This depends on the answer to "what 'SoaS' refers to," above.~~

=== Make a SoaS mailing list ===

~~If (1), Sebastian's code would likely be "SoaS-Fedora" or similar, possibly after an application process allowing it to use the "SoaS" name.~~

~~If (2), Sebastian's code would have~~ a ~~different secondary name ("SoaS-Fedora" or some other) but could (and likely would) start out as the specific SoaS edition that SL referred to when marketing "~~SoaS."

~~If (3)~~, ~~Sebastian's code is simply "SoaS~~."

The list was created at http://lists.sugarlabs.org/listinfo/soas after reaching consensus on the ticket requesting that the list be created, http://dev.sugarlabs.org/ticket/1419.

~~Who decides~~:

From the list description: "This list is intended for discussions related to the development of Sugar on a Stick, which is located in the Sugar Labs wiki. User feedback can also be directed to feedback@sugarlabs.org and the IAEP (It's An Education Project) mailing list. Upstream development and discussions of Sugar take place in the sugar-devel mailing list. Other LiveUSB Sugar projects are invited and very welcome to share their concepts, ideas and thoughts on-list, too." Also see the [http://meeting.sugarlabs.org/sugar-meeting.log.20090923_1558.html log from the informal IRC discussion about mailing list creation] for more context.

This is ~~dependent~~ on the ~~answer~~ to ~~"what~~ '~~SoaS' refers~~ to," ~~so in effect~~ the ~~people who decide that question also decide who gets to decide this question~~.

== Side questions ==

Line 92:

Line 89:

Both decisions would be made by SLOBs or a decision panel convened by the SLOBs. This issue is a peripheral one that isn't particularly within the scope of the current SoaS discussions in this thread, though.

==Soas-v7 Release Announcement==

[SoaS] ANNOUNCE: Sugar on a Stick 7 (Quandong)

pbrobinson 06/05/2012

I'd like to announce Sugar on a Stick 7 (Quandong)

There's been a lot of work go into this release from a lot of

communities from Fedora and all the Fedora 17 features that give us

new and exciting hardware support to the Sugar Labs community and all

the new features that come with the Sugar 0.96 release on which SoaS

v7 is based.

Thanks go to all the people that have contributed to this release

including Kalpa and Thomas who helped directly with SoaS, the Sugar

development team and other Sugar developers. A lot of work has been

done to ensure we can get working core Activities like Read and Browse

and what should a good working base for deployments to test and add

to.

Some of the key new features of this release include:

- Based on Fedora 17 and it's new features [1]

- Massively improved x86 Mac support [2]

- Sugar 0.96 with initial support for GTK3 Activities and many other

improvements [3]

- Return of Browse, now based on WebKit

- The long awaited return of Read and inclusion of GetBooks

- Enhanced hardware support with the 3.3 kernel

- An increase in default Activities by nearly 50%

Almost all of the previous Activities have seen updated releases

including but not limited to:

- Abacus 35 (GTK3)

- Record 95

- Physics 9

- TurtleArt 138

Newly added Activities include:

- Browse 137 (GTK3)

- Countries 33

- Finance 7

- GetBooks 11

- Help 14 (GTK3)

- Infoslicer 14

- Labyrinth 12

- Paint 43

- Portfolio 21

- Read 99 (GTK3)

There are many more Activities available through the usual Fedora repositories.

The release name, Quandong, continues the tradition of naming releases

by types of fruit. The Quandong [4] or Native Peach is a native

Australian bushfood.

You can download the release from the following link.

http://spins.fedoraproject.org/soas/

It can also be installed as part of a standard Fedora 17 install and

is shipped as part of the official Fedora installer DVD and the Fedora

Multi Spin Live DVD. It can also be installed from the GUI package

tool within a running Fedora install or by command line "sudo yum

install @sugar-desktop".

[1] https://fedoraproject.org/wiki/Releases/17/FeatureList

[2] http://mjg59.dreamwidth.org/12037.html

[3] http://wiki.sugarlabs.org/go/0.96/Notes

[4] http://en.wikipedia.org/wiki/Santalum_acuminatum

_______________________________________________

SoaS mailing list

SoaS@lists.sugarlabs.org

http://lists.sugarlabs.org/listinfo/soas

== Side notes ==

Line 98:

Line 168:

Feedback from a first grade teacher: What teachers care about: (1) Is it friendly? (2) Is it consistent? (3) Can the effort needed to maintain it be sustained? What they don't care about: (1) What group "runs" it? (2) Who owns the trademark? (3) What bleeding-edge features are being developed now for a future release? (3) What is the underlying technology? What would reassure them: (1) Peer support. (2) Seeing it in action, so they can create a "mental paradigm" category for something like Sugar/SoaS.

Added Notes:

*1.) F12(rawhide) and opensuse-edu now distribute a dual mode live.iso of Sugar-Desktop which boots into sugar as a CD or can be used to dd write to a USB/SD "stick". (persistence is a work in progress on these)[[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux#Dual_Mode_.iso_Files]] [[http://lizards.opensuse.org/2009/04/28/whats-behind-lzma-compressed-livecds/]][[http://git.berlios.de/cgi-bin/gitweb.cgi?p=kiwi;a=blob;f=modules/KIWILinuxRC.sh;h=6591ab5125df730800bf3dc3dde9ce875183568c;hb=HEAD]][[http://alt.fedoraproject.org/pub/alt/nightly-composes/education/]]

*2.) Sugar from multiple distros is available[[http://people.sugarlabs.org/Tgillard/]] as a VMPlayer or Virtualbox "Appliance" which can be stored on a USB/SD "Stick" and thus is transportable with (persistence) from PC to PC.

*3.) There are "full installs"(real file structure-not a live system) of: Sugar, Sugar+Gnome, Sugar+KDE on larger(4GB+) USB Sticks which are available for download [[http://people.sugarlabs.org/Tgillard/]]in compressed form that can be written to a bootable USB/SD with a dd command in several minutes.

Added Notes:

from Soas lists:

Rubén Rodríguez Pérez

* Trisquel-Edu (Live USB)

* Trisquel-Sugar (Announced 09/28/2009)

I will further explain the differences:

We are including the Sugar packages in both our 2.2 LTS version (where

you can find the Trisquel Edu edition), and in our new 3.0 STS version.

All our live Sugar images will be based on the STS one, as it will

provide better hardware support.

Trisquel Edu, which is a GNOME based educational system, can run Sugar

as an alternate environment, or serve it via LTSP. The Edu edition (like

the Pro one) is only available in the 2.2 LTS version of the distro. It

will be the recommended version for large Sugar-on-Trisquel deployments.

== Development notes ==

Processes we should document.

* [http://me.etin.gs/sugar/sugar.log.20100317_1245.html how to make a kickstart file]

: How to make a remix:http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Instructions

* [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100319_0950.html minimal kickstart file]

* Package selection: timeline and criteria. How does stuff make it onto SoaS?

== Some checksum hash(s) please ==

The following links are missing the SoaS SHA256 checksum/hashs

http://fedora-spins.c3sl.ufpr.br/alt/spins/linux/releases/15/Spins/i686/Fedora-15-i686-Spins-CHECKSUM

http://fedora-spins.c3sl.ufpr.br/alt/spins/linux/releases/15/Spins/x86_64/Fedora-15-x86_64-Spins-CHECKSUM

Could someone post a png or gif of the hash for these files here since fedora won't update this until F16(Verne) is out.

--[[User:Chief Mike|Chief Mike]] 11:29, 18 October 2011 (EDT)

:sha256sum 95650ec1257670e44466e75059ff8b05f636cd78658a025ae52c8992145f778c Fedora-15-i686-Live-SoaS.iso

:md5sum 67dc6fe4625f61d9d51f89c082f3c9c3 Fedora-15-i686-Live-SoaS.iso

:sha256sum aa18f9dae1fe8d9bde47a45fefd19f2127dfc1001de3c1f76fbc1f85ec576e0d Fedora-15-x86_64-Live-SoaS.iso

:md5sum db209baffdef41b7ca029b6e224ed7d1 Fedora-15-x86_64-Live-SoaS.iso

:: from my copies --[[User:FGrose|FGrose]] 12:30, 18 October 2011 (EDT)

@@ Line 1: / Line 1: @@
 {{TOCright}}
+==Installation==
+While it is easy to find the download instructions, the non-GUI [[Sugar_on_a_Stick/Installation/Variations|installation]] instructions are hard to find [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations#livecd-iso-to-disk_script][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations#liveusb-creator_from_command_line_in_terminal]and I don't know where the GUI instructions are.[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation] --[[User:Walter|Walter]] 21:28, 4 June 2010 (EDT)
 ==[[Sugar on a Stick/FAQ]]==
 See [[Sugar on a Stick/FAQ]] and [[Talk:Sugar on a Stick/FAQ]]. For older versions of this page, see [[/Archive]].
-There's a lot going on in [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019311.html this thread]; here is my attempt to summarize discussions so far. If I've missed or misstated anything, please correct me. [[User:Mchua|Mchua]] 05:35, 21 September 2009 (UTC)
+There's a lot going on in [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019311.html this thread]; here is my attempt to summarize discussions so far. If I've missed or misstated anything, please correct me. Last updated by [[User:Mchua|Mchua]] 04:14, 24 September 2009 (UTC)
 == What are we talking about? ==
@@ Line 13: / Line 16: @@
 SoaS is a Linux-based, Sugar-running, delivered-on-a-thumbdrive distribution focused on customizability, deployability, and local support, and meant for 1-to-1 use in schools.
-The term is currently a trademark owned by SL and used to refer colloquially to several things:
+The term is currently used colloquially to refer to several things:
 * the code, based on Fedora, that Sebastian has been working on (...for lack of a better descriptor)
@@ Line 21: / Line 24: @@
 == Proposed next steps ==
-=== Make a SoaS mailing list ===
+=== Formalize what SL project status means for SoaS spins ===
-Support:
-* SoaS discussions are often SoaS-specific and treat "Sugar" as an upstream; the details of development for one do not necessarily matter for the other, so splitting into two separate lists may help people manage their inbox traffic better.
-* There are sufficient numbers of people (including several key SoaS developers) interested in a SoaS-specific list to enable good working conversations to be had there.
-Concerns:
-* The membership of an SoaS list overlaps heavily with the existing iaep and sugar-devel lists, so a new list to reach everyone may not be needed.
-* Splitting off a separate list might create overly segregated conversations with less total momentum than if we all continued on iaep and sugar-devel.
-Who decides:
-This is unclear. Is it Bernie, as head of Infrastructure? Is it SLOBs, as part of granting SoaS a particular status?
-=== Formalize a SoaS development team ===
+SoaS development and Sugar platform development are two separate projects done by different groups; one for Sugar platform development and one for each SoaS spin. There is currently only one active SoaS spin, and it is the Fedora-based project being driven by Sebastian Dziallas, for a current grand total of 2 project groups; however, there may be other SoaS spins in the future.
-This means acknowledging that SoaS development and Sugar platform development are not the same thing, and that they are done by two different groups (which may have many overlapping members). The creation of a mailing list is seen as part of this separation of project identities.
+Exactly what it means to be a SL project is still an open question.
-Exactly how these groups will operate, what the relationship between them will be, how they will be governed, what tools they will use where, etc. are still open questions with varying opinions on each topic; however, it does not seem that anyone has objected to the notion that SoaS and the Sugar Platform are two (highly related) projects, not one.
+# What are the criteria a SL project must meet (including requirements for ongoing engagement/contribution)?
+# How does something become a SL project?
+## Who determines whether a project meets these criteria?
+## How do they make that determination?
+## Is there a schedule and/or timeline for this determination?
+## How does someone initiate the process for requesting SL project status, and who can do so?
+## What happens if it is determined that a project does not meet these criteria?
+# How does a SL project become not a SL project, and for what reasons might this happen?
+# What benefits (mailing list, etc.) does a SL project get?
+# How can all of the above answers be amended if needed in the future?
+# What is the list of current projects that we are considering including in the initial "this is a SL project" approval round, and what do these projects have to do in order to be approved for the criteria?
 Who decides:
-This is unclear.
+These decisions need to ultimately be ratified by SLOBs. It's been suggested that Sebastian's Fedora-based SoaS spin be the test case for the first "SL project," so it makes sense to start out on the SoaS mailing list to come up with a set of proposed answers to these questions that will work for the projects themselves, then ask SLOBs to formalize them (with more discussion/modification if need be).
 === Determine what "Sugar on a Stick" refers to ===
@@ Line 54: / Line 56: @@
 Who decides:
-SLOBs, or a decision panel convened by SLOBs (the latter is happening now).
+A decision panel convened by the SLOBs (the latter is happening now), with strong input from both the current "SoaS" team and the Marketing team. See [http://lists.sugarlabs.org/archive/sugar-devel/2009-September/019548.html this mailing list thread calling for discussion panel volunteers].
-=== Determine what "the code Sebastian is working on" is called ===
+== Completed next steps ==
-This depends on the answer to "what 'SoaS' refers to," above.
+=== Make a SoaS mailing list ===
-If (1), Sebastian's code would likely be "SoaS-Fedora" or similar, possibly after an application process allowing it to use the "SoaS" name.
-If (2), Sebastian's code would have a different secondary name ("SoaS-Fedora" or some other) but could (and likely would) start out as the specific SoaS edition that SL referred to when marketing "SoaS."
-If (3), Sebastian's code is simply "SoaS."
+The list was created at http://lists.sugarlabs.org/listinfo/soas after reaching consensus on the ticket requesting that the list be created, http://dev.sugarlabs.org/ticket/1419.
-Who decides:
+From the list description: "This list is intended for discussions related to the development of Sugar on a Stick, which is located in the Sugar Labs wiki. User feedback can also be directed to feedback@sugarlabs.org and the IAEP (It's An Education Project) mailing list. Upstream development and discussions of Sugar take place in the sugar-devel mailing list. Other LiveUSB Sugar projects are invited and very welcome to share their concepts, ideas and thoughts on-list, too." Also see the [http://meeting.sugarlabs.org/sugar-meeting.log.20090923_1558.html log from the informal IRC discussion about mailing list creation] for more context.
-This is dependent on the answer to "what 'SoaS' refers to," so in effect the people who decide that question also decide who gets to decide this question.
 == Side questions ==
@@ Line 92: / Line 89: @@
 Both decisions would be made by SLOBs or a decision panel convened by the SLOBs. This issue is a peripheral one that isn't particularly within the scope of the current SoaS discussions in this thread, though.
+==Soas-v7 Release Announcement==
+ [SoaS] ANNOUNCE: Sugar on a Stick 7 (Quandong)
+ pbrobinson 06/05/2012
+ I'd like to announce Sugar on a Stick 7 (Quandong)
+ There's been a lot of work go into this release from a lot of
+ communities from Fedora and all the Fedora 17 features that give us
+ new and exciting hardware support to the Sugar Labs community and all
+ the new features that come with the Sugar 0.96 release on which SoaS
+ v7 is based.
+ Thanks go to all the people that have contributed to this release
+ including Kalpa and Thomas who helped directly with SoaS, the Sugar
+ development team and other Sugar developers. A lot of work has been
+ done to ensure we can get working core Activities like Read and Browse
+ and what should a good working base for deployments to test and add
+ to.
+ Some of the key new features of this release include:
+ - Based on Fedora 17 and it's new features [1]
+ - Massively improved x86 Mac support [2]
+ - Sugar 0.96 with initial support for GTK3 Activities and many other
+ improvements [3]
+ - Return of Browse, now based on WebKit
+ - The long awaited return of Read and inclusion of GetBooks
+ - Enhanced hardware support with the 3.3 kernel
+ - An increase in default Activities by nearly 50%
+ Almost all of the previous Activities have seen updated releases
+ including but not limited to:
+ - Abacus 35 (GTK3)
+ - Record 95
+ - Physics 9
+ - TurtleArt 138
+ Newly added Activities include:
+ - Browse 137 (GTK3)
+ - Countries 33
+ - Finance 7
+ - GetBooks 11
+ - Help 14 (GTK3)
+ - Infoslicer 14
+ - Labyrinth 12
+ - Paint 43
+ - Portfolio 21
+ - Read 99 (GTK3)
+ There are many more Activities available through the usual Fedora repositories.
+ The release name, Quandong, continues the tradition of naming releases
+ by types of fruit. The Quandong [4] or Native Peach is a native
+ Australian bushfood.
+ You can download the release from the following link.
+ http://spins.fedoraproject.org/soas/
+ It can also be installed as part of a standard Fedora 17 install and
+ is shipped as part of the official Fedora installer DVD and the Fedora
+ Multi Spin Live DVD. It can also be installed from the GUI package
+ tool within a running Fedora install or by command line "sudo yum
+ install @sugar-desktop".
+ [1] https://fedoraproject.org/wiki/Releases/17/FeatureList
+ [2] http://mjg59.dreamwidth.org/12037.html
+ [3] http://wiki.sugarlabs.org/go/0.96/Notes
+ [4] http://en.wikipedia.org/wiki/Santalum_acuminatum
+ _______________________________________________
+ SoaS mailing list
+ SoaS@lists.sugarlabs.org
+ http://lists.sugarlabs.org/listinfo/soas
 == Side notes ==
@@ Line 98: / Line 168: @@
 Feedback from a first grade teacher: What teachers care about: (1) Is it friendly? (2) Is it consistent? (3) Can the effort needed to maintain it be sustained? What they don't care about: (1)  What group "runs" it? (2) Who owns the trademark? (3) What bleeding-edge features are being developed now for a future release? (3) What is the underlying technology? What would reassure them: (1) Peer support. (2) Seeing it in action, so they can create a "mental paradigm" category for something like Sugar/SoaS.
+Added Notes:
+*1.) F12(rawhide) and opensuse-edu now distribute a dual mode live.iso of Sugar-Desktop which boots into sugar as a CD or can be used to dd write to a USB/SD "stick". (persistence is a work in progress on these)[[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux#Dual_Mode_.iso_Files]] [[http://lizards.opensuse.org/2009/04/28/whats-behind-lzma-compressed-livecds/]][[http://git.berlios.de/cgi-bin/gitweb.cgi?p=kiwi;a=blob;f=modules/KIWILinuxRC.sh;h=6591ab5125df730800bf3dc3dde9ce875183568c;hb=HEAD]][[http://alt.fedoraproject.org/pub/alt/nightly-composes/education/]]
+*2.) Sugar from multiple distros is available[[http://people.sugarlabs.org/Tgillard/]] as a VMPlayer or Virtualbox "Appliance" which can be stored on a USB/SD "Stick" and thus is transportable with (persistence) from PC to PC.
+*3.) There are "full installs"(real file structure-not a live system) of: Sugar, Sugar+Gnome, Sugar+KDE on larger(4GB+) USB Sticks which are available for download [[http://people.sugarlabs.org/Tgillard/]]in compressed form that can be written to a bootable USB/SD with a dd command in several minutes.
+Added Notes:
+from Soas lists:
+Rubén Rodríguez Pérez
+* Trisquel-Edu (Live USB)
+* Trisquel-Sugar (Announced 09/28/2009)
+I will further explain the differences:
+We are including the Sugar packages in both our 2.2 LTS version (where
+you can find the Trisquel Edu edition), and in our new 3.0 STS version.
+All our live Sugar images will be based on the STS one, as it will
+provide better hardware support.
+Trisquel Edu, which is a GNOME based educational system, can run Sugar
+as an alternate environment, or serve it via LTSP. The Edu edition (like
+the Pro one) is only available in the 2.2 LTS version of the distro. It
+will be the recommended version for large Sugar-on-Trisquel deployments.
+== Development notes ==
+Processes we should document.
+* [http://me.etin.gs/sugar/sugar.log.20100317_1245.html how to make a kickstart file]
+: How to make a remix:http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Instructions
+* [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100319_0950.html minimal kickstart file]
+* Package selection: timeline and criteria. How does stuff make it onto SoaS?
+== Some checksum hash(s) please ==
+The following links are missing the SoaS SHA256 checksum/hashs
+ http://fedora-spins.c3sl.ufpr.br/alt/spins/linux/releases/15/Spins/i686/Fedora-15-i686-Spins-CHECKSUM
+ http://fedora-spins.c3sl.ufpr.br/alt/spins/linux/releases/15/Spins/x86_64/Fedora-15-x86_64-Spins-CHECKSUM
+Could someone post a png or gif of the hash for these files here since fedora won't update this until F16(Verne) is out.
+--[[User:Chief Mike|Chief Mike]] 11:29, 18 October 2011 (EDT)
+:sha256sum 95650ec1257670e44466e75059ff8b05f636cd78658a025ae52c8992145f778c  Fedora-15-i686-Live-SoaS.iso
+:md5sum 67dc6fe4625f61d9d51f89c082f3c9c3  Fedora-15-i686-Live-SoaS.iso
+:sha256sum aa18f9dae1fe8d9bde47a45fefd19f2127dfc1001de3c1f76fbc1f85ec576e0d  Fedora-15-x86_64-Live-SoaS.iso
+:md5sum db209baffdef41b7ca029b6e224ed7d1  Fedora-15-x86_64-Live-SoaS.iso
+:: from my copies --[[User:FGrose|FGrose]] 12:30, 18 October 2011 (EDT)