Sugar Labs - User contributions [en]

Activity Library/Authors

2009-11-01T15:05:48Z

Cwhii: Fixed Activity Library link.

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
Activity authors can upload their Activities to the Sugar Labs Activity Library.

== Contributing your Activity ==

=== Developing your activity ===
For a guide on developing your own activity, please visit the [[Activity Team]].

=== Preparing your Activity ===
* Have a public system for reporting and managing bugs in your activity. This is an invaluable resource for us when we are reviewing your activity as it gives us information on any problems in your activity. We recommend using http://dev.sugarlabs.org .
* If possible, conduct a beta release cycle from your website every time you want to release a new version of your activity. Allow your current users to be involved, but be sure to warn them that the activity is in beta ;) Conducting a beta cycle will ensure your activity has less bugs and is of a higher quality when you release it and/or release new versions.
* Have a public forum for users to critique, comment on and discuss your activity. If this is not possible or impractical, create a page on [[Activities]] about your activity - this will group together any comments that users have about your activity and allow reviewers to gather information about your activity more speedily.
* If you are updating your activity, have a changelog. This will inform us what parts of the activity have changed and which parts we especially need to test and give extra scrutiny to.
* If any software is required for your activity, please state this in your submission.
* Only declare compatibility with Sugar versions and operating systems that you have tested with.
* Comply with [http://activities.sugarlabs.org/pages/policy Activity Policy]. They're only drafts at the moment, but we still enforce them.

=== Submiting your activity ===
* Once you have developed your activity(alpha and beta versions are welcome), create a [http://activities.sugarlabs.org/en-US/sugar/users/register Library Account].
* [[Activity_Library/Glossary#Submitted_activity|Submit]] your Activity to the [http://activities.sugarlabs.org/en-US/sugar/developers Activity Library].
* [[Activity_Library/Glossary#Completed_activity|Complete]] it.
* If your activity is in alpha or beta stage and you want other users test/review it for you, email to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@] mailing list with tag [ANNOUNCE] in subject field.

=== Making your activity Public ===
* If your activity is ready to be public, [[Activity_Library/Glossary#Nominated_activity|Nominate]] it. After that, your activity will pushed to review queue for Library Editors.
* Do not use Library Editors as beta testers and bug finders. This is not the purpose of editors. Please test the activity extensively before nominating to the public.
* After your activity is pushed to the public, notification email will be send to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@].

Each submission must be approved by an Editor or Administrator before it is listed on the site. Whether approved or denied, an email is sent to the authors. A comment is required if denied. If approved, the activity is moved to a directory so that it can be replicated across the sugarlabs.org mirrors.

The approval queue contains all of the submitted activities in a chronologic order, but the activities are not always handled in a [http://en.wikipedia.org/wiki/FIFO FIFO]/[http://en.wikipedia.org/wiki/LIFO LIFO] way. The reviewer just picks an activity and start reviewing.
Most activities are reviewed following the main procedure for reviewing activities:

# Install the activity (and restart the application if needed).
# Check if the application is still functioning as it should.
# Briefly ensure that the core functionality of the activity works.
# Check if the description and version notes are accurate.

Then the activity is approved or denied. If the activity is denied, the reviewer will include comments on why it was denied. Keep in mind that the reviewer try to thoroughly test your activity, but, like any other, they don't have an unlimited amount of time.

If you have questions about the procedure, you could join #sugar on irc.freenode.net. Information about how to get your activity reviewed faster can be found at: [[#How_to_Get_Your_Activity_Reviewed_Faster]].

=== Submit new activity version ===

* Upload new version, it will be pushed to review queue.
* After new version of your activity is pushed to the public, notification email will be send to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@].

== Activity Library Developer Pages ==

=== Welcome Page ===
Also known as the Developers Control Panel (or Developers CP), when you enter /developers/ you are prompted to login or create an account.

=== Main Page ===
Once you've logged in, you're presented with a brief overview of the activities you've submitted and links to submit more.

=== User Profile ===
Each user is able to edit their own profile. Here you specify your name, email, and personal website. By default, your email address is not listed on the end-user website. Administrators are also presented with the ability to manage the permissions level of the user.

A user can be designated as an Administrator, Editor (aka Moderator) or User (aka Developer).

=== User Manager ===
An administrator has a list of all users and their permissions. From this screen mass updates are available. There is also a link for creating a new user.

=== Listings ===
Available to administrators only, a list of every item can be shown. On the sidebar are links to the Activities List. This shows the name, description, and date last updated. The name is a link to edit each item.

[[Category:Activity Library]]

Talk:Sugar Labs/Getting Involved

2009-02-03T07:47:55Z

Cwhii: /* Questions */ Product content

== Questions ==
Is the content writer section referring to the wiki? [[User:cwhii|cwhii]]
:Yes, I saw this section yesterday and I'm fairly certain that was the intent. You'll notice that the associated teams are the Doc, Wiki, and Marketing teams. [[User:Ridderman|Ridderman]] 16:55, 7 December 2008 (UTC)

Then what about content that is to be included in the product rather than promotional and support content? [[User:cwhii]] 2-Feb-2009

== Suggestions ==
Gary -- this is some really nice work but there are a couple of things which would make it substantially better:
# Clicking on the images should take me to a nice description of the roles, not to the Image pages themselves.
:: Oh man, tell me about it. Wikis are designed for copyright reasons to make this as tough as possible on image content. The wiki needs extra plug-ins or custom hacks to make this work properly. I did get one working case after about 3hrs of testing, but it meant images would be hard linked (so the page would need to be manually updated if any get changed), and generate nasty 3 line URL mouse overs (on my browser at least). Best case I can think of is to convince someone to install the custom Image Map plug-in, which has a fair chance of working without breaking the table alignment. I notice fedora made a separate page on their regular web-site [http://fedoraproject.org/en/join-fedora] just to get this behaviour. --[[User:Garycmartin|Garycmartin]] 21:28, 21 January 2009 (UTC)
# Say I want to meet some people from role X. How do I do that?
:: Thanks, good idea, each team should list its members. Perhaps the semantic wiki plug-in is worth installing for this (Mel backed off asking for it re: test case content/results). Members should at least make a User wiki page for themselves, a little semantic wiki could then auto generate lists for each team where ever needed. --[[User:Garycmartin|Garycmartin]] 21:28, 21 January 2009 (UTC)
--[[User:Mstone|Michael Stone]] 19:18, 21 January 2009 (UTC)

Talk:Sugar Labs/Getting Involved

2009-02-03T07:44:09Z

Cwhii: /* Questions */

== Questions ==
Is the content writer section referring to the wiki? [[User:cwhii|cwhii]]
:Yes, I saw this section yesterday and I'm fairly certain that was the intent. You'll notice that the associated teams are the Doc, Wiki, and Marketing teams. [[User:Ridderman|Ridderman]] 16:55, 7 December 2008 (UTC)

== Suggestions ==
Gary -- this is some really nice work but there are a couple of things which would make it substantially better:
# Clicking on the images should take me to a nice description of the roles, not to the Image pages themselves.
:: Oh man, tell me about it. Wikis are designed for copyright reasons to make this as tough as possible on image content. The wiki needs extra plug-ins or custom hacks to make this work properly. I did get one working case after about 3hrs of testing, but it meant images would be hard linked (so the page would need to be manually updated if any get changed), and generate nasty 3 line URL mouse overs (on my browser at least). Best case I can think of is to convince someone to install the custom Image Map plug-in, which has a fair chance of working without breaking the table alignment. I notice fedora made a separate page on their regular web-site [http://fedoraproject.org/en/join-fedora] just to get this behaviour. --[[User:Garycmartin|Garycmartin]] 21:28, 21 January 2009 (UTC)
# Say I want to meet some people from role X. How do I do that?
:: Thanks, good idea, each team should list its members. Perhaps the semantic wiki plug-in is worth installing for this (Mel backed off asking for it re: test case content/results). Members should at least make a User wiki page for themselves, a little semantic wiki could then auto generate lists for each team where ever needed. --[[User:Garycmartin|Garycmartin]] 21:28, 21 January 2009 (UTC)
--[[User:Mstone|Michael Stone]] 19:18, 21 January 2009 (UTC)

Talk:Sugar Labs/Getting Involved

2008-12-07T02:00:04Z

Cwhii: Content writer for wiki?

Is the content writer section referring to the wiki? cwhii

Sugar System Stack (ASCII Text)

2008-12-03T23:26:37Z

Cwhii:

===Sugar Application Stack (ASCII Text)===

<pre>
------------------------------------------------------------------------------------------------
| Packaging | Layer | Contents |
------------+-----------+-----------+-----------+-----------------------------------------------
| | | | Sugar | Pre-installed | Turtle |
| | | | Library | From-the-web | Read Art |
| | | |Collections|Locally-created| Etoys |
|???????????+-----------+-----------+-----------+---------------| ... |
| | | Fructose | Sugar | | Write |
| | | | Activities| Browse | Record |
| | Sucrose |-----------+-----------+----------------------------------------------|
| | | Glucose | Sugar |sugar sugar-base sugar-toolkit etoys Journal |
| | | | Framework |presence-service sugar-datastore sugar-artwork|
| Starch |===========+===========+===========+==============================================|
| | | | Software | GNOME freedesktop Gtk+ dbus X Windows System |
| | | | Stack | matchbox gconf telepathy xulrunner abiword |
| | | | | squeak |
| | Ribose +-----------+-----------+----------------------------------------------|
| | | | Operating | Fedora Ubuntu | | Mac |MSWindows| |
| | | | System |Debian Other-Linux| LTSP| OSX | (QEMU) | ... |
| | | | | -Distributions| | | | |
|-----------+-----------+-----------+-----------+----------------------------------------------|
| | | | Hardware | OLPC | Asus | Intel | OLPC | |
| | | | Platform | XO-1 | EEE PC | Classmate | XO-2 | ... |
------------+-----------+-----------+------------+----------------------------------------------
</pre>

[[Sugar Application Stack]] Graphical view.

Sugar System Stack (ASCII Text)

2008-12-03T23:16:22Z

Cwhii: Sugar Application Stack (ASCII Text) - Added headings.

===Sugar Application Stack (ASCII Text)===

<pre>
|-----------------------------------------------------------------------------------------------
| Packaging | Layer | Contents |
|-----------+-----------+-----------+-----------+-----------------------------------------------
| | | | Sugar | Pre-installed | Turtle |
| | | | Library | From-the-web | Read Art |
| | | |Collections|Locally-created| Etoys |
|???????????+-----------+-----------+-----------+---------------| ... |
| | | Fructose | Sugar | | Write |
| | | | Activities| Browse | Record |
| | Sucrose |-----------+-----------+----------------------------------------------|
| | | Glucose | Sugar |sugar sugar-base sugar-toolkit etoys Journal |
| | | | Framework |presence-service sugar-datastore sugar-artwork|
| Starch |===========+===========+===========+==============================================|
| | | | Software | GNOME freedesktop Gtk+ dbus X Windows System |
| | | | Stack | matchbox gconf telepathy xulrunner abiword |
| | | | | squeak |
| | Ribose +-----------+-----------+----------------------------------------------|
| | | | Operating | Fedora Ubuntu | | Mac |MSWindows| |
| | | | System |Debian Other-Linux| LTSP| OSX | (QEMU) | ... |
| | | | | -Distributions| | | | |
|-----------+-----------+-----------+-----------+----------------------------------------------|
| | | | Hardware | OLPC | Asus | Intel | OLPC | |
| | | | Platform | XO-1 | EEE PC | Classmate | XO-2 | ... |
|-----------+-----------+-----------+------------+----------------------------------------------
</pre>

[[Sugar Application Stack]] Graphical view.

Sugar System Stack (ASCII Text)

2008-12-03T19:21:29Z

Cwhii: Sugar Application Stack (ASCII Text) - added Starch/Sucrose/Ribose/Fructose/Glucose.

===Sugar Application Stack (ASCII Text)===

<pre>
|-----------+-----------+-----------+-----------+-----------------------------------------------
| | | | Sugar | Pre-installed | Turtle |
| | | | Library | From-the-web | Read Art |
| | | |Collections|Locally-created| EToys |
|???????????+-----------+-----------+-----------+---------------| ... |
| | | Fructose | Sugar | | Write |
| | | | Activities| Browse | Record |
| | Sucrose |-----------+-----------+----------------------------------------------|
| | | Glucose | Sugar |sugar sugar-base sugar-toolkit etoys Journal |
| | | | Framework |presence-service sugar-datastore sugar-artwork|
| Starch |===========+===========+===========+==============================================|
| | | | Software | GNOME freedesktop Gtk+ dbus X Windows System |
| | | | Stack | matchbox gconf telepathy xulrunner abiword |
| | | | | squeak |
| | Ribose +-----------+-----------+----------------------------------------------|
| | | | Operating | Fedora Ubuntu | | Mac |MSWindows| |
| | | | System |Debian Other-Linux| LTSP| OSX | (QEMU) | ... |
| | | | | -Distributions| | | | |
|-----------+-----------+-----------+-----------+----------------------------------------------|
| | | | Hardware | OLPC | Asus | Intel | OLPC | |
| | | | Platform | XO-1 | EEE PC | Classmate | XO-2 | ... |
|-----------+-----------+-----------+------------+----------------------------------------------
</pre>

[[Sugar Application Stack]] Graphical view.

Sugar System Stack (ASCII Text)

2008-12-03T18:25:15Z

Cwhii: Software stack layer added.

===Sugar Application Stack (ASCII Text)===

<pre>
------------+-----------------------------------------------
| Sugar | Pre-installed | Turtle |
| Library | From-the-web | Read Art |
|Collections|Locally-created| EToys |
|-----------+---------------| ... |
| Sugar | | Write |
| Activities| Browse | Record |
|-----------+----------------------------------------------|
| Sugar |sugar sugar-base sugar-toolkit etoys Journal |
| Framework |presence-service sugar-datastore sugar-artwork|
|===========+==============================================|
| Software | GNOME freedesktop Gtk+ dbus X Windows System |
| Stack | matchbox gconf telepathy xulrunner abiword |
| | squeak |
|-----------+----------------------------------------------|
| Operating | Fedora Ubuntu | | Mac |MSWindows| |
| System |Debian Other-Linux| LTSP| OSX | (QEMU) | ... |
| | -Distributions| | | | |
|-----------+----------------------------------------------|
| Hardware | OLPC | Asus | Intel | OLPC | |
| Platform | XO-1 | EEE PC | Classmate | XO-2 | ... |
------------+-----------------------------------------------
</pre>

[[Sugar Application Stack]] Graphical view.

Sugar System Stack (ASCII Text)

2008-12-03T16:10:56Z

Cwhii: /* Sugar Application Stack (ASCII Text) */ Link to graphical version.

===Sugar Application Stack (ASCII Text)===

<pre>
------------+----------------------------------------------
| Library | Pre-installed | Turtle |
|Collections| From-the-web | Read Art |
| |Locally-created| EToys |
|-----------+---------------| ... |
| Sugar | | Write |
| Activities| Browse | Record |
------------+----------------------------------------------
|Application| Sugar |
| Framework | |
------------+----------------------------------------------
|Operating |Fedora Ubuntu | LTSP| Mac | MSWindows | |
| System | Debian Other | | OSX | (QEMU) | ... |
------------+----------------------------------------------
| Hardware | OLPC | Asus | Intel | OLPC | |
| Platform | XO-1 | EEE PC | Classmate | XO-2 | ... |
------------+----------------------------------------------
</pre>

[[Sugar Application Stack]] Graphical view.

Sugar System Stack (ASCII Text)

2008-12-03T16:07:40Z

Cwhii: Sugar Application Stack (ASCII Text) new.

2008-11-02T17:33:25Z

Cwhii: /* Project - Emle - Web Site */ Devlopment version links added.

{|style="float:right"
| {{User en}}
|}

==C.W.Holeman II==

 cwhii_cplo@Julian5Locals.com remove the fives
 http://JulianLocals.com/cwhii

==Emle - Electronic Mathematics Laboratory Equipment==

===Project Web Site===

Emle project web site is hosted by SourceForge.net.

'''Emle - Electronic Mathematics Laboratory Equipment Web Site'''
 http://emle.sourceforge.net/index.shtml

===Most Recent Release===

The most recently released version of the Emle application
is on the SourceForge.net Emle project web site.
It is a copy of it as it would be installed on Sugar from the collection bundle.

'''Emle V2.4-4 - Collection Index'''
 http://emle.sourceforge.net/emle020404/emle_menu.html

===Development Version===

Still-under-development version of the Emle application
is on the SourceForge.net cvs source code server.
It is a copy as would be installed on Sugar from the collection bundle.

'''Collection Index'''
 http://emle.cvs.sourceforge.net/viewvc/*checkout*/emle/emle/emle_index.html

'''Documentation Page'''
 http://emle.cvs.sourceforge.net/viewvc/*checkout*/emle/emle/dev/web_site.html

'''Developer Info'''
 http://emle.cvs.sourceforge.net/viewvc/*checkout*/emle/emle/dev/contribute_introduction.html

==Emle - Structure==

Emle is composed of a collection of:

*Labs

Each labs is composed of:

*Equipment
*Instructions

==Emle Tasks==

Emle has a prototype implementation.
To make it usable there are several tasks that need to be worked upon.

*The instructions and other text need to be translated.
*Labs need to be designed, implemented and instructions written.
*Additional equipment is needed to expand the possible labs that can be written.
*Code needs to be added in Javascript to support additional features as needed by the equipment.

Each level of the above tasks is ready to be addressed.
As the functionality of an existing level is exercised/stressed the lower levels will need to be expanded.
The labs and equipment are written in XML and the instructions are mainly XHTML.
Each of the lower levels require increasingly more technical skills.

==Emle Technologies==

HTML index page has a static index of languages and labs available.
The selected lab XML file is processed by XLST in the web browser using emle_lab.xsl and the specified language message file. The resulting page includes XHTML, SVG and Javascript which provides an interactive lab for the student.

User:Cwhii

2008-10-29T21:52:38Z

Cwhii: Moved from olpc

{|style="float:right"
| {{User en}}
|}

==C.W.Holeman II==

 cwhii_cplo@Julian5Locals.com remove the fives
 http://JulianLocals.com/cwhii

==Project - Emle - Web Site==

Electronic Mathematics Laboratory Equipment Web Site
 http://emle.sourceforge.net/index.shtml

Emle V2.4-4 - Index
 http://emle.sourceforge.net/emle020404/emle_menu.html

==Emle - Structure==

Emle is composed of a collection of:

*Labs

Each labs is composed of:

*Equipment
*Instructions

==Emle Tasks==

Emle has a prototype implementation.
To make it usable there are several tasks that need to be worked upon.

*The instructions and other text need to be translated.
*Labs need to be designed, implemented and instructions written.
*Additional equipment is needed to expand the possible labs that can be written.
*Code needs to be added in Javascript to support additional features as needed by the equipment.

Each level of the above tasks is ready to be addressed.
As the functionality of an existing level is exercised/stressed the lower levels will need to be expanded.
The labs and equipment are written in XML and the instructions are mainly XHTML.
Each of the lower levels require increasingly more technical skills.

==Emle Technologies==

HTML index page has a static index of languages and labs available.
The selected lab XML file is processed by XLST in the web browser using emle_lab.xsl and the specified language message file. The resulting page includes XHTML, SVG and Javascript which provides an interactive lab for the student.

User:Cwhii

2008-10-21T01:55:48Z

Cwhii: New.

http://emle.sf.net