Sugar Labs - User contributions [en]

Machine/bender

2023-07-15T19:09:10Z

MrBIOS:

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD
* Ubuntu 20.04.2 LTS

[[Image:BenderRacked.jpg|thumb|320px]]

== Info ==
Owned by Sugar Labs, Inc.
Hosted by Sonic in Santa Rosa, CA

Bender and Papert are two twin KVM hosts bought by Sugar Labs in 2021.

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Libera.chat IRC network

== Hosting ==

[[Image:SonicColo.jpg|thumb|320px]]

Hosted by Sonic in Santa Rosa CA

== Network configuration ==

Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:

vi /etc/netplan/bender.yaml
netplan generate
netplan apply

=== IPv4 ===

Bender is globally accessible through a public, static IPv4 address

Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonic IP pool" in <code>masters/sugarlabs.org.zone</code>.

* Usable IPv4 addresses: 192.184.220.210 ~ 192.184.220.222 (13 addresses)
* Subnet Mask: 255.255.255.240
* Default Gateway: 192.184.220.209
* DNS: 8.8.8.8, 8.8.4.4

=== IPv6 ===
IPv6 configuration is a bit weird.

* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127

The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.

=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.

There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Virtualization ==

Virtual machines are KVM guests managed with libvirt.

=== Storage ===

All virtual disks come from a pool backed by the main LVM VG:

virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined

virsh # pool-start nvme-pool
Pool nvme-pool started

virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted

virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB

Disks assigned to VMs will appear here:

virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup

Disks can be created, listed and deleted using the vol-* commands:

virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created

virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB

virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted

Please avoid allocating large VM volumes as image file within the host's root filesystem: they're slow and hard to manage. It's ok to use images for test VMs.

Machine/bender

2023-07-15T19:08:14Z

MrBIOS: /* IPv4 */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD
* Ubuntu 20.04.2 LTS

[[Image:BenderRacked.jpg|thumb|320px]]

== Info ==
Owned by Sugar Labs, Inc.
Hosted by Sonic in Santa Rosa, CA

Bender and Papert are two twin KVM hosts bought by Sugar Labs in 2021.

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Libera.chat IRC network

== Hosting ==

[[Image:SonicColo.jpg|thumb|320px]]

Hosted by Sonic in Santa Rosa CA

== Network configuration ==

