https://wiki.sugarlabs.org/api.php?action=feedcontributions&feedformat=atom&user=Annegentle 2026-05-29T21:23:59Z User contributions MediaWiki 1.43.0 https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=38515 2009-09-30T03:56:43Z

<p>Annegentle: /* Tutorials */</p> <hr /> <div>{{Translations <br /> | [[Documentation Team|english]] &amp;#124; [[Documentation Team/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Documentation Team|home=Documentation}}{{TOCright}}&lt;/noinclude&gt;<br /> == Mission ==<br /> {{:Documentation Team/Mission}}<br /> == Sugar FLOSS manual ==<br /> FLOSS Manuals held a BookSprint during the last week of August 2008 in Austin, TX; together, we wrote separate but combinable (remixable) manuals for Sugar, individual Sugar Activities and the hardware it may run on, such as the XO. <br /> {| class=wikitable<br /> |-<br /> |&lt;span class=&quot;plainlinks&quot;&gt; [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]&lt;/span&gt;<br /> | available as: &lt;span class=&quot;plainlinks&quot;&gt;[http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).&lt;/span&gt;<br /> |}<br /> <br /> The manuals for a number of Sugar Activities are now published (including manuals for [http://en.flossmanuals.net/write_activity '''Write'''], [http://en.flossmanuals.net/terminal '''Terminal'''], [http://en.flossmanuals.net/chat '''Chat'''], [http://en.flossmanuals.net/browse '''Browse'''], [http://en.flossmanuals.net/record '''Record'''], and [http://en.flossmanuals.net/turtleart '''Turtle Art''']). <br /> <br /> Please help us improve these manuals by going to http://en.flossmanuals.net/write where the editable versions reside. Note that we are including tutorials and notes to parents and teachers as part of the documentation effort. Helping expanding these sections would be greatly appreciated.<br /> <br /> Those who participated include: Adam Hyde, Anne Gentle, David Farning, Mikus Grinbergs, Brian Jordan, Adam Holt, Janet Swisher, Morgan Collett, Yama Ploskonka, David Cramer, Emily Kaplan, Faisal Anwar, Christoph Derndorfer, Sandy Culver, Aaron Konstam, and the Sugar community. <br /> <br /> Many thanks also to [http://www.motive.com Motive], our hosts in Austin.<br /> <br /> ===Translation===<br /> We are translating the Sugar FLOSS manual into<br /> Spanish ([http://translate.flossmanuals.net/bin/view/Sugar_es es]),<br /> French ([http://translate.flossmanuals.net/bin/view/Sugar_fr fr]),<br /> Dutch ([http://translate.flossmanuals.net/bin/view/Sugar_nl nl]),<br /> German ([http://translate.flossmanuals.net/bin/view/Sugar_de de]),<br /> and Portuguese ([http://translate.flossmanuals.net/bin/view/Sugar_pt pt]). Please help us.<br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[Documentation Team/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial - we now have an Etoys Activity manual set up on FLOSS Manuals. Feel free to contribute here: [http://en.flossmanuals.net/bin/view/Etoys/WebHome|Etoys]<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[Documentation Team/Glossary | Glossary]]<br /> <br /> == Subpages ==<br /> <br /> {{Special:PrefixIndex/{{PAGENAMEE}}/}}<br /> <br /> <br /> [[Category:Documentation Team]]<br /> [[Category:General public]]<br /> [[Category:Team]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Marketing_Team/Presentations&diff=23624 2009-03-22T19:47:55Z

<p>Annegentle: Added CoSN presentation link</p> <hr /> <div>== Sugar Labs bullet points ==<br /> <br /> * [[:Image:Sugarlabs-bullets.odp]]<br /> <br /> == Netbook World Summit ==<br /> <br /> * [[:Image:Netbook.odp| Walter's Netbook World Summit talk]]<br /> <br /> == Previous events ==<br /> <br /> * [http://stud4.tuwien.ac.at/~e0425826/FUDCon.odp FUDCon 2008 Brno] (Christoph Derndorfer)<br /> <br /> * [http://www.codewiz.org/pub/sugar/slides/SugarBeagle.odp ESC Boston 2008] ([[User:Bernie|Bernie Innocenti]])<br /> <br /> * [http://www.codewiz.org/pub/sugar/slides/ Bernie's collection of OLPC &amp; Sugar marketing material]<br /> <br /> * [[:Image:Bolzano.odp| Walter's talk in Bolzano, Italy]]<br /> <br /> * [[:Image:USMP.odp|Walter's talk at the University of San Martin de Porres, Lima Peru]]<br /> <br /> == Sugarcamp 2008 ==<br /> <br /> Video for many of these is available in raw form at http://download.laptop.org/content/conf/20081117-sugarcamp/ -- help is welcome in editing &amp; converting to free formats!<br /> <br /> John Tierney was so nice to share with us the mind maps he took while attending the talks: [[Image:SugarCamp_Mind_Map_Collection.pdf]].<br /> <br /> === Monday ===<br /> <br /> * [http://www.codewiz.org/pub/olpc/slides/sugarcamp/SugarcampIntro.odp Sugarcamp intro] ([[User:Bernie|Bernie Innocenti]])<br /> <br /> === Tuesday ===<br /> <br /> * [http://people.collabora.co.uk/~cassidy/talks/sugar-camp-collab-archi-and-state-of-implementation.pdf Collaboration state of the art] (Guillaume Desmottes)<br /> <br /> * [http://people.collabora.co.uk/~cassidy/talks/sugar-camp-futur-of-collab.pdf Future of collaboration] (Guillaume Desmottes)<br /> <br /> * [http://docs.google.com/EmbedSlideshow?docid=dcfrb5jw_1dqrh9sgr The medium is the message] (Yama)<br /> <br /> === Wednesday ===<br /> <br /> * [http://sugarlabs.org/wiki/images/c/ca/Sugarcamp-cscott-legacy.pdf Desktop legacy compatibility] ([[User:CScott|CScott]])<br /> * [http://sugarlabs.org/wiki/images/f/fb/I18n.pdf Internationalization] (Sayamindu)<br /> * [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-i18n.pdf;hb=HEAD Internationalization] ([[User:CScott|CScott]])<br /> * [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-misc.pdf;hb=HEAD Misc. Topics] ([[User:CScott|CScott]])<br /> * [http://www.sugarlabs.org/wiki/images/1/1b/Sugarcamp-cscott-network.pdf Network] ([[User:CScott|CScott]])<br /> <br /> === Thursday ===<br /> <br /> * [[Media:Sugar-meeting.odp|working with users Open Office presentation by Greg Smith]]<br /> * [http://www.resara.com/presentation.ppt Resara and LTSP by Brendan Powers] (PowerPoint &amp;mdash; [http://docs.google.com/Presentation?id=dcvvrqtp_241fjp7rdgm view in Google Docs])<br /> * [http://docs.google.com/Presentation?id=dddknwgs_360gwgwbnf2 Caroline Meeks - Sugar on a Stick]<br /> * [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-collab.pdf;hb=HEAD Collaboration] ([[User:CScott|CScott]])<br /> <br /> === Friday ===<br /> <br /> * [[Media:Portfolios.odp|Sugar portfolios presentation by Walter Bender and Evangeline Harris Stefanakis]]<br /> * [[Media:SugarLabsOverview.odp|Sugar Labs overview by Walter Bender]]<br /> * [http://www.christianmarcschmidt.com/components/schmidt_sugar_design.pdf Design Opportunities for Sugar, by Christian Marc Schmidt and Eben Eliason]<br /> <br /> === Saturday ===<br /> * [http://www.codewiz.org/pub/sugar/slides/sugarcamp/SugarLabsInfrastructure.odp Sugar Labs infrastructure] ([[User:Bernie|Bernie Innocenti]])<br /> <br /> == FOSDEM 2009 ==<br /> <br /> * [[Media:FOSDEM2009.odp|The Sugar platform: Why GNOME may care?]] by Tomeu Vizoso<br /> <br /> ==CUE (Computer Using Educators)Conference, Palm Springs CA March 2009==<br /> * [http://wiki.laptop.org/go/Image:CUE_XO_03-05-09.pdf One Laptop Per Child: What's The Fuss All About?], Caryl Bigenho's overview of OLPC, the XO, and Sugar for Califonia Educators. Ppt version to follow.<br /> <br /> ==CoSN (Consortium for School Networking) 2009 Annual Conference, Austin, TX March 12 2009==<br /> * [http://wiki.sugarlabs.org/go/Image:Sugar_User-Interface_Opportunity.pdf Sugar User Interface Opportunity], Anne Gentle presenting on behalf of Walter Bender.</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=File:Sugar_User-Interface_Opportunity.pdf&diff=23623 2009-03-22T19:45:24Z

<p>Annegentle: </p> <hr /> <div></div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team/FAQ&diff=21169 2009-03-10T02:24:29Z

<p>Annegentle: /* What resources are available for creating documents? */</p> <hr /> <div>&lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br /> {{TeamHeader|DocumentationTeam}}<br /> <br /> Welcome to the [[DocumentationTeam|DocumentationTeam]] FAQ! The aim of this page is to provide an up to date list of common questions that we get about the [[DocumentationTeam|DocumentationTeam]]. This page contains many frequently-asked questions along with some answers.<br /> <br /> To ask a new Documentation question, please '''post your question(s) [[Talk:DocumentationTeam/FAQ|here]]'''. We encourage you to answer questions and keep these pages organized.<br /> &lt;/noinclude&gt;<br /> ===What documentation is needed?===<br /> <br /> See [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] for a partial answer. This addresses primarily hardware and software documentation for students, teachers, system administrators, and developers, and the separate issue of [http://wiki.laptop.org/go/Localization localization]. There are proposals for teacher training and textbooks, but little is available.<br /> <br /> ===What resources are available for creating documents?===<br /> <br /> * [http://en.flossmanuals.net/bin/view/Main/WebHome FLOSS Manuals - free manuals for free software]<br /> * [http://wiki.laptop.org/go/Git#The_OLPC_Git_Repository Source code repository]<br /> * [http://wiki.laptop.org/go/Content_repositories Content Repositories]<br /> * [http://wiki.laptop.org/go/Builds Test builds/OS Images]<br /> * [http://wiki.laptop.org/ OLPC Wiki]<br /> * [http://lists.laptop.org/listinfo/devel Software developers mailing list]<br /> * [http://lists.laptop.org/listinfo/peripherals Peripherals mailing list]<br /> * [http://lists.laptop.org/listinfo/educators Educators mailing list]<br /> * [http://lists.laptop.org/listinfo/library Library and content mailing list]<br /> <br /> and other such locations.<br /> <br /> ===How do I get involved?===<br /> <br /> See [[Sugar Labs/GettingInvolved]] for general information. Beyond that, look at what is being done, and offer to write, edit, or test something.<br /> <br /> ===Who is working on documentation?===<br /> <br /> See [[DocumentationTeam/Contacts]].<br /> <br /> &lt;noinclude&gt;<br /> See the Community [[Sugar Labs/FAQ|FAQ]] for more answers.<br /> [[Category:DocumentationTeam]]<br /> &lt;/noinclude&gt;</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8324 2008-08-23T01:50:27Z

<p>Annegentle: </p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint August 2008 ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> ''Accomodations ''<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> <br /> 12515 Research Blvd<br /> <br /> Austin, TX 78759<br /> <br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> Since I'm not having much luck convincing Austinites that picking people up at the airport is great fun with many benefits, it<br /> looks likely that you all should use the Super Shuttle (www.supershuttle.com) or Capital Metro's airport routes (www.capmetro.org/riding/airport.asp) rather than get picked up. Taking or sharing a cab is also an option.<br /> <br /> ''Using FLOSS Manuals''<br /> <br /> If you're not familiar with the FLOSS Manuals interface, you might<br /> want to take a look at this screencast for an overview/starter guide<br /> http://www.screencast.com/t/wHSXac3b43.<br /> <br /> ''XO Hardware for the Sprint''<br /> <br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> ''Schedule''<br /> <br /> Sunday 11:00 AM Goal setting session at the hotel (Changed from 3:00 because Adam Holt has a prior meeting that afternoon.)<br /> <br /> Sunday 7:00 PM Mozart's meetup with the XO-Austin user group<br /> <br /> Monday 9:00 AM Anne meeting in the hotel lobby to walk over to Motive <br /> <br /> Tuesday lunch Riata Bar &amp; Grill - Austinites welcome<br /> <br /> Wednesday late afternoon - some Rest &amp; Relaxation such as Barton Springs? Segway Tour? <br /> <br /> Noon CST daily con call for status updates<br /> <br /> Typical daily schedule will be approximately 9:30am - 6:00pm CST. We can't stay later every day, but on Monday we can stay late as long as you let Anne know so that she can tell the security personnel when everyone expects to leave (8 or 9 at the very latest it sounds like).<br /> <br /> === Remote participation ===<br /> We're going to do our best to allow remote participants to take part in the event. We will be holding a daily phone call in the afternoon for all participants. [[User:Seth|Seth]] will be available at OLPC's office as a direct contact for unanswered questions, or if one of the (Cambridge) development team needs to be reached.<br /> <br /> Noon CST daily con call for status updates<br /> <br /> Remote contributors:<br /> * [[User:Seth|Seth]]<br /> * Greg Dek<br /> * Christoph<br /> * David Cramer<br /> * Emily Kaplan<br /> <br /> Unconfirmed:<br /> * Faisal Anwar (tentative)<br /> * Robert Nagle<br /> * Scott Nesbitt <br /> * Belinda Lopez<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8309 2008-08-21T18:15:53Z

<p>Annegentle: /* BookSprint August 2008 */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint August 2008 ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> ''Accomodations ''<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> Since I'm not having much luck convincing Austinites that picking people up at the airport is great fun with many benefits, it<br /> looks likely that you all should use the Super Shuttle (www.supershuttle.com) or Capital Metro's airport routes (www.capmetro.org/riding/airport.asp) rather than get picked up. Taking or sharing a cab is also an option.<br /> <br /> ''Using FLOSS Manuals''<br /> <br /> If you're not familiar with the FLOSS Manuals interface, you might<br /> want to take a look at this screencast for an overview/starter guide<br /> http://www.screencast.com/t/wHSXac3b43.<br /> <br /> ''XO Hardware for the Sprint''<br /> <br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> ''Schedule''<br /> <br /> Sunday 11:00 AM Goal setting session at the hotel (Changed from 3:00 because Adam Holt has a prior meeting that afternoon.)<br /> <br /> Sunday 7:00 PM Mozart's meetup with the XO-Austin user group<br /> <br /> Monday 9:00 AM Anne meeting in the hotel lobby to walk over to Motive <br /> <br /> Tuesday lunch Riata Bar &amp; Grill - Austinites welcome<br /> <br /> Noon CST daily con call for status updates<br /> <br /> Typical daily schedule will be approximately 9:30am - 6:00pm CST but we are allowed to stay later if needed.<br /> <br /> === Remote participation ===<br /> We're going to do our best to allow remote participants to take part in the event. We will be holding a daily phonecall in the afternoon for all participants. [[User:Seth|Seth]] will be available at OLPC's office as a direct contact for unanswered questions, or if one of the (Cambridge) development team needs to be reached.<br /> <br /> Noon CST daily con call for status updates<br /> <br /> Remote contributors:<br /> * [[User:Seth|Seth]]<br /> * Greg Dek<br /> * Christoph<br /> * David Cramer<br /> * Emily Kaplan<br /> <br /> Unconfirmed:<br /> * Faisal Anwar (tentative)<br /> * Robert Nagle<br /> * Scott Nesbitt <br /> * Belinda Lopez<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8307 2008-08-21T17:55:44Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint August 2008 ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> ''Accomodations ''<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> Since I'm not having much luck convincing Austinites that picking people up at the airport is great fun with many benefits, it<br /> looks likely that you all should use the Super Shuttle (www.supershuttle.com) or Capital Metro's airport routes (www.capmetro.org/riding/airport.asp) rather than get picked up. Taking or sharing a cab is also an option.<br /> <br /> ''Using FLOSS Manuals''<br /> <br /> If you're not familiar with the FLOSS Manuals interface, you might<br /> want to take a look at this screencast for an overview/starter guide<br /> http://www.screencast.com/t/wHSXac3b43.<br /> <br /> <br /> ''XO Hardware for the Sprint''<br /> <br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> ''Schedule''<br /> <br /> Sunday 11:00 AM Goal setting session at the hotel (Changed from 3:00 because Adam Holt has a prior meeting that afternoon.)<br /> Sunday 7:00 PM Mozart's meetup with the XO-Austin user group<br /> Monday 9:00 AM Anne meeting in the hotel lobby to walk over to Motive <br /> Tuesday lunch Riata Bar &amp; Grill - Austinites welcome<br /> <br /> Noon CST daily con call for status updates<br /> <br /> Typical daily schedule will be approximately 9:30am - 6:00pm CST but we are allowed to stay later if needed.<br /> <br /> === Remote participation ===<br /> We're going to do our best to allow remote participants to take part in the event. We will be holding a daily phonecall in the afternoon for all participants. [[User:Seth|Seth]] will be available at OLPC's office as a direct contact for unanswered questions, or if one of the (Cambridge) development team needs to be reached.<br /> <br /> Remote contributors:<br /> * [[User:Seth|Seth]]<br /> * Greg Dek<br /> * Christoph<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8306 2008-08-21T17:53:33Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> ''Using FLOSS Manuals''<br /> <br /> If you're not familiar with the FLOSS Manuals interface, you might<br /> want to take a look at this screencast for an overview/starter guide<br /> http://www.screencast.com/t/wHSXac3b43.<br /> <br /> <br /> ''XO Hardware for the Sprint''<br /> <br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> ''Schedule''<br /> <br /> Sunday 11:00 AM Goal setting session at the hotel (Changed from 3:00 because Adam Holt has a prior meeting that afternoon.)<br /> Sunday 7:00 PM Mozart's meetup with the XO-Austin user group<br /> Monday 9:00 AM Anne meeting in the hotel lobby to walk over to Motive <br /> Tuesday lunch Riata Bar &amp; Grill - Austinites welcome<br /> <br /> Noon CST daily con call for status updates<br /> <br /> Typical daily schedule will be approximately 9:30am - 6:00pm CST but we are allowed to stay later if needed.<br /> <br /> === Remote participation ===<br /> We're going to do our best to allow remote participants to take part in the event. We will be holding a daily phonecall in the afternoon for all participants. [[User:Seth|Seth]] will be available at OLPC's office as a direct contact for unanswered questions, or if one of the (Cambridge) development team needs to be reached.<br /> <br /> Remote contributors:<br /> * [[User:Seth|Seth]]<br /> * Greg Dek<br /> * Christoph<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8259 2008-08-19T20:42:19Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> ''XO Hardware for the Sprint''<br /> <br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> ''Schedule''<br /> <br /> Sunday 3:00 PM Start and goal setting session, at the hotel<br /> Sunday 7:00 PM Mozart's meetup with the XO-Austin user group<br /> <br /> Monday 9:00 AM Anne meeting in the hotel lobby to walk over to Motive <br /> <br /> Noon CST daily con call for status updates<br /> <br /> Typical daily schedule will be approximately 9:30am - 6:00pm CST but we are allowed to stay later if needed.<br /> <br /> === Remote participation ===<br /> We're going to do our best to allow remote participants to take part in the event. We will be holding a daily phonecall in the afternoon for all participants. [[User:Seth|Seth]] will be available at OLPC's office as a direct contact for unanswered questions, or if one of the (Cambridge) development team needs to be reached.<br /> <br /> Remote contributors:<br /> * [[User:Seth|Seth]]<br /> * Greg Dek<br /> * Christoph<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8075 2008-08-16T18:00:47Z

<p>Annegentle: /* BookSprint */ XO hardware added</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> ''XO Hardware for the Sprint&quot;&quot;<br /> I've got a spreadsheet set up with the names of all the XOs we can use<br /> at the BookSprint. I have 8 now and Mikus will do the updates (I<br /> already requested dev keys on all of them.) Here's the published<br /> version: http://spreadsheets.google.com/pub?key=pjAQh2AGJq8cooRMaUwKlWg.<br /> I can add everyone as collaborators next week once we get all the data<br /> filled in, so when updates are done to a machine, the writer can just<br /> update the spreadsheet.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8064 2008-08-16T13:58:19Z

<p>Annegentle: </p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, (512) 219-6500 where attendees are staying. There is breakfast served at the hotel.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=8063 2008-08-16T13:48:58Z

<p>Annegentle: </p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX, where attendees are staying. There is breakfast served at the hotel.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Repurposing the best from these [http://wiki.laptop.org/go/Documentation_Projects 20 pre-existing documents] will be key. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Talk:Documentation_Team&diff=8062 2008-08-16T11:48:00Z

<p>Annegentle: /* Try Sugar I */</p> <hr /> <div>One programmer's opinion:<br /> <br /> I believe it is a mistake to rely on &quot;read the code&quot; as a solution to sugar documentation. There needs to be a document for each class this organization invents. The document should contain at least the following:<br /> <br /> 1. What the class is for and when it's appropriate for the developer to use it.<br /> <br /> 2. What the class is derived from (if anything), what base-class methods/attributes it overrides/extends/hides and what new methods/attributes are provided. *<br /> <br /> 3. Methods and attributes reference (it could be appropriate for this part to be generated from the code).<br /> <br /> <br /> (*) Pardon me if that's not Python-speak: I'm new to the Python language. Methods are the things in a class that start with &quot;def&quot;; attributes are the class's data.<br /> <br /> <br /> Finally, there needs to be both an index to classes and a &quot;roadmap&quot; showing how the classes relate to each other. Examples would be nice to have, too, but this &quot;developers' reference guide&quot; is essential -- otherwise the learning curve is too steep and third-party developers will go devote their time to some easier-understood project.<br /> <br /> I hate to hold Microsoft up as a good example (they aren't -- they're only so-so when it comes to documentation), but the hyperlinked documentation for the Microsoft Foundation Class library is fairly decent. The documentation for the Swing library in Java is nearly as good, though the class library reference part could use a better layout.<br /> <br /> A nice-to-have in all of this would be the ability to call up the relevent documentation while coding, as can be done in Visual Studio.<br /> [[User:Davewa|dave]] 20:03, 19 May 2008 (UTC)<br /> <br /> <br /> <br /> * sugar-base and sugar-toolkit has API documentation in the code. What tool do we use to generate html? Where do we generate it and where we make it available? Do we need to build them to generate docs?<br /> :* See http://wiki.laptop.org/go/API_reference#System_Services.2FHardware for PyDoc and epydoc references. Also, how do we want to reference http://wiki.laptop.org/go/API_reference? Is it out of date? Do we start from scratch, or just update that? --[[User:Morgs|Morgs]] 14:57, 30 May 2008 (UTC)<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Collaboration API. I have no idea, morgs we need your help here.<br /> :* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration] --[[User:Morgs|Morgs]] 19:59, 15 May 2008 (UTC)<br /> ::* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> :::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> :::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Manual ==<br /> <br /> * Setup a development environment. This is wiki oriented so we should probably not even mention jhbuild (we should definitely not do so until we have a bunch of autobuild slaves running).<br /> * &quot;Write your activity&quot; tutorial. It should include all the important bits: graphic controls, datastore, collaboration<br /> ** see OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook] [[User:ChristophD|ChristophD]] 03:59, 30 May 2008 (UTC)<br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> <br /> == Try Sugar I ==<br /> <br /> I think it is a critical part of this effort that we document how to try Sugar on existing platforms (e.g., use of a LiveCD). This will make it easier for teachers and parents to get comfortable enough to make the capital investment in the hardware. --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> <br /> I want to think about this and figure out a good approach. We have a teacher in Austin who might be a good person to send drafts to. I'll try to think of a good way to integrate this into the doc. [[User:Annegentle|Annegentle]] 11:47, 16 August 2008 (UTC)<br /> <br /> == Try Sugar II ==<br /> <br /> I think it is also a critical part of this effort to introduce to the user community the notion of modifying code. Perhaps an example of modifying the Home View from a circle to a spiral would be a good example? --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> <br /> I'd love to learn enough to write a tutorial on this scenario. Let's work on it. [[User:Annegentle|Annegentle]] 11:46, 16 August 2008 (UTC)</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Talk:Documentation_Team&diff=8061 2008-08-16T11:47:05Z

<p>Annegentle: /* Try Sugar II */</p> <hr /> <div>One programmer's opinion:<br /> <br /> I believe it is a mistake to rely on &quot;read the code&quot; as a solution to sugar documentation. There needs to be a document for each class this organization invents. The document should contain at least the following:<br /> <br /> 1. What the class is for and when it's appropriate for the developer to use it.<br /> <br /> 2. What the class is derived from (if anything), what base-class methods/attributes it overrides/extends/hides and what new methods/attributes are provided. *<br /> <br /> 3. Methods and attributes reference (it could be appropriate for this part to be generated from the code).<br /> <br /> <br /> (*) Pardon me if that's not Python-speak: I'm new to the Python language. Methods are the things in a class that start with &quot;def&quot;; attributes are the class's data.<br /> <br /> <br /> Finally, there needs to be both an index to classes and a &quot;roadmap&quot; showing how the classes relate to each other. Examples would be nice to have, too, but this &quot;developers' reference guide&quot; is essential -- otherwise the learning curve is too steep and third-party developers will go devote their time to some easier-understood project.<br /> <br /> I hate to hold Microsoft up as a good example (they aren't -- they're only so-so when it comes to documentation), but the hyperlinked documentation for the Microsoft Foundation Class library is fairly decent. The documentation for the Swing library in Java is nearly as good, though the class library reference part could use a better layout.<br /> <br /> A nice-to-have in all of this would be the ability to call up the relevent documentation while coding, as can be done in Visual Studio.<br /> [[User:Davewa|dave]] 20:03, 19 May 2008 (UTC)<br /> <br /> <br /> <br /> * sugar-base and sugar-toolkit has API documentation in the code. What tool do we use to generate html? Where do we generate it and where we make it available? Do we need to build them to generate docs?<br /> :* See http://wiki.laptop.org/go/API_reference#System_Services.2FHardware for PyDoc and epydoc references. Also, how do we want to reference http://wiki.laptop.org/go/API_reference? Is it out of date? Do we start from scratch, or just update that? --[[User:Morgs|Morgs]] 14:57, 30 May 2008 (UTC)<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Collaboration API. I have no idea, morgs we need your help here.<br /> :* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration] --[[User:Morgs|Morgs]] 19:59, 15 May 2008 (UTC)<br /> ::* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> :::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> :::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Manual ==<br /> <br /> * Setup a development environment. This is wiki oriented so we should probably not even mention jhbuild (we should definitely not do so until we have a bunch of autobuild slaves running).<br /> * &quot;Write your activity&quot; tutorial. It should include all the important bits: graphic controls, datastore, collaboration<br /> ** see OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook] [[User:ChristophD|ChristophD]] 03:59, 30 May 2008 (UTC)<br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> <br /> == Try Sugar I ==<br /> <br /> I think it is a critical part of this effort that we document how to try Sugar on existing platforms (e.g., use of a LiveCD). This will make it easier for teachers and parents to get comfortable enough to make the capital investment in the hardware. --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> <br /> == Try Sugar II ==<br /> <br /> I think it is also a critical part of this effort to introduce to the user community the notion of modifying code. Perhaps an example of modifying the Home View from a circle to a spiral would be a good example? --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> <br /> I'd love to learn enough to write a tutorial on this scenario. Let's work on it. [[User:Annegentle|Annegentle]] 11:46, 16 August 2008 (UTC)</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Talk:Documentation_Team&diff=8060 2008-08-16T11:46:52Z

<p>Annegentle: /* Try Sugar II */</p> <hr /> <div>One programmer's opinion:<br /> <br /> I believe it is a mistake to rely on &quot;read the code&quot; as a solution to sugar documentation. There needs to be a document for each class this organization invents. The document should contain at least the following:<br /> <br /> 1. What the class is for and when it's appropriate for the developer to use it.<br /> <br /> 2. What the class is derived from (if anything), what base-class methods/attributes it overrides/extends/hides and what new methods/attributes are provided. *<br /> <br /> 3. Methods and attributes reference (it could be appropriate for this part to be generated from the code).<br /> <br /> <br /> (*) Pardon me if that's not Python-speak: I'm new to the Python language. Methods are the things in a class that start with &quot;def&quot;; attributes are the class's data.<br /> <br /> <br /> Finally, there needs to be both an index to classes and a &quot;roadmap&quot; showing how the classes relate to each other. Examples would be nice to have, too, but this &quot;developers' reference guide&quot; is essential -- otherwise the learning curve is too steep and third-party developers will go devote their time to some easier-understood project.<br /> <br /> I hate to hold Microsoft up as a good example (they aren't -- they're only so-so when it comes to documentation), but the hyperlinked documentation for the Microsoft Foundation Class library is fairly decent. The documentation for the Swing library in Java is nearly as good, though the class library reference part could use a better layout.<br /> <br /> A nice-to-have in all of this would be the ability to call up the relevent documentation while coding, as can be done in Visual Studio.<br /> [[User:Davewa|dave]] 20:03, 19 May 2008 (UTC)<br /> <br /> <br /> <br /> * sugar-base and sugar-toolkit has API documentation in the code. What tool do we use to generate html? Where do we generate it and where we make it available? Do we need to build them to generate docs?<br /> :* See http://wiki.laptop.org/go/API_reference#System_Services.2FHardware for PyDoc and epydoc references. Also, how do we want to reference http://wiki.laptop.org/go/API_reference? Is it out of date? Do we start from scratch, or just update that? --[[User:Morgs|Morgs]] 14:57, 30 May 2008 (UTC)<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Collaboration API. I have no idea, morgs we need your help here.<br /> :* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration] --[[User:Morgs|Morgs]] 19:59, 15 May 2008 (UTC)<br /> ::* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> :::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> :::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Manual ==<br /> <br /> * Setup a development environment. This is wiki oriented so we should probably not even mention jhbuild (we should definitely not do so until we have a bunch of autobuild slaves running).<br /> * &quot;Write your activity&quot; tutorial. It should include all the important bits: graphic controls, datastore, collaboration<br /> ** see OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook] [[User:ChristophD|ChristophD]] 03:59, 30 May 2008 (UTC)<br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> <br /> == Try Sugar I ==<br /> <br /> I think it is a critical part of this effort that we document how to try Sugar on existing platforms (e.g., use of a LiveCD). This will make it easier for teachers and parents to get comfortable enough to make the capital investment in the hardware. --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> <br /> == Try Sugar II ==<br /> <br /> I think it is also a critical part of this effort to introduce to the user community the notion of modifying code. Perhaps an example of modifying the Home View from a circle to a spiral would be a good example? --[[User:Walter|Walter]] 17:54, 11 August 2008 (UTC)<br /> I'd love to learn enough to write a tutorial on this scenario. Let's work on it. [[User:Annegentle|Annegentle]] 11:46, 16 August 2008 (UTC)</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7955 2008-08-14T15:51:22Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX <br /> I'm also checking into another hotel where a friend works but it's not within walking distance.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7954 2008-08-14T15:49:55Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels and may get a discounted rate at one a friend works at.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> David Farning (Sugar Labs affiliate and community builder)<br /> Arr AUS 7:21pm Sat, Aug 23, 2008<br /> Dep AUS 6:00am Sat, Aug 30, 2008<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX <br /> I'm also checking into another hotel where a friend works but it's not within walking distance.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7953 2008-08-14T15:12:46Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels and may get a discounted rate at one a friend works at.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> Dep AUS Sun, Aug 30<br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX <br /> I'm also checking into another hotel where a friend works but it's not within walking distance.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7951 2008-08-14T15:10:24Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels and may get a discounted rate at one a friend works at.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> Adam Hyde (founder of FLOSS Manuals)<br /> Arr AUS 10:30AM Sat, Aug 23 <br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX <br /> I'm also checking into another hotel where a friend works but it's not within walking distance.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7944 2008-08-13T20:02:08Z

<p>Annegentle: /* BookSprint */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels and may get a discounted rate at one a friend works at.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> <br /> The venue has changed from Outernet to Motive - their address is:<br /> 12515 Research Blvd<br /> Austin, TX 78759<br /> www.motive.com<br /> <br /> There's a hotel within walking distance, Extended Stay America, at <br /> 12424 Research Blvd, Austin, TX <br /> I'm also checking into another hotel where a friend works but it's not within walking distance.<br /> <br /> I'd like to arrange pickup at the airport for all participants - to avoid cab fares and so forth. So let me get some work going for that, and I'll update this page with more information.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7848 2008-08-09T14:49:06Z

<p>Annegentle: Added BookSprint section, added arrival and departure info</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> == BookSprint ==<br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels and may get a discounted rate at one a friend works at.<br /> <br /> ''Arrival/Departure plans''<br /> Brian Jordan (activities/sugar/Pygame hacker, OLPC intern exploring 3rd World deployment)<br /> Arr AUS 12:25PM TUE Aug 26<br /> Dep AUS 5:05PM THU Aug 28<br /> <br /> Adam Holt (100-person support gang founder &amp; coordinator)<br /> Arr AUS 11:10AM SAT Aug 23<br /> Dep AUS 6:35AM SAT Aug 30<br /> <br /> Walter Bender (former president of software and content at OLPC, writer of Getting Started at laptop.org/start, Sugar Labs affiliate)<br /> Arr AUS morning Sun Aug 24<br /> Dep AUS morning Fri Aug 29<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7835 2008-08-08T04:26:08Z

<p>Annegentle: /* User Manuals */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. <br /> <br /> Attendee listing (fluid and changing) is at http://flossmanuals.net/donate.<br /> <br /> One attendee plans to camp. Anne Gentle is working on more detailed information on local hotels near the host location - but several hotels are near the host location. The location looks like it’ll be Outernet, which is located in Northwest Austin. A map is here: http://www.outer.net/contact.php.<br /> <br /> Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> '''See also'''<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]<br /> <br /> ==Topic Ideas==<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7789 2008-08-03T03:16:29Z

<p>Annegentle: /* Tutorials */</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> See also<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook] <br /> <br /> Topic Ideas<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> * Ideally, each Activity will have a tutorial within a manual on FLOSS Manuals. Here's a rough outline for each Activity Manual:<br /> <br /> Introduction<br /> <br /> Getting Started <br /> <br /> Tutorials<br /> <br /> Reference<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team&diff=7788 2008-08-03T03:15:07Z

<p>Annegentle: /* User Manuals */ adding outlines and BookSprint info</p> <hr /> <div>{{Translations <br /> | [[DocumentationTeam|english]] &amp;#124; [[DocumentationTeam/lang-es|español]] }}<br /> &lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}&lt;/noinclude&gt;<br /> <br /> Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.<br /> <br /> == User Manuals ==<br /> We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .<br /> <br /> FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. Here are rough working outlines:<br /> <br /> Sugar Manual<br /> <br /> Connecting to the network <br /> <br /> Installing and configuring <br /> <br /> Personalizing Sugar <br /> <br /> Updating the version <br /> <br /> Installing New Activities <br /> <br /> Interface <br /> <br /> Neighborhood View <br /> <br /> Group View <br /> <br /> Home View <br /> <br /> Activity View <br /> <br /> Joining Activities <br /> <br /> Switching Activities <br /> <br /> Exiting Activities <br /> <br /> Troubleshooting Sugar<br /> <br /> <br /> XO Manual<br /> <br /> Getting started with the XO <br /> <br /> About computers <br /> <br /> Opening the XO <br /> <br /> Starting the XO <br /> <br /> Keyboard Shortcuts <br /> <br /> Conserving Disk Space <br /> <br /> Maintenance <br /> <br /> Backing Up <br /> <br /> Caring for Your XO <br /> <br /> Charging the Battery <br /> <br /> Replacing the Battery <br /> <br /> Screen <br /> <br /> Safety <br /> <br /> Repairing Your XO<br /> <br /> Avoiding Loss of Your XO <br /> <br /> Hardware Specifications <br /> <br /> Getting Support <br /> <br /> <br /> See also<br /> * [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.<br /> * OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook] <br /> <br /> Topic Ideas<br /> * Setup a development environment. With and without jhbuild.<br /> * &quot;Write your activity&quot; tutorial. It should include:<br /> ** graphic controls,<br /> ** datastore, <br /> ** collaboration.<br /> <br /> == Programming References ==<br /> === [http://api.sugarlabs.org API] ===<br /> <br /> The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.<br /> <br /> References <br /> * http://wiki.laptop.org/go/API_reference?<br /> * Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.<br /> * Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].<br /> <br /> :* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the &quot;manual&quot;. One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]<br /> ::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)<br /> ::* Hey, I came up with an alternate &quot;reference&quot; implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)<br /> * Low level API (non-python activities). We should just move bert document on this wiki.<br /> :this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with <br /> :* http://wiki.laptop.org/go/Sugar_Factory<br /> :* http://www.catmoran.com/olpc/#sugxterm<br /> <br /> == Tutorials ==<br /> <br /> * Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.<br /> * Etoys based activity tutorial?<br /> <br /> == Glossary ==<br /> <br /> [[DocumentationTeam/Glossary | Glossary]]<br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=User:Walter/sandbox&diff=7210 2008-07-10T03:51:03Z

<p>Annegentle: changed connecting to connected... it was bugging me :)</p> <hr /> <div>Wiki-based Getting Started Guide (based on Joyride 2037)<br /> <br /> * [[User:Walter/sandbox/Connecting | Getting Connected]]<br /> * [[User:Walter/sandbox/Home | Home View]]<br /> * [[User:Walter/sandbox/Neighborhood | Neighborhood View]]<br /> * [[User:Walter/sandbox/Frame | The Frame]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team/Book_Sprint&diff=7194 2008-07-09T19:13:16Z

<p>Annegentle: /* Location */</p> <hr /> <div>&lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam}}&lt;/noinclude&gt;<br /> <br /> We are planning a book sprint this fall for create a user's guide for Sugar. Please add add you comment and concerns here or on the discussion page.<br /> <br /> == Location ==<br /> OLPC offices (Boston)<br /> <br /> yet unknown, Anne investigating (Austin)<br /> <br /> == Date ==<br /> late August (tentative proposal 16-23)<br /> <br /> == Scope of documentation for sprint ==<br /> Audience: kids, parents, and teachers. End-users, basically.<br /> <br /> Getting Started Guide for the file system, wireless connections, everything you do without Activities. <br /> Walter Bender has started with [User:Walter/sandbox], which points out where the Floss Manual can be updated to be hardware-free (for example, his annotations with OLPC-XO-1-specific hints for keyboard shortcuts and specifics for the OLPC-XO-1 hardware). Updates should be made to http://en.flossmanuals.net/olpc_simple.<br /> <br /> Getting Started with an Activity for specific Activities, such as Browse and Record.<br /> A starter manual for the Record activity can be found at http://en.flossmanuals.net/olpc_record. Priorities needed for which Activities to start first.<br /> <br /> == Recruited/invited writers (expect about 5-6 in person) ==<br /> Anne Gentle - Austin, Texas<br /> <br /> Adam Hyde - Netherlands<br /> <br /> David Farning - Wisconsin<br /> <br /> Walter Bender - East coast<br /> <br /> Greg DeKoenigsberg - Raleigh NC<br /> <br /> Emily Kaplan - Illinois (Chicago area)<br /> <br /> Robert Nagle - Houston<br /> <br /> Janet Swisher - Austin<br /> <br /> David Cramer - Austin</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team/Book_Sprint&diff=7193 2008-07-09T19:13:02Z

<p>Annegentle: /* Recruited/invited writers (expect about 5-6 in person) */</p> <hr /> <div>&lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam}}&lt;/noinclude&gt;<br /> <br /> We are planning a book sprint this fall for create a user's guide for Sugar. Please add add you comment and concerns here or on the discussion page.<br /> <br /> == Location ==<br /> OLPC offices (Boston)<br /> yet unknown, Anne investigating (Austin)<br /> <br /> == Date ==<br /> late August (tentative proposal 16-23)<br /> <br /> == Scope of documentation for sprint ==<br /> Audience: kids, parents, and teachers. End-users, basically.<br /> <br /> Getting Started Guide for the file system, wireless connections, everything you do without Activities. <br /> Walter Bender has started with [User:Walter/sandbox], which points out where the Floss Manual can be updated to be hardware-free (for example, his annotations with OLPC-XO-1-specific hints for keyboard shortcuts and specifics for the OLPC-XO-1 hardware). Updates should be made to http://en.flossmanuals.net/olpc_simple.<br /> <br /> Getting Started with an Activity for specific Activities, such as Browse and Record.<br /> A starter manual for the Record activity can be found at http://en.flossmanuals.net/olpc_record. Priorities needed for which Activities to start first.<br /> <br /> == Recruited/invited writers (expect about 5-6 in person) ==<br /> Anne Gentle - Austin, Texas<br /> <br /> Adam Hyde - Netherlands<br /> <br /> David Farning - Wisconsin<br /> <br /> Walter Bender - East coast<br /> <br /> Greg DeKoenigsberg - Raleigh NC<br /> <br /> Emily Kaplan - Illinois (Chicago area)<br /> <br /> Robert Nagle - Houston<br /> <br /> Janet Swisher - Austin<br /> <br /> David Cramer - Austin</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team/Book_Sprint&diff=7192 2008-07-09T19:12:23Z

<p>Annegentle: </p> <hr /> <div>&lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam}}&lt;/noinclude&gt;<br /> <br /> We are planning a book sprint this fall for create a user's guide for Sugar. Please add add you comment and concerns here or on the discussion page.<br /> <br /> == Location ==<br /> OLPC offices (Boston)<br /> yet unknown, Anne investigating (Austin)<br /> <br /> == Date ==<br /> late August (tentative proposal 16-23)<br /> <br /> == Scope of documentation for sprint ==<br /> Audience: kids, parents, and teachers. End-users, basically.<br /> <br /> Getting Started Guide for the file system, wireless connections, everything you do without Activities. <br /> Walter Bender has started with [User:Walter/sandbox], which points out where the Floss Manual can be updated to be hardware-free (for example, his annotations with OLPC-XO-1-specific hints for keyboard shortcuts and specifics for the OLPC-XO-1 hardware). Updates should be made to http://en.flossmanuals.net/olpc_simple.<br /> <br /> Getting Started with an Activity for specific Activities, such as Browse and Record.<br /> A starter manual for the Record activity can be found at http://en.flossmanuals.net/olpc_record. Priorities needed for which Activities to start first.<br /> <br /> == Recruited/invited writers (expect about 5-6 in person) ==<br /> Anne Gentle - Austin, Texas<br /> Adam Hyde - Netherlands<br /> David Farning - Wisconsin<br /> Walter Bender - East coast<br /> Greg DeKoenigsberg - Raleigh NC<br /> Emily Kaplan - Illinois (Chicago area)<br /> Robert Nagle - Houston<br /> Janet Swisher - Austin<br /> David Cramer - Austin</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=Documentation_Team/Contacts&diff=6860 2008-06-28T19:52:45Z

