Sugar Labs - User contributions [en]

User:TimClicks/Testing Manual

2010-10-29T20:05:12Z

TimClicks:

Purpose

This document is designed to support new Sugar Labs and OLPC testers. It provides a look into why we do what we do, how to do what we do as well as well as how to see the results.

Sections

* Introduction
** OLPC Foundation
** Sugar Labs
* XO
** Turning it on
** Reflashing it
* Sugar
** How Sugar is put together, looking from the outside
** How Sugar is put together, looking from the inside
** How the Journal works
** How activities are built
* Testing Tips
** Building a sense of discovery
** Finding debugging logs

Links

Reflashing XO http://wiki.laptop.org/go/OS_images

User:TimClicks/Testing Manual

2010-10-29T19:17:19Z

TimClicks: Created page with "Purpose This document is designed to support new Sugar Labs and OLPC testers. It provides a look into why we do what we do, how to do what we do as well as well as how to see th..."

Activity Team

2010-10-09T06:04:58Z

TimClicks: /* General overview of git */ Anish Mangal explains the [http://lists.sugarlabs.org/archive/sugar-devel/2010-October/027633.html git workflow] on the Sugar development mailing list

<noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude>

==Mission==

{{:Activity Team/Mission}}

==Tips for Activity Developers==

=== Ask your 'newbie' question on-line ===

Join [http://en.wikipedia.org/wiki/IRC IRC] channel [irc://irc.freenode.net/sugar-newbies #sugar-newbies] (e.g. via [http://webchat.freenode.net/?randomnick=1&prompt=1&channels=sugar-newbies web client]) and ask your question about activity, or sugar core, development process. Also browse chat [http://meeting.sugarlabs.org/sugar-newbies logs].

=== Creating a new activity ===

See [[Activity Team/Resources|Activity Team Resources]].

=== Problems logging in to Gitorious? ===

Gitorious users are sometimes having their IP addresses incorrectly blacklisted by OSU-OSL, the organization that hosts git.sugarlabs.org. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing support@ouosl.org.

This has happened to a number of activity authors and we are working on getting it resolved.

===Move an activity===

We need help moving activities over to Sugar Labs from OLPC's servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How_to_migrate_from_OLPC]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

===Cross-platform compatibility===

As Sugar is integrated into more distros and the hardware base expands, it is important to keep Activity developers informed of any issues they need be aware of. For example, when Sugar was only expected to run on the XO-1 laptop, it was safe to assume that the display was always 1200x900.

The [[Activity Team/Compatibility Tips|Compatibility Tips]] page is a place to accumulate tips.

===Modify Activities===

A guide has been written describing how to make simple modifications to popular Sugar activities. Examples include adding sounds to TamTam, blocks to TurtleArt, buttons to Calculate, etc.

*[[Activity_Team/Modifying_an_Activity]]

===General overview of git===

Once you have [[Activity Team/How_to_migrate_from_OLPC|migrated]] your project, you may have some of [[Activity Team/Git FAQ|questions regarding how Sugar Labs uses git]].

Additional background on git can be found at these locations:

* [[Activity Team/Git FAQ|Sugar Labs git FAQ]]
* [http://book.git-scm.com/ Git Community Book]
* John Wiegley has written an overview of git: [http://ftp.newartisans.com/pub/git.from.bottom.up.pdf Git from the bottom up].
* Charles Duran from Harvard has written a lovely overview of git at [http://www.eecs.harvard.edu/~cduan/technical/git/ Understanding Git Conceptually].
* GNOME maintains a [http://www.gnome.org/~federico/misc/git-cheat-sheet.txt list of references to git for mortals].
* [http://progit.org/book/ Pro Git] by Scott Chacon
* [http://www.gitcasts.com/ Gitcasts]
* Anish Mangal explains the [http://lists.sugarlabs.org/archive/sugar-devel/2010-October/027633.html git workflow] on the Sugar development mailing list

== Testers ==

Please see the [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information.

== Background information ==

=== Sugar Activities ===

There is an [[Activities]] page where we highlight Sugar activities in the wiki. (We need to discuss how best to manage the content of this page as well as how to manage the activity-specific sub-pages.)

===Sugar [[Human Interface Guidelines]]===

The [[Human_Interface_Guidelines|Sugar Human Interface Guidelines]] content has also been migrated to Sugar Labs. This guide is a critical resource when designing activities.
: An [[Activity Team/Project Ideas#Activity HIG|Activity HIG]] discussion

===Sugar Almanac===

The [[Development Team/Almanac|Sugar Almanac]] content has been migrated to Sugar Labs. It's a great, quick reference when building python Activities.

===activities.sugarlabs.org===

The [http://activities.sugarlabs.org Sugar Activity Library] is our user-facing portal for Sugar activities. The site uses the back-end Mozilla built for Firefox and Thunderbird extensions at addons.mozilla.org, called Remora. To help out, check out [[Activity Library]].

===sugar-widgets library===

See [[Development Team/sugar-port]].

===sugar-sprites library===

See [[Activity Team/Sugar-sprites]]

== Misc. ==

=== Activity Team users on activities.sugarlabs.org ===

Fake emails to identify users:
* ''activity.team@sugarlabs.org'' activities that are supported by Activity Team
* ''trash@dev.null'' activities to remove

===setup.py===

There is a handy utility that is a standard part of Sugar Activity bundles, setup.py. You should use it to create and update POT files, generate a MANIFEST file and update locale files, and create .xo and .tar files for distribution.

./setup.py genpot
./setup.py fix_manifest
./setup.py dist_xo
./setup.py dist_source

===Packaging activities discussion===

We are currently discussing how to package activities in the future, in order to support all distributions. Please add your comments to the following pages.
* [[Activity Team/Packaging|Packaging]]
** should we remove "Activities" section from that page; all issues where moved to Activity_Status page [[User:Alsroot|alsroot]] 10:33, 16 January 2009 (UTC)
* [[Activity Team/Packaging Ideas|Packaging ideas]]

=== The Sugar Control Panel ===

While not strictly in the realm of Activities, it may be useful on occasion to add a section to the Sugar Control Panel. [[Activity Team/Control Panel|Things to keep in mind]].

=== A typical update cycle ===

Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:
# make a clone (anyone)
# make your changes (anyone)
# mail your patch to sugar_devel (anyone)
# make changes as per suggestions by the project maintainer and developer community (anyone)
# push your changes (anyone)
# request a merge (anyone)
# write release notes (anyone)
# tag the new version in git (project maintainer)
# create the .xo and .tar files (project maintainer)
# upload .tar to download.sugarlabs.org (project maintainer)
# upload .xo to activities.sugarlabs.org (project maintainer)
# update wiki documentation (anyone)

==[[Activity Team/Project Ideas|Project Ideas]]==

The Activity Team always needs project ideas and suggestions. Post your ideas to [[Activity Team/Project Ideas]].

If you see something here you would like to help with, please [[Activity Team/Contacts|contact us]].

[[User:Wade|Wade]] 17:19, 13 January 2009 (UTC)

==Additional resources==

Additional resources may be found [[Activity_Team/Resources|here]].

==Meetings==

Please check [[/Meetings]] for meeting schedules/logs.

== Subpages ==
{{Special:PrefixIndex/{{PAGENAME}}/}}

[[Category:Activity Team]]
[[Category:Team]]

0.90/Testing

2010-10-08T09:53:59Z

TimClicks: fixed broken link: https://wiki.ubuntu.com/Sugar

<noinclude>{{TOCright}}
[[Category:Testing]]
</noinclude>

==Install testing environment==
===Fedora 14===

* {{Iframe|See this testing request for [[0.90/Testing|Sugar 0.90]] |http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg15705.html|900|700|1}}

* See also [[Community/Distributions/Fedora]].

===SoaS===

See [[Sugar on a Stick/Beta]].

Also see: [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations]

*Testing Suggestions for v4:[http://wiki.sugarlabs.org/go/Talk:0.90/Testing]

===Ubuntu 10.04 (Lucid Lynx)===

Follow instructions at the [http://wiki.ubuntu.com/Sugar Ubuntu wiki] to install the latest Sugar packages and keep them up-to-date.

==Testing plans==

=== Mesh network ===
* Flash at least two XOs with the latest version of Sugar and the latest version of NetworkManager.
==== Autoconnect ====
* connect to an Access Point on one machine and restart the machine
-> ''the machine does autoconnect with the AP''
* start the machine without having connected to an AP before
-> ''the machine should autoconnect to a mesh network''
==== Connect both machines to the same channel ====
-> ''the buddies should be present on the neighborhood view of the other machine''
==== Share an activity ====
-> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''

=== Ad-hoc network ===

[[File:Adhoc network Indicate population.png]]

Flash at least two XOs with the latest version of Sugar and the latest version of NetworkManager.
==== Autoconnect ====
* connect to an Access Point on one machine and restart the machine
---> ''the machine does autoconnect with the AP''
* start the machine without having connected to an AP before
---> ''the machine should autoconnect to Ad-hoc network 1''
* start machine A and connect to the Ad-hoc network 6, start machine B without having been connected to an AP before
---> ''machine B should autoconnect to the Ad-hoc network 6''
==== Connect both machines to the same channel ====
---> ''the buddies should be present on the neighborhood view of the other machine''

[[File:Adhoc network connected.png]]

==== Share an activity ====
---> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''
==== Population ====
The Ad-hoc icons in the neighborhood view do indicate whether the network is "populated" or not, whether it is used by more than one person. It does not indicate the number of people that are connected though. If the fill color of the Ad-hoc icon is set then there is at least one person listening.
* On machine A connect to an Ad-hoc network. Start machine B which has been connected to an access point before.
---> ''On machine B it should automatically connect to the access point and the icon representing the Ad-hoc network machine A is connected to should be colored, the fill color is set.''
* Shut down machine A.
---> ''after 10-15 minutes the icon representing the Ad-hoc network machine A is connected to should be uncolored, the fill color is NOT set. This is indicates that the network is not populated.''

=== Collaborate between XO-1.0 and XO-1.5 without infrastructure ===
The XO-1.5 and XO-1.0 will see adhoc networks in his neighborhood view, so it the XO-1.0 can connect to an adhoc network that has been created by a learner on the XO-1.5.
[[File:Adhoc network XO-1.png]]

===0.90 Features===
For instructions how to test the [[Features]] listed below please have a look at the section "How to test" of each Feature page. Please add yourself with your test result to the table of each Feature.

* '''Enhanced Gettext'''
[http://wiki.sugarlabs.org/go/Features/Enhanced_Gettext#How_To_Test Enhanced Gettext Testing plan] - Enhanced Gettext adds an extra search path for translation files for Sugar activities. This allows deployments to add and update activity translations independently of the release process.

Name, result, comments

Juan Pérez, no, none

* '''Allow the Sugar user to connect to 3G networks'''
[http://wiki.sugarlabs.org/go/Features/3G_Support#How_To_Test 3G Support Testing plan] - This Feature allows the Sugar user to connect to 3G networks using a device in the frame.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Works !! Comment
|-
| ''Jane Doe''
| ''yes'' || ''None''
|-
|}

* '''Font configuration'''
[http://wiki.sugarlabs.org/go/Features/Font_configuration#How_To_Test Font configuration] - Distributors/deployers can use a GConf preference to customize the Sugar font size.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Works !! Comment
|-
| ''Marko Marković''
| ''yes/no'' || ''None''
|-
|}

===Language Tests===
* Test your own native language (can be set using the Control Panel).
** is the 3G Feature listed in the section above fully translated?

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Language !! Works !! Comment
|-
| ''Max Mustermann''
| ''German'' || ''yes/no'' || ''None''
|-
|}

===Backwards compatibility tests===
* '''Migrate the Journal'''
Please verify that the Journal is migrated fine after an update. For example from 0.82 to 0.88.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Versions !! Works !! Comment
|-
| ''Pierre-Paul-Jacques''
| ''0.82-0.88'' || ''yes/no'' || ''None''
|-
|}

===Connectivity: Different internet connections===
You should test here if you can connect with a WEP and WPA/WPA2 network, if a wired connection is possible and the 3G connection test can be logged here, too.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Connectivity Type !! Works !! Comment
|-
| ''Pierre-Paul-Jacques''
| ''WEP'' || ''yes/no'' || ''None''
|-
|}

===Bug Fix testing===
For particular bugs you can indicate your test results in this section. This can be done by more than one person, just separate name and result by a column.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Bug !! Description !! Works? !! Tester !! Comment
|-
| {{Bug|1}} || ''Example'' || ''yes, no, yes'' || ''Walter Bender, Tomeu Vizoso, Gary C. Martin'' || ''None''
|-
| {{Bug|1358}} || Synchronize changes made to a Journal entry || ''yes/no'' || ''Name'' || ''None''
|-
| {{Bug|330}} || Several Access Points with the same essid || ''yes/no'' || ''Name'' || ''None''
|-
| {{Bug|1497}} || Name input screen is deactivable || ''yes/no'' || ''Name'' || ''None''
|-
| {{Bug|1602}} || Can't connect to WEP shared key networks || ''yes/no'' || ''Name'' || ''None''
|-
| {{Bug|1601}} || Intro screen doesn't unfreeze dcon || ''yes/no'' || ''Name'' || ''None''
|-
|}

==How to write a good bug report==
You should note the following in the bug report:
* the version you are using
* steps to reproduce

In most cases it is of interest to the developers to look at the Sugar logs. Instructions how to get the logs can be seen [http://wiki.sugarlabs.org/go/BugSquad/Get_Logs here].

==Meetings==
====Where====
Meetings are held online using IRC, [http://en.wikipedia.org/wiki/IRC Internet Relay Chat]. You can read here more how to use [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat | IRC]] to join the meeting. The meeting will be taking place on the channel #sugar on the irc.freenode.net server, irc://irc.freenode.net#sugar, or [http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=1 webchat client].
=== 01 March 2010 ===
'''When:''' 14:00 UTC (9 EST)
=== Testing Day February the 16th ===
This will be an asynchronous effort, hence "Testing day" :). However we will do two kickstart meetings. One at 14:00 UTC and one at 19:00 UTC. In these meetings we will give a short introduction to what to test and answer questions about how to get the image on a usb-key and of course how to gather the results.
==== When ====
* Kickoff-Meeting 1: 14:00 UTC
* Kickoff-Meeting 2: 19:00 UTC
==== Attendees ====
Are you planning to attend? Add your name and your expertise below!
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Tester !! Feature owner !! Coordinator !! Special skills
|-
! [[User:Erikos | Simon Schampijer]]
| yes || yes || yes
|-
! [[User:Sdz | Sebastian Dziallas]]
| yes || no || [[Sugar_on_a_Stick|soas]]
|-
! [[User:Rkabir | Ryan Kabir]]
| yes || no || no
|-
! [[User:Mchua|Mel chua]]
| yes || no || [http://blog.melchua.com/category/soas/ soas pilot] || community QA, SMW-based test case systems
|-
|[[User:Satyag|Satyaakam Goswami]] || yes ||no ||[http://translate.sugarlabs.org/hi/ Hindi Translation] || testing
|-
! [[User:garycmartin|Gary Martin]]
| yes || no || no
|}

[http://shell.sugarlabs.org/~erikos/soas-testing-day-13-02-10.iso Soas Testing day build] Very old see below:

==Current Testing image==

'''This is the http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ latest soas nightly build is f14(rawhide) sugar 0.88.1''' Presently broken (07/30/2010)

Sugar Network/Recipe Specification

2010-08-07T21:58:55Z

TimClicks: /* [Activity] */ '''icon''' = <icon-file-name-wo-suffix> => '''icon''' = <icon-file-name-without-suffix>

<noinclude>
{{TOCright}}
[[Category:Zero Sugar]]
</noinclude>

== Spec file sections ==

The 0sugar.info specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of Zero Sugar workflows, everything depends on the 0sugar.info spec file.

For activities, ''activity.info'', a deprecated spec file name, is supported.

=== [DEFAULT] ===

Common options. Options from this section will be accessible from all other sections. It may be useful to store options that are common for all sections.

'''import''' = <filename> [; ...]

Import another spec file. Makes sense only within the [DEFAULT] section itself.

=== Common options ===

Options that are common for all sections except [DEFAULT].

'''inherit''' = <section-name> [; ...]

Include options from another section.

'''merge''' = <section-name> [; ...]

The same behaviour as ''inherit'', but merges values for list type options, i.e., the final values will consist of the base-section values with addtional child-section values. List options are:

* category
* requires
* binding
* include
* exclude
* langs
* packaged

=== [Component] ===

This is a required section (but see also [[#Presets|presets]]). It describes the main recipe component.

'''slug''' = <package-slug>

The string used as identifier in cases like 0install feed urls or native package names. Only lower alphabetic, numeric, "+" or "-" symbols are allowed. Slug value should be at least two characters long and start with an alphanumeric character.

'''name''' = <package-name>

Package name, in free form, equals to ''slug'', by default.

'''summary''' = <one-line-description>

Short descriptive line.

'''description''' = <multi-line-description>

Long descriptive text. To wrap long text, all lines after the second, should start with spaces. This field is equal to ''summary'' by default.

'''license''' = <licence-name>

Package license. Short licence names from [http://fedoraproject.org/wiki/Licensing Fedora naming scheme] are welcome.

'''homepage''' = <url>

Packaged project home page.

'''icon''' = <icon-file-name>

Relative (from Zero Sugar based project) path to icon file.

'''category''' = <category> [; ...]

A classification for the package using values defined by [http://standards.freedesktop.org/menu-spec/latest/apa.html freedesktop.org menu specification].

'''age''' = <age-number>

Simple number that will be used as a major number for ''version'', see [[Activity Team/Zero Sugar/Packaging Guide#Versioning|versioning scheme]] for details.

'''version''' = <version-number>

Current version of the package using [http://0install.net/interface-spec.html#id4016582 0install version format]. If the ''age'' option was set, versioning is a bit [[Activity Team/Zero Sugar/Packaging Guide#Versioning|different]].

'''stability''' = <stability-level>

Stability level of current version. Values conform to [http://0install.net/interface-spec.html#id4016716 0install stability levels] and could be:
* insecure
* buggy
* developer
* testing
* stable

'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]

List of [[Activity Team/Zero Sugar/Packaging Guide#Package_names|dependencies]] that should exist before using the package.

'''binding''' = [prepend|append|replace] <variable-name> [<insert-text-to-prepend-variable-value>] [; ...]

The environment variables 0install should export to the process that uses this package. This makes sense only for multiple-activity-serving dependencies (like libraries), not for the activity itself.

'''main''' = <path-to-exec-file>

The relative path of an executable inside the implementation that should be executed by default when the package is run.

'''exec''' = <shell-command>

Instead of using an executable program from the ''main'' option, 0sugar can bundle a script to run an arbitrary shell command.

If a package has neither ''main'' nor ''exec'', then it cannot be executed. This typically means that the package is for a library.

'''include''' = <glob-pattern> [; ...]

[[Activity Team/Zero Sugar/Packaging Guide#Glob patterns|Glob pattern]] for files to include to the package. Path related patterns will be processed starting from [[#Predefined_options|%(DISTDIR)s/%(PREFIX)s]] directory. By default, all files are assumed.

'''exclude''' = <glob-pattern> [; ...]

Like ''include'' option but for excluding files from the package. In additional, various temporary files will be excluded like ''.bak'' or ''.pyc''.

'''langs''' = <lang-name> [; ...]
include[<lang-name>] = <glob-pattern> [; ...]
exclude[<lang-name>] = <glob-pattern> [; ...]

A special form of ''include''/''exclude'' options that are intended to create separate, per locale, (sub)packages. If language is mentioned in ''langs'' list but doesn't have ''include[]''/''exclude[]'' options, ''include''/''exclude'' will be used (in that case, using special [[#Predefined_options|LANG]] variable makes sense).

'''arch''' = <arch>

Makes sense only for binary (sub)packages, and can contain:
* ''all'' for noarch (by default)
* ''any'' for binaries to use the current architecture

=== [Buid] ===

How to build binaries. If package contains binary implementations, this section should be present to describe the building process.

'''NOTE''' The commands in this section will be executed, not only in the developer's environment, but also in the user's, if a proper binary wasn't found; so move all development-related commands, like autogen.sh, to the ''[Maintain]'' section.

'''requires''' = <dependency-name> [(=|>=|<) <version>] [; ...]

What [[Activity Team/Zero Sugar/Packaging Guide#Package_names|dependencies]] should be present before building the package from sources, in addition to ''requires'' values from the ''[Component]'' sections.

'''configure''' = <shell-command>

Shell command to configure sources before building, e.g, invoking the ''configure'' script in auto-tools-based projects. It is important to use [[#Predefined_options|predefined constants]], at least ''%(PREFIX)s'', during configuration to prepare valid Zero packages. If the source code does not require a configuration stage, this option could be omited.

'''make''' = <shell-command>

Shell command to make binaries from sources. If the source code does not require a making stage, this option could be omited.

'''install''' = <shell-command>

Shell command to place files that are ready for distribution into the ''%(DISTDIR)s'' directory.

=== [Source] ===

How to create sources tarball. Options make sense only in the package-developer's environment.

'''url''' = <url>

While packaging 3rd-party applications, url to download sources tarball.

'''patch''' = <path-to-patch> [patch-level] [; ...]

If ''source'' option is used, 3rd-party sources might be patched.

'''exec''' = <shell-command>

Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing ''exec'' shell command, 0sugar will pick up newly appeared tarball if it was created in package root directory.

'''include''' = <glob-pattern> [; ...]
'''exclude''' = <glob-pattern> [; ...]

If neither ''url'' nor ''exec'' options were used, all files will be bundled and these [[Activity Team/Zero Sugar/Packaging Guide#Glob patterns|glob patterns]] might be used to concretize selection.

'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]

The packages that should be present before creating sources tarball. For example, if the ''exec'' command generates .c files from .vala, the vala dependency should be mentioned in the ''requires'' option.

== Presets ==

Instead of component sections, special sections might be used. These sections extend the standard ''[Component]'' options, and might add special meaning to existing ones, see the description for each particular preset.

=== [Activity] ===

This preset should be present only for activities (or for applications that could be used also as Activities, e.g., GCompris is a regular application but could be launched in Sugar mode).

Preset uses the same options as ''[Component]'' with these additions:

'''activity_version'''

Option is deprecated, ''version'' should be used instead.

'''bundle_id''' = <bundle-id>

See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. Option will be deprecated after implementing 0sugar in glucose and switching to identifying activities by urls (like 0install feeds).

'''icon''' = <icon-file-name-without-suffix>

Behaviour from activity.info is supported (value should not have ".svg" suffix, and icon file could be found only in activity subdirectory) but deprecated. Regular ''icon'' behaviour from ''[Component]'' section should be used instead.

'''exec''' = <shell-command>

Sugar will pass additional [[Development_Team/Low-level_Activity_API#Command_Line_Arguments| command line arguments]] to this command.

'''mime_types''' = <mime-type> [; ...]

List of mime types supported by the activity. It's used when opening a file from the web or to present to the user a list of activities which can open a certain Journal object.

'''tags''' = <tag> [; ...]

Tags give more context in which to group the activity. This is used to allow users to find activities more easily in the Journal, the Home view, etc.

=== [Application] ===

If this preset exists, an executable file will be created for native packages to launch ''main'' program or ''exec'' script. The executable file will be named by the ''slug'' option value and placed in the ''/usr/bin'' directory.

=== [Package] ===

If this section is present, the recipe should be used only for defining native packages on http://refinery.sugarlabs.org.

Package section might define native package names only for particular repository for current OBS project. In that case subnames should be used:

[Package/<repository-name-glob>]

Options:

'''package''' = <native-package-name> [; ...]

Name of a package (binary package, for binary-based distributions) associated with the recipe. It is important to use real package name, for virtual packages, use ''provides'' option.

'''provides''' = <native-package-name> [; ...]

If ''package'' can be installed by virtual name.

'''devel''' = <native-package-name> [; ...]

Name of devel package (for binary-based distributions) associated with the recipe. It is important to use real package name, for virtual packages, use ''devel-provides'' option.

'''devel-provides''' = <native-package-name> [; ...]

If devel package can be installed by virtual name.

'''distro''' = <distro-name>

Name of distribution that current section is defining package names for. Supported values (case-sensitive):

* ''RPM'' for all RPM-based distributions,
* ''Debian'' for all Debian-based distributions,
* ''Gentoo'' for Gentoo distribution,
* ''Slack'' for Slackware distribution,
* ''Ports'' for FreeBSD Ports.

== Predefined options ==

Options defined within ''[Build]'' section:

* ''BUILDDIR'' where the build happens
* ''SRCDIR'' path to directory with sources; for a custom (via 0compile) build, ''BUILDDIR'' and ''SRCDIR'' are different, while building on OBS, they are the same
* ''DISTDIR'' temporary path to place installed files before bundling them
* ''PREFIX'' should be used as installation prefix path, e.g., for {{Code|./configure --prefix}}
* ''CFLAGS'' default gcc CFLAGS
* ''CXXFLAGS'' default gcc CXXFLAGS

In sections that contain ''langs'' option:

* ''LANG'' current language while building per language implementation

Also, during the ''0sugar build'' command invocation, ''0sugar'' exports the environment variables that should be used in ''exec'' options, for example, to implement a conditional build.

* ''ZSUGAR_<argument-in-upper-case>'' map ''0sugar'' long command line arguments
* ''SECTION_<section-name-in-upper-case>'' for every spec file section that will be processed

== Examples ==

=== Python activity ===

Python-based activity with standard Sugar Platform dependencies.

[Activity]
slug = cartoon-builder
name = Cartoon Builder
summary = Create your own cell-animation sequences
license = GPLv2+
homepage = http://wiki.sugarlabs.org/go/Activities/Cartoon_Builder
icon = activity/activity-cartoonbuilder.svg
category = Games;Education
version = 11.4.9-pre3
stability = testing
exec = sugar-activity activity.CartoonBuilderActivity

=== Python library ===

A python-based library that could be used as is, or as an activity dependency.

[Component]
slug = journal
summary = Hight level library to create your own Journal-like activity
license = GPLv3+
homepage = http://wiki.sugarlabs.org/go/Activity_Team/Services/Journal
version = 1
stability = testing
requires = toolkit/python
binding = PYTHONPATH

=== C-based library with Python binding ===

[DEFAULT]
slug = polyol
summary = Intermediate level GObject based libraries for Sugar
description = Polyol is a set of libraries that are written in Vala.
Libraries are intended to provide high-level C API to basic Sugar
features including Gtk based user interface. Applications that are
linked against Polyol, interact with sugar processes
(like shell, datastore, etc.) via DBus.
license = LGPLv3+
homepage = http://wiki.sugarlabs.org/go/Activity_Team/Polyol

age = 0
version = 1
stability = testing

[Component]
requires = glib; gconf; libgee >= 0.5; gtk+ >= 2.12; pango >= 1.20; librsvg
binding = LD_LIBRARY_PATH lib
PKG_CONFIG_PATH lib/pkgconfig
VAPIDIR share/vala/vapi
exclude = python/**
arch = any

[Component/python]
requires = python; pygtk; pycairo; %(slug)s
binding = PYTHONPATH python
include = python/**
arch = any

[Build]
requires = pkg-config; cmake; make; gcc-c
configure = cmake -D CMAKE_INSTALL_PREFIX=%(PREFIX)s
-D PYTHON_SITEDIR=%(PREFIX)s/python
-D COMPONENTS="collab;ds;env;gui;shell;toolkit"
-D BINDING=python
-D CMAKE_C_FLAGS:STRING="%(CFLAGS)s"
%(SRCDIR)s
make = make
install = make DESTDIR=%(DISTDIR)s install

Development Team/Code Review

2010-05-16T21:39:10Z

TimClicks: /* Proposal */ effected -> affected

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

= Introduction =
Because Sugar is an open source project, anyone can contribute to it and thus improve the learning experience of children all around the world.

Once you have fixed a bug or implemented a new feature, you can send it to the current maintainers of Sugar by following the code review process.

This process allows the maintainers to feel confident about taking the responsibility of delivering your code to children. This means applying it to the current code base, fixing any bugs that are later discovered in your code or as consequences of it, modifying your code to gain new features, assisting packagers, deployers and translators, etc.

It is strongly recommended that you read about the review process and [[Development Team/Code guidelines|Code guidelines]] before starting to code.

The process is composed by the following phases, explained below: preliminary discussion, proposal, discussion and acceptance.

= Phases =

== Preliminary discussion ==

Except when the patch will be trivial, it's a good idea to notify the maintainers that you are going to work on this issue and discuss possible approaches with them. This avoids duplicated work and will give you an idea of what is considered a good idea by the maintainers before you commit substantial work in the patch itself.

May be interesting as well to discuss with the broad community about the usefulness of any proposed new feature. This way the maintainers will feel more motivated to commit their own time so that your work gets included.

Plan your work together with the maintainer in such a way that code will be submitted in chunks of reasonable size, a good rule of thumb is in patches of below 2000 lines.

== Proposal ==

* Create your patch using the 'git format-patch' command. (<code>git format-patch HEAD^</code> will create a 00xx-blahblah.patch for every commit. So don't forget to git commit!!)
* If your patch addresses an issue which is not registered in [https://bugs.sugarlabs.org the Sugar Labs trac instance], please open a new ticket for it.
* Attach the patch to the ticket
* Alternatively, you can add a link pointing to a cloned tree. Make sure it contains only the changes you propose for review.
* Add the keyword 'r?' to call the attention of reviewers.
* Add a testcase in a ticket comment. 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.

If your patch is a new feature and reasonably big, you may prefer to submit it for review to the Sugar-devel [http://lists.sugarlabs.org/listinfo/sugar-devel mailing list]. If you do please add the 'r?' keyword to the ticket anyway and reference the mailing list thread.

In order to make it easy for the reviewer please:

* note which module is affected e.g., sugar, sugar-toolkit...
* note possible dependencies e.g. the patch is for sugar but depend on the current HEAD of sugar-toolkit which went in 5 seconds ago (see also separate section about external dependencies below)

== Discussion ==

Maintainers and peers of the Sugar modules periodically check the review queue in Trac. If a few days pass without comment since the patch was submitted, please ping the maintainer in IRC or in the mailing list. At times maintainers are very busy and will appreciate the ping, even if repeated.

The reviewer will read your patch, evaluate its impact to the existing code base and comment on it. The 'r?' keyword will be changed to 'r+' if the patch is accepted, to 'r!' if further information or action is requested from the submitter, or to 'r-' if the patch gets rejected.

See [[Development Team/Code guidelines|Code guidelines]] for common criteria for code in Sugar.

Once you have answered the questions and/or attached a new patch, set the 'r!' keyword back to 'r?'.

== Acceptance ==

Once your patch has received a 'r+', the reviewer will push your code to the repository. From now on your code is part of the Sugar code base and the community will maintain it for you.

== Commit ==
If you have commit access to the repositories you should read the [[Activity_Team/Git|commit guidelines]] as well before submitting your changes.

= Dependencies =

Dependencies need to be fulfilled on all platforms running Sugar (i.e., they need to be available at all and need to be installed which means occupying disk space), so think twice before introducing new ones. Please discuss them on [[Sugar Labs/Communication channels#Developer Lists|sugar-devel]] in advance and clearly state them in the ticket. It's a always a good idea to check whether sufficiently recent versions of your proposed dependencies are already packaged for all (stable releases of the) major distributions, on '''all''' of their (semi-)supported architectures (e.g., ARM and PowerPC). If not, start requesting them (at the distribution bug trackers) ASAP and also mention it on sugar-devel and the ticket.

[[Category:Development Team]]

Development Team/Jhbuild

2010-03-13T07:04:37Z

TimClicks: /* External links */ removed dead links

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

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr | Xephyr]] nested X window server.
Below are generic instructions on how to use jhbuild to get up and running with Sugar.

==Compatible platforms==

Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).

==Check distro-specific instructions==

Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:

* [[/Debian | Debian]]
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]).
* [[/Ubuntu | Ubuntu]]
* [[/Mandriva | Mandriva]]

Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.

==Some general advice==

Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.

If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Communication channels#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Communication channels#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.

==Prerequisites==
; python
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.
; git
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".
; svn
: A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code.

These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages.

==Check out sugar-jhbuild==

In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

::Make sure you are in the _user's_ home directory
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s

You'll know if it worked if you get something like this:
<pre>
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/
remote: Counting objects: 4688, done.
remote: Compressing objects: 100% (1998/1998), done.
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.
Resolving deltas: 100% (2759/2759), done.
</pre>

==Build sugar base system and its dependencies==

Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].

And now run it.
./sugar-jhbuild run sugar-emulator

If it doesn't run or you have other problems read on.

=== Dealing with dependencies ===

''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).

If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [https://bugs.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 in the [https://bugs.sugarlabs.org/ Sugar Labs bug tracker].

===Some tips===

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build without -n will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build -n -a --clean
./sugar-jhbuild run sugar-emulator

The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.

=== known issue with hulahop ===

* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.
::Question. How do you run autoconf to fix this problem?
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands

=== If build breaks after an update ===

The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].

== Run Sugar ==

This command launches the Sugar emulator in a nested X session:

./sugar-jhbuild run sugar-emulator

To exit the emulator, press Alt-Q.

To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).

Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.

The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running multiple instances ==
To run an additional instance of sugar, you can start the second instance in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run sugar-emulator

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/

== Run an individual activity ==

Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch ''bundle_name''

You will see debug output appearing in Terminal.

== Configure the mode and resolution of Sugar ==

You can make Sugar run fullscreen or specify a size (in pixels):

./sugar-jhbuild run sugar-emulator --fullscreen
./sugar-jhbuild run sugar-emulator --dimensions 1200x900

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

== From within Sugar ==
Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen

== Customize ==

To customize the build you can modify the configuration file named <code>sugar.jhbuildrc</code> or create a copy of it and pass <code>--file /path/to/your/new/config</code> to sugar-jhbuild.

=== Write access to the repositories ===

If you have write access to the repositories you can add this (if your login name happens to be marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

== Compiling using 2 or more CPU cores ==

Before running <code>./sugar-jhbuild build</code>, append this to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["MAKEFLAGS"] = "-j4 -l4"
</pre>

Adjust the numbers to be twice the number of CPU cores in your machine.

== Using ccache to speed up rebuilds ==

To speed up full rebuilds of sugar-jhbuild (i.e. running <code>./sugar-jhbuild build</code> after removing the <code>source</code> directory) you can use [http://ccache.samba.org/ ccache]. Install it and append the following to <code>sugar.jhbuildrc</code>:

<pre>
os.environ["CCACHE_DIR"] = os.path.join(os.path.dirname(__file__), "ccache")
os.environ["PATH"] = "/usr/lib/ccache:"+os.environ["PATH"]
</pre>

Adjust <code>/usr/lib/ccache</code> to the path used by your distribution and create the <code>ccache</code> directory (inside your <code>sugar-jhbuild</code> checkout).

==Useful Internal Links==
* [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]

==External links==

* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

Summer of Code/2010/Organization Application

2010-03-12T23:49:19Z

TimClicks: added actual application

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== 2010 Answers (Actual) ==

;Organization Name:
:Sugar Labs

;Description
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

;Home page:
:http://www.sugarlabs.org/

;Main Organization License:
:GNU General Public License

;Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, instead of a pure individual need of its developers. This means that explicit community-building programs like GSoC are especially important. Most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

:Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

;If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006<nowiki>:</nowiki> 3/6 for 3 out of 6 students passed in 2006.
: 2009: 5/5

;What is the URL for your ideas page?
:http://idea.sugarlabs.org/

;What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.
:http://lists.sugarlabs.org/listinfo/sugar-devel
:All community, including international, mailing lists are listed: http://wiki.sugarlabs.org/go/Mailing_Lists

;What is the main IRC channel for your organization?
:<nowiki>#</nowiki>sugar irc.freenode.net

;Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site.
:Please see http://wiki.sugarlabs.org/go/Summer_of_Code/Student_application_template. You are welcome to create a proposal page by copying the content to
http://wiki.sugarlabs.org/go/Summer_of_Code/2010/Your_proposal_name.

: '''About you'''
*What is your name?
*What is your email address?
*What is your Sugar Labs wiki username?
*What is your IRC nickname?
*What is your primary language? (We have mentors who speak multiple languages and can match you with
one of them if you'd prefer.)
*Where are you located, and what hours do you tend to work? (We also try to match mentors by general
time zone if possible.)
*Have you participated in an open-source project before? If so, please send us URLs to your profile
pages for those projects, or some other demonstration of the work that you have done in open-
source. If not, why do you want to work on an open-source project this summer?

:'''About your project'''
*What is the name of your project?
*Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
*What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
*Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

:'''You and the community'''

*If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
*Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
*What will you do if you get stuck on your project and your mentor isn't around?
*How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

:'''Miscellaneous'''
*What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
*Describe a great learning experience you had as a child.
*Is there anything else we should have asked you or anything else that we should know that might
make us like you or your project more?

;What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible:
:Core criteria
::Experience with code.
::Experience with supervision.
::Regularity of communication with community.

:Other criteria
::Alignment of experience with student projects.
::Languages spoken.
::Time-zone.

:All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.

;What is your plan for dealing with disappearing students?
:Mitigation:
::Make membership of the developer & community mailing lists part of the process to have a student proposal accepted.
::Make it clear that weekly feedback reports are required from students.
::Identify times of likely work stress where mentor may be unavailable, e.g. travel, at start.
::Conduct a weekly IRC meeting. Apologies to be sent in by email.

:Actions if student disappears without notice:
::Mentor contacts student.
::If no response within 48h, send warning email.
::Mentors discuss student project - attempt to identify any issues.
::Discussion w/ student to see if the team can
::If no response within 48h of second email, student is failed.

;What is your plan for dealing with disappearing mentors?
:Mitigation:
::Be clear on the expectations of 1-2h per week for all of the mentors.
::Use experienced & committed mentors.
:: Identify times of likely work stress where mentor may be unavailable, e.g. travel, at start.
:: Mentors are already sitting within #sugar and we have established strong personal relationships with each other.

:Actions if a mentor disappears without notice:
:: Student contacts GSoC coordinator.
:: If no response within 48h, send warning email.
:: Mentors discuss student project - attempt to identify any issues.
:: Discussion w/ student to see if the team can
:: If no response within 48h of second email, student is failed.

;What steps will you take to encourage students to interact with your project's community before, during and after the program?
:Project-led
:: Membership of community mailing list is part of the process to have a student proposal accepted.
:: We have an active set IRC channels, where the students are highly encouraged to lurk.

:Sugar Labs-led
:: Mentor or Sugar Labs administrator sends a welcome/introductory note to the community & developer lists.
:: Welcome the student to provide end-user support via IRC & support lists.
:: We encourage all of our developers to refine their writing skills so they can contribute to our wiki & documentation. While indirect, this is of great help to the community.

:After
:: The Sugar Labs team will acknolwedge students' contributions at the end with thank you notes, blog posts, and possibly invitations to present at various conferences.

;What will you do to ensure that your accepted students stick with the project after GSoC concludes?
:Remind them that their work is benefiting nearly 2 million children around the world. Most of these children are in the developing world.
:We are investigating whether GSoC students contribute into the 'trunk', rather than a specific GSoC branch. This will minimise the risk that the code will not be able to be integrated.
:We will ensure that code is the same standard of code review is undertaken for GSoC as other contributors. This way the GSoC students will know that their contributions are already of a high standard.
:We will offer students a report to be sent to the mailing lists of their contributions, blog posts & offering them opportunities to present at conferences if possible.

;Is there anything else you would like to tell the Google Summer of Code program administration team? :
:Thank You

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers (Proposed) ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.
:: Nicely worded. --[[User:TimClicks|TimClicks]] 04:26, 12 March 2010 (UTC)

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)
::Me too --[[User:TimClicks|TimClicks]] 04:25, 12 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===

;2010
:I'm willing to be the backup person but would welcome someone else taking this role. --[[User:Walter|Walter]] 14:18, 12 March 2010 (UTC)

===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===

;2009
:All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.

:List of mentors:
:name <gmail account name>
#Walter Bender <walter.bender>
#Jameson Quinn <Jameson.Quinn>
#Nirav Patel <nrpatel>
#Tomeu Vizoso <tomeu.vizoso>
#Bobby P <bobbypowers> nteon on IRC
#Sebastian Silva <sebastian at fuentelibre.org> (alternative: sebatustra)
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>

;2010

:List of mentors:
:name <gmail account name>
#Walter Bender <walter.bender>

===What is your plan for dealing with disappearing students?===

;2009
:We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.

;2010
:FWIW, we didn't have this problem in 2009, so perhaps our mechanisms for retention are robust. --[[User:Walter|Walter]] 14:19, 12 March 2010 (UTC)

===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

;2010
:We did lose one mentor last year but the safety net worked almost seamlessly. --[[User:Walter|Walter]] 14:20, 12 March 2010 (UTC)

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:26:02Z

TimClicks: /* Describe your organization. */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.
:: Nicely worded. --[[User:TimClicks|TimClicks]] 04:26, 12 March 2010 (UTC)

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)
::Me too --[[User:TimClicks|TimClicks]] 04:25, 12 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===

;2009
:All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.

:List of mentors:
:name <gmail account name>
#Walter Bender <walter.bender>
#Jameson Quinn <Jameson.Quinn>
#Nirav Patel <nrpatel>
#Tomeu Vizoso <tomeu.vizoso>
#Bobby P <bobbypowers> nteon on IRC
#Sebastian Silva <sebastian at fuentelibre.org> (alternative: sebatustra)
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>

===What is your plan for dealing with disappearing students?===

;2009
:We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.

===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:25:08Z

TimClicks: /* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)
::Me too --[[User:TimClicks|TimClicks]] 04:25, 12 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===

;2009
:All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.

:List of mentors:
:name <gmail account name>
#Walter Bender <walter.bender>
#Jameson Quinn <Jameson.Quinn>
#Nirav Patel <nrpatel>
#Tomeu Vizoso <tomeu.vizoso>
#Bobby P <bobbypowers> nteon on IRC
#Sebastian Silva <sebastian at fuentelibre.org> (alternative: sebatustra)
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>

===What is your plan for dealing with disappearing students?===

;2009
:We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.

===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:24:07Z

TimClicks: /* What criteria did you use to select these individuals as mentors? Please be as specific as possible. */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===

;2009
:All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.

:List of mentors:
:name <gmail account name>
#Walter Bender <walter.bender>
#Jameson Quinn <Jameson.Quinn>
#Nirav Patel <nrpatel>
#Tomeu Vizoso <tomeu.vizoso>
#Bobby P <bobbypowers> nteon on IRC
#Sebastian Silva <sebastian at fuentelibre.org> (alternative: sebatustra)
#Wade Brainerd <wadetb>
#Luis Gustavo Lira, BSc, MSc <lira.lg at pucp.edu.pe>
#Ben Lau <xbenlau>
#Sayamindu Dasgupta <sayamindu>
#Austin Appel <scorche15>

===What is your plan for dealing with disappearing students?===

;2009
:We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.

===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:23:12Z

TimClicks: /* What is your plan for dealing with disappearing students? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===

;2009
:We will set the expectation that students will not be out of communications for more than 60 hours (ie, the length of a weekend) without prior notification to their mentor. We'll also hold mandatory weekly meetings in IRC for all the students to report on progress made, problems encountered, and proposed next steps. If a student does disappear, their mentor will attempt to contact them through all reasonable means to see what happened.

===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:22:45Z

TimClicks: /* What is your plan for dealing with disappearing mentors? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===

;2009
:Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.

===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:22:25Z

TimClicks: /* What steps will you take to encourage students to interact with your project's community before, during and after the program? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===

;2009
:Many of our potential pool of students are already involved in the project, volunteering in a variety of roles, including support, documentation, etc. GSoC presents an opportunity for them to dedicate themselves full time for three months. Also relevant are the steps in the application (getting comments, providing a screenshot) and the Sugar pilot mentioned below.

===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:22:06Z

TimClicks: /* What will you do to ensure that your accepted students stick with the project after GSoC concludes? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===
;2009
:The best we can do is infect the students with enthusiasm for our project's goals. We will launch a Sugar pilot near each accepted project so that students can see immediate results and feedback from children and teachers using their work, thus investing them further in longer-term sustainability and getting their local communities involved as well.

Summer of Code/2010/Organization Application

2010-03-12T04:21:09Z

TimClicks: /* What is the URL for your ideas page? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

;2010 (Walter)
:Sugar Labs is the community organization behind the Sugar Learning Platform. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar is Free Software that offers a hardware- and distro-independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking. Sugar is used every school day in 25+ languages by almost 2,000,000 children in more than 40 countries. Sugar Labs is a member project of the Software Freedom Conservancy. Its volunteers are passionate about learning and the opportunities that Free Software can bring to education.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

::I think this is fine to reuse. --[[User:Walter|Walter]] 22:49, 11 March 2010 (UTC)

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

;2010 (Walter)
:We participated in GSoC in 2009. We had a team of 5 students who worked both one-on-one with their mentors and engaged in overall Sugar development community. Wwe were new to the program and a relatively unknown project at the time; nonetheless, we attracted some outstanding students, most of whom have stayed involved with the project.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; 2010 (Tim McNamara)
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:49:25Z

TimClicks: /* Does your organization have an application template you would like to see students use? If so, please provide it now. */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; Tim McNamara
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
; 2009
: [[Summer_of_Code/Student_application_template]]

===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:48:46Z

TimClicks: /* What is the main IRC channel for your organization? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; Tim McNamara
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:<nowiki>#sugar</nowiki> on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:48:07Z

TimClicks: /* What is the main IRC channel for your organization? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; Tim McNamara
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===

;2009
:#sugar on irc.freenode.net

===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:45:59Z

TimClicks: /* What is the main development mailing list for your organization? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; Tim McNamara
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===

;2009
:Sugar devel <sugar-devel@lists.sugarlabs.org>
:We also have a non-technical list at:
:It's An Education Project <iaep@lists.sugarlabs.org>
:GSOC students are encouraged to consider also subscribing to this list to better understand and discuss the educational issues surrounding Sugar.

===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:45:21Z

TimClicks: /* What is the URL for your ideas page? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
; Tim McNamara
: http://idea.sugarlabs.org/

; 2009
: http://wiki.sugarlabs.org/go/Development_Team/Project_Ideas

===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:41:43Z

TimClicks: /* Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===

;2009
:As mentioned in the previous question Sugar Labs only officially became a member project of the SFC in June 2008 and all previous Sugar projects were completed under the OLPC banner.

===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:40:49Z

TimClicks: /* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===

;2009
:Sugar is a community project. We hope to grow our community of developers through our participation in GSoC. In particular, we see GSoC as a good opportunity to tap into the interest we've had from university students who want to get involved with the project and see summer as a good chance to dedicate themselves full-time to doing something substantial with the community. The GSoC program also provides us with a useful impetus to examine our support structures and tools for new contributors, making us more able to welcome new open-source contributors to our project in the future.
:Also note that, unlike many open source projects, the "itch" that Sugar scratches is a social need, not an individual need of its developers. This means that explicit community-building programs like GSoC are especially important, as most developers will not become familiar with the software and comfortable contributing through day-to-day use.
:We also expect to get some tangible code from the student projects that will have a positive impact on our current and future deployments, including the pilots we'll be starting near students participating in GSoC this summer.

===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:40:03Z

TimClicks: /* Describe your organization. */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===

;2009
:Sugar Labs is the community organization behind the Sugar Learning Platform, a free and open-source software project. Sugar is the core component of a worldwide effort to provide every child with equal opportunity for a quality education. Originally developed for the One Laptop per Child XO-1 netbook and designed from the ground up especially for children, Sugar offers a hardware and distro independent alternative to traditional “office-desktop” software. Sugar Activities running on the Sugar Learning Platform promote collaborative learning and critical thinking, and are used every school day in 25 languages by almost 1,000,000 children in more than 40 countries.
:Sugar Labs, a volunteer, non-profit organization, is a member project of the Software Freedom Conservancy. The mission of Sugar Labs is to support the Sugar community of users and developers and establish regional, autonomous “Sugar Labs” around the world to tailor Sugar to local languages and curricula. Sugar Labs volunteers are passionate about providing education to children.

===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:37:50Z

TimClicks: /* Overview */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions! I've used the [[Summer_of_Code/SL_application | 2009 material]] as a starting point.

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:26:29Z

TimClicks: /* Answer Template */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions!

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.

;Author
:Here is my answer to that silly question.

This renders as:

;Author
:Here is my answer to that silly question.

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:25:37Z

TimClicks:

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions!

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answer Template ==

Please cite your answer using a definition list. This will make things easier when multiple suggestions for an question appear.
<nowiki>
;Author
:Here is my answer to that silly question.
</nowiki>

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:23:09Z

TimClicks: /* What license(s) does your project use? */

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions!

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

;Tim McNamara
:Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:22:11Z

TimClicks: /* What license(s) does your project use? */ Primarily GPL v2....

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions!

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===

Primarily GPL v2. Authors of sub-projects, which we call Activities, are entitled to develop in their own licence terms. Only Activities with open sourced licences are included as part of the Sugar Learning Platform.

===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:19:15Z

TimClicks:

== Overview ==

Sugar Labs needs to put its application together. We welcome all contributions!

== Likely Questions ==

Sourced from the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_app GSoC FAQ]:

#Describe your organization.
#Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
#Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
#If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
#What license(s) does your project use?
#What is the URL for your ideas page?
#What is the main development mailing list for your organization?
#What is the main IRC channel for your organization?
#Does your organization have an application template you would like to see students use? If so, please provide it now.
#Who will be your backup organization administrator?
#What criteria did you use to select these individuals as mentors? Please be as specific as possible.
#What is your plan for dealing with disappearing students?
#What is your plan for dealing with disappearing mentors?
#What steps will you take to encourage students to interact with your project's community before, during and after the program?
#What will you do to ensure that your accepted students stick with the project after GSoC concludes?

== Answers ==

===Describe your organization.===
===Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?===
===Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.===
===If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?===
===What license(s) does your project use?===
===What is the URL for your ideas page?===
===What is the main development mailing list for your organization?===
===What is the main IRC channel for your organization?===
===Does your organization have an application template you would like to see students use? If so, please provide it now.===
===Who will be your backup organization administrator?===
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
===What is your plan for dealing with disappearing students?===
===What is your plan for dealing with disappearing mentors?===
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
===What will you do to ensure that your accepted students stick with the project after GSoC concludes?===

Summer of Code/2010/Organization Application

2010-03-11T21:16:39Z

TimClicks:

2009-10-05T03:40:44Z

TimClicks: created

= PyCon 2009 =

== Event Details ==

For more information, go to the [http://nz.pycon.org KiwiPyCon 2009 website].

== Sugar Organizer ==

[[User:TimClicks | Tim McNamara]] will be organizing Sugar's presence at PyCon 2009.

== Attendees ==

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

# [[User:TimClicks | Tim McNamara]]
# Your name here!

== Lodging ==

More info as it becomes available.

== Schedule ==

More info as it becomes available.

[[Category:Event]]

User:TimClicks/Events/KiwiPyCon2009

2009-10-05T03:34:42Z

TimClicks: created

Development Team/Jhbuild

2009-10-02T04:33:04Z

TimClicks: /* Jhbuild FAQ */ formatting

<noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude>

Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.
Below are generic instructions on how to use jhbuild to get up and running with Sugar.

==Compatible platforms==

Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.

See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).

==Check distro-specific instructions==

Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:

* [[/Debian | Debian]]
* [[/Fedora | Fedora]]
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process].
* [[/Ubuntu | Ubuntu]]
* [[/Mandriva | Mandriva]]

==Some general advice==

Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.

If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.

==Jhbuild FAQ==
:Q:
::<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?
:A:
::<sdziallas> dgd: this can be caused by different packaging policies...
::<dgd> sdziallas, ergo not a reason for concern, thanks!

definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)

==Prerequisites==
; python
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.
; git
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name.
; svn
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.

These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.

==Check out sugar-jhbuild==

In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild

::Make sure you are in the _user's_ home directory
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s

You'll know if it worked if you get something like this:
<pre>
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/
remote: Counting objects: 4688, done.
remote: Compressing objects: 100% (1998/1998), done.
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.
Resolving deltas: 100% (2759/2759), done.
</pre>

==Build sugar base system and its dependencies==

Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.

cd sugar-jhbuild
./sugar-jhbuild update
./sugar-jhbuild depscheck
./sugar-jhbuild build
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process]. Before saying that [http://www.youtube.com/ Youtube] is unfriendly to Linux because of the flash player, try installing it. [http://get.adobe.com/flashplayer/ Adobe flash works] on my Ubuntu 9.04 and Fedora 11 without hitch.

And now run it.
./sugar-jhbuild run

If it doesn't run or you have other problems read on.
=== Dealing with dependencies ===

''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).

If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), 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 in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].

===Some tips and known issues===
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.
::Question. How do you run autoconf to fix this problem?
::: when you get asked because of the error, choose the configure stage

== Run Sugar ==

This command launches the Sugar emulator in a nested X session:

./sugar-jhbuild run

To exit the emulator, press Alt-Q.

To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).

Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.

The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running multiple instances ==
To run an additional instance of sugar, you can start the second instance in the following way:

SUGAR_PROFILE=2 ./sugar-jhbuild run

This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/

== Run an individual activity ==

Within sugar, e.g. in Terminal, this command launches an individual activity for testing:

sugar-launch ''bundle_name''

You will see debug output appearing in Terminal.

== Configure the mode and resolution of Sugar ==

You can make Sugar run fullscreen or specify a size (in pixels):

./sugar-jhbuild run sugar-emulator --fullscreen
./sugar-jhbuild run sugar-emulator --dimensions 1200x900

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

== Other commands ==

JHBuild has several other commands that can be useful for development. You can get an overview with:

./sugar-jhbuild --help-commands

A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)

./sugar-jhbuild update
./sugar-jhbuild build -a --clean
./sugar-jhbuild run

The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.

== If build breaks after an update ==

The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
./sugar-jhbuild depscheck
regularly and install the missing packages.

If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].

== From within Sugar ==
Once you have Sugar running, here are some useful commands:
*'''Alt+Shift+F''' makes the frame appear and disappear
*'''Ctrl-Q''' quits an activity
*'''Alt+Shift+Q''' quits Sugar
*'''Alt+Shift+O''' opens the search
*'''Alt+Shift+R''' rotates the screen

== Customize ==

To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.

=== Write access to the repositories ===

If you have write access to the repositories you can add this (if your login name happens to be marco):
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'

==Useful Internal Links==
* [[Development Team/Understanding the Code|Understanding Sugar Code]]
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]

==External links==

* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].

[[Category:Installing Sugar]]
[[Category:Jhbuild]]

Development Team

2009-10-01T21:40:29Z

TimClicks: /* Kill Bugs! */ - trac.sugarlabs.org + dev.sugarlabs.org

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>{{TOCright}}

==Mission==
{{:Development Team/Mission}}

== Meetings ==
The development team has a regular IRC meeting (See the Sugar Labs [[Sugar Labs#Calendar|calendar]]). Find out more about the meeting time and upcoming and earlier meetings [[Development Team/Meetings|here]]. Help: [[Sugar_Labs/Contacts#IRC.2C_Internet_Relay_Chat |Using IRC]]

== Mini tutorials ==
The development team hosts mini tutorials covering short (five-minute) topics relevant to writing Sugar activities. Please refer to the [[Development Team/Mini tutorials|Mini tutorials page]] to sign up for teaching a topic.

== Development systems ==
All of core Sugar development except system-dependent modifications can be done on a standard computer by compiling [[Development Team/Jhbuild|jhbuild]] and editing with your favorite editor (eclipse/pydev, emacs, vim, etc.). Activity (aka application) development can be done in many environments using pre-compiled [[Supported_systems#Sucrose|packages]] ("sucrose") or [[Supported_systems#Starch|images]] ("starch").

== Document your work ==
See [[Features/Feature Template]] for an example.

== Code review ==
Patches to Sugar are more than welcome. There are guidelines for [[Development Team/Code Review|code review]] to get them accepted.

== Package Sucrose for your distribution ==
* Currently there are efforts to maintain Sugar as part of [[Community/Distributions/Debian|Debian]], [[Community/Distributions/Ubuntu|Ubuntu]], and [[Community/Distributions/Fedora|Fedora]].
* Help us maintain good communication with distribution packagers to assist in this. Start a [[Packaging Team]].

== Kill Bugs! ==
* Help test. See [[{{Upcoming Stable Release}}/Testing]].
* See our bug tracking system http://dev.sugarlabs.org/.
* Join the [[BugSquad]].

== Project Ideas ==
* Want to work on an interesting Sugar project, or have an idea of your own? Check the [[Development Team/Project Ideas|project ideas]] page.
* Prepare a new Sugar [[Features/Policy|Feature]].
* See the [[Summer of Code]] and [[Sugar Summer Program]] efforts; ideas, students, mentors, and organization help are welcomed.
==Platform Release Cycles==

'''Sugar platform release''' version cycle: | [[0.82]] | [[0.84]] | [[0.86]] | [[0.88]] |

'''[[/Release/CurrentRelease/Sucrose]]'''

== Subpages ==
{{Special:PrefixIndex/Development Team/}}

[[Category:Development Team]]
[[Category:Team]]