Network configuration is managed via [https://netplan.io/ netplan]. To modify, do:

vi /etc/netplan/bender.yaml
netplan generate
netplan apply

=== IPv4 ===

Bender is globally accessible through a public, static IPv4 address

Sonic assigned a /28 network to Sugar Labs. IP assignments are managed in our DNS configuration. Search for "Sonic IP pool" in <code>masters/sugarlabs.org.zone</code>.

Usable IPv4 addresses: 192.184.220.210 ~ 192.184.220.222 (13 addresses)
Subnet Mask: 255.255.255.240
Default Gateway: 192.184.220.209
DNS: 8.8.8.8, 8.8.4.4

=== IPv6 ===
IPv6 configuration is a bit weird.

* Public block: 2001:5a8:601:f::/64
* Sonic gateway: 2001:5a8:5:3a::15:0/127
* Transport IP: 2001:5a8:5:3a::15:1/127

The gateway is configured to route all traffic for our netblock to the transport IP, which is currently assigned to bender.

=== Bridges ===
The br0 bridge is created at startup and shared with the virtual machines hosted on Bender. It gives the VMs unfiltered access to the external network. There's no DHCP, all machines must define a static IP configuration, taking care not to stomp onto each other.

There is also a virbr0 bridge created by libvirt on startup from <code>/etc/libvirt/qemu/networks/default.xml</code>. This is a NAT interface and is not meant for VMs directly serving on the Internet.

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Virtualization ==

Virtual machines are KVM guests managed with libvirt.

=== Storage ===

All virtual disks come from a pool backed by the main LVM VG:

virsh # pool-define-as nvme-pool logical --source-name nvme-pool
Pool nvme-pool defined

virsh # pool-start nvme-pool
Pool nvme-pool started

virsh # pool-autostart nvme-pool
Pool nvme-pool marked as autostarted

virsh # pool-info nvme-pool
Name: nvme-pool
UUID: 5812819f-b8bf-484e-98fb-2e100fe83df2
State: running
Persistent: yes
Autostart: yes
Capacity: 1.64 TiB
Allocation: 250.00 GiB
Available: 1.40 TiB

Disks assigned to VMs will appear here:

virsh # vol-list nvme-pool
Name Path
-----------------------------------------
aslo1-root /dev/nvme-pool/aslo1-root
aslo1-srv /dev/nvme-pool/aslo1-srv
backup /dev/nvme-pool/backup

Disks can be created, listed and deleted using the vol-* commands:

virsh # vol-create-as nvme-pool testvm-root 20G
Vol testvm-root created

virsh # vol-info testvm-root --pool nvme-pool
Name: testvm-root
Type: block
Capacity: 20.00 GiB
Allocation: 20.00 GiB

virsh # vol-delete testvm-root --pool nvme-pool
Vol testvm-root deleted

Please avoid allocating large VM volumes as image file within the host's root filesystem: they're slow and hard to manage. It's ok to use images for test VMs.

Mission

2022-02-20T18:58:31Z

MrBIOS:

[[Trademark|Sugar Labs®]] is a volunteer-run project whose mission is to reach global learners and educators with a collection of tools that enable them to explore, discover, create, and reflect in their local language. Sugar Labs distributes these tools freely and encourages its users to appropriate them, taking ownership and responsibility for their learning.

<noinclude>
''Copied from [[Oversight Board/Meeting Minutes-2017-05-05]] with addition of a trademark link.''
</noinclude>

Sugar on a Stick/Downloads

2022-02-16T17:15:25Z

MrBIOS:

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |


[[File:Download Mirabell.png|link=http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220215.iso]]

x86_64 (64-bit)

| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|

| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick/Downloads

2022-02-16T17:13:42Z

MrBIOS: change link to known-working F35 SoaS Respin ISO, with bug fixed

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a 32-bit computer with the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |


[[File:Download Mirabell.png|link=http://download.sugarlabs.org/soas/Fedora-SoaS-Live-x86_64-F35-20220215.iso]]

x86_64 (64-bit)

| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/35/Spins/armhfp/images/Fedora-SoaS-35-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|
See the [https://spins.fedoraproject.org/soas/download/index.html Spins download page] for the following:
* ARM® Technology downloads
* Some support links
| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick

2022-02-16T17:08:25Z

MrBIOS: /* What is Sugar on a Stick? */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]

{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}__NOTOC__</noinclude>

==What is Sugar on a Stick?==
{{:Sugar on a Stick/Downloads}}
=== What's new in Sugar on a Stick? ===
* Sugar [[0.118]], see the [[0.118/Notes|release notes for 0.118]],
* several updated activities,
* based on Fedora 35, see the [[fedoradocs:fedora/f34/release-notes/|release notes for Fedora 35]]
:

==== Known bugs ====

* See also [[fedora:Common_F34_bugs|Common Fedora 35 bugs]].

== Sugar on a Stick installation instructions ==
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|left|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted]. 
# '''Download''' the latest [[Sugar on a Stick/Downloads | Sugar on a Stick]] .iso file. 
# '''Load''': Insert a USB flash drive (or SD Card) with 2 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----
=== GNU/Linux ===
{|style="width: 800px;"
|-
|width="160px" valign=top| [[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
{{:Sugar on a Stick/Linux/Installation}}
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
GNU/Linux users may also want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro, apart from Sugar on a Stick.
----

=== Apple Mac OS X ===
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Macintosh]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
The instructions below are based on the Ubuntu Web page at <http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx>.
# '''Prepare''': These instructions are for '''32-bit''' and '''64-bit''' processors. 
# '''Download''' the latest [[Sugar on a Stick/Downloads|Sugar on a Stick]] .iso file. 
# '''Load''': Here is a simple way to load a bootable USB on a Mac. 
## Enter the Terminal: <code>/Applications/Utilities/Terminal</code>.
## Type <code>diskutil list</code>. You should see all the disk drives you have inserted into your computer.
## Insert the disk drive to which you want to write Sugar on a Stick.
## Type <code>diskutil list</code> again. You should see that your USB drive has been added to the list. If not, wait a while and repeat.
## Type <code>hdiutil convert -format UDRW -o <Sugar on a Stick image file>.img <Sugar on a Stick image file></code> to convert the image into a bootable format.
## Type <code>sudo diskutil unmountDisk <device name></code> to unmount the disk (it will not be ejected).
## Type <code>sudo dd if=<Sugar on a Stick image file>.img.dmg of=<device name> bs=1m</code>. <code>sudo</code> will ask for your password, and then <code>dd</code> will start writing the disk file.
## When <code>dd</code> finishes writing the disk file, type <code>sudo diskutil eject <device name></code>.
# '''Boot''': Insert the USB stick into a USB port on your computer, then reboot and press and hold the Option key while rebooting. You should see a list of all the EFI-recognizable USB drives that can be bootstrapped. If Sugar on a Stick is not one such drive, it cannot be bootstrapped: you need rEFInd (a fork of rEFIt). 
 
:* Have a MacBook? Consider these options:
::[[File:Usb1.png|50px]] [[Testing/Reports/Sugar on a Stick#MacBook Persistent SoaS v5 USB EFI Boot|'''MacBook Persistent SoaS v5 USB EFI Boot''']]
:: [[Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air|Bootable CD of Trisquel 4.5 for MacBook Air]]
:: See other installation variations at [[Sugar Creation Kit]]
::[[File:Apple.gif|30px]] [[Tutorials/Installation/Burn_a_CD.iso_on_a_Mac|'''Burning a CD from an .iso file on a Mac''']]
|}

Alternative [[Macintosh|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----

===Advanced users===
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=olpc:Releases]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:Releases]]'' from OLPC (which may require a [[olpc:Activation_and_developer_keys|developer key]]).

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 
==Some alternate installations==
* Once you download, and then burn or load a Sugar on a Stick (SoaS) .iso file, and boot it, the running Fedora 34 SoaS Live CD/USB may be used to install Fedora with Sugar to a hard disk or a 4 GB USB stick [[Tutorials/Installation/Install with liveinst|with the '''{{Code|liveinst}} command''']].
:- You start with a SoaS LiveOS image, and then load an uncompressed version onto the hard disk or USB stick.

=== Want to contribute to Sugar on a Stick? ===
{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started.

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==
===[[Sugar on a Stick/Beta]]===

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

=== <s>Meetings</s> ===

Communication through the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] has replaced regular meetings.
:We once had weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings.

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
* Older [[:Category:Live USB|portable Sugar distributions]] based on other Linux distributions .
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.

== Previous versions and other subpages index ==
{{Show|Earlier versions of Sugar on a Stick and other project pages can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Local Labs

2022-01-23T19:26:22Z

MrBIOS: /* Notice */

<noinclude>{{TeamHeader|Local Labs|xbgColor=ffb673}}{{TOCright}}</noinclude>

Sugar Labs appreciates the efforts of Local Labs in making the Sugar platform relevant to their local communities. Local Labs around the globe do the following, and more:

* Adapt the technology and pedagogy to an area's culture and resources (e.g, developing activities and content specific to a region)
* Help translate Sugar to the local language(s)
* Support Sugar deployments in area schools
* Create a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable
* Provide for communication,between the local communities and the global Sugar Labs community
* Develop Local content and software that can be used not only for local purposes but also for the overall community
* Host, co-host or partner in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar

Sugar Labs seeks to foster a sense of ownership and associated entrepreneurship with the user communities who support Sugar. Sugar Labs, as the official representative of the project itself, maintains responsibility for setting clear goals and maintaining any necessary infrastructure needed by the project as a whole. In turn, Local Labs dedicate themselves to using Sugar to serve their local communities. But, what is the "business model" for a successful Local Lab? It seems that some necessary conditions for success would be:

* A university connection as a local human resource
* A local pilot user group from which to learn
* A local passion or sub-goal that provides a rational for the work
* Bi-directional communication with Sugar Labs and other Local Labs
* A sustainable and well-defined entrepreneurship model
* A program to reach out to local free-software communities and local industry
* A marketing program or roadmap

What are other considerations? And are these initial "conditions" correct? Your input would be of great value to the efforts of Local Labs everywhere. Please join the discussion.

==Proposals==

*[[Sugar Labs Ghana]] proposal
*[[Sugar Labs DC]] proposal
*[[Sugar Labs Chile]] proposal

==Notice==

Sugar Labs Local Labs are not officially endorsed by or affiliated with Sugar Labs, Inc.

==Subpages==

{{Special:PrefixIndex/Local Labs/}}

[[Category:Local Lab]]
[[Category:Team]]
[[Category:Deployment]]

Finance

2022-01-23T19:25:32Z

MrBIOS: Remove references to our affiliation with SFC, where relevant, as we're now a stand-alone non-profit corporation

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The Treasurer manages finances for Sugar Labs.

== 2017-01-01 to 2017-10-06 ==



<pre>
$ ledger -V -s -S T -d "T&l<=2" -f sugar.ledger bal '/^(Income|Expenses).*Sugar/'
$ -305,599.52 Income:Sugar
$ 230,231.80 Expenses:Sugar
--------------------
$ -75,367.72 SUGAR LABS ASSETS AS OF 2017-10-06 (ignore the minus sign)
</pre>

<pre>
2017 complete financials (until 2017-10-06) from SFConservancy's Sugar/Ledger/sugar.ledger and associated files:

2017-01-26 from 2016-10-09 Expedia.ca - Artemis Papert - Flight - Budget From Search: $1,039 - Turtle Art Day PY 2016 - 1387.78
2017-02-13 from 2017-01-17 from 2016-12-23 from 2016-11-03? REV WIRE OUT - EDGAR QUISPE CHAMBI - Undefined Transaction (for Aymara translation) - 600.00
2017-04-10 from 2017-03-28 MARTIN DANIEL OESTERREICH WEIBERLEN - Domestic Wire Funds - Debit (for Guarani translation) - 900.00
2017-05-05 from 2017-04-13 PAYONEER INC - PAYMENT - ACH Credit - Google, Inc. - GCI 2017 Funds - 7000.00 (6300.00 after SFC's 10% deducted)
2017-06-21 Outreachy - 2017-05 Sponsorship - 6500.00
Ignacio Rodríguez - GCI 2016, 2017-06-05 to 2017-06-08 - 2017-08-16 transaction (1942) to Walter Bender - 1550.96 (covers 2 below)
2017-07-02 Ignacio Rodríguez - American Airlines (MVD-SFO) - Budget from search: $1,451 - GCI 2016 - 1350.96
2017-07-02 Ignacio Rodríguez - M&IE Per Diem - Max $230 - GCI 2016 - 200.00
Samson Goddy - GSoC Mentor Summit 2017-10-13 to 2017-10-15 - 3166.99 (covers 8 below)
2017-09-29 Samson Goddy - JetBlue (LAX-BOS) - Paid by (SFC's) Brett Smith - Sub-budget from search: $242 - Budget from search: $2,748 - Budget from Project: $2,000 - GSoC Mentor Summit 2017 161.20
2017-10-04 from 2017-09-26 Samson Goddy - Emirates (LOS-SFO, BOS-LOS, official books contain typo "Ethiad") - Paid by (SFC's) Brett Smith - Sub-budget from search: $1,400 - Budget from search: $2,748 - Budget from Project: $2,000 - GSoC Mentor Summit 2017 - 1279.14
2017-10-04 from 2017-10-03 SAMSON SAMUEL GODDY - Domestic Wire Funds - Debit (550 + 347.73 via Walter Bender = 202.27 + 695.46) - 897.73
2017-10-04 from 2017-08-14 hnaylor@igc.org - Hilary Naylor - PayPal payment (for Samson Goddy) - 708.00 ($8 fee + covers 4 below)
2017-08-16 Visa - Samson Goddy - GSoC Mentor Summit 2017 - 176.56
2017-08-16 Visa Agent - Samson Goddy - GSoC Mentor Summit 2017 - 138.08
2017-09-10 Grand Ibro Hotel - Samson Goddy - GSoC Mentor Summit 2017 - 55.33
2017-09-11 Samson Goddy - M&IE Per Diem - Max: $367.50 - GSoC Mentor Summit 2017 Visa - 330.03
2017-10-05 from 2017-09-29 Samson Goddy - Arik (PHC-LOS) - Paid by Walter Bender - Sub-budget from search: $257 - Budget from search: $2,748 - Budget from Project: $2,000 - GSoC Mentor Summit 2017 - 120.92

2017 INCOME TO DATE (2017-10-06) *ESTIMATED* FROM ABOVE: $6300.00
2017 EXPENSES TO DATE (2017-10-06) *ESTIMATED* FROM ABOVE: $14105.73

Which do not match the more official numbers below due to various issues like transactions posting in a different financial year, conflicting exchange rates, etc:

$ ledger -V -s -S T -d "T&l<=2" -f sugar.ledger bal '/^(Income|Expenses).*Sugar/' -b 2017
$ -6,300.00 Income:Sugar
$ 11,953.67 Expenses:Sugar
--------------------
$ 5,653.67
</pre>



== 2016-01-01 to 2016-12-31 ==



<pre>
2016 complete financials from SFConservancy's Sugar/Ledger/sugar.ledger and associated files:

Walter Bender - Thailand Conference 2016-02-01 to 2016-02-05 - 2016-04-13 transaction (1808) 1389.29 (covers 6 below)
2015-12-23 Turkish Airlines - Walter Bender - Constructionism 2016 - Flight (BOX-BKK) - 807.22
2015-12-24 King Mongkut's University of Technology Thonburi - Walter Bender - Constructionism 2016 - Conference Registration - 250.00
2016-02-01 Uber - Walter Bender - Constructionism 2016 - Ground Transportation - 30.21
2016-02-01 Hellconia House - Walter Bender - Constructionism 2016 - Hotel - 168.60
2016-02-06 Boston Logan International Airport - Walter Bender - Constructionism 2016 - Parking - 3.00
2016-02-07 ME&I Per Diem - Walter Bender - Constructionism 2016 - 130.26
Devin Ulibarri - Thailand Conference 2016-02-01 to 2016-02-05 - 3656.67 (covers 5 below)
2016-02-01 Hellconia House - Devin Ulibarri - Constructionism 2016 - Hotel - 168.60
2016-02-02 King Mongkut's University of Technology Thonburi - Devin Ulibarri - Constructionism 2016 - Conference Registration - 380.00
2016-02-07 ME&I Per Diem - Devin Ulibarri - Constructionism 2016 - 354.48
2016-04-22 from 2015-12-23 Turkish Airlines (BOS-BKK) - Devin Ulibarri - purchased by Walter Bender - Constructionism 2016 - Flight - 787.31
2016-05-26 for 2016-05-13 Devin Ulibarri - Constructionism 2016 - Consulting Work - 500.00
2016-02-05 from 2015-12-14 GOOGLE INC - BP SETTLE - ACH - CREDIT - 1914.55 (apparently this does not count as 2016 income?)
2016-04-22 from 2016-03-20 EDGAR QUISPE CHAMBI - DOMESTIC WIRE FUNDS - DEBIT (for Aymara translation) - 200.00
2016-05-06 from 2016-02-13 GOOGLE INC - BP SETTLE - ACH CREDIT - 7000.00 (6300.00 after SFC's 10% deducted)
Edgar Quispe Chambi - 2016-05-12 DOMESTIC WIRE FUNDS - DEBIT (Conferences:Simposio Internacial) - 161.88 (covers 6 below)
2016-03-20 Cruz Del Sur - Edgar Quispe Chambi - Bus Transport - 26.66
2016-03-20 Cruz Del Sur - Edgar Quispe Chambi - Bus Transport - 17.48
2016-03-21 Jian Hotel - Edgar Quispe Chambi - Hotel - Partial Reimbursement Per Request - 20.66
2016-03-22 Expresso - Edgar Quispe Chambi - Bus Transport - 5.86
2016-03-22 Cruz Del Sur - Edgar Quispe Chambi - Bus Transport - 32.25
2016-03-22 ME&I Per Diem - Edgar Quispe Chambi - 58.97
Mariah Noelle Villarreal - GCI 2016-06-11 to 2016-06-15 - Flight - transaction 2016-06-13 from 2016-05-09 Jet Blue (BOS-SFO) - 563.20
Samson Goddy - for Yoruba translation - 4000.00 (covers 2 below)
2016-07-01 OGONDA SOLOMON - DOMESTIC WIRE FUNDS - DEBIT - 350.00
2016-10-07 OGONDA SOLOMON - for Samson Goddy - DOMESTIC WIRE FUNDS - DEBIT - 3650.00
2016-08-31 Transfer from Sugar Vanguard to new Treasury Money Market (neither income nor expenditure) - 59972.88
2016-09-12 Google - GSoC 2016 - Sugar Mentor Funds (credit) - 6300.00 (5670.00 after SFC's 10% deducted)
Lionel Laske - GSoc Mentor Summit 2016-10-28 to 2016-10-30 - transaction 2016-11-28 - 824.83 (covers 3 below)
2016-10-24 Aéroports de Paris - Lionel Laské - Parking - GSoC Mentor Summit 2016 - 75.12
2016-10-28 South and East Bay Airport Suttle - Lionel Laské - Ground Transportation - GSoC Mentor Summit 2016 - 40.00
2016-11-28 from 2016-09-09 Expedia.fr (CDG-SFO) - Lionel Laské - Flight - Budget From Search: UNKNOWN - GSoC Mentor Summit 2016 (incl 21.90 currency conversion) - 709.71
Michaël Ohayon - GSoc Mentor Summit 2016-10-28 to 2016-10-30 - 706.26 (covers 2 below)
2016-11-25 from 2016-08-24 United Airlines (CDG-SFO) - Michaël Ohayon - Flight - Budget From Search: $671 - GSoC Mentor Summit 2016 - 670.73
2016-11-25 from 2016-11-01 ME&I Per Diem - Michaël Ohayon - 4 days - Max: $224 - GSoC Mentor Summit 2016 - 35.53
Andrea Vasquez Guerra - 2016-11-28 - Domestic Wire Funds - Debit - 559.00 (covers 3 below)
2016-10-16 Sky Airline (SCL-MVD) - Andrea Vasquez Guerra - Flight - Budget From Search: $412 - Turtle Art Day UY 2016 - 340.00
2016-10-26 despagar.com - Andrea Vasquez Guerra - Hotel, 2 nights - Avg: $94/night, Max: $160/night - Turtle Art Day UY 2016 - 187.40
2016-11-03 ME&I Per Diem - Andrea Vasquez Guerra - 3 days - Max: $230 - Turtle Art Day UY 2016 - 31.60
2016-11-30 from 2016-01-29 onwards - Dividend (credit) - 208.75 (187.88 after SFC 10% deducted; dividend payments do not appear after 2016-11-30, as of 2017-10-06)

2016 INCOME *ESTIMATED* FROM ABOVE: $12178.75
2016 EXPENSES *ESTIMATED* FROM ABOVE: $12061.13

Which do not match the more official numbers below due to various issues like transactions posting in a different financial year, conflicting exchange rates, etc:

$ ledger -V -s -S T -d "T&l<=2" -f sugar.ledger bal '/^(Income|Expenses).*Sugar/' -b 2016 -e 2017
$ -12,200.34 Income:Sugar
$ 10,738.09 Expenses:Sugar
--------------------
$ -1,462.25
</pre>



== Fiscal Year 2015 (1 March 2015 - 29 February 2016) ==

Four fiscal years (2012, 2013, 2014, 2015) are summarized below by Adam Holt, after the Oversight Board received extensive accounting files from SFC late evening of 11 February 2016.

<pre>
PROJECTED ESTIMATE AS OF 11 FEB 2016:
FINAL/ACTUAL YEAR-END NUMBERS FOR 29 FEB 2016 MAY BE VERY DIFFERENT

Income:Conservancy:Donations 900.00
Income:Sugar:Donations 8,100.00
Total Donations 9,000.00
Total Interest Income 28.56
TOTAL INCOME 9,028.56

Expenses:Sugar:Development 550.00
Expenses:Sugar:Conferences:Travel 4,610.46
Expenses:Sugar:Conferences:Travel:Per Diem 30.65
Expenses:Sugar:Trademark:Registration 700.00
TOTAL EXPENSES 5,891.11

Cash 101,375.99
Accounts Receivable 1,914.55
TOTAL ASSETS 103,290.54

Accounts Payable 0.40
Liabilities, Credit Cards 8,639.86
Donated To [Software Freedom] Conservancy 12,683.40
TOTAL LIABILITIES 21,323.66

NET ASSETS: $81,966.88
</pre>

== Fiscal Year 2014 (1 March 2014 - 28 February 2015) ==

<pre>
Income:Conservancy:Donations 4,962.00
Income:Sugar:Donations 44,658.01
Total Donations 49,620.01
Total Interest Income 2.17
TOTAL INCOME 49,622.18

Expenses:Sugar:Conferences:Food 2,176.27
Expenses:Sugar:Conferences:Materials 49.00
Expenses:Sugar:Conferences:Travel 1,991.90
Expenses:Sugar:Conferences:Travel:Per Diem 31.65
Expenses:Sugar:Conferences:Venue 124.00
Expenses:Sugar:Banking Fees 0.01
TOTAL EXPENSES 4,372.83

Cash 99,453.09
Accounts Receivable (0.00)
TOTAL ASSETS 99,453.09

Accounts Payable 0.40
Liabilities, Credit Cards 7,939.86
Donated To [Software Freedom] Conservancy 11,780.54
TOTAL LIABILITIES 19,720.80

NET ASSETS: $79,732.29
</pre>

== Fiscal Year 2013 (1 March 2013 - 28 February 2014) ==

<pre>
Income:Conservancy:Donations 4,911.00
Income:Sugar:Donations 44,199.00
Total Donations 49,110.00
Total Interest Income 4.09
Income:Sugar:Currency Conversion 115.10
TOTAL INCOME 49,229.19

Expenses:Sugar:Development 825.00
Expenses:Sugar:Conferences:Food 1,400.00
Expenses:Sugar:Conferences:Travel 11,160.72
Expenses:Sugar:Conferences:Travel:Per Diem 121.43
Expenses:Sugar:Currency Conversion 38.39
TOTAL EXPENSES 13,545.54

Cash 52,060.38
Accounts Receivable 5,000.00
TOTAL ASSETS 57,060.38

Accounts Payable 2,857.05
Liabilities, Credit Cards 7,939.86
Donated To [Software Freedom] Conservancy 6,818.34
TOTAL LIABILITIES 17,615.25

NET ASSETS: $39,445.13
</pre>

== Fiscal Year 2012 (1 March 2012 - 28 February 2013) ==

<pre>
Income:Conservancy:Donations 1,907.02 (same number appears below as OUTGOING donation, weird)
Income:Sugar:Donations -1706.02 (what is a negative donation? SFC will know?)
Total Donations 201.00
Total Interest Income 7.26
TOTAL INCOME 208.26

Expenses:Sugar:Conferences:Travel 2,317.64
Expenses:Sugar:Banking Fees 5.22
Expenses:Sugar:Currency Conversion 13.41
Expenses:Sugar:Promotional 2,390.00
Expenses:Sugar:Computer Equipment 4,699.29
Expenses:Sugar:Hosting 25.00
TOTAL EXPENSES 9,450.56

Cash 17,359.35
Accounts Receivable 50.00
TOTAL ASSETS 17,409.35

Accounts Payable (0.00)
Liabilities, Credit Cards 6,829.53
Donated To [Software Freedom] Conservancy 1,907.02
TOTAL LIABILITIES 8,736.55

NET ASSETS: $8,672.80
</pre>

== Early 2012 financial snapshot ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end).

* The Current Assets balance is accurate as of January 31, 2012 and is $19,830.84, held as follows:
** $19,830.84 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $19,830.84 USD is earmarked as follows ([http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html source]):
** $9,615.92 USD for Gould Grant
** $1,600.00 USD has been ear-marked to purchase a server
** $8,614.92 USD unrestricted (available for future grants)

''[[User:Robert|Robert Fadel]] (was) providing monthly income and expense details.''

''Balance information is based on a ledger account reconciliation completed on February 24, 2012.''

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

'''Important Note:''' [http://wiki.sugarlabs.org/go/User:Bernie Bernie Innocenti] has immediate permission to approve anybody's requests of $200 of less!

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

Travel funding is subject to the '''[https://sfconservancy.org/projects/policies/conservancy-travel-policy.html Software Freedom Conservancy Travel and Reimbursable Expense Policy.]'''

Please read the policy to understand if you are eligible to ask for funds to cover a trip. Here's a handy shortlist of summary questions:

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

Sugar Labs can book flights direct, but will need the following info to do so:

* Exact itinerary, including specific flights, airports and time, and be sure the total is within the travel policy requirements.
* Passport Information
** Full Name, as it appears on the Passport
** Issue Date
** Expiration date
** Country of Issue
** Gender
** Date of Birth
* Mobile number (For flight change alters, if you want them)
* Frequent flyer numbers for major airlines (if you want the miles credited)
* Seat Preference (either specific seats, or "Aisle vs. Window" preference)
* Meal Preference (if a meal is included in the coach flight)

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

== Archive of transactions ==

=== December 2011 ===

'''End-of-month balance:''' $19,855.84

'''Net change since last month:''' -$452.48

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| Bank Service Charges
| align="center"| -
|
! align="right" |$25.00
|
|-
|Sugar Camp Lima Travel
|
|
! align="right"| $1,706.15
|
|-
| Individual Donations
| Misc
! align="right"| $1,278.23
|
|
|-
|Interest
|Vanguard
! align="right"| $0.44
|
|
|-
!
! align="right"| Total
! align="right"| $1,278.67
! align="right"| $1,731.15
!
|}

=== November 2011 ===

'''End-of-month balance:''' $20,308.32

'''Net change since last month:''' +$173.59

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| Bank Service Charges
| align="center"| -
|
! align="right" |$36.90
|
|-
|Gould Grant Expense
|
|
! align="right"| $89.99
|
|-
| Individual Donations
| Misc
! align="right"| $300.00
|
|
|-
|Interest
|Vanguard
! align="right"| $0.48
|
|
|-
!
! align="right"| Total
! align="right"| $300.48
! align="right"| $126.89
!
|}

=== October 2011 ===

'''End-of-month balance:''' $20,134.73

'''Net change since last month:''' +0.45

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No expenses
|
|
! align="center" |-
|
|-
| Interest
| Vanguard
! align="right"| $0.36
|
|
|-
!
! align="right"| Total
! align="right"| $0.45
! align="center"| -
!
|}

=== September 2011 ===

'''End-of-month balance:''' $20,134.28

'''Net change since last month:''' +0.36

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No expenses
|
|
! align="center" |-
|
|-
| Interest
| Vanguard
! align="right"| $0.36
|
|
|-
!
! align="right"| Total
! align="right"| $0.36
! align="center"| -
!
|}

=== August 2011 ===

'''End-of-month balance:''' $20,133.92

'''Net change since last month:''' -$1,277.86

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| Fundraising
|
|
! align="right" |-$1,278.23
|
|-
| Interest
| Vanguard
! align="right"| $0.37
|
|
|-
!
! align="right"| Total
! align="right"| $0.37
! align="right"| -$1,278.23
!
|}

=== July 2011 ===

'''End-of-month balance:''' $21,411.78

'''Net change since last month:''' +$2,505.49

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No Expenses
| align="center"| -
|
! align="center" |-
|
|-
| Google SoC Support
| Checking
! align="right"| $2,500.00
|
|
|-
| Individual Donations
| Misc
! align="right"| $5.00
|
|
|-
|Interest
|Vanguard
! align="right"| $0.49
|
|
|-
!
! align="right"| Total
! align="right"| $2,505.49
! align="center"| -
!
|}

=== June 2011 ===

'''End-of-month balance:''' $18,906.29

'''Net change since last month:''' +0.75

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No Expenses
|
|
! align="right" |-
|
|-
| Interest
| Vanguard
! align="right"| $0.75
|
|
|-
!
! align="right"| Total
! align="right"| $0.75
! align="right"| -
!
|}

=== May 2011 ===

'''End-of-month balance:''' $18,905.54

'''Net change since last month:''' -$1,273.99

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| EduJam
| align="center"| -
|
! align="right" |$1,100.00
|
|-
| Meetings: NYC 2011
|
|
! align="right"| $200.18
|
|-
| Individual Donations
| Misc
! align="right"| $25.00
|
|
|-
|Interest
|Vanguard
! align="right"| $1.19
|
|
|-
!
! align="right"| Total
! align="right"| $26.19
! align="right"| $1,300.18
!
|}

=== April 2011 ===

'''End-of-month balance:''' $20,179.53

'''Net change since last month:''' -$19,778.90

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| Cycling
| align="center"| -
|
! align="right" |$145,000.00
|
|-
| Durham Cycling Donation
| Checking
! align="right"| $125,000.00
|
|
|-
| Individual Donations
| Misc
! align="right"| $220.00
|
|
|-
|Interest
|Vanguard
! align="right"| $1.10
|
|
|-
!
! align="right"| Total
! align="right"| $125,221.10
! align="right"| $145,000.00
!
|}

=== March 2011 ===

'''End-of-month balance:''' $39,958.43

'''Net change since last month:''' +$20,131.30

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No Expenses
| align="center"| -
|
! align="center" |-
|
|-
| Carhart Cycling Donation
| Checking
! align="right"| $20,000.00
|
|
|-
| Individual Donations
| Misc
! align="right"| $130.00
|
|
|-
|Interest
|Vanguard
! align="right"| $1.30
|
|
|-
!
! align="right"| Total
! align="right"| $20,131.30
! align="center"| -
!
|}

=== February 2011 ===

'''End-of-month balance:''' $19,827.13

'''Net change since last month:''' +1.04

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| No Expenses
| align="center"| -
|
! align="center" |-
|
|-
| Interest
| Vanguard
! align="right"| $1.04
|
|
|-
!
! align="right"| Total
! align="right"| $1.04
! align="center"| -
!
|}

=== January 2011 ===

'''End-of-month balance:''' $19,826.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! width="225" | Item
! width="225" |From/To
! width="100" |Income
! width="100" |Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
! align="right" |-$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest
| Vanguard
! align="right"| $0.92
|
|
|-
!
! align="right"| Total
! align="right"| $0.92
! align="right"| -$1,680.00
!
|}