<p>Annegentle: /* List of Editors */</p> <hr /> <div>&lt;noinclude&gt;{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br /> {{TeamHeader|DocumentationTeam}}&lt;/noinclude&gt;<br /> <br /> == Mailing List ==<br /> tbd<br /> <br /> == IRC Channel ==<br /> tbd<br /> <br /> == List of Editors ==<br /> <br /> {|<br /> ! Area of Specialty''' !! '''Wiki Username'''<br /> |-<br /> <br /> | Mentor || Edward [[User:Mokurai|Mokurai]] Cherlin, API tech writer, educator, linguist, mathematician and a few other things.<br /> <br /> |-<br /> <br /> | Coordination || Anne Gentle [[User:Annegentle|Annegentle]], parent, technical writer, blogger. <br /> |}<br /> <br /> <br /> [[Category:DocumentationTeam]]</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=User:Annegentle&diff=6859 2008-06-28T19:43:52Z

<p>Annegentle: </p> <hr /> <div>Anne Gentle is a senior technical writer volunteering for the [[DocumentationTeam | Documentation Team]]. I have two kids and love introducing technology to them. I currently work a flexible 30-hour work week to spend more time with my family and home, but I like to stay busy. I have a lot of energy because these busy but balanced days fill me up rather than tire me out.</div>

Annegentle https://wiki.sugarlabs.org/index.php?title=User:Annegentle&diff=6858 2008-06-28T19:42:57Z

<p>Annegentle: New page: Anne Gentle is a senior technical writer volunteering for the Documentation Team. I have two kids and love introducing technology to them. I currently work a flexible 30-hour work week to ...</p> <hr /> <div>Anne Gentle is a senior technical writer volunteering for the Documentation Team. I have two kids and love introducing technology to them. I currently work a flexible 30-hour work week to spend more time with my family and home, but I like to stay busy. I have a lot of energy because these busy but balanced days fill me up rather than tire me out.</div>

Annegentle