http://wiki.laptop.org/mediawiki/api.php?action=feedcontributions&user=119.111.124.194&feedformat=atomOLPC - User contributions [en]2024-03-29T13:03:27ZUser contributionsMediaWiki 1.31.7http://wiki.laptop.org/mediawiki/index.php?title=Original_Annotation_API_Proposal&diff=245327Original Annotation API Proposal2010-09-08T21:10:28Z<p>119.111.124.194: </p>
<hr />
<div>== Original API Proposal ==<br />
<br />
(Per discussion with Ian Bicking and Joshua Gay).<br />
<br />
A proposal for an Atom representation of an [[annotation]] based on the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php Atom syndication standard] [http://www.research-service.com/ research paper].<br />
<br />
Here's an example from that document:<br />
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<feed xmlns="http://www.w3.org/2005/Atom"><br />
<br />
<title>Example Feed</title> <br />
<link href="http://example.org/"/><br />
<updated>2003-12-13T18:30:02Z</updated><br />
<author> <br />
<name>John Doe</name><br />
</author> <br />
<id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id><br />
<br />
<entry><br />
<title>Atom-Powered Robots Run Amok</title><br />
<link href="http://example.org/2003/12/13/atom03"/><br />
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id><br />
<updated>2003-12-13T18:30:02Z</updated><br />
<summary>Some text.</summary><br />
</entry><br />
<br />
</feed><br />
<br />
An annotation is a single Atom entry:<br />
<br />
<entry<br />
xmlns:ann="http://wiki.laptop.org/go/Annotation"><br />
<title><!-- stupid title has to exist, but we don't have to actually <br />
put in text --></title><br />
<link href="{document being commented on}" /><br />
<id>urn:uuid:blahblahblah</id> <!-- ID for *this* entry --><br />
<updated>YYYY-MM-DDTHH:MM:DD</updated><br />
<source>{uri}</source><br />
<content type="html"><br />
Delete this term<br />
</content><br />
<category term="copyedit" scheme="http://laptop.org" /><br />
<category term="{tag}" scheme="?" /><br />
<ann:selected-text>Some text that was highlighted</ann:selected-text><br />
<ann:pointer>/html[1]/body[1]/div[2]</ann:pointer> <!-- page-wide comments and annotations would not have a pointer --><br />
<author><br />
<uri>{open ID URI}</uri><br />
</author><br />
</entry><br />
<br />
Entries can be posted with the Atom Publishing Protocol [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-14.html another IETF standard].<br />
<br />
This is based on a APP Collection. This is some base URI, e.g.,:<br />
<br />
http://localhost/APP/<br />
<br />
You POST to this URI with this entry as the content body. The server will respond with a Location header that indicates where the entry has been placed. This value will be put into the <code>&lt;source&gt;</code> tag, indicating where the entry is now stored. Later updates to the comment are done by PUTting to this URI, with the new entry. Removing the comment is done by DELETE'ing the URI.<br />
<br />
When you do <code>GET /APP/</code> you will get an Atom feed. This is basically a set of entries enclosed in a <code>&lt;feed&gt;</code> element.<br />
<br />
When you load a page, you would load any comment feeds in which you have indicated interest. This would happen asynchronously -- locally-hosted or cached comments will come up quickly, but potentially other comments would come up more slowly. This also involves fetching data from other domains, which is currently barred in Javascript with XMLHttpRequest; we'll have to create an exception to the permissions.<br />
<br />
=== Threading Comments ===<br />
<br />
Annotations can have comments; effectively annotations on the annotation. This can be done using the [http://www.ietf.org/rfc/rfc4685.txt in-reply-to extension]. Lets say you leave a comment on the previous example entry, you'd have:<br />
<br />
<entry<br />
xmlns:ann="http://wiki.laptop.org/go/Annotation"<br />
xmlns:thr="http://purl.org/syndication/thread/1.0"><br />
<title></title><br />
<link href="{source uri from other entry; or to original document?}" /><br />
<id>urn:uuid:04f9820d03</id> <!-- ID for *this* entry --><br />
<thr:in-reply-to ref="urn:uuid:blahblahblah"<br />
href="{source uri from other entry}"<br />
type="application/atom+xml" /><br />
<updated>YYYY-MM-DDTHH:MM:DD</updated><br />
<content type="html"><br />
This annotation is dumb.<br />
</content><br />
<author><br />
<uri>{open ID URI}</uri><br />
</author><br />
</entry><br />
<br />
=== Redundancy and Threading ===<br />
<br />
If an annotation is attached to another annotation that isn't available (maybe it hasn't been uploaded, maybe it's been deleted, maybe it's private, etc), then the tree-like threading of the comments starts to fall apart. To make this more reparable, some redundant information will be included in the Atom entry. A link to the most-parent document will be retained through all entries. In the case of an annotation that is attached to a specific piece of text, that text will also be copied. Then the UI may place the orphaned comment someplace appropriate. The orphaned comment should still ''look'' lost -- it's not in its proper context, and ideally it would be moved or deleted or edited to make it more appropriate.<br />
<br />
=== hAtom ===<br />
<br />
[http://microformats.org/wiki/hatom hAtom] is a [[Microformat]] for putting Atom entries in HTML. We may way to represent the inline comments using this, mostly to provide a satisfying sense of symmetry in what is displayed, serialized, and created by the annotation process. But not all kinds of annotations will fit into this.<br />
<br />
=== Pointers ===<br />
<br />
While annotations can be made on pages (URLs), they can also be made on ''parts'' of a page. There will be a variety of ways of indicating the point at which the comment applies.<br />
<br />
For PDF documents, a combination of page and coordinates can be used. For HTML an XPath document can be used. For images in HTML an XPath plus coordinates could be used. The format can be extended if there are other useful ways of indicating positions -- for example, a link between two locations.<br />
<br />
<br />
[[Category:Annotation]]</div>119.111.124.194http://wiki.laptop.org/mediawiki/index.php?title=Editor_Musical&diff=237690Editor Musical2010-06-21T03:52:09Z<p>119.111.124.194: /* Source Codes e Projetos em Desenvolvimento */</p>
<hr />
<div>{{Translations}}<br />
{{Olpcboxtop|toptext=[[{{PAGENAME}}|Editor Musical]]}}<br />
{{ OBX activity |[[Image:Activity-musical.png]]|extra|Status demo v1.3}}<br />
{{ OBX source other|[http://code.google.com/p/editor-musical/downloads/list code.google.com]|SVN}}<br />
{{ OBX pot }}<br />
{{ OBX team |[[NATE-LSI]]}}<br />
<small>see more [[:Category:OBX templates|templates]] or [[OBX proposals|propose new]]</small><br />
{{Olpcboxbottom}}<br />
<br />
== Download da Versão de Demonstração ==<br />
<br />
Faça o download em http://code.google.com/p/editor-musical/downloads/list<br />
<br />
Depois de descompactar o arquivo, acesse a pasta "MusicalEditor.activity" e leia o arquivo README que esclarecerá suas dúvidas.<br />
<br />
== O Aplicativo ==<br />
<br />
O Editor Musical é um software que permite aprendizagem e composição de música de maneira fácil.<br />
<br />
Ele está sendo desenvolido por uma equipe formada pelo [[LSI]] (Laboratório de Sistemas Integráveis).<br />
<br />
O LSI é um Laboratório da Escola Politécnica da USP (Universidade de São Paulo) que, entre outras atividades, tem desenvolvido aplicativos para apoiar a educação e criou em 2006 equipes responsáveis por migrar softwares educionais feitos em [[Java]] para a linguagem de programação padrão do OLPC: [[Python_pt]].<br />
<br />
Um destes aplicativos é o Editor Musical:<br />
<br />
== Interface Gráfica ==<br />
[[Image:MusicalEditor.jpg|700px|Editor Musical]]<br />
<br />
== Características ==<br />
<br />
*Programa de fácil manejo<br />
<br />
*Quantidade de instrumentos por composição definida pelo usuário<br />
<br />
*Até o momento o modo de composição é único (modo grade), mas é provável que novos modos integrem o aplicativo<br />
<br />
*Cada instrumento pertence a um conjunto (por exemplo, instrumento de cordas), e cada conjunto tem uma cor específica.<br>Assim, o usuário pode assimilar a cor da composição com o tipo de instrumento usado. Logo, ele vai perceber qual o papel de instrumentos de cordas, instrumentos de percussão etc. nas músicas<br />
<br />
*O aplicativo roda em modo monousuário e multiusuário (ou colaborativo) que usará a rede mesh<br />
<br />
*Tenta-se implementar um modo que permita ao usuário gravar som da entrada de microfone do OLPC<br />
<br />
<br />
<br />
= NATE-LSI =<br />
== Links Relacionados ==<br />
. [[LSI]]<br><br />
. [[FACIL]]<br><br />
. [[Editor Musical]]<br><br />
. [[Oficina de Desenho]]<br><br />
- [[LíNGUO]]<br><br />
- [[Quebra-Cabeca Musical]]<br><br />
- [[Jogo do Piano]]<br><br />
- [[Quimera]]<br />
<br />
== Source Codes e Projetos em Desenvolvimento ==<br />
- [http://code.google.com/p/facilhtml Fácil] <br><br />
- [http://code.google.com/p/editor-musical Editor Musical][http://www.college-paper.org/custom-term-paper.html TermPaper] <br><br />
- [http://code.google.com/p/oficina Oficina de Desenho Colaborativa]<br><br />
- [http://code.google.com/p/qcmusical/ Quebra Cabeça Musical]<br><br />
- [http://code.google.com/p/jogodopiano Jogo do Piano]<br><br />
<br />
<br />
<br />
[[Category:Software ideas]]<br />
[[Category:OLPC Brazil]]<br />
[[Category:Music]]<br />
{{Activity page<br />
|icon=Image:Activity-musical.png<br />
|genre=Media, Audio, and Video Players<br />
|short description=The Musical Editor is a musical software that allows children to learn how to develop their own compositions. <br />
|contact person=NATE-LSI<br />
|activity source=http://code.google.com/p/editor-musical/downloads/list<br />
|devel status=4. Beta<br />
|language=Portuguese<br />
}}<br />
{{Activity bundle<br />
|bundle URL=http://editor-musical.googlecode.com/files/MusicalEditor.activity-1-3.tar.gz<br />
|activity version=1.3<br />
}}</div>119.111.124.194http://wiki.laptop.org/mediawiki/index.php?title=Editor_Musical&diff=237689Editor Musical2010-06-21T03:51:18Z<p>119.111.124.194: /* Source Codes e Projetos em Desenvolvimento */</p>
<hr />
<div>{{Translations}}<br />
{{Olpcboxtop|toptext=[[{{PAGENAME}}|Editor Musical]]}}<br />
{{ OBX activity |[[Image:Activity-musical.png]]|extra|Status demo v1.3}}<br />
{{ OBX source other|[http://code.google.com/p/editor-musical/downloads/list code.google.com]|SVN}}<br />
{{ OBX pot }}<br />
{{ OBX team |[[NATE-LSI]]}}<br />
<small>see more [[:Category:OBX templates|templates]] or [[OBX proposals|propose new]]</small><br />
{{Olpcboxbottom}}<br />
<br />
== Download da Versão de Demonstração ==<br />
<br />
Faça o download em http://code.google.com/p/editor-musical/downloads/list<br />
<br />
Depois de descompactar o arquivo, acesse a pasta "MusicalEditor.activity" e leia o arquivo README que esclarecerá suas dúvidas.<br />
<br />
== O Aplicativo ==<br />
<br />
O Editor Musical é um software que permite aprendizagem e composição de música de maneira fácil.<br />
<br />
Ele está sendo desenvolido por uma equipe formada pelo [[LSI]] (Laboratório de Sistemas Integráveis).<br />
<br />
O LSI é um Laboratório da Escola Politécnica da USP (Universidade de São Paulo) que, entre outras atividades, tem desenvolvido aplicativos para apoiar a educação e criou em 2006 equipes responsáveis por migrar softwares educionais feitos em [[Java]] para a linguagem de programação padrão do OLPC: [[Python_pt]].<br />
<br />
Um destes aplicativos é o Editor Musical:<br />
<br />
== Interface Gráfica ==<br />
[[Image:MusicalEditor.jpg|700px|Editor Musical]]<br />
<br />
== Características ==<br />
<br />
*Programa de fácil manejo<br />
<br />
*Quantidade de instrumentos por composição definida pelo usuário<br />
<br />
*Até o momento o modo de composição é único (modo grade), mas é provável que novos modos integrem o aplicativo<br />
<br />
*Cada instrumento pertence a um conjunto (por exemplo, instrumento de cordas), e cada conjunto tem uma cor específica.<br>Assim, o usuário pode assimilar a cor da composição com o tipo de instrumento usado. Logo, ele vai perceber qual o papel de instrumentos de cordas, instrumentos de percussão etc. nas músicas<br />
<br />
*O aplicativo roda em modo monousuário e multiusuário (ou colaborativo) que usará a rede mesh<br />
<br />
*Tenta-se implementar um modo que permita ao usuário gravar som da entrada de microfone do OLPC<br />
<br />
<br />
<br />
= NATE-LSI =<br />
== Links Relacionados ==<br />
. [[LSI]]<br><br />
. [[FACIL]]<br><br />
. [[Editor Musical]]<br><br />
. [[Oficina de Desenho]]<br><br />
- [[LíNGUO]]<br><br />
- [[Quebra-Cabeca Musical]]<br><br />
- [[Jogo do Piano]]<br><br />
- [[Quimera]]<br />
<br />
== Source Codes e Projetos em Desenvolvimento ==<br />
- [http://code.google.com/p/facilhtml Fácil] <br><br />
- [http://code.google.com/p/editor-musical Editor Musical][http://www.college-paper.org/custom-term-paper.html TermPaper<br><br />
- [http://code.google.com/p/oficina Oficina de Desenho Colaborativa]<br><br />
- [http://code.google.com/p/qcmusical/ Quebra Cabeça Musical]<br><br />
- [http://code.google.com/p/jogodopiano Jogo do Piano]<br><br />
<br />
<br />
<br />
[[Category:Software ideas]]<br />
[[Category:OLPC Brazil]]<br />
[[Category:Music]]<br />
{{Activity page<br />
|icon=Image:Activity-musical.png<br />
|genre=Media, Audio, and Video Players<br />
|short description=The Musical Editor is a musical software that allows children to learn how to develop their own compositions. <br />
|contact person=NATE-LSI<br />
|activity source=http://code.google.com/p/editor-musical/downloads/list<br />
|devel status=4. Beta<br />
|language=Portuguese<br />
}}<br />
{{Activity bundle<br />
|bundle URL=http://editor-musical.googlecode.com/files/MusicalEditor.activity-1-3.tar.gz<br />
|activity version=1.3<br />
}}</div>119.111.124.194http://wiki.laptop.org/mediawiki/index.php?title=Sugar&diff=224503Sugar2009-11-19T08:04:59Z<p>119.111.124.194: /* Learning More */</p>
<hr />
<div>__NOTOC__<br />
{{OLPC}}<br />
<br />
Development of future versions of Sugar takes place at [http://WWW.sugarlabs.org Sugar Labs]. The OLPC [[Release notes/8.2.0]] contains version 0.82.1 of Sugar.<br />
<br />
<div style="float:right"><br />
__TOC__<br />
</div><br />
Sugar is the core of the [[OLPC Human Interface Guidelines|OLPC Human Interface]]. Its goal is to turn the Laptop into a fun, easy to use, social experience that promotes sharing and learning. <br />
<br />
[[Image:Sugar.png|350px|thumb|none|Sugar running on Fedora]]<br />
[[Image:Neighborhood.jpg|200px]][[Image:Home.jpg|200px]][[Image:Web1200.png|200px]]<br />
<br />
==Getting Sugar==<br />
Sugar is available:<br />
<br />
; on the [[XO]] laptop<br />
: If you have an XO-1, it's running Sugar. Read [[Upgrading the XO]] to update to the latest version.<br />
<br />
; as [[OS images]]<br />
: You can install or upgrade an XO to a new OS image. You can also run a Sugar image using [[:Category:Emulation|emulation]] on almost any operating system, including Windows.<br />
<br />
; as Live CDs<br />
: You can download a [[LiveCD]] <tt>.iso</tt> file and burn it to a CD, and then boot and run it on almost any x86 PC, including x86 Macintosh.<br />
<br />
; as packages for other Linux distributions<br />
: You can [[:Category:Installing Sugar|install Sugar from packages]] on other Linux distributions (Fedora, Debian, Ubuntu, etc.) using [[yum]] or apt-get, and run Sugar as an alternative UI.<br />
<br />
; as runnable source code for developers on Linux<br />
: Developers on Linux can install from the latest source code using [[Sugar with sugar-jhbuild]].<br />
<br />
Once you get [[Sugar]] running, take a picture of your desktop or laptop running Sugar, and leave a thumbnail and note in the relevant Talk page (the "discussion" tab) about what build you used and how it worked.<br />
<br />
==Getting started==<br />
<br />
You can explore the Sugar interface in our [http://laptop.org/8.2.0/manual/ Getting Started guide].<br />
There are other [[Getting started]] resources.<br />
<br />
Note the "Frame key" [[Image:Key_frame.jpg|40px]] at the top-right corner of your [http://laptop.org/en/laptop/start/keyboard.shtml keyboard],<br />
which toggles the presence of the Frame on and off the screen. (The Frame<br />
is the black border around the screen that holds the activity taskbar,<br />
clipboard, buddy list, etc.)<br />
<br />
You can restart Sugar by pressing the Ctrl-Alt-Erase (im sorry but what's the erase key?) keys simultaneously.<br />
<br />
==Develop==<br />
<br />
Developers, once you've installed Sugar, you can go on to develop for the environment.<br />
<br />
===Exploring Sugar===<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Building the XO: Introducing Sugar - Red Hat Magazine 2007-02-23]<br />
* [[Sugar_with_sugar-jhbuild|Build]] from sources<br />
* Read the human interaction [[HIG|guidelines]]<br />
* Get an overview of the [[Sugar Architecture|architecture]]<br />
* [[Sugar_Activity_Tutorial|Write]] your own activity<br />
* Check out the library of [[Sugar Code Snippets]]<br />
* [[Understanding sugar code]] organization.<br />
* See a list of Sugar [[Activities|activities]] and specifications.<br />
* [http://dev.laptop.org/git?p=sugar;a=summary Sugar source repository]<br />
* [http://dev.laptop.org/query?status=new&status=assigned&status=reopened&group=component&order=priority Current trac tickets, sorted by category]. The TODO list.<br />
* [http://dev.laptop.org/roadmap Roadmap]<br />
<br />
=== Learning More ===<br />
*[[Creating an Activity]], ''General information about how to create an activity''.<br />
*[[Activity tutorial]], ''Technical information about how to create an activity''<br />
*[[Activity bundles]], ''Technical information abot how to package an activity''<br />
*[[Sugar Activity Builder]], ''General Script to make a Sugar's activity skeleton''<br />
*[[Hacking Sugar]], ''Tips and tricks''<br />
<br />
===Contribute===<br />
<br />
* Go to our [http://join.sugarlabs.org Getting Involved] page.<br />
* Subscribe to the [http://lists.sugarlabs.org/listinfo/sugar-devel mailing list] (here are [http://lists.sugarlabs.org/pipermail/sugar-devel/ its archives])<br />
* Join the [irc://irc.freenode.net/sugar IRC channel]<br />
* Give Sugar some [http://bugs.sugarlabs.org/query?status=new&status=assigned&status=reopened&order=priority love]!<br />
* Test and report [http://bugs.sugarlabs.org/newticket issues]<br />
<br />
[[Category:Sugar]]<br />
[[Category:Developers]]<br />
[[Category:Subsystems]]</div>119.111.124.194http://wiki.laptop.org/mediawiki/index.php?title=Sugar&diff=224502Sugar2009-11-19T08:03:34Z<p>119.111.124.194: /* Learning More */</p>
<hr />
<div>__NOTOC__<br />
{{OLPC}}<br />
<br />
Development of future versions of Sugar takes place at [http://WWW.sugarlabs.org Sugar Labs]. The OLPC [[Release notes/8.2.0]] contains version 0.82.1 of Sugar.<br />
<br />
<div style="float:right"><br />
__TOC__<br />
</div><br />
Sugar is the core of the [[OLPC Human Interface Guidelines|OLPC Human Interface]]. Its goal is to turn the Laptop into a fun, easy to use, social experience that promotes sharing and learning. <br />
<br />
[[Image:Sugar.png|350px|thumb|none|Sugar running on Fedora]]<br />
[[Image:Neighborhood.jpg|200px]][[Image:Home.jpg|200px]][[Image:Web1200.png|200px]]<br />
<br />
==Getting Sugar==<br />
Sugar is available:<br />
<br />
; on the [[XO]] laptop<br />
: If you have an XO-1, it's running Sugar. Read [[Upgrading the XO]] to update to the latest version.<br />
<br />
; as [[OS images]]<br />
: You can install or upgrade an XO to a new OS image. You can also run a Sugar image using [[:Category:Emulation|emulation]] on almost any operating system, including Windows.<br />
<br />
; as Live CDs<br />
: You can download a [[LiveCD]] <tt>.iso</tt> file and burn it to a CD, and then boot and run it on almost any x86 PC, including x86 Macintosh.<br />
<br />
; as packages for other Linux distributions<br />
: You can [[:Category:Installing Sugar|install Sugar from packages]] on other Linux distributions (Fedora, Debian, Ubuntu, etc.) using [[yum]] or apt-get, and run Sugar as an alternative UI.<br />
<br />
; as runnable source code for developers on Linux<br />
: Developers on Linux can install from the latest source code using [[Sugar with sugar-jhbuild]].<br />
<br />
Once you get [[Sugar]] running, take a picture of your desktop or laptop running Sugar, and leave a thumbnail and note in the relevant Talk page (the "discussion" tab) about what build you used and how it worked.<br />
<br />
==Getting started==<br />
<br />
You can explore the Sugar interface in our [http://laptop.org/8.2.0/manual/ Getting Started guide].<br />
There are other [[Getting started]] resources.<br />
<br />
Note the "Frame key" [[Image:Key_frame.jpg|40px]] at the top-right corner of your [http://laptop.org/en/laptop/start/keyboard.shtml keyboard],<br />
which toggles the presence of the Frame on and off the screen. (The Frame<br />
is the black border around the screen that holds the activity taskbar,<br />
clipboard, buddy list, etc.)<br />
<br />
You can restart Sugar by pressing the Ctrl-Alt-Erase (im sorry but what's the erase key?) keys simultaneously.<br />
<br />
==Develop==<br />
<br />
Developers, once you've installed Sugar, you can go on to develop for the environment.<br />
<br />
===Exploring Sugar===<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Building the XO: Introducing Sugar - Red Hat Magazine 2007-02-23]<br />
* [[Sugar_with_sugar-jhbuild|Build]] from sources<br />
* Read the human interaction [[HIG|guidelines]]<br />
* Get an overview of the [[Sugar Architecture|architecture]]<br />
* [[Sugar_Activity_Tutorial|Write]] your own activity<br />
* Check out the library of [[Sugar Code Snippets]]<br />
* [[Understanding sugar code]] organization.<br />
* See a list of Sugar [[Activities|activities]] and specifications.<br />
* [http://dev.laptop.org/git?p=sugar;a=summary Sugar source repository]<br />
* [http://dev.laptop.org/query?status=new&status=assigned&status=reopened&group=component&order=priority Current trac tickets, sorted by category]. The TODO list.<br />
* [http://dev.laptop.org/roadmap Roadmap]<br />
<br />
=== Learning More ===<br />
*[[Creating an Activity]], ''General information about how to create an activity''.<br />
*[[Activity tutorial]], ''Technical information about how to create an activity''<br />
*[http://www.term-paper-research.com/custom-research-paper.html Research Papers], ''Additional information how to improve writing activity''<br />
*[[Activity bundles]], ''Technical information abot how to package an activity''<br />
*[[Sugar Activity Builder]], ''General Script to make a Sugar's activity skeleton''<br />
*[[Hacking Sugar]], ''Tips and tricks''<br />
<br />
===Contribute===<br />
<br />
* Go to our [http://join.sugarlabs.org Getting Involved] page.<br />
* Subscribe to the [http://lists.sugarlabs.org/listinfo/sugar-devel mailing list] (here are [http://lists.sugarlabs.org/pipermail/sugar-devel/ its archives])<br />
* Join the [irc://irc.freenode.net/sugar IRC channel]<br />
* Give Sugar some [http://bugs.sugarlabs.org/query?status=new&status=assigned&status=reopened&order=priority love]!<br />
* Test and report [http://bugs.sugarlabs.org/newticket issues]<br />
<br />
[[Category:Sugar]]<br />
[[Category:Developers]]<br />
[[Category:Subsystems]]</div>119.111.124.194