Sugar Labs - User contributions [en]

Service/smtp

2011-04-08T14:28:51Z

Nubae:

== Hostnames ==

{|class=wikitable
! hostname !! service !! port !! function
|-
| smtp.sugarlabs.org || smtp || 25 || Local delivery (plain SMTP)
|-
| smtp.sugarlabs.org || [http://www.faqs.org/rfcs/rfc2476.html submission] || 587 || Email relay (SMTP with STARTTLS, password authentication required)
|-
| smtp.sugarlabs.org || smtps || 465 || Email relay (SMTP with SSL, password authentication required)
|}

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

* postmaster AT sugarlabs DOT org

== Sysadmins ==

* [[User:Bernie|Bernie Innocenti]]

== Notes ==

* Users with a Sugar Labs [[Service/shell|shell account]] on can use our SMTP relay for personal email submission. Any abuse will be prosecuted.

* Preferably use the [http://www.faqs.org/rfcs/rfc2476.html submission] port for email relay. Unauthenticated and unencrypted connections are not allowed to relay.

* smtp.sugarlabs.org is *not* the MX for the sugarlabs.org.
Google Apps handles our domain and forwards to smtp.sugarlabs.org for unknown users

* Just for those of you wanting to use just one email client (namely gmail in this case), you can simply add a second account to run through gmail (say user@activitiycentral.com or user@sugarlabs.org) and it will then allow you to choose which account you'd like to send from.

- To do this u need to login to your gmail account and go the following url its pretty hiddeb away: https://mail.google.com/mail/?tab=om#settings/accounts
Then choose send mail from another address and follow the instructioins for sending out via smtp.sugarlabs.org

== SPF ==

Our domains use a non-strict (~all) [http://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] record.

If you send email with sugarlabs.org in the From: header, then you '''MUST''' submit it to our
SMTP server.

== DKIM ==

Our domain publishes a '''test''' [http://en.wikipedia.org/wiki/DKIM DKIM] key. All outgoing email
is signed, but at this time verifiers will ignore our DKIM signature.

To test DKIM, send an email to autorespond+dkim@dk.elandsys.com

In anticipation of switching on strict DKIM verification, all email for the sugarlabs.org domain
must be submitted to our SMTP server. Failure to do so may result in your email being occasionally
blocked by spam filters.

== See also ==

[[Service/imap]]

[[Category:Service|imap]]

Dextrose/Server/Addons

2011-03-27T15:24:35Z

Nubae:

Some changes that will be included in the dextrose server, a lot of it based on work done by the AU olpc guys.

Take out active antenna stuff:

# clean up active antenna stuff and superflous network connections here:
rm -f /etc/sysconfig/network-scripts/route-lanbond0
rm -f /etc/sysconfig/network-scripts/route-eth0
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond0
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond1
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond2
rm -f /etc/sysconfig/network-scripts/ifcfg-msh0
rm -f /etc/sysconfig/network-scripts/ifcfg-msh1
rm -f /etc/sysconfig/network-scripts/ifcfg-msh2
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh0
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh1
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh2
rm -f /etc/sysconfig/network-scripts/ifcfg-eth1
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:0
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:1
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:2

Make custom named based on original XS:

# setup custom named
mv /sbin/ifup-local /sbin/ifup-local.rpmsave
cat > /sbin/ifup-local <<EOF
# Authors: Jerry Vonau <jvonau@shaw.ca>
# Martin Langhoff <martin@laptop.org>
#
if [ x"\${1}" = x ]; then
exit
else
case \$1 in
eth0|ppp0)
namedtpl=/etc/named-xs.conf.tpl
namedconf=/etc/named-xs.conf
FWD=""
for i in \`cat /etc/resolv.conf | grep nameserver | awk '{print \$2}'\`;
do
if [ x\$i != x127.0.0.1 ]; then
FWD="\$FWD \$i;"
else
exit
fi
done
cp \$namedtpl \$namedconf
logger "changing /etc/named-xs.conf using forwarders \$FWD"
sed -i -e "s/@@BASEDNSFWD@@/\$FWD/" \$namedconf
logger "changing /etc/resolv.conf for principal school server"
cp /etc/sysconfig/olpc-scripts/resolv.conf /etc/resolv.conf
;;
esac
fi
EOF
chmod 755 /sbin/ifup-local

Dextrose/Server/Addons

2011-03-27T15:18:51Z

Nubae:

Some changes that will be included in the dextrose server, a lot of it based on work done by the AU olpc guys.

Take out active antenna stuff:

# clean up active antenna stuff and superflous network connections here:
rm -f /etc/sysconfig/network-scripts/route-lanbond0
rm -f /etc/sysconfig/network-scripts/route-eth0
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond0
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond1
rm -f /etc/sysconfig/network-scripts/ifcfg-mshbond2
rm -f /etc/sysconfig/network-scripts/ifcfg-msh0
rm -f /etc/sysconfig/network-scripts/ifcfg-msh1
rm -f /etc/sysconfig/network-scripts/ifcfg-msh2
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh0
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh1
rm -f /etc/sysconfig/network-scripts/ifcfg-wmesh2
rm -f /etc/sysconfig/network-scripts/ifcfg-eth1
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:0
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:1
rm -f /etc/sysconfig/network-scripts/ifcfg-lanbond0:2

Make custom named based on original XS:

# setup custom named
mv /sbin/ifup-local /sbin/ifup-local.rpmsave
cat > /sbin/ifup-local <<EOF
# Authors: Jerry Vonau <jvonau@shaw.ca>
# Martin Langhoff <martin@laptop.org>
#
if [ x"\${1}" = x ]; then
exit
else
case \$1 in
eth0|ppp0)
namedtpl=/etc/named-xs.conf.tpl
namedconf=/etc/named-xs.conf
FWD=""
for i in \`cat /etc/resolv.conf | grep nameserver | awk '{print \$2}'\`;
do
if [ x\$i != x127.0.0.1 ]; then
FWD="\$FWD \$i;"
else
exit
fi
done
cp \$namedtpl \$namedconf
logger "changing /etc/named-xs.conf using forwarders \$FWD"
sed -i -e "s/@@BASEDNSFWD@@/\$FWD/" \$namedconf

logger "changing /etc/resolv.conf for principal school server"
cp /etc/sysconfig/olpc-scripts/resolv.conf /etc/resolv.conf
;;
esac
fi
EOF
chmod 755 /sbin/ifup-local

2011-02-22T21:41:59Z

Nubae: /* Dextrose Server */

Dextrose/Server/DebianBuilding

2011-02-17T20:13:11Z

Nubae: Created page with "This is a description on how to integrate the FAI (Fully Automated Install) using debian technology to create a similar server with similar services to the pre-defined RHEL 6 ins..."

Dextrose/Server

2011-02-17T20:08:46Z

Nubae: /* Dextrose Server */

Dextrose/Server/Building

2011-02-13T23:52:40Z

2009-09-06T01:02:11Z

Nubae:

db example:
what is it? || Where is it || Screenshots || Saved instances if I have it
Activity

<code>
Moodle Linking to Sugar Activities
goal
make it easy for students to upload work straight to Moodle servers
with and w/o logins?
reproduce enthusiasm found on Scratch for programming with etoys. turtle art, writing etc
students I've worked with want
lots of feedback from peers
to share their work with peers
to work on projects with friends
later they'll figure out their friends may not be the best people to work with
but best to figure that out EARLY
sharing to be easy
control over who can edit
blame trees to see who messed up a part of a larger group project
grp projects should have no more than 3 people
to have fun
building games is fun
writing is not fun unless it's Alice like then it becomes a game again
variety
structure
to be as lazy as possilbe most of the time
to feel they are smart
SHOW they are smart
nothing in Sugar really makes that easy yet
activity uploads
etoys etc
speak
encourage students to tell stories using speak
encourage creation of FAQs
Turtle Art
pippy
labyrinth
nice for mind mapping but it's clumsy
where to begin
python
why python?
Nubae knows it
hello world
nubae's pyclic?
need to know how to get pyclic into a Sugar install...
it's not in Sugar activities
http://activities.sugarlabs.org/en-US/sugar/search?q=pyclic&cat=all
it's here
http://git.sugarlabs.org/projects/pyclic
can we get pyclic into Pippy as well?
nice to get that into Pippy examples
tie the Pyclic data straight into the Moodle DB and tie THAT data into the Moodle Quiz management interface
start here with a basic test prompt interface
sample UI though far from perfect
http://docs.google.com/previewtemplate?id=0Al9mmCKTPBRYdHNtWUN2aWlEZmtnVjZSWXZRZ2trNVE&mode=public
question builder
http://docs.google.com/View?id=dhq9ft55_82f46pw9dk
New activity
quiz builder and admin
goal
students write and answer questions
teacher or expert volunteers act as editors and gate keepers
put the onus of thinking on students!
flow description
http://docs.google.com/View?id=dhq9ft55_82f46pw9dk
student writes X number of questions as determined by teacher
Question types
multiple choice =MC
short answer= SA
true/false= T/F
essay
cloze
submits questions via Python or other UI to moodle db
student is now qualified to take test
while taking test student can
see if question was student created or teacher created
this will increase interest in the question and who is the student
can suggest better answer
can suggest a better question
student scores for FITB/ SA/ MC/ Cloze can be returned immediately
short answer and essay questions can go back to teacher or back to community for further evaluation
use volunteers to help teacher grade
users
XO users
non XO users
viewing of materials
only logged in to moodle server
child security etc
fields
questions
can we pull the machine specs XO or otherswise
version of Sugar?
user ID
encourage firstname, last initial and maybe weight
IP
should tell us country and city...
maybe that could be the intial log in UserID? last 3 digits of IP?
voluntary
school name
teacher name
class name
notes
nice to have something like this
http://freemind.sourceforge.net/wiki/index.php/Mind_Map_Gallery#Education_Technology
media wiki supports freemind mindmap files
a tool that would allow lots of users to see and build upon other ideas in real time
gobby like but with a diagramming UI
connect the dots
explode certain ideas
derive new documents from base document
annotations are date stamped and contain User ID

</code>--[[User:Dennis Daniels|Dennis Daniels]] 20:20, 5 September 2009 (UTC)

Sugar on a Stick/Getting Involved

2009-06-18T18:38:05Z

Nubae: /* Downloading alternative images */

<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|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}{{TOCright}}</noinclude>
==Send us your Thoughts==
Send e-mail to [mailto:iaep@lists.sugarlabs.org iaep@lists.sugarlabs.org]. This is our [http://lists.sugarlabs.org/listinfo/iaep "It's an Education Project" mailing list].

===Help with Project Design===
See [[Sugar on a Stick/Resources#Home View Design | Home View design]] for a discussion of which activities should be visible on the first view of a running Sugar system.

== Help with Deployment ==
* We are experimenting with the [http://schools.sugarlabs.org/mod/forum/view.php?id=530 Sugar Labs Moodle system] to help in coordinating deployment work on this project.
* [[Deployment Team/School_Key]] Information on various Sugar on a Stick deployments.
* Protocol for [[April 17 Olin Play Session]]
* Notes from [[April 18th YMCA Healthy Kids Day]]

==Help with Testing==
With new builds coming frequently, it is sometimes hard to keep track of known problems and temporary workarounds. Sometimes a build will not complete the boot process, or only start certain services.

Testers can help other testers by organizing some of their findings here. Remember different hardware combinations may have different results.

Download guide: [[Sugar_on_a_Stick#Getting_Sugar_on_a_Stick_.28beta.29 | Getting SoaS (beta)]].
{{:Sugar_on_a_Stick/Getting Involved/Testing}}
== Join the development effort ==

* Development discussions take place on the Sugar-Devel email list, http://lists.sugarlabs.org/listinfo/sugar-devel.
* Real-time development chat is at irc://irc.freenode.net#sugar Mibbit: [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23sugar&noServerTab=false #sugar]
* Source files are at [http://git.sugarlabs.org/projects/soas Gitorious SoaS home]
* [[OLPC:Rawhide-XO]] for the closely-related development of Sugar for the XO-1 laptop on Fedora 11.
=== Downloading alternative images ===

A variety of images for testing are available (see table below). Some of images might still be unstable; that means ''they might not work yet.''

* The SoaS beta release is currently based on ''{{SoaS-2 beta}}''. It's the most stable version we have right now, and is recommended for general testing purposes.

* On the other hand, you can also grab a current snapshot, which includes the latest bits, but these might contain some issues and bite back. We really need your help on testing those to move forward!

* The virtual appliance is ''not ready'' for general use and is under heavy development. Any help with testing it is also appreciated, though.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''available solution''' || '''current state''' || '''download location'''
|-
| SoaS ''Beta'' || beta quality || http://download.sugarlabs.org/soas/releases/soas-beta.iso
|-
| SoaS ''Snapshot'' || varying quality || {{SoaS-2 path}}
|-
| SoaS ''Virtual Appliance'' || alpha quality || {{SoaS-2 app-path}}
|-
| SoaS ''openSUSE Sugar (55+ activities)'' || beta quality || http://en.opensuse.org/Sugar - usb/cd/dvd/appliance images available
|-
|}

Previous snapshots are provided in the subsequent directories on http://download.sugarlabs.org/soas/.

=== Roadmap ===
Review and contribute to plans and schedules on the [[Sugar on a Stick/Roadmap| Project roadmap page]].
<noinclude>
==Subpages==
{{Special:PrefixIndex/{{PAGENAME}}/}}

[[Category:Participate]]
</noinclude>

Sugar on a Stick/Linux

2009-06-18T18:34:56Z

Nubae: /* Linux instructions */

{{TOCright}}
== Introduction ==
This page helps you to put your [[Sugar on a Stick]] image on a USB flash drive under Linux. If you have questions, trouble or feedback, please let us know on the [[Talk:Sugar on a Stick|SoaS talk]] page. It is important to note, that though currently SoaS is best known to be carried with the Fedora base, it exists with other dsitributions as a base too, for example the http://en.opensuse.org/Sugar - openSUSE variant. If you can improve these instructions, please edit the page and do so!

== [[Sugar on a Stick/Installation/OLPC | SoaS on an OLPC XO-1]]==
* See [[Sugar on a Stick/Installation/OLPC]] for booting an OLPC XO-1 with SoaS images.

== Linux instructions ==

This is known to work in Fedora and Ubuntu and should work in other Linux distributions.

For the openSUSE Sugar variant (bundled with 55+ activities) go to http://en.opensuse.org/Sugar

First, start downloading the SoaS <tt>.iso</tt> image from the [[Sugar on a Stick#Downloading alternative images]] table, then return here.

* Make sure you have the ''syslinux'' package installed on the operating system that you will use to prepare the Live USB image. It is recommended that you also have the ''isomd5sum'' package installed. The ''cryptsetup'' package is another option potentially used by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install syslinux isomd5sum cryptsetup</code> will install the packages.)
**''syslinux'' is needed to set up booting on the FAT file system of the USB disc or Live CD.
**''isomd5sum'' is needed for the recommended verification step, which checks that the .iso file is complete after its travels. If there is a problem with the .iso file, the script will exit and provide a failure message. The verification step can be bypassed by using the <code>--noverify</code> option.
**''cryptsetup'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''squashfs'' file system employed by the Live USB deployment.
* Plug in a 1GB or larger USB stick into your computer.
* Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)

* Check the USB device. In the example below the device is /dev/sdb:
: <tt>'''df -h'''</tt>
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 7.0G 11G 40% /
tmpfs 1.5G 0 1.5G 0% /lib/init/rw
varrun 1.5G 96K 1.5G 1% /var/run
varlock 1.5G 0 1.5G 0% /var/lock
udev 1.5G 2.9M 1.5G 1% /dev
tmpfs 1.5G 104K 1.5G 1% /dev/shm
lrm 1.5G 2.0M 1.5G 1% /lib/modules/2.6.27-11-generic/volatile
/dev/sdb1 996M 913M 84M 92% /mnt/myUSBdisc

* Then check to see that the partition is marked as bootable, 
: <tt>sudo fdisk '''-l'''</tt> ''<----that's a lowercase letter 'L' for the '''l'''ist option.''
You should see output that looks like this:
Disk /dev/sdb: 1047 MB, 1047265280 bytes
255 heads, 63 sectors/track, 127 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0008325f
.
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 127 1020096 6 FAT16
The '*' under the Boot column is what you want to see.
: If not, then
:* For Ubuntu 8.10, menu: System -> Administration -> Partition Editor (GParted).
::# Select your USB device (/dev/sd''b'' for the rest of these instructions),
::# then your partition (/dev/sd''b1''),
::# then menu: Partition -> Manage Flags,
::# check the boot box,
::# and Close to mark the partition as bootable.

:* For Fedora,
::# <tt>parted /dev/sd''b''</tt>
::# toggle 1 boot
::# quit

* Also, check to see that you do not already have an existing bootloader (such as GRUB) in the MBR of your stick. (If you have not previously used this stick as a live boot, you can skip this step.) To be sure that the USB stick's MBR is wiped clean, overwrite it completely using:
: <tt>dd if=/dev/zero of=/dev/sd''b'' bs=446 count=1</tt>
** (Actually, that didn't work for me. But this did:
**: <tt>lilo -M /dev/sd''b''</tt>
**:It put in a standard MBR that boots whichever partition has been called bootable. It does not install LILO as such.)
* Unmount the drive, 
: <tt>sudo umount /dev/sd''b1''</tt>
* Change mode to make the script executable.
: <tt>chmod +x livecd-iso-to-disk.sh</tt>
* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.
: <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sd''b1''</tt>
The ''livecd-iso-to-disk'' installation has the advantage over the ''liveusb-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but leaving out the --home-size-mb NNN option).
* The <code>--delete-home</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). You wouldn't use the --delete-home option on an upgrade of the operation system only.
Depending on the size of your USB stick, you may have to decrease <code>--overlay-size-mb</code> and <code>--home-size-mb</code> values (example, for 1 GB stick, use 200 for each).

== Alternative installation methods ==

=== UNetbootin ===

UNetbootin (Universal Netboot Installer) is a cross-platform utility that can create Live USB systems.

:*http://unetbootin.sourceforge.net/

* Choose the Diskimage ISO option.
* Select the downloaded .iso image file.
* Press OK and wait for your USB stick to be created.

----
''Notes:''
*Keep in mind that UNetbootin doesn't support persistent overlays, so you won't be able to save files using the Journal.
*Under soas gives errors
----

=== Fedora Live USB Creator ===
(This section is under construction.)

Fedora's ''liveusb-creator'' (see [[Sugar on a Stick/Windows | windows install section]] above for how to use).
Needs to be loaded from Synaptic Package Manager

Has persistence, easy to use.

Instructions are at http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Getting_Involved/Testing/Soas-F11b_Sugar0.84.2

-On full installs of Fedora 11 Preview can add sugar desktop and make a Soas version with a Full Gnome desktop plus a
Sugar Desktop on one USB Stick or SD Card (Wireless WPA works with EeePC900)

-see for details :

++++PREPARATORY WORK : use Partition Editor to erase existing partition on sdb? (CHECK THIS CAREFULLY!);then make NEW partition as a fat16 primary partition LABELED FEDORA then set boot flag.++++

-to label the partition FEDORA on Fedora, use <pre>dosfslabel devicename FEDORA</pre> dosfslabel comes with the "dosfstools" rpm package.

== What's next? ==

After you've created your stick, it's time to [[Sugar_on_a_Stick#Boot|boot your stick]] and [[Sugar on a Stick/Getting Involved | test]] it out. Please also [[Sugar on a Stick/Getting Involved/Testing | report]] your observations.

[[Category:HowTo]]

Sugar on a Stick/Linux

2009-06-18T18:33:40Z

Nubae: /* Introduction */

{{TOCright}}
== Introduction ==
This page helps you to put your [[Sugar on a Stick]] image on a USB flash drive under Linux. If you have questions, trouble or feedback, please let us know on the [[Talk:Sugar on a Stick|SoaS talk]] page. It is important to note, that though currently SoaS is best known to be carried with the Fedora base, it exists with other dsitributions as a base too, for example the http://en.opensuse.org/Sugar - openSUSE variant. If you can improve these instructions, please edit the page and do so!

== [[Sugar on a Stick/Installation/OLPC | SoaS on an OLPC XO-1]]==
* See [[Sugar on a Stick/Installation/OLPC]] for booting an OLPC XO-1 with SoaS images.

== Linux instructions ==

This is known to work in Fedora and Ubuntu and should work in other Linux distributions.

First, start downloading the SoaS <tt>.iso</tt> image from the [[Sugar on a Stick#Downloading alternative images]] table, then return here.

* Make sure you have the ''syslinux'' package installed on the operating system that you will use to prepare the Live USB image. It is recommended that you also have the ''isomd5sum'' package installed. The ''cryptsetup'' package is another option potentially used by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install syslinux isomd5sum cryptsetup</code> will install the packages.)
**''syslinux'' is needed to set up booting on the FAT file system of the USB disc or Live CD.
**''isomd5sum'' is needed for the recommended verification step, which checks that the .iso file is complete after its travels. If there is a problem with the .iso file, the script will exit and provide a failure message. The verification step can be bypassed by using the <code>--noverify</code> option.
**''cryptsetup'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''squashfs'' file system employed by the Live USB deployment.
* Plug in a 1GB or larger USB stick into your computer.
* Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)

* Check the USB device. In the example below the device is /dev/sdb:
: <tt>'''df -h'''</tt>
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 7.0G 11G 40% /
tmpfs 1.5G 0 1.5G 0% /lib/init/rw
varrun 1.5G 96K 1.5G 1% /var/run
varlock 1.5G 0 1.5G 0% /var/lock
udev 1.5G 2.9M 1.5G 1% /dev
tmpfs 1.5G 104K 1.5G 1% /dev/shm
lrm 1.5G 2.0M 1.5G 1% /lib/modules/2.6.27-11-generic/volatile
/dev/sdb1 996M 913M 84M 92% /mnt/myUSBdisc

* Then check to see that the partition is marked as bootable, 
: <tt>sudo fdisk '''-l'''</tt> ''<----that's a lowercase letter 'L' for the '''l'''ist option.''
You should see output that looks like this:
Disk /dev/sdb: 1047 MB, 1047265280 bytes
255 heads, 63 sectors/track, 127 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0008325f
.
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 127 1020096 6 FAT16
The '*' under the Boot column is what you want to see.
: If not, then
:* For Ubuntu 8.10, menu: System -> Administration -> Partition Editor (GParted).
::# Select your USB device (/dev/sd''b'' for the rest of these instructions),
::# then your partition (/dev/sd''b1''),
::# then menu: Partition -> Manage Flags,
::# check the boot box,
::# and Close to mark the partition as bootable.

:* For Fedora,
::# <tt>parted /dev/sd''b''</tt>
::# toggle 1 boot
::# quit

* Also, check to see that you do not already have an existing bootloader (such as GRUB) in the MBR of your stick. (If you have not previously used this stick as a live boot, you can skip this step.) To be sure that the USB stick's MBR is wiped clean, overwrite it completely using:
: <tt>dd if=/dev/zero of=/dev/sd''b'' bs=446 count=1</tt>
** (Actually, that didn't work for me. But this did:
**: <tt>lilo -M /dev/sd''b''</tt>
**:It put in a standard MBR that boots whichever partition has been called bootable. It does not install LILO as such.)
* Unmount the drive, 
: <tt>sudo umount /dev/sd''b1''</tt>
* Change mode to make the script executable.
: <tt>chmod +x livecd-iso-to-disk.sh</tt>
* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.
: <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sd''b1''</tt>
The ''livecd-iso-to-disk'' installation has the advantage over the ''liveusb-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but leaving out the --home-size-mb NNN option).
* The <code>--delete-home</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). You wouldn't use the --delete-home option on an upgrade of the operation system only.
Depending on the size of your USB stick, you may have to decrease <code>--overlay-size-mb</code> and <code>--home-size-mb</code> values (example, for 1 GB stick, use 200 for each).

== Alternative installation methods ==

=== UNetbootin ===

UNetbootin (Universal Netboot Installer) is a cross-platform utility that can create Live USB systems.

:*http://unetbootin.sourceforge.net/

* Choose the Diskimage ISO option.
* Select the downloaded .iso image file.
* Press OK and wait for your USB stick to be created.

----
''Notes:''
*Keep in mind that UNetbootin doesn't support persistent overlays, so you won't be able to save files using the Journal.
*Under soas gives errors
----

=== Fedora Live USB Creator ===
(This section is under construction.)

Fedora's ''liveusb-creator'' (see [[Sugar on a Stick/Windows | windows install section]] above for how to use).
Needs to be loaded from Synaptic Package Manager

Has persistence, easy to use.

Instructions are at http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Getting_Involved/Testing/Soas-F11b_Sugar0.84.2

-On full installs of Fedora 11 Preview can add sugar desktop and make a Soas version with a Full Gnome desktop plus a
Sugar Desktop on one USB Stick or SD Card (Wireless WPA works with EeePC900)

-see for details :

++++PREPARATORY WORK : use Partition Editor to erase existing partition on sdb? (CHECK THIS CAREFULLY!);then make NEW partition as a fat16 primary partition LABELED FEDORA then set boot flag.++++

-to label the partition FEDORA on Fedora, use <pre>dosfslabel devicename FEDORA</pre> dosfslabel comes with the "dosfstools" rpm package.

== What's next? ==

After you've created your stick, it's time to [[Sugar_on_a_Stick#Boot|boot your stick]] and [[Sugar on a Stick/Getting Involved | test]] it out. Please also [[Sugar on a Stick/Getting Involved/Testing | report]] your observations.

[[Category:HowTo]]

Marketing Team/Events/LinuxTag2009

2009-06-17T17:44:58Z

Nubae: /* Shifts */

{{TOCright}}

= LinuxTag 2009 =

[[‎Image:Linux_Logo_Datum_en.jpg |450x100px]]

== Event Details ==
LinuxTag is the most important place for Linux and open source software in Europe. In 2009, the 15th LinuxTag presents news for professional users, decision makers, developers, beginners and the Linux community - from 24th until 27th June on the Fairground in Berlin.
For more information, go to the [http://www.linuxtag.org/2009/en.html LinuxTag 2009 website].

[http://www.linuxtag.org/2009/en/besucher/reiseplanung.html Here] are instructions how you get to Linuxtag.

== Sugar Organizer ==

[[User:Erikos | Simon Schampijer | simon at sugarlabs dot org]] will be organizing Sugar's presence at LinuxTag 2009.

== Attendees ==

Are you planning to attend? Add your name and contact info below!
# [[User:Erikos | Simon Schampijer]]
# [[User:Tomeu | Tomeu Vizoso]]
# [[User:Sdz | Sebastian Dziallas]]
# [[User:nubae | David Van Assche]]
# [[User:fab | Fabian Affolter]]
# [[User:jzGreen | James Zaki]]
# [[User:SeanDaly | Sean Daly]]
# [http://wiki.laptop.org/go/Support_Gang Adam Holt]

== Sugar Activities ==
Sugar does advocate the concepts of activities - you learn through doing, so if you want more learning you want more doing. So the Sugar Labs team wants to get engaged at Linuxtag:

# We will have a [[Marketing_Team/Events/LinuxTag2009#Sugar_Booth | booth]] located at 7.2a 110a.
# Greg gives the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=787 "Education, Innovation, and Free Software"] (Saturday, 27.06 - 15.00-16.00 Saal 5)
# Simon gives the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=791 Sugar - a software playground for learning about learning"] (Saturday, 27.06 - 17.00 Saal 5)
# Sebastian will be giving a barcamp session at [http://fedoraproject.org/wiki/FUDCon:Berlin_2009 FUDCon] about various educational efforts, mainly SoaS ([http://www.linuxtag.org/2009/de/program/fudcon.html Linuxtag Fudcon project])
# Pablo Casal and Eduardo Blanco from Netlabs are giving the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=789 "Plan Ceibal - A country-wide OLPC deployment in Uruguay"] (Saturday 27.06 - 16.00 Saal 5). They designed the initial proposal for Ceibal's network, and are currently consultants for the project.

== Sugar Booth ==
Our booth will be at 7.2a 110a. We share this [http://www.linuxtag.org/2009/dl/projekte/Halle7.2a/198-50198--72a110a.pdf booth] with our friends from:
* [http://www.olpc-deutschland.de/ OLPC Deutschland e.V.]
* [http://www.squeak.de/ Squeak Germany]
* [http://wiki.skolelinux.de/LinuxTag2009 Skolelinux Germany]
* [http://www.linux4afrika.de/ Linux4Afrika]
* [http://www.x2go.org X2go]

Please list your availability if you are interested in helping with the booth. Or if you already know which shifts you want to take, feel free to add yourself in the second table. German skills are welcome - but not needed. Ideally a shift is two people, but given the space reserved at the booth size I think we can get away with one as well. Helping at the booth means answering questions regarding Sugar and Sugar Labs, demoing Sugar and flashing Soas on request. People helping at the booth will get a Linuxtag ticket.

=== Shifts ===
Availability:

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! German !! 24.06.09 !! 25.06.09 !! 26.06.09 !! 27.06.09 !! Note
|-
! Schampijer
| Native || yes || yes || yes || not available from 16.00 to 18.00 as he has a talk there || is there in the mornings to make sure everything is set up
|-
! Tomeu
| None || ? || ? || full day? || full day || x
|-
! Sebastian Dziallas
| Native || || || || will arrive in the morning || yes
|-
! David Van Assche
| Native || yes || yes || yes || yes || in between sugar and opensuse booths...

|}

Plan:

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Day !! 10.00-12.00 !! 12.00-14.00 !! 14.00-16.00 !! 16.00-18.00
|-
! 24.06.09
| Schampijer || David || x || x
|-
! 25.06.09
| Schampijer || x || David || x
|-
! 26.06.09
| Sean || x || Sean || x
|-
! 27.06.09
| x || Sean || x || Sean
|-
|}
* Tuesday 23.06.09 - 15.00: Booth Setup
* Saturday 27.06.09 - 18.30++: Booth tear-down and cleanup after the exhibition hall closes.
* all times are local Berlin times

=== Storage Space ===
We have a coops (Germans would say Kabüffchen as a diminutive of Kabuff) at the booths. As this is only meant for booth equipment all the other belongings like jackets, luggage etc can be stored at the wardrobe without any cost.

=== Power and Internet Connectivity ===
Power and Internet will be provided by LinuxTag and Messe Berlin for the project booths. What we need are:
* extension cords
* long network cables

Not permitted by Linuxtag:
* wireless access points (You are not permitted to operate your private wireless LAN. Please take this serious. There will be several site surveys to ensure this.)
* coffeemakers, kettles and cooking stuff
* connect visitors to the project's network

=== Lunch ===
Linuxtag is offering Lunch for the helpers. If we want to participate we would need helpers and not only eaters. More information can be found [http://wiki.linuxtag.org/w/fp:Lunch_2009 at].

== TODO ==
* Flyers with information about Sugar/Sugar Labs/interesting talks for the booth
* Poster - From the Linuxtag Team: Please prepare at least one large poster (A1 or A0) to be placed on the walls of your booth or infocounter, so that visitors understand what the booth is all about, or what the particular machine in front of them intends to demonstrate. Without posters or other similar stuff the booth will probably look a bit deserted and not that interesting at all. -- You can use adhesive tape to fix the posters on the walls. If you plan to demonstrate fancy hardware at your booth, it is very helpful to describe these particular pieces of hardware in a poster or a large sign, so that visitors recognize its value or notice that it is extraordinary.
* Project Workshops / BoFs: Linuxtag still have quite some slots left for workshops. The ultimate deadline for asking for a space for a workshop will be reached on Sunday, June 21st, 2009.

== Equipment ==
* Booth Banner - [[user:SeanDaly | Sean]] has [http://wiki.sugarlabs.org/go/Marketing_Team/BoothBanners one] and ordered a second one (Banners are 80cm x 200cm)
* 100 brightly colored branded Sugar Labs balloons in different colors - [[user:SeanDaly | Sean]]
* 21 inch screen for demoing Sugar at the booth - [[user:Erikos | Erikos]]
* Extension cords - [[user:Erikos | Erikos]]

== Lodging ==
* Accommodation Information from [http://www.linuxtag.org/2008/en/visitors/travel.html Linuxtag]
* [http://www.pension-freiraum.de/ Pension Freiraum]
** Nice area with bars restaurant cafe, about 25 minutes to the conference
* [http://www.hotel-funkturm-messe.de/english/home.html Hotel Funkturm]
** right next door to the conference area (room 4-6 persons, 100euro per night for the room, inclusive breakfast)

== Schedule ==

=== Tuesday, June 23 ===
* 15.00-16.00: Booth Setup

=== Wednesday, June 24 ===
* 10.00-18.00: Linuxtag (Including the SugarLabs booth)

=== Thursday, June 25 ===
* 10.00-18.00: Linuxtag (Including the SugarLabs booth)
* 19.00: [http://www.linuxtag.org/2009/en/about/linuxnacht.html LinuxNacht] - Get-together of speakers, exhibitors and the LinuxTag team at [http://www.e4-berlin.de/location.php E4]

=== Tuesday, June 26 ===
* 10.00-18.00: Linuxtag (Including the SugarLabs booth)

=== Friday, June 27 ===
* 10.00-18.00: Linuxtag (Including the SugarLabs booth)
* 16.00-18.00: [http://wiki.linuxtag.org/w/Keysigning Keysigning Party]

=== Saturday, June 28 ===
* 10.00-18.00: Linuxtag (Including the SugarLabs booth)
* x:00 hall 7.2b: Sugar Labs at "Papers Fast Forward", 2 minutes (2 slides) to highlight your most exciting exhibit
* 15.00-16.00 Saal 5: Greg gives the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=787 "Education, Innovation, and Free Software"]
* 16.00-16:30 Saal 5: Pablo Casal and Eduardo Blanco from Netlabs are giving the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=789 "Plan Ceibal - A country-wide OLPC deployment in Uruguay"]. They designed the initial proposal for Ceibal's network, and are currently consultants for the project.
* 17.00-17:30 Saal 5: Simon gives the talk: [http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vortragsdetails.html?talkid=791 Sugar - a software playground for learning about learning"]

=== Sunday, June 29 ===
* Bar Camp Sessions at [http://lists.sugarlabs.org/archive/iaep/2009-June/006311.html FUDCon]

[[Category:Event]]

Marketing Team/Events/LinuxTag2009

2009-06-08T12:08:28Z

Nubae: /* Attendees */

= LinuxTag 2009 =

== Event Details ==

For more information, go to the [http://www.linuxtag.org/2009/en.html LinuxTag 2009 website].

== Sugar Organizer ==

[[User:Erikos | Simon Schampijer | simon at sugarlabs dot org]] will be organizing Sugar's presence at LinuxTag 2009.

== Attendees ==

Are you planning to attend? Add your name and contact info below!

# [[User:Erikos | Simon Schampijer]]
# [[User:Tomeu | Tomeu Vizoso]]
# [[User:Sdz | Sebastian Dziallas]]
# [[User:nubae | David Van Assche]]

== Sugar activities ==

# We will have a booth located at 7.2a 110a. We share this booth with our friends from:
## [http://www.olpc-deutschland.de/ OLPC Deutschland e.V.]
## [http://www.squeak.de/ Squeak Germany]
## [http://wiki.skolelinux.de/LinuxTag2009 Skolelinux Germany]
## [http://www.linux4afrika.de/ Linux4Afrika]
## [http://www.x2go.org X2go]
# Greg gives the talk: "Education, Innovation, and Free Software"
# Simon gives the talk: "Sugar - a software playground for learning about learning" (Saturday, 27.06 - 17.00 Saal 5)
# Sebastian will be giving a barcamp session at FUDCon about various educational efforts, mainly SoaS

== Sugar Booth ==
Our booth will be at 7.2a 110a.

Please add your name to take a shift. Ideally a shift is two Persons. Helping at the booth means answering questions regarding Sugar and Sugar Labs, demoing Sugar and flashing Soas on request. People helping at the booth will get a Linuxtag ticket.

{| border="3"
! Day !! 10.00-12.00 !! 12.00-14.00 !! 14.00-16.00 !! 16.00-18.00
|-
! 24.06.09
| Schampijer || x || x || x
|-
! 25.06.09
| x || x || x || x
|-
! 26.06.09
| x || x || x || x
|-
! 27.06.09
| x || x || x || x
|-
|}

== TODO ==

# We need a banner for the booth

== Lodging ==
* Accommodation Information from [http://www.linuxtag.org/2008/en/visitors/travel.html Linuxtag]
* [http://www.pension-freiraum.de/ Pension Freiraum]
** Nice area with bars restaurant cafe, about 25 minutes to the conference
* [http://www.hotel-funkturm-messe.de/english/home.html Hotel Funkturm]
** right next door to the conference area (room 4-6 persons, 100euro per night for the room, inclusive breakfast)

== Schedule ==

More info as it becomes available.

[[Category:Event]]

Talk:OpenSUSE

2009-05-18T15:15:30Z

Nubae: /* = */

General observations of the Sugar Camp meeting in Paris, France held
16th and 17th of May 2009.
====================================================================

Massive strides were made in community integration and community
driven projects which will be considered or worked on in the coming
months for the next release of Sugar, referred at this time as 0.86,
and to be officially released in August of this year, following a 6
month release cycle of Gnome and many other open source projects.

Some of the more interesting changes that will happen are a move away
from matchbox to metacity, the well known and supported backend window
manager used by Gnome. This should in theory allow for much greater
integration into Gnome itself of individual sugar activities, as well
as the launching of sugar in Gnome, and even speed improvements. This
move is possible because the XO 1.5 will have more memory and better
cpu speeds, as well as a move away from sugar being agnostic to that
hardware. Sugar on a Stick was the big focus, which is now working
quite well, but still not perfect.

A desire for a revival of the help application was shown and that will
become one of the core fructose activities, though likely it will be
totally updated and perhaps even interactive. Browse will be upgraded
to have tabbed browsing, and have better support for integrated
flash/gnash, pdf support and youtube casts. A demo was shown of a
screencast of the usage of an activity coded at the camp, using turtle
art. These quick advances show that it is not only possible to
strengthen the Sugar Core and its activities, but also that one day
soon we will have a ubiquitous sugar solution that will run on all
distributions and platforms and most hardware.

The mention of fundraising was raised and there is a target in place
of aquiring 100,000 euros within the next release cycle which will be
used primarily in marketing and gathering core sugar people to the
places they need face to face talks like the one provided in Paris.

Our particular subgroup was asked to come up with a solution for
better support, performance, security, testing, triaging, and quality
assurance. The following is a report of what we came up with:

===========================================================================

Future of Sugar – Support, triaging and quality assurance– Famework for 0.86

===========================================================================

There were various discussion topics that included various subtopics.
Our group was responsible for the Autopackaging group, or better known
as the support, testing and quality assurance group.

The other groups were:
M – Marketing
A – Autopackaging
SE – School Environment
R – Roadmap

Sadly, the School Environment topic got cancelled, though it is of
particular importance to larger deployments and anything including the
school server. The subtopics for that group included: Teacher
Training; Primers – paperbacks; Technical feedback; Centralised admin
for deployments and Mass deployments

==========================================================================

Autopackaging – We can define this as the process of going from the
code that developers write going into the git version control system
to the public. There is an easy way of automating this without
spending too much time on the development. This is currently a task
being taken up by Aleksey Lim, who sadly could not be at Sugar Camp but
is pretty much a core developer at this point.

The name of the project is jhconvert and it will be responsible for
generating spec files and policy files for the various distributions
Sugar chooses to support. This is somewhat of a political issue, as
usually it is the package maintainers who do such a task, but
automation will make it much easier for Sugar to reach the public, and
I for one, being the maintainer for Sugar packages on OpenSUSE am
happy about this. For those distributions that choose not to support
this approach, they can always either take the code directly from git
and re-invent the wheel or do this manually, or take the src rpms or
src debs. I can speak only for openSUSE, but there, this direct
automation from git to the opensuse build system will be a reality,
and will allow for a direct transition from new revisions to
activities being uploaded to git, to them being available for all
distros and all platforms automatically.

=======================================================================

Method of communication between wishers/bugsquad and core development team

=======================================================================

At the moment, the centralised programmers upload their stuff and
apply patches to git as and when and the review queue is up to the
programmers. This needs to change drastically and a methodology of
collecting support and feature data efficiently and effectively must
be the part of people other than the core developers, who have far
more pressing needs and no time to review the thousands of requests
coming through the support pipeline. We need people to review the
tracker and review queue. 2-3 core people should be looking through
the bug tracker, and inform the programmers. This task used to be done
by Greg Smith of OLPC who did an incredibly difficult job in a great
way under extreme conditions. Finding a replacement will not be easy,
but currently there are many active volunteers who want to help in
this area.

They are out there in groups doing Q/A, support, testing and triaging,
but someone needs to be the user experience leader, a person who both
the developers know and trust, and who can weed out the support or
feature requests that are unrealistic or irrelevant. One possibility
was to automate this by putting a voting mechanism in place for
something like trac, but it would unlikely be used and could be easily
tampered with. If there is anyone out there willing to take on this
difficult and demanding task, but extremely rewarding experience,
please contact the Sugar team, via the mailing lists, IRC, the wikis,
OLPC, or support forums.

=======================================================================

Methodology for bug tracking and triaging – to peer reviewing and fixing:

=======================================================================

a. The user finds a bug in the latest release and then puts it into track.

b. The bugsquad does triage. Triage means assessing the bug,
validating it, and giving it a priority, and milestone (which release
its going to be fixed in.)

c. At some time, someone will try to fix it, usually a core developer.
If it’s not a core developer, it will always be attached as a patch
and reviewed.

d. Next step is peer review.

e. Patch gets improved, turned down, or accepted. This loop will
continue until the parties are happy with the code status.

f. Someone with commit access commits the patch.

======================================================================

When will 0.82 be end of life? – There is no answer to this currently
as it is to early to know what people in the field need. Should it be
long term, short term, very long term? These answers will come at some
stage, but not right now.

Currently packaging happens to fructose and glucose only. This will
not be the issue in the next release. RPMS will be automatically
created, though it will be the decision of the distribution in
question whether and how to use them. The .xo bundles will still be
there but will be overwritten (basically put into a different place
and given priority over the older relkease.)

===================================================================

Should we use package kit to standardize the packaging? This was a
question that came up and it is an interesting proposal, what do we think?

======================================================================

Auto testing of activities

======================================================================

There is something called sugarbot that should auto test activities.
It’s a google summer of code activity, but should be there for the
next release. It tests honey, not glucose, fructose.

We need a testing roadmap for glucose and fructose. Doing something
like what Gnome does would be good. We could also look at KDE. Are
there any other ideas on how to do this?

======================================================================

Buildbot will not run on the current hardware. We need to find a
sponsor for the machines and hosting?

This has now been communicated and should be fixed... As I understand
it, buildbot takes a look at some of the automation of testing packages
being built. Maybe alsroot can expand...

Talk:OpenSUSE

2009-05-18T14:48:57Z

Nubae: General observations of the Sugar Camp meeting in Paris, France held 16th and 17th of May 2009 - relational to opensuse and autpackaging

General observations of the Sugar Camp meeting in Paris, France held
16th and 17th of May 2009.
====================================================================

Massive strides were made in community integration and community
driven projects which will be considered or worked on in the coming
months for the next release of Sugar, referred at this time as 0.86,
and to be officially released in August of this year, following a 6
month release cycle of Gnome and many other open source projects.

Some of the more interesting changes that will happen are a move away
from matchbox to metacity, the well known and supported backend window
manager used by Gnome. This should in theory allow for much greater
integration into Gnome itself of individual sugar activities, as well
as the launching of sugar in Gnome, and even speed improvements. This
move is possible because the XO 1.5 will have more memory and better
cpu speeds, as well as a move away from sugar being agnostic to that
hardware. Sugar on a Stick was the big focus, which is now working
quite well, but still not perfect.

A desire for a revival of the help application was shown and that will
become one of the core fructose activities, though likely it will be
totally updated and perhaps even interactive. Browse will be upgraded
to have tabbed browsing, and have better support for integrated
flash/gnash, pdf support and youtube casts. A demo was shown of a
screencast of the usage of an activity coded at the camp, using turtle
art. These quick advances show that it is not only possible to
strengthen the Sugar Core and its activities, but also that one day
soon we will have a ubiquitous sugar solution that will run on all
distributions and platforms and most hardware.

The mention of fundraising was raised and there is a target in place
of aquiring 100,000 euros within the next release cycle which will be
used primarily in marketing and gathering core sugar people to the
places they need face to face talks like the one provided in Paris.

Our particular subgroup was asked to come up with a solution for
better support, performance, security, testing, triaging, and quality
assurance. The following is a report of what we came up with:

===========================================================================

Future of Sugar – Support, triaging and quality assurance– Famework for 0.86

===========================================================================

There were various discussion topics that included various subtopics.
Our group was responsible for the Autopackaging group, or better known
as the support, testing and quality assurance group.

The other groups were:
M – Marketing
A – Autopackaging
SE – School Environment
R – Roadmap

Sadly, the School Environment topic got cancelled, though it is of
particular importance to larger deployments and anything including the
school server. The subtopics for that group included: Teacher
Training; Primers – paperbacks; Technical feedback; Centralised admin
for deployments and Mass deployments

==========================================================================

Autopackaging – We can define this as the process of going from the
code that developers write going into the git version control system
to the public. There is an easy way of automating this without
spending too much time on the development. This is currently a task
being taken up by Aleksy Lin, who sadly could not be at Sugar Camp but
is pretty much a core developer at this point.

The name of the project is jhconvert and it will be responsible for
generating spec files and policy files for the various distributions
Sugar chooses to support. This is somewhat of a political issue, as
usually it is the package maintainers who do such a task, but
automation will make it much easier for Sugar to reach the public, and
I for one, being the maintainer for Sugar packages on OpenSUSE am
happy about this. For those distributions that choose not to support
this approach, they can always either take the code directly from git
and re-invent the wheel or do this manually, or take the src rpms or
src debs. I can speak only for openSUSE, but there, this direct
automation from git to the opensuse build system will be a reality,
and will allow for a direct transition from new revisions to
activities being uploaded to git, to them being available for all
distros and all platforms automatically.

=======================================================================

Method of communication between wishers/bugsquad and core development team

=======================================================================

At the moment, the centralised programmers upload their stuff and
apply patches to git as and when and the review queue is up to the
programmers. This needs to change drastically and a methodology of
collecting support and feature data efficiently and effectively must
be the part of people other than the core developers, who have far
more pressing needs and no time to review the thousands of requests
coming through the support pipeline. We need people to review the
tracker and review queue. 2-3 core people should be looking through
the bug tracker, and inform the programmers. This task used to be done
by Greg Smith of OLPC who did an incredibly difficult job in a great
way under extreme conditions. Finding a replacement will not be easy,
but currently there are many active volunteers who want to help in
this area.

They are out there in groups doing Q/A, support, testing and triaging,
but someone needs to be the user experience leader, a person who both
the developers know and trust, and who can weed out the support or
feature requests that are unrealistic or irrelevant. One possibility
was to automate this by putting a voting mechanism in place for
something like trac, but it would unlikely be used and could be easily
tampered with. If there is anyone out there willing to take on this
difficult and demanding task, but extremely rewarding experience,
please contact the Sugar team, via the mailing lists, IRC, the wikis,
OLPC, or support forums.

=======================================================================

Methodology for bug tracking and triaging – to peer reviewing and fixing:

=======================================================================

a. The user finds a bug in the latest release and then puts it into track.
b. The bugsquad does triage. Triage means assessing the bug,
validating it, and giving it a priority, and milestone (which release
its going to be fixed in.)
c. At some time, someone will try to fix it, usually a core developer.
If it’s not a core developer, it will always be attached as a patch
and reviewed.
d. Next step is peer review.
e. Patch gets improved, turned down, or accepted. This loop will
continue until the parties are happy with the code status.
f. Someone with commit access commits the patch.

======================================================================

When will 0.82 be end of life? – There is no answer to this currently
as it is to early to know what people in the field need. Should it be
long term, short term, very long term? These answers will come at some
stage, but not right now.

Currently packaging happens to fructose and glucose only. This will
not be the issue in the next release. RPMS will be automatically
created, though it will be the decision of the distribution in
question whether and how to use them. The .xo bundles will still be
there but will be overwritten (basically put into a different place
and given priority over the older relkease.)

===================================================================

Should we use package kit to standardize the packaging? This was a
question that came up and it is an interesting proposal, what do we think?

======================================================================

Auto testing of activities

======================================================================

There is something called sugarbot that should auto test activities.
It’s a google summer of code activity, but should be there for the
next release. It tests honey, not glucose, fructose.

We need a testing roadmap for glucose and fructose. Doing something
like what Gnome does would be good. We could also look at KDE. Are
there any other ideas on how to do this?

======================================================================

Buildbot will not run on the current hardware. We need to find a
sponsor for the machines and hosting?

This has now been communicated and should be fixed... As I understand
it, buildbot takes a look at some of the automation of testing packages
being built. Maybe alsroot can expand...

Development Team/Packaging

2009-04-23T15:20:08Z

Nubae:

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Distro
! Current development version
! Contact
! Last Sugar version
! Status
|-
| [[Community/Distributions/ALTLinux|ALT Linux]]
| Sisyphus
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
| [[Community/Distributions/Debian|Debian]]
| (multiple concurrent branches)
| [http://wiki.debian.org/JonasSmedegaard Jonas Smedegaard]
| See here: http://qa.debian.org/developer.php?login=debian-olpc-devel@lists.alioth.debian.org
| [[#Needs pyabiword|Needs pyabiword]], [[#Needs evince python bindings|Needs evince python bindings]]
|-
| [[Community/Distributions/Fedora|Fedora]]
| F11 (Leonidas)
| [[User:Erikos|Simon Schampijer]]
| 0.83.4 per http://koji.fedoraproject.org/koji/packageinfo?packageID=4562
|-
| [[Sugar_on_a_Stick|SoaS-1]]
| F10 based
|
| 0.84.x [http://download.sugarlabs.org/soas/repositories/1/ RPM repository]
|-
| [[Sugar_on_a_Stick|SoaS-2]]
| F11 based
|
| 0.84.x [http://download.sugarlabs.org/soas/repositories/2/ RPM repository]
|-
| [[Community/Distributions/Gentoo|Gentoo]]
| Sugar overlay
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|-
| [[Community/Distributions/Mandriva|Mandriva]]
| Cooker
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
| [http://en.opensuse.org/Sugar openSUSE]
| openSUSE Factory
| [http://en.opensuse.org/User:Nubae Nubae]
| 0.84.x
|-
| [[Community/Distributions/Ubuntu|Ubuntu]]
| 9.04 (Jaunty Jackalope)
| [https://wiki.ubuntu.com/SugarTeam SugarTeam]
| 0.83.x
| [[#Needs pyabiword|Needs pyabiword]]
|-
| [[Community/Distributions/Magalhães|Magalhães]] (Caixa Mágica)
| 12
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
|}

This table might be generated by a script like the one Collabora uses: http://people.collabora.co.uk/~cassidy/tp-versions.html

Source: http://people.collabora.co.uk/~cassidy/tp-versions.html

== Status notes ==

=== Needs pyabiword ===

In order for Write to work, abiword needs to be built with --enable-libabiword ([http://bugs.debian.org/512777 Debian bug #512777]) and the pyabiword package needs to be added.

=== Needs evince python bindings ===

In order for Read to work, evince needs to be built as a library and needs to have python bindings. This means evince 2.25.90 and gnome-python-desktop with the evince python bindings built.

Development Team/Packaging

2009-04-23T14:19:38Z

Nubae:

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Distro
! Current development version
! Contact
! Last Sugar version
! Status
|-
| [[Community/Distributions/ALTLinux|ALT Linux]]
| Sisyphus
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
| [[Community/Distributions/Debian|Debian]]
| (multiple concurrent branches)
| [http://wiki.debian.org/JonasSmedegaard Jonas Smedegaard]
| See here: http://qa.debian.org/developer.php?login=debian-olpc-devel@lists.alioth.debian.org
| [[#Needs pyabiword|Needs pyabiword]], [[#Needs evince python bindings|Needs evince python bindings]]
|-
| [[Community/Distributions/Fedora|Fedora]]
| F11 (Leonidas)
| [[User:Erikos|Simon Schampijer]]
| 0.83.4 per http://koji.fedoraproject.org/koji/packageinfo?packageID=4562
|-
| [[Sugar_on_a_Stick|SoaS-1]]
| F10 based
|
| 0.84.x [http://download.sugarlabs.org/soas/repositories/1/ RPM repository]
|-
| [[Sugar_on_a_Stick|SoaS-2]]
| F11 based
|
| 0.84.x [http://download.sugarlabs.org/soas/repositories/2/ RPM repository]
|-
| [[Community/Distributions/Gentoo|Gentoo]]
| Sugar overlay
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|-
| [[Community/Distributions/Mandriva|Mandriva]]
| Cooker
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
| [http://en.opensuse.org/Sugar openSUSE]
| openSUSE Factory
| [http://en.opensuse.org/User:Nubae|David Van Assche]
| 0.84.x
|-
| [[Community/Distributions/Ubuntu|Ubuntu]]
| 9.04 (Jaunty Jackalope)
| [https://wiki.ubuntu.com/SugarTeam SugarTeam]
| 0.83.x
| [[#Needs pyabiword|Needs pyabiword]]
|-
| [[Community/Distributions/Magalhães|Magalhães]] (Caixa Mágica)
| 12
| [[User:Alsroot|Aleksey Lim]]
| 0.84.x
|
|-
|}

This table might be generated by a script like the one Collabora uses: http://people.collabora.co.uk/~cassidy/tp-versions.html

Source: http://people.collabora.co.uk/~cassidy/tp-versions.html

== Status notes ==

=== Needs pyabiword ===

In order for Write to work, abiword needs to be built with --enable-libabiword ([http://bugs.debian.org/512777 Debian bug #512777]) and the pyabiword package needs to be added.

=== Needs evince python bindings ===

In order for Read to work, evince needs to be built as a library and needs to have python bindings. This means evince 2.25.90 and gnome-python-desktop with the evince python bindings built.

Marketing Team/Events/FOSDEM 2009

2009-01-18T10:08:35Z

Nubae: /* Attendance */

== About ==

OLPC / SugarLabs will have a presence at [http://www.fosdem.org/2009/ FOSDEM'09] taking place in Brussels (Belgium) from Saturday, February 7 to Sunday, February 8.

Additionally plans are underway to have a one-day OLPC / Sugar community meetup on (probably) Friday, February 6.

== Goals | FOSDEM'09 ==

* getting more developers to work on Sugar related tasks

== Goals | Community Meetup ==

* discussing the current state of things
* making plans for 2009:
** better defining the relation between OLPC and Sugar Labs
** advancing the Sugar platform
** making awesome educational content
** writing cool activities
** building and contacting relevant communities around OLPC and Sugar
** generally making it easier to contribute to OLPC and Sugar
** translating existing documentation (e.g. FlossManuals)
** writing materials geared towards how teachers can use the XO and Sugar in schools
** designing great marketing materials
** ...
* socializing, finally being able to put faces to nicknames

== Attendance ==

Please sign up here if you plan to attend!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name
! Community Meetup Friday 6th
! FOSDEM Saturday 7th
! FOSDEM Sunday 8th
! Notes
|-
| [[User:ChristophD|ChristophD]]
| Yes
| Yes
| Yes
| flight to Brussel is booked, will arrive on the evening of Feb. 5
|-
| [[User:niklaus|niklaus]]
| Yes
| Yes
| Yes
|
|-
| [[User:Tomeu|Tomeu]]
| Yes
| Yes
| Yes
| flight booked, arrive Feb 6th at 10.30am
|-
| [[User:BenjaminBerg|Benjamin Berg]]
| Yes
| Yes
| Yes
|
|-
| [[User:Marcopg|Marcopg]]
| Yes
| Yes
| Yes
| (not sure yet)
|-
| [[User:Cassidy|Guillaume Desmottes]]
| Yes
| Yes
| Yes
|
|-
| h01ger / Holger Levsen
| Yes
| Yes
| Yes
|
|-
| [[User:nubae|nubae / David Van Assche]]
| Yes
| Yes
| Yes
| flight to Brussel is booked, will arrive on the evening of Feb. 5
|-
|}

== Schedule ==

Tomeu is going to talk about [http://live.gnome.org/Brussels2009/Devroom#head-fed044e7ec0c3f61c0819739876aaa276e55c8e1 "The Sugar platform"] in the [http://live.gnome.org/Brussels2009/Devroom GNOME dev room] on Saturday 15:00.

Greg is going to talk about "Sugar and Fedora" in the [https://fedoraproject.org/wiki/FedoraEvents/FOSDEM/FOSDEM2009#Speakers_in_the_Dev_Room Fedora dev room] on Saturday 17.00.

== To-Do ==

* decide if we are going to ask a sister project for a piece of a booth (we did so last year in the GNOME booth)
* find a venue for the friday meeting
* lots of things...

== Comments ==

Please add relevant notes and thoughts!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

Marketing Team/Events/FOSDEM 2009

2009-01-18T10:01:55Z

Nubae: /* Attendance */

OLPC / SugarLabs will have a presence at [http://www.fosdem.org/2009/ FOSDEM'09] taking place in Brussels (Belgium) from Saturday, February 7 to Sunday, February 8.

Additionally plans are underway to have a one-day OLPC / Sugar community meetup on (probably) Friday, February 6.

== Goals | FOSDEM'09 ==

* getting more developers to work on Sugar related tasks

== Goals | Community Meetup ==

* discussing the current state of things
* making plans for 2009:
** better defining the relation between OLPC and Sugar Labs
** advancing the Sugar platform
** making awesome educational content
** writing cool activities
** building and contacting relevant communities around OLPC and Sugar
** generally making it easier to contribute to OLPC and Sugar
** translating existing documentation (e.g. FlossManuals)
** writing materials geared towards how teachers can use the XO and Sugar in schools
** designing great marketing materials
** ...
* socializing, finally being able to put faces to nicknames

== Attendance ==

Please sign up here if you plan to attend!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name
! Community Meetup Friday 6th
! FOSDEM Saturday 7th
! FOSDEM Sunday 8th
! Notes
|-
| [[User:ChristophD|ChristophD]]
| Yes
| Yes
| Yes
| flight to Brussel is booked, will arrive on the evening of Feb. 5
|-
| [[User:niklaus|niklaus]]
| Yes
| Yes
| Yes
|
|-
| [[User:Tomeu|Tomeu]]
| Yes
| Yes
| Yes
| flight booked, arrive Feb 6th at 10.30am
|-
| [[User:BenjaminBerg|Benjamin Berg]]
| Yes
| Yes
| Yes
|
|-
| [[User:Marcopg|Marcopg]]
| Yes
| Yes
| Yes
| (not sure yet)
|-
| [[User:Cassidy|Guillaume Desmottes]]
| Yes
| Yes
| Yes
|
|-
| h01ger / Holger Levsen
| Yes
| Yes
| Yes
|
|-
| [[User:nubae|David Van Assche]]
| Yes
| Yes
| Yes
|
|-
|}

== Schedule ==

Tomeu is going to talk about [http://live.gnome.org/Brussels2009/Devroom#head-fed044e7ec0c3f61c0819739876aaa276e55c8e1 "The Sugar platform"] in the [http://live.gnome.org/Brussels2009/Devroom GNOME dev room] on Saturday 15:00.

Greg is going to talk about "Sugar and Fedora" in the [https://fedoraproject.org/wiki/FedoraEvents/FOSDEM/FOSDEM2009#Speakers_in_the_Dev_Room Fedora dev room] on Saturday 17.00.

== To-Do ==

* decide if we are going to ask a sister project for a piece of a booth (we did so last year in the GNOME booth)
* find a venue for the friday meeting
* lots of things...

== Comments ==

Please add relevant notes and thoughts!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

Marketing Team/Events/FOSDEM 2009

2009-01-14T08:39:50Z

Nubae: /* Attending | FOSDEM'09 */

OLPC / SugarLabs will have a presence at [http://www.fosdem.org/2009/ FOSDEM'09] taking place in Brussels (Belgium) from Saturday, February 7 to Sunday, February 8.

Additionally plans are underway to have a one-day OLPC / Sugar community meetup on (probably) Friday, February 6.

== Goals | FOSDEM'09 ==

* getting more developers to work on Sugar related tasks

== Goals | Community Meetup ==

* discussing the current state of things
* making plans for 2009:
** better defining the relation between OLPC and Sugar Labs
** advancing the Sugar platform
** making awesome educational content
** writing cool activities
** building and contacting relevant communities around OLPC and Sugar
** generally making it easier to contribute to OLPC and Sugar
** translating existing documentation (e.g. FlossManuals)
** writing materials geared towards how teachers can use the XO and Sugar in schools
** designing great marketing materials
** ...
* socializing, finally being able to put faces to nicknames

== Attending | FOSDEM'09 ==

Please sign up here if you plan to attend!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

* [[User:ChristophD|ChristophD]] (flight to Brussel is booked, will arrive on the evening of Feb. 5)
* [[User:niklaus|niklaus]]
* [[User:Tomeu|Tomeu]]
* [[User:BenjaminBerg|Benjamin Berg]]
* [[User:Marcopg|Marcopg]] (not sure yet)
* [[User:Cassidy|Guillaume Desmottes]]
* h01ger / Holger Levsen
* [[User:nubae|David Van Assche]]

== Attending | Community Meetup ==

Please sign up here if you plan to attend!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)

* [[User:ChristophD|ChristophD]] (flight to Brussel is booked, will arrive on the evening of Feb. 5)
* [[User:niklaus|niklaus]]
* [[User:Tomeu|Tomeu]] (flight booked, arrive Feb 6th at 10.30am)
* [[User:BenjaminBerg|Benjamin Berg]]
* [[User:Marcopg|Marcopg]] (not sure yet)
* [[User:Erikos|Erikos]] (not sure yet, will try my best)
* h01ger / Holger Levsen

== Schedule ==

TBD

Have proposed two talks, one in the [https://fedoraproject.org/wiki/FedoraEvents/FOSDEM/FOSDEM2009#Speakers_in_the_Dev_Room Fedora dev room] and the other in the [http://live.gnome.org/Brussels2009/Devroom GNOME dev room]. [[User:Tomeu|tomeu]] 12:29, 7 January 2009 (UTC)

== To-Do ==

* decide if we are going to ask a sister project for a piece of a booth (we did so last year in the GNOME booth)
* find a venue for the friday meeting
* lots of things...

== Comments ==

Please add relevant notes and thoughts!
[[User:ChristophD|ChristophD]] 03:40, 7 January 2009 (UTC)