Sugar Labs - User contributions [en]

Development Team/Jhbuild/Debian

2021-07-03T08:46:17Z

Sascha silbe: Removed outdated information: Debian#648724 has been fixed for a long time

== Supported versions ==
Currently Wheezy (testing) and Sid (unstable) are supported.

Squeeze isn't supported any more because Sugar is in the progress of migrating to GTK 3 / Gnome 3, requiring bleeding edge versions of a couple of components.

== Prerequisites ==
In order to install sugar-jhbuild, you need to install git-core, lsb-release, python and subversion:
sudo aptitude install git-core lsb-release python subversion pkg-config

== Installing dependencies ==
After installing and updating sugar-jhbuild according to the [[../|common instructions]], you can use this invocation to install all dependencies automatically:

./sugar-jhbuild depscheck -s | sudo xargs aptitude -y install

== Known issues ==

In order to use [[Activities/Read|Read]], you will need gir1.2-evince-3.0 >= 3.3.90-1, currently only available in [http://wiki.debian.org/DebianExperimental Debian experimental].
sudo apt-get install -t experimental gir1.2-evince-3.0 libevview3-3

Design Team/Contacts

2021-07-03T08:43:58Z

Sascha silbe: Remove myself; have been inactive for a long time

<noinclude>{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}[[Category:Design Team]][[Category:Contact]]
</noinclude>

== Coordinators ==
{{:Design Team/Coordinator}}

== IRC channel ==
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.

== Team Members ==
Please add yourself to the list if you're interested in participating!

*[[User:Walter | Walter Bender]]
*[[User:MartinDengler | Martin Dengler]]
*[[User:Eben | Eben Eliason]]
*[[User:FGrose | Frederick Grose]]
*[[User:Walter | Fadi Tash]]
*[[User:Josh | Josh Williams]]
*[[User:David Brown|David Brown]] 21:37, 22 August 2012 (EDT)
* [[User:Sebastian|Sebastian Silva]]
*[[User:PFidelis | Peace Ojemeh]]

User:Sascha silbe

2021-07-03T08:43:00Z

Sascha silbe: Remove outdated information

Machine/lightwave

2021-07-03T08:41:18Z

Sascha silbe: Remove outdated information: myself as admin, PGP keyserver

== 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.

In the future, it will 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

== Notes ==

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

Service/keys

2013-06-17T10:06:10Z

Sascha silbe: keys.sugarlabs.org is down and won't come back

== Description ==

{{Obsolete|keys.sugarlabs.org is down and won't come back}}

keys.sugarlabs.org '''was''' an OpenPGP [http://en.wikipedia.org/wiki/Key_server_(cryptographic) key server] powered by the [https://bitbucket.org/yminsky/sks-keyserver SKS] keyserver software.

We use [http://www.monkeysphere.info Monkeysphere] to allow users to [http://web.monkeysphere.info/doc/service-authentication-ssh/ authenticate our SSH host keys] using their PGP web of trust. Future plans include [http://web.monkeysphere.info/doc/ssh-user-authentication managing user keys] (authorized_keys) as well. Monkeysphere regularly searches for and fetches (potential) [http://tools.ietf.org/html/rfc4880 OpenPGP] keys for all users to check for new and/or revoked keys, which causes some load on keyservers. In order not to annoy operators of (other) public keyservers, we run our own. As a nice side effect we contribute back to the OpenPGP community by being [http://sks-keyservers.net/status/info/keys.sugarlabs.org part of] the [http://sks-keyservers.net/overview-of-pools.php SKS keyserver pool], similar to what we do for [[Service/time|NTP]].

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats Status] as provided by the server itself
* [http://sks-keyservers.net/status/info/keys.sugarlabs.org Status] as monitored by the pool

== Hostnames ==

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats keys.sugarlabs.org]

== Hosted on ==

keys.sugarlabs.org was hosted on [[Machine/lightwave]].

== Administrative contact ==

[http://lists.sugarlabs.org/listinfo/systems systems AT sugarlabs DOT org]

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* <strike>[[User:sascha_silbe|Sascha Silbe]]</strike>

== Notes ==

== Upgrade notes ==

== See Also ==

[[Category:Service|keys]]

Service/keys

2012-06-03T08:53:50Z

Sascha silbe: /* Description */ update link to SKS

== Description ==

keys.sugarlabs.org is an OpenPGP [http://en.wikipedia.org/wiki/Key_server_(cryptographic) key server] powered by the [https://bitbucket.org/yminsky/sks-keyserver SKS] keyserver software.

We use [http://www.monkeysphere.info Monkeysphere] to allow users to [http://web.monkeysphere.info/doc/service-authentication-ssh/ authenticate our SSH host keys] using their PGP web of trust. Future plans include [http://web.monkeysphere.info/doc/ssh-user-authentication managing user keys] (authorized_keys) as well. Monkeysphere regularly searches for and fetches (potential) [http://tools.ietf.org/html/rfc4880 OpenPGP] keys for all users to check for new and/or revoked keys, which causes some load on keyservers. In order not to annoy operators of (other) public keyservers, we run our own. As a nice side effect we contribute back to the OpenPGP community by being [http://sks-keyservers.net/status/info/keys.sugarlabs.org part of] the [http://sks-keyservers.net/overview-of-pools.php SKS keyserver pool], similar to what we do for [[Service/time|NTP]].

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats Status] as provided by the server itself
* [http://sks-keyservers.net/status/info/keys.sugarlabs.org Status] as monitored by the pool

== Hostnames ==

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats keys.sugarlabs.org]

== Hosted on ==

[[Machine/lightwave]]

== Administrative contact ==

[http://lists.sugarlabs.org/listinfo/systems systems AT sugarlabs DOT org]

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:sascha_silbe|Sascha Silbe]]

== Notes ==

== Upgrade notes ==

== See Also ==

[[Category:Service|keys]]

HIG

2012-03-26T17:11:46Z

Sascha silbe: Link from acronym to actual page. The acronym is easier to type (for posting links or jumping directly to the page rather than navigating the wiki).

#REDIRECT [[Human Interface Guidelines]]

Development Team/Jhbuild/Fedora

2012-03-19T21:17:39Z

Sascha silbe: /* Supported versions */ minimum version is F16 now because of sugar-toolkit-gtk3

==Supported versions==

You will need at least Fedora 16. Fedora 17 or later is recommended (and required in order to run [[Activities/Read|Read]]).

To determine which version you are using, just run the following (you may need to install it first, see below for instructions):
lsb_release -ir

==Prerequisites==

yum install redhat-lsb

Other than that and the packages mentioned by <code>./sugar-jhbuild depscheck</code> (please see the non-distro specific instructions) nothing else should be required.
If you notice that any package is required, but not mentioned by depscheck, please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component on the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].

Development Team/Jhbuild/Debian

2012-03-19T20:44:37Z

Sascha silbe: mention known issues

== Supported versions ==
Currently Wheezy (testing) and Sid (unstable) are supported.

Squeeze isn't supported any more because Sugar is in the progress of migrating to GTK 3 / Gnome 3, requiring bleeding edge versions of a couple of components.

== Prerequisites ==
In order to install sugar-jhbuild, you need to install git-core, lsb-release, python and subversion:
sudo aptitude install git-core lsb-release python subversion

== Installing dependencies ==
After installing and updating sugar-jhbuild according to the [[../|common instructions]], you can use this invocation to install all dependencies automatically:

./sugar-jhbuild depscheck -s | sudo xargs aptitude -y install

== Known issues ==

Sugar will currently fail to start up because of [http://bugs.debian.org/648724 Debian#648724]. Until the package maintainer uploads the fix to the official Debian archive, you can build the patched package yourself. [[User:Sascha_silbe|Sascha Silbe]] can provide binary packages for amd64, armel, i386 and maybe powerpc on request.

In order to use [[Activities/Read|Read]], you will need gir1.2-evince-3.0 >= 3.3.90-1, currently only available in [http://wiki.debian.org/DebianExperimental Debian experimental].

Development Team/Jhbuild/Debian

2012-03-19T20:37:14Z

Sascha silbe: /* Supported versions */ Squeeze isn't good enough any more

Features/Introduction Tutorial

2012-03-06T16:42:22Z

Sascha silbe: /* Documentation */ tutorius.org is got grabbed :-/

<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Introduction_Tutorial]]

</noinclude>





== Summary ==
Provide an interactive introduction to Sugar for first-time users.

== Owner ==
* Name: [[User:ErickLavoie| Erick Lavoie]]
* Email: Name above in lowercase AT gmail.com

== Current status ==
* Targeted release: Undefined
* Last updated: 04-26-2010
* Percentage of completion: Suspended

Note: Due to a higher than expected work requirement at the master level, I'll be suspending work on Tutorius indefinitely. I'll leave the page here, so that the idea is still available. Should anybody want to have more information on how Tutorius was working, I'll be glad to share.

== Detailed Description ==
The proposal consists in providing a default interactive tutorial for Sugar that will give an overview of the particularities of the Sugar interface.

The proposal aims at giving an overview of the Frame, the different Views, the Journal, Browse and Write in a single tutorial.

The tutorial should be stored as an XML file representing the execution states of the tutorial.

Translation of the tutorial should be made using the gettext convention by storing translations of the tutorial strings along side the XML file using the gettext schema (.po, .pot, .mo files).

The tutorial should be independent of the screen resolution.

For the 0.90 release, the tutorial won't be user modifiable other than by modifying the XML format by hand, which won't be recommended.

== Benefit to Sugar ==
This feature should lower the barrier of entry to Sugar by making it easier to learn the platform by having to resort less to external documentation.

As discussed with Gerald Ardito, picking up Activities seems to work well for most students. However, getting used to the specific idioms of Sugar requires more efforts and therefore would benefit from having an interactive tutorial.

== Scope ==
Most of the work has already been done as part of the Tutorius project that ended on December 2009. However, there is still some work to do before the existing system can reliably be integrated to Sugar. The modifications to Sugar as well as the work to be done is outlined below.

=== Sugar Modifications ===
The major changes to Sugar consist in introducing two new concepts, Probes and Overlays, and an additional service in the sugar-session.

Probes allow obtaining events from Activities/Shell and the execution of arbitrary actions from a separate process. This ability should be reviewed in light of the security policy of Sugar.

Overlays are Layouts or Windows used to draw custom graphics on top of Activities, the Frame, the Journal or any Sugar View. A more complete description for Probes and Overlays is given in the Tutorius Architecture document referred in the Documentation section.

The tutorius service in the sugar-session adds an Engine to execute tutorials, a registering mecanism to register and unregister Probes when Activities are started and stopped and a dbus interface to start and stop tutorials.

Those changes involve modifications of less than 100 lines of code in the existing Sugar code base to the following files:
* sugar:bin/sugar-session (Add the tutorius service)
* sugar:src/jarabe/frame/frame.py (Add an Overlay and a Probe)
* sugar:src/journal/journalactivity.py (Add a Probe)
* sugar-toolkit:src/sugar/activity/activity.py (Add a Probe)
* sugar-toolkit:src/sugar/graphics/window.py (Add an Overlay)

In addition to the previous modifications:
* The tutorius files should be found under the sugar.tutorius module.
* Some icons will be added.
* The tutorial will be stored under ./sugar/default/tutorius in the user home directory.

=== Tasks ===
# Define an [[Features/Introduction_Tutorial/Script | exact script]] for the introduction tutorial
# Rebase the existing Tutorius code base on top of Sugar 0.88
# Create a reliable [[Features/Introduction_Tutorial/Overlay | Overlay]] for all the different Views and the Frame
# Make the Message Bubble position relative to the screen size
# Make sure the current localization mecanism is reliable
# Add the logging screen option (See UI Mocks)
# Add the option item to replay the introduction tutorial (See UI Mocks)
# Produce a tutorial
# Translate the tutorial in French
# Write documentation for the translation team

The only risky item is the creation of a reliable Overlay for the different Views. For a technical description of what it involves, see [[Features/Introduction_Tutorial/Overlay]]. Any help from GTK gurus in the community is welcome, as our last attempt at this was unsuccessful.

==UI Design==
This tutorial should be accessible from the first login screen, right after the color selection, and from the option menu:

http://tutorius.org/blog/wp-content/uploads/2010/03/login1-300x226.png
http://tutorius.org/blog/wp-content/uploads/2010/03/options-300x225.png

The tutorial will provide an overview of the Desktop, the Group and the Neighborhood Views as well as the Frame, the Journal, the Write and the Browse activity. Here are screenshots of what it might look like for some of them.

http://tutorius.org/blog/wp-content/uploads/2010/03/desktop-300x214.png
http://tutorius.org/blog/wp-content/uploads/2010/03/neighborhood-300x214.png
http://tutorius.org/blog/wp-content/uploads/2010/03/journal-300x216.png
http://tutorius.org/blog/wp-content/uploads/2010/03/write-300x216.png

The information presented to the user will be essentially composed of bubble messages pointing at screen elements. Progress through the tutorial will be accomplished by the user clicking a next button at the bottom of the screen. Once the tutorial is over, the user will be brought back to the Desktop screen where she will be able to resume interacting with the system normally. At any time during the tutorial, the user can press the Stop button to interrupt the current tutorial and return to the place she was when she started the tutorial.

== How To Test ==
{{:{{PAGENAME}}/Testing}}

== User Experience ==
The tutorial won't affect the regular workflow or experience for the platform other than providing a tutorial on the first connexion.

== Dependencies ==
None.

== Contingency Plan ==
Revert to the previous release behavior.

== Documentation ==
*http://docs.google.com/Doc?docid=0AVT_nzmWT2B2ZGN3dDd2MzRfNTF0dzMyNGdnag&hl=en (Meeting with Gerald Ardito and John Tierney)
*http://docs.google.com/Doc?docid=0AVT_nzmWT2B2ZGN3dDd2MzRfNTBka3J4bW1kaA&hl=en (Tutorius Engine States)

The following document provides a high-level view of the Tutorius Architecture. The original system was more powerful since it allowed Creation and Sharing of tutorials from within Sugar also. However, for the purpose of this feature proposal and to ease integration, only the Execution of tutorials will be considered. For the time being, any reference to the Store, the Workshop, the Creator and the Remote may safely be ignored. They are kept in case a further integration of those tools is accepted by the community in a later release.

The execution scenarios presented are not completely up-to-date and will be revised in the next weeks. For the time being, the most interesting part should be the component diagrams and descriptions.
*http://docs.google.com/Doc?docid=0ARkLUElWcqxDZGdkOWo3c2ZfOWdqeGtyZmY2&hl=en#Components_2405436521573161_98 (Tutorius Architecture)

* <nowiki>http://www.tutorius.org</nowiki> (Website for the project that ended on December 2009; now owned by a domain grabber)

== Source Code ==

* http://git.sugarlabs.org/projects/tutorius

Forks of sugar components:
* http://git.sugarlabs.org/projects/sugar-toolkit/repos/sugar-toolkit-tutorius
* http://git.sugarlabs.org/projects/sugar/repos/tutorius
* http://git.sugarlabs.org/projects/sugar-jhbuild/repos/tutorius

== Release Notes ==
A default interactive tutorial is provided on the first login to help familiarize a new user to Sugar. This tutorial can also be replayed anytime from the option menu.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Dextrose/Building

2012-03-05T19:02:22Z

Sascha silbe: /* Creating a build */ document image variants

<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}</noinclude>

== Dextrose build system ==

Dextrose uses [http://wiki.laptop.org/go/OS_Builder olpc-os-builder], a tool create by OLPC to build official and customized system images. The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose, and fixes and enhancements waiting to be pushed upstream.

== Build host requirements ==

The Dextrose build system is known to work on '''Fedora 14 x86_64''' and '''Fedora 16 x86_64'''. The OS on the host system ''shouldn't'' matter because the build runs in a chroot environment. olpc-os-builder does not yet run on Ubuntu due to a missing dependency (bitfrost).

The initial build requires about '''700MB''' of rpm packages and Sugar activity bundles. The packages and bundles are cached for futures builds.

== Initial setup ==

* If sudo isn't configured to work with your account, add yourself to the '''wheel''' group. Alternatively, you can become root with <code>su -</code>.

* Install build dependencies (you need to be root to do this)

yum upgrade
yum install libtomcrypt-devel bitfrost crcimg make gcc mtd-utils python-imgcreate zip unzip zlib-devel lzma

* Install the olpc-bootanim-tools package:

rpm -i http://download.sugarlabs.org/dextrose/testing/dx3/rpms/x86_64/os/olpc-bootanim-tools-2.14-1.bernie1.fc16.x86_64.rpm

If you have a 32bit machine:

rpm -i http://download.sugarlabs.org/dextrose/testing/dx3/rpms/i386/os/olpc-bootanim-tools-2.14-1.bernie1.fc16.i686.rpm

Alternatively, you could rebuild the olpc-bootanim package from source:

yum install rpm-build netpbm-progs
wget http://download.sugarlabs.org/dextrose/testing/dx3/rpms/source/olpc-bootanim-2.14-1.bernie1.fc16.src.rpm
rpmbuild --rebuild olpc-bootanim-2.14-1.bernie1.fc16.src.rpm
rpm -U ~/rpmbuild/RPMS/*/olpc-bootanim-tools-*.rpm

* Checkout the Dextrose build system

git clone git://git.sugarlabs.org/dextrose/mainline.git dextrose

* Compile build helper programs

cd dextrose
make

* Generate initial sequence number for the builds (42 is just an example)

echo 42 >buildnr-dx

== Creating a build ==

* Become root and run the build system:

time sudo ./osbuilder.py config/dextrose3-xo1-nognome.ini

The initial build may take several hours, depending on available bandwidth.
Subsequent builds will take about 15-20 minutes on average desktop machines.

Upon completion, the new image will be available in <tt>build/output</tt>.
Now copy it on a USB stick and test it on your target.

=== Available variants ===

There's a set of configuration files for each variant of the images you can build. You only need to specify the top-level file (i.e. none of the <code>*-common.ini</code> files) to build an image:

;dextrose3-xo1-gnome.ini:
:Works on [[olpc:XO-1|XO-1]], includes Gnome. Not recommended unless you're running from an external SD card as the free space available on the internal NAND is too limited with Gnome installed.
;dextrose3-xo1-nognome.ini:
:Works on [[olpc:XO-1|XO-1]], does not include Gnome. This is the recommended image for XO-1s.
;dextrose3-xo1.5-gnome.ini:
:Works on [[olpc:XO-1.5|XO-1.5]] (including XO-1.5 [[olpc:OLPC_English_Non-membrane_Keyboard|HS]]), includes Gnome. Some teachers and older students seem to like Gnome, so you can trade off some of the free space that could be used by the Journal for the additional desktop environment.
;dextrose3-xo1.5-nognome.ini:
:Works on [[olpc:XO-1.5|XO-1.5]] (including XO-1.5 [[olpc:OLPC_English_Non-membrane_Keyboard|HS]]), doesn't include Gnome. More space for the Journal, so use this one if your users don't ask for Gnome and you haven't paid for a larger (i.e. > 4GB) SD card.
;dextrose3-xo1.75-gnome.ini:
:Experimental [[olpc:XO-1.75|XO-1.75]] image with Gnome.
;dextrose3-xo1.75-nognome.ini:
:Experimental [[olpc:XO-1.75|XO-1.75]] image without Gnome.

== Debugging ==

Because several build tools (olpc-os-builder, imgcreate and yum) run chrooted
and nested into each other, error output is often obscure or misleading.
Before digging into the code, try asking on IRC in case someone has already seen
the same problem.

== Publishing the images ==

Please do not publish signed builds unless they implement the [http://wiki.laptop.org/go/Antitheft_HowTo OLPC anti-theft system].

== Customizing your build ==

olpc-os-builder is documented at
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/doc/README README]
in the olpc-os-builder tree. The modules are documented in <tt>README</tt> files in the
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/modules modules] directory.

=== Upstream Code ===

Dextrose is based on [http://dev.laptop.org/git/projects/olpc-os-builder/ olpc-os-builder] by Daniel Drake. You can fetch the latest source code into your Dextrose repository:

git remote add olpc git://dev.laptop.org/projects/olpc-os-builder
git fetch olpc
git log olpc/master

=== Customizing the core RPMs ===

* Go to the <tt>rpms/PACKAGENAME</tt> in the dextrose tree

* Edit the spec file. Typically this involves adding a new patch, which is done by adding a <tt>PatchNN:</tt> tag and a corresponding <tt>%patchNN</tt> rule in <tt>%setup</tt>. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].

* Increase the release number after each change.

=== building the Custom RPM ===

If you have a Fedora 11 i386 system, just type:

make i586

Otherwise, you need to build in a [http://fedoraproject.org/wiki/Projects/Mock mock] chroot:

make srpm
sudo mock -r fedora-11-i386 --resultdir=. --rebuild mypackage.src.rpm

=== Uploading the Custom RPM ===

* Upload rpm to a yum repository and add it to the ini file used by the OLPC OS builder.

* To automate this step, we have a rule <tt>make uploadrpm</tt> which points at the Dextrose repository. Edit <tt>rpms/common/Makefile.common</tt> or <tt>rpms/common/uploadrpm</tt> to retarget this rule to your repository.

=== Building custom kernels ===

$ git clone http://dev.laptop.org/git/olpc-2.6/
$ cd olpc-2.6
$ setarch i386 make ARCH=i386 xo_1-kernel-rpm

== Resources ==

* [[Machine/dextrose|Dextrose VM]] hosted by [[Machine/treehouse|treehouse]]

* [[Development_Team/Jhbuild|Sugar-jhbuild]] - The Sugar build system

* [http://www.rpm.org/wiki/Docs RPM] - The Red Hat package manager

* [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora packaging] - Fedora packaging workflow and conventions

* [http://createrepo.baseurl.org/ createrepo] - the yum package repositories builder

* [http://activities.sugarlabs.org ASLO] - The Sugar Labs Activities Library

* General understanding of the Linux system plumbing infrastructure: [http://www.kernel.org/ kernel],
[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev], [http://www.freedesktop.org/wiki/Software/dbus dbus], [http://www.freedesktop.org/wiki/Software/DeviceKit DeviceKit], [http://www.freedesktop.org/wiki/NetworkManager NetworkManager],
[http://www.x.org/wiki/ Xorg]...

* Flashing laptops and debugging any problems

* Interaction with the Sugar and OLPC community to solve issues and minimize our divergence from the official builds.

Features/Proxy Settings

2012-02-14T13:36:49Z

Sascha silbe: Update to reflect current status

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Set up a proxy on a computer in the same network
* Open Owner icon → Network Control Panel
* Change the proxy settings according to your proxy setup
* Switch to Gnome and check that Gnome Control Center → Network → Network proxy has the same options set
* Use Browse to access the [https://www.sugarlabs.org/ Sugar Labs home page]

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2012-02-14T13:13:31Z

Sascha silbe: /* UI Design */ update screenshots

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Setting proxy parameters via special Control Panel component.

== Owner ==

* Code: [[User:alsroot|Aleksey Lim]]
* Icons: [[User:M_anish| Anish Mangal]]

== Current status ==

* Targeted release: 0.96
* Last updated: 2Tue Nov 22 20:40:01 UTC 2011
* Percentage of completion: 95%

== Detailed Description ==

In some cases people might be behind HTTP proxy. For now, there is no any users friendly way in Sugar to setup proxy setting.

== Benefit to Sugar ==

Set proxy parameters without using low level tools like gconftool or switching to Gnome session. This is especially required in Australia and is being developed by ActivityCentral following their input.

== Scope ==

New Control Panel component.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* clone [http://git.sugarlabs.org/alsroot/proxy_cp sources]
* symlink cloned directory to CP components directory, {{Code|/usr/share/sugar/extensions/cpsection}} by default
* restart sugar shell
* open Proxy CP component and setup proxy connection
* open gnome-network-setting and check if it has the same options set

== User Experience ==

The feature is entirely localized only within Control Panel.

== Dependencies ==

None.

== Contingency Plan ==

Do not use new Control Panel component.

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Gnome-3-proxy-settings.png

2012-02-14T13:12:36Z

Sascha silbe: Screenshot of the Gnome 3 Control Center showing the proxy settings.

Screenshot of the Gnome 3 Control Center showing the proxy settings.

File:Proxy-section-5.png

2012-02-14T13:03:20Z

Sascha silbe: Screenshot of the lower part of the Network Control Panel, showing the proxy section with manual proxy settings for a proxy that '''does''' require authentication.

Screenshot of the lower part of the Network Control Panel, showing the proxy section with manual proxy settings for a proxy that '''does''' require authentication.

File:Proxy-section-4.png

2012-02-14T13:02:47Z

Sascha silbe: Screenshot of the lower part of the Network Control Panel, showing the proxy section with manual proxy settings for a proxy that does '''not''' require authentication.

Screenshot of the lower part of the Network Control Panel, showing the proxy section with manual proxy settings for a proxy that does '''not''' require authentication.

File:Proxy-section-3.png

2012-02-14T13:00:00Z

Sascha silbe: Screenshot of the lower part of the Network Control Panel, showing the proxy section with WPAD selected.

Screenshot of the lower part of the Network Control Panel, showing the proxy section with WPAD selected.

File:Proxy-section-2.png

2012-02-14T12:57:48Z

Sascha silbe: Screenshot of the lower part of the Network Control Panel, showing the proxy section with no proxy set (i.e. direct connection).

Screenshot of the lower part of the Network Control Panel, showing the proxy section with no proxy set (i.e. direct connection).

File:Proxy-section-1.png

2012-02-14T12:55:58Z

Sascha silbe: Screenshot of the upper part of the Network Control Panel, showing part of the proxy section.

Screenshot of the upper part of the Network Control Panel, showing part of the proxy section.

Service/keys

2012-02-14T09:55:48Z

Sascha silbe: /* Description */ update link to SKS homepage

== Description ==

keys.sugarlabs.org is an OpenPGP [http://en.wikipedia.org/wiki/Key_server_(cryptographic) key server] powered by the [http://code.google.com/p/sks-keyserver/ SKS] keyserver software.

We use [http://www.monkeysphere.info Monkeysphere] to allow users to [http://web.monkeysphere.info/doc/service-authentication-ssh/ authenticate our SSH host keys] using their PGP web of trust. Future plans include [http://web.monkeysphere.info/doc/ssh-user-authentication managing user keys] (authorized_keys) as well. Monkeysphere regularly searches for and fetches (potential) [http://tools.ietf.org/html/rfc4880 OpenPGP] keys for all users to check for new and/or revoked keys, which causes some load on keyservers. In order not to annoy operators of (other) public keyservers, we run our own. As a nice side effect we contribute back to the OpenPGP community by being [http://sks-keyservers.net/status/info/keys.sugarlabs.org part of] the [http://sks-keyservers.net/overview-of-pools.php SKS keyserver pool], similar to what we do for [[Service/time|NTP]].

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats Status] as provided by the server itself
* [http://sks-keyservers.net/status/info/keys.sugarlabs.org Status] as monitored by the pool

== Hostnames ==

* [http://keys.sugarlabs.org:11371/pks/lookup?op=stats keys.sugarlabs.org]

== Hosted on ==

[[Machine/lightwave]]

== Administrative contact ==

[http://lists.sugarlabs.org/listinfo/systems systems AT sugarlabs DOT org]

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:sascha_silbe|Sascha Silbe]]

== Notes ==

== Upgrade notes ==

== See Also ==

[[Category:Service|keys]]

Development Team/Release

2012-01-31T17:28:58Z

Sascha silbe: /* String cooling */ fix syntax error

<noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>
== Goals and modules proposal ==

At the beginning of each release [[:Category:Platform Cycle|cycle]], maintainers will work on a set of goals, document them and assign owners. See the upcoming stable release, [[{{Upcoming Stable Release}}/Roadmap]]. (These goals typically involve major interventions or the addition of new components, e.g., someone develops a speech engine specially for his mother tongue and wants it in Sugar. Hence, the process described below is primarily for module maintainers. If you are a developer with a feature or bug fix, you may want to refer to the [[Features/Feature Template|new feature process]].)

=== New modules proposal ===

The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following information:

(See [[Features/Feature Template]].)

* Short description of the features.
* Screenshots or screencasts.
* Are you willing to follow the [[Development Team/Release/Roadmap#Schedule|Schedule]]?
* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)
* System components the activity depends on.
* Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web.
* Status of internationalization.
* Code repository.
* Bug tracking system.
* Homepage.

Criteria for approval will be:

* Supports internationalisation and localisation.
* Does not duplicate the functionalities of other activities.
* Provide functionality that the community judges as important for reaching the goals of the project.
* Maintainer responsiveness and willingness to provide regular releases.



== Module release ==

For both intermediates and final releases module maintainers are responsible to announce the module release and make the sources available. Note that the release number of the module does not need to match the Sucrose release number.
More in detail:

{{Anchor|Glucose}}
=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===
* Build a source tarball

make distcheck

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).

* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is:
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

{{Anchor|Fructose}}
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
* Build a source tarball
If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.

python setup.py dist_source

The tarball will be generated inside the dist directory.

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).

* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there.

The preferred location for fructose components is:
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/
which translates to:
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.

=== Using the release script ===
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.

You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):

./release --help

== Sugar release cycle==
{{Template:Platform Cycle Linkbar}}

Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:

* Ensure that all the module releases are available by the scheduled date.
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.
* If issues arise coordinate with the relevant module maintainers to solve them.
* Announce the release on sugar-devel@lists.sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.

=== Roadmap Update ===

The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:

* Detailed schedule of release dates and freeze points.
* List of modules and external dependencies.
* Reference to all the tickets considered for the release.
* References to the new feature proposals.

=== Feature freeze ===
By Feature Freeze all new features have to be complete, reviewed and pushed to the repository. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.

This allows developers to concentrate on refining the new features instead of adding yet more functionality.

The feature freeze affects all the modules included in the release and comprise also ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], referencing the patches you would like to land. It will have to be granted by two [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.

=== UI Freeze ===
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.

This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.

If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.

=== String cooling===
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.

=== String Freeze===
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.

=== Stabilizing ===
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:
|TestCase|
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.

=== Hard code freeze ===
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[Development Team/Release/Contacts#People|members]] of the team.

=== Branching ===

After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.

A new branch is created on the Pootle server, e.g., Fructose-0.82 and Fructose-0.84. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.

You can create a remote branch like this (in your repository):

git branch sucrose-0.84
git push origin sucrose-0.84

And to work on it (in your repository):

git checkout -b sucrose-0.84 origin/sucrose-0.84
git pull

== Bug triaging ==

Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.

Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases.

== Automation ==

TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.

==Related pages==
{{Template:Platform Cycle Linkbar}}

See also [[:Category:Release Notes]]{{Special:PrefixIndex/{{PAGENAME}}/}}

Features/Proxy Settings

2012-01-24T17:34:17Z

Sascha silbe: /* UI Design */ Updated screenshots

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Setting proxy parameters via special Control Panel component.

== Owner ==

* Code: [[User:alsroot|Aleksey Lim]]
* Icons: [[User:M_anish| Anish Mangal]]

== Current status ==

* Targeted release: 0.96
* Last updated: 2Tue Nov 22 20:40:01 UTC 2011
* Percentage of completion: 95%

== Detailed Description ==

In some cases people might be behind HTTP proxy. For now, there is no any users friendly way in Sugar to setup proxy setting.

== Benefit to Sugar ==

Set proxy parameters without using low level tools like gconftool or switching to Gnome session. This is especially required in Australia and is being developed by ActivityCentral following their input.

== Scope ==

New Control Panel component.

== UI Design ==

The feature adds a button and UI to the My-Settings window. Mockups below.

[[File:Cp-proxy.png|center|600px]]

[[File:Proxy-cp-2.png|center|600px]] [[File:Proxy-cp-3.png|center|600px]]

For comparison, this is what the Gnome 2 proxy settings dialog looks like:

[[File:Gnome2-proxy-settings.png|600px]]

== How To Test ==

* clone [http://git.sugarlabs.org/alsroot/proxy_cp sources]
* symlink cloned directory to CP components directory, {{Code|/usr/share/sugar/extensions/cpsection}} by default
* restart sugar shell
* open Proxy CP component and setup proxy connection
* open gnome-network-setting and check if it has the same options set

== User Experience ==

The feature is entirely localized only within Control Panel.

== Dependencies ==

None.

== Contingency Plan ==

Do not use new Control Panel component.

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Proxy-cp-3.png

2012-01-24T17:32:00Z

Sascha silbe: Screenshot of (the lower half of) the proxy Control Panel.

Screenshot of (the lower half of) the proxy Control Panel.

File:Proxy-cp-2.png

2012-01-24T17:31:37Z

Sascha silbe: Screenshot of (the upper half of) the proxy Control Panel.

Screenshot of (the upper half of) the proxy Control Panel.

Features/Proxy Settings

2012-01-24T16:19:54Z

Sascha silbe: /* UI Design */ swap mockups so Sugar and Gnome can be compared directly

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Setting proxy parameters via special Control Panel component.

== Owner ==

* Code: [[User:alsroot|Aleksey Lim]]
* Icons: [[User:M_anish| Anish Mangal]]

== Current status ==

* Targeted release: 0.96
* Last updated: 2Tue Nov 22 20:40:01 UTC 2011
* Percentage of completion: 95%

== Detailed Description ==

In some cases people might be behind HTTP proxy. For now, there is no any users friendly way in Sugar to setup proxy setting.

== Benefit to Sugar ==

Set proxy parameters without using low level tools like gconftool or switching to Gnome session. This is especially required in Australia and is being developed by ActivityCentral following their input.

== Scope ==

New Control Panel component.

== UI Design ==

The feature adds a button and UI to the My-Settings window. Mockups below.

[[File:Cp-proxy.png|center|600px]]

[[File:Proxy.png|center|600px]]

For comparison, this is what the Gnome 2 proxy settings dialog looks like:

[[File:Gnome2-proxy-settings.png|600px]]

== How To Test ==

* clone [http://git.sugarlabs.org/alsroot/proxy_cp sources]
* symlink cloned directory to CP components directory, {{Code|/usr/share/sugar/extensions/cpsection}} by default
* restart sugar shell
* open Proxy CP component and setup proxy connection
* open gnome-network-setting and check if it has the same options set

== User Experience ==

The feature is entirely localized only within Control Panel.

== Dependencies ==

None.

== Contingency Plan ==

Do not use new Control Panel component.

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2012-01-24T16:18:37Z

Sascha silbe: /* UI Design */ Add Gnome 2 proxy settings screenshot for comparison

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Setting proxy parameters via special Control Panel component.

== Owner ==

* Code: [[User:alsroot|Aleksey Lim]]
* Icons: [[User:M_anish| Anish Mangal]]

== Current status ==

* Targeted release: 0.96
* Last updated: 2Tue Nov 22 20:40:01 UTC 2011
* Percentage of completion: 95%

== Detailed Description ==

In some cases people might be behind HTTP proxy. For now, there is no any users friendly way in Sugar to setup proxy setting.

== Benefit to Sugar ==

Set proxy parameters without using low level tools like gconftool or switching to Gnome session. This is especially required in Australia and is being developed by ActivityCentral following their input.

== Scope ==

New Control Panel component.

== UI Design ==

The feature adds a button and UI to the My-Settings window. Mockups below.

[[File:Proxy.png|center|600px]]

[[File:Cp-proxy.png|center|600px]]

For comparison, this is what the Gnome 2 proxy settings dialog looks like:

[[File:Gnome2-proxy-settings.png|600px]]

== How To Test ==

* clone [http://git.sugarlabs.org/alsroot/proxy_cp sources]
* symlink cloned directory to CP components directory, {{Code|/usr/share/sugar/extensions/cpsection}} by default
* restart sugar shell
* open Proxy CP component and setup proxy connection
* open gnome-network-setting and check if it has the same options set

== User Experience ==

The feature is entirely localized only within Control Panel.

== Dependencies ==

None.

== Contingency Plan ==

Do not use new Control Panel component.

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Gnome2-proxy-settings.png

2012-01-24T16:15:46Z

Sascha silbe: Screenshot of the proxy settings in Gnome 2

Screenshot of the proxy settings in Gnome 2

Dextrose/2/Merge Plan

2011-12-05T21:23:51Z

Sascha silbe: make it clear that this list hasn't been updated since it was created

<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}</noinclude>

This is a summary of all Sugar patches in Dextrose as of 2010-09-27. Most of these patches
have been submitted to sugar-devel@ or attached to tickets. Some have already
found their way upstream, others still have quality issues. All of them have been
integrated and tested in Dextrose to produce a better overall Sugar environment.

Refer to the [http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/rpms rpms directory] in git
for the actual patches.

See also [[Dextrose/TODO/Patches]].

== Upstreamed bug fixes ==

sugar-datastore/sl2132-reduce-_FLUSH_TIMEOUT-to-5sec.patch
sugar-datastore/sl2132-set-index_updated-flag-on-ds-shutting-down.patch
sugar-datastore/sl2095-invert-datastore-clean-logic.patch

These plug a serious journal data loss condition that was observed
repeatedly in the field.

sugar/sl2064-always-listen-for-NameOwnerChanged-DBus-message.patch

It turns out that this patch does not really fix #2064, but it
doesn't hurt either.

sugar/fix-duplication-of-OLPC-mesh-icons.patch

Three or more mesh icons were being added after every suspend/resume.

sugar/journal-xobundle-removal-wont-remove-installed-one.patch

Quite surprising behavior: removing a bundle from the journal would uninstall
activity too.

sugar/sl2062-catch-network-errors-when-trying-to-register-to-the-xs.patch
sugar/sl1940-register-session-failed-fix.patch

These two help make registration to schoolserver less painful.

sugar/add-button-frame.patch

Add frame and journal keybindings to F5/F6 (for XO1.5-HS)

sugar/indicate-inactive-state-in-mesh-device-icon.patch

Not sure how this interacts with the switch from mesh to ad-hoc, but
we applied it long ago.

sugar/restore-sugar-launch-by-bundle-id-substring-fixes-89.patch
sugar/improve-activity-updater-icon.patch
sugar/disconnect-icon-in-wifi-palette-1736.patch
sugar-toolkit/use-set_toolbar_box-in-example-code.patch
sugar-toolkit/set-default-accelerators-for-Copy-and-Paste-buttons.patch
sugar-toolkit/sl1861-remove-unneeded-debug-logs.patch

These are not really important, but safe and nice to have.

sugar/sl1842-journal-show-error-on-write-failure.patch
sugar-toolkit/sl1842-notify-red-alert.patch
sugar-toolkit/add-ErrorAlert.patch

The version that went upstream lacks the fancy red alert part. For the sake
of staying closer to upstream, we could rebase Dextrose on this version.
I don't particularly care.

sugar-artwork/sugar-artwork-gtkdep.patch
sugar-artwork/revert-to-GTK_WIDGET_IS_SENSITIVE.patch

Small build fixes.

== Upstreamed new features ==

sugar/sizelist-0000-cover-letter.patch
sugar/sizelist-0001-Journal-Retrieve-filesize-from-the-datastore.patch
sugar/sizelist-0002-Add-a-filesize-column-to-the-journal-list-model.patch
sugar/sizelist-0003-Journaltoolbox-Add-add_separator-method-for-convenie.patch
sugar/sizelist-0004-Add-a-ListViewButton-to-the-journal-search-toolbar.patch
sugar/sizelist-0006-Display-the-sorting-property-in-the-last-column.patch
sugar/sizelist-0005-Rename-the-date-column-to-sort_column.patch
sugar/sizelist-0007-Expandedentry-Try-to-use-the-filesize-property.patch
sugar/sizelist-0008-Implement-sorting-for-removable-devices.patch
sugar/sizelist-0009-Add-sort-by-creation-time-option-to-the-ListViewButt.patch
sugar/sizelist-0010-Add-ctime-property-to-the-journal-model.patch
sugar-artwork/sizelist-0001-add-icons-for-the-sorting-options-in-the-Journal.patch
sugar-datastore/sizelist-0002-Add-migration-code-from-DS-v0-for-the-filesize-prope.patch
sugar-datastore/sizelist-0006-Implement-migration-from-DS-v0-for-ctime-property.patch
sugar-datastore/sizelist-0000-cover-letter.patch
sugar-datastore/sizelist-0005-Check-ctime-on-index-rebuild.patch
sugar-datastore/sizelist-0004-Add-ctime-property-to-the-index-and-datastore.patch
sugar-datastore/sizelist-0003-Check-filesize-property-on-index-rebuild.patch
sugar-datastore/sizelist-0001-Add-filesize-property-to-the-index.patch
sugar-datastore/sizelist-0007-Increment-CURRENT_LAYOUT_VERSION-to-trigger-an-index.patch

Andres' series for sorting the journal by file size:
http://wiki.sugarlabs.org/go/Features/Journal_Sort
THIS IS NOT A GEEK TOY! If the filesize is not exposed, users are
unable to figure out how to free up space when the journal becomes
full.

sugar/sl1610-default-ad-hoc-networks.patch
sugar-artwork/ad_hoc_artwork.patch

http://wiki.sugarlabs.org/go/Features/Sugar_Adhoc_Networks

sugar/bundle-Delete-profile-data-only-when-erased.patch
sugar-toolkit/bundle-Delete-activities-profile-data-when-uninstall.patch

This is sl#2074. Merged after a very long struggle.

sugar/caacupe-Protected-activities-list.patch

A variation of this went upstream. Formadores like this feature very much.

== Unreviewed bugfixes ==

sugar/sl1673-fix-network-disconnect-and-discard-history-v2.patch

An upstream maintainer wants this split in 4 patches and submitter is waiting for consensus,
so this useful patch remains stuck in review. There's a newer patch attached
to sl#1673, someone should check it out.

sugar/fix-for-file-list-sorting-for-FAT32-formatted-flash-drives-in-journal.patch

This one seems to have fallen through the cracks. Need to resubmit.

sugar-toolkit/sl1876.patch

Review stuck in sl#1876.

sugar-toolkit/fix-two-trivial-shell-log-warnings.patch

Reviewed on sugar-devel, should be merged. Someone should ping Quozl.

sugar/avoid-popping-an-empty-list-in-the-software-updater.patch

Works, but Quozl posted a better counter-patch. Merge that one.

== Unsubmitted bugfixes ==

sugar/jasg-register-rename.patch
sugar/prevent-multiple-XS-icons-when-re-register.patch

After first registeration with the schoolserver, the "Register"
menu item disappears. If the schoolserver gets replaced or the
user changes school, there's no way to repeat the registrarion
process. This patch provides a crude solution to this problem.

sugar-artwork/journal-reindex-icon.patch
sugar/journal-0002-reindex.patch
sugar/journal-0003-reindex-translations.patch

The journal index sometimes gets corrupted or out of sync with data.
This can happen at the hardware, filesystem or datastore level and
there's not much we can do about it. This patches provide a workaround for
users. No, it's not a geek toy.

sugar/reverse-sort-order-of-activities-list.patch

Jorge or someone should post this to sugar-devel@.

== Rejected new features ==

sugar/backup-translations.patch
sugar/backup-0001-Volumes-Backup-and-Restore.patch
sugar/backup-0002-Journal-XS-backup-and-restore.patch
sugar/backup-0005-save-lease.patch
sugar/journal-0001-Processdialog-prerequisite-check-support.patch
sugar-artwork/gmartin-School-Server-Icon.patch

This series implements easy backup and restore of the journal to
removable media and schoolservers. It has been submitted for review,
but upstream found it unacceptable for various reasons. Uruguay and
Paraguay like this feature the way it is, so these patches remain
off-tree.

sugar/use-the-spanish-verb-quitar-for-unmounting-devices.patch

Better-than-nothing patch, but the real fix would require a gettext
kludge in the code (see http://bugs.python.org/issue2504 )

sugar/cpu-and-memory-resource-indicator.patch
sugar-artwork/cpu-and-memory-indicator-icons.patch

See sl#2141. This is seen as another geek's toy, but geeks could simply
cat /proc/meminfo... users really need a simple way to see why the XO
isn't performing well with too many open activities.

sugar/dynamically-set-number-of-control-panel-columns.patch

The approach to compute the column width is wrong, but it produces better
results than the current fixed number of columns. So, for now, I'm keeping
this better-than-nothing fix.

== Unreviewed new features ==

sugar/restart-option.patch

We're doing good progress in sl#1206.

== Unsubmitted new features ==

sugar/accessibility_0001_cp_accessibility_keyboard.patch
sugar/accessibility_0002_magnifier_extension.patch
sugar/accessibility_0003_cp_accessibility_contrast.patch
sugar/accessibility_0004_cp_accessibility_mouse.patch
sugar/accessibility_0005_cp_accessibility_capital_letters.patch
sugar/accessibility_0006_virtualkeyboard.patch
sugar/accessibility_0007_cp_translations.patch
sugar/accessibility_0008_cp_show-virtualkeyboard-for-accessibility.patch
sugar/accessibility_0009_cp_show-virtualkeyboard-for-accessibility-traslate.patch
sugar-artwork/accessibility_0001_contrast.patch
sugar-artwork/accessibility_0002_virtualkeyboard_icon.patch
sugar-toolkit/accessibility_0001_style-contrast.patch

Accessibility features developed in Uruguay. These have not been submitted
for review yet. http://wiki.sugarlabs.org/go/File:Dextrose_teclado_virtual.png

sugar/microformat-updater.patch

This is a backend for the new Sugar activity updater, implementing the
olpc microformat protocol which is used by several deployments.

sugar/gsm-errors-palette.patch

Improves diagnostic messages for GSM dongles.

sugar/sl2006-touchpad-device-on-frame.patch
sugar-artwork/sl2006-icons-for-touchpad-panel.patch

Walter's XO-1 touchpad control panel. It would be nice to add a global
shortcut such as alt-shift-T.

== Unreviewed cleanups ==

sugar/simplify-the-definition-of-UpdateModel._bundles_to_check..patch

Should be merged.

sugar-toolkit/remove-incomplete-MANIFEST-support.patch

The incomplete design and implementation of MANIFEST files has been laying
around for 3 years. We can choose to clean it up now, or let it bitrot for
another 3 years. Posted some time ago to sugar-devel, nobody reviewed it.

== Experimental Patches ==

sugar-toolkit/change-keep-string-to-keep-a-copy.patch
sugar-toolkit/keep_a_copy_translation_missing.patch

Several alternatives have been suggested on the list, but nobody implemented
them, so this one still stands.

sugar-toolkit/kill-the-delayed-menus-for-good.patch

This change has been at the center of a huge design / UX / testing flame war a
while ago. I've merged it to observe user reactions, so
hopefully we can have a polite discussion based on some real data.

sugar-toolkit/sugar-toolkit-dont-configure-fonts.patch
sugar/sugar-enable-settings-manager.patch

We had to temporarily exclude these because sugar-settings-manager does
not play well with xulrunner in F11.

sugar/add-font-dpi-schema.patch

This is a companion patch of a fix sugar-settings-manager which has
already landed in git. It's needed by xulrunner (Browse).

sugar/set-default-scaling-to-100.patch

This is only required on the XO. We should really autodetect this.

== Disabled and obsolete patches ==

sugar-toolkit/sl1948-Race-condition-with-name-widget-in-the-activ.patch

Erikos came up with a better fix in sl#1948. Should test it.

sugar/sl1814-consolidate-activity-launch-entry-point.patch

This also fixes sl#1719, which I've definitely seen happen in Dextrose.
I don't know why this patch is disabled in our spec file, it should probably
be retested.

sugar/click-on-journal-icons-with-a-exclusive-time-frame.patch

Requested by the Waveplace folks. This should be dropped once we get the
proper fix for sl#1719 (see above).

sugar/backup-0003-Journal-documents-volume-button.patch

We no longer need this feature since we decided to disable Gnome, other
deployments may find it useful. (but journal crashes when you drop files on
the icon)

sugar/pe558-modify-volumnestoolbar-to-mount-a-directory.patch

This makes it possible to easily exchange documents with Gnome.
Since we don't ship Gnome any more, we dropped this feature.h

sugar/pe558-backup-restore-front-end-for-control-panel.patch
sugar/pe558-add-option-to-mount-any-user-directory-to-journal.patch
sugar/pe558-journal-management-control-panel-feature.patch

This patch series has been replaced by Tincho's Journal-based backup/restore
functionality. Keeping them around in case someone else prefers the control
panel UI.

sugar/fix-name-clash-set_state.patch

This isn't strictly needed on 0.88, but it's confusing

Platform Team/Server Kit/sugar-server

2011-12-04T15:46:54Z

Sascha silbe: /* Configuration */ fix link to templates

== Summary ==

The core [[Sugar Server Kit]] component.

The singular program requires only Python, and obvious dependencies like coreutils, to allow all its services to function properly. It provides basic sugar related services, and uses one CLI tool to manage all its functionality.

== Functionality ==

=== Registry ===

During the sugar-server work, all its components have access to a registry, an analog of a database to keep information about registered users or activated machines. The registry is file based, i.e., every item is kept in one file (in JSON notation) in the {{Code|<root-option>/home/registry}} directory.

There are two subdirectories, i.e., "tables":

* {{Code|users}}, for registered users, and
* {{Code|machines}}, for machines that requested activation leases on bootstrap.

Registry items might contain the following keys:

* {{Code|uid}}, user's identity got after registration on a server;
* {{Code|machine_sn}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;
* {{Code|machine_uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;
* {{Code|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code|~/.ssh/authorized_keys}} file; note that OLPC XS operates with stripped version of public keys.

== Services ==

The list of services that sugar-server provides. Each service has a described interface to understand how it interact with clients. The counterpart for these interfaces is the [[Sugar_Server_Kit/sugar-client|sugar-client]] with a [[Sugar_Server_Kit/Client_API|Client API]] it provides for clients, e.g., Sugar Shell.

If a particular service supports a [[wikipedia:Representational_state_transfer |RESTfull interface]], the HTTP server is started on {{Code|host}} with the {{Code|httpd-port}} port. The content of requests and replies is transferred using dictionaries in JSON notation.

The resulting dictionary on success, will contain predefined keys:

* {{Code|success: OK}};

The resulting dictionary on failure, will contain:

* {{Code|success: ERR}};
* {{Code|error}}, error message.

=== registry ===

Provides Sugar users registration on a school server. After being registered, Sugar on user's side will set up interaction with a school server. See [[Sugar_Server_Kit/sugar-client|sugar-client]] project for details from the client point of view.

Interface:

POST '''/client/register'''

Process registration on a server.

The input dictionary, contains (see [[#User_identity_models|identity models]] section for additional details):

* {{Code|nickname}}, user's Sugar nick name;
* {{Code|machine_sn}}, machine's serial number, makes special sense only for XO anti-thief support and [[#Hardware_based_model|hardware based]] identity model,
* {{Code|machine_uuid}}, machine's UUID value, makes special sense only for XO anti-thief support,
* {{Code|pubkey}}, SSH public key passed as-is.

The resulting dictionary, contains:

* {{Code|uid}}, unique identity that needs to be used for further interaction with the server.

GET '''/client/status'''?uid=''UID''

Get information about client's status on a server.

The resulting dictionary, contains:

* {{Code|registered}}, if {{Code|False}}, client needs to process registration;
* {{Code|jabber-url}}, if {{Code|registered}} is {{Code|True}}, Jabber server url;
* {{Code|backup-url}}, if {{Code|registered}} is {{Code|True}}, Rsync url to backup Journal to, needs to be used as-is.
* {{Code|pending-restore}}, is there a pending restore, i.e., if {{Code|True}}, during the registration on a server, there was an existing backup; any further, post registration, backup or restore will clean up the {{Code|pending-restore}} flag.

Requested uid might be NOT registered in cases like:

* registration was removed from the server,
* request was sent to a server that was not the same as where the uid was created,
* someone [[#Vulnerabilities|registered]] the same serial number.

Requirements:

* Current Sugar Shell code calls only XML-RPC method using the hard coded {{Code|http://schoolserver:8080/}} url. This restriction can be avoided using [[Sugar_Server_Kit/sugar-client|sugar-client]].

Backwards compatibility:

''dict'' '''register'''(''str'' machine_sn, ''str'' nickname, ''str'' machine_uuid, ''str'' pubkey)

To support OLPC's XS clients, RPC function to serve registration requests. The XML-RPC service will be listening to the {{Code|8080}} port on the {{Code|--host}} host.

=== backup ===

Process backup and restore for students' Journals. The service accepts requests that clients send before starting the backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be obtained from a {{Code|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.

Users' backups are stored in the {{Code|<root-option>/home/backups/<UID's-last-two-chars>/<UID>}} directories.

Interface:

GET '''/client/backup'''?uid=''UID''

Check if client can start transferring Journal files.

The resulting dictionary, contains:

* {{Code|accepted}}, if {{Code|True}}, clients can start backup process.

Requirements:

* The {{Code|root}} configuration option should point to the home directory of the system user that starts sugar-server process. This is needed because clients will SSH to this user to perform Rsync backups.

Backwards compatibility:

Note, this backup functionality is not compatible with client tools that work with OLPC XS. The problem is that these tools construct a backup url on the client side (using only the server host name from a backup url given after registration on the server) so relying that every client has its own system user on the server side. That doesn't work with this new backup functionality, where there is only one system user on the server side, and authorisation happens at the SSH level (using the {{Code|command}} option in {{Code|~/.ssh/authorized_keys}} file).

=== activation ===

This service is intended to process anti-thief requests that XO laptops send to the server during the boot process. It is looking for pre-created leases using {{Code|<root-option>/share/leases/<SN's-last-two-chars>/<SN>}} paths. If there are no existing leases and the {{Code|delegation}} option is {{Code|True}}, it will ask the [[#keyring|keyring]] service to generate a new one using delegated leases.

Interface:

GET '''/client/lease'''?machine_sn=''MACHINE_SN''

Get OLPC anti-thief lease for specified XO's serial number.

The resulting dictionary, contains:

* {{Code|lease}}, lease content

Requirements:

* Current XO's bootstrap code uses TCP interface, having the following numbers hard coded:
** {{Code|host}} needs to be {{Code|172.18.0.1}},
** {{Code|activation-port}} needs to be {{Code|191}},
** XOs use {{Code|172.18.96.1}} as a gateway while connecting to {{Code|172.18.0.1}}.

Backwards compatibility:

Service is also listening to {{Code|--activation-port}} port on the {{Code|--host}} host to process TCP requests used by the XO's bootstrapping code. If sent data starts with a serial number, the service will reply with:

* {{Code|STOLEN}} text, if serial number is stated as stolen;
* lease content found for serial number;
* {{Code|UNKNOWN}} for errors.

=== keyring ===

Keyring service is needed to work with the activation one. It signs delegated leases for activation requests if pre-existing leases weren't found.

Interface:

There is no public interface, the service is used internally by sugar-server.

== User identity models ==

How sugar-server will identify users upon registration.

=== Hardware based model ===

The use case assumes:

* the hardware is intended to run only Sugar,
* it serves only one user,
* there is an existing practice within XO deployments with workflows that need to be preserved.

To process registration, users need to provide:

* valid SSH public key,
* valid machine serial number, i.e., a serial number that the school server is aware of, e.g., there is an activation lease.

After re-flashing an XO (with loosing private key), it is possible to re-register the user by uploading a new public key. See [[#Vulnerabilities|below]] for related vulnerability issues.

The following TODO needs to be implemented:

* Properly handle backups after hardware switching for the particular user.
* More reliable identity scheme that will avoid [[#Vulnerabilities|compromising users]].

=== SSH key based model ===

This is a low level model, since the major feature is uploading an SSH public key to the server. This model might be useful in cases like:

* the hardware is intended to run not only Sugar (thus, might not be affected by "re-flashing" issue),
* it might serve multiple users.

To process registration, users need to provide a

* valid SSH public key.

To always have access to already-uploaded-to-the-server data, people need to take care about securing their SSH key. This key can be found in the {{Code|~/.sugar/''<profile>''/owner.key}} file.

=== Vulnerabilities ===

How current implementations are bad.

'''Compromised users'''

Current implementation of [[#Hardware based model|hardware based]] identity model has a security issue that might be described with the following use case:

* an XO registered on a school server;
* processed several Journal backups there;
* got re-flashed and failed in keeping client side identities, like the Sugar profile private key;
* the XO wants to re-register to restore Journal content from a previous backup. But from the school server point of view, this request is a regular registration request from a new XO (which provides the same serial number that the existing registration uses).

Sugar-server will process these registrations assuming that the request was sent from an XO that has exactly the same serial number that was provided with the request.

'''Compromised servers'''

Both identity models might process registration on fake servers. The only thing clients need to start a registration, is a properly resolved {{Code|schoolserver}} host name.

Possible solutions:

* [[Sugar_Server_Kit/1.2/Todo#Avoid_compromised_school_servers|Switch to HTTPS]].

== Configuration ==

By default, configuration occurs based on several sources (sorted by order of application):

* {{Code|/etc/sugar-server.conf}} system-wide configuration file,
* {{Code|~/.config/sugar-server/config}} user-wide configuration file,
* {{Code|sugar-server}}'s command-line arguments.

Configuration files contain option names equal to command-line arguments. To get the current configuration, call:

sugar-server config

See [http://git.sugarlabs.org/server/templates/trees/master/mace/sugar-server sugar-server-templates] sources for an example.

== Getting involved ==

* [http://bugs.sugarlabs.org/newticket?component=sugar-server-kit Report] on bugs.
* Read the [http://git.sugarlabs.org/server/server/blobs/master/HACKING HACKING] file to know how to contribute with code.

== Resources ==

* [http://git.sugarlabs.org/server/server Sources].

Platform Team/Server Kit/sugar-server

2011-12-04T14:28:59Z

Sascha silbe: /* registry */ fix typo

== Summary ==

The core [[Sugar Server Kit]] component.

The singular program requires only Python, and obvious dependencies like coreutils, to allow all its services to function properly. It provides basic sugar related services, and uses one CLI tool to manage all its functionality.

== Functionality ==

=== Registry ===

During the sugar-server work, all its components have access to a registry, an analog of a database to keep information about registered users or activated machines. The registry is file based, i.e., every item is kept in one file (in JSON notation) in the {{Code|<root-option>/home/registry}} directory.

There are two subdirectories, i.e., "tables":

* {{Code|users}}, for registered users, and
* {{Code|machines}}, for machines that requested activation leases on bootstrap.

Registry items might contain the following keys:

* {{Code|uid}}, user's identity got after registration on a server;
* {{Code|machine_sn}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;
* {{Code|machine_uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;
* {{Code|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code|~/.ssh/authorized_keys}} file; note that OLPC XS operates with stripped version of public keys.

== Services ==

The list of services that sugar-server provides. Each service has a described interface to understand how it interact with clients. The counterpart for these interfaces is the [[Sugar_Server_Kit/sugar-client|sugar-client]] with a [[Sugar_Server_Kit/Client_API|Client API]] it provides for clients, e.g., Sugar Shell.

If a particular service supports a [[wikipedia:Representational_state_transfer |RESTfull interface]], the HTTP server is started on {{Code|host}} with the {{Code|httpd-port}} port. The content of requests and replies is transferred using dictionaries in JSON notation.

The resulting dictionary on success, will contain predefined keys:

* {{Code|success: OK}};

The resulting dictionary on failure, will contain:

* {{Code|success: ERR}};
* {{Code|error}}, error message.

=== registry ===

Provides Sugar users registration on a school server. After being registered, Sugar on user's side will set up interaction with a school server. See [[Sugar_Server_Kit/sugar-client|sugar-client]] project for details from the client point of view.

Interface:

POST '''/client/register'''

Process registration on a server.

The input dictionary, contains (see [[#User_identity_models|identity models]] section for additional details):

* {{Code|nickname}}, user's Sugar nick name;
* {{Code|machine_sn}}, machine's serial number, makes special sense only for XO anti-thief support and [[#Hardware_based_model|hardware based]] identity model,
* {{Code|machine_uuid}}, machine's UUID value, makes special sense only for XO anti-thief support,
* {{Code|pubkey}}, SSH public key passed as-is.

The resulting dictionary, contains:

* {{Code|uid}}, unique identity that needs to be used for further interaction with the server.

GET '''/client/status'''?uid=''UID''

Get information about client's status on a server.

The resulting dictionary, contains:

* {{Code|registered}}, if {{Code|False}}, client needs to process registration;
* {{Code|jabber-url}}, if {{Code|registered}} is {{Code|True}}, Jabber server url;
* {{Code|backup-url}}, if {{Code|registered}} is {{Code|True}}, Rsync url to backup Journal to, needs to be used as-is.
* {{Code|pending-restore}}, is there a pending restore, i.e., if {{Code|True}}, during the registration on a server, there was an existing backup; any further, post registration, backup or restore will clean up the {{Code|pending-restore}} flag.

Requested uid might be NOT registered in cases like:

* registration was removed from the server,
* request was sent to a server that was not the same as where the uid was created,
* someone [[#Vulnerabilities|registered]] the same serial number.

Requirements:

* Current Sugar Shell code calls only XML-RPC method using the hard coded {{Code|http://schoolserver:8080/}} url. This restriction can be avoided using [[Sugar_Server_Kit/sugar-client|sugar-client]].

Backwards compatibility:

''dict'' '''register'''(''str'' machine_sn, ''str'' nickname, ''str'' machine_uuid, ''str'' pubkey)

To support OLPC's XS clients, RPC function to serve registration requests. The XML-RPC service will be listening to the {{Code|8080}} port on the {{Code|--host}} host.

=== backup ===

Process backup and restore for students' Journals. The service accepts requests that clients send before starting the backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be obtained from a {{Code|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.

Users' backups are stored in the {{Code|<root-option>/home/backups/<UID's-last-two-chars>/<UID>}} directories.

Interface:

GET '''/client/backup'''?uid=''UID''

Check if client can start transferring Journal files.

The resulting dictionary, contains:

* {{Code|accepted}}, if {{Code|True}}, clients can start backup process.

Requirements:

* The {{Code|root}} configuration option should point to the home directory of the system user that starts sugar-server process. This is needed because clients will SSH to this user to perform Rsync backups.

Backwards compatibility:

Note, this backup functionality is not compatible with client tools that work with OLPC XS. The problem is that these tools construct a backup url on the client side (using only the server host name from a backup url given after registration on the server) so relying that every client has its own system user on the server side. That doesn't work with this new backup functionality, where there is only one system user on the server side, and authorisation happens at the SSH level (using the {{Code|command}} option in {{Code|~/.ssh/authorized_keys}} file).

=== activation ===

This service is intended to process anti-thief requests that XO laptops send to the server during the boot process. It is looking for pre-created leases using {{Code|<root-option>/share/leases/<SN's-last-two-chars>/<SN>}} paths. If there are no existing leases and the {{Code|delegation}} option is {{Code|True}}, it will ask the [[#keyring|keyring]] service to generate a new one using delegated leases.

Interface:

GET '''/client/lease'''?machine_sn=''MACHINE_SN''

Get OLPC anti-thief lease for specified XO's serial number.

The resulting dictionary, contains:

* {{Code|lease}}, lease content

Requirements:

* Current XO's bootstrap code uses TCP interface, having the following numbers hard coded:
** {{Code|host}} needs to be {{Code|172.18.0.1}},
** {{Code|activation-port}} needs to be {{Code|191}},
** XOs use {{Code|172.18.96.1}} as a gateway while connecting to {{Code|172.18.0.1}}.

Backwards compatibility:

Service is also listening to {{Code|--activation-port}} port on the {{Code|--host}} host to process TCP requests used by the XO's bootstrapping code. If sent data starts with a serial number, the service will reply with:

* {{Code|STOLEN}} text, if serial number is stated as stolen;
* lease content found for serial number;
* {{Code|UNKNOWN}} for errors.

=== keyring ===

Keyring service is needed to work with the activation one. It signs delegated leases for activation requests if pre-existing leases weren't found.

Interface:

There is no public interface, the service is used internally by sugar-server.

== User identity models ==

How sugar-server will identify users upon registration.

=== Hardware based model ===

The use case assumes:

* the hardware is intended to run only Sugar,
* it serves only one user,
* there is an existing practice within XO deployments with workflows that need to be preserved.

To process registration, users need to provide:

* valid SSH public key,
* valid machine serial number, i.e., a serial number that the school server is aware of, e.g., there is an activation lease.

After re-flashing an XO (with loosing private key), it is possible to re-register the user by uploading a new public key. See [[#Vulnerabilities|below]] for related vulnerability issues.

The following TODO needs to be implemented:

* Properly handle backups after hardware switching for the particular user.
* More reliable identity scheme that will avoid [[#Vulnerabilities|compromising users]].

=== SSH key based model ===

This is a low level model, since the major feature is uploading an SSH public key to the server. This model might be useful in cases like:

* the hardware is intended to run not only Sugar (thus, might not be affected by "re-flashing" issue),
* it might serve multiple users.

To process registration, users need to provide a

* valid SSH public key.

To always have access to already-uploaded-to-the-server data, people need to take care about securing their SSH key. This key can be found in the {{Code|~/.sugar/''<profile>''/owner.key}} file.

=== Vulnerabilities ===

How current implementations are bad.

'''Compromised users'''

Current implementation of [[#Hardware based model|hardware based]] identity model has a security issue that might be described with the following use case:

* an XO registered on a school server;
* processed several Journal backups there;
* got re-flashed and failed in keeping client side identities, like the Sugar profile private key;
* the XO wants to re-register to restore Journal content from a previous backup. But from the school server point of view, this request is a regular registration request from a new XO (which provides the same serial number that the existing registration uses).

Sugar-server will process these registrations assuming that the request was sent from an XO that has exactly the same serial number that was provided with the request.

'''Compromised servers'''

Both identity models might process registration on fake servers. The only thing clients need to start a registration, is a properly resolved {{Code|schoolserver}} host name.

Possible solutions:

* [[Sugar_Server_Kit/1.2/Todo#Avoid_compromised_school_servers|Switch to HTTPS]].

== Configuration ==

By default, configuration occurs based on several sources (sorted by order of application):

* {{Code|/etc/sugar-server.conf}} system-wide configuration file,
* {{Code|~/.config/sugar-server/config}} user-wide configuration file,
* {{Code|sugar-server}}'s command-line arguments.

Configuration files contain option names equal to command-line arguments. To get the current configuration, call:

sugar-server config

See [http://git.sugarlabs.org/server/templates/trees/master/etc/sugar-server sugar-server-templates] sources for an example.

== Getting involved ==

* [http://bugs.sugarlabs.org/newticket?component=sugar-server-kit Report] on bugs.
* Read the [http://git.sugarlabs.org/server/server/blobs/master/HACKING HACKING] file to know how to contribute with code.

== Resources ==

* [http://git.sugarlabs.org/server/server Sources].

Platform Team/Server Kit/sugar-server

2011-12-04T14:25:51Z

Sascha silbe: /* Registry */ fix typo

== Summary ==

The core [[Sugar Server Kit]] component.

The singular program requires only Python, and obvious dependencies like coreutils, to allow all its services to function properly. It provides basic sugar related services, and uses one CLI tool to manage all its functionality.

== Functionality ==

=== Registry ===

During the sugar-server work, all its components have access to a registry, an analog of a database to keep information about registered users or activated machines. The registry is file based, i.e., every item is kept in one file (in JSON notation) in the {{Code|<root-option>/home/registry}} directory.

There are two subdirectories, i.e., "tables":

* {{Code|users}}, for registered users, and
* {{Code|machines}}, for machines that requested activation leases on bootstrap.

Registry items might contain the following keys:

* {{Code|uid}}, user's identity got after registration on a server;
* {{Code|machine_sn}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;
* {{Code|machine_uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;
* {{Code|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code|~/.ssh/authorized_keys}} file; note that OLPC XS operates with stripped version of public keys.

== Services ==

The list of services that sugar-server provides. Each service has a described interface to understand how it interact with clients. The counterpart for these interfaces is the [[Sugar_Server_Kit/sugar-client|sugar-client]] with a [[Sugar_Server_Kit/Client_API|Client API]] it provides for clients, e.g., Sugar Shell.

If a particular service supports a [[wikipedia:Representational_state_transfer |RESTfull interface]], the HTTP server is started on {{Code|host}} with the {{Code|httpd-port}} port. The content of requests and replies is transferred using dictionaries in JSON notation.

The resulting dictionary on success, will contain predefined keys:

* {{Code|success: OK}};

The resulting dictionary on failure, will contain:

* {{Code|success: ERR}};
* {{Code|error}}, error message.

=== registry ===

Provides Sugar users registration on a school server. After being registered, Sugar on user's side will set up interaction with a school server. See [[Sugar_Server_Kit/sugar-client|sugar-client]] project for details from the client point of view.

Interface:

POST '''/client/register'''

Process registration on a server.

The input dictionary, contains (see [[#User_identity_models|identity models]] section for additional details):

* {{Code|nickname}}, user's Sugar nick name;
* {{Code|machine_sn}}, machine's serial number, makes special sense only for XO anti-thief support and [[#Hardware_based_model|hardware based]] identity model,
* {{Code|machine_uuid}}, machine's UUID value, makes special sense only for XO anti-thief support,
* {{Code|pubkey}}, SSH public key passed as-is.

The resulting dictionary, contains:

* {{Code|uid}}, unique identity that needs to be used for further interaction with the server.

GET '''/client/status'''?uid=''UID''

Get information about client's status on a server.

The resulting dictionary, contains:

* {{Code|registered}}, if {{Code|False}}, client needs to process registration;
* {{Code|jabber-url}}, if {{Code|registered}} is {{Code|True}}, Jabber server url;
* {{Code|backup-url}}, if {{Code|registered}} is {{Code|True}}, Rsync url to backup Journal to, needs to be used as-is.
* {{Code|pending-restore}}, is there a pending restore, i.e., if {{Code|True}}, during the registration on a server, there was an existing backup; any further, post registration, backup or restore will clean up the {{Code|pending-restore}} flag.

Requested uid might be NOT registered in cases like:

* registration was removed from the server,
* request was sent to a server that was not the same as where the uid was created,
* someone [[#Vulnerabilities|registered]] the same serial number.

Requirements:

* Current Sugar Shell code calls only XML-RPC method using the hard coded {{Code|http://schoolserver:8080/}} url. This restriction can be avoided using [[Sugar_Server_Kit/sugar-client|sugar-client]].

Backwards compatibility:

''dict'' '''register'''(''str'' machine_sn, ''str'' nickname, ''str'' machine_uuid, ''str'' pubkey)

To support OLPC's XS clients, RPC function to serve registration requests. The XML-RPM service will be listening to the {{Code|8080}} port on the {{Code|--host}} host.

=== backup ===

Process backup and restore for students' Journals. The service accepts requests that clients send before starting the backup process. If server accepts requests, clients start Rsync'ing Journal data via SSH. The Rsync url needs to be obtained from a {{Code|/client/status}} request and be used without any modification on the client side, i.e., the process is fully server driven.

Users' backups are stored in the {{Code|<root-option>/home/backups/<UID's-last-two-chars>/<UID>}} directories.

Interface:

GET '''/client/backup'''?uid=''UID''

Check if client can start transferring Journal files.

The resulting dictionary, contains:

* {{Code|accepted}}, if {{Code|True}}, clients can start backup process.

Requirements:

* The {{Code|root}} configuration option should point to the home directory of the system user that starts sugar-server process. This is needed because clients will SSH to this user to perform Rsync backups.

Backwards compatibility:

Note, this backup functionality is not compatible with client tools that work with OLPC XS. The problem is that these tools construct a backup url on the client side (using only the server host name from a backup url given after registration on the server) so relying that every client has its own system user on the server side. That doesn't work with this new backup functionality, where there is only one system user on the server side, and authorisation happens at the SSH level (using the {{Code|command}} option in {{Code|~/.ssh/authorized_keys}} file).

=== activation ===

This service is intended to process anti-thief requests that XO laptops send to the server during the boot process. It is looking for pre-created leases using {{Code|<root-option>/share/leases/<SN's-last-two-chars>/<SN>}} paths. If there are no existing leases and the {{Code|delegation}} option is {{Code|True}}, it will ask the [[#keyring|keyring]] service to generate a new one using delegated leases.

Interface:

GET '''/client/lease'''?machine_sn=''MACHINE_SN''

Get OLPC anti-thief lease for specified XO's serial number.

The resulting dictionary, contains:

* {{Code|lease}}, lease content

Requirements:

* Current XO's bootstrap code uses TCP interface, having the following numbers hard coded:
** {{Code|host}} needs to be {{Code|172.18.0.1}},
** {{Code|activation-port}} needs to be {{Code|191}},
** XOs use {{Code|172.18.96.1}} as a gateway while connecting to {{Code|172.18.0.1}}.

Backwards compatibility:

Service is also listening to {{Code|--activation-port}} port on the {{Code|--host}} host to process TCP requests used by the XO's bootstrapping code. If sent data starts with a serial number, the service will reply with:

* {{Code|STOLEN}} text, if serial number is stated as stolen;
* lease content found for serial number;
* {{Code|UNKNOWN}} for errors.

=== keyring ===

Keyring service is needed to work with the activation one. It signs delegated leases for activation requests if pre-existing leases weren't found.

Interface:

There is no public interface, the service is used internally by sugar-server.

== User identity models ==

How sugar-server will identify users upon registration.

=== Hardware based model ===

The use case assumes:

* the hardware is intended to run only Sugar,
* it serves only one user,
* there is an existing practice within XO deployments with workflows that need to be preserved.

To process registration, users need to provide:

* valid SSH public key,
* valid machine serial number, i.e., a serial number that the school server is aware of, e.g., there is an activation lease.

After re-flashing an XO (with loosing private key), it is possible to re-register the user by uploading a new public key. See [[#Vulnerabilities|below]] for related vulnerability issues.

The following TODO needs to be implemented:

* Properly handle backups after hardware switching for the particular user.
* More reliable identity scheme that will avoid [[#Vulnerabilities|compromising users]].

=== SSH key based model ===

This is a low level model, since the major feature is uploading an SSH public key to the server. This model might be useful in cases like:

* the hardware is intended to run not only Sugar (thus, might not be affected by "re-flashing" issue),
* it might serve multiple users.

To process registration, users need to provide a

* valid SSH public key.

To always have access to already-uploaded-to-the-server data, people need to take care about securing their SSH key. This key can be found in the {{Code|~/.sugar/''<profile>''/owner.key}} file.

=== Vulnerabilities ===

How current implementations are bad.

'''Compromised users'''

Current implementation of [[#Hardware based model|hardware based]] identity model has a security issue that might be described with the following use case:

* an XO registered on a school server;
* processed several Journal backups there;
* got re-flashed and failed in keeping client side identities, like the Sugar profile private key;
* the XO wants to re-register to restore Journal content from a previous backup. But from the school server point of view, this request is a regular registration request from a new XO (which provides the same serial number that the existing registration uses).

Sugar-server will process these registrations assuming that the request was sent from an XO that has exactly the same serial number that was provided with the request.

'''Compromised servers'''

Both identity models might process registration on fake servers. The only thing clients need to start a registration, is a properly resolved {{Code|schoolserver}} host name.

Possible solutions:

* [[Sugar_Server_Kit/1.2/Todo#Avoid_compromised_school_servers|Switch to HTTPS]].

== Configuration ==

By default, configuration occurs based on several sources (sorted by order of application):

* {{Code|/etc/sugar-server.conf}} system-wide configuration file,
* {{Code|~/.config/sugar-server/config}} user-wide configuration file,
* {{Code|sugar-server}}'s command-line arguments.

Configuration files contain option names equal to command-line arguments. To get the current configuration, call:

sugar-server config

See [http://git.sugarlabs.org/server/templates/trees/master/etc/sugar-server sugar-server-templates] sources for an example.

== Getting involved ==

* [http://bugs.sugarlabs.org/newticket?component=sugar-server-kit Report] on bugs.
* Read the [http://git.sugarlabs.org/server/server/blobs/master/HACKING HACKING] file to know how to contribute with code.

== Resources ==

* [http://git.sugarlabs.org/server/server Sources].

0.96/Feature List

2011-11-22T17:05:05Z

Sascha silbe: /* Proposed Features for 0.96 */ remove Features/ fix up Multi-selection entry

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

== Proposed Features for 0.96 ==
These features have been proposed for the Sugar 0.96 Release cycle and await approval.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Owner !! Name !! Summary !! Take
|-
| Gonzalo Odiard || [[Features/GlobalTextToSpeech | Global Text to Speech]] || When the user press Alt+Shift+S the currently selected text should be said by the computer. || yes
|-
| Walter Bender || [[Features/Write_to_journal_anytime|Write to Journal anytime]] || Replacement for the Naming Alert that lets you write to the Journal at any time while working on an activity. || yes
|-
| Gonzalo Odiard || [[Features/Journal_data_tagged_private_or_public|Journal data tagged private or public]] || Provide a way to identify Journal entries as private for the owner or public. ||
|-
| Walter Bender || [[Features/Multiple_home_views|Multiple Home Views]] || Option to have different collections of activities on the Home View for formal (classroom) and informal (home) use. ||
|-
| Walter Bender || [[Features/Thumbs_View_in_Journal|Thumbs View in Journal]] || Thumbs view plugin for Journal. ||
|-
| Walter Bender || [[Features/Background_image_on_home_view|Background image on Home View]] || Add the ability to set a background image to the Home View. ||
|-
| Walter Bender || [[Features/Journal_Volume_Toolbar_enhancement|Journal Volume Toolbar enhancement]] || The VolumesToolbar class in volumetoolbar.py should be extended so that Sugar activities can "mount" directories containing example projects, e.g., the samples subdirectory in Turtle Art. Thus samples will be available through the Sugar Chooser rather than having to use the GNOME file chooser. ||
|-
| Walter Bender || [[Features/Activity_specific_metadata_in_Journal|Activity specific metadata in Journal]] || The idea is to record metadata related to the use of an activity and display it in the detail view of the Journal. || yes
|-
| Sebastian Silva || [[Features/Statistics_gathering|Statistics gathering]] || To gather usage statistics in separate logs from error logs (up to a storage limit). The software improvement process requires usage statistics data to learn from our users. ||
|-
| Anish Mangal, Aleksey Lim || [[Features/Proxy_configuration|Proxy configuration]] || To add a section in the Control Panel that allows the user to configure network proxy settings. || yes ||
|-
| Gonzalo Odiard || [[Features/Multi_selection|Multi-selection]] || Enable operation on multiple selected entries in the Journal. ||
|}

== Accepted Features for 0.96 ==
These features have been accepted by the Release Manager for the Sugar 0.96 Release.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Owner !! Complete !!Name !!Summary !!Updated
|-
| Gonzalo Odiard || 0% || [[Features/EvinceIntrospectionBindings | Evince Introspection Bindings]] || The pygtk bindings used until F14 to use the evince backend in Read activity, are no longer present in F16. We need use the new gi based bindings. || 1-Nov-2011
|-
| Manuel Quiñones || 0% || [[Features/WebKit | Port Browse to use WebKit through introspection]] || Browse and related components are switching to WebKit as its back-end technology provider. || 1-Nov-2011
|-
| Simon Schampijer || 0% || [[Features/GTK3 | GTK3]] || Sugar needs to rebase itself on new generations of its key underlying technologies: GTK+ 3 and PyGObject Introspection. || 1-Nov-2011
|-
|}

== Feature Process ==

* The process for adding, proposing, and accepting new features into Sugar is on the [[Features/Policy]] page.
* The deadline for proposing and completing new features is the ''Feature Freeze'' on the [[0.96/Roadmap]]
* Feature pages in process but not targeted for a particular release can be found in [[:Category:Feature Page Incomplete]]

0.96/Feature List

2011-11-22T13:51:51Z

Sascha silbe: /* Proposed Features for 0.96 */ remove Features/ from feature page link descriptions to make table more readable

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

== Proposed Features for 0.96 ==
These features have been proposed for the Sugar 0.96 Release cycle and await approval.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Owner !! Name !! Summary
|-
| Gonzalo Odiard || [[Features/GlobalTextToSpeech | Global Text to Speech]] || When the user press Alt+Shift+S the currently selected text should be said by the computer.
|-
| Walter Bender || [[Features/Write_to_journal_anytime|Write to Journal anytime]] || Replacement for the Naming Alert that lets you write to the Journal at any time while working on an activity.
|-
| Gonzalo Odiard || [[Features/Journal_data_tagged_private_or_public|Journal data tagged private or public]] || Provide a way to identify Journal entries as private for the owner or public.
|-
| Walter Bender || [[Features/Multiple_home_views|Multiple Home Views]] || Option to have different collections of activities on the Home View for formal (classroom) and informal (home) use.
|-
| Walter Bender || [[Features/Thumbs_View_in_Journal|Thumbs View in Journal]] || Thumbs view plugin for Journal.
|-
| Walter Bender || [[Features/Background_image_on_home_view|Background image on Home View]] || Add the ability to set a background image to the Home View.
|-
| Walter Bender || [[Features/Journal_Volume_Toolbar_enhancement|Journal Volume Toolbar enhancement]] || The VolumesToolbar class in volumetoolbar.py should be extended so that Sugar activities can "mount" directories containing example projects, e.g., the samples subdirectory in Turtle Art. Thus samples will be available through the Sugar Chooser rather than having to use the GNOME file chooser.
|-
| Walter Bender || [[Features/Activity_specific_metadata_in_Journal|Activity specific metadata in Journal]] || The idea is to record metadata related to the use of an activity and display it in the detail view of the Journal.
|-
| Sebastian Silva || [[Features/Statistics_gathering|Statistics gathering]] || To gather usage statistics in separate logs from error logs (up to a storage limit). The software improvement process requires usage statistics data to learn from our users.
|-
| Anish Mangal, Aleksey Lim || [[Features/Proxy_configuration|Proxy configuration]] || To add a section in the Control Panel that allows the user to configure network proxy settings.
|}

== Accepted Features for 0.96 ==
These features have been accepted by the Release Manager for the Sugar 0.96 Release.
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Owner !! Complete !!Name !!Summary !!Updated
|-
| Gonzalo Odiard || 0% || [[Features/EvinceIntrospectionBindings | Evince Introspection Bindings]] || The pygtk bindings used until F14 to use the evince backend in Read activity, are no longer present in F16. We need use the new gi based bindings. || 1-Nov-2011
|-
| Manuel Quiñones || 0% || [[Features/WebKit | Port Browse to use WebKit through introspection]] || Browse and related components are switching to WebKit as its back-end technology provider. || 1-Nov-2011
|-
| Simon Schampijer || 0% || [[Features/GTK3 | GTK3]] || Sugar needs to rebase itself on new generations of its key underlying technologies: GTK+ 3 and PyGObject Introspection. || 1-Nov-2011
|-
|}

== Feature Process ==

* The process for adding, proposing, and accepting new features into Sugar is on the [[Features/Policy]] page.
* The deadline for proposing and completing new features is the ''Feature Freeze'' on the [[0.96/Roadmap]]
* Feature pages in process but not targeted for a particular release can be found in [[:Category:Feature Page Incomplete]]

Machine/identity

2011-09-18T14:17:14Z

Sascha silbe: Document installation of VM "identity" on treehouse

== Description ==

<code>identity</code> is a 64bit VM running Debian Squeeze for the client certificate based OpenID provider.

== Installation ==

=== Base system ===

sudo virsh vol-create-as treehouse identity-root 8G
sudo virt-install --ram=512 --name=identity --arch=x86_64 --vcpus=1 --hvm \
--accelerate --disk vol=treehouse/identity-root --network=network:default \
--nographics --extra-args='console=tty0 console=ttyS0,115200n8 expert' \
--location=http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/

This will create a new VM and run the Debian installer inside it, with an emulated serial console attached to stdio.

Config options:
* english, US, US keyboard
* identity, sugarlabs.org
* use entire disk, all in one, remove swap, recreate / (full size), noatime + user_xattr
* user "administrator" (not used) with root password (manually removed later)
* package sets: "Standard system", "SSH server"

After reboot:
* Log in as root with password (still via emulated serial console)
* <code>passwd -d root</code>
* <code>aptitude install etckeeper monkeysphere</code>
* Set up monkeysphere as usual (host key, user authentication, keyserver)
* Set up second network interface with static IPv4 address, IPv6 tunnel
* Shutdown and (re)start VM (needed for libvirtd to create the network interface - <code>attach-interface</code> didn't do it)

Service/shell

2011-09-18T09:41:12Z

Sascha silbe: /* Public web hosting */ fix link

'''To request a new account, go to [[Service/Account]].'''

== Hostnames ==

* ssh://shell.sugarlabs.org
* http://people.sugarlabs.org/

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

'''sysadmin AT sugarlabs DOT org'''

For non-emergency calls, preferably send email to the administrative contact.
For urgent requests, the list of systems administrators is on [[Machine/sunjammer]].

== Notes ==

=== Password Management ===

To change your password, you can visit https://ldap.sugarlabs.org/passwd .
To reset your password, send a GPG-signed request to the sysadmin contact.

Passwords expire every 6 months. You will receive an email remainder a few
days in advance. If you don't update your password, your account will be disabled,
including shell access via ssh public keys.

To conserve resources, shell accounts will be removed from the system after
6 months of inactivity.

=== Local email management ===

Instead of forwarding email to another account, you could use IMAP or our webmail.
See [[Service/imap]] and [[Service/smtp]].

=== Public web hosting ===

The contents of <code>~/public_html</code> will be visible as http://people.sugarlabs.org/USERNAME
and http://people.sugarlabs.org/~USERNAME .

You can use PHP in your web pages. It will execute with your credentials.

Please avoid distributing non-free software from your account. It is also not allowed by the terms under which the [http://www.fsf.org/ Free Software Foundation] hosts us.

=== Public git hosting ===

You can publish your personal git repositories on http://people.sugarlabs.org/gitweb .
The repositories will also be accessible via the git protocol as
git://people.sugarlabs.org/USERNAME/REPONAME.git

* Copy or symlink your repository to <code>~/public_git</code>.
* Ensure that the path to your repository is publicly readable.
* Touch the file <code>git-daemon-export-ok</code> in the repository.

=== OpenID ===

Your account provides an [http://openid.net/ OpenID] identity provider that can be
used to log into any OpenID-enabled service: https://id.sugarlabs.org/USERNAME .

=== IRC Proxies ===

You can run your favorite IRC client or proxy on your account. We also offer a system-wide [[Sysadmin/IRC_Proxy|IRC Proxy]].

== See Also ==

* [[Service/Account]] (for users)
* [[Sysadmin/User_management]] (for sysadmins)
* [[Service/imap]]
* [[Service/smtp]]

[[Category:Service|shell]]

Service/shell

2011-09-18T09:39:28Z

Sascha silbe: /* Public web hosting */ fix link

'''To request a new account, go to [[Service/Account]].'''

== Hostnames ==

* ssh://shell.sugarlabs.org
* http://people.sugarlabs.org/

== Hosted on ==

[[Machine/sunjammer]]

== Administrative contact ==

'''sysadmin AT sugarlabs DOT org'''

For non-emergency calls, preferably send email to the administrative contact.
For urgent requests, the list of systems administrators is on [[Machine/sunjammer]].

== Notes ==

=== Password Management ===

To change your password, you can visit https://ldap.sugarlabs.org/passwd .
To reset your password, send a GPG-signed request to the sysadmin contact.

Passwords expire every 6 months. You will receive an email remainder a few
days in advance. If you don't update your password, your account will be disabled,
including shell access via ssh public keys.

To conserve resources, shell accounts will be removed from the system after
6 months of inactivity.

=== Local email management ===

Instead of forwarding email to another account, you could use IMAP or our webmail.
See [[Service/imap]] and [[Service/smtp]].

=== Public web hosting ===

The contents of <code>~/public_html</code> will be visible as http://people.sugarlabs.org/USERNAME
and http://people.sugarlabs.org/~USERNAME .

You can use PHP in your web pages. It will execute with your credentials.

Please avoid distributing non-free software from your account. It is also not allowed by the terms under which the [[http://www.fsf.org/ Free Software Foundation]] hosts us.

=== Public git hosting ===

You can publish your personal git repositories on http://people.sugarlabs.org/gitweb .
The repositories will also be accessible via the git protocol as
git://people.sugarlabs.org/USERNAME/REPONAME.git

* Copy or symlink your repository to <code>~/public_git</code>.
* Ensure that the path to your repository is publicly readable.
* Touch the file <code>git-daemon-export-ok</code> in the repository.

=== OpenID ===

Your account provides an [http://openid.net/ OpenID] identity provider that can be
used to log into any OpenID-enabled service: https://id.sugarlabs.org/USERNAME .

=== IRC Proxies ===

You can run your favorite IRC client or proxy on your account. We also offer a system-wide [[Sysadmin/IRC_Proxy|IRC Proxy]].

== See Also ==

* [[Service/Account]] (for users)
* [[Sysadmin/User_management]] (for sysadmins)
* [[Service/imap]]
* [[Service/smtp]]

[[Category:Service|shell]]

Events/SugarCamp

2011-08-24T21:24:02Z

Sascha silbe: /* Off-schedule hacking sessions */ add touch screen support

=== General information ===

Please see http://olpc-france.org/blog/sugar-camp-2011-in-paris/

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
| staying with Simon between 9 and 12 and will then find sth for the other 2 nights
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
| 10, 11
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] w/ Christoph
|-
| Sascha Silbe, Sabine Schneider
| 9-14
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma]
|-
|-
| Mitchell Seaton
| 7-12
| Staying at [http://www.montclair-hostel.com/ Le Montclair Hostel]
|-
| Christophe Guéret
| 10
| Staying at [http://www.booking.com/hotel/fr/de-paris.en-us.html Hotel de Paris]
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

Accomodation options (sorted roughly from cheapest to nicest):
* [http://www.woodstock.fr/rates.php Woodstock hostel] budget hostel. Daniel stayed here before, it's not the nicest place in the world (but he'd stay again).
* [http://www.hotel-bb.com/reservation-hotel/hotel_info?hotelId=4244#hotel&utm_source=googlemap&utm_medium=2010&utm_campaign=googlemap B&B Hotel PARIS Porte de la Villette]. Really cheap "internet offer" hotel rooms - ~18 euro per person per night for a twin? [http://www.tripadvisor.co.uk/Hotel_Review-g187147-d261698-Reviews-B_B_Paris_Porte_de_la_Villette-Paris_Ile_de_France.html Dodgy at night?]. 1km to venue.
* [http://www.st-christophers.co.uk/paris-hostels/book-paris-hostels St Christophers Hostel]. Massive hostel. 1.2km to venue.
* [http://www.paris-hostel.biz/budget.html Perfect hotel & hostel] affordable double/triple rooms, with private apartments nearby. 4.2km from venue. --> fully booked already [[User:ChristophD|ChristophD]] 08:52, 19 August 2011 (EDT)
* [http://www.montclair-hostel.com/ Le Montclair Hostel] - a little more expensive. 3.6km to venue.
* [http://www.caulaincourt.com/eng/resa-eng.php Caulain Square Hostel]. 4.8km from venue.
* [http://paris.fr.craigslist.fr/vac/] CraigsList

=== Off-schedule hacking sessions ===

There is separate space available on Saturday and Sunday for hacking sessions, and Bastien is looking for somewhere for Monday too (if not, we can tour some cafes).

Ideas for sessions (please add/edit):
* Focus on a couple of 11.3.0 issues (Daniel, Simon, Saturday afternoon?)
* Finish some pending design discussions (Simon, Gary, Sascha)
* The road to PyGI/GTK3: no-hippo, porting Sugar theme to GTK3, etc. (Daniel, Simon, Raul, Sunday and Monday?)
* Extra documentation session: wikification of OLPC's new deployment guide PDF, documentation for ongoing Haiti efforts (Christoph)
* Journal improvements: Action View, multi selection, WebDAV support, version support, etc. (Sascha)
* Touch screen support (Sascha)

Events/SugarCamp

2011-08-24T21:21:35Z

Sascha silbe: /* Off-schedule hacking sessions */ add Journal improvements, add myself to some proposed sessions

Events/SugarCamp

2011-08-24T19:57:34Z

Sascha silbe: staying at Hotel Palma 9.-14.

=== General information ===

Please see http://olpc-france.org/blog/sugar-camp-2011-in-paris/

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
| staying with Simon between 9 and 12 and will then find sth for the other 2 nights
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
| 10,11
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] w/ Christoph
|-
| Sascha Silbe, Sabine Schneider
| 9-14
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma]
|-
|-
| Mitchell Seaton
| 7-12
| Staying at [http://www.montclair-hostel.com/ Le Montclair Hostel]
|-
| Christophe Guéret
| 10
| no decided yet, interested in sharing something
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

Accomodation options (sorted roughly from cheapest to nicest):
* [http://www.woodstock.fr/rates.php Woodstock hostel] budget hostel. Daniel stayed here before, it's not the nicest place in the world (but he'd stay again).
* [http://www.hotel-bb.com/reservation-hotel/hotel_info?hotelId=4244#hotel&utm_source=googlemap&utm_medium=2010&utm_campaign=googlemap B&B Hotel PARIS Porte de la Villette]. Really cheap "internet offer" hotel rooms - ~18 euro per person per night for a twin? [http://www.tripadvisor.co.uk/Hotel_Review-g187147-d261698-Reviews-B_B_Paris_Porte_de_la_Villette-Paris_Ile_de_France.html Dodgy at night?]. 1km to venue.
* [http://www.st-christophers.co.uk/paris-hostels/book-paris-hostels St Christophers Hostel]. Massive hostel. 1.2km to venue.
* [http://www.paris-hostel.biz/budget.html Perfect hotel & hostel] affordable double/triple rooms, with private apartments nearby. 4.2km from venue. --> fully booked already [[User:ChristophD|ChristophD]] 08:52, 19 August 2011 (EDT)
* [http://www.montclair-hostel.com/ Le Montclair Hostel] - a little more expensive. 3.6km to venue.
* [http://www.caulaincourt.com/eng/resa-eng.php Caulain Square Hostel]. 4.8km from venue.
* [http://paris.fr.craigslist.fr/vac/] CraigsList

=== Off-schedule hacking sessions ===

There is separate space available on Saturday and Sunday for hacking sessions, and Bastien is looking for somewhere for Monday too (if not, we can tour some cafes).

Ideas for sessions (please add/edit):
* Focus on a couple of 11.3.0 issues (Daniel, Simon, Saturday afternoon?)
* Finish some pending design discussions (Simon, Gary)
* The road to PyGI/GTK3: no-hippo, porting Sugar theme to GTK3, etc. (Daniel, Simon, Raul, Sunday and Monday?)
* Extra documentation session: wikification of OLPC's new deployment guide PDF, documentation for ongoing Haiti efforts (Christoph)

Talk:Sugar Labs/Donate

2011-07-24T18:07:12Z

Sascha silbe: request to add new section for non-US donations

== From outside the US ==

The note about wire transfers is hidden inside the "Mail us a check" section. It would be nice to make it more prominent by moving it to a new section titled "From outside the US". The text could read:

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 <conservancy@softwarefreedom.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]]. If you're inside the EU you may contact [[User:Sascha_silbe|Sascha Silbe]].

-- [[User:Sascha silbe|Sascha silbe]] 14:07, 24 July 2011 (EDT)

== Membership ==

I would like to propose that Sugar Labs reconsiders adding a membership structure for donors. It appears this was already discussed in the oversight board meeting that took place 2008/09/19, as indicated in the meeting minutes excerpt:"We also discussed the idea of members dues, but reached consensus that it wasn't a good idea at this stage." (http://sugarlabs.org/go/Sugar_Labs/OversightBoard/Meeting_Minutes-2008-09-19)

As a potential donor, I see the following benefits to implementing a membership structure:
#It is easier to introduce other potential donors to the project when one brandishes a fancy membership card.
#Annual membership payments would match nicely with the annual salary requirements of paid developers.
#Membership tenure (in the form of cheaper renewals, bounty points, etc . . .) could be used to entice existing members to renew their memberships.

Some examples of other non-profit organizations that utilize a membership based donation system:
#The Planetary Society (https://planetary.org/join/membership/)
#*Founded in 1980
#Free Software Foundation (https://www.fsf.org/associate/support_freedom/join_fsf?referrer=4052)
#*Provides members with bootable membership cards
#Electronic Frontier Foundation (https://secure.eff.org/site/Donation?ACTION=SHOW_DONATION_OPTIONS&CAMPAIGN_ID=1082&JServSessionIdr006=8sqitlker1.app13b)
#*Receive a T-shirt and/or hat with membership

== Donating hardware ==

If you donate hardware to Sugar Labs and give us a full inventory that you donate, we will send a letter back that acknowledges the in-kind donation. As far as the value of the donation and how much you can you use as a tax deduction, that's up to the donor to discuss with their accountant, using the acknowledgment of the in-kind donation. In other words, the recipient 501(c)(3) organization doesn't get
involved with what the financial value is, it merely acknowledges for the donor that the physical items have been received as an in-kind donation on a particular date. The rest is for the donor and their
accountants to figure out.

Service/mirrors

2011-07-24T09:10:19Z

Sascha silbe: Instructions for adding a mirror, minor changes

<noinclude>{{TeamHeader|Infrastructure Team}}{{TOCright}}
[[Category:Resource]]

==Introduction==
A content delivery network or content distribution network (CDN) is a system of computers containing copies of data, placed at various points in a network so as to maximize bandwidth for access to the data from clients throughout the network. A client accesses a copy of the data near to the client, as opposed to all clients accessing the same central server, thereby causing a bottleneck near that server.

==Mirrors==
The current list of available mirrors is available at http://mirrors.sugarlabs.org/

==Goals==
* Reduce bandwidth at primary download server.
* Improve quality of service for users.
* Move content closer to users.

==Setting up a Mirror==
Setting up a mirror is very easy. All you need is a web server which is available via http, and (if possible) rsync.

Please contact systems@sugarlabs.org if you are interested.

== System Summary ==
The Sugar Labs Content Delivery Network uses [http://www.mirrorbrain.org/ MirrorBrain] as a redirector. The redirector, which lives in a Sugar Labs data center, keeps track of which files are available on which mirror. When a user requests a file, the redirector points the user to the correct mirror and automatically starts the file download.

=== Mirrors ===
[http://mirrors.sugarlabs.org Mirrors] are completely passive. To set up a mirror, a mirror system administrator needs to:
* Set up rsync job to synchronise a copy of the files on downloads.sugarlabs.org onto their local system.
* Publish the files via HTTP and -- if possible -- rsync. Rsync allows for efficient [http://www.mirrorbrain.org/features/#mirror-monitoring mirror monitoring] (scanning). FTP is less efficient, but still preferred over an HTTP-only mirror.
* Alert the Sugar Labs system administrators that they would like their mirror into rotation, including the following information in the request:
** Name and URL of the mirror operator (e.g. organisation)
** Name and email address of the administrative contact
** [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO 3166-1 alpha-2] country code of the server location
** HTTP base URL of the files on the mirror
** rsync base URL of the files on the mirror

=== Redirector ===

* Choose a name for the mirror, usually the host name.
* Register the mirror with MirrorBrain:
sudo -u mirrorbrain mb new <mirror name> --operator-name <operator name> \
--operator-url <operator URL> -a <admin name> -e <admin email> \
-c <country code> -H <base HTTP URL> -R <base rsync URL> -F <base FTP URL>
* Scan and enable the mirror:
sudo -u mirrorbrain mb scan -e <mirror name>

File:Sugar-wifi-conn-disable-2.png

2011-06-30T21:34:20Z

Sascha silbe: Screenshot of the wireless network Frame device in connected state showing the Disable wireless devices option (proposed)

Screenshot of the wireless network Frame device in connected state showing the Disable wireless devices option (proposed)

File:Screenshot of the wireless network Frame device in disabled state.png

2011-06-30T21:31:47Z

Sascha silbe: Screenshot of the wireless network Frame device in disabled state (proposed)

Screenshot of the wireless network Frame device in disabled state (proposed)

File:Sugar-wifi-disconn-text.png

2011-06-30T20:28:00Z

Sascha silbe: Screenshot of the wireless network Frame device in disconnected state (proposed change)

Screenshot of the wireless network Frame device in disconnected state (proposed change)

File:Browse-save-password.png

2011-06-30T19:48:55Z

Sascha silbe: Screenshot of the save password dialog in Browse

Screenshot of the save password dialog in Browse

File:Sugar-ap-forget.png

2011-06-26T19:31:54Z

Sascha silbe: Screenshot of the proposed palette option to remove connections / forget network credentials.

Screenshot of the proposed palette option to remove connections / forget network credentials.

0.92/Notes

2011-06-07T17:27:09Z

Sascha silbe: Copy over and adjust content from 0.90 Release Notes. Still needs some work.

<noinclude>{{ Translations | [[0.92/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Category:Release Notes]]

''Please do not edit unless you are part of the Sugar Release Team!''

Sucrose 0.92 Release Notes

== Introduction ==
Sucrose 0.92 is the latest version of the [http://www.sugarlabs.org/ Sugar learning platform]: Sugar promotes collaborative learning through [http://activities.sugarlabs.org/ Sugar Activities] that encourage critical thinking, the heart of a quality education. Designed from the ground up especially for children, Sugar offers an alternative to traditional “office-desktop” software. Furthermore it provides a flexible and powerful platform for activity developers.

Sugar is Free and Open Source Software and consists of [[Taxonomy#Glucose:_The_base_Sugar_environment|Glucose]], the base system environment; and [[Taxonomy#Fructose:_The_set_of_demonstration_activities|Fructose]], a set of demonstration activities. This new release contains many new features, performance and code improvements, bug fixes, and translations.

== What is new for users ==

== What is new for distributors and deployers ==

== What's new for developers ==
The following changes are important for developers using the Sucrose 0.90 developer platform.

=== Widgets ===

=== API ===

=== Activity Authors guidelines ===
There are still many activities that do not use the new activity toolbars introduced in 0.86. We encourage activity authors to use the new toolbars as there have been huge improvements in usability (e.g., stopping an activity).

Jim Simmons has written a guide to writing Sugar Activities (Please see [http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction Make your own Sugar Activities!]) which details how to convert your activity to the new toolbars while still keeping backward compatibility with older Sugar versions.

== What's new for packagers ==

== Internationalization (i18n) and Localization (l10n) ==

== Compatibility ==

== Update to this version ==
Please use the instructions for your distribution (SoaS, Fedora, Ubuntu, Debian, etc.) of choice to upgrade to this release. Note that it may take a while until the release is packaged for each distribution. Please stay tuned for distribution specific announcements and watch out for updates at [[Downloads|Get Sugar]].

== Getting the sources ==
If you want to package Sugar for your favorite distribution or just want to examine Sugar's lovely code here are the released bundles. If you are interested in the full changelog you can use the [http://git.sugarlabs.org/ Sugar git repositories].

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.92.1.tar.bz2 sugar 0.92.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.92.1.tar.bz2 sugar-datastore 0.92.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.92.1.tar.bz2 sugar-toolkit 0.92.1]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.92.0.tar.bz2 sugar-base 0.92.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-presence-service/sugar-presence-service-0.90.2.tar.bz2 sugar-presence-service 0.90.2]
* [http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.92.0.tar.bz2 sugar-artwork 0.92.0]
* [http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.1.2390.tar.gz etoys 4.1.2390]
* [http://download.sugarlabs.org/sources/sucrose/glucose/hulahop/hulahop-0.7.1.tar.bz2 hulahop 0.7.1]

=== <abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> modules ===
* [http://download.sugarlabs.org/sources/sucrose/fructose/Pippy/Pippy-40.tar.bz2 Pippy 40]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-122.tar.bz2 Browse 122]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Calculate/Calculate-35.tar.bz2 Calculate 35]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-116.tar.gz Etoys 116]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Chat/Chat-70.tar.bz2 Chat 70]
* [http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/TurtleArt-108.tar.bz2 TurtleArt 108]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Jukebox/Jukebox-20.tar.bz2 Jukebox 20]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-24.tar.bz2 Log 24]
* [http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-17.tar.bz2 ImageViewer 17]
* [http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-73.tar.bz2 Write 73]

== Installing/running 0.92 ==

===On Fedora from the shell:===
yum groupinstall sugar-desktop
will install Sugar 0.92 as a GDM selection on login.

===Install sugar-emulator===
yum install sugar-emulator
Run:
sugar-emulator -f
to run Sugar in a full screen window in a Gnome session.

'''Note''': You may need to disable SELinux (See http://www.crypt.gen.nz/selinux/disable_selinux.html)

== Looking at the release cycle details ==
You can browse the notes of each development release in [[0.92/Roadmap#Schedule]]. Their respective sources are listed there as well.

== Credits ==
Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible.

We want to especially thank:
* the [[Infrastructure_Team | ''Infrastructure team'']] which does all this great work in the background without which the development would not be possible at all,

* the ''deployments'' that provide the development team with feedback from the field,

* the [[Design_Team | ''Design team'']] which guided the design of features with UI changes or impact on the workflow,

* the [[Translation_Team | ''Translation team'']] which makes sure that Sugar is enjoyable in the local languages of our users,

* the ''developers'' that submit patches for new features and bug fixes and do review other's patches,

* the ''maintainers'' that make sure their code is shippable and which provide packagers with new tarballs,

* the ''packagers'' which provide distributions with new Sugar packages,

* the [[Sugar_on_a_Stick | ''SoaS team'']] for providing a Sugar version to test with during the development cycle,

* the ''testers'' for finding the small and bigger issues,

* the ''release team'' and [[Development_Team | ''Development team'']] for coordinating those efforts.

Design Team/Meetings

2011-05-29T15:08:50Z

Sascha silbe: /* Upcoming IRC meeting: Sunday 15:00 UTC */ add topic for Neighborhood design change (NetworkManager interfacing)

<noinclude>{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}
[[Category:Design Team]]
[[Category:Meetings]]</noinclude>
__NOTOC__
The Sugar Labs Meetings calendar is available in a variety of formats at these links: [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].

To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run:
:{{Code|date -d '[current date] [time] UTC'}}
:{{Code|date -d '2008-06-03 14:00 UTC'}}
{{Admon/important|Remember|Please post discussion materials for the full community. [[Design Team/Proposals]] and [[Features]] are 2 good places for referencing design ideas.}}

=== Upcoming IRC meeting: Sunday 15:00 UTC ===

Topics:
* Reword warning in Browse when stopping while there are downloads happening in the background ({{Bug|1508}}, [http://lists.sugarlabs.org/archive/sugar-devel/2011-May/thread.html#31362 thread on sugar-devel])
* PDF support for Browse ([https://patchwork.sugarlabs.org/patch/797/ Patch]): Icon, placement of icon
* Neighborhood: Differentiate between devices (Access Points, GSM/3G modems, wired ethernet) and configured NetworkManager connections so we can support advanced set-ups like hidden SSID and separate networks with the same name (default router configuration)
* General feedback on [[Design_Team/Toolbar Catalog|existing activity toolbar designs]]. (Gonzalo)
* Notification icon high contrast improvements (garycmartin)
* Follow up on a standard tool icon for create-new/modify type Activity functionality (e.g. cog/spanner/scissors discussion) (erikos)
* Invocation widget for new details view dialogue placement/design (replace/repurpose Keep widget? Browse 'show in journal' alert to use new dialogue?)
* [[Design_Team/0.88_Meeting#Resume.2FStart_new_on_the_Home_View|Activity startup in the Home View]]: Introduce new concept to distinguish between 'start new' vs 'resume' (erikos)
* Control Panel [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29827 rework] (erikos)
* School server icon in Neighbourhood ([http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29979 part of] Thread "Reflect internet connectivity in the 'Network' frame icon" (esp. a [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/030015.html set of design questions]), [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43#i_2629524 mention of school server icon] during the last meeting)
* [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29869 Indicating "internet connectivity"]
* Frame: Expand hot corner on the upper left to be the entire grid cell (big enough for finger) (walterbender)
** To accommodate the unintentional frame activation that continues to plague Learners, so much so that Dextrose defaults to inactive corners and edges, add a Touch corner section to the control panel for the Frame that includes the selection of upper left or upper right (an accessibility feature, lower corners will interfere with scroll bars) and a dimension slider (pixels) 0 to grid width. (FGrose)
* [[Design_Team/Proposals/Home_View/Toolbar|Home View toolbar -> Framebar]] ([http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029953.html FGrose])
* Give priority to last installed activity by date installed and not version number ie:browse-120 installed from sugar Control panel update should not block browse-119.xo installed later [[The_Undiscoverable#Activities_are_located_in_2_places |Activities_are_located_in_2_places]] deleting browse=119.xo reverts to older browse-120 from update. (Sometimes the latest update does not work)(satellit)?
Some further information on the above topics is included in mails from [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029912.html Simon] and [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029915.html Walter]
* Journal backup UIs (silbe)
** Backup/Restore via Activities (needs design input)
** Backup/Restore directly from Journal (currently implemented in Dextrose, is it appropriate to upstream?)

Future topics (missing information):
* virtual keyboard support (silbe)
* Uruguays accessibility support patch series (silbe)
* tablet support (silbe)

Old topics:
* How to handle start-up delay due to data store migration ({{Bug|1546}})? (silbe)
* Uncaught exception handler ({{Bug|2063}})
* "Your Journal is empty" shown for unreadable storage media ({{Bug|1810}})
* invalid/unknown colors are shown as owner colors ({{Bug|1750}})
* Drop down menus give no indication of their existence, also are too slow to load ({{Bug|1169}}, [http://people.sugarlabs.org/bernie/sugar/sugar-0.88-patches/sugar-toolkit/kill-the-delayed-menus-for-good.patch Patch] from Michael Stone)

We should also go through [http://bugs.sugarlabs.org/query?component=design&status=accepted&status=assigned&status=new&status=reopened open tickets filed against component design] some time.

== Who and what==
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.

In general, discussion focuses on:
* high level design goals and ideas
* feedback and discussion of problems in the current design
* reviews of design proposals

== Adding topics ==
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.

== Past meetings ==

=== Sunday 17th April 2011 15:00 UTC ===
* Proposal for adding a standard activity "About Dialog" (icarito)
* Discussion of extra metadata/files that could be good to add ABOUT/README/AUTHORS/MAINTAINER upstream git rep in activity.info (silbe)
See [http://meeting.sugarlabs.org/sugar-meeting/2011-04-17#i_2658914 logs] for details.

=== Sunday 10th April 2011 15:00 UTC ===
* Follow up on a standard tool icon for create-new/modify type Activity functionality (e.g. cog/spanner/scissors discussion) (erikos)
* Built-in Activity examples UI and/or root fs access (walterbender)
* Standard system icon use (re Gonzalo's email)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-10T14:41:44 logs] for details.

=== Sunday 27th March 2011 15:00 UTC ===
* Feedback for Record Activity [http://wiki.laptop.org/go/User:Godiard/Record/NewToolbar toolbar rework]. (garycmartin)

See [http://meeting.sugarlabs.org/sugar-meeting/2011-03-27#i_2649936 log] for details.

=== Sunday 20th March 2011 15:00 UTC ===
* A standard tool icon for create-new/modify type Activity functionality (e.g. for Memorize, Abacus, et al user customisation) (erikos)
** use of a scissor (like editing an activity), or the gear like we use in 'view source'?
* Get rid of Alt-1 for taking screenshots (collides with some applications, e.g. irssi) (silbe)
* What date should the activities list view show for pre-installed activities? ([http://dev.laptop.org/ticket/10487 OLPC#10487], [http://lists.laptop.org/pipermail/devel/2011-March/thread.html#31544 patch discussion]) (silbe)

See this [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-20T19:01:02 log] and this [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-20T20:03:00 log] for details

=== 2011 March 13 ===

* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)
** discussed on [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-27 27 February] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07#i_2633453 20 February], when we agreed to prepare [[Talk:Features/Write_to_journal_anytime#Mockups|mockups]] for some of the ideas. These [http://wiki.sugarlabs.org/images/e/e2/Detailview_20110313.pdf design mockups] were reviewed today.

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-13T15:05:59 logs] for details.

=== 2011 March 06 ===

* Housekeeping discussion (trying to keep realtime meeting agenda items on things that benefit from realtime)
** Journal backup UI ([http://patchwork.sugarlabs.org/patch/174/ Patch] from Martin Abente, [http://patchwork.sugarlabs.org/patch/171/ Patch] from Sascha Silbe, [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4326 Backup] and [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4327 Restore] activities by Sascha Silbe) (silbe)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-06 logs] for details

=== 2011 February 27 ===

Discussed topics:
* Size issue with icons in Random Layout (Home View) (walterbender)
** [[Design_Team/Proposals/Home_View/Freeform_icon_size|mock-ups]]
* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)
** discussed [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07#i_2633453 last week], agreed to prepare [[Talk:Features/Write_to_journal_anytime#Mockups|mockups]] for some of the ideas.

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-27 logs] for details.

=== 2011 February 20 ===

Discussed topics:
* Remove 'Keep' Button: Replace by 'copy to' functionality in the Journal (erikos)
** [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22| The Notion of Keeping]]
** Remove button and add 'Copy to >' functionality to the Frame palette for the activity. This preserves ready access from current activity, but minimizes unintentional copying. (FGrose)
**: [[Design_Team/Proposals/Toolbars/Icons|possible copy-to-journal icon]]
* CPU and memory resource indicator for the Frame (silbe)
*: [[Features/Resource monitoring]] (action item)
* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07.html minutes] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07 logs] for details.

=== 2011 February 13 ===

Discussed topics:
* Size issue with icons in Random Layout (Home View) (walterbender)
* Speaker frame device: pop up palette on left-click instead of toggling mute (silbe)
* Don't hide Register menu item upon successful registration (silbe)
* Journal entries on external media: [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029848.html Invalidate preview] if the data file was changed? (silbe)
** 'Watermark' the image with 'Changed'. (Even an old image may help identify the object.) (FGrose)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43.html minutes] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43 logs] for details.

Followup discussion:
* Updating the [[Human Interface Guidelines]]
*: A [http://wiki.sugarlabs.org/index.php?title=Human_Interface_Guidelines&printable=yes printable version] can be prepared by selecting 'Printable version' in the 'Using the Wiki' section of the sidebar.

=== 2010 July 10 ===
* http://lists.laptop.org/pipermail/devel/2010-July/029187.html
*: Designs for the proposed Start new/Resume functionality in Home view.
* [[Design Team/Meetings/2010-07-10|meeting log]]
=== 2009 August 16 ===
[http://meeting.sugarlabs.org/sugar-meeting.minutes.20090816_0941.html Summary] & [http://meeting.sugarlabs.org/sugar-meeting.log.20090816_0941.html log] - Sugar 0.86 Design

=== 2009 May 09 ===
[http://meeting.sugarlabs.org/sugar-meeting.20090509_1013.html Summary] & [http://meeting.sugarlabs.org/sugar-meeting.log.20090509_1013.html log].
==== Topics ====

* Sayamindu's dictionary dialog.
*:See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg04042.html
* Jameson's accelerators proposals.
*:See [[Design_Team/Proposals#Keyboard_Action]]
* Printing proposal from several people.
*:See [[Print Support]], http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03984.html, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03991.html
* Martin's clock proposal.
*:See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03934.html

=== 2009 April 19 ===

Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090419_0911.html

==== Topics ====

We discussed design goals for the next release 0.86. Design mockups will be created in response to the high-level features listed below (potentially in advance of SugarCamp 2009 on May 16th), to further illustrate the design intent and allow for integration with the development schedule.

High-level feature recap:

* polish activity list in Home
* support filtering/searching via tags in Home
* add list views to groups/neighorhood
* make groups dynamic (like neighborhood)
* extend activity chat
* add overlay chat to groups/neighborhood
* design a bulletin-board _activity_
* remove management from activity list, ensure _all_ installed activities are in Journal
* new toolbar design

Concrete design/development tasks:

# design mockups to make the frame more discoverable
# design mockups to polish the new toolbars
# Home list view: remove the date column and enable alphabetical sort. Label versions "Version x"
# Design mockups for tagging/filtering/search within Home view
# Draft changes to activity.info file to support tagging
# Design mockups for overlay chat in groups/neighborhood (should also include revising the activity chat..which exists but not as earlier designs proposed)
# Design mockups of bulletin board activity
# Design mockups for list views in groups and neighborhood

=== 2009 March 21 ===

Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090321_1009.html

==== Topics ====

Discussion of the Home view and whether to abandon the notion of favorites for a single consolidated view

See [[Design Team/Proposals]].

Unify look of web services

=== (Marketing Team) 2009 March 10 ===
Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 
Summary: http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03132.html

=== 2009 March 01 ===

Logs: [[Design Team/Meetings/09.03.01]]

==== Topics ====

We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.

Other topics: Discuss development roadmap and prioritize design activities for next build

=== 2008 December 19 ===

==== Topics ====

We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.

=== 2008 December 04 ===

==== Topics ====

We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.

==== Media ====

* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)‎]]

==== Logs ====

* http://meeting.sugarlabs.org/sugar-meeting/2008-12-04#i_2382400

=== 2008 November 26 ===

We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.

==== Topics ====
===== Short Term Roadmap Definition =====

To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.

=====Groups=====
=====Resuming activities from Home=====
=====Enhancing the Journal=====
=====Improving Toolbars=====
=====Encouraging Naming/Tagging=====

==== Logs ====
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html

=== 2008 September 18 ===
==== Topics ====
===== Visual Clipboard API =====
For reference, please see the [[olpc:Specifications/Clipboard| clipboard specification]]. For a more targeted list of features and goals, please see the [[Design Team/Specifications/Clipboard|clipboard planning page]].

We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.

Some references:
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html

===== Advancing the Journal =====
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].

Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.

===== Icon reviews =====
We discussed three icons today.

'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.

'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.

'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.

Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.

Design Team/Meetings

2011-05-29T15:00:39Z

Sascha silbe: /* Upcoming IRC meeting: Sunday 15:00 UTC */ add topic for PDF support in Browse

<noinclude>{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}
[[Category:Design Team]]
[[Category:Meetings]]</noinclude>
__NOTOC__
The Sugar Labs Meetings calendar is available in a variety of formats at these links: [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].

To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run:
:{{Code|date -d '[current date] [time] UTC'}}
:{{Code|date -d '2008-06-03 14:00 UTC'}}
{{Admon/important|Remember|Please post discussion materials for the full community. [[Design Team/Proposals]] and [[Features]] are 2 good places for referencing design ideas.}}

=== Upcoming IRC meeting: Sunday 15:00 UTC ===

Topics:
* Reword warning in Browse when stopping while there are downloads happening in the background ({{Bug|1508}}, [http://lists.sugarlabs.org/archive/sugar-devel/2011-May/thread.html#31362 thread on sugar-devel])
* PDF support for Browse ([https://patchwork.sugarlabs.org/patch/797/ Patch]): Icon, placement of icon
* General feedback on [[Design_Team/Toolbar Catalog|existing activity toolbar designs]]. (Gonzalo)
* Notification icon high contrast improvements (garycmartin)
* Follow up on a standard tool icon for create-new/modify type Activity functionality (e.g. cog/spanner/scissors discussion) (erikos)
* Invocation widget for new details view dialogue placement/design (replace/repurpose Keep widget? Browse 'show in journal' alert to use new dialogue?)
* [[Design_Team/0.88_Meeting#Resume.2FStart_new_on_the_Home_View|Activity startup in the Home View]]: Introduce new concept to distinguish between 'start new' vs 'resume' (erikos)
* Control Panel [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29827 rework] (erikos)
* School server icon in Neighbourhood ([http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29979 part of] Thread "Reflect internet connectivity in the 'Network' frame icon" (esp. a [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/030015.html set of design questions]), [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43#i_2629524 mention of school server icon] during the last meeting)
* [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/thread.html#29869 Indicating "internet connectivity"]
* Frame: Expand hot corner on the upper left to be the entire grid cell (big enough for finger) (walterbender)
** To accommodate the unintentional frame activation that continues to plague Learners, so much so that Dextrose defaults to inactive corners and edges, add a Touch corner section to the control panel for the Frame that includes the selection of upper left or upper right (an accessibility feature, lower corners will interfere with scroll bars) and a dimension slider (pixels) 0 to grid width. (FGrose)
* [[Design_Team/Proposals/Home_View/Toolbar|Home View toolbar -> Framebar]] ([http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029953.html FGrose])
* Give priority to last installed activity by date installed and not version number ie:browse-120 installed from sugar Control panel update should not block browse-119.xo installed later [[The_Undiscoverable#Activities_are_located_in_2_places |Activities_are_located_in_2_places]] deleting browse=119.xo reverts to older browse-120 from update. (Sometimes the latest update does not work)(satellit)?
Some further information on the above topics is included in mails from [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029912.html Simon] and [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029915.html Walter]
* Journal backup UIs (silbe)
** Backup/Restore via Activities (needs design input)
** Backup/Restore directly from Journal (currently implemented in Dextrose, is it appropriate to upstream?)

Future topics (missing information):
* virtual keyboard support (silbe)
* Uruguays accessibility support patch series (silbe)
* tablet support (silbe)

Old topics:
* How to handle start-up delay due to data store migration ({{Bug|1546}})? (silbe)
* Uncaught exception handler ({{Bug|2063}})
* "Your Journal is empty" shown for unreadable storage media ({{Bug|1810}})
* invalid/unknown colors are shown as owner colors ({{Bug|1750}})
* Drop down menus give no indication of their existence, also are too slow to load ({{Bug|1169}}, [http://people.sugarlabs.org/bernie/sugar/sugar-0.88-patches/sugar-toolkit/kill-the-delayed-menus-for-good.patch Patch] from Michael Stone)

We should also go through [http://bugs.sugarlabs.org/query?component=design&status=accepted&status=assigned&status=new&status=reopened open tickets filed against component design] some time.

== Who and what==
The meeting is targeted to Sugar core and activity developers, but remains open to anyone interested. It's primary purpose is to open the design approach, making it more transparent and allowing the community to provide feedback on both current and upcoming features.

In general, discussion focuses on:
* high level design goals and ideas
* feedback and discussion of problems in the current design
* reviews of design proposals

== Adding topics ==
You can add topics for discussion to the topics section for the meeting throughout the week. Posted topics will be collected and sent out in the announcement on the morning of the meeting.

== Past meetings ==

=== Sunday 17th April 2011 15:00 UTC ===
* Proposal for adding a standard activity "About Dialog" (icarito)
* Discussion of extra metadata/files that could be good to add ABOUT/README/AUTHORS/MAINTAINER upstream git rep in activity.info (silbe)
See [http://meeting.sugarlabs.org/sugar-meeting/2011-04-17#i_2658914 logs] for details.

=== Sunday 10th April 2011 15:00 UTC ===
* Follow up on a standard tool icon for create-new/modify type Activity functionality (e.g. cog/spanner/scissors discussion) (erikos)
* Built-in Activity examples UI and/or root fs access (walterbender)
* Standard system icon use (re Gonzalo's email)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-10T14:41:44 logs] for details.

=== Sunday 27th March 2011 15:00 UTC ===
* Feedback for Record Activity [http://wiki.laptop.org/go/User:Godiard/Record/NewToolbar toolbar rework]. (garycmartin)

See [http://meeting.sugarlabs.org/sugar-meeting/2011-03-27#i_2649936 log] for details.

=== Sunday 20th March 2011 15:00 UTC ===
* A standard tool icon for create-new/modify type Activity functionality (e.g. for Memorize, Abacus, et al user customisation) (erikos)
** use of a scissor (like editing an activity), or the gear like we use in 'view source'?
* Get rid of Alt-1 for taking screenshots (collides with some applications, e.g. irssi) (silbe)
* What date should the activities list view show for pre-installed activities? ([http://dev.laptop.org/ticket/10487 OLPC#10487], [http://lists.laptop.org/pipermail/devel/2011-March/thread.html#31544 patch discussion]) (silbe)

See this [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-20T19:01:02 log] and this [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-20T20:03:00 log] for details

=== 2011 March 13 ===

* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)
** discussed on [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-27 27 February] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07#i_2633453 20 February], when we agreed to prepare [[Talk:Features/Write_to_journal_anytime#Mockups|mockups]] for some of the ideas. These [http://wiki.sugarlabs.org/images/e/e2/Detailview_20110313.pdf design mockups] were reviewed today.

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-13T15:05:59 logs] for details.

=== 2011 March 06 ===

* Housekeeping discussion (trying to keep realtime meeting agenda items on things that benefit from realtime)
** Journal backup UI ([http://patchwork.sugarlabs.org/patch/174/ Patch] from Martin Abente, [http://patchwork.sugarlabs.org/patch/171/ Patch] from Sascha Silbe, [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4326 Backup] and [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4327 Restore] activities by Sascha Silbe) (silbe)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-06 logs] for details

=== 2011 February 27 ===

Discussed topics:
* Size issue with icons in Random Layout (Home View) (walterbender)
** [[Design_Team/Proposals/Home_View/Freeform_icon_size|mock-ups]]
* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)
** discussed [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07#i_2633453 last week], agreed to prepare [[Talk:Features/Write_to_journal_anytime#Mockups|mockups]] for some of the ideas.

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-27 logs] for details.

=== 2011 February 20 ===

Discussed topics:
* Remove 'Keep' Button: Replace by 'copy to' functionality in the Journal (erikos)
** [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22| The Notion of Keeping]]
** Remove button and add 'Copy to >' functionality to the Frame palette for the activity. This preserves ready access from current activity, but minimizes unintentional copying. (FGrose)
**: [[Design_Team/Proposals/Toolbars/Icons|possible copy-to-journal icon]]
* CPU and memory resource indicator for the Frame (silbe)
*: [[Features/Resource monitoring]] (action item)
* [[Features/Write_to_journal_anytime|Replace Naming Alert]]: a) switch to Journal detail view b) option in the activity toolbar to do a description and tags (erikos)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07.html minutes] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-20T16:30:07 logs] for details.

=== 2011 February 13 ===

Discussed topics:
* Size issue with icons in Random Layout (Home View) (walterbender)
* Speaker frame device: pop up palette on left-click instead of toggling mute (silbe)
* Don't hide Register menu item upon successful registration (silbe)
* Journal entries on external media: [http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029848.html Invalidate preview] if the data file was changed? (silbe)
** 'Watermark' the image with 'Changed'. (Even an old image may help identify the object.) (FGrose)

See [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43.html minutes] and [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-13T14:01:43 logs] for details.

Followup discussion:
* Updating the [[Human Interface Guidelines]]
*: A [http://wiki.sugarlabs.org/index.php?title=Human_Interface_Guidelines&printable=yes printable version] can be prepared by selecting 'Printable version' in the 'Using the Wiki' section of the sidebar.

=== 2010 July 10 ===
* http://lists.laptop.org/pipermail/devel/2010-July/029187.html
*: Designs for the proposed Start new/Resume functionality in Home view.
* [[Design Team/Meetings/2010-07-10|meeting log]]
=== 2009 August 16 ===
[http://meeting.sugarlabs.org/sugar-meeting.minutes.20090816_0941.html Summary] & [http://meeting.sugarlabs.org/sugar-meeting.log.20090816_0941.html log] - Sugar 0.86 Design

=== 2009 May 09 ===
[http://meeting.sugarlabs.org/sugar-meeting.20090509_1013.html Summary] & [http://meeting.sugarlabs.org/sugar-meeting.log.20090509_1013.html log].
==== Topics ====

* Sayamindu's dictionary dialog.
*:See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg04042.html
* Jameson's accelerators proposals.
*:See [[Design_Team/Proposals#Keyboard_Action]]
* Printing proposal from several people.
*:See [[Print Support]], http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03984.html, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03991.html
* Martin's clock proposal.
*:See http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03934.html

=== 2009 April 19 ===

Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090419_0911.html

==== Topics ====

We discussed design goals for the next release 0.86. Design mockups will be created in response to the high-level features listed below (potentially in advance of SugarCamp 2009 on May 16th), to further illustrate the design intent and allow for integration with the development schedule.

High-level feature recap:

* polish activity list in Home
* support filtering/searching via tags in Home
* add list views to groups/neighorhood
* make groups dynamic (like neighborhood)
* extend activity chat
* add overlay chat to groups/neighborhood
* design a bulletin-board _activity_
* remove management from activity list, ensure _all_ installed activities are in Journal
* new toolbar design

Concrete design/development tasks:

# design mockups to make the frame more discoverable
# design mockups to polish the new toolbars
# Home list view: remove the date column and enable alphabetical sort. Label versions "Version x"
# Design mockups for tagging/filtering/search within Home view
# Draft changes to activity.info file to support tagging
# Design mockups for overlay chat in groups/neighborhood (should also include revising the activity chat..which exists but not as earlier designs proposed)
# Design mockups of bulletin board activity
# Design mockups for list views in groups and neighborhood

=== 2009 March 21 ===

Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090321_1009.html

==== Topics ====

Discussion of the Home view and whether to abandon the notion of favorites for a single consolidated view

See [[Design Team/Proposals]].

Unify look of web services

=== (Marketing Team) 2009 March 10 ===
Log: http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 
Summary: http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg03132.html

=== 2009 March 01 ===

Logs: [[Design Team/Meetings/09.03.01]]

==== Topics ====

We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.

Other topics: Discuss development roadmap and prioritize design activities for next build

=== 2008 December 19 ===

==== Topics ====

We'll continue discussion of revised, and thorough, mockups for overlay chat in activities. This includes ways in which this chat system can extend into the other zoom levels, and short term and long term goals.

=== 2008 December 04 ===

==== Topics ====

We'll focus on possibilities for overlay chat in activites, presenting both short term and long term ideas, and discuss how this could later be extended to the neighborhood.

==== Media ====

* [[Media:Overlay_chat_sketch.pdf | Overlay chat sketch (PDF)‎]]

==== Logs ====

* http://meeting.sugarlabs.org/sugar-meeting/2008-12-04#i_2382400

=== 2008 November 26 ===

We'd like to hold a meeting this week while the topics discussed at the recent SugarCamp are fresh in our minds. Though this is not part of the usual meeting cycle, I think it's important enough to merit an extra meeting. Due to Thanksgiving on Thursday, we'll hold it on Wednesday instead.

==== Topics ====
===== Short Term Roadmap Definition =====

To capitalize on the extremely valuable discussions at the recent SugarCamp in Cambridge, we'd like to take some time to define a rough feature roadmap for the Sugar OS within the OLPC 9.1 timeframe. As a starting point for this discussion, we should likely review the various design proposals presented on the last day of the conference.

=====Groups=====
=====Resuming activities from Home=====
=====Enhancing the Journal=====
=====Improving Toolbars=====
=====Encouraging Naming/Tagging=====

==== Logs ====
* http://meeting.laptop.org/sugar-meeting.20081126_1018.html

=== 2008 September 18 ===
==== Topics ====
===== Visual Clipboard API =====
For reference, please see the [[olpc:Specifications/Clipboard| clipboard specification]]. For a more targeted list of features and goals, please see the [[Design Team/Specifications/Clipboard|clipboard planning page]].

We had a fairly long discussion about this, which didn't seem to get too far. Fortunately, a follow-up between Marco and I clarified some points, and we agreed that it should be possible to implement the majority of the goals across the system using the "formats" allowed in the GTK protocols, and falling back to sane defaults when extra info isn't provided.

Some references:
* http://www.pygtk.org/pygtk2tutorial/ch-NewInPyGTK2.2.html#sec-Clipboards
* http://www.pygtk.org/pygtk2tutorial/ch-DragAndDrop.html
* http://www.pygtk.org/pygtk2tutorial/ch-ManagingSelections.html

===== Advancing the Journal =====
I'd like to have a conversation regarding the current iteration of the Journal, future plans, and the steps we hope to take toward them in the next major release so we can scope our goals. The latest mockups (though slightly out of date) can be seen [http://wiki.laptop.org/go/Designs/Journal here].

Due to the lengthy clipboard discussion, we didn't hit this topic today. We'll pick it up first thing next week.

===== Icon reviews =====
We discussed three icons today.

'''Settings (control panel)''': By popular demand, a wrench was chosen as the base for this icon, though it was also proposed that a wrench and screwdriver could be clearer. It was agreed that the wrench is a simpler icon, and a more generic metaphor which could be used to represent "settings" throughout the system. A few visual tweaks {{Trac|8198|}} made many happier with the wrench, but since this isn't a major change they can come post 8.2.

'''View Details (Journal)''': The old designs for this button closely resembled a play button (but with an open triangle, akin to a greater than (>) symbol), which some found confusing. The new proposal is an ellipsis [...] icon, to indicate the idea that more info is available, but omitted in the abbreviated list view. This works nicely within the [wiki.laptop.org/go/Designs/Journal new Journal designs], since the icons will occasionally appear within a string of icon-annotated text. All present agreed the latter was a better direction. This change could make 8.2.

'''Access Point''': Recent experience reports have indicated that the removal of an identifier of the connected AP is frustrating. The proposal discussed is shown [http://interdimensionmedia.com/scratch/devices.png], which wraps the former AP icon (the circle) in "parenthesis" (meant to indicate radio signal). This retains the primitive circular shape of the current access points, but illustrates which is connected in a way which alludes to the wireless activity LED. The point was discussed that the other LED is actually more semantically correct, but not as suitable as an icon.

Additionally, these [http://wiki.laptop.org/go/Image:School_server_and_ap.png alternate designs] were proposed, using antennae to make the purpose of the icons clearer. We may wish to elicit feedback about these alternatives from teachers and kids to see which convey the notion of wireless connectivity the best. The triangle proposed here was used once, and subsequently removed due to some distaste for the shape in this context, but it may still convey the idea better with the antenna. This change is strongly desired for 8.2.