<-BACK to Sugar Creation Kit
Sweets Distribution
- Annotated screen shots with Links
- Click on title ^ to go to topic
- Some ideas on how to present SWEETS. (Inkyfingers)
- look at Infrastructure for an overview.
- Click on title ^ to go to topic
- (Sweets Distribution is easier to use for Ubuntu' and its Derivatives (Adding an additional Repository to apt) as the packages are pre-configured, ready to use.)
- (Developed for Trisquel-sugar-Toast )
- Click on title ^ to go to topic
- (Advanced)
- Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo
- (This guide describes how to run Sugar using Sugar Packaging Management System, Sweets.)
- Request for better Documentation of installs
- Log of Installation of sugar-sweets 0.88 and 0.94 on f16-GNOME3-shell
- Installing_Sugar_via_sweets_-_in_Mint-12
- Installing_Sugar_via_sweets_-_in_Debian_testing_Wheezy
- (For developers)
- Click on title ^ to go to topic
- Collaboration support for Internet-less environments (but not only)
- Tests of which activities start by page
* The possibility to launch Base Software in heterogeneous
software and hardware environments.
* Using Base Software, provide access to various Content
(Sugar activities, artifacts created by Sugar activities, books, etc.)
created within the Sugar community.
* Using Base Software, provide collaborative functionality to
support Social activity around the Content.
* Instruments and workflows to adapt Content and Base Software
to specific needs that Sugar Deployment might face,
including extreme ones like off-line environments and restricting
hardware.
- [Sugar-devel] [SWEETS] Testing collaboration related fixes 05/07/2012
Hi all!
Following the plan for Harmonic Distribution v0.2 (which will be a basis
for Sugar Distribution to use in peruvian pilot), in Sugar Shell code
were made fixes that are intended to make Telepathy (everything related to
Neighbourhood view and Sugar Activities sharing/joining) more stable
(that was broken since global redesign started after 0.88 release).
Fixes are accessible from SweetsDistribution:Factory repository. Follow
regular Sweets Distribution installation instructions[1] to install
fixed Sugar Shell on all supported platforms[2].
Some visible changes in F1 view:
* the number of buddies should be increased from ~20 to 70-90
some Sugar versions (maybe 0.90-0.92) don't publish information about
nickname/colors on regular basis; this information are being stored on
disk for now
* for some buddies, server still don't have information about colors
(replaced by gray) and nick names (jabber ids)
If you have a time and want to help Puno deployment pilot, please,
consider possibility to install sweets-desktop from Factory repository
and do some testing of collaboration functionality.
Some tips:
* while interacting with another buddies, make sure that all
participants use Sweets Distribution (some F1 buddies might misbehave)
* the good criteria of stability level of new Sugar is comparing with
how collaboration happen in 0.88 Sugar.
Source code, for interested in people, can be found in top commits from:
* http://git.sugarlabs.org/desktop/sugar
* http://git.sugarlabs.org/desktop/sugar-toolkit
* http://git.sugarlabs.org/server/prosody-sugar
[1] Community/Distributions/Sweets_Distribution#Installation
[2] Platform_Team/Harmonic_Distribution/Supported_platforms
-- Aleksey
Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
- Advanced
- used to build non-live CD/DVD isos
Pungi needs to run on the arch it is composing, as root, and with an install of what it is composing, eg if you are composing Fedora 8, you need to be running Fedora 8.
This is so that the correct userland tools are used to create the images and such used by anaconda.
The eventual usage of pungi will most likely be in mock chroots to facilitate this.
It needs to run on the arch it is composing due to how anaconda-runtime determines what files to put in the boot images at this time.
Currently the releases of pungi are designed to run on an updated Rawhide system. Development of pungi always tracks Rawhide.
- Click on title ^ to go to topic
- (Very Advanced)
- Koji is the software that builds RPM packages for the Fedora project
- How_to_create_an_RPM_package in Fedora
- https://fedoraproject.org/wiki/How_to_create_an_RPM_package
- Click on title ^ to go to topic
- Advanced - Used by Sugar Developers
There is a git user named "pootle" that acts as the proxy by which all
PO file translations are committed from the Pootle server. Please
make pootle a committer on the repo and I will make the connections
between git and the Pootle server.
Some "best practices" about working with git and Pootle are described here.
Translation Team Best Practices
- Click on title ^ to go to topic
- "Groupthink is a library of self-sharing data structures written in python and shared over dbus.
- Together with the D-Bus Tubes provided by the Telepathy framework, this enables data structures to be shared over a network."
- Click on title ^ to go to topic
Dextrose uses olpc-os-builder, a tool create by OLPC to build official and customized system images.
The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose,
and fixes and enhancements waiting to be pushed upstream.
- Click on title ^ to go to topic
Manuals
- OLPC Manual
- Help Activity Refresh
- Manuals Info
