Sugar Labs - User contributions [en]

Events/SugarCamp3

2014-03-17T22:36:02Z

ChristophD: bought my flights today

<noinclude>[[Category:Event]]</noinclude>
=== General information ===

Date: '''April 12-13, 2014'''

Location: '''Paris, France'''

For more information and a preliminary schedule please see http://olpc-france.org/sugarcamp/index.en.html

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-12
| not sure yet
|-
| Adam Holt
| Apr 10-13 (3 nights)
| Bastien's house?!
|}

Event venue: Cité des Sciences et de l'Industrie
30 Avenue Corentin Cariou
75019 Paris France

Accomodation options (sorted roughly from cheapest to nicest):
* to be done (look at the [[User:Bzg/SugarCamp|Sugar Camp 2011 page]] for some possible options)

=== Pre/Post event ===

''We have enough room for Sugar and OLPC hackers that would like to hack/talk on Friday & Monday before and after the event. Please register to the event and tell us if you want to participate to the Pre/Post event.''

Ideas for sessions (please add/edit):
* ...

Events/SugarCamp3

2014-03-12T11:42:23Z

ChristophD: created the page after exchange on IAEP

=== General information ===

Date: April 12-13, 2014
Location: Paris, France

For more information and a preliminary schedule please see http://olpc-france.org/sugarcamp/index.en.html

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-12 (still need to book my flights)
| not sure yet
|}

Event venue: Cité des Sciences et de l'Industrie
30 Avenue Corentin Cariou
75019 Paris France

Accomodation options (sorted roughly from cheapest to nicest):
* to be done (look at the [[User:Bzg/SugarCamp|Sugar Camp 2011 page]] for some possible options)

=== Pre/Post event ===

''We have enough room for Sugar and OLPC hackers that would like to hack/talk on Friday & Monday before and after the event. Please register to the event and tell us if you want to participate to the Pre/Post event.''

Ideas for sessions (please add/edit):
* ...

Sugarcamp SF 2012

2012-10-24T17:38:57Z

ChristophD: added links for photos