Crowd funding/Sugar Network

2022-01-23T19:19:13Z

MrBIOS: /* Disclaimer */

== Disclaimer ==

The content of this page is not legally endorsed by or affiliated with Sugar Labs Inc. This is a private initiative of [[#Development team|people]] who take part in the project.

== What is this page about ==

This is a [[wikipedia:Crowd_funding|crowd funding]] initiative to support [[#The project|Sugar Network]] development process. It is intended to be an access point for people who want to donate funds to [[#Development team|development team]] to continue working on [[Harmonic_Distribution/1.0/Roadmap|implementation]].

This page should answer on the following questions:

* [[#Development team|Who we are?]]
* [[#The project|What we are working on?]]
* [[#How to donate|How you can help us to continue working?]]
* [[#Overall progress|How to track the overall progress to see if your help is needed?]]

''Why Wiki page?''

* Wiki page is an intermediate solution until more appropriate model will be found; right now, it will let team working;
* Development team is spread world wide (the same for possible donators) and it is not obvious how to handle donations in such case;
* We are looking for more sustainable and common model that is being [[Oversight_Board/Meeting_Minutes-2012-05-10|discussed]] on Sugar Labs Oversight Board level.

== The project ==

In short, Sugar Network is a system (software and infrastructure) to let people share different types of content, support collaborative work on that content, do that regardless the Internet connectivity.

To learn more about the Sugar Network, consult the following pages:

* [[Sugar Network]] home page,
* [[Sugar_Network/Declaration_of_purpose|declaration of purpose]],
* [[Platform_Team/Sugar_Network|technical pages]].

The plan is working on the 1.0 version during the 2012 year. For detailed information see [[Harmonic Distribution]] [[Harmonic_Distribution/1.0/Roadmap|Roadmap]] and [[Harmonic_Distribution/1.0/Todo#Intermediate_releases|TODO]] pages. To track for intermediate releases, add [[Harmonic_Distribution/1.0/Roadmap|release page]] to your watch list. To monitor development commits, subscribe to [http://git.sugarlabs.org/network Gitorious project]'s [http://git.sugarlabs.org/network.atom feed]. To try current development version, follow the [[Sugar_Network#Try_it|instructions]].

The important note for possible donators, this page is requesting to support development process (literally, writing the code) of community software project which is named ''"Sugar Network"'''. At the same time, such systems require downstream deployment work to make it useful for people in the field. Such deployment work is less predictable and rather important for organizations (like education ministries or Sugar distributors) then for personal donators. Look for [[#The product|Red Azúcar]] for details.

=== The product ===

Red Azúcar is a downstream solution based on Sugar Network and is intended to be a ''"final product"'' to bring Sugar Network to people in the field. It is being created within the Sugar Labs Peru By the Research and Development Team "Somos Azúcar". Most of the work is different to Sugar Network development process. In technical aspects, the focus is shifting to deployment rather than development. In non technical aspects, Red Azúcar is taking care about populating Sugar Network content with materials useful for local people, work with educators and state people, etc. Sugar Network developers also take part in Red Azúcar, but obviously, Red Azúcar involves much more people and requires more resources to work on.

Please, consult the following pages if you are looking for a way to support Red Azúcar:

* [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa Red Azúcar: Proyecto Piloto Hexoquinasa]
* [http://somosazucar.org/2010/05/01/presentacion-proyecto-malla/ Red Azúcar: Proyecto Malla]

You can also send a contact request email to malla AT somosazucar.org the Sugar Labs Peru Oversight Board.

== Development team ==

The development team consists of the following people (in alphabetical order):

* <strike>[[User:alsroot|Aleksey Lim]]</strike> Got funding.
: Location: Russia, Rubtsovsk
: Brief intro: see a [[User:Alsroot#Hi|short bio]]; Sugar Labs contributor since 2008
: Role in project: server side and client library
: Spend time: full time working on the project

* [[User:Laura_Vargas|Laura Vargas]]
: Location: Bogotá, Colombia
: Brief intro: Research and Development at SomosAZUCAR.Org since 2009
: Role in project: UI Designer
: Spend time: split time to work on [[#The product|Red Azúcar]], downstream product

* [[User:Sebastian|Sebastian Silva]]
: Location: Ancón, Perú
: Brief intro: See [[User:Sebastian|member profile]]. Sugar Labs contributor since 2008
: Role in project: webui client developer
: Spend time: split time to work on [[#The product|Red Azúcar]], downstream product

== Overall progress ==

Sugar Network development process is started since the end of 2011. It will continue being developed until implementing 1.0 version (further development will depend on feedback gotten during the implementation process) in any case. The only thing is how much time developers can spend on implementation. And, here we are looking for your help.

{| class="wikitable" border="1"
|-
! scope="col" | '''Accepted / Requested'''
|-
| style="text-align: center; height: 65px" bgcolor="lightgreen" | 4900$/9000$
|-
|}

The ''Requested'' sum is calculated from gentle minimal per developer per month, which is ~500$ multiplied by number of developers (3) and number of months remained in 2012. The ''Accepted'' sum might grow due to reasons like personal sources developers found, donations from this page, or, funding gotten by [[#The product|Red Azúcar]]. The overhead will go to support [[#The product|Red Azúcar]].

== How to donate ==

Send an email to <strike>alsroot@sugarlabs.org,</strike> laura@somosazucar.org and sebastian@somosazucar.org to get in contact with the team.

== Donations ==

* Juan Camilo Lema, 1000$
* Aleksey Lim, 1500$
* Bernie Innocent, 2400$

Trademark

2022-01-23T19:18:20Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

<noinclude>[[Category:Policy]]
[[Category:Oversight board]]
[[Category:Governance]]
</noinclude>
__NOEDITSECTION__

Our goal is to make Sugar a recognized and trusted name in learning. A well-conceived trademark policy is instrumental in achieving this goal: it makes clear trademark-usage arrangements with partners and other FOSS projects. ''We want your participation.'' Please [[#Contact information|contact us]] if you have any questions about our policy.

----

'''SUGAR LABS TRADEMARK POLICY'''

== Purpose ==

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs® remain clear to the public. This is in keeping with our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.

As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program. Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that [[#Other marks used by Sugar Labs|Section 2.5 "Other Marks Used by Sugar Labs"]] provides guidelines for other marks used by Sugar Labs. Sugar Labs, Inc. is the holder of the [http://tmportal.uspto.gov/external/portal/tow?SRCH=Y&isSubmitted=true&details=&SELECT=US+Serial+No&TEXT=77634279# registered mark].

== Guidelines for using the Marks ==

=== Registered trademark symbol on first mention ===

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs®".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

=== Permissions required for usage ===

==== Using the marks without prior written permission ====

You may use the Sugar Labs Marks without prior written permission (subject to the other sections):

#For example, to refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[#Approved licenses|approved license]].
#Or to identify Sugar Labs software as a distinct component of a software offering. Please note however that we prefer that Sugar be described as a "learning environment", not a "desktop", and its programs as "Activities", not "applications".

==== Using the marks with prior written permission ====

You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

#If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in [[#Using the marks without prior written permission|the previous section (2.2.1 "Using the Marks Without Prior Written Permission")]], we encourage you to participate in our label program, designed to help educators recognize your project as a good choice for learning.

Please refer to our [[Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

==== Referring to Sugar Labs ====

You do not need written permission to factually refer to the Sugar Labs project itself, its products, or its protocols.

=== Using the Marks as part of a product name ===

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

=== Prohibited usages of the Marks ===

You may not use the Marks in the following ways:

==== Ways likely to cause confusion ====

In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs marks should be secondary in prominence to the primary context of use in advertising and promotional materials, including graphics on websites, etc.);

==== Ways that indicate a greater degree of association than actually exists ====

In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

==== Ways that imply a designated successor ====

In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

==== Ways that imply favoritism ====

In a way that indicates that Sugar Labs [[Oversight_Board/2009/Meeting_Log-2009-12-18|favors one distribution, platform, product, etc. over another]] except where explicitly indicated in writing by Sugar Labs.

=== Other marks used by Sugar Labs ===

Sugar Labs also uses the following other marks:

==== Sugar on a Stick ====

The "Sugar on a Stick" name and mark is pending registration and is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion. You are free to use "Sugar on a Stick" to refer to the specific Sugar Labs distribution.

==== Sugar Labs Partner ====

"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

==== Sugar Learning Platform ====

"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections [[#Permissions required for usage|2.2 "Permissions Required for Usage"]] and [[#Using the Marks as part of a product name|2.3 "Using the Marks as Part of a Product Name"]] of this policy.

==== Sugar ====

We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

==== Local Sugar Lab ====

The popularity of the Sugar platform has inspired numerous unaffiliated volunteers, developers, and deployment specialists to use Sugar and educate others on how to use Sugar. We affectionately refer to these user communities as "Local Labs," and allow them to refer to themselves as Sugar Labs <Region Name> without written permission (See [[Local_Labs#Local_Labs_Directory]]).

=== Merchandise using the Marks ===

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the [[Marketing_Team/Logo|logo page on the Sugar Labs website.]] Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections Sections [[#Permissions required for usage|2.2 "Permissions Required for Usage"]] and [[#Using the Marks as part of a product name|2.3 "Using the Marks as Part of a Product Name"]] of this policy.

=== Rights reserved by Sugar Labs, Inc ===

Sugar Labs, Inc. reserves the sole right to:

==== Determining compliance ====

Determine compliance with this policy;

==== Modifications of this policy ====

Modify this policy in ways consistent with its mission of protecting the public;

==== Grant exceptions to this policy ====

Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

== Contact information ==

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, or for more information concerning our label program, please contact Sugar Labs by emailing trademark AT sugarlabs.org or by writing to [[Sugar_Labs/Contacts#Mail]].

== Usage examples ==

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

== Approved licenses ==

We have adopted http://opensource.org/docs/osd as a set of approved software and content licenses and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable.

Oversight Board/Next meeting

2022-01-23T19:14:35Z

MrBIOS: /* Agenda items */

=== Next meeting===

* Wednesday, 2022-01-19 at 19:30 UTC, (per agreed motion 2020-06, "meet every two weeks"),
* on Matrix (matrix.org room: Sugar)

==== Agenda items ====

Current draft is published at https://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2021-06-23 (which will later become the minutes for the meeting).

Our agenda is typically negotiated as first item of business in the meeting. Add topics by either;

* write to sugar-devel and slobs at lists dot sugarlabs dot org (the most transparent method), or;
* write to slobs at lists dot sugarlabs dot org (a transparent method), or;
* write to a member of the oversight board (a non-transparent method).
* editing the wiki page for the agenda yourself (before the meeting).

Standing agenda items;

* pending motions from e-mail,
* reports from Ombudsman,
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
* discussion of goals,

Sugar Labs/SFC Fiscal Agreement

2022-01-23T19:13:08Z

MrBIOS:

<noinclude>[[Category:Policy]]</noinclude>

As of 2022, this is a historical document, as Sugar Labs has become an independent, 501(c)3 non-profit corporation.

SOFTWARE FREEDOM CONSERVANCY
FISCAL SPONSORSHIP AGREEMENT

See [[File:AmendedFSASugar.pdf]]

Sugar Labs/Governance/Transactions

2022-01-23T19:06:56Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

== Administrative transactions ==

Sugar Labs is a tax-exempt non-profit 501(c)3 corporation.

accounts-payable AT tix DOT sugarlabs DOT org is the place to write if you’re asking Sugar Labs to send money to someone. This includes reimbursements for travel and other project expenses, contractor payments, payments for conference services, and so on.

accounts-receivable AT tix DOT sugarlabs DOT org is the place to write if Sugar Labs should expect to receive money from someone, or for customer service after they’ve sent Sugar Labs money. Write here if you want Sugar Labs to send an invoice to someone (including invoices after payment), to let Sugar Labs know about conference sponsorships, or to give Sugar Labs a heads-up about what an incoming check is for.

accounts-taxinfo AT tix DOT sugarlabs DOT org is the place to send tax documents like W-8BEN, W-9,

=== Request for payment ===

Some Sugar Labs projects have a budget (e.g., Google Summer of Code). Typically there is a project leader who has put together a budget that has been vetted by the Oversight Board (See [[#Project proposal approval]]). If you have incurred a project-related expense, please submit a copy of your receipt to accounts-payable AT tix DOT sugarlabs DOT org. along with a brief explanation of the expense. Please be sure to include reference to the specific project for which the expense applies.

Similarly, if you need to invoice Sugar Labs, please submit your invoice along with a reference to a project to accounts-payable AT tix DOT sugarlabs DOT org.

'''Please note''' that [[https://wiki.sugarlabs.org/go/Finance finances]] are routinely processed around the ides (15th) of each month. (Hence the latency in payments after approval can be up to 30 days.)

In order to expedite the process, please be sure to include documentation of your expenses: a receipt that shows the price of the purchase or some documentation from a third party (e.g., your credit card company) that shows the specific amount paid.

Also, please also include:
* the reference to the board Transaction approval.
* a brief paragraph explaining what was accomplished, e.g., what you did for the project during your travel.
* How you'd liked to be reimbursed. The four payment options, in order of preference, are:
:1. Issue you a check in USD from a USA bank, sent to you via post. For this option, we just need your postal address.
:2. PayPal. For this, we need an email address that is valid for the Paypal account be paid.
:3. Wire the amount in your local currency to your bank account in your country. For this option, we need all of the following information:
:::SWIFT Code
:::For USA, ACH routing number for incoming payments.
:::Bank Name
:::Bank Address
:::Account Number
:::Full Name of the Account Holder
:::Full Address of Account Holder
:::IBAN (if available, mandatory for Europe)
:::Preferred Currency
:::BIC
:4. Issue you a check in your local currency, sent to you via post. For this option, we just need your postal address and what currency you want.

=== Project proposal approval ===

If you are applying for a grant proposal and wish to include Sugar Labs as a partner, it is necessary to run your draft proposal text by the Executive Director to make sure that it is within the bounds of the Sugar Labs, Inc. mission. Please send a draft slobs AT sugarlabs.org DOT org two weeks ''before'' the proposal is due in order to allow time for review and feedback.

=== License request ===

The [[Sugar_Labs/Governance/Trademark|Sugar Labs trademark policy]] describes the various marks and conditions of usage that are held by Sugar Labs, Inc.. If you are interested in using a Sugar Labs trademark, please contact slobs@sugarlabs.org with the following information:

* a list of which marks are desired to be licensed, along with a full description of how they will be used;
* a description of the current use of any Sugar Labs marks;
* a list of any individuals or corporations that will be participating in the proposed use of the mark;
* a list of any Sugar Labs community members with whom you are currently working;
* information for a primary contact person, including email address and phone number.

Initial contact will be made within two weeks of receipt of a request.

=== Tax receipt request ===

Please contact Sugar Labs regarding tax receipts for donations made to Sugar Labs at accounts-receivable AT tix DOT sugarlabs DOT org.

[[Category:General public]]
[[Category:Governance]]

Featured Books

2022-01-23T19:04:42Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

These books are by authors associated with Sugar Labs about Sugar and OLPC topics. Through the Amazon Affiliate program, clicking through these links to purchase these books from Amazon will result in a small donation to Sugar Labs.

Sugar Labs/Governance/Transactions

2022-01-23T19:04:13Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

== Administrative transactions with the Software Freedom Conservancy ==

Sugar Labs is a tax-exempt non-profit 501(c)3 corporation.

accounts-payable AT tix DOT sugarlabs DOT org is the place to write if you’re asking Conservancy to send money to someone. This includes reimbursements for travel and other project expenses, contractor payments, payments for conference services, and so on.

accounts-receivable AT tix DOT sugarlabs DOT org is the place to write if Conservancy should expect to receive money from someone, or for customer service after they’ve sent the Conservancy money. Write here if you want the Conservancy to send an invoice to someone (including invoices after payment), to let the Conservancy know about conference sponsorships, or to give the Conservancy a heads-up about what an incoming check is for.

accounts-taxinfo AT tix DOT sugarlabs DOT org is the place to send tax documents like W-8BEN, W-9,

=== Request for payment ===

Some Sugar Labs projects have a budget (e.g., Google Summer of Code). Typically there is a project leader who has put together a budget that has been vetted by the Conservancy (See [[#Project proposal approval]]). If you have incurred a project-related expense, please submit a copy of your receipt to accounts-payable AT tix DOT sugarlabs DOT org. along with a brief explanation of the expense. Please be sure to include reference to the specific project for which the expense applies.

Similarly, if you need to invoice Sugar Labs, please submit your invoice along with a reference to a project to accounts-payable AT tix DOT sugarlabs DOT org.

'''Please note''' that [[https://wiki.sugarlabs.org/go/Finance finances]] are routinely processed around the ides (15th) of each month. (Hence the latency in payments after approval can be up to 30 days.)

In order to expedite the process, please be sure to include documentation of your expenses: a receipt that shows the price of the purchase or some documentation from a third party (e.g., your credit card company) that shows the specific amount paid.

Also, please also include:
* the reference to the board Transaction approval.
* a brief paragraph explaining what was accomplished, e.g., what you did for the project during your travel.
* How you'd liked to be reimbursed. The four payment options, in order of preference, are:
:1. Issue you a check in USD from a USA bank, sent to you via post. For this option, we just need your postal address.
:2. PayPal. For this, we need an email address that is valid for the Paypal account be paid.
:3. Wire the amount in your local currency to your bank account in your country. For this option, we need all of the following information:
:::SWIFT Code
:::For USA, ACH routing number for incoming payments.
:::Bank Name
:::Bank Address
:::Account Number
:::Full Name of the Account Holder
:::Full Address of Account Holder
:::IBAN (if available, mandatory for Europe)
:::Preferred Currency
:::BIC
:4. Issue you a check in your local currency, sent to you via post. For this option, we just need your postal address and what currency you want.

=== Project proposal approval ===

If you are applying for a grant proposal and wish to include Sugar Labs as a partner, it is necessary to run your draft proposal text by the Executive Director to make sure that it is within the bounds of the Sugar Labs, Inc. mission. Please send a draft slobs AT sugarlabs.org DOT org two weeks ''before'' the proposal is due in order to allow time for review and feedback.

=== License request ===

The [[Sugar_Labs/Governance/Trademark|Sugar Labs trademark policy]] describes the various marks and conditions of usage that are held by the Conservancy on behalf of Sugar Labs. If you are interested in using a Sugar Labs trademark, please contact conservancy AT sfconservancy DOT org with the following information:

* a list of which marks are desired to be licensed, along with a full description of how they will be used;
* a description of the current use of any Sugar Labs marks;
* a list of any individuals or corporations that will be participating in the proposed use of the mark;
* a list of any Sugar Labs community members with whom you are currently working;
* information for a primary contact person, including email address and phone number.

Initial contact will be made within two weeks of receipt of a request.

=== Tax receipt request ===

Please contact the Software Freedom Conservancy regarding tax receipts for donations made to Sugar Labs at accounts-receivable AT tix DOT sugarlabs DOT org.

[[Category:General public]]
[[Category:Governance]]

Deployment Team/Local Lab MOU

2022-01-23T18:59:40Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Deployment Team}} </noinclude>

'''DRAFT: for discussion purposes only'''

MEMORANDUM OF UNDERSTANDING
BETWEEN SUGAR LABS AND XYZ

This memorandum of understanding (MOU) is made by and between Sugar Labs and XYZ. Sugar Labs, Inc. is a Delaware nonprofit public benefit corporation, which has received recognition of exemption from federal income tax under Section 501(c)(3) of the Internal Revenue Code (IRC) and classification as a public charity under IRC Sections 509(a)(1) and 170(b)(1)(A)(vi). XYZ is an entity local to region ABC.

WHEREAS:

A. The mission of Sugar Labs is to produce, distribute, and support the use of the Sugar learning platform, a free software project.

B. The mission of XYZ is to provide tools for learning to the children of ABC, with the goal to increase the use of computers and the Internet in order to provide the best opportunities for learning and supporting them to participate in a knowledge-based economy.

THEREFORE, THE PARTIES HEREBY AGREE AS FOLLOWS:

1.Sugar Labs and XYZ agree to establish Sugar Labs ABC, a local-to-ABC entity to do software development, deployment, and support, including providing local and regional technical and pedagogical support; creating new learning activities and pedagogical practice; providing localization and internationalization of software, content, and documentation; and providing integration and customization services.

2.Sugar Labs ABC:
:a. will be co-branded entity established in ABC;
:b. will have Sugar Labs and XYZ representation on their board of directors;
:c. will have web presence at abc.sugarlabs.org;
:d. will appoint a representative to Sugar Labs and to XYZ;
:e. will not act as an agent for Sugar Labs nor to take any action inconsistent with the status of Sugar Labs as a public charity;
:f. agrees to abide by the principles of Free Software, open communication, and community participation;
:g. agrees to operate within the scope of the joint learning missions of Sugar Labs.

3.Sugar Labs:
:a. will help identify resources to be utilized by Sugar Labs ABC on technical and pedagogical issues;
:b. will appoint a Sugar Labs member to the Sugar Labs ABC board of directors;
:c. will include Sugar Labs ABC as part of the global Sugar Labs community;
:d. will not charge any license fee for the use of the Sugar Labs brand;
:e. will collect no fees from Sugar Labs ABC.

4.XYZ:
:a. will take ultimate responsibility for Sugar Labs ABC: all community programs, public information work, fund-raising events, processing and acknowledgment of cash and non-cash revenue items, accounts payable and receivable, negotiation of leases and contracts, disbursement of Sugar Labs ABC's funds (including grants), and other activities planned shall be the ultimate responsibility of XYZ and shall be conducted in the name of XYZ;
:b. agrees to pay all reasonable costs incurred by Sugar Labs to support Sugar Labs ABC; Sugar Labs shall notify the authorized representative prior to incurring any significant expenditures and shall provide a periodic report of any such expenses to to the authorized representative.
:c. agrees to establish a research fund to disperse to university and industry applicants within ABC to further advance the Sugar learning platform or its deployment within ABC.

5.Termination. Sugar Labs or XYZ may terminate this Agreement at any time subject to a reasonable effort by both parties to reach an accord regarding any disagreements.

== Spanish version ==

*For an spanish version of this draft MOU please see: http://co.sugarlabs.org/go/Memorando_de_Entendimiento
*Para una version en español de este Memorando en proceso de construcción por favor vea: http://co.sugarlabs.org/go/Memorando_de_Entendimiento

[[Category:Deployment]]

Trademark/Guidelines

2022-01-23T18:58:04Z

MrBIOS:

One of the purposes of the Sugar Labs® Project is to make learning software available in consistent format that the public can come to trust. To achieve this purpose it is important that the technology can quickly be identified and that the recipient knows the technology they are receiving is the official and unmodified version.

=== Current usages ===

For a list of groups who have received permission to use the Sugar Labs trademark, along with copies of their original usage requests, see [[Trademark permissions granted]].

=== Domain names ===

In the past, community members have inquired whether it is permissible to use the Sugar Labs Marks, including the word "Sugar Labs," in an Internet domain name.

Sugar Labs uses subdomains of ''sugarlabs.org'' so that local community sites can form without cost or excessive effort to that community. Details about the process and benefits of a ''sugarlabs.org'' subdomain are located on the [[Local community domains]] wiki page.

For any other use of the Sugar Labs Marks in a domain name, please [[#Contact_information|contact the oversight board]].

=== Trademark Usage Guidelines ===

{| border="1"
! Guideline !! Acceptable-use examples !! Unacceptable-use examples
|-
| When using the Sugar Labs Marks you must provide the proper trademark symbols and a trademark attribution statement. || Use Sugar Labs® for the first instance of the trademark, and include the statement "Sugar Labs is a trademark of Sugar Labs, Inc." || Never using the ® mark for Sugar Labs, nor a trademark statement per the guidelines.
|-
| Always distinguish trademarks from surrounding text with at least initial capital letters or in all capital letters. || Sugar Labs, SUGAR LABS || sugar labs, yoursugarlabs
|-
| Always use proper trademark form and spelling. || Sugar Labs || SuGaR Labs, Suhgah Labs, sugarlabs
|-
| Never use "a" or "the" to refer to an instance of the trademark. Always use a trademark as an adjective modifying a noun, or as a singular noun. || This is a Sugar Labs system. Anyone can install Sugar Labs software. || I put a Sugar Labs on my mom's computer. I have seventeen Sugar on a Sticks running in my lab.
|-
| Never use a trademark as a verb. Trademarks are products or services, never actions. || Install Sugar Labs on your computer. || Sugarize your system today!
|-
| Never use a trademark as a possessive. Instead, the following noun should be used in possessive form or the sentence reworded so there is no possessive. || The desktop of the Sugar Labs interface is very clean. || Sugar Labs' desktop interface is very clean.
|-
| Take care in translating a trademark into another language. || Quiero instalar Azúcar 0.86 en mi sistema. La página principal de la fundación de Sugar Labs es http://sugarlabs.org || La página principal de la fundación de los laboratorios de azúcar es http://sugarlabs.org.
|-
| Never use trademarks to coin new words or names. || ''N/A'' || Sugar Labs Fashion for geeks
|-
| Never alter a trademark in any way including through unapproved fonts or visual identifiers (although we are happy to discuss your ideas). || Proper use of the Sugar Labs logo || Putting a sugar cube on top of the trademark
|-
| Never use or register any trademarks that are confusingly similar to, or a play on, the words Sugar Labs. || ''N/A'' || Sugah Project
|-
| Never combine your company name with the Sugar Labs name or use the Sugar Labs name in a way that it could be perceived that the Sugar Labs Project and your company have an organizational link such as a joint venture. || AcmeEdu uses Sugar Labs software on all its servers. || Bix Max systems are a partnership of Sugar Labs and AcmeEdu.
|-
| Never use the Sugar Labs Marks in a manner that infringes Sugar Labs, Inc. trademark rights or violates any federal, state, or international law. || ''N/A'' || Applying Sugar Labs logo outside permitted uses
|-
| Never use terminology that states or implies that the Sugar Labs Project assumes any responsibility for the performance of your products and services. || AcmeEdu uses Sugar Labs software on all its school computers. || Sugar Labs runs AcmeEdu's school computers.
|-
| Never abbreviate or use any Sugar Labs Marks as an acronym. || ''N/A'' || SugarBar, (Sugar user groups are really beneficial and resourceful)
|-
| The Sugar Labs logo must be hyperlinked to (http://sugarlabs.org/), in contexts where such a hyperlink is technically feasible. || Hyperlinking the logo where feasible || Not hyperlinking the logo where feasible
|}

=== Logo Usage Guidelines ===

For more information about the requirements for logo size, appearance, placement, and other considerations, refer to [[Logo/UsageGuidelines | the Logo/Usage Guidelines]] for the Sugar Labs mark and the [[Legal/Secondary_trademark_usage_guidelines | Secondary Trademark Usage Guidelines]] for the Secondary Mark.

Sugar Labs/Contacts/Mail

2022-01-23T18:55:47Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

You also may contact us by mail:

:Executive Director
:Sugar Labs, Inc.
:2021 E Ben White Blvd #240-1271
:Austin TX 78741
:USA

Sugar Labs/Governance

2022-01-23T18:52:53Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}
[[Category:General public]]
[[Category:Governance]]
[[Category:Policy]]
</noinclude>

==Sugar Labs Rules of Governance==
Please comment on the [[Talk:Sugar Labs/Governance|discussion page]].

----

One of the challenges that free software projects face is the impact of governance on their [[Sugar_Labs/Members|community members]]: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary.

Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making.

===Sugar Labs, Inc.===

Sugar Labs is a 501(c)3 not-for-profit foundation.

The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]).

==== Transactions ====

* [[Sugar_Labs/Governance/Transactions#Request_for_payment|Request for payment]]
* [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]]
* [[Sugar_Labs/Governance/Transactions#License_request|License request]]
* [[Sugar_Labs/Governance/Transactions#Tax_receipt|Tax receipt request]]

===Oversight Board===

The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]].

Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Oversight Board/Minutes]]).

The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board.

The current list of Oversight Board members is on the [[Oversight Board]] page.

'''Election Process'''

The Sugar Labs [[Sugar_Labs/Members|membership]] elects the Oversight Board each August, for terms beginning in September. Members can nominate themselves to run in the election according to each Election's calendar. The election process is overseen by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]], which can be reached at elections at sugarlabs.org.

====Decision Panels====

The Oversight Board's role is to manage the day-to-day affairs of Sugar Labs and to help the community to build consensus. On the rare occasion of a contentious issue on which no general consensus can be reached, the Oversight Board is responsible for convening a Decision Panel. The Oversight Board will be responsible for determining when a Decision Panel is required and for selecting members for the Decision Panel. Members of the Oversight Board are not permitted to serve on a Decision Panel. A Decision Panel will solicit community input, discuss (in private if they deem it necessary), reach a conclusion internally, and produce a report documenting their conclusion. (Anyone may submit advice to a Decision Panel.) The Oversight Board will review and ratify Decision Panel reports.

===Advisory Board===

The [[Sugar Labs/Governance/Advisory Board|Advisory Board]] is made up of organizations and companies that support Sugar Labs. The Advisory Board has no decision-making authority but provides a vehicle for its members to communicate with the Oversight Board and help the Directors guide the overall direction of Sugar and the Sugar Labs Project. The Advisory Board will appoint (up to) three (3) members who will be non-voting attendees of Oversight Board meetings. The Advisory Board will meet up to twice per year.

The Advisory Board consists of representatives from the following Sugar Labs Foundation member corporations and projects.

Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project.

=== Special Interest Groups ===

Special Interest Groups (SIGs) may be established by any member. They can be formed around
any topic and, if they prove to be useful, can be designated as official committees.
SIGs typically organize themselves as [[Sugar Labs/Teams|Teams]], [[:Category:Project|Projects]], or [[Local Labs]].

===Referenda===

At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]], which can be reached at elections at sugarlabs.org.

A 75% vote of all of the members can override an Oversight Board decision.

=== Subpages ===

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Procedures

2022-01-23T18:49:39Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

What follows is one community member's proposal for travel procedures.

===Internal Procedures===

==Internal Procedure #01: "Request for Travel Policy exemptions"==

Before asking for a travel advance, please consider the following questions:
* Is the travel on behalf of Sugar Labs?
* Has the trip been approved by the Sugar Labs oversight board or some designated representative of the board?
* Do the travel plans comply with the Sugar Labs [https://github.com/conservancy/policies/blob/master/Travel/conservancy-travel-policy.md travel policy]?
* Do you need to have a ticket purchased on your behalf? If so, please refer to [https://github.com/conservancy/policies/blob/master/Travel/info-needed-to-book-a-flight-for-someone.txt].
* Do you need cash for local travel and/or per diem expenses?

Anyone traveling on behalf of Sugar Labs may request a travel advance by sending a written request to the oversight board <slobs AT lists.sugarlabs.org>. Be sure to include the reason for your request, the amount requested, the anticipated dates of travel, and answers to the questions above.

The oversight board will discuss the request and may ask for clarification. The criteria for approval include:
* relevance to Sugar Labs
* availability of funds

It may take the board ''up to one week'' to reach its decision, so please make your request as far in advance as possible.

The deliberations of the board will either published on a [https://lists.sugarlabs.org public email list] or in a [https://meeting.sugarlabs.org/sugar-meeting/meetings meeting log]. The decision itself will be documented on [[Oversight_Board/Decisions]].

If the travel advance is approved (by at least four board members) then our Treasurer or Executive Director will communicate the decision on behalf of the applicant.

Sugar Labs/Executive Director

2022-01-23T18:47:36Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

The Executive Director (ED) is responsible for the day-to-day operations of the foundation and reports directly to the [[Oversight Board]]. The ED runs the board meetings and is the point of last recourse in case the board becomes deadlocked.

[[User:Walter|Walter Bender]] was elected by the during the [[Oversight_Board/2008/Log-2008-09-19|2008-09-19 board meeting]] as our first executive director.

Sugar Labs/About

2022-01-23T18:45:59Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

[[Sugar Labs|Sugar Labs®]], a non-profit 501(c)3 corporation, serves as a support base and gathering place for the community of educators and software developers who want to extend the [[What is Sugar?|Sugar learning platform]] and create Sugar-compatible applications.

Sugar is available under the free software [http://www.gnu.org/copyleft/gpl.html GNU General Public License (GPL)] to anyone who wants to use or extend it.

[[Sugar Labs|Learn more about Sugar Labs.]]

Sugar Labs

2022-01-23T18:43:41Z

MrBIOS: Remove references to our affiliation with SFC, as we're now a stand-alone non-profit corporation

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}
[[Category:General public]]
[[Category:Team]]
</noinclude>__TOC__

===Mission===

[[Trademark|Sugar Labs®]] is a volunteer-driven 501(c)3 nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates [[Sugar Labs/Getting Involved|volunteers]] around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking [[Donate|funding]] to accelerate development.

== [[:Category:Team|Teams]] ==
Sugar Labs is organized around overlapping Teams. Please use the '''Community''' panel in the wiki sidebar to visit and explore the work and events for each team.
This [[:Category:Team | ''Team'' category page]] collects all Sugar Labs wiki pages with a ''Team'' tag.
== [[:Category:Project|Projects]] ==
Sugar Labs is working on a few [[:Category:Project|projects]] focused on delivering specific goals in a defined time period. The '''Projects''' panel in the wiki sidebar holds our premier projects. Please also see these project home pages:

| [[Harmonic Distribution]] | [https://sugardextrose.org/ Dextrose] | [[Sugar Creation Kit]] | [[Sugar on a Stick]] |

| [[Replacing Textbooks]] | [[Math4Team |Math4 Project]] |

| [[Summer of Code]] |

== Sugar Labs: a community ==
:::::::for learning and software-development
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs, Inc. and serves as a support base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible applications.

=== Education Goals ===
Sugar is useful only to the extent it is used by the learning community. Thus, Sugar Labs is working with educators around the world to focus on these learning challenges:

* To make Sugar and Sugar activities freely and readily available to learners everywhere
* To explore and share best practices
* To provide a forum for discussion and support for technology for learning
* To provide mechanism for evaluation and dissemination of results.

=== Technical Goals ===
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” Thus Sugar puts an emphasis on “activities” rather than “applications.” The foundation will focus on solving the challenges that are relevant to these aspects of the interface, namely:

* To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
* To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every distribution and every virtual machine—removing hardware-related dependencies wherever possible.
* To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.
* To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.

=== Community Goals ===
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. Sugar Labs would like to help community members start projects that help sustain and grow the Sugar technology and learning communities:

* To provide local and regional technical and pedagogical support.
* To create new learning activities and pedagogical practice.
* To provide localization and internationalization of software, content, and documentation.
* To provide integration and customization services.

=== Principles ===
In order for Sugar to be successful, it needs the participation of a large number of people who share common goals while maintaining independence, so that each participant has the ability to act independently. For these reasons, Sugar Labs subscribes to the principles described [http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/ here], which are the author's own translation of an [http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta original text in Spanish.]

====Identity====
* Clear mission – Fully disclosed objectives.
* Declared commitments – Affinities and aversions explained.
* Declared outside connections – Relationships with other organizations explicitly listed.

====Structure====
* Horizontal organization – Teams and facilitators work on responsibilities and agreements.
* Identified contributors – Who is who, people are reachable.
* Clear responsibilities – Who is in charge of what.
* Activities described – All of the ongoing work is acknowledged.
See [[Wiki_Team/Guide/Wiki_Structure | Wiki Structure]] for a guide to how the wiki models Sugar Labs' structure.

====Operation====
* Open participation – Anybody can access the information and get a first responsibility.
* Meritocracy – Responsibilities are acquired (or lost) based on one's skills, results, and contributors’ support.
* Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.

====Information====
* Regular reports – Reported activities and future plans allow monitoring and participation.
* Information accessible – Even internal operational information is available by default.
*: We try to operate '''''[[Archive/Current_Events/2009-06-10#En_plein_air|en plein air]]'''''.
* Explicit confidentiality – It is explained what matters are confidential, why, and who can access them.

====Goods====
* Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion [[Sugar Labs/Funding|here]].)
* Resources – Inventory of items detailing who contributed what and why.
* Public accounts – It’s clear where the money comes from and where it goes.
* A special [[Sugar Labs/Thank You|thanks]] to our contributors.

=== [[Sugar Labs/Governance|Governance]] ===
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].

==[[Sugar Labs/Roadmap|Roadmap]]==
The [[Sugar Labs/Roadmap|Sugar Community roadmap]] is used to guide our community efforts:
* Mission, Vision, Values
* Distribution
* Deployments
* Quality Assurance
* Infrastructure

==[[Sugar Labs/Current Events|Community News]]==
A [[Sugar Labs/Current Events|current events page]] is updated weekly (usually on Monday morning) with notes from the Sugar Labs community. (The Sugar Digest is also sent to the [http://lists.sugarlabs.org/listinfo/community-news community-news at lists.sugarlabs.org] list and blogged at [http://walterbender.org/ walterbender.org].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit [http://planet.sugarlabs.org planet.sugarlabs.org].)

An '''[[Archive/Current Events|archive]]''' of Sugar Digests is available.

==[[Sugar Labs/Events | Events Calendar]]==
Sugar [[Sugar Labs/Events | community events]] are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats: [[Image:XML.gif|link=http://www.google.com/calendar/feeds/6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com/public/basic]] [[Image:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[Image:HTML.gif|link=http://www.google.com/calendar/embed?src=6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com&ctz=America/New_York]].

Please contact [[User:Walter]] if you'd like to post an event to the calendar. Or simply post it below and it will be included.

== [[Local Labs]] ==
A local Sugar Lab adapts the technology and pedagogy to an area's culture and resources (''e.g.'', developing activities and content specific to a region); helps translate Sugar to the local language(s); supports Sugar deployments in area schools; creates a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable; provides for communication, between the local communities and the global Sugar Labs community; develops Local content and software that can be used not only for local purposes but also for the overall community; hosts, co-hosts or partners in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar.

Please visit these Local Labs:

| [http://co.sugarlabs.org/go/Laboratorios_A

�car_Colombia Sugar Labs Colombia] | [http://cl.sugarlabs.org/go/Página_Principal Sugar Labs Chile] | [[Sugar Labs DC]] | [http://pe.sugarlabs.org/ Sugar Labs Peru] | [http://ar.sugarlabs.org/ Sugar Labs Argentina] |
<div class="NavFrame "><div class="NavHead">'''Local Lab wiki portal''' </div><div class="NavContent">
{|
|[http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Sugar Labs Colombia]
{{#widget:Iframe
|url=http://co.sugarlabs.org
|width=410
|height=342
|border=1
}}
|[http://cl.sugarlabs.org/go/Página_Principal Chile Local Labs]
{{#widget:Iframe
|url=http://cl.sugarlabs.org
|width=410
|height=342
|border=1
}}
|-
|[[Sugar Labs DC]]
{{#widget:Iframe
|url=http://wiki.sugarlabs.org/go/Sugar_Labs_DC
|width=410
|height=342
|border=1
}}
|[http://pe.sugarlabs.org/ Sugar Labs Peru]
{{#widget:Iframe
|url=http://pe.sugarlabs.org/
|width=410
|height=342
|border=1
}}
|-
|[http://ar.sugarlabs.org/ Sugar Labs Argentina]
{{#widget:Iframe
|url=http://ar.sugarlabs.org
|width=410
|height=342
|border=1
}}
| Who's next?
|}
</div></div>

== Subpages index ==
{{Special:PrefixIndex/Sugar_Labs/}}

Sugar Labs/Donate

2021-12-31T18:29:56Z

MrBIOS:

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}
Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but is now an independent 501(c)(3) charitable non-profit organization.



=== Donate Via PayPal ===
Donations via PayPal may be sent to donations@sugarlabs.org, or via https://paypal.me/sugarlabsinc

=== Donate Via Zelle (US Only) ===
Donations via PayPal may be sent via Zelle to donations@sugarlabs.org

=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

International donations via PayPal are preferred, if possible. Otherwise, donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-12-31T18:29:35Z

MrBIOS:

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but is now an independent 501(c)(3) charitable non-profit organization.



=== Donate Via PayPal ===
Donations via PayPal may be sent to donations@sugarlabs.org, or via https://paypal.me/sugarlabsinc

=== Donate Via Zelle (US Only) ===
Donations via PayPal may be sent via Zelle to donations@sugarlabs.org

=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

International donations via PayPal are preferred, if possible. Otherwise, donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-12-31T18:27:21Z

MrBIOS: /* From outside the US */

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but has become an independent entity.





=== Via PayPal ===
Donations via PayPal may be sent to donations@sugarlabs.org, or via https://paypal.me/sugarlabsinc

=== Via Zelle (US Only) ===
Donations via PayPal may be sent via Zelle to donations@sugarlabs.org

=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

International donations via PayPal are preferred, if possible. Otherwise, donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-12-31T18:26:19Z

MrBIOS: /* Via PayPal */

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but has become an independent entity.





=== Via PayPal ===
Donations via PayPal may be sent to donations@sugarlabs.org, or via https://paypal.me/sugarlabsinc

=== Via Zelle (US Only) ===
Donations via PayPal may be sent via Zelle to donations@sugarlabs.org

=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

Donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-12-31T18:26:00Z

MrBIOS: Additional donation methods

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but has become an independent entity.





=== Via PayPal ===
Donations via PayPal may be sent to donations@sugarlabs.org, or via https://paypal.me/sugarlabsinc

=== Via Zelle (US Only)
Donations via PayPal may be sent via Zelle to donations@sugarlabs.org

=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

Donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-07-27T16:11:42Z

MrBIOS:

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but has become an independent entity.





=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

Donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Sugar Labs/Donate

2021-07-27T16:11:03Z

MrBIOS: Reflect the fact that we're now an independent entity, not affiliated with Software Freedom Conservancy

{{Graduate | HIGH PRIORITY. Also grab recent transactions/etc wikicode from https://trisquel.info/en/donate }}

As of 2021, Sugar Labs Inc. is a 501(c)(3) not-for-profit organization incorporated in the state of New Jersey of the United States of America; its [[wikipedia:Employer_Identification_Number|EIN]] is 84-3289298.

Sugar Labs was formerly a member project of the [http://sfconservancy.org/ Software Freedom Conservancy], a 501(c)(3) not-for-profit organization, but has become an independent entity.





=== Mail us a check ===

Please make your check payable to:
:'''Sugar Labs, Inc.'''

Checks should then be mailed to:
:Sugar Labs, Inc.
:2028 E Ben White Blvd #240-1271
:Austin, TX 78741
:USA

=== From outside the US ===

Donations from banks outside of the US or not in US dollars should be handled by wire.
Donors wishing to send a wire should contact <donations@sugarlabs.org>

You might want to team up with other donors to save international banking fees.
Feel free to post to [[Mailing_Lists#General_Lists|iaep]] to say you wish to make a donation.

Machine/lightwave

2021-07-03T05:20:43Z

MrBIOS: /* Admins */

== Hostnames ==

* lightwave.sugarlabs.org
* ns1.sugarlabs.org

== General Information ==

This is intended to be a high security machine managed by core members
of the Infrastructure team.

It currently runs only our [[Service/Nameservers|Master Nameserver]] and PGP keyserver ([http://keys.sugarlabs.org:11371/pks/lookup?op=stats keys.sugarlabs.org]).
In the future, it will also run the master LDAP, which is currently
hosted on Sunjammer.

== Location ==

KVM virtual machine hosted on [[Machine/justice]]

== Admins ==

* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Libera.chat
* [[User:sascha_silbe|Sascha Silbe]], silbe on #sugar Libera.chat

== Notes ==

* Please don't install web applications or other insecure services on this machine.
* Please don't create additional user accounts on this machine.

Machine/justice

2021-07-03T02:13:20Z

MrBIOS: /* Admins */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* justice.sugarlabs.org
* freedom.sugarlabs.org

== Info ==

Freedom and Justice are two twin KVM hosts bought by Sugar Labs in 2012.

Justice is currently our primary VM hosting box, while freedom is a hot-standby running some secondary services in docker containers and backups.

== Machines ==

The following machines services are hosted:

* [[Machine/lightwave]], [[Service/Nameservers]],
* [[Machine/pootle]], [[Service/translate]],
* [[Service/activities]] aslo,
* [[Machine/library]],
* [[Machine/aslo4]],
* [[Machine/jita]], [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],

== Hardware ==
* 2U rack-mountable case
* Motherboard Supermicro H8SGL (or maybe H8SGL-F)
* 8-core Opteron 6212 @ 1.7GHz
* 64GB RAM
* 2x1TB RAID1

== Management ==
The two servers have SMT management cards from Supermicro with a seriously awful web interface:
* [http://justice-mng.sugarlabs.org/ justice-mng.sugarlabs.org]
* [http://freedom-mng.sugarlabs.org/ freedom-mng.sugarlas.org]
Of course you need a separate account. Full KVM support requires the Java browser plugin (yuck!), so we mostly use them for the big reset button in case a server hangs (it happened about once per year).

'''Use a long, unguessable password, but not one you're also using elsewhere! A few years ago, a backdoor was discovered in this firmware which would reveal all passwords in plaintext with a simple telnet! Also, login uses unencrypted http.'''

It's also possible to talk to the management card from Linux using ipmitool.

Both cards are running firmware version 3.16, which patched a huge backdoor that would trivially reveal all passwords in plaintext. No kidding. There's a [https://www.supermicro.com/support/resources/bios_ipmi.php?vendor=2&keywords=H8S newer firmware version], but attempts to update to it failed with both Chrome and Firefox (error: "413 - Request Entity Too Large"). I suspect a bug in their http POST implementation :-(

== Software ==
* Justice: Ubuntu 18.04 LTS Bionic
* Freedom: Ubuntu 18.04 LTS Bionic

== Location ==
Hosted by the [http://media.mit.edu/ MIT Media Lab] in server room E15-243.

== Admins ==
* [[User:MrBIOS|Alex Perez]], aperezbios on #sugar libera.chat
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar libera.chat
* [[User:Srevin03|Srevin Saju]], srevinsaju on #sugar on libera.chat

== Network configuration ==
Justice is globally accessible through public, static IPv4.
The IPv6 /64 subnet (6to4) is currently experimental and not associated with AAAA records.

== Hosted VMs ==
All KVM virtual machines are managed by libvirtd.

See [[Sysadmin/Add virtual machine]] for creating new VMs.

{{Special:PrefixIndex/{{PAGENAME}}/}}

Machine/justice

2021-07-03T02:12:19Z

MrBIOS: /* Machines */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* justice.sugarlabs.org
* freedom.sugarlabs.org

== Info ==

Freedom and Justice are two twin KVM hosts bought by Sugar Labs in 2012.

Justice is currently our primary VM hosting box, while freedom is a hot-standby running some secondary services in docker containers and backups.

== Machines ==

The following machines services are hosted:

* [[Machine/lightwave]], [[Service/Nameservers]],
* [[Machine/pootle]], [[Service/translate]],
* [[Service/activities]] aslo,
* [[Machine/library]],
* [[Machine/aslo4]],
* [[Machine/jita]], [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],

== Hardware ==
* 2U rack-mountable case
* Motherboard Supermicro H8SGL (or maybe H8SGL-F)
* 8-core Opteron 6212 @ 1.7GHz
* 64GB RAM
* 2x1TB RAID1

== Management ==
The two servers have SMT management cards from Supermicro with a seriously awful web interface:
* [http://justice-mng.sugarlabs.org/ justice-mng.sugarlabs.org]
* [http://freedom-mng.sugarlabs.org/ freedom-mng.sugarlas.org]
Of course you need a separate account. Full KVM support requires the Java browser plugin (yuck!), so we mostly use them for the big reset button in case a server hangs (it happened about once per year).

'''Use a long, unguessable password, but not one you're also using elsewhere! A few years ago, a backdoor was discovered in this firmware which would reveal all passwords in plaintext with a simple telnet! Also, login uses unencrypted http.'''

It's also possible to talk to the management card from Linux using ipmitool.

Both cards are running firmware version 3.16, which patched a huge backdoor that would trivially reveal all passwords in plaintext. No kidding. There's a [https://www.supermicro.com/support/resources/bios_ipmi.php?vendor=2&keywords=H8S newer firmware version], but attempts to update to it failed with both Chrome and Firefox (error: "413 - Request Entity Too Large"). I suspect a bug in their http POST implementation :-(

== Software ==
* Justice: Ubuntu 18.04 LTS Bionic
* Freedom: Ubuntu 18.04 LTS Bionic

== Location ==
Hosted by the [http://media.mit.edu/ MIT Media Lab] in server room E15-243.

== Admins ==
* [[User:MrBIOS|Alex Perez]], aperezbios on #sugar Freenode
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Freenode
* [[User:Scg|Samuel Cantero]], scg on #sugar Freenode
* [[User:SAMdroid|Sam]], samdroid on #sugar on Freenode
* [[User:Srevin03|Srevin Saju]], srevinsaju on #sugar on Freenode

== Network configuration ==
Justice is globally accessible through public, static IPv4.
The IPv6 /64 subnet (6to4) is currently experimental and not associated with AAAA records.

== Hosted VMs ==
All KVM virtual machines are managed by libvirtd.

See [[Sysadmin/Add virtual machine]] for creating new VMs.

{{Special:PrefixIndex/{{PAGENAME}}/}}

Machine/bender

2021-07-03T00:55:12Z

MrBIOS: /* Network configuration */

Machine/bender

2021-07-03T00:44:18Z

MrBIOS: /* Admins */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD
* Ubuntu 20.04.2 LTS

== Info ==
Owned by Sugar Labs, Inc.
Hosted by Sonic in Santa Rosa, CA

Bender and Papert are two twin KVM hosts bought by Sugar Labs in 2021.

== Admins ==
* [[User:MrBIOS|Alex Perez]], MrBIOS on #sugar Libera.chat IRC network
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Libera.chat IRC network

== Network configuration ==

Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.

Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
to it: 2002:5395:9edc::/48.

The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.
The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together
several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works
naturally, without the need to add any special routing rules on bender.

The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:

ip addr add 2002:5395:9edc:1::1/64 dev virbr0

To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:

interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;

#bernie: subnet 1 of our /48 6to4 on Develer Consiagnet
prefix 2002:5395:9edc:1::1/64
{
AdvOnLink on;
AdvAutonomous on;
};
};

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Hosted VMs ==
All buildslaves currently run off bender as KVM virtual machines managed by libvirtd.

The machines are not globally addressable on IPv4 and are only reachable by IPv6. The
IPv6 address is dynamically configured by radvd to a subnet of the public 6to4 net.

All the VMs are in /srv/images. See the README in the same directory.

They have been created with

virt-install --name buildslave-name --ram 512 \
--disk path=/srv/images/buildslave-name.img,size=10
--network network:default \
--location "mirror-http-address" \
--extra-args="console=tty0 console=ttyS0,115200n8 serial"

Machine/bender

2021-07-03T00:43:06Z

MrBIOS: /* Location */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD
* Ubuntu 20.04.2 LTS

== Info ==
Owned by Sugar Labs, Inc.
Hosted by Sonic in Santa Rosa, CA

Bender and Papert are two twin KVM hosts bought by Sugar Labs in 2021.

== Admins ==
* [[User:Bernie|Bernie Innocenti]], _bernie on #sugar Freenode
* [[User:dnarvaez|Daniel Narvaez]], dnarvaez on #sugar Freenode
* Stefano Fedrigo <aleph AT develer.com>, sometimes _aleph on Freenode (local access, office hours CET)
* Develer Infrastructure <it AT lists.develer.com> (local access, office hours CET)

== Network configuration ==

Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.

Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
to it: 2002:5395:9edc::/48.

The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.
The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together
several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works
naturally, without the need to add any special routing rules on bender.

The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:

ip addr add 2002:5395:9edc:1::1/64 dev virbr0

To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:

interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;

#bernie: subnet 1 of our /48 6to4 on Develer Consiagnet
prefix 2002:5395:9edc:1::1/64
{
AdvOnLink on;
AdvAutonomous on;
};
};

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Hosted VMs ==
All buildslaves currently run off bender as KVM virtual machines managed by libvirtd.

The machines are not globally addressable on IPv4 and are only reachable by IPv6. The
IPv6 address is dynamically configured by radvd to a subnet of the public 6to4 net.

All the VMs are in /srv/images. See the README in the same directory.

They have been created with

virt-install --name buildslave-name --ram 512 \
--disk path=/srv/images/buildslave-name.img,size=10
--network network:default \
--location "mirror-http-address" \
--extra-args="console=tty0 console=ttyS0,115200n8 serial"

Machine/bender

2021-07-03T00:30:43Z

MrBIOS: /* Hardware */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* HPE ProLiant DL360 Gen10 1RU server
** Dual socket, current configuration has one CPU
* [https://ark.intel.com/content/www/us/en/ark/products/199342/intel-xeon-gold-5218r-processor-27-5m-cache-2-10-ghz.html Xeon Gold 5218R]
** 20 cores/40 threads
** 2.1GHz base frequency, 4.0GHz max turbo frequency
** 27.5MB of cache
* 64GB RAM
* 2TB NVMe SSD
* Ubuntu 20.04.2 LTS

== Location ==
Hosted by [http://www.develer.com/ Develer]

== Admins ==
* [[User:Bernie|Bernie Innocenti]], _bernie on #sugar Freenode
* [[User:dnarvaez|Daniel Narvaez]], dnarvaez on #sugar Freenode
* Stefano Fedrigo <aleph AT develer.com>, sometimes _aleph on Freenode (local access, office hours CET)
* Develer Infrastructure <it AT lists.develer.com> (local access, office hours CET)

== Network configuration ==

Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.

Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
to it: 2002:5395:9edc::/48.

The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.
The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together
several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works
naturally, without the need to add any special routing rules on bender.

The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:

ip addr add 2002:5395:9edc:1::1/64 dev virbr0

To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:

interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;

#bernie: subnet 1 of our /48 6to4 on Develer Consiagnet
prefix 2002:5395:9edc:1::1/64
{
AdvOnLink on;
AdvAutonomous on;
};
};

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Hosted VMs ==
All buildslaves currently run off bender as KVM virtual machines managed by libvirtd.

The machines are not globally addressable on IPv4 and are only reachable by IPv6. The
IPv6 address is dynamically configured by radvd to a subnet of the public 6to4 net.

All the VMs are in /srv/images. See the README in the same directory.

They have been created with

virt-install --name buildslave-name --ram 512 \
--disk path=/srv/images/buildslave-name.img,size=10
--network network:default \
--location "mirror-http-address" \
--extra-args="console=tty0 console=ttyS0,115200n8 serial"

Machine/bender

2021-07-03T00:26:16Z

MrBIOS: /* Hostnames */

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==
* bender.sugarlabs.org

== Hardware ==
* Crappy minitower
* Core 2 Duo 1.8GHz
* 6GB RAM
* 2x1TB RAID1, 2x320GB RAID1
* Fedora 13 x86_64

== Location ==
Hosted by [http://www.develer.com/ Develer]

== Admins ==
* [[User:Bernie|Bernie Innocenti]], _bernie on #sugar Freenode
* [[User:dnarvaez|Daniel Narvaez]], dnarvaez on #sugar Freenode
* Stefano Fedrigo <aleph AT develer.com>, sometimes _aleph on Freenode (local access, office hours CET)
* Develer Infrastructure <it AT lists.develer.com> (local access, office hours CET)

== Network configuration ==

Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.

Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
to it: 2002:5395:9edc::/48.

The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.
The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together
several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works
naturally, without the need to add any special routing rules on bender.

The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:

ip addr add 2002:5395:9edc:1::1/64 dev virbr0

To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:

interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;

#bernie: subnet 1 of our /48 6to4 on Develer Consiagnet
prefix 2002:5395:9edc:1::1/64
{
AdvOnLink on;
AdvAutonomous on;
};
};

Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.

== Hosted VMs ==
All buildslaves currently run off bender as KVM virtual machines managed by libvirtd.

The machines are not globally addressable on IPv4 and are only reachable by IPv6. The
IPv6 address is dynamically configured by radvd to a subnet of the public 6to4 net.

All the VMs are in /srv/images. See the README in the same directory.

They have been created with

virt-install --name buildslave-name --ram 512 \
--disk path=/srv/images/buildslave-name.img,size=10
--network network:default \
--location "mirror-http-address" \
--extra-args="console=tty0 console=ttyS0,115200n8 serial"

Machine

2021-07-03T00:25:40Z

MrBIOS: /* Physical */

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>

Computing hardware or virtual machines maintained by the Sugar Labs [[Infrastructure Team]].

== Physical ==

* [[Machine/justice]]
* [[Machine/freedom]]
* [[Machine/bender]]
* [[Machine/papert]]

== Virtual ==

* [[Machine/lightwave]], with [[Service/Nameservers]],
* [[Machine/pootle]], with [[Service/translate]], or https://translate.laptop.org,
* [[Machine/aslo]], with [[Service/activities]] aslo, or https://activities.laptop.org,
* [[Machine/library]],
* [[Machine/aslo3]], with [[Service/activities3]] aslo-v3, https://github.com/sugarlabs/aslo-v3,
* [[Machine/jita]], with [[Service/git]], [[Service/jabber]], [[Service/meeting]], [[Service/obs]], [[Service/chat]], [[Service/cgit]], [[Service/blacklist]], [[Service/stats]],
* [[Machine/amnesia]],
* [[Machine/beacon]], 

== Containers ==

* org.sugarlabs.bugs
* org.sugarlabs.developer-rebuilder
* org.sugarlabs.www-rebuilder
* org.sugarlabs.use-socialhelp
* org.sugarlabs.socialhelp_sso
* local_discourse/app
* org.turtleartday.www-rebuilder
* org.sugarlabs.help-rebuilder

== Student Listing ==

This list was made by a GCI 2018 student.

* [[Machine/backup]]
* [[Machine/bender]]
* [[Machine/freedom]]
* [[Machine/jita]]
* [[Machine/justice]]
* [[Machine/lightwave]]
* [[Machine/pootle]]
* [[Machine/schools]]
* [[Machine/schoolserver]]
* [[Machine/trinity]]

== Automatic Listing ==

This list is generated automatically from Wiki pages that have a prefix of "Machine". It may contain subpages of machines. It may contain machines that have been decommissioned; kept as historical data against future need.

{{Special:PrefixIndex/Machine/}}

[[Image:Sugarlabs systems.jpg|frame]]

Sugar on a Stick/Beta

2021-06-16T01:17:08Z

MrBIOS: /* SoaS nightly builds */

<noinclude>
[[Category:Live USB]]
</noinclude>
==SoaS nightly builds==
[https://www.happyassassin.net/nightlies.html Fedora nightly-composes page] - Look for the '''SoaS live''' section well down in the table.
* See [[Fedora 35]], [[Testing/Reports/Sugar on a Stick]] for testing results.

==Install, test, report==
* See [[Sugar on a Stick/Installation]]
**Note that with larger images one may need to adjust the overlay or home folder size in order to fit the installation onto a 1-GB USB device (for example, with soas-x86_64-20101004.16.iso (503 MB), {{Code|--home-size-mb 190}} was needed), otherwise, the filesystem will get corrupted during the creation of the home folder as the disc space is exhausted.

* [[0.112/Testing|Sugar 0.112 Testing]]
* [[Sugar on a Stick QA]]
* [[Sugar on a Stick/Bugs]]
* [[BugSquad/Bug Report]]

Supporting distributions

2021-06-08T22:57:04Z

MrBIOS:

<noinclude>
[[Category:Supported systems]]
</noinclude>

Sugar is supported by several GNU/Linux distributions. Sugar Labs does not support any specific distribution, but does focus development on Fedora and Debian, which helps SoaS and Ubuntu.

{| style="text-align: left"
!Logo!!Name!!Notes
|-
|[[File:Soas-avocado.svg|200px|link=Sugar_on_a_Stick]]||[[Sugar on a Stick]]|| Live system of the Sugar Learning Environment
|-
|[[File:Fedora-small.jpg|link=Fedora]]||[[Fedora]]||Fedora 34
|- style="height: 55px"
|[[File:Ubuntu-small.jpg|link=Ubuntu]]||[[Ubuntu]]||Ubuntu 18.04 Bionic
|-
|[[File:Debian-small.jpg|link=Debian]]||[[Debian]]||Debian Stretch, see also [[Live Build]]
|- style="height: 55px"
|[[File:Olpc_logo.png|middle|200px|link=OLPC:Releases]]||[[OLPC:Releases|OLPC OS 16.04]]||OLPC OS for OLPC NL3 laptops based on Ubuntu 16.04 Xenial
|-
|[[File:Olpc_logo.png|middle|200px|link=OLPC:Releases]]||[[OLPC:Releases|OLPC OS 13.x]]||OLPC OS for OLPC XO laptops based on Fedora 18
|-
|[[File:Suse-small.jpg|link=OpenSUSE]]||[[OpenSUSE|openSUSE]]||Part of an Linux for Education (Li-f-e) series
|-
|[[File:Trisquel_icon.png|link=Trisquel_On_A_Sugar_Toast]]||[[Trisquel_On_A_Sugar_Toast |Trisquel Toast]]||Based on Ubuntu
|}

{{Note/note|Please note:|
* Development changes occur rapidly, and the text here lags the current state of systems development.
* For the latest information on any development project, visit their work sites.}}

Sugar on a Stick

2021-06-08T22:55:02Z

MrBIOS: /* Some alternate installations */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]

{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}__NOTOC__</noinclude>

==What is Sugar on a Stick?==
{{:Sugar on a Stick/Downloads}}
=== What's new in Sugar on a Stick? ===
* Sugar [[0.118]], see the [[0.118/Notes|release notes for 0.113]],
* several updated activities,
* based on Fedora 34, see the [[fedoradocs:fedora/f34/release-notes/|release notes for Fedora 34]]
:

==== Known bugs ====

* See also [[fedora:Common_F34_bugs|Common Fedora 34 bugs]].

== Sugar on a Stick installation instructions ==
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|left|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted]. 
# '''Download''' the latest [[Sugar on a Stick/Downloads | Sugar on a Stick]] .iso file. 
# '''Load''': Insert a USB flash drive (or SD Card) with 2 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----
=== GNU/Linux ===
{|style="width: 800px;"
|-
|width="160px" valign=top| [[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
{{:Sugar on a Stick/Linux/Installation}}
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
GNU/Linux users may also want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro, apart from Sugar on a Stick.
----

=== Apple Mac OS X ===
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Macintosh]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
The instructions below are based on the Ubuntu Web page at <http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx>.
# '''Prepare''': These instructions are for '''32-bit''' and '''64-bit''' processors. 
# '''Download''' the latest [[Sugar on a Stick/Downloads|Sugar on a Stick]] .iso file. 
# '''Load''': Here is a simple way to load a bootable USB on a Mac. 
## Enter the Terminal: <code>/Applications/Utilities/Terminal</code>.
## Type <code>diskutil list</code>. You should see all the disk drives you have inserted into your computer.
## Insert the disk drive to which you want to write Sugar on a Stick.
## Type <code>diskutil list</code> again. You should see that your USB drive has been added to the list. If not, wait a while and repeat.
## Type <code>hdiutil convert -format UDRW -o <Sugar on a Stick image file>.img <Sugar on a Stick image file></code> to convert the image into a bootable format.
## Type <code>sudo diskutil unmountDisk <device name></code> to unmount the disk (it will not be ejected).
## Type <code>sudo dd if=<Sugar on a Stick image file>.img.dmg of=<device name> bs=1m</code>. <code>sudo</code> will ask for your password, and then <code>dd</code> will start writing the disk file.
## When <code>dd</code> finishes writing the disk file, type <code>sudo diskutil eject <device name></code>.
# '''Boot''': Insert the USB stick into a USB port on your computer, then reboot and press and hold the Option key while rebooting. You should see a list of all the EFI-recognizable USB drives that can be bootstrapped. If Sugar on a Stick is not one such drive, it cannot be bootstrapped: you need rEFInd (a fork of rEFIt). 
 
:* Have a MacBook? Consider these options:
::[[File:Usb1.png|50px]] [[Testing/Reports/Sugar on a Stick#MacBook Persistent SoaS v5 USB EFI Boot|'''MacBook Persistent SoaS v5 USB EFI Boot''']]
:: [[Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air|Bootable CD of Trisquel 4.5 for MacBook Air]]
:: See other installation variations at [[Sugar Creation Kit]]
::[[File:Apple.gif|30px]] [[Tutorials/Installation/Burn_a_CD.iso_on_a_Mac|'''Burning a CD from an .iso file on a Mac''']]
|}

Alternative [[Macintosh|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----

===Advanced users===
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=olpc:Releases]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:Releases]]'' from OLPC (which may require a [[olpc:Activation_and_developer_keys|developer key]]).

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 
==Some alternate installations==
* Once you download, and then burn or load a Sugar on a Stick (SoaS) .iso file, and boot it, the running Fedora 34 SoaS Live CD/USB may be used to install Fedora with Sugar to a hard disk or a 4 GB USB stick [[Tutorials/Installation/Install with liveinst|with the '''{{Code|liveinst}} command''']].
:- You start with a SoaS LiveOS image, and then load an uncompressed version onto the hard disk or USB stick.

=== Want to contribute to Sugar on a Stick? ===
{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started.

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==
===[[Sugar on a Stick/Beta]]===

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

=== <s>Meetings</s> ===

Communication through the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] has replaced regular meetings.
:We once had weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings.

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
* Older [[:Category:Live USB|portable Sugar distributions]] based on other Linux distributions .
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.

== Previous versions and other subpages index ==
{{Show|Earlier versions of Sugar on a Stick and other project pages can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick

2021-06-08T22:54:41Z

MrBIOS: Remove PowerPC Mac links, Fedora no longer supports PPC

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]

{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}__NOTOC__</noinclude>

==What is Sugar on a Stick?==
{{:Sugar on a Stick/Downloads}}
=== What's new in Sugar on a Stick? ===
* Sugar [[0.118]], see the [[0.118/Notes|release notes for 0.113]],
* several updated activities,
* based on Fedora 34, see the [[fedoradocs:fedora/f34/release-notes/|release notes for Fedora 34]]
:

==== Known bugs ====

* See also [[fedora:Common_F34_bugs|Common Fedora 34 bugs]].

== Sugar on a Stick installation instructions ==
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|left|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted]. 
# '''Download''' the latest [[Sugar on a Stick/Downloads | Sugar on a Stick]] .iso file. 
# '''Load''': Insert a USB flash drive (or SD Card) with 2 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----
=== GNU/Linux ===
{|style="width: 800px;"
|-
|width="160px" valign=top| [[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
{{:Sugar on a Stick/Linux/Installation}}
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
GNU/Linux users may also want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro, apart from Sugar on a Stick.
----

=== Apple Mac OS X ===
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Macintosh]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
The instructions below are based on the Ubuntu Web page at <http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx>.
# '''Prepare''': These instructions are for '''32-bit''' and '''64-bit''' processors. 
# '''Download''' the latest [[Sugar on a Stick/Downloads|Sugar on a Stick]] .iso file. 
# '''Load''': Here is a simple way to load a bootable USB on a Mac. 
## Enter the Terminal: <code>/Applications/Utilities/Terminal</code>.
## Type <code>diskutil list</code>. You should see all the disk drives you have inserted into your computer.
## Insert the disk drive to which you want to write Sugar on a Stick.
## Type <code>diskutil list</code> again. You should see that your USB drive has been added to the list. If not, wait a while and repeat.
## Type <code>hdiutil convert -format UDRW -o <Sugar on a Stick image file>.img <Sugar on a Stick image file></code> to convert the image into a bootable format.
## Type <code>sudo diskutil unmountDisk <device name></code> to unmount the disk (it will not be ejected).
## Type <code>sudo dd if=<Sugar on a Stick image file>.img.dmg of=<device name> bs=1m</code>. <code>sudo</code> will ask for your password, and then <code>dd</code> will start writing the disk file.
## When <code>dd</code> finishes writing the disk file, type <code>sudo diskutil eject <device name></code>.
# '''Boot''': Insert the USB stick into a USB port on your computer, then reboot and press and hold the Option key while rebooting. You should see a list of all the EFI-recognizable USB drives that can be bootstrapped. If Sugar on a Stick is not one such drive, it cannot be bootstrapped: you need rEFInd (a fork of rEFIt). 
 
:* Have a MacBook? Consider these options:
::[[File:Usb1.png|50px]] [[Testing/Reports/Sugar on a Stick#MacBook Persistent SoaS v5 USB EFI Boot|'''MacBook Persistent SoaS v5 USB EFI Boot''']]
:: [[Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air|Bootable CD of Trisquel 4.5 for MacBook Air]]
:: See other installation variations at [[Sugar Creation Kit]]
::[[File:Apple.gif|30px]] [[Tutorials/Installation/Burn_a_CD.iso_on_a_Mac|'''Burning a CD from an .iso file on a Mac''']]
|}

Alternative [[Macintosh|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----

===Advanced users===
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=olpc:Releases]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:Releases]]'' from OLPC (which may require a [[olpc:Activation_and_developer_keys|developer key]]).

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 
==Some alternate installations==
* Once you download, and then burn or load a Sugar on a Stick (SoaS) .iso file, and boot it, the running Fedora 30 SoaS Live CD/USB may be used to install Fedora with Sugar to a hard disk or a 4 GB USB stick [[Tutorials/Installation/Install with liveinst|with the '''{{Code|liveinst}} command''']].
:- You start with a SoaS LiveOS image, and then load an uncompressed version onto the hard disk or USB stick.

=== Want to contribute to Sugar on a Stick? ===
{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started.

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==
===[[Sugar on a Stick/Beta]]===

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

=== <s>Meetings</s> ===

Communication through the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] has replaced regular meetings.
:We once had weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings.

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
* Older [[:Category:Live USB|portable Sugar distributions]] based on other Linux distributions .
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.

== Previous versions and other subpages index ==
{{Show|Earlier versions of Sugar on a Stick and other project pages can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick

2021-06-08T22:53:11Z

MrBIOS: Update to SoaS 34

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]

{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}__NOTOC__</noinclude>

==What is Sugar on a Stick?==
{{:Sugar on a Stick/Downloads}}
=== What's new in Sugar on a Stick? ===
* Sugar [[0.118]], see the [[0.118/Notes|release notes for 0.113]],
* several updated activities,
* based on Fedora 34, see the [[fedoradocs:fedora/f34/release-notes/|release notes for Fedora 34]]
:

==== Known bugs ====

* See also [[fedora:Common_F34_bugs|Common Fedora 34 bugs]].

== Sugar on a Stick installation instructions ==
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|left|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted]. 
# '''Download''' the latest [[Sugar on a Stick/Downloads | Sugar on a Stick]] .iso file. 
# '''Load''': Insert a USB flash drive (or SD Card) with 2 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----
=== GNU/Linux ===
{|style="width: 800px;"
|-
|width="160px" valign=top| [[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
{{:Sugar on a Stick/Linux/Installation}}
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
GNU/Linux users may also want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro, apart from Sugar on a Stick.
----

=== Apple Mac OS X ===
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Macintosh]]
 
[[File:Download Mirabell.png|left|link=Sugar on a Stick/Downloads]]
[[File:USB flash drive.jpg|156px|link=Sugar on a Stick/Downloads]]
|valign=top|
The instructions below are based on the Ubuntu Web page at <http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-mac-osx>.
# '''Prepare''': These instructions are for '''32-bit''' and '''64-bit''' processors. 
# '''Download''' the latest [[Sugar on a Stick/Downloads|Sugar on a Stick]] .iso file. 
# '''Load''': Here is a simple way to load a bootable USB on a Mac. 
## Enter the Terminal: <code>/Applications/Utilities/Terminal</code>.
## Type <code>diskutil list</code>. You should see all the disk drives you have inserted into your computer.
## Insert the disk drive to which you want to write Sugar on a Stick.
## Type <code>diskutil list</code> again. You should see that your USB drive has been added to the list. If not, wait a while and repeat.
## Type <code>hdiutil convert -format UDRW -o <Sugar on a Stick image file>.img <Sugar on a Stick image file></code> to convert the image into a bootable format.
## Type <code>sudo diskutil unmountDisk <device name></code> to unmount the disk (it will not be ejected).
## Type <code>sudo dd if=<Sugar on a Stick image file>.img.dmg of=<device name> bs=1m</code>. <code>sudo</code> will ask for your password, and then <code>dd</code> will start writing the disk file.
## When <code>dd</code> finishes writing the disk file, type <code>sudo diskutil eject <device name></code>.
# '''Boot''': Insert the USB stick into a USB port on your computer, then reboot and press and hold the Option key while rebooting. You should see a list of all the EFI-recognizable USB drives that can be bootstrapped. If Sugar on a Stick is not one such drive, it cannot be bootstrapped: you need rEFInd (a fork of rEFIt). 
 
:* Have a MacBook? Consider these options:
::[[File:Usb1.png|50px]] [[Testing/Reports/Sugar on a Stick#MacBook Persistent SoaS v5 USB EFI Boot|'''MacBook Persistent SoaS v5 USB EFI Boot''']]
:: [[Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air|Bootable CD of Trisquel 4.5 for MacBook Air]]
:: See other installation variations at [[Sugar Creation Kit]]
::[[File:Apple.gif|30px]] [[Tutorials/Installation/Burn_a_CD.iso_on_a_Mac|'''Burning a CD from an .iso file on a Mac''']]
:* Have an iBook or PowerPC Mac?
:: See [[Ubuntu/PPC]] and [[fedora:Architectures/PowerPC]].
|}

Alternative [[Macintosh|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Getting Started/Explore|guide to exploring Sugar]].
----

===Advanced users===
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=olpc:Releases]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:Releases]]'' from OLPC (which may require a [[olpc:Activation_and_developer_keys|developer key]]).

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 
==Some alternate installations==
* Once you download, and then burn or load a Sugar on a Stick (SoaS) .iso file, and boot it, the running Fedora 30 SoaS Live CD/USB may be used to install Fedora with Sugar to a hard disk or a 4 GB USB stick [[Tutorials/Installation/Install with liveinst|with the '''{{Code|liveinst}} command''']].
:- You start with a SoaS LiveOS image, and then load an uncompressed version onto the hard disk or USB stick.

=== Want to contribute to Sugar on a Stick? ===
{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started.

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[Sugar on a Stick/Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==
===[[Sugar on a Stick/Beta]]===

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

=== <s>Meetings</s> ===

Communication through the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] has replaced regular meetings.
:We once had weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings.

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* For deployments lacking easy Internet access, one can turn a computer into a '''Sugar on a Stick Creation Station'''. The [[Sugar Creation Kit]] includes the materials you need to create Live USB sticks sticks and to install additional Activities, along with documentation and previous versions of Sugar on a Stick.
* Older [[:Category:Live USB|portable Sugar distributions]] based on other Linux distributions .
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.

== Previous versions and other subpages index ==
{{Show|Earlier versions of Sugar on a Stick and other project pages can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick/Downloads

2021-06-08T22:50:01Z

MrBIOS:

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

A more recent version of Sugar is available on the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34-1.2.iso]]
x86_64 (64-bit), see [https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/ How to install].
|-
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/armhfp/images/Fedora-SoaS-34-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|
See the [https://spins.fedoraproject.org/soas/download/index.html Spins download page] for the following:
* ARM® Technology downloads
* Some support links
| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick/Downloads

2021-06-08T22:48:41Z

MrBIOS: Update download links for SoaS Fedora 34

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

A more recent version of Sugar is available on the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34-1.2.iso]]
x86_64 (64-bit), see [https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/ How to install].
|-
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/armhfp/images/Fedora-SoaS-34-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

See also;

* [[Sugar on a Stick/Download/hashes|How to verify downloads]].
* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|
See the [https://spins.fedoraproject.org/soas/download/index.html Spins download page] for the following:
* ARM® Technology downloads
* Some support links
| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Sugar on a Stick/Downloads

2021-06-08T22:47:24Z

MrBIOS:

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}</noinclude>__NOTOC__
{|
|-
| rowspan="4" style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickAvocado-320px.png|320px|left|link=https://spins.fedoraproject.org/soas/]]
| colspan="2" style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [https://fedoraproject.org/wiki/Overview Fedora®] [https://spins.fedoraproject.org/soas Spin] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]].

Sugar on a Stick will run on
* any 64-bit Notebook, Laptop, or Desktop computer, with a minimum of 1GB RAM, that can run Linux, Windows or macOS, using a USB thumbdrive or stick, as a [[wikipedia:Live USB|Live USB]],
* a Raspberry Pi 2 or 3, using a microSD card, or;
* any computer as a virtual machine.

You can use Sugar on a Stick to demo Sugar almost anywhere without disturbing the contents of the computer you use, and if people like what they see, you can [[Tutorials/Installation/Install with liveinst|install]] Sugar on a Stick to their hard drives or other sticks from the demo stick.

Our most recent working version of Sugar on a Stick was released on '''23 April 2021''' with '''Fedora 34'''.
(Unfortunately, SoaS 33 suffers from a startup problem and this problem has been fixed but they'll be no new image until SoaS34 when Fedora34 is released, you can download this [https://dl.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34-1.2.iso rawhide image] for testing.)

A more recent version of Sugar is available on the TOAST version of Sugar (Trisquel on a Sugar Toast). See [[Trisquel On A Sugar Toast]].

|- style="border: 0; border-width: 0; text-align: center"
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=[https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-34-1.2.iso]]
x86_64 (64-bit), see [https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/ How to install].
|-
| colspan="2" style="border: 0; border-width: 0; text-align: left" |
[[File:Download Mirabell.png|link=https://download.fedoraproject.org/pub/fedora/linux/releases/34/Spins/armhfp/images/Fedora-SoaS-34-1.2.armhfp.raw.xz]]
armhfp Raspberry Pi 2 or 3, see [https://github.com/sugarlabs/sugar/blob/master/docs/rpi-soas.md How to install].
|-
| colspan="3" style="border: 0; border-width: 0; text-align: left" |

See also;

* [[Sugar on a Stick/Download/hashes|How to verify downloads]].
* How to quickly demonstrate: ([[Sugar on a Stick/Installation Process|English]]), ([[Sugar on a Stick/Proceso de instalacion|en español]])

|-
|
See the [https://spins.fedoraproject.org/soas/download/index.html Spins download page] for the following:
* ARM® Technology downloads
* Some support links
| colspan="2" |

|}

''Fedora and the Infinity design logo are trademarks of Red Hat, Inc.''

Oversight Board/Meeting Minutes-2021-02-17

2021-02-23T23:21:44Z

MrBIOS: switch to <nowiki> preformatted block of text for log

== SLOB Meeting -- February 17, 2021 ==

Attending: Walter, Claudia, Lionel, Perrie, MrBios

From the community: Sum2it, srevinsaju

== Topics ==

=== Finances ===

No transactions as of yet in 2021

=== Ombudsman ===

Nothing to report, although Walter will write some text to make it more obvious in our Code of Conduct that we have an ombudsman.

=== SFC ===

Claudia reported no new correspondence

=== GSoC ===

Perrie submitted the application to great acclaim

=== GSoD ===

We discussed using Summer of Documentation to prepare materials in support of teachers.

Perrie and Samson will lay the groundwork for our application

=== Workshops ===

Walter will be giving a workshop to teachers in Brazil on the 19th which could serve as a model for future Sugar Labs workshops.

=== Web Site ===

We discussed the need for some updates, including more focus on Flatpack, Sugarizer, etc. And a section on more academic papers in support of our activities. Perrie has a design proposal.

=== Matrix ===

There was consensus that Matrix worked well and we will try it again at the next meeting.

=== Next Meeting ===

3 March 2021

We have invited the new president of OLPC, Mariana Ludmila Cortés to join us in a discussion.

=== Log ===
<nowiki>walterbender: hello every... any SLOB members here? hmm. holding a meeting in Matrix seems to be a fail :P
llaske_ (@freenode_llaske_:matrix.org) joined the room.
llaske_ (@llaske_:matrix.org): Is there a channel for the SLOB meeting?
walterbender: here but no one seems to have come to the meeting (except you) I even remembered to send a reminder
llaske_ (@llaske_:matrix.org): I've got a message telling that I've not right to do audio in the channel Yes I've seen your reminder
callaurrea: Hi everyone
walterbender: Hi callaurrea glad you made it
llaske_ (@llaske_:matrix.org): Hi
callaurrea: Thanks for the reminder
walterbender: I suppose we could try using the video call mechanism, but lets see if anyone else shows up. Meanwhile, I can report on a few things that don't need much discussion/debate.
Finances: no transactions yet in 2021.
mrbios: hi folks.
walterbender: We have a quorum. Great.
mrbios: I have conflicting meetings but am in both :)
walterbender: Sorry. Maybe at the end we can discuss finding a better time for everyone?
callaurrea: good idea, walterbender
walterbender: Anyway, re Finances, a concern was raised about our spending $$ on lawyers. This is all related to the hopefully one-time process of setting up the non-profit org in the US. It is the only time in our project's history that we have had legal expenses. I don't know if it could have been done otherwise. But it is not something we should see repeated.
llaske_ (@llaske_:matrix.org): Make sense and this work is documented from month.
walterbender: all in all, we have spent about US $500 per year on average for legal over the lifetime of the org... pretty reasonable
llaske_ (@llaske_:matrix.org): I don't think there is a real concern
walterbender: certainly nothing "corrupt" about it any other finance questions/concerns?
llaske_ (@llaske_:matrix.org): Nope. I was very surprised by the Martin message.
walterbender: (The sum total of expenses for which I cannot find receipts is $20.)
callaurrea: I don't think we could have done the work well without the expenses
walterbender: Again, not seemingly a major concern. Re the ombudsman, nothing to report, although I wish, if Martin had concerns, he would have approached Pattie before sending his very public admonishment. Maybe we need to better publicize the fact that we have an ombudsperson?
llaske_ (@llaske_:matrix.org): May be we could answer Martin publicly about this
walterbender: I will try to come up with some language to include in our code of conduct document.
perrieee joined the room.
walterbender: Alex has been speaking with him (and both Alex and I wrote to him off list).
perrieee: Hi everyone
walterbender: hi perrieee
perrieee: sorry I am late
llaske_ (@llaske_:matrix.org): Hi Perrie
walterbender: perrieee: can you see the backlog?
perrieee: yes I can
walterbender: callaurrea: anything to report from SFC?
llaske_ (@llaske_:matrix.org): BTW another subject for our agenda: GSoC. Our application has been completed by Perrie (thanks). It's on the way. Result is expected March 9th
walterbender: Yes... I was going to say a public thank you to Perrie, Lionel and Jui
callaurrea: Nothing. Other than my communication with them about the W-9 form, which happened in January No communication Thanks you, Perrie Lionel and Jui can you share the info? it would be good to include important highlights from the application into the minutes
walterbender: Perrie, maybe you could include the text of the application somewhere is the GSoC repo? So we don't have to hunt down all those numbers again next year. maybe as a wiki page?
perrieee: sure .. I can put that together and share tomorrow
walterbender: thx https://github.com/sugarlabs/GSoC/wiki
perrieee: but this is what our profile correctly looks like
walterbender: Meanwhile, we can continue to add project ideas... Does anyone know much about the Google Summer of Doc program? Deadlines, etc?
sum2it joined the room.
walterbender: We've been discussing it in a thread somewhere
perrieee: for ideas, I want to bring up the project for a redesign of our website again: https://github.com/sugarlabs/GSoC/pull/91#issuecomment-776364048 now the time frame has been shortened
walterbender: I think we should apply and focus on materials to support teachers to take advantage of our tools. callaurrea: you'd be a great mentor for that theme
callaurrea: Love to
llaske_ (@llaske_:matrix.org): Clearly teachers material will be great. It's often asked for Sugarizer on the field
llaske_ (@llaske_:matrix.org): But I don't know if it could be a proposal for GSoD. Which people could really write this sort of doc ?
walterbender: perrieee: (I will share the log and minutes) llaske_: if we find someone who can write well, we can help shape the content
callaurrea: Speaking about OLCP. Mariana may have ideas for other topics? should we reach out to her to establish connections?
walterbender: callaurrea: yes... I have been chatting with her on FB A friend of ours just became the new president of OLPC
llaske_ (@llaske_:matrix.org): Oh really ? who is it?
walterbender: Mariana She is interested in deepening the ties to Sugar Labs
llaske_ (@llaske_:matrix.org): Cool
callaurrea: we can invite her to present at one of our meetings... vision, where they are, etc.?
walterbender: Mariana Ludmila Cortés -- I am not sure of her OLPC email callaurrea: great idea I will see if she can join us in two weeks.
sum2it: Hi all, just joined and read the backlog.
walterbender: I just asked her if she can join us for a discussion in 2 weeks :P hi sum2it any other discussion topics? I gave a talk to a bunch of teachers in Brazil last week and am following up with a workshop this Friday.
callaurrea: missed that
walterbender: Arranged through USP any other discussion topics?
perrieee: yes ... what is the plan for the website refresh?
callaurrea: can we add the link to your sat workshop to the minutes?
walterbender: callaurrea: yes... I will add it
perrieee: I was personally thinking this GSoc will be a good time
callaurrea: we said we will begin with some of those activities... for our packages
walterbender: perrieee: I think it is a reasonable scope for a scaled back GSoC but we do need to have a concrete proposal as to how the new website is tangibly better -- both in terms of the visitor experience and maintenance overhead
perrieee: There is already a design drafted set ... I can share that again
llaske_ (@llaske_:matrix.org): I think we should do a light update of our website just to mention that SugarLabs is now Sugar, MusicBlocks and Sugarizer. But it could be done outside of GSoC in my opinion
walterbender: callaurrea: hopefully my Friday workshop can be a rehearsal for the (bi-?) monthly Sugar Labs workshops
srevinsaju (@srevinsaju:matrix.org): (I am not a part of SLOBS), but our website update mechanism has been broken since 2020 January
llaske_ (@llaske_:matrix.org): srevinsaju: sounds like a priority to fix it first
perrieee: https://www.figma.com/proto/iVvHw3nrOCjBi3FfCOM4PC/Sugar-refresh?node-id=924%3A1&scaling=min-zoom
srevinsaju (@srevinsaju:matrix.org): some changes like the Flathub by tchx84 and others are missing,
callaurrea: Is it Fridays
perrieee: this is a draft, texts will change ... but yeah
walterbender: my USP workshop happens to be Friday... that is all the Sugar Labs ones can be whenever you think best perrieee: I will take a look... it sounds like no matter what we need to make some updates so it is good that you have put thought into it * walterbender would like a section on background reading too * walterbender is writing a book chapter right now on Music Blocks he could share
perrieee: do you mean something like a story behind SL
walterbender: callaurrea: https://zoom.us/j/98734210784?pwd=b0xHenJuQVpKY3VBd3Y2NFJHRnlDQT09 Password: 422968 (at 2:30 US East Coast -- 19:30 UTC)
sum2it: Will it be a part of a larger book?
walterbender: perrieee: I mean simply a list of papers about Sugar, Sugarizer, Music Blocks, etc. for someone interested in some of the pedagogy
callaurrea: Sat at 2:30 pm?
perrieee: oh oh coool yeah sure
walterbender: sum2it: a friend is putting together a collection of essays in celebration of the 50th anniversary of Seymour and Cynthia's 20 things to do with a computer paper. I am writing about thing #11 -- music callaurrea: Friday :smile: * walterbender does not know how to use meojis or type emoji
sum2it: walterbender Happy to help with drafts and/or editing, anytime.
walterbender: https://dspace.mit.edu/handle/1721.1/5836
walterbender
callaurrea: we have one paper
walterbender: callaurrea: we have the Turtle Blocks one you, Cynthia and I wrote :P
callaurrea: yes!!
walterbender: sum2it: if you wanna read/comment on my draft, you are more than welcome.
sum2it: Will do.
walterbender: https://docs.google.com/document/d/1qTGRsQfOmLvR5V2Y_iD9y58MRqK9MHXTS7HFh6a-wGw/edit?usp=sharing
sum2it: Thanks.
walterbender: Any other business? I want to be respectful of the time
llaske_ (@llaske_:matrix.org): That's all on my side
walterbender: Did someone volunteer to follow up on Google Summer of Documentation?
perrieee: I can do a follow up
walterbender: thx
perrieee: Samson and I :)
walterbender: What did everyone think of using Matrix?
callaurrea: I am ok with it
llaske_ (@llaske_:matrix.org): It's like an IRC++
perrieee: I like the experience ...
sum2it: This is good
walterbender: I feel like it is a bit more inclusive than our video calls (and easier for the person writing up the minutes -- he says selfishly) So, lets use it again next time? I will let you know if Mariana can join us.
callaurrea: agree
llaske_ (@llaske_:matrix.org): okay
perrieee: agree
sum2it: +1
walterbender: OK. Until next time, feel free to ping me here thanks everyone
sum2it: Bye
llaske_ (@llaske_:matrix.org): Thanks all. Bye
sum2it: Thanks all
perrieee: bye, thanks all'''</nowiki>

Oversight Board/Meeting Minutes-2021-02-17

2021-02-23T23:16:38Z

MrBIOS:

== SLOB Meeting -- February 17, 2021 ==

Attending: Walter, Claudia, Lionel, Perrie, MrBios

From the community: Sum2it, srevinsaju

== Topics ==

=== Finances ===

No transactions as of yet in 2021

=== Ombudsman ===

Nothing to report, although Walter will write some text to make it more obvious in our Code of Conduct that we have an ombudsman.

=== SFC ===

Claudia reported no new correspondence

=== GSoC ===

Perrie submitted the application to great acclaim

=== GSoD ===

We discussed using Summer of Documentation to prepare materials in support of teachers.

Perrie and Samson will lay the groundwork for our application

=== Workshops ===

Walter will be giving a workshop to teachers in Brazil on the 19th which could serve as a model for future Sugar Labs workshops.

=== Web Site ===

We discussed the need for some updates, including more focus on Flatpack, Sugarizer, etc. And a section on more academic papers in support of our activities. Perrie has a design proposal.

=== Matrix ===

There was consensus that Matrix worked well and we will try it again at the next meeting.

=== Next Meeting ===

3 March 2021

We have invited the new president of OLPC, Mariana Ludmila Cortés to join us in a discussion.

=== Log ===
'''walterbender: hello every... any SLOB members here? hmm. holding a meeting in Matrix seems to be a fail :P

llaske_ (@freenode_llaske_:matrix.org) joined the room.
llaske_ (@llaske_:matrix.org): Is there a channel for the SLOB meeting?

walterbender: here but no one seems to have come to the meeting (except you) I even remembered to send a reminder

llaske_ (@llaske_:matrix.org): I've got a message telling that I've not right to do audio in the channel Yes I've seen your reminder

callaurrea: Hi everyone

walterbender: Hi callaurrea glad you made it

llaske_ (@llaske_:matrix.org): Hi

callaurrea: Thanks for the reminder

walterbender: I suppose we could try using the video call mechanism, but lets see if anyone else shows up. Meanwhile, I can report on a few things that don't need much discussion/debate.

Finances: no transactions yet in 2021.

mrbios: hi folks.

walterbender: We have a quorum. Great.

mrbios: I have conflicting meetings but am in both :)

walterbender: Sorry. Maybe at the end we can discuss finding a better time for everyone?

callaurrea: good idea, walterbender

walterbender: Anyway, re Finances, a concern was raised about our spending $$ on lawyers. This is all related to the hopefully one-time process of setting up the non-profit org in the US. It is the only time in our project's history that we have had legal expenses. I don't know if it could have been done otherwise. But it is not something we should see repeated.

llaske_ (@llaske_:matrix.org): Make sense and this work is documented from month.

walterbender: all in all, we have spent about US $500 per year on average for legal over the lifetime of the org... pretty reasonable

llaske_ (@llaske_:matrix.org): I don't think there is a real concern

walterbender: certainly nothing "corrupt" about it any other finance questions/concerns?

llaske_ (@llaske_:matrix.org): Nope. I was very surprised by the Martin message.

walterbender: (The sum total of expenses for which I cannot find receipts is $20.)

callaurrea: I don't think we could have done the work well without the expenses

walterbender: Again, not seemingly a major concern. Re the ombudsman, nothing to report, although I wish, if Martin had concerns, he would have approached Pattie before sending his very public admonishment. Maybe we need to better publicize the fact that we have an ombudsperson?

llaske_ (@llaske_:matrix.org): May be we could answer Martin publicly about this

walterbender: I will try to come up with some language to include in our code of conduct document.

perrieee joined the room.

walterbender: Alex has been speaking with him (and both Alex and I wrote to him off list).

perrieee: Hi everyone

walterbender: hi perrieee

perrieee: sorry I am late

llaske_ (@llaske_:matrix.org): Hi Perrie

walterbender: perrieee: can you see the backlog?

perrieee: yes I can

walterbender: callaurrea: anything to report from SFC?

llaske_ (@llaske_:matrix.org): BTW another subject for our agenda: GSoC. Our application has been completed by Perrie (thanks). It's on the way. Result is expected March 9th

walterbender: Yes... I was going to say a public thank you to Perrie, Lionel and Jui

callaurrea: Nothing. Other than my communication with them about the W-9 form, which happened in January No communication Thanks you, Perrie Lionel and Jui can you share the info? it would be good to include important highlights from the application into the minutes

walterbender: Perrie, maybe you could include the text of the application somewhere is the GSoC repo? So we don't have to hunt down all those numbers again next year. maybe as a wiki page?

perrieee: sure .. I can put that together and share tomorrow

walterbender: thx https://github.com/sugarlabs/GSoC/wiki

perrieee: but this is what our profile correctly looks like

walterbender: Meanwhile, we can continue to add project ideas... Does anyone know much about the Google Summer of Doc program? Deadlines, etc?

sum2it joined the room.

walterbender: We've been discussing it in a thread somewhere

perrieee: for ideas, I want to bring up the project for a redesign of our website again: https://github.com/sugarlabs/GSoC/pull/91#issuecomment-776364048 now the time frame has been shortened

walterbender: I think we should apply and focus on materials to support teachers to take advantage of our tools. callaurrea: you'd be a great mentor for that theme

callaurrea: Love to

llaske_ (@llaske_:matrix.org): Clearly teachers material will be great. It's often asked for Sugarizer on the field

llaske_ (@llaske_:matrix.org): But I don't know if it could be a proposal for GSoD. Which people could really write this sort of doc ?

walterbender: perrieee: (I will share the log and minutes) llaske_: if we find someone who can write well, we can help shape the content

callaurrea: Speaking about OLCP. Mariana may have ideas for other topics? should we reach out to her to establish connections?

walterbender: callaurrea: yes... I have been chatting with her on FB A friend of ours just became the new president of OLPC

llaske_ (@llaske_:matrix.org): Oh really ? who is it?

walterbender: Mariana She is interested in deepening the ties to Sugar Labs

llaske_ (@llaske_:matrix.org): Cool

callaurrea: we can invite her to present at one of our meetings... vision, where they are, etc.?

walterbender: Mariana Ludmila Cortés -- I am not sure of her OLPC email callaurrea: great idea I will see if she can join us in two weeks.

sum2it: Hi all, just joined and read the backlog.

walterbender: I just asked her if she can join us for a discussion in 2 weeks :P hi sum2it any other discussion topics? I gave a talk to a bunch of teachers in Brazil last week and am following up with a workshop this Friday.

callaurrea: missed that

walterbender: Arranged through USP any other discussion topics?

perrieee: yes ... what is the plan for the website refresh?

callaurrea: can we add the link to your sat workshop to the minutes?

walterbender: callaurrea: yes... I will add it

perrieee: I was personally thinking this GSoc will be a good time

callaurrea: we said we will begin with some of those activities... for our packages

walterbender: perrieee: I think it is a reasonable scope for a scaled back GSoC but we do need to have a concrete proposal as to how the new website is tangibly better -- both in terms of the visitor experience and maintenance overhead

perrieee: There is already a design drafted set ... I can share that again

llaske_ (@llaske_:matrix.org): I think we should do a light update of our website just to mention that SugarLabs is now Sugar, MusicBlocks and Sugarizer. But it could be done outside of GSoC in my opinion

walterbender: callaurrea: hopefully my Friday workshop can be a rehearsal for the (bi-?) monthly Sugar Labs workshops

srevinsaju (@srevinsaju:matrix.org): (I am not a part of SLOBS), but our website update mechanism has been broken since 2020 January

llaske_ (@llaske_:matrix.org): srevinsaju: sounds like a priority to fix it first

perrieee: https://www.figma.com/proto/iVvHw3nrOCjBi3FfCOM4PC/Sugar-refresh?node-id=924%3A1&scaling=min-zoom

srevinsaju (@srevinsaju:matrix.org): some changes like the Flathub by tchx84 and others are missing,

callaurrea: Is it Fridays?

perrieee: this is a draft, texts will change ... but yeah

walterbender: my USP workshop happens to be Friday... that is all the Sugar Labs ones can be whenever you think best perrieee: I will take a look... it sounds like no matter what we need to make some updates so it is good that you have put thought into it * walterbender would like a section on background reading too * walterbender is writing a book chapter right now on Music Blocks he could share

perrieee: do you mean something like a story behind SL

walterbender: callaurrea: https://zoom.us/j/98734210784?pwd=b0xHenJuQVpKY3VBd3Y2NFJHRnlDQT09 Password: 422968 (at 2:30 US East Coast -- 19:30 UTC)

sum2it: Will it be a part of a larger book?

walterbender: perrieee: I mean simply a list of papers about Sugar, Sugarizer, Music Blocks, etc. for someone interested in some of the pedagogy

callaurrea: Sat at 2:30 pm?

perrieee: oh oh coool yeah sure

walterbender: sum2it: a friend is putting together a collection of essays in celebration of the 50th anniversary of Seymour and Cynthia's 20 things to do with a computer paper. I am writing about thing #11 -- music callaurrea: Friday :smile: * walterbender does not know how to use meojis or type emoji

sum2it: walterbender Happy to help with drafts and/or editing, anytime.

walterbender: https://dspace.mit.edu/handle/1721.1/5836

walterbender

callaurrea: we have one paper

walterbender: callaurrea: we have the Turtle Blocks one you, Cynthia and I wrote :P

callaurrea: yes!!

walterbender: sum2it: if you wanna read/comment on my draft, you are more than welcome.

sum2it: Will do.

walterbender: https://docs.google.com/document/d/1qTGRsQfOmLvR5V2Y_iD9y58MRqK9MHXTS7HFh6a-wGw/edit?usp=sharing

sum2it: Thanks.

walterbender: Any other business? I want to be respectful of the time

llaske_ (@llaske_:matrix.org): That's all on my side

walterbender: Did someone volunteer to follow up on Google Summer of Documentation?

perrieee: I can do a follow up

walterbender: thx

perrieee: Samson and I :)

walterbender: What did everyone think of using Matrix?

callaurrea: I am ok with it

llaske_ (@llaske_:matrix.org): It's like an IRC++

perrieee: I like the experience ...

sum2it: This is good

walterbender: I feel like it is a bit more inclusive than our video calls (and easier for the person writing up the minutes -- he says selfishly) So, lets use it again next time? I will let you know if Mariana can join us.

callaurrea: agree

llaske_ (@llaske_:matrix.org): okay

perrieee: agree

sum2it: +1

walterbender: OK. Until next time, feel free to ping me here thanks everyone

sum2it: Bye

llaske_ (@llaske_:matrix.org): Thanks all. Bye

sum2it: Thanks all

perrieee: bye, thanks all'''

BugSquad/Telepathy Debugging

2021-02-14T18:24:44Z

MrBIOS: /* Fedora 20 */

<noinclude>
[[Category:Testing]]
[[Category:BugSquad]]
[[Category:HowTo]]
</noinclude>
== Enabling debug logs for Telepathy ==

When there are certain kinds of problems with collaboration, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files. If you haven't already seen [[BugSquad/Get Logs]], see that page first.

=== Fedora 20 through Fedora 35/rawhide ===

Starting with Fedora 20, to enable debug logging of Salut and Gabble:
* Edit the /etc/environment file
G_MESSAGES_DEBUG="all"
SALUT_DEBUG="all"
SALUT_LOGFILE=/home/olpc/salut.log
GABBLE_DEBUG=all
GABBLE_LOGFILE=/home/olpc/gabble.log
* Reboot

=== Fedora 18 ===
* Edit the ~/.sugar/debug file (default version shown below in the gray box) and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE and PRESENCESERVICE_DEBUG by removing the initial '#' character
* For debugging lower level problems in the Telepathy connection managers, enable LM_DEBUG (for telepathy-gabble) or GIBBER_DEBUG (for telepathy-salut). Note that these will produce much bigger log files.
* Reboot (or restart the display manager).

<pre>
# Uncomment the following lines to turn on many sugar debugging
# log files and features
#export LM_DEBUG=net
#export GABBLE_DEBUG=all
#export GABBLE_LOGFILE=$HOME/.sugar/default/logs/telepathy-gabble.log
#export SALUT_DEBUG=all
#export SALUT_LOGFILE=$HOME/.sugar/default/logs/telepathy-salut.log
#export GIBBER_DEBUG=all
#export PRESENCESERVICE_DEBUG=1
#export SUGAR_LOGGER_LEVEL=debug

# Uncomment the following line to enable core dumps
#ulimit -c unlimited
</pre>

Telepathy log files are now available at <tt>~/.sugar/default/logs/telepathy-gabble.log</tt> and <tt>~/.sugar/default/logs/telepathy-salut.log</tt> .
Be sure to attach these files if you submit a ticket about a Telepathy issue.

== Capturing core files (XO specific) ==

Core files are produced when a program crashes and contain useful debugging information. By default, core files are disabled on the XO. Here is how to enable them.

* As root:

echo /tmp/core-%p-%e > /proc/sys/kernel/core_pattern

: This tells the kernel to put core files into the /tmp directory. This will only be effective until the laptop is rebooted. To make it persistent across reboots, add the following line to /etc/sysctl.conf:

kernel.core_pattern = /tmp/core-%p-%e

* Add the following line to <tt>./sugar/debug</tt>:

ulimit -c unlimited

This turns off any limit on core file size.

== Debugging scenarios ==

* no presence seen on (or of) other machines/laptops
* activity was shared but doesn't appear on other laptops
* invitation was sent but not received
* other sharing problems

===Troubleshooting example===
See this discussion thread, http://www.mail-archive.com/devel@lists.laptop.org/msg24799.html