SugarCamp++ will be Mon Oct 22 to Wed Oct 24 in San Francisco (business hours especially) immediately following [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html OLPC SF's global community summit].

Presenting an opportunity for all to begin real hacking & implementation of the tech/learning/organizational ideas exchanged over the weekend summit

Please join & help strengthen collaborative global education! Inspired by the rapidly-approaching [http://lists.sugarlabs.org/archive/iaep/2012-August/015452.html dream of Sugar 1.0] and the [http://www.olpcnews.com/laptops/xo-4/olpc_xo_4_will_provide_significant_performance_boost.html XO-4].

We strongly welcome new participants. Read up on [http://planet.sugarlabs.org ongoing] [http://planet.laptop.org projects], think about [mailto:volunteer@laptop.org volunteering] with [http://www.sugarlabs.org Sugar Labs] and [http://one.laptop.org OLPC], open your imagination to what open-learning-for-all might become -- and [http://olpcMAP.net put yourself on the map] :)

 
http://olpcSF.org/sites/default/files/u8/red_xo_in_sf_fog_2012.jpg

= Photos =

* From Adam Holt: http://www.flickr.com/photos/tiayiti/
* From Mike Lee: http://www.flickr.com/photos/curiouslee/
* From Mark Battley: http://www.flickr.com/photos/ntugigroup/

= Topics =

Please add project topics below if you will give them legs :)

* [http://cananian.livejournal.com/66654.html XOrduino], Curricular Arcs, Streamlined Teacher Training
* [http://lists.laptop.org/pipermail/server-devel/2012-August/006126.html School Server] [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc Community Edition] (hassle-free [http://ChildrensLibrary.org ICDL], Yes We [http://khanAcademy.org Khan], lessons learned from Oct 19-21 demo classroom @ SFSU? etc)
* [http://lists.sugarlabs.org/archive/sugar-devel/2012-August/thread.html#38829 Sugar 0.98 & 1.0 and what lies beyond] (vs Windows 8 releasing Fri Oct 26 ;)
* Hackers Without Borders, Feedback from Small/Medium-sized Deployments, [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 NewCo], [http://wiki.laptop.org/go/ALEARN_Network ALEARN]
* Documentation within Sugar; Video Tutorials; Books/Histories of OLPC/Sugar
* Power Infrastructure: developing countries' schools need what??
* Translating [http://google.com/search?q=olpc+butia Butía] construction instructions from Spanish to English (Christoph)
* Sensors... build, test, create lesson ideas (STEM, SET, and SCIB), maybe video tutorials of how-to make? KISS! (Caryl)

= Attendees =

Please add your name if you will come & contribute to the future of Sugar/OLPC or similar -- include 2 words about your preferred project:

* [http://twitter.com/adborden Aaron Borden]? OLPC SF
* Adam Gordon, Toronto/[http://ntugigroup.org Kenya] (Oct 19-22)
* Adam Holt, Boston (Oct 17-25)
* Alex Kleider, SF - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* Aleksey Lim, Russia (Oct 19-24?)
* Anish Mangal, UMichigan, former Dextrose Project Manager (Oct 17-21)
* Anna Schoolfield, Birmingham Alabama (Oct 19-24?)
* [http://lumiere.ens.fr/~guerry/ Bastien Guerry?] Paris - XS Community Edition? (Oct 19? 21-23?)
* [http://codewiz.org Bernie Innocenti], Boston - Google, Sugar Labs founder (Oct 19-28)
* Bert Freudenberg, Germany - Etoys (Oct 19-21)
* Bill Stelzer, US Virgin Islands (Oct 18-27)
* Caryl Bigenho, Los Angeles area - Teacher & [http://wiki.laptop.org/go/Contributors_program Contributors Program] mentor (Oct 19-24)(Robots, Sensors, XS)
* Christoph Derndorfer, Vienna - OLPC News Editor (in SF Oct 17-25)
* Cherry Withers? San Jose CA | Philippines
* Christine Murakami? Ohio - [http://csgolpc2012.weebly.com Columbus School for Girls]
* Claudia Urrea? Boston | Colombia - OLPC [http://one.laptop.org/about/people/claudia-urrea Director of Learning] (Oct 21-23)
* [http://twitter.com/craigperue Craig Perue] - Jamaica Ministry of Education (Curricular Arcs, Project Mgmt, Oct 19-21)
* CScott Ananian? Boston - [http://cananian.livejournal.com XOrduino?] [http://lists.sugarlabs.org/archive/iaep/2012-September/015518.html Arduino?]
* Dafydd Harries - alum of Collabora Ltd (Oct 16-23)
* Daniel Drake, Nicaragua (Oct 18-24)
* David Farning, Wisconsin - [http://activitycentral.com Activity Central] founder (Oct 19-24?)
* David Jessup? Florida - OLPC/Liberty City [http://one.laptop.org/about/people/david-jessup-jr Project Manager] (Oct 19-22?)
* Ed Bigenho, Los Angeles area-Volunteer "helper" (Oct 19-24)(Robots, sensors)
* Gary Martin? Scotland
* George Hunt, NYC - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition] (Oct 19-24)
* Giulia D'Amico, Miami - OLPC [http://one.laptop.org/about/people/giulia-damico VP of Business Development] (Oct 19-21?)
* Grant Bowman - [http://olpcSF.org OLPC SF]
* Janissa Balcomb - [http://olpc2010-lesotho.blogspot.com/ Lesotho] (Oct 19-23)
* Jennifer Martino - [http://www.olpccanada.com/blog/ OLPC Canada] [http://twitter.com/olpccanada Director] (Oct 18-22)
* Jerry Vonau? Winnipeg - [http://www.laptop.org.au/ OLPC Australia], [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* John Watlington, Boston - OLPC VP of Hardware Engineering (Oct 20-22)
* Jonathan Ooms, Global Literacy Foundation
* Kevin Gordon, Toronto | [http://ntugigroup.org Kenya] (Oct 18-22)
* Luke Faraone, DC/Boston (Oct 19? 21-22?)
* Marina Zdobnova, LA/Russia (Oct 19-24?)
* Mark Battley, Toronto | [http://ntugigroup.org Kenya] - Curricular Arcs (Oct 16-25)
* Mary Lou Jepsen? Taiwan - [http://pixelqi.com/ Pixel Qi]
* Matt Keller, Connecticut | Ethiopia - [http://www.technologyreview.com/view/429206/emtech-preview-another-way-to-think-about/ OLPC Literacy Project] (Oct 19-21)
* Mitch Seaton, Philippines (eKindling) | Australia | Denmark (Oct 18-26)
* Mike Lee, DC - Tablets, [http://youtu.be/VuOvwJAwA0U XOrduino, XO Stick], Scratch, Etoys, [http://proyectojuanchacon.blogspot.com/2012/09/sugarlabs-dc-is-back.html SugarLabs DC], [http://olpcLearningClub.org OLPC Learning Club], [http://bib.archive.org/ Books in Browsers] (Oct 19-23/26)
* Nancie Severs, New Hampshire/Thailand/Vietnam - [http://wiki.laptop.org/go/Contributors_program Contributors Program] coordinator (Oct 17/18-22)
* Nick Doiron? SF - Code For America (Oct 19-22)
* Richard M.Batna, Montreal (Oct 18-23)
* Richard Smith? Boston - [http://lists.laptop.org/listinfo/power power electronics], OLPC [http://one.laptop.org/about/people/richard-smith Director of Embedded Engineering]
* Rod Weis, Global Literacy Foundation
* Ruben Rodriguez? Spain - Activity Central CTO
* Sameer Verma - [http://olpcSF.org OLPC SF] Chief Organizer
* Sarah Naguib? [http://laptopsforegypt.wordpress.com Ohio | Egypt]
* Simon Schampijer? Berlin
* SJ Klein? Boston - [http://meta.wikimedia.org/wiki/Trustees Wikipedia Board], [http://dp.la Digital Public Library of America] (Oct 20-21)
* Tanja Kohn, Austria (in SF October 16 - 26 early morning)
* Tim Falconer, Pennsylvania (Oct 19-22?)
* Tony Anderson, Rwanda - Karma Learning System, XS Community Edition? (Oct 19-24)
* Walter Bender, Boston - [[Oversight Board|Sugar Labs Executive Director]] (Oct 21-24)
* Yoshiki Ohshima? Los Angeles

= Registration =

Be sure to add your name to the "Attendees" list above, with a couple words about your interests, and also write to holt @ laptop.org confirming there's still room!

Both rooms below will be free (thanks to the amazing generosity of SF State University's College of Business) with reliable Wifi included -- lunch/dinner is available for individual purchase downstairs at the large Food Court.

Note the preceding weekend's [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html Oct 19-21 Community Summit] itself (structured talks/demos/panels etc, you don't want to miss, [https://www.eventbrite.com/event/4025544512 please register now!]) costs $25 to $40/person to pay for facilities rental, great community shirts, supplies etc. A price that would indeed be an order of magnitude higher if it weren't for the astonishing volunteer efforts of the http://olpcSF.org community :)

= Location =

In 2 modern classrooms, Oct 22-24 (Mon to Wed), 8AM to 5PM:

San Francisco State University
Rooms 667 & 668
835 Market St, 6th Floor (go downtown, NOT main campus)
San Francisco, CA 94103

= Evening Excitement =

Nearby pubs will be well-used too! (And restaurants, and large food court below SFSU/downtown)
 
* [http://twitter.com/AfricaHackTrip AfricaHackTrip] Drink-up, Wednesday Oct 17, 6:30PM @ Showdown saloon (happy hour!) 10 6th Street, San Francisco: http://www.meetup.com/AfricaHackTrip/events/85351052/
* Reception @ SFSU/Downtown [http://olpcSF.org/summit Friday Oct 19, 5:00PM]. [https://www.eventbrite.com/event/4025544512 Please Register Now] for the summit if you haven't!
* Party in Bolinas Sunday Oct 21, 6PM (1hr from SF, across Golden Gate). Rental vehicles will be arranged in person during the weekend summit, ask for the awesome June & Alex Kleider on the summit floor!
* Will Obama/Romney mention OLPC in their [http://www.2012presidentialelectionnews.com/2012-debate-schedule/2012-presidential-debate-schedule/ foreign policy debate] Monday Oct 22, 6PM PDT? As [http://blog.laptop.org/2012/10/03/former-president-clinton-mentions-olpc/ Bill Clinton just did] Sept 23? Find out at a local bar with us!
* [http://wiki.laptop.org/go/User:Cbigenho Caryl Bigenho] and [http://derndorfer.eu Christoph Derndorfer] invite you to an on-street segway city adventure for about $30, perhaps late Mon/Tue Oct 22-23? Music/shows also possible. Please contact them or jot something in right here !
* SF [http://www.africahacktrip.org/ AfricaHackTrip] Meeting #1, Wednesday Oct 24, Noon @ SFSU downtown: http://www.meetup.com/AfricaHackTrip/events/85328062/
 
The olpc-social@googlegroups.com mailing list for [https://www.eventbrite.com/event/4025544512 registered summit attendees] can also help coordinate ad hoc/spontaneous in-city get-togethers etc!

== Relevant SF Communities ==

* [http://en.wikipedia.org/wiki/Noisebridge Award-winning] anarchistic SF educational hackerspace: http://Noisebridge.net
* Silicon Valley-San Francisco Bay Area Python Interest Group, meets Oct 25: http://BayPIGgies.net

= Accommodations =

San Francisco is not cheap, but great hostels are available if you book them early. Please write to the olpc-sf@lists.laptop.org public mailing list for tips, so you can get to know & stay nearby others: http://lists.laptop.org/listinfo/olpc-sf

The olpc-social@googlegroups.com mailing list for [https://www.eventbrite.com/event/4025544512 registered summit attendees] can also help coordinate ad hoc/spontaneous in-city get-togethers etc!

= Ride Board =

Drivers and Passengers: Post your ride information here.

* Driver: Janissa Balcomb, traveling from Wayan, Idaho. Room for 1 passenger comfortably, 2 if one has short legs. Leaving Idaho Thu Oct 18, Returning ?Wed (or Thu) Oct 24 (or 25). Main route will be via I-80 thru Elko, Reno & Sacramento. Will probably camp overnight partway.

= Suggestions =

Most welcome (register & click Edit above!) & also here: http://wiki.sugarlabs.org/go/Talk:Sugarcamp_SF_2012

Please also join the [http://lists.laptop.org/listinfo/olpc-sf olpc-sf public mailing list] if you'd like to volunteer making this event an important if not historic contribution to global collaborative learning, thanks! You may also write privately to Adam Holt if you prefer: holt @ laptop.org

Sugarcamp SF 2012

2012-09-28T15:53:17Z

ChristophD: /* Topics */

SugarCamp++ will be Mon Oct 22 to Wed Oct 24 in San Francisco (business hours especially) immediately following [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html OLPC SF's global community summit].

Presenting an opportunity for all to begin real hacking & implementation of the tech/learning/organizational ideas exchanged over the weekend summit

Please join & help strengthen collaborative global education! Inspired by the rapidly-approaching [http://lists.sugarlabs.org/archive/iaep/2012-August/015452.html dream of Sugar 1.0] and the [http://www.olpcnews.com/laptops/xo-4/olpc_xo_4_will_provide_significant_performance_boost.html XO-4].

We strongly welcome new participants. Read up on [http://planet.sugarlabs.org ongoing] [http://planet.laptop.org projects], think about [mailto:volunteer@laptop.org volunteering] with [http://www.sugarlabs.org Sugar Labs] and [http://one.laptop.org OLPC], open your imagination to what open-learning-for-all might become -- and [http://olpcMAP.net put yourself on the map] :)

 
http://olpcSF.org/sites/default/files/u8/red_xo_in_sf_fog_2012.jpg

= Topics =

Please add project topics below if you will give them legs :)

* [http://cananian.livejournal.com/66654.html XOrduino], Curricular Arcs, Streamlined Teacher Training
* [http://lists.laptop.org/pipermail/server-devel/2012-August/006126.html School Server] [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc Community Edition] (hassle-free [http://ChildrensLibrary.org ICDL], Yes We [http://khanAcademy.org Khan], lessons learned from Oct 19-21 demo classroom @ SFSU? etc)
* [http://lists.sugarlabs.org/archive/sugar-devel/2012-August/thread.html#38829 Sugar 0.98 & 1.0 and what lies beyond] (vs Windows 8 releasing Fri Oct 26 ;)
* Hackers Without Borders, Feedback from Small/Medium-sized Deployments, [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 NewCo], [http://wiki.laptop.org/go/ALEARN_Network ALEARN]
* Documentation within Sugar; Video Tutorials; Books/Histories of OLPC/Sugar
* Power Infrastructure: developing countries' schools need what??
* translating butía construction instructions from Spanish to English (Christoph)

= Relevant SF Communities =

* [http://en.wikipedia.org/wiki/Noisebridge Award-winning] anarchistic SF educational hackerspace: http://Noisebridge.net
* Silicon Valley-San Francisco Bay Area Python Interest Group, meets Oct 25: http://BayPIGgies.net

= Attendees =

Please add your name if you will come & contribute to the future of Sugar/OLPC or similar -- include 2 words about your preferred project:

* [http://twitter.com/adborden Aaron Borden]? OLPC SF
* Adam Gordon, Toronto/[http://ntugigroup.org Kenya] (Oct 19-22)
* Adam Holt, Boston (Oct 17-25)
* Alex Kleider, SF - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* Aleksey Lim, Russia (Oct 19-24?)
* Anish Mangal, UMichigan, former Dextrose Project Manager (Oct 17-21)
* Anna Schoolfield, Birmingham Alabama (Oct 19-24?)
* [http://lumiere.ens.fr/~guerry/ Bastien Guerry?] Paris - XS Community Edition?
* [http://codewiz.org Bernie Innocenti], Boston - Google, Sugar Labs founder (Oct 19-24?)
* Bill Stelzer, US Virgin Islands (Oct 18-27)
* Caryl Bigenho, Los Angeles area - Teacher & [http://wiki.laptop.org/go/Contributors_program Contributors Program] mentor (Oct 19-24)
* Christoph Derndorfer, Vienna - OLPC News Editor (in SF Oct 17-25)
* Cherry Withers? San Jose CA | Philippines
* Christine Murakami? Ohio - [http://csgolpc2012.weebly.com Columbus School for Girls]
* Claudia Urrea? Boston | Colombia - OLPC [http://one.laptop.org/about/people/claudia-urrea Director of Learning]
* [http://twitter.com/craigperue Craig Perue] - Jamaica Ministry of Education (Curricular Arcs, Project Mgmt)
* CScott Ananian? Boston - [http://cananian.livejournal.com XOrduino?] [http://lists.sugarlabs.org/archive/iaep/2012-September/015518.html Arduino?]
* Daniel Drake, Nicaragua (Oct 18-24)
* David Farning, Wisconsin - [http://activitycentral.com Activity Central] founder (Oct 19-24?)
* David Jessup? Florida - OLPC/Liberty City [http://one.laptop.org/about/people/david-jessup-jr Project Manager] (Oct 19-22?)
* Ed Bigenho, Los Angeles area (Oct 19-24)
* Gary Martin? Scotland
* George Hunt, NYC - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition] (Oct 19-24)
* Giulia D'Amico? - OLPC [http://one.laptop.org/about/people/giulia-damico VP of Business Development]
* Grant Bowman - [http://olpcSF.org OLPC SF]
* Janissa Balcomb - [http://olpc2010-lesotho.blogspot.com/ Lesotho] (Oct 19-22?)
* Jennifer Martino - [http://www.olpccanada.com/blog/ OLPC Canada] [http://twitter.com/olpccanada Director] (Oct 18-22)
* Jerry Vonau? Winnipeg - [http://www.laptop.org.au/ OLPC Australia], [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* Kevin Gordon, Toronto | [http://ntugigroup.org Kenya] (Oct 18-22)
* Marina Zdobnova, LA/Russia (Oct 19-24?)
* Mark Battley, Toronto | [http://ntugigroup.org Kenya] - Curricular Arcs (Oct 18-24?)
* Mary Lou Jepsen? Taiwan - [http://pixelqi.com/ Pixel Qi]
* Matt Keller? Connecticut | [http://www.technologyreview.com/view/429206/emtech-preview-another-way-to-think-about/ Ethiopia] (Oct 20-21?)
* Mitch Seaton, Philippines | Australia | Denmark (Oct 18-26)
* Mike Lee, DC - Tablets, [http://olpcLearningClub.org OLPC Learning Club] (Oct 19-23)
* Nancie Severs, New Hampshire/Thailand/Vietnam - [http://wiki.laptop.org/go/Contributors_program Contributors Program] coordinator (Oct 18-22)
* Nick Doiron? SF - Code For America (Oct 19-24?)
* Richard M.Batna, Montreal (Oct 19-22?)
* Richard Smith? Boston - [http://lists.laptop.org/listinfo/power power electronics], OLPC [http://one.laptop.org/about/people/richard-smith Director of Embedded Engineering]
* Ruben Rodriguez? Spain - Activity Central CTO
* Sameer Verma - [http://olpcSF.org OLPC SF] Chief Organizer
* Sarah Naguib? [http://laptopsforegypt.wordpress.com Ohio | Egypt]
* Simon Schampijer? Berlin
* SJ Klein? Boston - [http://meta.wikimedia.org/wiki/Trustees Wikipedia Board], [http://dp.la Digital Public Library of America] (Oct 20-22?)
* Tanja Kohn, Austria (in SF October 16 - 26 early morning)
* Tony Anderson, Rwanda - Karma Learning System, XS Community Edition? (Oct 19-24?)
* Walter Bender, Boston - [[Oversight Board|Sugar Labs Executive Director]] (Oct 19-24?)
* Yoshiki Ohshima? Los Angeles

= Location =

In 2 modern classrooms, Oct 22-24 (Mon to Wed), 8AM to 5PM:

San Francisco State University
Rooms 667 & 668
835 Market St, 6th Floor (go downtown, NOT main campus)
San Francisco, CA 94103

Nearby pubs will be well-used evenings too !

== Registration ==

Be sure to add your name to the "Attendees" list above, with a couple words about your interests, and also write to holt @ laptop.org confirming there's still room!

Both rooms will be free (thanks to the amazing generosity of SF State University's College of Business) with reliable Wifi included -- lunch/dinner is available for individual purchase downstairs at the large Food Court.

Note the preceding weekend's [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html Oct 19-21 Community Summit] itself (structured talks/demos/panels etc, you don't want to miss, [https://www.eventbrite.com/event/4025544512 please register now!]) costs $25 to $40/person to pay for facilities rental, great community shirts, supplies etc. A price that would indeed be an order of magnitude higher if it weren't for the astonishing volunteer efforts of the http://olpcSF.org community :)

== Evenings Excitement ==

[http://wiki.laptop.org/go/User:Cbigenho Caryl Bigenho] and [http://derndorfer.eu Christoph Derndorfer] would love to help organize evening events if you have ideas please contact them or write something in right here !!

= Accommodations =

San Francisco is not cheap, but great hostels are available if you book them early. Please write to the olpc-sf@lists.laptop.org public mailing list for tips, so you can get to know & stay nearby others: http://lists.laptop.org/listinfo/olpc-sf

= Suggestions =

Most welcome (register & click Edit above!) & also here: http://wiki.sugarlabs.org/go/Talk:Sugarcamp_SF_2012

Please also join the [http://lists.laptop.org/listinfo/olpc-sf olpc-sf public mailing list] if you'd like to volunteer making this event an important if not historic contribution to global collaborative learning, thanks! You may also write privately to Adam Holt if you prefer: holt @ laptop.org

= Ride Board =

Drivers and Passengers: Post your ride information here.

* Driver: Janissa Balcomb, traveling from Wayan, Idaho. Room for 1 passenger comfortably, 2 if one has short legs. Leaving Idaho Thu Oct 18, Returning ?Wed (or Thu) Oct 24 (or 25). Main route will be via I-80 thru Elko, Reno & Sacramento. Will probably camp overnight partway.

Sugarcamp SF 2012

2012-09-26T09:07:39Z

ChristophD: /* Attendees */

SugarCamp++ will be Mon Oct 22 to Wed Oct 24 in San Francisco (business hours especially) immediately following [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html OLPC SF's global community summit].

Presenting an opportunity for all to begin real hacking & implementation of the tech/learning/organizational ideas exchanged over the weekend summit

Please join & help strengthen collaborative global education! Inspired by the rapidly-approaching [http://lists.sugarlabs.org/archive/iaep/2012-August/015452.html dream of Sugar 1.0] and the [http://www.olpcnews.com/laptops/xo-4/olpc_xo_4_will_provide_significant_performance_boost.html XO-4].

We strongly welcome new participants. Read up on [http://planet.sugarlabs.org ongoing] [http://planet.laptop.org projects], think about [mailto:volunteer@laptop.org volunteering] with [http://www.sugarlabs.org Sugar Labs] and [http://one.laptop.org OLPC], open your imagination to what open-learning-for-all might become -- and [http://olpcMAP.net put yourself on the map] :)

 
http://olpcSF.org/sites/default/files/u8/red_xo_in_sf_fog_2012.jpg

= Topics =

Please add project topics below if you will give them legs :)

* [http://cananian.livejournal.com/66654.html XOrduino], Curricular Arcs, Streamlined Teacher Training
* [http://lists.laptop.org/pipermail/server-devel/2012-August/006126.html School Server] [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc Community Edition] (hassle-free [http://ChildrensLibrary.org ICDL], Yes We [http://khanAcademy.org Khan], lessons learned from Oct 19-21 demo classroom @ SFSU? etc)
* [http://lists.sugarlabs.org/archive/sugar-devel/2012-August/thread.html#38829 Sugar 0.98 & 1.0 and what lies beyond] (vs Windows 8 releasing Fri Oct 26 ;)
* Hackers Without Borders, Feedback from Small/Medium-sized Deployments, [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 NewCo], [http://wiki.laptop.org/go/ALEARN_Network ALEARN]
* Documentation within Sugar; Video Tutorials; Books/Histories of OLPC/Sugar
* Power Infrastructure: developing countries' schools need what??

= Relevant SF Communities =

* [http://en.wikipedia.org/wiki/Noisebridge Award-winning] anarchistic SF educational hackerspace: http://Noisebridge.net
* Silicon Valley-San Francisco Bay Area Python Interest Group, meets Oct 25: http://BayPIGgies.net

= Attendees =

Please add your name if you will come & contribute to the future of Sugar/OLPC or similar -- include 2 words about your preferred project:

* [http://twitter.com/adborden Aaron Borden]? OLPC SF
* Adam Gordon, Toronto/[http://ntugigroup.org Kenya] (Oct 19-22)
* Adam Holt, Boston (Oct 17-25)
* Alex Kleider, SF - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* Anish Mangal, UMichigan, former Dextrose Project Manager (Oct 17-21)
* Anna Schoolfield, Birmingham Alabama (Oct 19-24?)
* [http://lumiere.ens.fr/~guerry/ Bastien Guerry?] Paris - XS Community Edition?
* [http://codewiz.org Bernie Innocenti], Boston - Google, Sugar Labs founder (Oct 19-24?)
* Bill Stelzer, US Virgin Islands
* Caryl Bigenho, Los Angeles - Teacher & [http://wiki.laptop.org/go/Contributors_program Contributors Program] mentor (Oct 19-24?)
* Christoph Derndorfer, Vienna - OLPC News Editor (in SF Oct 17-25)
* Cherry Withers? San Jose CA | Philippines
* Christine Murakami? Ohio - [http://csgolpc2012.weebly.com Columbus School for Girls]
* Claudia Urrea? Boston | Colombia - OLPC [http://one.laptop.org/about/people/claudia-urrea Director of Learning]
* [http://twitter.com/craigperue Craig Perue] - Jamaica Ministry of Education (Curricular Arcs, Project Mgmt)
* CScott Ananian? Boston - [http://cananian.livejournal.com XOrduino?] [http://lists.sugarlabs.org/archive/iaep/2012-September/015518.html Arduino?]
* Daniel Drake, Nicaragua (Oct 18-24)
* David Farning, Wisconsin - [http://activitycentral.com Activity Central] founder (Oct 19-24?)
* David Jessup? Florida - OLPC/Liberty City [http://one.laptop.org/about/people/david-jessup-jr Project Manager] (Oct 19-22?)
* Ed Bigenho (Oct 19-24?)
* Gary Martin? Scotland
* George Hunt, NYC - [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition] (Oct 19-24)
* Giulia D'Amico? - OLPC [http://one.laptop.org/about/people/giulia-damico VP of Business Development]
* Grant Bowman - [http://olpcSF.org OLPC SF]
* Janissa Balcomb - [http://olpc2010-lesotho.blogspot.com/ Lesotho] (Oct 19-22?)
* Jennifer Martino - [http://www.olpccanada.com/blog/ OLPC Canada] [http://twitter.com/olpccanada Director] (Oct 18-22)
* Jerry Vonau? Winnipeg - [http://www.laptop.org.au/ OLPC Australia], [http://wiki.laptop.org/go/XS_Community_Edition XS Community Edition]
* Kevin Gordon, Toronto | [http://ntugigroup.org Kenya] (Oct 18-22)
* Mark Battley, Toronto | [http://ntugigroup.org Kenya] - Curricular Arcs (Oct 18-24?)
* Mary Lou Jepsen? Taiwan - [http://pixelqi.com/ Pixel Qi]
* Matt Keller? Connecticut | [http://www.technologyreview.com/view/429206/emtech-preview-another-way-to-think-about/ Ethiopia] (Oct 20-21?)
* Mitch Seaton, Philippines | Australia | Denmark (Oct 18-26)
* Mike Lee, DC - Tablets, [http://olpcLearningClub.org OLPC Learning Club] (Oct 19-23)
* Nancie Severs, New Hampshire/Thailand/Vietnam - [http://wiki.laptop.org/go/Contributors_program Contributors Program] coordinator (Oct 18-22)
* Nick Doiron? SF - Code For America (Oct 19-24?)
* Richard M.Batna, Montreal (Oct 19-22?)
* Richard Smith? Boston - [http://lists.laptop.org/listinfo/power power electronics], OLPC [http://one.laptop.org/about/people/richard-smith Director of Embedded Engineering]
* Ruben Rodriguez? Spain - Activity Central CTO
* Sameer Verma - [http://olpcSF.org OLPC SF] Chief Organizer
* Sarah Naguib? [http://laptopsforegypt.wordpress.com Ohio | Egypt]
* Simon Schampijer? Berlin
* SJ Klein? Boston - [http://meta.wikimedia.org/wiki/Trustees Wikipedia Board], [http://dp.la Digital Public Library of America] (Oct 20-22?)
* Tanja Kohn, Austria (in SF October 16 - 26 early morning)
* Tony Anderson, Rwanda - Karma Learning System, XS Community Edition? (Oct 19-24?)
* Walter Bender, Boston - [[Oversight Board|Sugar Labs Executive Director]] (Oct 19-24?)
* Yoshiki Ohshima? Los Angeles

= Location =

In 2 modern classrooms, Oct 22-24 (Mon to Wed), 8AM to 5PM:

San Francisco State University
Rooms 667 & 668
835 Market St, 6th Floor (go downtown, NOT main campus)
San Francisco, CA 94103

Nearby pubs will be well-used evenings too !

== Registration ==

Be sure to add your name to the "Attendees" list above, with a couple words about your interests, and also write to holt @ laptop.org confirming there's still room!

Both rooms will be free (thanks to the amazing generosity of SF State University's College of Business) with reliable Wifi included -- lunch/dinner is available for individual purchase downstairs at the large Food Court.

Note the preceding weekend's [http://www.olpcnews.com/use_cases/community/olpc_san_francisco_community_summit_2012.html Oct 19-21 Community Summit] itself (structured talks/demos/panels etc, you don't want to miss, [https://www.eventbrite.com/event/4025544512 please register now!]) costs $25 to $40/person to pay for facilities rental, great community shirts, supplies etc. A price that would indeed be an order of magnitude higher if it weren't for the astonishing volunteer efforts of the http://olpcSF.org community :)

= Accommodations =

San Francisco is not cheap, but great hostels are available if you book them early. Please write to the olpc-sf@lists.laptop.org public mailing list for tips, so you can get to know & stay nearby others: http://lists.laptop.org/listinfo/olpc-sf

= Suggestions =

Most welcome (register & click Edit above!) & also here: http://wiki.sugarlabs.org/go/Talk:Sugarcamp_SF_2012

Please also join the [http://lists.laptop.org/listinfo/olpc-sf olpc-sf public mailing list] if you'd like to volunteer making this event an important if not historic contribution to global collaborative learning, thanks! You may also write privately to Adam Holt if you prefer: holt @ laptop.org

= Ride Board =

Drivers and Passengers: Post your ride information here.

* Driver: Janissa Balcomb, traveling from Wayan, Idaho. Room for 1 passenger comfortably, 2 if one has short legs. Leaving Idaho Thu Oct 18, Returning ?Wed (or Thu) Oct 24 (or 25). Main route will be via I-80 thru Elko, Reno & Sacramento. Will probably camp overnight partway.

Sugarcamp SF 2012

2012-09-20T13:18:33Z

ChristophD:

SugarCamp++ will be Mon Oct 22 to Wed Oct 24 in San Francisco, immediately following OLPC SF's global community summit: http://olpcSF.org/summit

Presenting an opportunity for all to begin real hacking & implementation of the tech/learning/organizational ideas exchanged over the weekend summit

Please join & help strengthen collaborative global education! Inspired by the rapidly-approaching [http://lists.sugarlabs.org/archive/iaep/2012-August/015452.html dream of Sugar 1.0] and the [http://www.olpcnews.com/laptops/xo-4/olpc_xo_4_will_provide_significant_performance_boost.html XO-4].

We strongly welcome new participants. Read up on [http://planet.sugarlabs.org ongoing] [http://planet.laptop.org projects], think about [mailto:volunteer@laptop.org volunteering] with [http://www.sugarlabs.org Sugar Labs] and [http://one.laptop.org OLPC], open your imagination to what open-learning-for-all might become -- and [http://olpcMAP.net put yourself on the map] :)

 
http://olpcSF.org/sites/default/files/u8/red_xo_in_sf_fog_2012.jpg

= Topics =

Please add project topics below if you will give them legs :)

* [http://cananian.livejournal.com/66654.html XOrduino], Curricular Arcs, Streamlined Teacher Training
* [http://lists.laptop.org/pipermail/server-devel/2012-August/006126.html School Server] [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc Community Edition] (hassle-free [http://ChildrensLibrary.org ICDL], Yes We [http://khanAcademy.org Khan], lessons learned from Oct 19-21 demo classroom @ SFSU? etc)
* [http://lists.sugarlabs.org/archive/sugar-devel/2012-August/thread.html#38829 Sugar 0.98 & 1.0 and what lies beyond] (vs Windows 8 releasing Fri Oct 26 ;)
* Hackers Without Borders, Feedback from Small/Medium-sized Deployments, [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 NewCo], [http://wiki.laptop.org/go/ALEARN_Network ALEARN]
* Documentation within Sugar; Video Tutorials; Books/Histories of OLPC/Sugar
* Power Infrastructure: developing countries' schools need what??

= Relevant SF Communities =

* [http://en.wikipedia.org/wiki/Noisebridge Award-winning] anarchistic SF educational hackerspace: http://Noisebridge.net
* Silicon Valley-San Francisco Bay Area Python Interest Group, meets Oct 25: http://BayPIGgies.net

= Attendees =

Please add your name if you will come & contribute to the future of Sugar/OLPC or similar -- include 2 words about your preferred project:

* [http://twitter.com/adborden Aaron Borden]? OLPC SF
* Adam Gordon, Toronto/[http://ntugigroup.org Kenya]
* Adam Holt, Boston (in SF Oct 18-25?)
* Alex Kleider, SF - XS Community Edition
* Anish Mangal, UMichigan (former Dextrose Project Manager)
* [http://lumiere.ens.fr/~guerry/ Bastien Guerry?] Paris - XS Community Edition?
* [http://codewiz.org Bernie Innocenti], Boston - Google, Sugar Labs founder
* Bill Stelzer, US Virgin Islands
* Caryl Bigenho, Los Angeles - Teacher & [http://wiki.laptop.org/go/Contributors_program Contributors Program] mentor
* Christoph Derndorfer, Vienna - OLPC News Editor (in SF Oct 17-25)
* Cherry Withers? San Jose CA | Philippines
* Christine Murakami? Ohio - [http://csgolpc2012.weebly.com Columbus School for Girls]
* Claudia Urrea? Boston | Colombia - OLPC [http://one.laptop.org/about/people/claudia-urrea Director of Learning]
* [http://twitter.com/craigperue Craig Perue] - Jamaica Ministry of Education (Curricular Arcs, Project Mgmt)
* CScott Ananian? Boston - [http://cananian.livejournal.com XOrduino?] [http://lists.sugarlabs.org/archive/iaep/2012-September/015518.html Arduino?]
* Daniel Drake, Nicaragua (will attend but not sure which days)
* David Farning, Wisconsin - [http://activitycentral.com Activity Central] founder
* David Jessup? Florida - OLPC/Liberty City [http://one.laptop.org/about/people/david-jessup-jr Project Manager]
* Gary Martin? Scotland
* George Hunt, NYC - [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc XS Community Edition]
* Giulia D'Amico? - OLPC [http://one.laptop.org/about/people/giulia-damico VP of Business Development]
* Grant Bowman - [http://olpcSF.org OLPC SF]
* Janissa Balcomb - [http://olpc2010-lesotho.blogspot.com/ Lesotho]
* Jennifer Martino - [http://www.olpccanada.com/blog/ OLPC Canada] [http://twitter.com/olpccanada Director] (Oct 18-22)
* Jerry Vonau? Winnipeg - [http://www.laptop.org.au/ OLPC Australia], [https://docs.google.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc XS Community Edition]
* Kevin Gordon, Toronto/[http://ntugigroup.org Kenya]
* Mark Battley, Toronto/[http://ntugigroup.org Kenya] - Curricular Arcs
* Mary Lou Jepsen? Taiwan - [http://pixelqi.com/ Pixel Qi]
* Matt Keller? Connecticut/[http://www.technologyreview.com/view/429206/emtech-preview-another-way-to-think-about/ Ethiopia]
* Mitch Seaton, Philippines/Australia/Denmark (Oct 18-26)
* Mike Lee, DC - Tablets, [http://olpcLearningClub.org OLPC Learning Club] (Oct 19-23)
* Nancie Severs, New Hampshire/Thailand/Vietnam (Oct 18-22) - [http://wiki.laptop.org/go/Contributors_program Contributors Program] coordinator
* Nick Doiron? SF - Code For America
* Richard M.Batna, Montreal
* Richard Smith? Boston - [http://lists.laptop.org/listinfo/power power electronics], OLPC [http://one.laptop.org/about/people/richard-smith Director of Embedded Engineering]
* Ruben Rodriguez, Spain? Activity Central CTO
* Sameer Verma - [http://olpcSF.org OLPC SF] Chief Organizer
* Sarah Naguib? [http://laptopsforegypt.wordpress.com Ohio/Egypt]
* Simon Schampijer? Berlin
* SJ Klein? Boston - [http://meta.wikimedia.org/wiki/Trustees Wikipedia Board], [http://dp.la Digital Public Library of America]
* Tony Anderson, Rwanda - Karma Learning System, XS Community Edition?
* Walter Bender, Boston - [[Oversight Board|Sugar Labs Executive Director]]
* Yoshiki Ohshima? Los Angeles

= Location =

UNCONFIRMED BUT LIKELY:

San Francisco State University 
835 Market St, 5th Floor (go downtown, NOT main campus!) 
San Francisco, CA 94103

In a modern classroom (or possibly 2!) Oct 22-24, most business hours and possibly Mon/Tue early evenings. Nearby pubs will be well-used evenings too.

== Registration ==

Cost will be kept to an absolute minimum (likely free, thanks to the amazing generosity of SFSU) with reliable Wifi included -- lunch/dinner available for individual purchase downstairs at the large Food Court.

Note the weekend's [http://olpcSF.org/summit Oct 19-21 Community Summit] itself (structured talks/demos/panels etc, you don't want to miss, [https://www.eventbrite.com/event/4025544512 please register now!]) costs $25 to $40/person to pay for facilities rental, great community shirts, supplies etc. A price that would indeed be an order of magnitude higher if it weren't for the astonishing volunteer efforts of the http://olpcSF.org community :)

= Accommodations =

San Francisco is not cheap, but great hostels are available if you book them early. Please write to the olpc-sf@lists.laptop.org public mailing list for tips, so you can get to know & stay nearby others: http://lists.laptop.org/listinfo/olpc-sf

= Suggestions =

Most welcome (register & click Edit above!) & also here: http://wiki.sugarlabs.org/go/Talk:Sugarcamp_SF_2012

Please also join the [http://lists.laptop.org/listinfo/olpc-sf olpc-sf public mailing list] if you'd like to volunteer making this event an important if not historic contribution to global collaborative learning, thanks! You may also write privately to Adam Holt if you prefer: holt @ laptop.org

= Ride Board =

Drivers and Passengers: Post your ride information here.

* Driver: Janissa Balcomb, traveling from Wayan, Idaho. Room for 1 passenger comfortably, 2 if one has short legs. Leaving Idaho Thu Oct 18, Returning ?Wed (or Thu) Oct 24 (or 25). Main route will be via I-80 thru Elko, Reno & Sacramento. Will probably camp overnight partway.

Sugarcamp SF 2012

2012-09-13T09:15:04Z

ChristophD: /* Attendees */

SugarCamp++ will be Mon Oct 22 to Wed Oct 24 in San Francisco, immediately following OLPC SF's global community summit: http://olpcSF.org/summit

Presenting an opportunity for all to begin real hacking & implementation of the tech/learning/organizational ideas exchanged over the weekend summit

Please join & help strengthen collaborative global education! Inspired by the rapidly-approaching [http://lists.sugarlabs.org/archive/iaep/2012-August/015452.html dream of Sugar 1.0] and the [http://www.olpcnews.com/laptops/xo-4/olpc_xo_4_will_provide_significant_performance_boost.html XO-4].

We strongly welcome new participants. Read up on [http://planet.sugarlabs.org ongoing] [http://planet.laptop.org projects], think about [mailto:volunteer@laptop.org volunteering] with [http://www.sugarlabs.org Sugar Labs] and [http://one.laptop.org OLPC], open your imagination to what open-learning-for-all might become -- and [http://olpcMAP.net put yourself on the map] :)

 
http://olpcSF.org/sites/default/files/u8/red_xo_in_sf_fog_2012.jpg

= Topics =

Please add project topics below if you will give them legs :)

* [http://cananian.livejournal.com/66654.html XOrduino], Curricular Arcs, Streamlined Teacher Training
* [http://lists.laptop.org/pipermail/server-devel/2012-August/006126.html School Server Community Edition] (hassle-free [http://ChildrensLibrary.org ICDL], Yes We [http://khanAcademy.org Khan], lessons learned from Oct 19-21 demo classroom @ SFSU? etc)
* [http://lists.sugarlabs.org/archive/sugar-devel/2012-August/thread.html#38829 Sugar 0.98 & 1.0 and what lies beyond] (vs Windows 8 releasing Fri Oct 26 ;)
* Hackers Without Borders, Feedback from Small/Medium-sized Deployments, [http://meeting.sugarlabs.org/sugar-meeting/meetings/2012-05-30T21:08:10 NewCo], [http://wiki.laptop.org/go/ALEARN_Network ALEARN]
* Documentation within Sugar; Video Tutorials; Books/Histories of OLPC/Sugar
* Power Infrastructure: developing countries' schools need what??

= Relevant SF Communities =

* [http://en.wikipedia.org/wiki/Noisebridge Award-winning] anarchistic SF educational hackerspace: http://Noisebridge.net
* Silicon Valley-San Francisco Bay Area Python Interest Group, meets Oct 25: http://BayPIGgies.net

= Attendees =

Please add your name if you will come & contribute to the future of Sugar/OLPC or similar -- include 2 words about your preferred project:

* Adam Holt, Boston (in SF Oct 18-25?)
* Alex Kleider, SF - XS Community Edition
* Anish Mangal, UMichigan (former Dextrose Project Manager)
* Bastien Guerry? Paris - XS Community Edition?
* Bernie Innocenti, Boston
* Bill Stelzer? US Virgin Islands
* Caryl Bigenho? Los Angeles
* Christoph Derndorfer, Vienna (hopefully in SF Oct 17-25 but TBC)
* Cherry Withers? San Jose CA | Philippines
* Christine Murakami? Columbus Ohio
* Claudia Urrea? Boston | Colombia
* Craig Perue, Jamaica - Curricular Arcs
* CScott Ananian? Boston - [http://cananian.livejournal.com/66654.html XOrduino?]
* Daniel Drake, Nicaragua (will attend but not sure which days)
* David Farning? Wisconsin
* Gary Martin? Scotland
* George Hunt, NYC - XS Community Edition
* Giulia D'Amico - OLPC Association, Miami
* Janissa Balcomb - Lesotho
* Jerry Vonau? Winnipeg - XS Community Edition?
* Kevin Gordon, Toronto/Kenya
* Mark Battley? Toronto/Kenya - Curricular Arcs
* Mary Lou Jepsen? Taiwan
* Matt Keller?? Connecticut
* Mitch Seaton, Philippines/Australia/Denmark (Oct 18-26)
* Mike Lee, DC (Oct 19-23)
* Nancie Severs, New Hampshire (Oct 18-22)
* Nick Doiron? SF
* Ruben Rodriguez, Spain? Activity Central CTO
* Sameer Verma, SF
* Simon Schampijer? Berlin
* Tony Anderson, Rwanda - Karma Learning System, XS Community Edition?
* Walter Bender, Boston
* Yoshiki Ohshima? Los Angeles

= Location =

UNCONFIRMED BUT LIKELY:

San Francisco State University 
835 Market St, 5th Floor (go downtown, NOT main campus!) 
San Francisco, CA 94103

In a modern classroom (or possibly 2!) Oct 22-24, most business hours and possibly Mon/Tue early evenings. Nearby pubs will be well-used evenings too.

Cost will be kept to an absolute minimum (possibly free, thanks to the amazing generosity of SFSU) with reliable Wifi included -- lunch/dinner available for purchase downstairs at the large Food Court.

Note the weekend's [http://olpcSF.org/summit Oct 19-21 Community Summit] itself (structured talks/demos/panels etc, you don't want to miss!) typically costs about $40/person to pay for room rental, supplies etc. That price would be an order of magnitude higher if it weren't for the astonishing volunteer efforts of the http://olpcSF.org community.

= Accommodations =

San Francisco is not cheap, but great hostels are available if you book them early. Please write to the olpc-sf@lists.laptop.org public mailing list for tips, so you can get to know & stay nearby others: http://lists.laptop.org/listinfo/olpc-sf

= Suggestions =

Most welcome (register & click Edit above!) & also here: http://wiki.sugarlabs.org/go/Talk:Sugarcamp_SF_2012

Please also join the [http://lists.laptop.org/listinfo/olpc-sf olpc-sf public mailing list] if you'd like to volunteer making this event an important if not historic contribution to global collaborative learning, thanks! You may also write privately to Adam Holt if you prefer: holt @ laptop.org

= Ride Board =

Drivers and Passengers: Post your ride information here.

* Driver: Janissa Balcomb, traveling from Wayan, Idaho. Room for 1 passenger comfortably, 2 if one has short legs. Leaving Idaho Thu Oct 18, Returning ?Wed (or Thu) Oct 24 (or 25). Main route will be via I-80 thru Elko, Reno & Sacramento. Will probably camp overnight partway.

Activities/XoEditor

2012-04-05T19:24:32Z

ChristophD: capital letters in Activity

<noinclude>{{GoogleTrans-en}}{{TOCright}}[[Category:Activities|xoEditor]]</noinclude>

[[Image:XOEditor-icon.svg]]

==About XOEditor==

XOEditor is an Activity that can be used to create different color combinations for the XO icon at the heart of the Sugar interface.

== Using XOEditor ==

[[Image:XOEditor.png]]

You launch XOEditor from the Home View by clicking on the Activity icon. Once the Activity has opened, you will see an XO icon in the center of the screen surrounded by colored circles. The circles are color "stroke-fill" combinations. By clicking on a circle, the XO icon takes on those colors. You can save a selected color combination using the Save Button on the Main Toolbar.

:'''Did you know''' that as of Version 3, XOEditor will save your colors?
:'''Did you know''' that you need to restart Sugar in order to load the new colors?
:'''Did you know''' that you can drag the dots around on the screen? The repositioned dots are saved to the Sugar Journal and will be restored when you relaunch the Activity.

=== The toolbars ===

[[Image:XOEditor-toolbar.png]]

On the Main Toolbar, from left to right:
;The Activity Toolbar button: Used to open the Activity toolbar
;The Save Button: Used to save the currently selected colors as your new Activity colors
;The standard Stop Button: Used to exit the Activity

=== Alerts ===

[[Image:XOEditor-toolbar-confirm.png]]

[[Image:XOEditor-toolbar-notify.png]]

XOEditor uses the Sugar alert system to:
:# confirm that you really do want to save the new colors you have selected; and
:# to alert you to the fact that the new colors will only be loaded upon a restart of Sugar.

=== Dragging the dots ===

[[Image:XOEditor-drag.png|300px]]

The dots can be dragged across the screen to be organized into different arrangements. These arrangements are saved to the Sugar Journal and restored when you resume the Activity.

== Where to get XOEditor ==
The XOEditor Activity is available on the [http://activities.sugarlabs.org/en-US/sugar/addon/4085 Sugar Labs Activity portal]. The source code to XOEditor is available on [http://git.sugarlabs.org/xo-colors gitorious].

== Where to report problems ==
You can report bugs and make feature requests [https://bugs.sugarlabs.org/newticket?component=Portfolio on our bug-tracking system] (You need to create an account first). To list all open tickets of XOEditor you can use [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Xoeditor query component=Xoeditor]. You are also welcome to leave comments/suggestions on the [[Talk:Activities/XoEditor]] page.

== A word to educators ==

While XOEditor is primarily intended to be used as a simple utility for changing the colors in the Sugar interface, it can be used to introduce some color concepts, such as [http://en.wikipedia.org/wiki/Monochrome monochrome], [http://en.wikipedia.org/wiki/Complementary_colors complementary colors], and some aspects of [http://interisciplinary-lab.wikispaces.com/file/view/jacobson.pdf color expression].

Example projects/questions:
:Can you sort the color dots by hue? e.g., drag the red dots to one region of the screen and the blue dots to another region of the screen. What should you do with the dots that are multicolored?
:Can you find color combinations that are "quiet"? "loud"?
:Which color combinations do you like? Why?

== A word to developers ==

The [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4085#version-2 original version of XOEditor] was written in Javascript and bundled into an instance of Browse. The original [[Activities/XoEditor/XoEditor.xml|XML file]] is in the wiki. As of Version 3, XOEditor has been rebased to Python.

The XO colors are stored using gconf:

<pre>~/.gconf/desktop/user/%gconf.xml</pre>

<pre>
<?xml version="1.0"?>
<gconf>
<entry name="color" mtime="1333639070" type="string">
<stringvalue>#00A0FF,#005FE4</stringvalue>
</entry>
<entry name="nick" mtime="1333490344" type="string">
<stringvalue>Walter Bender</stringvalue>
</entry>
</gconf>
</pre>

The Python code used to write to gconf:

<pre>
client = gconf.client_get_default()
client.set_string('/desktop/sugar/user/color', '%s,%s' % (
self._game.colors[0], self._game.colors[1]))
</pre>

== Suggestions for modification ==

* The colors used in XOEditor are from [http://git.sugarlabs.org/sugar-toolkit/mainline/blobs/master/src/sugar/graphics/xocolor.py the standand Sugar colors class]. An interesting challenge would be to modify the program to use a different list of color pairs. The use case for such a modifcation would be that it would let the learner explore a broader range of color combinations. (The XO colors were chosen to meet a specific, narrow set of criteria: legibility and colorfulness. What are some other criteria?)

* The original Javascript version of XOEditor let you look at the color pairs on top of different background colors. It would be a nice feature to add to the Python version. The use case for such a modification is that colors appear differently depending upon the context in which they are viewed. This modification would allow the learner to explore the impact of background color on perception.)

----

Please add your suggestions and/or patches and/or use cases here.

== Credits ==

XOEditor was written and is maintained by [[User:Walter]].

Activities/XoEditor

2012-04-05T19:23:29Z

ChristophD: /* About XOEditor */

<noinclude>{{GoogleTrans-en}}{{TOCright}}[[Category:Activities|xoEditor]]</noinclude>

[[Image:XOEditor-icon.svg]]

==About XOEditor==

XOEditor is an Activity that can be used to create different color combinations for the XO icon at the heart of the Sugar interface.

== Using XOEditor ==

[[Image:XOEditor.png]]

You launch XOEditor from the Home View by clicking on the Activity icon. Once the activity has opened, you will see an XO icon in the center of the screen surrounded by colored circles. The circles are color "stroke-fill" combinations. By clicking on a circle, the XO icon takes on those colors. You can save a selected color combination using the Save Button on the Main Toolbar.

:'''Did you know''' that as of Version 3, XOEditor will save your colors?
:'''Did you know''' that you need to restart Sugar in order to load the new colors?
:'''Did you know''' that you can drag the dots around on the screen? The repositioned dots are saved to the Sugar Journal and will be restored when you relaunch the Activity.

=== The toolbars ===

[[Image:XOEditor-toolbar.png]]

On the Main Toolbar, from left to right:
;The Activity Toolbar button: Used to open the Activity toolbar
;The Save Button: Used to save the currently selected colors as your new activity colors
;The standard Stop Button: Used to exit the Activity

=== Alerts ===

[[Image:XOEditor-toolbar-confirm.png]]

[[Image:XOEditor-toolbar-notify.png]]

XOEditor uses the Sugar alert system to:
:# confirm that you really do want to save the new colors you have selected; and
:# to alert you to the fact that the new colors will only be loaded upon a restart of Sugar.

=== Dragging the dots ===

[[Image:XOEditor-drag.png|300px]]

The dots can be dragged across the screen to be organized into different arrangements. These arrangements are saved to the Sugar Journal and restored when you resume the activity.

== Where to get XOEditor ==
The XOEditor Activity is available on the [http://activities.sugarlabs.org/en-US/sugar/addon/4085 Sugar Labs Activity portal]. The source code to XOEditor is available on [http://git.sugarlabs.org/xo-colors gitorious].

== Where to report problems ==
You can report bugs and make feature requests [https://bugs.sugarlabs.org/newticket?component=Portfolio on our bug-tracking system] (You need to create an account first). To list all open tickets of XOEditor you can use [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Xoeditor query component=Xoeditor]. You are also welcome to leave comments/suggestions on the [[Talk:Activities/XoEditor]] page.

== A word to educators ==

While XOEditor is primarily intended to be used as a simple utility for changing the colors in the Sugar interface, it can be used to introduce some color concepts, such as [http://en.wikipedia.org/wiki/Monochrome monochrome], [http://en.wikipedia.org/wiki/Complementary_colors complementary colors], and some aspects of [http://interisciplinary-lab.wikispaces.com/file/view/jacobson.pdf color expression].

Example projects/questions:
:Can you sort the color dots by hue? e.g., drag the red dots to one region of the screen and the blue dots to another region of the screen. What should you do with the dots that are multicolored?
:Can you find color combinations that are "quiet"? "loud"?
:Which color combinations do you like? Why?

== A word to developers ==

The [http://activities.sugarlabs.org/en-US/sugar/addons/versions/4085#version-2 original version of XOEditor] was written in Javascript and bundled into an instance of Browse. The original [[Activities/XoEditor/XoEditor.xml|XML file]] is in the wiki. As of Version 3, XOEditor has been rebased to Python.

The XO colors are stored using gconf:

<pre>~/.gconf/desktop/user/%gconf.xml</pre>

<pre>
<?xml version="1.0"?>
<gconf>
<entry name="color" mtime="1333639070" type="string">
<stringvalue>#00A0FF,#005FE4</stringvalue>
</entry>
<entry name="nick" mtime="1333490344" type="string">
<stringvalue>Walter Bender</stringvalue>
</entry>
</gconf>
</pre>

The Python code used to write to gconf:

<pre>
client = gconf.client_get_default()
client.set_string('/desktop/sugar/user/color', '%s,%s' % (
self._game.colors[0], self._game.colors[1]))
</pre>

== Suggestions for modification ==

* The colors used in XOEditor are from [http://git.sugarlabs.org/sugar-toolkit/mainline/blobs/master/src/sugar/graphics/xocolor.py the standand Sugar colors class]. An interesting challenge would be to modify the program to use a different list of color pairs. The use case for such a modifcation would be that it would let the learner explore a broader range of color combinations. (The XO colors were chosen to meet a specific, narrow set of criteria: legibility and colorfulness. What are some other criteria?)

* The original Javascript version of XOEditor let you look at the color pairs on top of different background colors. It would be a nice feature to add to the Python version. The use case for such a modification is that colors appear differently depending upon the context in which they are viewed. This modification would allow the learner to explore the impact of background color on perception.)

----

Please add your suggestions and/or patches and/or use cases here.

== Credits ==

XOEditor was written and is maintained by [[User:Walter]].

User:ChristophD

2011-11-18T19:08:42Z

ChristophD: /* contact */

__NOTOC__
==== real name ====

* Christoph Derndorfer

==== location====

* Vienna, Austria

==== contact ====

* christoph AT olpcnews.com DOT com

==== www ====

* [http://www.olpc.at OLPC Austria] (member)
* [http://www.olpcnews.com olpcnews] (co-editor)
* [http://christoph-d.blogspot.com/ personal blog]
* [http://twitter.com/random_musings twitter]

==== main focus of contributions to olpc / Sugar ====

* documentation ([http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook activity handbook] / [http://sugarlabs.org/go/DocumentationTeam booksprint])
* community outreach / presentations (chemnitzer linuxtage, cebit, austrian computer association, various austrian universities, olpc grassroots bootcamp)
* broad coverage of everything related to olpc and Sugar at olpcnews

==== other ====

Please also see [http://wiki.laptop.org/go/User:ChristophD my profile on wiki.laptop.org].

Finance

2011-11-09T14:37:05Z

ChristophD: /* Requesting budget */ added note about Bernie's authority for <$200 requests

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.

== Current finances ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.

* The last known balance is from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html August 1, 2011] and is $21,141.78 USD, held as follows:
** $21,141.78 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $21,141.78 USD is earmarked as follows ([http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html source]):
** $9,435.91 USD for Gould Grant
** $1,600 USD has been ear-marked to purchase a server
** $10,105.87 USD unrestricted (available for future grants)

''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)

''Balance updated based on information from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html this] and [http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html that] e-mail.'' [[User:ChristophD|ChristophD]] 20:23, 7 November 2011 (EST)

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

'''Important Note:''' [http://wiki.sugarlabs.org/go/User:Bernie Bernie Innocenti] has immediate permission to approve anybody's requests of $200 of less!

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

If you're asking for funds to cover a trip, use this set of questions.

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

== Archive of transactions ==

=== April 2011 ===

Not known.

=== March 2011 ===

Not known.

=== February 2011 ===

Not known.

=== January 2011 ===

'''End-of-month balance:''' $19,591.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! Item
! From/To
! Income
! Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
| -$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest from Vanguard account
| Vanguard
| $0.92
|
|
|-
!
! Total
! $0.92
! -$1,680.00
!
|}

Finance

2011-11-09T14:25:12Z

ChristophD: moved the Archive section to the end of the page since I think that the "requesting funds" information is more important

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.

== Current finances ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.

* The last known balance is from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html August 1, 2011] and is $21,141.78 USD, held as follows:
** $21,141.78 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $21,141.78 USD is earmarked as follows ([http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html source]):
** $9,435.91 USD for Gould Grant
** $1,600 USD has been ear-marked to purchase a server
** $10,105.87 USD unrestricted (available for future grants)

''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)

''Balance updated based on information from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html this] and [http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html that] e-mail.'' [[User:ChristophD|ChristophD]] 20:23, 7 November 2011 (EST)

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

If you're asking for funds to cover a trip, use this set of questions.

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

== Archive of transactions ==

=== April 2011 ===

Not known.

=== March 2011 ===

Not known.

=== February 2011 ===

Not known.

=== January 2011 ===

'''End-of-month balance:''' $19,591.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! Item
! From/To
! Income
! Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
| -$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest from Vanguard account
| Vanguard
| $0.92
|
|
|-
!
! Total
! $0.92
! -$1,680.00
!
|}

Finance

2011-11-08T01:23:41Z

ChristophD: /* Current finances */ updated with information about earmarked money

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.

== Current finances ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.

* The last known balance is from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html August 1, 2011] and is $21,141.78 USD, held as follows:
** $21,141.78 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $21,141.78 USD is earmarked as follows ([http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html source]):
** $9,435.91 USD for Gould Grant
** $1,600 USD has been ear-marked to purchase a server
** $10,105.87 USD unrestricted (available for future grants)

''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)

''Balance updated based on information from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html this] and [http://lists.sugarlabs.org/archive/iaep/2011-November/014354.html that] e-mail.'' [[User:ChristophD|ChristophD]] 20:23, 7 November 2011 (EST)

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Archive of transactions ==

=== April 2011 ===

Not known.

=== March 2011 ===

Not known.

=== February 2011 ===

Not known.

=== January 2011 ===

'''End-of-month balance:''' $19,591.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! Item
! From/To
! Income
! Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
| -$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest from Vanguard account
| Vanguard
| $0.92
|
|
|-
!
! Total
! $0.92
! -$1,680.00
!
|}

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

If you're asking for funds to cover a trip, use this set of questions.

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

Finance

2011-11-08T01:08:19Z

ChristophD: /* Current finances */ update to reflect that balance is based on August 1 check

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.

== Current finances ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.

* The last known balance is from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html August 1, 2011] and is $21,141.78 USD, held as follows:
** $21,141.78 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $21,141.78 USD is earmarked as follows:
** ?? for Gould Grant
** ?? unrestricted (available for future grants)

''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)

''Balance updated based on information from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html this e-mail].'' [[User:ChristophD|ChristophD]] 20:07, 7 November 2011 (EST)

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Archive of transactions ==

=== April 2011 ===

Not known.

=== March 2011 ===

Not known.

=== February 2011 ===

Not known.

=== January 2011 ===

'''End-of-month balance:''' $19,591.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! Item
! From/To
! Income
! Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
| -$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest from Vanguard account
| Vanguard
| $0.92
|
|
|-
!
! Total
! $0.92
! -$1,680.00
!
|}

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

If you're asking for funds to cover a trip, use this set of questions.

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

Finance

2011-11-08T01:07:19Z

ChristophD: /* Current finances */ update based on early November 2011 information

This page should answer two questions:

* How much money does Sugar Labs currently have, where did it come from, and what is it being used for?
* How can I ask for some of it?

(We hope you'll also help us figure out how to get more resources as well!)

The [[Oversight Board]] is currently responsible for the finances of Sugar Labs. This responsibility may be delegated to an individual at some later point.

== Current finances ==

All figures are in USD. All figures for a month refer to transactions that occurred within that month (i.e. a month is only calculated at the end.

* The last known balance is from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html November 3, 2011] and is $21,141.78 USD, held as follows:
** $21,141.78 USD in a Vanguard Money Market account held by the Software Freedom Conservancy on behalf of Sugar Labs

* The $21,141.78 USD is earmarked as follows:
** ?? for Gould Grant
** ?? unrestricted (available for future grants)

''[[User:Walter|Walter Bender]] should be filling in the details above shortly.'' [[User:Mchua|Mchua]] 17:54, 21 April 2011 (EDT)

''Balance updated based on information from [http://lists.sugarlabs.org/archive/iaep/2011-November/014349.html this e-mail].'' [[User:ChristophD|ChristophD]] 20:07, 7 November 2011 (EST)

== Where we get money from ==

Sugar Labs doesn't have much in the way of regular income, so we can't predict when new funding will come in. We've gotten funding from a few sources in the past:

* Donations from private individuals (thank you!)
* Grant money to develop certain aspects of Sugar Labs - this is typically earmarked for a specific project
* Google Summer of Code - Sugar Labs gets $500 of unrestricted funds for each student mentored.

In particular, if you're interested in applying for an external grant to work on some aspect of Sugar Labs, let us know; we'd be happy to help.

== Archive of transactions ==

=== April 2011 ===

Not known.

=== March 2011 ===

Not known.

=== February 2011 ===

Not known.

=== January 2011 ===

'''End-of-month balance:''' $19,591.09

'''Net change since last month:''' -$1,679.08

'''Transactions:'''

{|border="1" cellspacing="0" width="100%" align="right"
! Item
! From/To
! Income
! Expenses
! Notes
|-
| Gould Grant student developer salary
| Gould Grant student employee
|
| -$1,680.00
| Not sure if we want to put names here, so I left that information out. [[User:Mchua|Mchua]]
|-
| Interest from Vanguard account
| Vanguard
| $0.92
|
|
|-
!
! Total
! $0.92
! -$1,680.00
!
|}

== Requesting budget ==

You may request budget for Sugar Labs related travel or project expenses. We can't fully fund every request, because we do operate on a limited budget. But we can't fund yours if we don't know you have a need -- so if you do, fill out a request and we'll get in touch with you about it.

You can see the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component all open requests] and also the list of [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&component=fundingrequest&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone every request that's ever been made].

=== How to fill out a request ===

A request can be filled out in 10 minutes or less. We're trying to make this process as easy as possible!

# Open a [http://bugs.sugarlabs.org/newticket new ticket] in the Sugar Labs tracker. (You'll have to log into the tracker to do this.)
# Set the component to "fundingrequest." '''This is important. If the component is not set correctly, we will not see your ticket when we search for it!'''
# Answer the [[#What we need to know]] questions in the description field of your ticket.
# Once the ticket has been filed, Send an email to [http://lists.sugarlabs.org/listinfo/iaep iaep] (for transparency) and [http://lists.sugarlabs.org/listinfo/slobs slobs] (as the decision-making body) with the subject line "New Finance Request: <short summary of the item requested>," where <short summary of the item requested> is replaced by... well, a short summary of what you're asking for money for, and a link to the ticket in the body of your email. '''This is important. If you do not email both lists, nobody will know you've submitted a budget request!'''

At this point, you should wait to hear back from SLOBs. If nobody's responded to your request within a week, feel free to ping both mailing lists again.

=== What we need to know ===

Each request ticket must contain answers to one of the following sets of questions, depending on the type of funding you're asking for.

==== For funding travel ====

If you're asking for funds to cover a trip, use this set of questions.

# '''Where are you going''' (location and event)?
# '''What do you need covered?''' (Please estimate the costs in USD: hotel $X, travel $Y)
# '''If we cannot provide a full subsidy, will a partial subsidy be helpful?''' (Yes/No)
## If Yes can you specify the minimum amount you would need covered to facilitate your attendance
# If you are requesting airfare, include complete flight information such as flight numbers, desired departure and arrival airports, and times. Also let us know if you have specific time restrictions.
# '''Do you need a visa or other official processing before you can travel?''' If so, approximately how long does that processing take?
# '''What will you accomplish by going on this trip?''' Please be as specific as possible, since this is the most important factor in granting requests.

The last question really is the most important, and will likely be the longest part of your answer. Tell us what you're going to accomplish by taking this trip. Preference is given to people who are attending an event with a goal to make Sugar Labs better, and a plan for doing it.

Simply "meeting with people" or "talking about ways to do something" are not specific to Sugar Labs. Ideas can be discussed on mailing lists, after all. And although meeting face to face is a wonderful thing, that doesn't necessarily result in getting anything done.

* Not specific: Meet with other people from JKL Group.
* Not specific: Improve communication between Team X and Team Y.
* Specific: Write a working module for Web App Q that creates a service queue for Team X to do Task Z more efficiently.
* Specific: Agree on and publish a complete plan, schedule, and milestones for Project W.

==== For purchasing things ====

Use this template if you're requesting the purchase of equipment, a subscription, etc.

# '''What is being purchased?''' If it's a product, link to the product, etc.
# '''Why does this purchase benefit the operations of Sugar Labs?''' What is the blocker it resolves?
# '''Who will be responsible for the item?''' Who will own it? How will it be tracked/maintained?
# '''How much will it cost?''' Are there any maintenance costs associated with the purchase? How often will it have to be renewed (if at all)?
# '''What other options were evaluated for purchase?''' Why did the chosen product/service/option get selected as the best one? What were the criteria or features you needed?
# '''What deadlines are associated with this request?''' Do you need an answer by a certain date? Would the funding need to come by a particular point in time? Note that approving future spending is a separate action from actually spending the money - for instance, we may agree to fund something but pay for it 3 months down the line - so it's good to know both dates, if they exist.
# '''Other notes?'''

=== How decisions are made ===

This section explains the criteria typically used to decide whether to subsidize the travel of a specific applicant. It's provided for context only - if you're requesting funding, you don't actually have to read this stuff!

==== Relevance ====

* ''Does this purchase/event deliver information that is pertinent to an ongoing project of concern at the event?'' For example, an event that includes a critical brainstorming session on deployment outreac could be more effective with the attendance of a teacher or engineer from a deployment.
* ''Does the purchase/event provide an opportunity for this particular person to attract contribution to one or more areas in Sugar Labs?'' An event that attracts computer-based designers, for instance, might present an opportunity for a member of the Design team to attract new, skilled contributors.
* ''Is the requesting person a current contributor?'' Current contributors with a proven history of involvement in some sense are a known quantity. This does not mean that sponsorship shouldn't go to new or potential contributors, but it is a factor for consideration.

==== Criticality ====

* (For travel only) ''Does this person have demonstrated skills in an area that will promote reaching the goals of the event?'' For example, if Sugar's speaking schedule at an event requires someone with expertise on packaging Activities for various Linux distributions, it would make sense to sponsor the travel of someone who could give those talks.
* ''Are there clear deliverables attached to this purchase/event that otherwise cannot be achieved?'' Deliverables come in many forms, such as working code; completed documentation; or key decisions. For purchases, will the absence of the purchase block or negatively impact work that is already being done on the project? For events, if other contributors involved in the same area are expected to attend already, will this person's absence negatively impact their work at the event?
* ''How important is this subsidy to the purchase/event?'' Without the full subsidy, will the item not be able to be purchased, or will the applicant not be able to attend the event at all? Will a partial subsidy suffice? Would a change in plans, such as attending part of the event, or getting a less full-featured item, still allow this person's goals to be achieved? Is Sugar Labs funding the ''only'' option available for this purchase?

==== Specificity ====

* ''Has this person provided substantial information about the specific objectives to achieve?'' We look at the proposal critically, because there are usually more requests than we can fill. The best requests tend to reflect clear vision from the applicants of exactly what they will achieve through this funding, and a link between that vision and the larger objectives of Sugar Labs or a specific team.
* ''Are the objectives achievable within the time frame of the event/project?'' Sometimes it may not be possible to meet every objective despite best intentions and hard work. Nevertheless, sponsors should also carefully consider whether the deliverables can reasonably be finished by the end of the relevant time period. Setting and meeting reasonable expectations is a good habit for any project.

==== Proximity ====

* (For event travel only) ''Is this person located in the same region as the event?'' Regionally co-located people generally require less funding. It is not cost effective, for instance, to fund the travel of multiple people from North America to a European event. In specific cases there may be call for such subsidies, but in general regional events should reflect regional attendance and participation.

==== Expense ====

* ''How expensive is the request?'' A higher subsidy amount should carry with it higher expectations, more criticality, or other benefits that justify the expense. Keep in mind that the transparent approval process creates better accountability for sponsors in making decisions.

''This system is based on the [https://fedorahosted.org/fudcon-planning/wiki/FundingRequest Fedora community funding request system].''

Events/SugarCamp

2011-08-25T23:01:09Z

ChristophD: updated my info

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
| Staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] with Simon between on 9, 10, 12 and staying at [http://www.montclair-hostel.com/ Le Montclair Hostel] on 12 and 13
|-
| Daniel Drake
| 10, 11
| staying at Hotel Palma
|-
| Raul Gutierrez
| 10, 11
| staying at Hotel Palma
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] w/ Christoph
|-
| Sascha Silbe, Sabine Schneider
| 9-14
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma]
|-
|-
| Mitchell Seaton
| 7-12
| Staying at [http://www.montclair-hostel.com/ Le Montclair Hostel]
|-
| Christophe Guéret
| 10
| Staying at [http://www.booking.com/hotel/fr/de-paris.en-us.html Hotel de Paris]
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

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

Events/SugarCamp

2011-08-22T10:00:58Z

ChristophD:

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
| staying with Simon between 9 and 12 and will then find sth for the other 2 nights
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
|
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] w/ Christoph
|-
| Sascha Silbe
|
|
|-
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

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

Events/SugarCamp

2011-08-22T09:54:48Z

ChristophD: erikos, christoph update

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
| see Simon info
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
|
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| staying at [http://www.paris-hotel-palma.com/index.htm Hotel Palma] w/ Christoph
|-
| Sascha Silbe
|
|
|-
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

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

Events/SugarCamp

2011-08-21T20:54:55Z

ChristophD: /* Off-schedule hacking sessions */ added documentation session

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
|
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
|
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| Private room (shared with 1 other?)
|-
| Sascha Silbe
|
|
|-
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

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

Events/SugarCamp

2011-08-19T12:52:23Z

ChristophD: Perfect hostel is fully booked already

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
|
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
|
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
| 9-11
| Private room (shared with 1 other?)
|-
| Sascha Silbe
|
|
|-
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

Ideas for sessions (please add/edit):
* Focus on a couple of 11.3.0 issues (Daniel, Simon, Saturday afternoon?)
* Finish some pending design discussions (Simon, Gary)
* The road to PyGI/GTK3: no-hippo, porting Sugar theme to GTK3, etc. (Daniel, Simon, Raul, Sunday and Monday?)

Events/SugarCamp

2011-08-19T11:11:46Z

ChristophD:

=== General information ===

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

=== Accommodation ===

{| class="wikitable"
|-
! Person
! Nights needed
! Preference
|-
| Christoph Derndorfer
| 9-14
|
|-
| Daniel Drake
| 10, 11
| Whatever's cheap (dorm fine), but would pay a small amount more to share a private room
|-
| Raul Gutierrez
|
|
|-
| Gary Martin
|
|
|-
| Simon Schampijer
|
| Private room (shared with 1 other?)
|-
| Sascha Silbe
|
|
|-
|}

Venue: 30 Avenue Corentin Cariou, 75019 Paris, FR

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

=== Off-schedule hacking sessions ===

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

Ideas for sessions (please add/edit):
* Focus on a couple of 11.3.0 issues (Daniel, Simon, Saturday afternoon?)
* Finish some pending design discussions (Simon, Gary)
* The road to PyGI/GTK3: no-hippo, porting Sugar theme to GTK3, etc. (Daniel, Simon, Raul, Sunday and Monday?)

Oversight Board/Minutes

2011-06-12T02:42:54Z

ChristophD: added link to June 9 meeting log and to http://meeting.sugarlabs.org/sugar-meeting

<noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Oversight board will be holding regular bi-weekly meetings on Thursdays at 20 UTC on irc.freenode.net (channel: #sugar-meeting).
Please [[#Questions for upcoming meeting|add a topic]] you want to discuss with Oversight board members and join the [[#Next meeting|next meeting]].

Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.

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

==About==
The Sugar Labs [[Oversight_Board|Oversight Board]] "shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki,"

[[Sugar Labs/Governance/Committees|Committee]] reports will be a regular part of the meetings.

==Who==

The meeting is mainly targeted to Sugar Oversight Board, but everyone interested is welcome to join. It's primary purpose is to discuss general issues related to Sugar and the Sugar community; however, it is not intended as a replacement for the weekly developer meetings.

== Questions for upcoming meeting ==

If you have an idea or a question to discuss with Oversight Board members gathered in one place at the same time, please [[Wiki_Team/Guide/Editing_Pages#How_to_edit_one_section|add new entry]] to the list below, at least prior to ~48 hours before the [[#Next meeting|scheduled time]] to let the meeting chairman form the final agenda and/or contact with you if so.

* ''What are our biggest issues right now?''
** [[User:Alsroot/Sugar_Architecture#Implementation|some ideas from technical pov]], [[User:Alsroot|alsroot]] 05:36, 24 December 2010 (EST):
**# Educators, designers and user experience specialists are the real core of the Sugar. Since, imho, Sugar is not a particular software project but an education related ecosystem.
**# Lack of full-functional support of doers workflow.
* ''add question with detailed information here''

The discussion topics for upcoming meetings are listed [[#Agenda items|below]]. Topics will be collected between meetings, triaged by the meeting chair, and send out in the meeting announcement on ~24 hours before the meeting. A reminder to add topics will be announced in the [[Sugar_Labs/Current_Events|Sugar Digest]].

==Meetings ==

=== Next meeting===

==== 2011 April 28 15EST, 22UTC Email slobs at lists dot sugarlabs dot org to propose a time, if you want the topic queue to be brought up. ====

==== Agenda items ====

* Proposal for adopting the GPLv3 for Sugar and some core activities (bernie)

Please contact an oversight-board member to add topics to be considered for the meeting.

=== Open discussion topics===

{|
|width=50%; valign=top|
Administrative
* Committee reports
** Local Labs
** Membership/Sponsorship
** Events
***FOSDEM
***Others
** Deployment
** Infrastructure

* Funding
** Grant status
** Donations to our supporting partners

|width=50%; valign=top|
* Partnerships
** Pangaean
** Gitorious
** Qt Software
** Bicocca
** Relationship with OLPC

* Misc
** Babson program
** Website/wiki
** Release names
|}

=== Past meetings ===

Meetings were held on Friday and at 15:00 UTC except where specified. Logs of meetings on the #sugar-meeting channel are available [http://meeting.sugarlabs.org/sugar-meeting/ here].

{|
|width="25%" valign="top"|
'''2011'''

9 June
([[Oversight Board/2011/Meeting Minutes-2011-06-09|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/2011-06-09#i_2671836 log])

21 April
([[Oversight Board/Meeting Minutes-2011-04-21|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T19:00:15 log (1)][http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-04-21T20:05:05 log (2)])

4 March
([[Oversight Board/2011/Meeting Minutes-2011-03-04|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-04T23:00:51 log])

17 February
([[Oversight Board/2011/Meeting Minutes-2011-02-17|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-17 log])

10 February
([[Oversight Board/2011/Meeting Minutes-2011-02-10|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-10 log])

13 Jan
([[Oversight Board/2011/Meeting Minutes-2011-01-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-01-13T20:03:31 log])

|width="25%" valign="top"|
'''2010'''

23 Dec
([[Oversight Board/2010/Meeting-log-2010-12-23|log]])

16 Dec
([[Oversight Board/2010/Meeting-log-2010-12-16|log]])

13 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-13|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-13T22:03:08 log])

1 Dec
([[Oversight Board/2010/Meeting Minutes-2010-12-01|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-12-01T17:03:11 log])


26 Oct
([[Oversight Board/2010/Meeting Minutes-2010-10-26|minutes]], [http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-26T15:24:49 log])


28 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-28|minutes]], [[Oversight Board/Meeting Log-2010-09-28|log]])


14 Sep
([[Oversight Board/2010/Meeting Minutes-2010-09-14|minutes]], [http://jita.sugarlabs.org/sugar-meeting/meetings/2010-09-14T15:16:44 log])


24 Aug
([[Oversight Board/2010/Meeting Minutes-2010-08-24|minutes]], [[Oversight Board/Meeting Log-2010-08-24|log]])


11 Jul
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100711_0446.html discussion]


25 Jun (15UTC)
[http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100625_1103.html discussion]

04 June (15UTC)
([[Oversight Board/2010/Meeting Minutes-2010-06-04|minutes]], [[Oversight Board/2010/Meeting Log-2010-06-04|log]])

14 May (15UTC)
([[Oversight Board/2010/Meeting Minutes-2010-05-14|minutes]], [[Oversight Board/2010/Meeting Log-2010-05-14|log]])

07 May (15UTC)
([[Oversight Board/2010/Meeting Minutes-2010-05-07|minutes]], [[Oversight Board/2010/Meeting Log-2010-05-07|log]])

26 Mar (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-03-26|minutes]], [[Oversight Board/2010/Meeting Log-2010-03-26|log]])

12 Mar (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-03-12|minutes]], [[Oversight Board/2010/Meeting Log-2010-03-12|log]])

5 Mar (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-03-05|minutes]], [[Oversight Board/2010/Meeting Log-2010-03-05|log]])

26 Feb (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-02-26|minutes]], [[Oversight Board/2010/Meeting Log-2010-02.26|log]])

5 Feb (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-02-05|minutes]], [[Oversight Board/2010/Meeting Log-2010-02-05|log]])

29 Jan (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-01-29|minutes]], [[Oversight Board/2010/Meeting Log-2010-01-29|log]])

22 Jan (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-01-22|minutes]], [[Oversight Board/2010/Meeting Log-2010-01-22|log]])

15 Jan (16UTC)
([[Oversight Board/2010/Meeting Minutes-2010-01-15|minutes]], [[Oversight Board/2010/Meeting Log-2010-01-15|log]])

8 Jan
([[Oversight Board/2010/Meeting Minutes-2010-01-08|minutes]], [[Oversight Board/2010/Meeting Log-2010-01-08|log]])

|width="25%" valign="top"|
'''2009'''

30 Dec (Wed)
([[Oversight Board/2009/Meeting Minutes-2009-12-30|minutes]], [[Oversight Board/2009/Meeting Log-2009-12-30|log]])

23 Dec (Wed)
([[Oversight Board/2009/Meeting Minutes-2009-12-23|minutes]], [[Oversight Board/2009/Meeting Log-2009-12-23|log]])

18 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-18|minutes]], [[Oversight Board/2009/Meeting Log-2009-12-18|log]])

11 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-11|minutes]], [[Oversight Board/2009/Meeting Log-2009-12-11|log]])

4 Dec
([[Oversight Board/2009/Meeting Minutes-2009-12-04|minutes]], [[Oversight Board/2009/Meeting Log-2009-12-04|log]])

20 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-20|minutes]], [[Oversight_Board/2009/Meeting_Log-2009-11-20|log]])

13 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-13|minutes]], [[Oversight_Board/2009/Meeting_Log-2009-11-13|log]])

6 Nov
([[Oversight Board/2009/Meeting Minutes-2009-11-06|minutes]], [[Oversight_Board/2009/Meeting_Log-2009-11-06|log]])

30 Oct
([[Oversight Board/2009/Meeting Minutes-2009-10-30|minutes]], [[Oversight_Board/2009/Meeting_Log-2009-10-30|log]])

25 Sep
([[Oversight Board/2009/Meeting Minutes-2009-09-25|minutes]], [[Oversight Board/2009/Meeting Log-2009-09-25|log]])


28 Aug
([[Oversight Board/2009/Meeting Minutes-2009-08-28|minutes]], [[Oversight Board/Log-2009-08-28|log]])


10 Jul
([http://meeting.sugarlabs.org/sugar-meeting.minutes.20090710_0905.html minutes],
[http://meeting.sugarlabs.org/sugar-meeting.log.20090710_0905.html log])


06 Mar
([[Oversight Board/2009/Meeting Minutes-2009-03-06|minutes]])


13 Feb
([[Oversight Board/2009/Meeting Minutes-2009-02-13|minutes]], [[Oversight Board/2009/Log-2009-02-13|log]])


02 Feb (Mon)
([[Oversight Board/2009/Meeting Minutes-2009-02-02|minutes]], [[Oversight Board/2009/Log-2009-02-02|log]])


|width="25%" valign="top"|

'''2008'''

12 Dec

([[Oversight Board/2008/Meeting Minutes-2008-12-12|minutes]], [[Oversight Board/2008/Log-2008-12-12|log]])


31 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-31|minutes]], [[Oversight Board/2008/Log-2008-10-31|log]])


17 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-17|minutes]], [[Oversight Board/2008/Log-2008-10-17|log]])


03 Oct

([[Oversight Board/2008/Meeting Minutes-2008-10-03|minutes]], [[Oversight Board/2008/Log-2008-10-03|log]])


19 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-19|minutes]], [[Oversight Board/2008/Log-2008-09-19|log]])


5 Sep

([[Oversight Board/2008/Meeting Minutes-2008-09-05|minutes]], [[Oversight Board/2008/Log-2008-09-05|log]])


1 Aug

([[Oversight Board/2008/Meeting Minutes-2008-08-01|minutes]], [[Oversight Board/2008/Log-2008-08-01|log]])


18 Jul (17.00 UTC)

([[Oversight Board/2008/Meeting Minutes-2008-07-18|minutes]], [[Oversight Board/2008/Log-2008-07-18|log]])


30 Jun (Mon, 17.00 UTC)

([[Oversight Board/2008/Meeting_Minutes-2008-06-30|minutes]], [[Oversight Board/2008/Log-2008-06-30|log]])


|}

[[Category:Oversight board]]
[[Category:Meetings]]
[[Category:Meeting minutes]]
[[Category:Governance]]

EduJAM/2011

2011-05-14T22:29:59Z

ChristophD: /* Photos of the summit / Fotos del encuentro */

{{Translations}}
'''Thanks to all participants of eduJAM! 2011 (5-7 May 2011) // Gracias a todos los participantes del eduJAM! 2011 (5-7 Mayo 2011)'''
[[File:Edujam-final.jpg|800px]]

== Summit page // Página del evento ==
'''Home page of the summit: http://edujam2011.ceibaljam.org/edujam2011_en // Página principal del evento: http://edujam2011.ceibaljam.org'''

== Photos of the summit / Fotos del encuentro ==

* http://www.flickr.com/photos/62554468@N03/sets/72157626586497313/with/5716105406/
* http://picasaweb.google.com/pflores2/EduJAM2011#
* http://www.flickr.com/photos/christophd/sets/72157626514302097/with/5685214622/
* http://www.flickr.com/photos/madprime/
* http://codewiz.org/wiki/pictures/conf/EduJAM-2011
* http://www.flickr.com/x/t/0090009/photos/luzanone/sets/72157626656559110/
* http://picasaweb.google.com/ebordon/EduJam?authkey=Gv1sRgCLK9jtmCy7qH9QE#
* https://picasaweb.google.com/110361379457702390492/May132011?authkey=Gv1sRgCKbs2a_N-6SElwE# (captions to be added)

== Presentations ==

* http://www.slideshare.net/eduJam2011/presentations
* http://www.slideshare.net/search/slideshow?type=presentations&q=edujam

== Videos ==

* http://www.dailymotion.com/sugarlabs
* http://blog.printf.net/articles/2011/05/14/edujam-2011

== Press/blogosphere // Prensa/blogósfera ==
After event // Luego del evento:

eduJAM! 2011 & Sugar Code Sprint
* http://www.olpcnews.com/countries/uruguay/lapix_an_electronic_pen_accessory.html

Conozco Uruguay Tour:
* http://olpcuruguay2011.wordpress.com/ Note: You are invited to add your comments and articles to this group blog. There are 4 admins, so one of them will approve it for you.

Before event // Antes del evento:
* Puesta a punto de un encuentro vibrante con varias ofertas http://ceibaljam.org/drupal/?q=node/1173

== Misc ==
* Etherpad: http://etherpad.tugraz.at/NpJPnsS68L
* Projects show in the opening // Proyectos expuestos en la apertura: http://ceibaljam.org/node/1333
* list public archive: http://box541.bluehost.com/pipermail/all-edujam2011_ceibaljam.org/
* Look for #edujam in twitter: http://twitter.com/#!/search/edujam
* Related files // Archivos relacionados: http://ceibaljam.org/drupal/?q=node/1323

== Attendees - Please add info & link adresses // Asistentes - Por favor agreguen info & link ==
Argentina:
* María Abramovich
* Cynthia Casal
* Martin Langhoff, Argentina/Miami
* Alvar Maciel
* Laura Manolakis
* Gonzalo Odiard
* Manuel Quiñones
* Lucía Zanone
Austria:
* Christoph Derndorfer, Vienna/Madrid
Bolivia:
* Vladimir Castro Salas, Bolivia/Perú
Chile:
* Patricio Acevedo http://wiki.sugarlabs.org/go/Sugar_Labs_Chile
* Werner Westermann
Colombia:
* Rafael Ortiz, Colombia
* Bianca Suárez
El Salvador:
* Douglas Cerna, El Salvador
Francia:
* Bastien Guerry
Germany // Alemania
* Bert Freudenberg, Germany
* Simon Schampijer, Germany
Paraguay:
* Martín Abente http://wiki.sugarlabs.org/go/User:Tch
* Rodolfo Arce
Perú:
* Sebastián Silva, Perú/Colombia
India:
* Anish Mangal, India/Paraguay
Italia:
* Bernie Innocenti, Italy/USA
Uruguay:
* Micaela Acosta, ceibalJAM!
* Alan Aguiar, Butiá
* Andrés Aguirre, Butiá
* Andrés Ambrois, ceibalJAM!/Hackspace Montevideo http://wiki.laptop.org/index.php?title=User:Aa
* Federico Andrade, Butiá
* Barbanegra, Hackspace Montevideo
* Esteban Arias, Plan Ceibal
* Paolo Benini, RAP
* Esteban Bordón, Plan Ceibal
* Inés Bouvier, Flor de Ceibo
* Roxana Castellano, Creática
* Daniel Castelo, Plan Ceibal
* Gabriel Eirea, ceibalJAM!
* Ignacio Escudero, RAP
* Luciano Ferrari, Plan Ceibal
* Pablo Flores, ceibalJAM!
* Bernabé García, Hackspace Montevideo
* Sandra González, Plan Ceibal
* Ruben Ingver
* Karen López, Plan Ceibal
* Rocío Medina, RAP
* Luis Michelena, ceibalJAM!
* Oscar Nieto, RAP
* Evelyn Pelufo, Plan Ceibal
* Jesusa Pereira
* Eugenia Pinilla, Plan Ceibal
* Carlos Rabassa, RAP
* Nenny Rabassa, RAP
* Rosamel Ramirez
* Alejandro Rodríguez, ceibalJAM!
* Christofer Roibal, ceibalJAM!
* Leticia Romero, RAP/ceibalJAM!
* Fernando Sansberro
* Gonzalo Tejera, Butiá
* Victoria Torena, Plan Ceibal
* Guzmán Trindad
USA:
* Tony Anderson Texas/Nepal/Rwanda
* Chris Ball, OLPC, Boston
* Walter Bender, Sugar Labs
* Caryl Bigenho
* Ed Bigenho
* Aaron Borden, San Francisco
* Nick Doiron, New Hampshire/Uganda/Uruguay
* David Farning, USA
* Adam Holt, OLPC, Sugar Labs, USA
* Mr. Holt
* C. Scott Ananian, OLPC, Boston
* John Tierney, OLPC
Rusia:
* Aleksey Lim
Rwanda:
* Nkubito Bakuramutsa, Rwanda

= Information written during the organization of the summit =

This page is for planning the EduJAM! summit in Uruguay May 5th to 7th 2011.

'''Don't forget the [[Conozco Uruguay Tour|pre-summit tour Apr 30 - May 5,]] as well as post-summit codesprint May 8/9 onwards -- dates are final but details are evolving!'''

== Main goals ==
* '''Focus on developers'''. It does not mean at all we're not concerned about educational aspects, but as a developers community we have huge challenges and the summit will be more of a working instance than a "reflection" instance.
* '''Exceed OLPC and Sugar'''. The developers community goes beyond OLPC and Sugar, and this could be a good instance for bringing "non-olpc organizations" to the conversation.
* '''Focus on South America'''. Bring as many south american developers as possible to Uruguay.

== Program ==
A first sketch of the event (''preliminary,'' [http://ceibaljam.org/drupal/?q=node/1127 see also update here!]) is as follows:
Program committee:
* Andrés Ambrois
* Walter Bender
* Gabriel Eirea
* Pablo Flores
* Gonzalo Odiard
* Fernando Sansberro

== Pre-Summit "Conozco Uruguay" Exploration Tour ==
We're organizing a set of in-person activities for those who want to know more about the Uruguayan/Ceibal experience, visiting different points of the country, meeting with families, teachers, etc.

This will happen during the 5-6 days prior to the summit (from Saturday April 30th to Thursday May 5th) for independent and resilient travelers, committed to "anthropological" learning through patient exploration -- [[Conozco Uruguay Tour|details are emerging here!]]

== Attendees ==
Attendees and possible attendees list in: http://ceibaljam.org/drupal/?q=node/1108 
If you want to attend, please write us: edujam2011@ceibaljam.org

Including Volunteer Organizers: Martín Abente, Walter Bender, Gabriel Eirea, David Farning, Pablo Flores, [[user:Holt|Adam Holt]], Bernie Innocenti, Aleksey Lim, Anish Mangal, Gonzalo Odiard, [[user:aa|Andrés Ambrois]]

== Accommodation ==
We'll put here some information about possible places for staying. At the same time we'll make a volunteers hosting program, so Uruguayan volunteers can host some of the attendees. More information soon.

Uruguay (generally) uses [http://treehouse.ofb.net/go/en/voltage/Uruguay 220V European] [http://www.adaptelec.com/index.php?main_page=document_general_info&products_id=252 electrical outlets] so please consider bringing a small converter.

Wifi access will be sought where possible, but not guaranteed.

== Registration ==
[http://ceibaljam.org/drupal/?q=edujam2011_en Registration is now Open!]

As explained therein, pricing is $100, with confirmed volunteers/students paying $30 or $10. Attendance will likely be limited to about 100 attendees maximum.

Flight prices will rise, so we strongly encourage you to book your flight to Montevideo (MVD) & register today!

== Uruguay ==

Visas are [http://worldtravelguide.net/uruguay/passport-visa not required] for most US, Canada, Europe, Australia citizens.

Direct flights to Montevideo (Carrasco Airport) from:
* US: Miami
* Europe: Madrid
* Most of South America
* Nearby hubs: Buenos Aires, Sao Paulo, Santiago
There are also nice ferries from Buenos Aires: http://www.buquebus.com/

An airport departure tax of $30+ may be charged upon leaving Uruguay, if not pre-paid within your flight ticket.

Touristic information: http://www.turismo.gub.uy

Don't forget to register for "Conozco Uruguay", our [[Conozco Uruguay Tour|pre-summit eduTRIP!]] (Saturday April 30 - Thursday May 5)

==Discussion==

Caryl Bigenho has posted some really great suggestions & topics on the [[Talk:Uruguay_Summit_2011|Talk Page]] -- eg. she started with "fun" activities for teachers, students, and parents to participate in alongside software architects -- please join her to [[Talk:Uruguay_Summit_2011|share your own ideas, for things you'd like to do at EduJAM!]]

EduJAM/2011

2011-05-14T22:29:29Z

ChristophD: added link to Aaron's photos on Flickr

{{Translations}}
'''Thanks to all participants of eduJAM! 2011 (5-7 May 2011) // Gracias a todos los participantes del eduJAM! 2011 (5-7 Mayo 2011)'''
[[File:Edujam-final.jpg|800px]]

== Summit page // Página del evento ==
'''Home page of the summit: http://edujam2011.ceibaljam.org/edujam2011_en // Página principal del evento: http://edujam2011.ceibaljam.org'''

== Photos of the summit / Fotos del encuentro ==

http://www.flickr.com/photos/62554468@N03/sets/72157626586497313/with/5716105406/
* http://picasaweb.google.com/pflores2/EduJAM2011#
* http://www.flickr.com/photos/christophd/sets/72157626514302097/with/5685214622/
* http://www.flickr.com/photos/madprime/
* http://codewiz.org/wiki/pictures/conf/EduJAM-2011
* http://www.flickr.com/x/t/0090009/photos/luzanone/sets/72157626656559110/
* http://picasaweb.google.com/ebordon/EduJam?authkey=Gv1sRgCLK9jtmCy7qH9QE#
* https://picasaweb.google.com/110361379457702390492/May132011?authkey=Gv1sRgCKbs2a_N-6SElwE# (captions to be added)

== Presentations ==

* http://www.slideshare.net/eduJam2011/presentations
* http://www.slideshare.net/search/slideshow?type=presentations&q=edujam

== Videos ==

* http://www.dailymotion.com/sugarlabs
* http://blog.printf.net/articles/2011/05/14/edujam-2011

== Press/blogosphere // Prensa/blogósfera ==
After event // Luego del evento:

eduJAM! 2011 & Sugar Code Sprint
* http://www.olpcnews.com/countries/uruguay/lapix_an_electronic_pen_accessory.html

Conozco Uruguay Tour:
* http://olpcuruguay2011.wordpress.com/ Note: You are invited to add your comments and articles to this group blog. There are 4 admins, so one of them will approve it for you.

Before event // Antes del evento:
* Puesta a punto de un encuentro vibrante con varias ofertas http://ceibaljam.org/drupal/?q=node/1173

== Misc ==
* Etherpad: http://etherpad.tugraz.at/NpJPnsS68L
* Projects show in the opening // Proyectos expuestos en la apertura: http://ceibaljam.org/node/1333
* list public archive: http://box541.bluehost.com/pipermail/all-edujam2011_ceibaljam.org/
* Look for #edujam in twitter: http://twitter.com/#!/search/edujam
* Related files // Archivos relacionados: http://ceibaljam.org/drupal/?q=node/1323

== Attendees - Please add info & link adresses // Asistentes - Por favor agreguen info & link ==
Argentina:
* María Abramovich
* Cynthia Casal
* Martin Langhoff, Argentina/Miami
* Alvar Maciel
* Laura Manolakis
* Gonzalo Odiard
* Manuel Quiñones
* Lucía Zanone
Austria:
* Christoph Derndorfer, Vienna/Madrid
Bolivia:
* Vladimir Castro Salas, Bolivia/Perú
Chile:
* Patricio Acevedo http://wiki.sugarlabs.org/go/Sugar_Labs_Chile
* Werner Westermann
Colombia:
* Rafael Ortiz, Colombia
* Bianca Suárez
El Salvador:
* Douglas Cerna, El Salvador
Francia:
* Bastien Guerry
Germany // Alemania
* Bert Freudenberg, Germany
* Simon Schampijer, Germany
Paraguay:
* Martín Abente http://wiki.sugarlabs.org/go/User:Tch
* Rodolfo Arce
Perú:
* Sebastián Silva, Perú/Colombia
India:
* Anish Mangal, India/Paraguay
Italia:
* Bernie Innocenti, Italy/USA
Uruguay:
* Micaela Acosta, ceibalJAM!
* Alan Aguiar, Butiá
* Andrés Aguirre, Butiá
* Andrés Ambrois, ceibalJAM!/Hackspace Montevideo http://wiki.laptop.org/index.php?title=User:Aa
* Federico Andrade, Butiá
* Barbanegra, Hackspace Montevideo
* Esteban Arias, Plan Ceibal
* Paolo Benini, RAP
* Esteban Bordón, Plan Ceibal
* Inés Bouvier, Flor de Ceibo
* Roxana Castellano, Creática
* Daniel Castelo, Plan Ceibal
* Gabriel Eirea, ceibalJAM!
* Ignacio Escudero, RAP
* Luciano Ferrari, Plan Ceibal
* Pablo Flores, ceibalJAM!
* Bernabé García, Hackspace Montevideo
* Sandra González, Plan Ceibal
* Ruben Ingver
* Karen López, Plan Ceibal
* Rocío Medina, RAP
* Luis Michelena, ceibalJAM!
* Oscar Nieto, RAP
* Evelyn Pelufo, Plan Ceibal
* Jesusa Pereira
* Eugenia Pinilla, Plan Ceibal
* Carlos Rabassa, RAP
* Nenny Rabassa, RAP
* Rosamel Ramirez
* Alejandro Rodríguez, ceibalJAM!
* Christofer Roibal, ceibalJAM!
* Leticia Romero, RAP/ceibalJAM!
* Fernando Sansberro
* Gonzalo Tejera, Butiá
* Victoria Torena, Plan Ceibal
* Guzmán Trindad
USA:
* Tony Anderson Texas/Nepal/Rwanda
* Chris Ball, OLPC, Boston
* Walter Bender, Sugar Labs
* Caryl Bigenho
* Ed Bigenho
* Aaron Borden, San Francisco
* Nick Doiron, New Hampshire/Uganda/Uruguay
* David Farning, USA
* Adam Holt, OLPC, Sugar Labs, USA
* Mr. Holt
* C. Scott Ananian, OLPC, Boston
* John Tierney, OLPC
Rusia:
* Aleksey Lim
Rwanda:
* Nkubito Bakuramutsa, Rwanda

= Information written during the organization of the summit =

This page is for planning the EduJAM! summit in Uruguay May 5th to 7th 2011.

'''Don't forget the [[Conozco Uruguay Tour|pre-summit tour Apr 30 - May 5,]] as well as post-summit codesprint May 8/9 onwards -- dates are final but details are evolving!'''

== Main goals ==
* '''Focus on developers'''. It does not mean at all we're not concerned about educational aspects, but as a developers community we have huge challenges and the summit will be more of a working instance than a "reflection" instance.
* '''Exceed OLPC and Sugar'''. The developers community goes beyond OLPC and Sugar, and this could be a good instance for bringing "non-olpc organizations" to the conversation.
* '''Focus on South America'''. Bring as many south american developers as possible to Uruguay.

== Program ==
A first sketch of the event (''preliminary,'' [http://ceibaljam.org/drupal/?q=node/1127 see also update here!]) is as follows:
Program committee:
* Andrés Ambrois
* Walter Bender
* Gabriel Eirea
* Pablo Flores
* Gonzalo Odiard
* Fernando Sansberro

== Pre-Summit "Conozco Uruguay" Exploration Tour ==
We're organizing a set of in-person activities for those who want to know more about the Uruguayan/Ceibal experience, visiting different points of the country, meeting with families, teachers, etc.

This will happen during the 5-6 days prior to the summit (from Saturday April 30th to Thursday May 5th) for independent and resilient travelers, committed to "anthropological" learning through patient exploration -- [[Conozco Uruguay Tour|details are emerging here!]]

== Attendees ==
Attendees and possible attendees list in: http://ceibaljam.org/drupal/?q=node/1108 
If you want to attend, please write us: edujam2011@ceibaljam.org

Including Volunteer Organizers: Martín Abente, Walter Bender, Gabriel Eirea, David Farning, Pablo Flores, [[user:Holt|Adam Holt]], Bernie Innocenti, Aleksey Lim, Anish Mangal, Gonzalo Odiard, [[user:aa|Andrés Ambrois]]

== Accommodation ==
We'll put here some information about possible places for staying. At the same time we'll make a volunteers hosting program, so Uruguayan volunteers can host some of the attendees. More information soon.

Uruguay (generally) uses [http://treehouse.ofb.net/go/en/voltage/Uruguay 220V European] [http://www.adaptelec.com/index.php?main_page=document_general_info&products_id=252 electrical outlets] so please consider bringing a small converter.

Wifi access will be sought where possible, but not guaranteed.

== Registration ==
[http://ceibaljam.org/drupal/?q=edujam2011_en Registration is now Open!]

As explained therein, pricing is $100, with confirmed volunteers/students paying $30 or $10. Attendance will likely be limited to about 100 attendees maximum.

Flight prices will rise, so we strongly encourage you to book your flight to Montevideo (MVD) & register today!

== Uruguay ==

Visas are [http://worldtravelguide.net/uruguay/passport-visa not required] for most US, Canada, Europe, Australia citizens.

Direct flights to Montevideo (Carrasco Airport) from:
* US: Miami
* Europe: Madrid
* Most of South America
* Nearby hubs: Buenos Aires, Sao Paulo, Santiago
There are also nice ferries from Buenos Aires: http://www.buquebus.com/

An airport departure tax of $30+ may be charged upon leaving Uruguay, if not pre-paid within your flight ticket.

Touristic information: http://www.turismo.gub.uy

Don't forget to register for "Conozco Uruguay", our [[Conozco Uruguay Tour|pre-summit eduTRIP!]] (Saturday April 30 - Thursday May 5)

==Discussion==

Caryl Bigenho has posted some really great suggestions & topics on the [[Talk:Uruguay_Summit_2011|Talk Page]] -- eg. she started with "fun" activities for teachers, students, and parents to participate in alongside software architects -- please join her to [[Talk:Uruguay_Summit_2011|share your own ideas, for things you'd like to do at EduJAM!]]

Sugar on a Stick/Blueberry/Activities

2010-04-08T17:43:07Z

ChristophD:

Sugar on a Stick comes with a lot of pre-installed activities (and many more can be added via [http://activities.sugarlabs.org/ activities.sugarlabs.org]):

* Arithmetic
* Browse
* Calculate
* CartoonBuilder
* Chat
* Clock
* Colors
* EToys
* FlipSticks
* FoodForce2
* FreeCell
* GetIABooks
* ImageViewer
* InfoSlicer
* IRC
* JigsawPuzzle
* JokeMachine
* Jukebox
* Labyrinth
* Log
* Maze
* Memorize
* Moon
* Oficina
* Paint
* Pippy
* Physics
* Poll
* Read
* ReadETexts
* Record
* Scratch
* SliderPuzzle
* Sliderule
* SocialCalc
* Speak
* StoryBuilder
* TamTamEdit
* TamTamJam
* TamTamMini
* TamTamSynthLab
* Terminal
* TurtleArt
* TypingTurtle
* ViewSlides
* VisualMatch
* Write

Sugar on a Stick/Blueberry/Activities

2010-04-08T17:39:31Z

ChristophD:

Sugar on a Stick comes with a lot of pre-installed activities:

* Arithmetic
* Browse
* Calculate
* CartoonBuilder
* Chat
* Clock
* Colors
* EToys
* FlipSticks
* FoodForce2
* FreeCell
* GetIABooks
* ImageViewer
* InfoSlicer
* IRC
* JigsawPuzzle
* JokeMachine
* Jukebox
* Labyrinth
* Log
* Maze
* Memorize
* Moon
* Oficina
* Paint
* Pippy
* Physics
* Poll
* Read
* ReadETexts
* Record
* Scratch
* SliderPuzzle
* Sliderule
* SocialCalc
* Speak
* StoryBuilder
* TamTamEdit
* TamTamJam
* TamTamMini
* TamTamSynthLab
* Terminal
* TurtleArt
* TypingTurtle
* ViewSlides
* VisualMatch
* Write

Sugar on a Stick/Blueberry/Activities

2010-04-08T17:31:45Z

ChristophD:

Sugar on a Stick comes with a lot of pre-installed activities:

* Arithmetic
* Browse
* Calculate
* CartoonBuilder
* Chat
* Clock
* Colors
* FlipSticks
* FoodForce2
* FreeCell
* GetIABooks
* ImageViewer
* InfoSlicer
* IRC
* JigsawPuzzle
* JokeMachine
* Jukebox
* Labyrinth
* Log
* Maze
* Memorize
* Moon
* Oficina
* Pippy
* Physics
* PollBuilder
* Read
* ReadETexts
* Record
* Scratch
* SliderPuzzle
* Sliderule
* SocialCalc
* Speak
* StoryBuilder
* TamTamEdit
* TamTamJam
* TamTamMini
* TamTamSynthLab
* Terminal
* TurtleArt
* TypingTurtle
* ViewSlides
* VisualMatch
* Write

Sugar on a Stick/Blueberry/Activities

2010-04-08T17:30:00Z

ChristophD: Created page with 'Sugar on a Stick comes with a lot of pre-installed activities: * Browse * Calculate * CartoonBuilder * Chat * Colors * FlipSticks * FreeCell * ImageViewer * InfoSlicer * IRC * J…'

Sugar on a Stick comes with a lot of pre-installed activities:

* Browse
* Calculate
* CartoonBuilder
* Chat
* Colors
* FlipSticks
* FreeCell
* ImageViewer
* InfoSlicer
* IRC
* JigsawPuzzle
* JokeMachine
* Jukebox
* Labyrinth
* Log
* Maze
* Memorize
* Moon
* Pippy
* PollBuilder
* Read
* ReadETexts
* Record
* SliderPuzzle
* Speak
* StoryBuilder
* TamTamEdit
* TamTamJam
* TamTamMini
* TamTamSynthLab
* Terminal
* TurtleArt
* TypingTurtle
* ViewSlides
* Write

Marketing Team/Events/LinuxTag2010

2010-01-05T02:07:10Z

ChristophD: /* Attendees */

{{TOCright}}

= LinuxTag 2010 =

[http://www.linuxtag.org/2010/en.html http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/images/linuxtag-logo/LinuxTag-Logo-plain-blue.png]

== Event Details ==
LinuxTag is the most important place for Linux and open source software in Europe. In 2010, the 16th LinuxTag presents news for professional users, decision makers, developers, beginners and the Linux community - from '''9th until 12th June''' on the Fairground in Berlin.
For more information, go to the [http://www.linuxtag.org/2010/en.html LinuxTag 2010 website].

[http://www.linuxtag.org/2010/en/besucher/reiseplanung.html Here] are instructions how you get to Linuxtag.

== Sugar Organizer ==

[[User:Erikos | Simon Schampijer]] will be organizing Sugar's presence at LinuxTag 2010.

== Attendees ==

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

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! available from to !! stays at !! Note
|-
! [[User:Erikos | Simon Schampijer]]
| - || local || -
|-
! [[User:ChristophD | Christoph Derndorfer]]
| - || local || yet to be confirmed
|-
|}

== Sugar Activities ==
Sugar does advocate the concepts of activities - you learn through doing, so if you want more learning you want more doing. So the Sugar Labs team wants to get engaged at Linuxtag:

# We will aim to have a booth like last year
# There should be talks about Sugar, too

== Sugar Booth ==
''to be determined''



=== Shifts ===
''to be determined''


=== Storage Space ===
We have a coops (Germans would say Kabüffchen as a diminutive of Kabuff) at the booths. As this is only meant for booth equipment all the other belongings like jackets, luggage etc can be stored at the wardrobe without any cost.

=== Power and Internet Connectivity ===
Power and Internet will be provided by LinuxTag and Messe Berlin for the project booths. What we need are:
* extension cords
* long network cables
* switches

Not permitted by Linuxtag:
* wireless access points (You are not permitted to operate your private wireless LAN. Please take this serious. There will be several site surveys to ensure this.) - Mesh networking is allowed though
* coffeemakers, kettles and cooking stuff
* connect visitors to the project's network

=== Lunch ===
Linuxtag is offering Lunch for the helpers. If we want to participate we would need helpers and not only eaters. More information can be found [http://wiki.linuxtag.org/w/fp:Lunch_2009 at].

=== Flyer ===
* [[Media:Flyer_deutsch.pdf | german version PDF]]
* [[Media:Flyer_englisch.pdf | englisch version PDF]]

== TODO ==
''to be determined''

== Equipment ==
* Sugar Labs Booth Banner
* Sugar Labs balloons
* Flyers

== Lodging ==
* Accommodation Information from [http://www.linuxtag.org/2008/en/visitors/travel.html Linuxtag]
* [http://www.pension-freiraum.de/ Pension Freiraum]
** Nice area with bars restaurant cafe, about 25 minutes to the conference
* [http://www.hotel-funkturm-messe.de/english/home.html Hotel Funkturm]
** right next door to the conference area (room 4-6 persons, 100euro per night for the room, inclusive breakfast)

== Schedule ==
''to be determined''



== Impressions ==
''link your photos, add your comments here''

[[Category:Event]]

Karma:Meeting 08 Sep 2009

2009-09-07T09:50:12Z

ChristophD:

# Joshua Gay's involvement
# road to v0.1 (due on Friday!)
## which areas need most attention until then?
# status of subzero's paperwork for his thesis
# look at Chakra / knavbar
## any changes desired?
# help functionality

Karma:Meeting 08 Sep 2009

2009-09-07T09:44:11Z

ChristophD: Created page with '# Joshua Gay's involvement # road to v0.1 (due on Friday!) ## which areas need most attention until then? # status of subzero's paperwork for his thesis # look at Chakra / knavba…'

Karma

2009-09-07T09:42:21Z

ChristophD: /* Meetings */

<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>
[[Image:Karma.png|right]]

== The Karma Project ==

=== Rationale ===

Anyone with a modern standards-compliant web browser and a text editor should be able to create learning activities that can be used by anyone with a computer. Sugar should not be a walled garden that only allows learning activities expressly designed for it and it alone but rather gives extra power and depth to learning activities. Karma uses a specialized vocabulary that features a number of specialized terms. Please refer to the [[Karma/Dictionary|Karma Dictionary]] early and often.

=== Status ===

Karma is a sub-project of Sugar Labs that is under active development as a part of a [[Karma#GSoC_Project| Google Summer of Code project]]. The latest examples can be seen at [http://karma.sugarlabs.org http://karma.sugarlabs.org]. You can also check out the [http://karmaproject.wordpress.com Karma Project blog] for updates.

To try out the karma examples you need to have an html5-capable browser. The Browse activity within Sugar does not currently support html5. To try out karma within Sugar you need to install [http://dev.laptop.org/~bobbyp/surf/Surf-106.xo Surf] and its webkit dependencies or run Firefox 3.5 from the command-line.

=== What Karma Is ===

* Karma is a simple framework to create simple interactive learning activities primarily for Sugar but also to be viewable through any web browser that supports html5
* Karma is used to create simple activities that run off-line w/out access to the Internet
* Karma is for web developers who want to contribute to Sugar using their current skills
* Karma is built on top of open web standards such as html5, javascript, and CSS.
* Karma is built to run on top of web browsers that support html5, particularly the canvas element.
* Karma is built around the concept of individual "lessons" and multiple lessons can be aggregated into a sugar activity
* Karma is the evolution of OLE Nepal's work on the EPaath suite of lessons in Nepal
* Karma is designed with pervasive and easy internationalizaton in mind and integration with moodle, particularly for monitoring student progress
* Karma is pedagogically agnostic. Pedagogical choices are left to the lesson author.

=== What Karma Isn't ===

* Karma is not meant to replace pyGTK as the dominant toolset for creating Sugar activities
* Karma is not a tool for creating activities with complex 3D graphics. Karma is a tool for creating activities with simple 2D graphics
* Karma is not meant as a basis for a WYSIWG programming environment like TurtleArt, EToys, or Logo
* Karma is not built to support browsers that do not support html5, such as Internet Explorer and Firefox < version 3.5
* Karma is not intended to teach programming to children though it could be used as such

=== Design Philosophy ===

A Karma lesson is composed of a valid html5 document, javascript code, and css stylesheets and optional assets such as images, audio, video and lesson plans. Karma should be very easy for inexperienced developers to understand and work with. Even non-programmers should be able to make visible changes by tweaking the code and liberal use of cut-and-paste. Complexities such as integration with pootle, local storage, and certain types of animation should be abstracted so that novice developers don't have to understand them in order to effectively use Karma. Karma strictly adheres to the Model-View-Controller Pattern and similarly to unobtrusive JavaScript. In essence. you should be able to substantially change the look and feel of a Karma lesson by modifying the CSS or you could translate the activity, without having to understand the JavaScript code.

=== Design Goals ===
* Unobtrusive JavaScript
* No globals
* No native objects extension

=== Technical Architecture ===

* Run-time - Karma will work with basic functionality on any W3C standards-compliant browser that supports HTML5 tags canvas and audio. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within Sugar's [[Browse]] activity. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.
* Primary Programming language - Javascript ([https://developer.mozilla.org/En/JavaScript 1.8.1]) Karma depends heavily the javascript library jQuery, version 1.3.
* [[Karma/i18n|i18n]] -- Pervasive internationalization is a critical part of Karma
** Supported types of i18n
*** Output of Native Digits
*** Image switching per locale
*** Regular text, though it is unclear how to support plural forms, grammar shifts, and gender
*** Audio switching per locale
** Integration with pootle
* [[Karma/Utilities|Utilities]] -- we primarily use [http://www.narwhaljs.org narwhal] for command-line scripting and [http://code.google.com/p/jsdoc-toolkit/ jsdoc] for documentation
* Journal, Telepathy Integration -- method to be determined, perhaps using html5's offline storage feature, some resources [https://developer.mozilla.org/en/Offline_resources_in_Firefox here] and [http://www.weboshelp.net/webos-tutorials/156-palm-webos-html5-database-storage-tutorial here]
* Moodle Integration -- method to be determined
* [[Karma/Bundle_layout|Repo and Bundle layout]]

=== Conventions ===

* [[Karma:Anatomy_of_Lesson|Anatomy of a Karma Lesson]]
* The [[Karma/Dictionary|Karma Dictionary]]
* [[Karma/Specifications|Karma Specifications]] (early draft)
* Source Code stored in http://git.sugarlabs.org/projects/karma
* Working demos at http://karma.sugarlabs.org
* Project Documentation kept in the Sugar Labs wiki
* Coding conventions: Based in [http://www.gnu.org/prep/standards/standards.html GNU standards]
** Use camel-case for function names and variables
** Exception to above -- object constructors should start with a capital letter
** Set column-width to 79 characters (from Python standard practice)
** Whenever possible, use jslint and then teach the rest of us how
** Anything Doug Crockford advises in "JavaScript: The Good Parts"
* File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)

== GSoC Project ==

=== Team ===

Felipe Lopez Toledo "SubZero" is creating a prototype for Karma as a Google Summer of Code project. [[USER:BryanWB| Bryan Berry]] is serving as his mentor. [[User:ChristophD| Christoph Derndorfer]] is working on the draft specification.

=== [[Karma/To-Do|To-Do]] ===

=== Project Requirements ===

* Create a single prototype activity which could be used as a template for sugarizing AJAX activities. The GSoC participant should not create her own activity but recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This prototype should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An [[Karma/Assessment| assessment]] section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Uses simple html for the activity lesson plan and teacher notes.
** Integrates with the Journal
** Navigation and Help elements, ideally reusing widgets from [http://www.jquery.com jQuery]
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

=== Meetings ===

# Regular meeting between Felpe and Bryan every Tuesday 0215 UTC at #sugar on irc.freenode.net
# General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting

Meeting Notes
* [[Karma:Meeting 12 May 2009]]
* [[Karma:Meeting 02 Jun 2009]]
* [[Karma:Meeting 09 Jun 2009]]
* [[Karma:Meeting 23 Jun 2009]]
* [[Karma:Meeting 30 Jun 2009]]
* [[Karma:Meeting 21 Jul 2009]]
* [[Karma:Meeting 4 Aug 2009]]
* [[Karma:Meeting 11 Aug 2009]]
* [[Karma:Meeting 18 Aug 2009]]
* [[Karma:Meeting 24 Aug 2009]]
* [[Karma:Meeting 08 Sep 2009]]

=== Project Plan ===

==== GSoC ====
There are roughly 4 parts to this project plan: first get create a very simple learning activity with javascript and html5, second get that activity running on the XO, third extend the activity to take advantage of Sugar-specific features such as the Journal and Collaboration.

Before GSoc - June 1:
* get familiar with Sugar
* get familiar with html5
* Felipe to acquire XO
* learn more about JavaScript
* select the appropriate js framework -- jQuery

June 2 - June 12:
# “Karming” the "Quadrilaterals" activity using a non-elegant approach
# Post blog entry detailing challenges encountered and ideas on how to simplify the animation methods
# Post message to jquery-en and jquery-dev mailing lists asking for feedback

June 13 - July 12:
* Developing the first Karma widget (easy animation tool, boost animation tool from the selected js framework)
* Getting familiar with Sugar/Browse code
* Providing Karma + audio
* Providing Karma + client-side i18n
* Developing an activity template for Karma
* Changing the original activity to include above features

July 13:
Publish blog post that showcases updated activity. Explain problems encountered, what works, what still doesn’t.

July 15 - July 25:
* Fixing bugs
* Work on gears+karma support

July 26 - July 31:
* Documenting examples
* Improving documentation

August 1 - August 9: time for any eventual emergencies

==== KCD's remaining time in Nepal ====

from August 21 - Sept 10th

# Work on basic layout
#* html versions of chakra, lesson_nav
#* Examples of lesson_text, lesson_plan, teacher's note for "adding_up_to_10"
# The Karma specification
#* put it in separate page
#* document what needs to be done and post various ideas and problems

==== Subzero's University Thesis ====

Deadline: December 30th

Goals: i18n mechanism, animation support, several good examples
* i18n mechanism: i18n on Karma Objects, inline html i18n, html2po tool

==== Roadmap to 0.1 ====

TBD

=== Library ===

here lies a lot of links to resources specific to karma

UI
* Iphone Human Interface Guide http://developer.apple.com/iphone/library/documentation/userexperience/conceptual/mobilehig/MobileHIG.pdf
* Palm Pre interface guide http://developer.palm.com/images/palm/pdf/palm_webos_hi_guidelines.pdf
* 30 Usability Issues To Be Aware Of http://www.smashingmagazine.com/2007/10/09/30-usability-issues-to-be-aware-of/
* 10 Usability Nightmares You Should Be Aware Of http://www.smashingmagazine.com/2007/09/27/10-usability-nightmares-you-should-be-aware-of/
* "The Design of Everyday Things" book by Don Norman
* "Don't Make me think" by Steve Krug, guide to usability for web apps

HTML5
* http://www.smashingmagazine.com/2009/07/16/html5-and-the-future-of-the-web/
* http://www.w3.org/TR/html5-diff/ Differences between html4 and html5

General Web Design
* "Web Design in a Nutshell" from O'Reilly
* Apple "Web Page Development: Best Practices" http://developer.apple.com/internet/webcontent/bestwebdev.html

Canvas
* demos: http://html5demos.com/
* basics: http://dev.opera.com/articles/view/html-5-canvas-the-basics/
* painting web app: http://dev.opera.com/articles/view/html5-canvas-painting/
* mozilla canvas tutorial: https://developer.mozilla.org/en/Canvas_tutorial
* using canvas on webkit: http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/Canvas.html
* http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html

Javascript
* "Javascript: The Good Parts" book by Doug Crockford
* "jQuery in Action" book
* "Pro Javascript Techniques" by john resig
* All the tutorials at www.ejohn.org, esp.
** http://ejohn.org/blog/how-javascript-timers-work/

Coding Tools and Conventions
* Venkman -- javascript debugger http://www.svendtofte.com/code/learning_venkman/
* Firebug --- http://www.getfirebug.com
* For emacs users -- nxhtml mode and magit.el for working w/ git

== Subpages ==

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

[[Category:GSoC]]

Karma/Dictionary

2009-09-07T03:53:18Z

ChristophD:

;activity text: blue-print for the activity and contains every piece of information the developers need to implement the activity
; assets: multimedia objects such as images, sounds and videos that are used in Karma lessons
; bundle: a collection of lessons, possibly also including Karma utilities and a HTML 5 capable browser (see [[Karma/Bundle_layout]] for more details)
; Chakra: landing page (formerly known as MenuStage in E-Paath)
; exercise: exercise is where the student gets to assess how well she has learned the content of the lesson
; game: a fun way to explore the material introduced in the lesson which helps in the learning objective
; help text: accompanying online help within Karma
; klayer: a drawing space in a karma lesson that encapsulates the properties and methods of both the canvas element and its associated drawing context
; knavbar: lesson navigation
; kpage: an individual page within a lesson
; kpagenav: page navigation within lessons
; kstart: the landing / start page of a Karma lesson
; lesson: a self-contained unit of Karma content
; lesson plan: detailed overview of how teachers can use the activity in the classroom, which homework can be assigned to pupils, etc.
; review: a page containing the assessment and scores of past lessons
; teacher's note: document detailing learning goals, (possibly) links to related school book contents, ideas for preceding and follow-up activities, etc.
; tutorial: the first part of the lesson that introduces the concepts of the lesson
; [http://en.wikipedia.org/wiki/Unobtrusive_JavaScript unobtrusive javascript]

Karma/Dictionary

2009-09-04T08:14:11Z

ChristophD:

;activity text: blue-print for the activity and contains every piece of information the developers need to implement the activity
; assets: multimedia objects such as images, sounds and videos that are used in Karma lessons
; bundle: a collection of lessons, possibly also including Karma utilities and a HTML 5 capable browser (see [[Karma/Bundle_layout]] for more details)
; Chakra: landing page (formerly known as MenuStage in E-Paath)
; exercise: exercise is where the student gets to assess how well she has learned the content of the lesson
; game: a fun way to explore the material introduced in the lesson which helps in the learning objective
; help text: accompanying online help within Karma
; klayer: a drawing space in a karma lesson that encapsulates the properties and methods of both the canvas element and its associated drawing context
; knavbar: lesson navigation
; kpage: an individual page within a lesson
; kpagenav: page navigation within lessons
; lesson: a self-contained unit of Karma content
; lesson plan: detailed overview of how teachers can use the activity in the classroom, which homework can be assigned to pupils, etc.
; review: a page containing the assessment and scores of past lessons
; teacher's note: document detailing learning goals, (possibly) links to related school book contents, ideas for preceding and follow-up activities, etc.
; tutorial: the first part of the lesson that introduces the concepts of the lesson
; [http://en.wikipedia.org/wiki/Unobtrusive_JavaScript unobtrusive javascript]

Karma

2009-09-03T10:39:01Z

ChristophD: /* Library */

<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>
[[Image:Karma.png|right]]

== The Karma Project ==

=== Rationale ===

Anyone with a modern standards-compliant web browser and a text editor should be able to create learning activities that can be used by anyone with a computer. Sugar should not be a walled garden that only allows learning activities expressly designed for it and it alone but rather gives extra power and depth to learning activities. Karma uses a specialized vocabulary that features a number of specialized terms. Please refer to the [[Karma/Dictionary|Karma Dictionary]] early and often.

=== Status ===

Karma is a sub-project of Sugar Labs that is under active development as a part of a [[Karma#GSoC_Project| Google Summer of Code project]]. The latest examples can be seen at [http://karma.sugarlabs.org http://karma.sugarlabs.org]. You can also check out the [http://karmaproject.wordpress.com Karma Project blog] for updates.

To try out the karma examples you need to have an html5-capable browser. The Browse activity within Sugar does not currently support html5. To try out karma within Sugar you need to install [http://dev.laptop.org/~bobbyp/surf/Surf-106.xo Surf] and its webkit dependencies or run Firefox 3.5 from the command-line.

=== What Karma Is ===

* Karma is a simple framework to create simple interactive learning activities primarily for Sugar but also to be viewable through any web browser that supports html5
* Karma is used to create simple activities that run off-line w/out access to the Internet
* Karma is for web developers who want to contribute to Sugar using their current skills
* Karma is built on top of open web standards such as html5, javascript, and CSS.
* Karma is built to run on top of web browsers that support html5, particularly the canvas element.
* Karma is built around the concept of individual "lessons" and multiple lessons can be aggregated into a sugar activity
* Karma is the evolution of OLE Nepal's work on the EPaath suite of lessons in Nepal
* Karma is designed with pervasive and easy internationalizaton in mind and integration with moodle, particularly for monitoring student progress
* Karma is pedagogically agnostic. Pedagogical choices are left to the lesson author.

=== What Karma Isn't ===

* Karma is not meant to replace pyGTK as the dominant toolset for creating Sugar activities
* Karma is not a tool for creating activities with complex 3D graphics. Karma is a tool for creating activities with simple 2D graphics
* Karma is not meant as a basis for a WYSIWG programming environment like TurtleArt, EToys, or Logo
* Karma is not built to support browsers that do not support html5, such as Internet Explorer and Firefox < version 3.5
* Karma is not intended to teach programming to children though it could be used as such

=== Design Philosophy ===

A Karma lesson is composed of a valid html5 document, javascript code, and css stylesheets and optional assets such as images, audio, video and lesson plans. Karma should be very easy for inexperienced developers to understand and work with. Even non-programmers should be able to make visible changes by tweaking the code and liberal use of cut-and-paste. Complexities such as integration with pootle, local storage, and certain types of animation should be abstracted so that novice developers don't have to understand them in order to effectively use Karma. Karma strictly adheres to the Model-View-Controller Pattern and similarly to unobtrusive JavaScript. In essence. you should be able to substantially change the look and feel of a Karma lesson by modifying the CSS or you could translate the activity, without having to understand the JavaScript code.

=== Design Goals ===
* Unobtrusive JavaScript
* No globals
* No native objects extension

=== Technical Architecture ===

* Run-time - Karma will work with basic functionality on any W3C standards-compliant browser that supports HTML5 tags canvas and audio. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within Sugar's [[Browse]] activity. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.
* Primary Programming language - Javascript ([https://developer.mozilla.org/En/JavaScript 1.8.1]) Karma depends heavily the javascript library jQuery, version 1.3.
* [[Karma/i18n|i18n]] -- Pervasive internationalization is a critical part of Karma
** Supported types of i18n
*** Output of Native Digits
*** Image switching per locale
*** Regular text, though it is unclear how to support plural forms, grammar shifts, and gender
*** Audio switching per locale
** Integration with pootle
* [[Karma/Utilities|Utilities]] -- we primarily use [http://www.narwhaljs.org narwhal] for command-line scripting and [http://code.google.com/p/jsdoc-toolkit/ jsdoc] for documentation
* Journal, Telepathy Integration -- method to be determined, perhaps using html5's offline storage feature, some resources [https://developer.mozilla.org/en/Offline_resources_in_Firefox here] and [http://www.weboshelp.net/webos-tutorials/156-palm-webos-html5-database-storage-tutorial here]
* Moodle Integration -- method to be determined
* [[Karma/Bundle_layout|Repo and Bundle layout]]

=== Conventions ===

* [[Karma:Anatomy_of_Lesson|Anatomy of a Karma Lesson]]
* The [[Karma/Dictionary|Karma Dictionary]]
* [[Karma/Specifications|Karma Specifications]] (early draft)
* Source Code stored in http://git.sugarlabs.org/projects/karma
* Working demos at http://karma.sugarlabs.org
* Project Documentation kept in the Sugar Labs wiki
* Coding conventions: Based in [http://www.gnu.org/prep/standards/standards.html GNU standards]
** Use camel-case for function names and variables
** Exception to above -- object constructors should start with a capital letter
** Set column-width to 79 characters (from Python standard practice)
** Whenever possible, use jslint and then teach the rest of us how
** Anything Doug Crockford advises in "JavaScript: The Good Parts"
* File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)

== GSoC Project ==

=== Team ===

Felipe Lopez Toledo "SubZero" is creating a prototype for Karma as a Google Summer of Code project. [[USER:BryanWB| Bryan Berry]] is serving as his mentor. [[User:ChristophD| Christoph Derndorfer]] is working on the draft specification.

=== [[Karma/To-Do|To-Do]] ===

=== Project Requirements ===

* Create a single prototype activity which could be used as a template for sugarizing AJAX activities. The GSoC participant should not create her own activity but recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This prototype should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An [[Karma/Assessment| assessment]] section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Uses simple html for the activity lesson plan and teacher notes.
** Integrates with the Journal
** Navigation and Help elements, ideally reusing widgets from [http://www.jquery.com jQuery]
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

=== Meetings ===

# Regular meeting between Felpe and Bryan every Tuesday 0215 UTC at #sugar on irc.freenode.net
# General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting

Meeting Notes
* [[Karma:Meeting 12 May 2009]]
* [[Karma:Meeting 02 Jun 2009]]
* [[Karma:Meeting 09 Jun 2009]]
* [[Karma:Meeting 23 Jun 2009]]
* [[Karma:Meeting 30 Jun 2009]]
* [[Karma:Meeting 21 Jul 2009]]
* [[Karma:Meeting 4 Aug 2009]]
* [[Karma:Meeting 11 Aug 2009]]
* [[Karma:Meeting 18 Aug 2009]]
* [[Karma:Meeting 24 Aug 2009]]

=== Project Plan ===

==== GSoC ====
There are roughly 4 parts to this project plan: first get create a very simple learning activity with javascript and html5, second get that activity running on the XO, third extend the activity to take advantage of Sugar-specific features such as the Journal and Collaboration.

Before GSoc - June 1:
* get familiar with Sugar
* get familiar with html5
* Felipe to acquire XO
* learn more about JavaScript
* select the appropriate js framework -- jQuery

June 2 - June 12:
# “Karming” the "Quadrilaterals" activity using a non-elegant approach
# Post blog entry detailing challenges encountered and ideas on how to simplify the animation methods
# Post message to jquery-en and jquery-dev mailing lists asking for feedback

June 13 - July 12:
* Developing the first Karma widget (easy animation tool, boost animation tool from the selected js framework)
* Getting familiar with Sugar/Browse code
* Providing Karma + audio
* Providing Karma + client-side i18n
* Developing an activity template for Karma
* Changing the original activity to include above features

July 13:
Publish blog post that showcases updated activity. Explain problems encountered, what works, what still doesn’t.

July 15 - July 25:
* Fixing bugs
* Work on gears+karma support

July 26 - July 31:
* Documenting examples
* Improving documentation

August 1 - August 9: time for any eventual emergencies

==== KCD's remaining time in Nepal ====

from August 21 - Sept 10th

# Work on basic layout
#* html versions of chakra, lesson_nav
#* Examples of lesson_text, lesson_plan, teacher's note for "adding_up_to_10"
# The Karma specification
#* put it in separate page
#* document what needs to be done and post various ideas and problems

==== Subzero's University Thesis ====

Deadline: December 30th

Goals: i18n mechanism, animation support, several good examples
* i18n mechanism: i18n on Karma Objects, inline html i18n, html2po tool

==== Roadmap to 0.1 ====

TBD

=== Library ===

here lies a lot of links to resources specific to karma

UI
* Iphone Human Interface Guide http://developer.apple.com/iphone/library/documentation/userexperience/conceptual/mobilehig/MobileHIG.pdf
* Palm Pre interface guide http://developer.palm.com/images/palm/pdf/palm_webos_hi_guidelines.pdf
* 30 Usability Issues To Be Aware Of http://www.smashingmagazine.com/2007/10/09/30-usability-issues-to-be-aware-of/
* 10 Usability Nightmares You Should Be Aware Of http://www.smashingmagazine.com/2007/09/27/10-usability-nightmares-you-should-be-aware-of/
* "The Design of Everyday Things" book by Don Norman
* "Don't Make me think" by Steve Krug, guide to usability for web apps

HTML5
* http://www.smashingmagazine.com/2009/07/16/html5-and-the-future-of-the-web/
* http://www.w3.org/TR/html5-diff/ Differences between html4 and html5

General Web Design
* "Web Design in a Nutshell" from O'Reilly
* Apple "Web Page Development: Best Practices" http://developer.apple.com/internet/webcontent/bestwebdev.html

Canvas
* demos: http://html5demos.com/
* basics: http://dev.opera.com/articles/view/html-5-canvas-the-basics/
* painting web app: http://dev.opera.com/articles/view/html5-canvas-painting/
* mozilla canvas tutorial: https://developer.mozilla.org/en/Canvas_tutorial
* using canvas on webkit: http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/Canvas.html
* http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html

Javascript
* "Javascript: The Good Parts" book by Doug Crockford
* "jQuery in Action" book
* "Pro Javascript Techniques" by john resig
* All the tutorials at www.ejohn.org, esp.
** http://ejohn.org/blog/how-javascript-timers-work/

Coding Tools and Conventions
* Venkman -- javascript debugger http://www.svendtofte.com/code/learning_venkman/
* Firebug --- http://www.getfirebug.com
* For emacs users -- nxhtml mode and magit.el for working w/ git

== Subpages ==

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

[[Category:GSoC]]

Karma

2009-09-03T07:57:23Z

ChristophD: /* Library */

<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>
[[Image:Karma.png|right]]

== The Karma Project ==

=== Rationale ===

Anyone with a modern standards-compliant web browser and a text editor should be able to create learning activities that can be used by anyone with a computer. Sugar should not be a walled garden that only allows learning activities expressly designed for it and it alone but rather gives extra power and depth to learning activities. Karma uses a specialized vocabulary that features a number of specialized terms. Please refer to the [[Karma/Dictionary|Karma Dictionary]] early and often.

=== Status ===

Karma is a sub-project of Sugar Labs that is under active development as a part of a [[Karma#GSoC_Project| Google Summer of Code project]]. The latest examples can be seen at [http://karma.sugarlabs.org http://karma.sugarlabs.org]. You can also check out the [http://karmaproject.wordpress.com Karma Project blog] for updates.

To try out the karma examples you need to have an html5-capable browser. The Browse activity within Sugar does not currently support html5. To try out karma within Sugar you need to install [http://dev.laptop.org/~bobbyp/surf/Surf-106.xo Surf] and its webkit dependencies or run Firefox 3.5 from the command-line.

=== What Karma Is ===

* Karma is a simple framework to create simple interactive learning activities primarily for Sugar but also to be viewable through any web browser that supports html5
* Karma is used to create simple activities that run off-line w/out access to the Internet
* Karma is for web developers who want to contribute to Sugar using their current skills
* Karma is built on top of open web standards such as html5, javascript, and CSS.
* Karma is built to run on top of web browsers that support html5, particularly the canvas element.
* Karma is built around the concept of individual "lessons" and multiple lessons can be aggregated into a sugar activity
* Karma is the evolution of OLE Nepal's work on the EPaath suite of lessons in Nepal
* Karma is designed with pervasive and easy internationalizaton in mind and integration with moodle, particularly for monitoring student progress
* Karma is pedagogically agnostic. Pedagogical choices are left to the lesson author.

=== What Karma Isn't ===

* Karma is not meant to replace pyGTK as the dominant toolset for creating Sugar activities
* Karma is not a tool for creating activities with complex 3D graphics. Karma is a tool for creating activities with simple 2D graphics
* Karma is not meant as a basis for a WYSIWG programming environment like TurtleArt, EToys, or Logo
* Karma is not built to support browsers that do not support html5, such as Internet Explorer and Firefox < version 3.5
* Karma is not intended to teach programming to children though it could be used as such

=== Design Philosophy ===

A Karma lesson is composed of a valid html5 document, javascript code, and css stylesheets and optional assets such as images, audio, video and lesson plans. Karma should be very easy for inexperienced developers to understand and work with. Even non-programmers should be able to make visible changes by tweaking the code and liberal use of cut-and-paste. Complexities such as integration with pootle, local storage, and certain types of animation should be abstracted so that novice developers don't have to understand them in order to effectively use Karma. Karma strictly adheres to the Model-View-Controller Pattern and similarly to unobtrusive JavaScript. In essence. you should be able to substantially change the look and feel of a Karma lesson by modifying the CSS or you could translate the activity, without having to understand the JavaScript code.

=== Design Goals ===
* Unobtrusive JavaScript
* No globals
* No native objects extension

=== Technical Architecture ===

* Run-time - Karma will work with basic functionality on any W3C standards-compliant browser that supports HTML5 tags canvas and audio. This notably excludes Microsoft's Internet Explorer. Karma will be particularly tailored to work within Sugar's [[Browse]] activity. Longer-term we hope to extend Karma to take advantage of Sugar's collaboration features.
* Primary Programming language - Javascript ([https://developer.mozilla.org/En/JavaScript 1.8.1]) Karma depends heavily the javascript library jQuery, version 1.3.
* [[Karma/i18n|i18n]] -- Pervasive internationalization is a critical part of Karma
** Supported types of i18n
*** Output of Native Digits
*** Image switching per locale
*** Regular text, though it is unclear how to support plural forms, grammar shifts, and gender
*** Audio switching per locale
** Integration with pootle
* [[Karma/Utilities|Utilities]] -- we primarily use [http://www.narwhaljs.org narwhal] for command-line scripting and [http://code.google.com/p/jsdoc-toolkit/ jsdoc] for documentation
* Journal, Telepathy Integration -- method to be determined, perhaps using html5's offline storage feature, some resources [https://developer.mozilla.org/en/Offline_resources_in_Firefox here] and [http://www.weboshelp.net/webos-tutorials/156-palm-webos-html5-database-storage-tutorial here]
* Moodle Integration -- method to be determined
* [[Karma/Bundle_layout|Repo and Bundle layout]]

=== Conventions ===

* [[Karma:Anatomy_of_Lesson|Anatomy of a Karma Lesson]]
* The [[Karma/Dictionary|Karma Dictionary]]
* [[Karma/Specifications|Karma Specifications]] (early draft)
* Source Code stored in http://git.sugarlabs.org/projects/karma
* Working demos at http://karma.sugarlabs.org
* Project Documentation kept in the Sugar Labs wiki
* Coding conventions: Based in [http://www.gnu.org/prep/standards/standards.html GNU standards]
** Use camel-case for function names and variables
** Exception to above -- object constructors should start with a capital letter
** Set column-width to 79 characters (from Python standard practice)
** Whenever possible, use jslint and then teach the rest of us how
** Anything Doug Crockford advises in "JavaScript: The Good Parts"
* File naming conventions: lowercase letters, underscore instead of spaces (need to write more about it)

== GSoC Project ==

=== Team ===

Felipe Lopez Toledo "SubZero" is creating a prototype for Karma as a Google Summer of Code project. [[USER:BryanWB| Bryan Berry]] is serving as his mentor. [[User:ChristophD| Christoph Derndorfer]] is working on the draft specification.

=== [[Karma/To-Do|To-Do]] ===

=== Project Requirements ===

* Create a single prototype activity which could be used as a template for sugarizing AJAX activities. The GSoC participant should not create her own activity but recreate an existing activity such as one of [http://www.pustakalaya.org/external-content/static/epaath/E-Paath-2.activity/activity/Activity/MenuStage.html OLE Nepal's flash activities].
* This prototype should have the following features:
** Simple interactive animation and audio using html5 tags like <canvas> and <audio>
** An [[Karma/Assessment| assessment]] section that stores results of student's progress and gives them suggestions on improvement. Assessment info should be persistent.
** Uses simple html for the activity lesson plan and teacher notes.
** Integrates with the Journal
** Navigation and Help elements, ideally reusing widgets from [http://www.jquery.com jQuery]
** Some element of collaboration using Telepathy (This could be really hard, depending on the state of javascript bindings to dbus)

=== Meetings ===

# Regular meeting between Felpe and Bryan every Tuesday 0215 UTC at #sugar on irc.freenode.net
# General GSOC meeting for participants from Sugar every Tuesday 1400 UTC #sugar-meeting

Meeting Notes
* [[Karma:Meeting 12 May 2009]]
* [[Karma:Meeting 02 Jun 2009]]
* [[Karma:Meeting 09 Jun 2009]]
* [[Karma:Meeting 23 Jun 2009]]
* [[Karma:Meeting 30 Jun 2009]]
* [[Karma:Meeting 21 Jul 2009]]
* [[Karma:Meeting 4 Aug 2009]]
* [[Karma:Meeting 11 Aug 2009]]
* [[Karma:Meeting 18 Aug 2009]]
* [[Karma:Meeting 24 Aug 2009]]

=== Project Plan ===

==== GSoC ====
There are roughly 4 parts to this project plan: first get create a very simple learning activity with javascript and html5, second get that activity running on the XO, third extend the activity to take advantage of Sugar-specific features such as the Journal and Collaboration.

Before GSoc - June 1:
* get familiar with Sugar
* get familiar with html5
* Felipe to acquire XO
* learn more about JavaScript
* select the appropriate js framework -- jQuery

June 2 - June 12:
# “Karming” the "Quadrilaterals" activity using a non-elegant approach
# Post blog entry detailing challenges encountered and ideas on how to simplify the animation methods
# Post message to jquery-en and jquery-dev mailing lists asking for feedback

June 13 - July 12:
* Developing the first Karma widget (easy animation tool, boost animation tool from the selected js framework)
* Getting familiar with Sugar/Browse code
* Providing Karma + audio
* Providing Karma + client-side i18n
* Developing an activity template for Karma
* Changing the original activity to include above features

July 13:
Publish blog post that showcases updated activity. Explain problems encountered, what works, what still doesn’t.

July 15 - July 25:
* Fixing bugs
* Work on gears+karma support

July 26 - July 31:
* Documenting examples
* Improving documentation

August 1 - August 9: time for any eventual emergencies

==== KCD's remaining time in Nepal ====

from August 21 - Sept 10th

# Work on basic layout
#* html versions of chakra, lesson_nav
#* Examples of lesson_text, lesson_plan, teacher's note for "adding_up_to_10"
# The Karma specification
#* put it in separate page
#* document what needs to be done and post various ideas and problems

==== Subzero's University Thesis ====

Deadline: December 30th

Goals: i18n mechanism, animation support, several good examples
* i18n mechanism: i18n on Karma Objects, inline html i18n, html2po tool

==== Roadmap to 0.1 ====

TBD

=== Library ===

here lies a lot of links to resources specific to karma

UI
* Iphone Human Interface Guide http://developer.apple.com/iphone/library/documentation/userexperience/conceptual/mobilehig/MobileHIG.pdf
* Palm Pre interface guide http://developer.palm.com/images/palm/pdf/palm_webos_hi_guidelines.pdf
* Apple "Web Page Development: Best Practices" http://developer.apple.com/internet/webcontent/bestwebdev.html
* "The Design of Everyday Things" book by Don Norman
* "Don't Make me think" by Steve Krug, guide to usability for web apps

HTML5
* http://www.smashingmagazine.com/2009/07/16/html5-and-the-future-of-the-web/
* http://www.w3.org/TR/html5-diff/ Differences between html4 and html5

General Web Design
* "Web Design in a Nutshell" from O'Reilly

Canvas
* demos: http://html5demos.com/
* basics: http://dev.opera.com/articles/view/html-5-canvas-the-basics/
* painting web app: http://dev.opera.com/articles/view/html5-canvas-painting/
* mozilla canvas tutorial: https://developer.mozilla.org/en/Canvas_tutorial
* using canvas on webkit: http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/Canvas.html
* http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html

Javascript
* "Javascript: The Good Parts" book by Doug Crockford
* "jQuery in Action" book
* "Pro Javascript Techniques" by john resig
* All the tutorials at www.ejohn.org, esp.
** http://ejohn.org/blog/how-javascript-timers-work/

Coding Tools and Conventions
* Venkman -- javascript debugger http://www.svendtofte.com/code/learning_venkman/
* Firebug --- http://www.getfirebug.com
* For emacs users -- nxhtml mode and magit.el for working w/ git

== Subpages ==

{{Special:PrefixIndex/{{PAGENAMEE}}/}}

[[Category:GSoC]]

Karma/Nepal

2009-09-02T09:52:19Z

ChristophD: /* Chakra */

'''List of desired differences between the generic Karma design and the specific Nepal implementation.'''

== Chakra ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Item
! Generic
! Nepal
|-
! Grade / subject page
| grey icons for empty selections
| icons for empty selections are removed
|-
! Stage 1
| -
| add link to E-Pustakalaya
|}

== Lesson navigation ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Item
! Generic
! Nepal
|-
! Elements in knavbar
| Back, Chakra, Title, Tutorial, Exercise, Game, References, Help, Logo
| Back, Title, Help, Logo
|-
! Elements in knavbar (welcome)
| Back, Chakra, Title, Tutorial, Exercise, Game, References, Help, Logo
| Back, Title
|-
! Game icon in knavbar
| Yes (in grey when no game exists)
| No
|}

Karma/Nepal

2009-09-02T09:36:32Z

ChristophD: Created page with ''''List of desired differences between the generic Karma design and the specific Nepal implementation.''' == Chakra == {| border=1 cellpadding=3 style="border: 1px solid white;…'

'''List of desired differences between the generic Karma design and the specific Nepal implementation.'''

== Chakra ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Item
! Generic
! Nepal
|-
! Grade / subject page
| grey icons for empty selections
| icons for empty selections are removed
|}

== Lesson navigation ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Item
! Generic
! Nepal
|-
! Elements in knavbar
| Back, Chakra, Title, Tutorial, Exercise, Game, References, Help, Logo
| Back, Title, Help, Logo
|-
! Elements in knavbar (welcome)
| Back, Chakra, Title, Tutorial, Exercise, Game, References, Help, Logo
| Back, Title
|-
! Game icon in knavbar
| Yes (in grey when no game exists)
| No
|}

Karma/Dictionary

2009-09-01T03:58:53Z

ChristophD:

;activity text: blue-print for the activity and contains every piece of information the developers need to implement the activity
; assets: multimedia objects such as images, sounds and videos that are used in Karma lessons
; bundle: a collection of lessons, possibly also including Karma utilities and a HTML 5 capable browser (see [[Karma/Bundle_layout]] for more details)
; Chakra: landing page (formerly known as MenuStage in E-Paath)
; exercise: exercise is where the student gets to assess how well she has learned the content of the lesson
; game: a fun way to explore the material introduced in the lesson which helps in the learning objective
; help text: accompanying online help within Karma
; knavbar: lesson navigation
; kpage: an individual page within a lesson
; kpagenav: page navigation within lessons
; lesson: a self-contained unit of Karma content
; lesson plan: detailed overview of how teachers can use the activity in the classroom, which homework can be assigned to pupils, etc.
; review: a page containing the assessment and scores of past lessons
; teacher's note: document detailing learning goals, (possibly) links to related school book contents, ideas for preceding and follow-up activities, etc.
; tutorial: the first part of the lesson that introduces the concepts of the lesson
; [http://en.wikipedia.org/wiki/Unobtrusive_JavaScript unobtrusive javascript]

Karma/Dictionary

2009-09-01T03:57:49Z

ChristophD:

;activity text: blue-print for the activity and contains every piece of information the developers need to implement the activity
; assets: multimedia objects such as images, sounds and videos that are used in Karma lessons
; bundle: a collection of lessons, possibly also including Karma utilities and a HTML 5 capable browser (see [[Karma/Bundle_layout]] for more details)
; Chakra: landing page (formerly known as MenuStage in E-Paath)
; exercise: exercise is where the student gets to assess how well she has learned the content of the lesson
; game: a fun way to explore the material introduced in the lesson which helps in the learning objective
; help text: accompanying online help within Karma
; knavbar: lesson navigation
; kpagenav: page navigation within lessons
; lesson: a self-contained unit of Karma content
; lesson plan: detailed overview of how teachers can use the activity in the classroom, which homework can be assigned to pupils, etc.
; review: a page containing the assessment and scores of past lessons
; teacher's note: document detailing learning goals, (possibly) links to related school book contents, ideas for preceding and follow-up activities, etc.
; tutorial: the first part of the lesson that introduces the concepts of the lesson
; [http://en.wikipedia.org/wiki/Unobtrusive_JavaScript unobtrusive javascript]

Karma/Bundle layout

2009-08-31T05:05:34Z

ChristophD: /* The Main Karma Package */

== The Main Karma Package ==

''A set of tools that will help you start working with Karma quickly''

This is what is contained in the repository at http://git.sugarlabs.org/projects/karma/

* Includes script for Karma activity generation, xo bundle generation
* includes "platform" files, i.e. a basic html5-capable browser that can be used to create an xo bundle

ROOT/ ( ROOT is not actually a directory name, it just labels the top-level of this package )
assets/ ( images, sounds, and text common to karma.html, examples, and the lessons )
default/
images/
sounds/
locale_name/
images/
locale_name.json ( karma actually needs the .po file to be converted to .json )
sounds/
AUTHORS ( Should include names of everyone that has contributed to Karma main package )
chakra/ ( for all sub-pages of the chakra, e.g. grade1.html )
ChangeLog
COPYING ( Licensing information, should default to MIT License ? how distinguish b/w code licensing and content licensing )
css/ ( css/ and js/ contain the code common to all examples, lessons, and karma.html )
examples/ ( working examples of karma lessons )
index.html ( The starting page for accessing Karma lessons, should include links to the examples, known as the CHAKRA )
js/ ( css/ and js/ contain the code common to all examples, lessons, and karma.html )
karma ( This is a shell script that launches utils/karma.js, it just checks if you have java installed so you can run karma.js
it is inspired partly by rails and [http://docs.djangoproject.com/en/dev/ref/django-admin/ django-admin] administrative scripts )
lessons/ ( this is the workspace for creating new Karma lessons )
NEWS ( List of important changes to this package indexed by version )
po/
README
utils/ ( The [http://www.narwhaljs.org/ narwhal] command-line interpreter for javascript and other utility scripts used by karma.js )
bin/
browser/ ( An html5-capable browser that can be used to create sugar .xo bundle )
karma.js ( The main utility script for karma, all it dependencies live in utils/ )
packages/
tests/

== Karma XO bundle ==

* similar to E-Paath layout and uses the standard [[Development_Team/Almanac/Activity_Bundles|Sugar bundle structure]]
* It is still undecided whether karma will default to using Browse which is based on Firefox or [http://dev.laptop.org/~bobbyp/surf/Surf-106.xo Surf] which based on webkit (Safari/Chrome). Surf requires that you install the rpms for pywebkitgtk and webkitgtk

activity/
activity.info (activity info file)
activity-web.svg (icon for activity as specified in activity.info)
mimetypes.xml (map documents to MIME types)
text-plain.svg (icons for documents, e.g. "text-plain.svg" for "text/plain")
text-html.svg
contents (manifest for bundle contents)
contents.sig (credentials for signed bundle)
permissions.info (optional; '''not a stable API''')
assets/
AUTHORS
bin/
launch.sh (launcher script)
browser.dtd
browser.py
cert8.db
clickToView.xml
COPYING
css/
downloadmanager.py
edittoolbar.py
globalhistory.py
icons
index.html
js/
linkbutton.py
karma
karmaactivity.py
lessons/
locale
MANIFEST
messenger.py
model.py
palettes.py
places.py
po/
promptservice.py
README
securitydialogs.py
sessionhistory.py
sessionstore.py
setup.py
viewtoolbar.py
utils/
webtoolbar.py

== Karma lesson bundle ==

''consists of multiple lesson in a single bundle''

* common jquery and css files in a single folder
* The '''karma''' utility script can be used to generate a lesson bundle with accompanying main menu and ''search'' (probably some sort of sitemap)

bundle_name/
assets/
default/ ( default as in the default locale)
docs/
images/
sounds/
default.po
en-US/
docs/
images/
sounds/
default.po
chakra/ ( for all sub-pages of the chakra, e.g. grade1.html )
css/ ( common css files (e.g. jquery.jgrowl.css and menu.css ) )
index.html ( Common gateway to access the lessons in the bundle known as the Chakra)
js/ ( common javascript / jquery files )
lessons/ ( directory for all the lessons )
lesson_name1/
lesson_name2/

== Lesson ==

''consists of a single lesson''

lesson_name/
index.html ( lesson menu with iFrame for reading.html, css and js are common files, they are inside../css/ and ../js/ respectively)
tutorial/ ( contains files related to the tutorial )
game/ ( contains files related to the game )
exercise/ ( contains files related to the exercise )
assets/
{langCode}/ (files specific to langCode: en-US, en, es-MX, es, ....)
docs/
activity text
lesson plan
teachers note

*Notes:
# {langCode} represents the lang code and country code
# which will be the template language for aseets/docs/* ?, English suggested
# suggestion: rename assets/{langCode}/docs/ to docs/{langCode}/ . This is based that at this moment there are no other kind of files under assets/ than 'docs'

== Reading, Game and Exercise ==
''consist of a single 'reading', 'game' or 'exercise' ''

{type}/
index.html (valid html5 -- markup only includes visual elements and links in other resources, no inline code or styling )
css/{type}.css ( css files -- specific to the lesson )
js/{type}.js ( javascript controlling logic for the lesson )
po/ ( translation files )
ne-NP.po ( example translation file for Nepal - Nepali )
sp-ES.po ( example translation file for traditional Spanish )
{langCode}.po ( translation file )
assets/
generic/ ( for language independent assets (e.g. arrows, background images, etc.) )
images/
preview.jpg ( screenshot for Chakra )
sounds/
videos/
docs/
ne/
images/
sounds/
videos/
docs/
en/
images/
sounds/
videos/
docs/
{langCode}/
images/
sounds/
videos/
docs/
* Notes
# {type} represents 'game' or 'exercise' or 'reading'
# does docs/ is used?

Karma/Bundle layout

2009-08-31T05:05:10Z

ChristophD: /* Karma lesson bundle */

== The Main Karma Package ==

''A set of tools that will help you start working with Karma quickly''

This is what is contained in the repository at http://git.sugarlabs.org/projects/karma/

* Includes script for Karma activity generation, xo bundle generation
* includes "platform" files, i.e. a basic html5-capable browser that can be used to create an xo bundle

ROOT/ ( ROOT is not actually a directory name, it just labels the top-level of this package )
assets/ ( images, sounds, and text common to karma.html, examples, and the lessons )
default/
images/
sounds/
locale_name/
images/
locale_name.json ( karma actually needs the .po file to be converted to .json )
sounds/
AUTHORS ( Should include names of everyone that has contributed to Karma main package )
ChangeLog
COPYING ( Licensing information, should default to MIT License ? how distinguish b/w code licensing and content licensing )
css/ ( css/ and js/ contain the code common to all examples, lessons, and karma.html )
examples/ ( working examples of karma lessons )
index.html ( The starting page for accessing Karma lessons, should include links to the examples, known as the CHAKRA )
js/ ( css/ and js/ contain the code common to all examples, lessons, and karma.html )
karma ( This is a shell script that launches utils/karma.js, it just checks if you have java installed so you can run karma.js
it is inspired partly by rails and [http://docs.djangoproject.com/en/dev/ref/django-admin/ django-admin] administrative scripts )
lessons/ ( this is the workspace for creating new Karma lessons )
NEWS ( List of important changes to this package indexed by version )
po/
README
utils/ ( The [http://www.narwhaljs.org/ narwhal] command-line interpreter for javascript and other utility scripts used by karma.js )
bin/
browser/ ( An html5-capable browser that can be used to create sugar .xo bundle )
karma.js ( The main utility script for karma, all it dependencies live in utils/ )
packages/
tests/

== Karma XO bundle ==

* similar to E-Paath layout and uses the standard [[Development_Team/Almanac/Activity_Bundles|Sugar bundle structure]]
* It is still undecided whether karma will default to using Browse which is based on Firefox or [http://dev.laptop.org/~bobbyp/surf/Surf-106.xo Surf] which based on webkit (Safari/Chrome). Surf requires that you install the rpms for pywebkitgtk and webkitgtk

activity/
activity.info (activity info file)
activity-web.svg (icon for activity as specified in activity.info)
mimetypes.xml (map documents to MIME types)
text-plain.svg (icons for documents, e.g. "text-plain.svg" for "text/plain")
text-html.svg
contents (manifest for bundle contents)
contents.sig (credentials for signed bundle)
permissions.info (optional; '''not a stable API''')
assets/
AUTHORS
bin/
launch.sh (launcher script)
browser.dtd
browser.py
cert8.db
clickToView.xml
COPYING
css/
downloadmanager.py
edittoolbar.py
globalhistory.py
icons
index.html
js/
linkbutton.py
karma
karmaactivity.py
lessons/
locale
MANIFEST
messenger.py
model.py
palettes.py
places.py
po/
promptservice.py
README
securitydialogs.py
sessionhistory.py
sessionstore.py
setup.py
viewtoolbar.py
utils/
webtoolbar.py

== Karma lesson bundle ==

''consists of multiple lesson in a single bundle''

* common jquery and css files in a single folder
* The '''karma''' utility script can be used to generate a lesson bundle with accompanying main menu and ''search'' (probably some sort of sitemap)

bundle_name/
assets/
default/ ( default as in the default locale)
docs/
images/
sounds/
default.po
en-US/
docs/
images/
sounds/
default.po
chakra/ ( for all sub-pages of the chakra, e.g. grade1.html )
css/ ( common css files (e.g. jquery.jgrowl.css and menu.css ) )
index.html ( Common gateway to access the lessons in the bundle known as the Chakra)
js/ ( common javascript / jquery files )
lessons/ ( directory for all the lessons )
lesson_name1/
lesson_name2/

== Lesson ==

''consists of a single lesson''

lesson_name/
index.html ( lesson menu with iFrame for reading.html, css and js are common files, they are inside../css/ and ../js/ respectively)
tutorial/ ( contains files related to the tutorial )
game/ ( contains files related to the game )
exercise/ ( contains files related to the exercise )
assets/
{langCode}/ (files specific to langCode: en-US, en, es-MX, es, ....)
docs/
activity text
lesson plan
teachers note

*Notes:
# {langCode} represents the lang code and country code
# which will be the template language for aseets/docs/* ?, English suggested
# suggestion: rename assets/{langCode}/docs/ to docs/{langCode}/ . This is based that at this moment there are no other kind of files under assets/ than 'docs'

== Reading, Game and Exercise ==
''consist of a single 'reading', 'game' or 'exercise' ''

{type}/
index.html (valid html5 -- markup only includes visual elements and links in other resources, no inline code or styling )
css/{type}.css ( css files -- specific to the lesson )
js/{type}.js ( javascript controlling logic for the lesson )
po/ ( translation files )
ne-NP.po ( example translation file for Nepal - Nepali )
sp-ES.po ( example translation file for traditional Spanish )
{langCode}.po ( translation file )
assets/
generic/ ( for language independent assets (e.g. arrows, background images, etc.) )
images/
preview.jpg ( screenshot for Chakra )
sounds/
videos/
docs/
ne/
images/
sounds/
videos/
docs/
en/
images/
sounds/
videos/
docs/
{langCode}/
images/
sounds/
videos/
docs/
* Notes
# {type} represents 'game' or 'exercise' or 'reading'
# does docs/ is used?

Karma/Specifications

2009-08-25T08:53:10Z

ChristophD:

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

=== Introduction ===

Two main goals should be kept in mind when creating Karma lessons:

# they should be easy to adapt
# they should run on as much hardware as possibe with OLPC's XO-1 laptop representing the baseline

=== General Notes ===

==== Hardware constraints ====

Since a large percentage (if not the majority) of Karma users are envisioned to be using OLPC XO-1 laptops, netbooks, older hardware or generally relatively slow systems there are several performance constraints that need to be taken into account when designing Karma lessons.

* CPU/Memory: The baseline regarding available performance is the XO-1 laptop which comes with an AMD Geode LX 433MHz CPU and 256MB RAM ([http://wiki.sugarlabs.org/go/Karma/Specifications full specifications]). This limits the use of high-resolution multimedia, animations and videos to some degree.
* Display: Karma lessons should work well on displays with a resolution of 1024*768 (whereby a part of the display may be taken up by browser UI elements!).
* Mass storage: Since especially the XO-1 laptop only has very limited local mass storage (1GB) lessons should be kept reasonably small.
* Connectivity: Karma lessons must not assume constant connectivity with a locally (e.g. [http://wiki.laptop.org/go/School_server XS]) or globally available server. Support for storing data locally will be provided by Karma.

==== Accessibility ====

Follow best practices for accessibility (e.g. example of a [http://northtemple.com/1608 checklist]), especially with regard to [http://en.wikipedia.org/wiki/Color_blindness colorblindness].

=== HTML ===

* <!DOCTYPE HTML>

=== JavaScript ===

* ...

=== Animations ===

* Format(s): TBD
* Recommended tools: TBD
* Notes: TBD
The Karma animations are created using JavScript and the Karma plugin. At this moment we haven't defined a mechanism to "export" (and "import") one animation. But copying and pasting the code (of the animation) will be enough in most cases.

=== Images ===

* Format(s): [http://en.wikipedia.org/wiki/JPEG JPEG], [http://en.wikipedia.org/wiki/Portable_Network_Graphics PNG], [http://en.wikipedia.org/wiki/Scalable_Vector_Graphics SVG] '''(Note 1, 2 and 3)'''
* Recommended tools: [http://www.inkscape.org/ Inkscape], [http://www.gimp.org/ GIMP], [http://www.adobe.com/products/illustrator/ Adobe Illustrator] (non-free), [http://www.corel.com CorelDRAW] (non-free)
* Max. resolution: 1200*900 px
* Notes:
#To handle SVG files will be necessary to create a parser svg2canvas in order to introduce them as objects inside canvas element.
#Animated SVG content will be hard to reproduce using canvas.
#SVG animations seems slow under the XO-1 (Tested with [http://raphaeljs.com/ RaphaelJS] and Browse)

=== Sound ===

* Format(s): [http://en.wikipedia.org/wiki/Vorbis OGG Vorbis] (Note 1)
* Bit rate: TBD
* Max. size per lesson: 3~4MB
* Recommended tools: [http://audacity.sourceforge.net/ Audacity]
* Notes:
# https://developer.mozilla.org/En/Media_formats_supported_by_the_audio_and_video_elements

=== Video ===

* Format(s): TBD (Note 1)
* Recommended tools: TBD
* Notes: TBD
# https://developer.mozilla.org/En/Media_formats_supported_by_the_audio_and_video_elements

Karma:Meeting 24 Aug 2009

2009-08-24T09:36:05Z

ChristophD:

Agenda Items:

# Joshua Gay's presentation on August 27th
# Status of Lesson Number 1 ("Adding up to 10")
# Status of Karma plugin
# Status of Karma JS Documentation
# Timer animation: problems and solutions
# Christoph's mockups (scrollbar vs multiple pages)
# [[Karma/Assessment|Assessment]]
# [[Karma/Specifications|Specifications]]
## max. size of lesson
## markup in html
# Roadmap
## GSoC
## Christoph's remaining time in Nepal
## Subzero's bachelor thesis

Deployment Team/Places

2009-08-20T05:31:16Z

ChristophD: /* Europe */

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of Sugar installations
! Hardware used
! Software version
! Project blog/wiki
! Contact
|-
| Graz, Austria
| German
| 25
| XO-1
| build 767
| [http://elearningblog.phst.at/?cat=32 blog] (in German)
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Deployment Team/Places

2009-08-20T05:20:59Z

ChristophD: /* Europe */

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of Sugar installations
! Hardware used
! Software version
! Project blog/wiki
! Contact
|-
| Graz, Austria
| German
| 25
| XO-1
| build 767
| TBA
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Deployment Team/Places

2009-08-20T05:08:20Z

ChristophD: /* Europe */

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of XOs
! Software version
! Project blog/wiki
! Contact
|-
| Graz, Austria
| German
| 25
| build 767
| TBA
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Deployment Team/Places

2009-08-20T05:04:29Z

ChristophD: added info for Austrian pilot

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
=== Introduction ===

This page lists the places in the world where Sugar is used along with a contact person that will facilitate communication between the global and the local communities.

The column "# of members" is intended to give a rough estimation of the size of the local community and may include children, educators, parents, volunteers, etc

=== Asia ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| India
| English, Hindi, Marathi
| 32
| [[USER:Jpritikin|Joshua Pritikin]]
|-
| Nepal
| Nepali
| 40
| [[USER:BryanWB|Bryan Berry]], Rabi Karmacharya
|-
| Quezon City, Philippines
| Filipino, English
| 30
| [[USER:Jgotangco|Jerome Gotangco]]
|}

=== Africa ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Ethiopia
| Amharic
| ?
| ?
|}

=== America ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Colombia
| Spanish
| 7
| RafaelOrtiz
|-
| Peru
| Spanish
| ?
| Hernan Pachas?
|-
| Uruguay
| Spanish
| ?
| Pablo Flores?
|-
| Paraguay
| Spanish
| 4500
| Raul Gutierrez S.
|-
| Boston, USA
| English
| ?
| Caroline Meeks?
|}

=== Europe ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of XOs
! Software version
! # of members
! Contact
|-
| Graz, Austria
| German
| 25
| build 767
| 7
| David Van Assche, [[User:ChristophD|Christoph Derndorfer]]
|}

=== Oceania ===

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Region
! Languages
! # of members
! Contact
|-
| Solomon Islands
| Pijin, Marovo
| ?
| David Leeming?
|}

Development Team/Almanac

2009-08-19T07:42:39Z

ChristophD: /* How do I get additional help beyond this almanac? */

{{Almanac}}
{{Almanac TOC}}
== How do I get additional help beyond this almanac? ==
* Looking to get started with the basics of Sugar development? Check out OLPC Austria's [http://wiki.sugarlabs.org/images/5/51/Activity_Handbook_200805_online.pdf Activity Handbook] (''Please note that this handbook was last updated in May 2008 so the screenshots still show pre-8.2 design. In terms of the code itself things should still work as described. If you run into any issues please contact [[User:ChristophD|ChristophD]].'')
* See also [[Development Team/Almanac/Code Snippets]]

Now, on to the actual almanac ...

== Where can I see API changes? ==
API changes between OLPC releases can be seen here: [[Development Team/Almanac/API Changes|API Changes]]

== Getting Started ==
=== How do I structure my files so that they are a valid sugar activity? ===
Information on activity bundle structure can be found here: [[Development Team/Almanac/Activity Bundles|Activity Bundles]]

=== How do I make an icon for my activity? ===
Information on what you need to do can be found here: [[Development Team/Almanac/Making Icons|Making Icons]]

== Package: sugar ==
* [[Development Team/Almanac/sugar.env|sugar.env]]
* [[Development Team/Almanac/sugar.profile|sugar.profile]]
* [[Development Team/Almanac/sugar.mime|sugar.mime]]
* [[Development Team/Almanac/sugar.logger|sugar.logger]]

== Package: sugar.activity ==
* [[Development Team/Almanac/sugar.activity.activity|sugar.activity.activity]]
* [[Development Team/Almanac/sugar.activity.activityfactory|sugar.activity.activityfactory]]
* [[Development Team/Almanac/sugar.activity.registry|sugar.activity.registry]]

== Package: sugar.datastore ==
* [[Development Team/Almanac/sugar.datastore.datastore|sugar.datastore.datastore]]

== Package: sugar.graphics ==
* [[Development Team/Almanac/sugar.graphics.alert|sugar.graphics.alert]]
* [[Development Team/Almanac/sugar.graphics.icon|sugar.graphics.icon]]
* [[Development Team/Almanac/sugar.graphics.notebook|sugar.graphics.notebook]]
* [[Development Team/Almanac/sugar.graphics.toolbutton|sugar.graphics.toolbutton]]
* [[Development Team/Almanac/sugar.graphics.toolbox|sugar.graphics.toolbox]]
* [[Development Team/Almanac/sugar.graphics.style|sugar.graphics.style]]

== Package: sugar.presence ==
* [[Development Team/Almanac/Sugar.presence|Sugar.presence]]
* [[Development Team/Almanac/Sugar.presence.activity|Sugar.presence.activity]]
* [[Development Team/Almanac/Sugar.presence.buddy|Sugar.presence.buddy]]
* [[Development Team/Almanac/Sugar.presence.presenceservice|Sugar.presence.presenceservice]]

== Clipboard ==
* Notes on using [[Development Team/Almanac/GTK's Clipboard Module|GTK's Clipboard Module]]

== Logging ==
* [[Development Team/Almanac/sugar.logger|sugar.logger]]
* Notes on using [[Development Team/Almanac/Python Standard Logging|Python Standard Logging]]

== Internationalization ==
*[[Development Team/Almanac/Internationalization|Internationalization]]

== Text and Graphics for Sugar Activities ==
* [[Development Team/Almanac/Pango|Pango]]
=== How do I create a text box for code editing? ===
You can use gtksourceview2
<pre>
import gtk
import gtksourceview2
from sugar.graphics import style

...

# set up the buffer
buffer = gtksourceview2.Buffer()
if hasattr(buffer, 'set_highlight'): # handle different API versions
buffer.set_highlight(True)
else:
buffer.set_highlight_syntax(True)

# set mime type for the buffer
lang_manager = gtksourceview2.language_manager_get_default()
if hasattr(lang_manager, 'list_languages'): # again, handle different APIs
langs = lang_manager.list_languages()
else:
lang_ids = lang_manager.get_language_ids()
langs = [lang_manager.get_language(lang_id)
for lang_id in lang_ids]
for lang in langs:
for m in lang.get_mime_types():
if m == mime_type: # <-- this is the mime type you want
buffer.set_language(lang)

# set up the view object, use it like gtk.TextView
view = gtksourceview2.View(buffer)
view.set_size_request(300, 450)
view.set_editable(True)
view.set_cursor_visible(True)
view.set_show_line_numbers(True)
view.set_wrap_mode(gtk.WRAP_CHAR)
view.set_right_margin_position(80)
#view.set_highlight_current_line(True) #FIXME: Ugly color
view.set_auto_indent(True)
view.modify_font(pango.FontDescription("Monospace " +
str(style.FONT_SIZE)))
...

</pre>

To set the text in the buffer:
<pre>
buffer.set_text(text)
</pre>
To get all the text:
<pre>
text = buffer.get_text(buffer.get_start_iter(), buffer.get_end_iter())
</pre>

You will probably want to put the view in a gtk.ScrolledWindow
<pre>
sw = gtk.ScrolledWindow()
sw.add(view)
sw.set_policy(gtk.POLICY_AUTOMATIC, gtk.POLICY_AUTOMATIC)
</pre>
and add the sw object instead of the view.

You can find more in the Pippy source and in jarabe.view.sourceview.

== Audio & Video ==
* [[Development Team/Almanac/GStreamer|GStreamer]]

== Mouse ==
=== How do I change the mouse cursor in my activity to the wait cursor? ===
In your activity subclass:

<pre>
self.window.set_cursor( gtk.gdk.Cursor(gtk.gdk.WATCH) )
</pre>

and to switch it back to the default:

<pre>
self.window.set_cursor( None );
</pre>

=== How do I track the position of the mouse? ===
There are many different reasons you might want to track the position of the mouse in your activity, ranging from the entertaining ([[http://en.wikipedia.org/wiki/Xeyes]]) to the functional (hiding certain windows when the mouse hasn't moved for a couple of seconds and making those ui elements re-appear when the mouse has moved again). Here is one way you can implement this functionality:

<pre>

...
self.hideWidgetsTime = time.time()
self.mx = -1
self.my = -1
self.HIDE_WIDGET_TIMEOUT_ID = gobject.timeout_add( 500, self.mouseMightHaveMovedCb )

def _mouseMightHaveMovedCb( self ):
x, y = self.get_pointer()
passedTime = 0

if (x != self.mx or y != self.my):
self.hideWidgetsTime = time.time()
if (self.hiddenWidgets):
self.showWidgets()
self.hiddenWidgets = False
else:
passedTime = time.time() - self.hideWidgetsTime

if (passedTime >= 3):
if (not self.hiddenWidgets):
self.hideWidgets()
self.hiddenWidgets = True

self.mx = x
self.my = y
return True

</pre>

== Miscellaneous==

The tasks below are random useful techniques that have come up as I write code and documentation for this reference. They have yet to be categorized, but will be as a sufficient set of related entries are written.

=== How do I know when my activity is "active" or not? ===

You can set an event using the VISIBILITY_NOTIFY_MASK constant in order to know when your activity changes visibility. Then in the callback for this event, you simply compare the event's state to gtk-defined variables for activity visibility. See the [http://www.pygtk.org/docs/pygtk/gdk-constants.html#gdk-visibility-state-constants GDK Visibility State Constants] section of gtk.gdk.Constants for more information.

<pre>
# Notify when the visibility state changes by calling self.__visibility_notify_cb
# (PUT THIS IN YOUR ACTIVITY CODE - EG. THE __init__() METHOD)
self.add_events(gtk.gdk.VISIBILITY_NOTIFY_MASK)
self.connect("visibility-notify-event", self.__visibility_notify_cb)
...
# Callback method for when the activity's visibility changes
def __visibility_notify_cb(self, window, event):
if event.state == gtk.gdk.VISIBILITY_FULLY_OBSCURED:
print "I am not visible"
elif event.state in [gtk.gdk.VISIBILITY_UNOBSCURED, gtk.gdk.VISIBILITY_PARTIAL]:
print "I am visible"
</pre>

=== How do I get the amount of free space available on disk under the /home directory tree? ===
The following function uses the [http://docs.python.org/lib/module-statvfs.html statvfs] module. The following code demonstrates how to get the total amount of free space under /home.

<pre>
#### Method: getFreespaceKb, returns the available freespace in kilobytes.
def getFreespaceKb(self):
stat = os.statvfs("/home")
freebytes = stat[statvfs.F_BSIZE] * stat[statvfs.F_BAVAIL]
freekb = freebytes / 1024
return freekb
</pre>

Note, however, that assuming anything about "/home" is a bad idea, better use os.environ['HOME'] instead. Rainbow will put your actual files elsewhere,
some on ramdisks, some on flash. Be clear about which filesystem's free space you actually care about.

=== How do I know whether my activity is running on a physical XO? ===
Sugar runs on ordinary computers as well as on XO's. While your activity is typically going to be run on a real XO, some people will indeed run it elsewhere. Normally you shouldn't write your activity to care whether it's on an XO or not. If for some odd reason, you need to care, the easiest way to tell if you are on a physical XO is to check whether /sys/power/olpc-pm, an essential power management file for the XO, exists. <ref>[http://lists.laptop.org/pipermail/devel/2008-June/015923.html reliably detecting if running on an XO]</ref> <ref>OLPC [[olpc:Power Management Interface]]</ref>

<pre>
import os
...
#Print out a boolean value that tells us whether we are on an XO or not.
print os.path.exists('/sys/power/olpc-pm')
</pre>

=== How do I know the current language setting on my XO? ===
The system variable 'LANG' tells you which language is currently active on the XO. The following code shows how to look at the value of this variable.

<pre>
import os
...
_logger.debug(os.environ['LANG'])
</pre>

=== How do I repeatedly call a specific method after N number of seconds? ===
The gobject.timeout_add() function allows you to invoke a callback method after a certain amount of time. If you want to repeatedly call a method, simply keep invoking the gobject.timeout_add function in your callback itself. The code below is a simple example, where the callback function is named repeatedly_call. Note that the timing of the callbacks are approximate. To get the process going, you should make an initial call to repeatedly_call() somewhere in your code.

You can see a more substantive example of this pattern in use when we [[olpc:Pango#How_do_I_dynamically_set_the_text_in_a_pango_layout.3F | regularly update the time displayed on a pango layout object]].

<pre>

#This method calls itself ROUGHLY every 1 second
def repeatedly_call(self):
now = datetime.datetime.now()
gobject.timeout_add(self.repeat_period_msec, self.repeatedly_update_time)
</pre>

=== How do I update the current build version of code that is running on my XO? ===

There are several pages that give you instructions on how to install/update your current build.

* If you already have a working build installed and an internet connection, first try [[olpc:olpc-update]].
* If that doesn't work, you can look at instructions for an [[olpc:Activated upgrade]] that can be done via USB] boot.

As the instructions on the pages linked above note, make sure to install your activities separately after you have upgraded to a specific base build.

=== I am developing on an XO laptop, but my keyboard and language settings are not ideal. How can I change them? ===

Internationalized laptops will often have settings that might slow you down while developing. To change around the language settings so you can better understand environment messages, use the [[olpc:Sugar Control Panel]]

Keyboard settings on internationalized laptops<ref>[[olpc:Keyboard layouts#OLPC keyboard layouts]]</ref> can also be suboptimal, especially as characters like "-" and "/" are in unfamiliar positions. You can use the <tt>setxkbmap</tt> command in the [[olpc:Terminal Activity]] to reset the type of keyboard input used and then attach a standard U.S. keyboard that will allow you to type normally. The command below sets the keyboard to the US mapping (it will reset to the default internationalized mapping upon restart).

setxkbmap us

=== My Python activity wants to use threads; how do I do that? ===

A question that has been answered with limited success is which threading patterns are most appropriate for use in Sugar. The following pattern of code to work fine in basic instances:

<pre>
#### Method: __init__, initialize this AnnotateActivity instance
def __init__(self, handle):
...
self.sample_thread = Thread(target=self.announce_thread, args=())
self.sample_thread.setDaemon(0)
self.sample_thread.start()
...

def announce_thread(self):
while (self.Running):
time.sleep(1)
print "thread running"
self._update_chat_text("Thread", "In here")
</pre>

This is the basic series of steps that most online documentation on python suggests to use when trying to work with threads in python. The problem is that it is unclear how this pattern relates to code that worked in the SimCity activity:

<pre>
import gobject
gobject.threads_init()
#import dbus.mainloop.glib
#dbus.mainloop.glib.threads_init()
</pre>

It should be noted that in the SimCity activity the pygame sound player would not produce sound reliably unless this setup was done.



Should the two patterns always be used in tandem? It seems that the latter code is mainly to initiate gobject and other libraries to work with threading, but it is unclear what restrictions there are with using threading with these libraries. Does one take precedence over the other? It is not clear if there is any problem with using the standard python threading code on the sugar technology stack.





In fact, experiments with threading on sugar leads to several different problems. For one thing, thread termination was tricky - using the can_close() method for sugar activities to terminate an activity only killed threads in some circumstances. It did not properly handle terminating threads in the case of CTRL-C or terminal interrupts. You can try to catch signals (SIGINT, SIGTERM or SIGHUP), but you will still be running in to errors in terminating child threads using these as well.





Another set of errors with threading comes up when trying to combine with stream tubes. The bottom line is that it is unclear what the scope of threading in a Sugar activity should be - should it simply work if you do the standard python threading pattern, is the use of the glib.threads_init and gobject.threads_init calls necessary, are there other interactions with threads and dbus that need to be accounted for? With more clarity from sugar developers on how the platform envisions threading to work in an activity, we can be more comfortable writing entries in the Almanac to help developers write error-free code.



=== How do I customize the title that is displayed for each instance of my activity? ===

By default, activity titles are just the generic activity names that you specify in your activity.info file. In some applications, you may want the activity title to be more dynamic.

For example, it makes sense to set the title for different browser sessions to the active web page being visited. That way, when you look back in the journal at the different browser sessions you have run in the previous few days, you can identify unique sessions based on the website you happened to be visiting at the time.

The code below shows how you can set the metadata for your activity to reflect a dynamic title based on whatever session criteria you feel is important. This example is adapted from the Browse activity, which sets activity instance titles based on the title of the current web page being visited.

<pre>
if self.metadata['mime_type'] == 'text/plain':
if not self._jobject.metadata['title_set_by_user'] == '1':
if self._browser.props.title:
# Set the title of this activity to be the current
# title of the page being visited by the browser.
self.metadata['title'] = self._browser.props.title
</pre>

=== What packages are available on sugar to support game development? ===

If your activity will require tools that are typically needed to develop robust and clean video games, then you should utilize the [http://www.pygame.org/ pygame package]. It can be readily imported into any activity:

<pre>
import pygame
...
</pre>

=== How do I detect when one of the game buttons on the laptop have been pressed? ===

The laptop game buttons (the circle, square, x, and check buttons next to the LCD) are encoded as page up, home, page down and end respectively. So, you can detect their press by listening for these specific events. For example, the code below listens for button presses and then just writes to an output widget which button was pressed.

<pre>
...
#### Initialize this activity.
def __init__(self, handle):
...
self.connect('key-press-event', self._keyPressCb)
...

#### Method _keyPressCb, which catches any presses of the game buttons.
def _keyPressCb(self, widget, event):

keyname = gtk.gdk.keyval_name(event.keyval)

if (keyname == 'KP_Page_Up'):
self._chat += "\nCircle Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_Page_Down'):
self._chat += "\nX Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_Home'):
self._chat += "\nSquare Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_End'):
self._chat += "\nCheck Pressed!"
self._chat_buffer.set_text(self._chat)

return False
</pre>

=== How do I detect if one of the joystick buttons has been pressed? ===

This is the same process as detecting game buttons, except with different names for the keys. Again, you listen for "key-press-event" signals and then in your callback you check to see if the pressed button was one of the joystick keys.

<pre>
#### Initialize this activity.
def __init__(self, handle):
...
self.connect('key-press-event', self._keyPressCb)
...

#### Method _keyPressCb, which catches any presses of the game buttons.
def _keyPressCb(self, widget, event):

keyname = gtk.gdk.keyval_name(event.keyval)

if (keyname == 'KP_Up'):
self._chat += "\nUp Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_Down'):
self._chat += "\nDown Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_Left'):
self._chat += "\nLeft Pressed!"
self._chat_buffer.set_text(self._chat)
elif (keyname == 'KP_Right'):
self._chat += "\nRight Pressed!"
self._chat_buffer.set_text(self._chat)

return False
</pre>

=== How do i remove an specific button from the toolbar? ===

This is an example of the share button is removed:

<pre>
activity_toolbar = toolbox.get_activity_toolbar()
activity_toolbar.remove(activity_toolbar.share)
activity_toolbar.share = None
</pre>

== Notes ==
<references />

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

File:Activity Handbook 200805 online.pdf

2009-08-19T07:39:09Z

ChristophD: