https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=MartinDengler&feedformat=atomSugar Labs - User contributions [en]2024-03-28T10:27:11ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=Features/Clock_in_Frame&diff=100946Features/Clock in Frame2017-10-11T02:33:51Z<p>MartinDengler: add prior links</p>
<hr />
<div>== Summary ==<br />
A digital clock that displays in the lower frame<br />
<br />
== Owner ==<br />
* Name: <br />
<br />
* Email: <br />
<br />
== Current status ==<br />
* Targeted release: <br />
* Last updated: <br />
* Percentage of completion: 0%<br />
<br />
== Detailed Description ==<br />
<br />
== Benefit to Sugar ==<br />
<br />
== Scope ==<br />
<br />
==UI Design==<br />
<br />
See https://wiki.sugarlabs.org/go/Design_Team/Proposals/Frame<br />
Old mockups at https://gist.github.com/mdengler/c4f5ce5f04a9560a779ed990b881cd63 .<br />
<br />
== How To Test ==<br />
<br />
== User Experience ==<br />
The user will see a digital clock when they expose the frame, a dropdown menu to adjust the rtc would be good too<br />
<br />
== Dependencies ==<br />
<br />
== Contingency Plan ==<br />
<br />
== Documentation ==<br />
<br />
== Release Notes ==<br />
<br />
== Comments and Discussion ==<br />
<br />
There is much prior discussion, including at https://wiki.sugarlabs.org/go/Design_Team/Proposals/Frame</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=QEMU&diff=100927QEMU2017-10-09T04:52:39Z<p>MartinDengler: remove incorrect 'smart' quotes from egrep command line</p>
<hr />
<div><noinclude>[[Category:Virtual machine or platform emulator]]</noinclude><br />
The [[wikipedia:QEMU|QEMU]] emulation environment, including the accelerators kqemu and kvm, lets you run a variety of software on your computer in a protected environment. This includes software that is incompatible with your operating system, and software for different processors. Other options are [[VirtualBox]] (Free Software) and [[VMware]], commercial software with a no-cost runtime version.<br />
<br />
==Use Cases==<br />
<br />
* [[Windows]]: Run [[Sugar]], [[olpc:School_server|School Server]], Linux more generally (for example, as a method for shifting from Windows to Linux)<br />
* [[Macintosh]]: Run Sugar, School Server, any Linux<br />
* Linux on Linux: [[Fedora]] (including School Server) on [[Ubuntu]] and the like<br />
* Sugar on Arm processors: Encore [[Mobilis]] and proposed [[olpc:XO-2|XO-2]]<br />
* BSD: qemu in development<br />
<br />
You can run [[Emulator image files]] of almost any version of Sugar and the XS school server in qemu, including daily builds, releases, Sugar on a Stick, Live CDs, sugar-jhbuild, and whatever else we come up with. As we [[port Sugar]] to other computer architectures, such as [[ARM]], this will become increasingly important, so that developers and testers do not have to purchase one of each. There are emulation modules for qemu to emulate a wide range of processors and peripherals.<br />
<br />
==Getting Started==<br />
<br />
One of these commands will work in most Linux distributions, using yum for Red Hat-style packages on Fedora and related distros, or apt-get for Debian-style packages on Debian, Ubuntu, and related distros. Otherwise, consult system documentation for package installation or installing from source.<br />
<br />
* yum install qemu<br />
* apt-get install qemu<br />
<br />
There are full-screen text and windowed graphical package manager clients such as aptitude and Synaptic to assist you.<br />
<br />
You should install an accelerator if at all possible, that is, if your processor supports virtualization in hardware. To find out whether it does, run the command<br />
<br />
$ egrep '(vmx|svm)' /proc/cpuinfo<br />
flags : fpu vme de pse tsc msr pae mce cx8 … vmx …<br />
flags : fpu vme de pse tsc msr pae mce cx8 … vmx …<br />
<br />
Some of the output is truncated in this example, and your results will probably differ elsewhere.<br />
<br />
There are two sets of flags because the processor used for this example has two cores. You would be looking for the “vmx” flag for an Intel-VT and the “svm” flag for an AMD-V processor.<br />
<br />
This test succeeds if you get any lines of text as a result, and fails if the result is blank.<br />
<br />
Installing KVM on Ubuntu is completely automatic, using<br />
<br />
$ apt-get install kvm<br />
<br />
The installation script gets the source code, compiles it into your kernel, and configures it to Just Work[TM]. Consult system documentation for other Linux distros and other OSs, or if you want to install kqemu instead. Either kqemu or kvm will give you something like a ten times performance boost, according to some sources. Your mileage may vary.<br />
<br />
==HOWTO==<br />
<br />
You can run qemu on a variety of disk images, including .iso (CD image format), .img (raw disk images), .qcow2 (qemu Copy-On-Write).<br />
<br />
===Creating disk images===<br />
<br />
To create an empty, compressed, expandable hard drive image of 300 GB capacity, enter<br />
<br />
$ qemu-img create my.img 300G<br />
<br />
using the name of the image file you want to create. The file will be in qcow2 format unless you specify another option.<br />
<br />
300 GB is what the School Server installation program wants. After installation, the image file will expand to 6.8 GB.<br />
<br />
$ qemu-img info XS.img<br><br />
image: XS.img<br><br />
file format: qcow2<br><br />
virtual size: 300G (322122547200 bytes)<br><br />
disk size: 6.8G<br><br />
cluster_size: 4096<br />
<br />
To convert a read-only CD image such as the [[Sugar on a Stick]] Beta to read-write qcow2,<br />
<br />
$ qemu-img convert -O qcow2 soas-beta.iso soas-beta.img<br />
<br />
===Minimum Command===<br />
<br />
$ qemu -hda hda.img<br />
<br />
or<br />
<br />
$ kvm -hda hda.img<br />
<br />
where you will substitute the name of your .img or other disk image file.<br />
<br />
Similarly for .iso images such as a Sugar LiveCD.<br />
<br />
$ kvm -cdrom cd.iso<br />
<br />
This may well boot your image and run, letting you log in and try out your software, assuming that your image file is valid and your processor is not too old. Depending on what your purpose is, you may prefer to add other options. Here are some examples. For full details, consult the qemu documentation.<br />
<br />
===Virtual Hardware===<br />
Set memory size, sound, networking, second hard drive, CD<br />
<br />
$ kvm -m 512 -soundhw es1370 -net user -net nic,model=rtl8139 -hda hda.img -hdb hdb.img -cdrom cd.iso<br />
<br />
===Install [http://wiki.laptop.org/go/School_server School Server]===<br />
<br />
$ kvm -m 512 -hda hda.img -cdrom XS.iso<br />
<br />
Pay attention to the boot sequence or it will just skip to its defaults. Press F12 when instructed to get to the boot menu, and tell it to boot from CD. Follow on-screen instructions. The process is almost completely automated. You will then have to set up networking to make this image accessible to jabber users and the like.<br />
<br />
===Command Line===<br />
<br />
This is actually a full terminal interface. It is good for remote virtual servers, where you don't want to run X (too unstable) but you want to be able to log in with ssh to administer the system. This also lets you run full-screen text mode applications such as aptitude and Midnight Commander. Curses is named for the full-screen terminal cursor, which can be anywhere in a 24 × 80 field.<br />
<br />
$ kvm -m 512 -curses -hda hda.img<br />
<br />
==qemu monitor==<br />
<br />
The key combination Ctl-Alt-2 (not F2) transfers you from your running virtual machine to the qemu command line. This lets you query the system, save and load snapshots, and perform other administrative tasts. See the qemu documentation for available commands. Unfortunately the process of saving snapshots is not reliable. It may appear to work, but create a corrupted image.<br />
<br />
==Resources==<br />
<br />
* [http://www.nongnu.org/qemu/ QEMU home page]<br />
* [http://virtualize-it.highspeed-data.net/index.php/tag/kqemu/ more on KVM]<br />
* [[OLPC:QEMU]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/Decisions&diff=100780Oversight Board/Decisions2017-09-15T18:15:52Z<p>MartinDengler: Update 2017-09-15 motion to reflect an additional vote</p>
<hr />
<div>This page (largely complete) is intended to be a one-stop place for reviewing all of the Sugar Labs oversight board (SLOB) actions and decisions.<br />
<br />
The date headlines are the date a motion is agreed, disagreed, or - in the case of motions to be voted on via email within 7 days of posting which did not get voted on - failed by timing out.<br />
<br />
We welcome non-member proposals at the time of a meeting; but they require both a proposer and seconder from among the members of the board. Several proposals that were not taken as motions are shown here struck out, as in <s>MEMBER MOTION</s>.<br />
<br />
==2017-09-15==<br />
;AGREED MOTION 2017-16 Proposed by Walter Bender, seconded by Samson Goddy<br />
Motion: To answer the questions posed by the SFC regarding the xo-computer icon as follows:<br />
:(Q1) Why is the XO logo included in the sugar-artwork repo now -- and does the SLOBs want to keep it there?<br />
:(A1) The xo-computer icon has been part of Sugar since we first designed and built Sugar (beginning in 2006) and we would like to keep it there until such time as the design team decides there is a reason to change it.<br />
:(Q2) Assuming the SLOBs want to keep the XO logo in sugar-artwork: what outcome would the SLOBs *prefer* to see happen? E.g., <br />
:- Does Sugar want downstream users to be able to redistribute and modify Sugar's codebase with or without the XO trademark file included in the program? <br />
:- Does the SLOBs want downstream users to be able to modify and redistribute the XO trademark image itself, or is that less important to Sugar? <br />
:(A2) Sugar Artwork, including the xo-computer icon, is currently licensed under the GPL and we would like our downstream users to be able to use all of our artwork under the terms of that license. As far as the use of any trademark image outside of the context of Sugar, we have no opinion.<br><br />
(5 in favor, 1 opposed, 1 vote not cast) See [http://lists.sugarlabs.org/archive/sugar-devel/2017-September/054709.html]<br />
<br />
==2017-09-14==<br />
;AGREED MOTION 2017-15 Proposed by Laura Vargas, seconded by Samson Goddy<br />
Motion: Sugar Labs to participate in GCI 2017.<br />
(6 in favor) [http://lists.sugarlabs.org/archive/iaep/2017-September/020111.html 1] [http://lists.sugarlabs.org/archive/iaep/2017-September/020113.html 2] [http://lists.sugarlabs.org/archive/iaep/2017-September/020114.html 3] [http://lists.sugarlabs.org/archive/iaep/2017-September/020115.html 4] [http://lists.sugarlabs.org/archive/iaep/2017-September/020119.html 5] [http://lists.sugarlabs.org/archive/iaep/2017-September/020121.html 6]<br />
<br />
==2017-09-05==<br />
;AGREED MOTION 2017-14 Proposed by Samson Goddy, seconded by Walter Bender.<br />
Motion: To add three contributors into the membership/election committee: Pericherla Seetaramaraju (Google Summer of Code Intern), Hirshi Patel (Contributor and Google Summer of Code Mentor) and Ibiam Chihurumnaya (Member of Sugar Labs).<br />
<br />
(5 in favor. 2 opposed) [http://lists.sugarlabs.org/archive/iaep/2017-September/020033.html]<br />
<br />
==2017-08-10==<br />
;AGREED MOTION 2017-13 Proposed by Laura Vargas, seconded by Samson Goddy. Motion: Sugar Labs Financial Manager will have a monthly stipend of US$ TBD in exchange for: 1 complete financial report per quarter and it's publication on the Sugar Labs Finance Wiki page maximum 30 calendar days after the end of the period. The format to be used should be compatible with the International Financial Reporting Standards or it's equivalent in the U.S..<br />
(4 in favor Laura, Samson, Lionel, Adam 3 opposed: Walter, Ignacio and Sameer)<br />
References for in favor votes:<br />
[https://lists.sugarlabs.org/archive/iaep/2017-August/019947.html]<br />
[https://lists.sugarlabs.org/archive/iaep/2017-August/019948.html]<br />
[https://lists.sugarlabs.org/archive/iaep/2017-August/019996.html]<br />
[https://lists.sugarlabs.org/archive/iaep/2017-August/019997.html]<br />
<br />
==2017-08-13==<br />
;FAILED MOTION 2017-12 Proposed by Walter Bender, seconded by Samson Goddy: Motion: Samson Goddy has been selected as a Sugar Labs representative to the Google Summer of Code mentor summit. He has requested a travel advance to cover the costs of his visa application. The advance, including wire fees comes to $US 627.05. This motion is to approve the travel advance. (As additional background, Google will be covering up to $2200 in travel expenses for two representatives to attend the summit. Since our other representative is local to the SF area, the bulk of that money would be available to cover Samson's travel, so the net impact on SL funds will be negligible.<br><br />
(3 in favor, 2 opposed, 2 abstain).<br />
[http://lists.sugarlabs.org/archive/iaep/2017-August/019979.html 1][http://lists.sugarlabs.org/archive/iaep/2017-August/019977.html 2]<br />
[http://lists.sugarlabs.org/archive/iaep/2017-August/019982.html 3]<br />
<br />
==2017-06-20==<br />
;FAILED MOTION 2017-11 Proposed by Laura Vargas, seconded by Samson Goddy [https://lists.sugarlabs.org/archive/iaep/2017-June/019872.html]: Sugar Labs will allocate a budget (To Be Defined) for "professional services" required to create a fitable image for Samson's and Ibiam's young XO partners in Africa. Sugar Labs will make an open call to the mailing list to find one or more professional to do it.<br><br />
(2 in favor, 5 abstain).<br />
<br />
== 2017-05-24 ==<br />
;FAILED MOTION 2017-10 Walter Bender, seconded by Sameer Verma [http://lists.sugarlabs.org/archive/iaep/2017-May/019751.html]: Sugar Labs agrees to cover up to US$2800 for expenses related to traveling to the Scratch2017BDX, 17th to 22nd of July, 2017 for Samson Goddy and Ibiam Chihurumnaya. (See [https://docs.google.com/document/d/152VDfUcdcGOHOFBLT3lG15sUFpzBeuBCGiNAGCSOLj4/edit?usp=sharing])<br>(Motion failed 3 in favor, 2 against, 1 abstain, 1 recused).<br />
<br />
== 2017-05-05 ==<br />
;AGREED MOTION 2017-09 Samson Goddy, seconded by Lionel Laske: Revise the mission statement to "Sugar Labs is a volunteer-run project whose mission is to reach global learners and educators with a collection of tools that enable them to explore, discover, create, and reflect in their local language. Sugar Labs distributes these tools freely and encourages its users to appropriate them, taking ownership and responsibility for their learning."<br>(Motion passed 5 in favor, 1 opposed, 1 abstained) http://meeting.sugarlabs.org/sugar-meeting/2017-05-05<br />
<br />
;PROPOSED MOTION 2017-08 Laura Vargas, not seconded: Revise the mission statement to "Sugar Labs is a community-run project whose mission is to support a collection of free/libre software tools that facilitates learners to discover, create, reflect, translate, share and appropriate such tools in sustainable and creative manners."<br />
<br />
== 2017-04-21 ==<br />
;FAILED MOTION 2017-07 Walter Bender, seconded by Samson Goddy: Revise the Sugar Labs mission statement to "Sugar Labs is a volunteer-run project whose mission is to reach global learners and educators with a collection of tools that enable them to explore, discover, create, and reflect in their local language. Sugar Labs distributes these tools freely and encourages its users to appropriate them, taking ownership and responsibility for their learning."<br>(Motion failed: 3 votes for, 4 abstained)<br />
<br />
== 2017-04-21 ==<br />
;FAILED MOTION 2017-06 Laura Vargas, seconded by Lionel Laske: Urgent maintenance budget of 500$ for fixing spam attacks on Sugar Network. Detail of the tasks to do are described in the Technical Service Request provided by Laura. It's an one shot motion to avoid interruption of service for Sugar Network users. Further investments on Sugar Network will be correlated to discussion about long-term support of the platform.<br>(3 votes for, 1 vote against, 1 recuse, 1 abstain and 1 member absent)<br />
<br />
== 2017-04-07 ==<br />
<br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-04-07T19:03:42.html]<br />
<br />
;AGREED MOTION 2017-05 Lionel Laske, seconded by Walter: Sugar Labs agrees to provide an advance for Ignacio to attend to the GCI summit.<br>(6 votes for)<br />
<br />
== 2017-02-19 ==<br />
<br />
[http://lists.sugarlabs.org/archive/iaep/2017-February/019377.htmlemail thread 1]<br />
[http://lists.sugarlabs.org/archive/iaep/2017-February/019388.html email thread 2]<br />
<br />
;AGREED MOTION 2017-04 Walter, posting by email a motion seconded by Laura Vargas: Sugar Labs agrees to participate in Outreachy 14 in order to promote and support women and minority participation in FOSS projects. The cost would be $5500 for one internship. The funds would come from our general funds.<br>(5 votes for, 2 votes yet to be received)<br />
<br />
== 2017-01-06 ==<br />
<br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-01-06T19:07:40 log]<br />
<br />
;AGREED MOTION 2017-03 Walter Bender, posting motion seconded by Jose Miguel Garcia: To appoint volunteers Ignacio Rodriguez, Samson Goddy and Laura Vargas as the new elections and membership committee, with the purpose of debugging current membership list and running the 2016's elections for the 3 seats at the Board available for the 2016-2018 period and to appoint Dave Crossland as an impartial election oversight party.<br>(4 votes for, 1 abstain, 2 members absent)<br />
<br />
;AGREED MOTION 2017-02 Walter Bender, posting motion seconded by Tony Anderson: Sugar is a learning platform based on the constructionist educational principles of Jean Piaget, Seymour Papert, Cynthia Solomon, and Alan Kay. Sugar Labs is responsible to develop, distribute, and support Sugar with the help of a global volunteer community of contributors. Sugar Labs provides Sugar in two forms: Sugar for personal computers and XOs and Sugarizer (Sugar Mobile) for mobile devices and the Web.<br>(5 votes for, 2 members absent)<br />
<br />
;AGREED MOTION 2017-01 Tony Anderson, posting motion seconded by Walter Bender: that the Board approve the expenses associated with the Paraguay TA day and the exception to the advance purchase policy.<br>(4 votes for, 1 abstain, 2 members absent)<br />
<br />
== 2016-10-07 ==<br />
<br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-10-07 log]<br />
<br />
;AGREED MOTION 2016-44 Walter Bender, posting motion seconded by Tony Anderson (SLOB): To dedicate the upcoming Sugar release to Marvin Minsky and Seymour Papert in honor of their numerous contributions to technology and learning.<br>(5 votes for, 2 members absent)<br />
<br />
== 2016-09-02 ==<br />
<br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-09-02T19:03:42 log]<br />
<br />
;AGREED MOTION 2016-43 Walter Bender, posting motion seconded by Tony Anderson (SLOB): Approval of funding for Turtle Art Days in Paraguay, Uruguay, and Nigeria in October/November; the PY budget is ~$1K; UY budget ~$2K; NG budget ~$5K; these events would come from the tripadvisor funds.<br>(5 votes for, 2 members absent)<br />
<br />
== 2016-07-01 ==<br />
<br />
[[Oversight_Board/Meeting_Minutes-2016-07-01|Minutes]], <br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-07-01T19:00:23 IRC log].<br />
<br />
;AGREED MOTION 2016-42B (formerly 2016-42) Walter Bender, posting motion initially drafted by Caryl Bigenho (member) and Tony Anderson (SLOB) and Adam Holt (SLOB): The Sugar Labs Oversight Board shall appoint a Finance Manager by majority vote from among the members of Sugar Labs Oversight Board. The Finance Manager serves at the will of the board. The Finance Manager may be paid a stipend at the discretion of the board. Duties of the Finance Manager will be to: 1. Serve as Sugar Lab's central coordinator on all financial matters. 2. Report quarterly at a scheduled Oversight Board meeting the following: Confirmation of the accuracy of the previous quarter's report according to the Software Freedom Conservancy; Balance at the beginning of the quarter preceding the meeting; Expenses during the quarter; Income received during the quarter; Balance at the end of the quarter. 3. The Finance Manager has discretion to approve petty cash amounts up to $200 to pay for miscellaneous expenditures critical for the functioning of Sugar Labs. If approved and everything is in order, these will often be paid within (about) 30 days of when they are submitted to the Software Freedom Conservancy, who control Sugar Labs' banking. If not approved, the applicant is free to ask for a vote at a future Oversight Board meeting. 4. All motions for funding of larger projects will be presented first to the Finance Manager who will review them to be sure the funds are being used in a way that appears fiscally sound. If everything is in order, the Finance Manager will place the motion on the agenda for consideration at the next possible Oversight Board meeting, and circulate on the IAEP mailing list for public discussion. 5. At the meeting, after a finance motion has been moved and seconded, discussion should be confined to the motion.<br>(5 votes for, 2 against)<br>(Full motion with sample financial report available at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg17107.html) <br />
<br />
<br />
;AGREED MOTION 2016-42 Walter Bender, posting motion initially drafted by Sameer and Tony: While suggestions for motions can come from anyone in the community, motions should be made by Sugar Labs oversight board members.<br> (7 votes for).<br />
<br />
<br />
;AGREED MOTION 2016-41 Walter Bender, posting motion initially drafted by Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval.<br>(4 votes for, 1 against, 2 abstain)<br>(note that the "low income" solicitation did not reach consensus during the meeting and Dave Crossland offered to work with the board to ensure the solicitation will meet their approval before it is sent to members.)<br />
<br />
== 2016-06-30 ==<br />
;<s>MEMBER MOTION 2016-40</s> Dave Crossland: To append to existing bylaw for Finance Manager new procedures.<br />
;<s>MEMBER MOTION 2016-39</s> Dave Crossland: To replace existing bylaw for Finance Manager.<br />
<br />
== 2016-06-14 ==<br />
;<s>MEMBER MOTION 2016-38</s> Dave Crossland: to consider email votes on motions only valid if they are sent to both the SLOBs and IAEP mailing lists. (not seconded)<br />
<br />
== 2016-06-11 ==<br />
;<s>MEMBER MOTION 2016-37</s> Dave Crossland, posting motion initially drafted by Tony Anderson: to undertake a fund raising drive. Arrangements will be made to enable on-line contributions by PayPal, debit or credit card or other means. Once the means to make contributions is in place, the Financial Manager will initiate and lead the drive. The Sugar Labs web site will show progress in donations toward the goal. (not seconded)<br />
<br />
== 2016-06-10 ==<br />
;<s>MEMBER MOTION 2016-36</s> Dave Crossland: to vote on each motion proposed by a member, dropping the current practice of requiring a seconding before voting. (not seconded)</s><br />
;<s>MEMBER MOTION 2016-35</s> Dave Crossland: to agree the following procedure for all future monthly SLOB meetings: the chair will confirm the meeting meets quorum; the chair will make any announcements submitted to them before the meeting; the chair will announce the first motion pending a vote on that day; each present SLOB member will announce their vote; the chair will announce the outcome of the motion; the chair will announce the next motion, until all motions are voted on; the chair will invite everyone attending to an open discussion of any topic until the meeting ends at the time scheduled. (not seconded)<br />
;AGREED MOTION 2016-34 Walter Bender, posting motion initially drafted by Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (5 votes for, 1 against, 1 abstain, see http://www.mail-archive.com/iaep%40lists.sugarlabs.org/msg16711.html)<br />
;<s>MEMBER MOTION 2016-33</s> Laura Vargas: to update current SL vision statement ("About Sugar Labs(R): Sugar Labs(R) is a volunteer-driven member project of Software Freedom Conservancy, a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates volunteers around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs(R) is supported by donations and is seeking funding to accelerate development.") to the new proposed text: "Sugar Labs is a global community where you can learn how to design, develop and deploy high-quality Free/Libre Software that facilitates self-discovery learning experiences and collaboration among young children of all continents." (not seconded)<br />
<br />
== 2016-06-09 ==<br />
;<s>MEMBER MOTION 2016-32</s> Dave Crossland: The value of $Y in the Finance Manager Guidelines should be $200 (not seconded)<br />
<br />
== 2016-06-03 ==<br />
<br />
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2016-06-03T19:01:08 IRC log]<br />
;FAILED MOTION 2016-31 Walter Bender, posting motion initially drafted by Dave Crossland: To adopt the [https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&oldid=98911 Vision proposal 2016]. (not seconded)<br />
;<s>MEMBER MOTION 2016-30</s> Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To add to the bylaws a new section, “Sugar Labs Oversight Board Spending Guidelines”</s>] (dependent upon MOTION 2016-27)<br />
;<s>MEMBER MOTION 2016-29</s> Dave Crossland: [https://docs.google.com/document/d/1ssTPbBC23prkOLHUNpaPO56zpQQkD0IL4FA3FFmAUvw/edit#heading=h.meqor5elzkoa To append the following text to the existing bylaw for the Finance Manager office</s>] (dependent upon MOTION 2016-27)<br />
;FAILED MOTION 2016-28 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-27)<br />
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)<br />
<br />
== 2016-05-29 ==<br />
<br />
;<s>MEMBER MOTION 2016-26</s> Dave Crossland: To request donations from Sugar Labs Members, to be allocated to the General Fund through the SFC. The annual donation requested will be $12 USD from members who self-identify as low-income (such as students); $36, $120, or $600 USD from general members. (not seconded)<br />
<br />
;<s>MEMBER MOTION 2016-25</s> Dave Crossland: To request a membership donation from each currently active Sugar Labs Member to be allocated to the General Fund for the calendar year of 2016, and a public statement about how they use Sugar and why they are involved in Sugar Labs to post on the website; there is no penalty for not paying a membership or not providing a statement; by default members who donate will be kept private, and requested to opt-in to be recognised. The donation requested will be $12 USD from members who self-identify as low-income (such as students); $36 USD from general members; $120 from members who can opt-in to be placed prominently on the website; and $600 from members who can (privately if they wish) submit a release codename, subject to SLOB approval. (seconded at http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg16767.html but all SLOBs abstained)<br />
<br />
;<s>MEMBER MOTION 2016-24</s> Dave Crossland: Whereas it is the general policy of Sugar Labs to retain all GSoC mentoring stipends in the General Fund, if a mentor asks a GSoC Admin (for example in 2016, Walter or Lionel) to pay a stipend to a mentor, their share of the stipend amount will be disbursed without further motions to approve the spending. The share is calculated from the total awarded for the GSoC slot by Google, minus 10% (as all Sugar Labs income is donated to Software Freedom Conservancy for organisational services), minus 5% (retained for Sugar Labs General Funds), divided by the number of mentors for the project. For example, in a year with 6 slots and 10 mentors at $500, the total revenue is $3,000; 10% for Conservancy is $300 and 5% for Sugar Labs is $150, leaving a total of $2,550 or $255 per mentor. (not seconded)<br />
<br />
== 2016-05-25 ==<br />
;<s>MEMBER MOTION 2016-23</s> Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To define procedures for requesting, obtaining, and reporting use of SugarLabs funds] (dependent upon MOTION 2016-22)<br />
;<s>MEMBER MOTION 2016-22</s> Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded)<br />
<br />
== 2016-05-12 ==<br />
;AGREED MOTION 2016-21 Walter Bender: to reimburse Edgar Quispe for expenses incurred representing Sugar Labs at the Traducción e interpretación en las lenguas originarias del Perú meeting in Lima. The cost is $168.88. : (See http://lists.sugarlabs.org/archive/iaep/2016-May/018196.html)<br />
<br />
== 2016-05-11 ==<br />
;FAILED MOTION 2016-20 Walter Bender: to allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit. : (3 votes for, 1 vote against, and 3 abstains): Motion 2016-34 was agreed on the same subject<br />
<br />
== 2016-05-06 ==<br />
;AGREED MOTION 2016-19 Walter Bender, posting motion initially drafted by Dave Crossland: To pay for laboratoriosazucar.org domain registration renewal<br />
;FAILED MOTION 2016-27 Walter Bender, posting motion initially drafted by Caryl Bigenho: [https://docs.google.com/document/d/16jIFuZ9bX-Bv675BpA1KmcEcRcX4PRCOUEX0ICRUkOc/edit To replace existing bylaw for Finance Manager] (not seconded, further drafting requested)<br />
;AGREED MOTION 2016-14 Walter Bender, posting motion initially drafted by : To fund a program to initiate the translation of Sugar into Yoruba. The work would be led by Samson Goddy and reviewed by Chris Leonard, in his role as Translation Community Manager (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052462.html]).<br />
;AGREED MOTION 2016-13 Walter Bender, posting motion initially drafted by Dave Crossland: To update the Sugar License from GPLv2 to GPLv3 [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052552.html]<br />
;FAILED MOTION 2016-12 Walter Bender: To allow the mentors participating in Google Summer of Code to disperse the mentor stipend among themselves as they see fit (See [http://lists.sugarlabs.org/archive/sugar-devel/2016-May/052463.html]).<br />
;FAILED MOTION 2016-11 Lionel Laske: To adopt the wiki Vision proposal for 2016 (not seconded)<br />
<br />
== 2016-04-09 ==<br />
;AGREED MOTION 2016-10 Walter Bender: To offer Devin U. an honorarium ($500) to compensate him since he needed to take a week off from work to run two Turtle/Music Blocks workshops at the Constructionism Conference. The funds would be allocated from the Trip Advisor grant which are in support of promoting and advancing Turtle Blocks around the world. (Vote taken by email.)<br />
;AGREED MOTION 2016-09 Walter Bender: Walter, as PI of the Trip Advisor grant, will inform the SL oversight board of his plans for workshops that fall under the guise promotion of Turtle Blocks but otherwise has discretion in organizing and funding these events, within the budget constraints of grant and the travel guidelines of the SFC. (Vote taken by email.)<br />
<br />
== 2016-04-07 ==<br />
;<s>MEMBER MOTION 2016-08a</s> Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): All funds raised by any Sugar Labs community member in the name of Sugar Project's translations must be directed to the “Sugar Projects Translation's Fund”. (not seconded)<br />
;<s>MEMBER MOTION 2016-08a</s> Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): >The present SugarLabs Oversight board appoints the current Translation's Committee, with the full responsability of reviewing, upgrading, approving and overseeing Sugar Translation Projects and Proposals made by any interested party, with special attention to Native Languages communities. (not seconded)<br />
;<s>MEMBER MOTION 2016-08a</s> Laura Vargas ([http://lists.sugarlabs.org/archive/iaep/2016-April/017801.html reference]): Requests for funds will be presented to the Translation's Committee, in writing, with copy to the IAEP mailing list and the Localization mailing list, at least 72 hours in advance of the monthly scheduled "Translation Committee Meeting". Committe members shall vote during the meeting for approval by simple majority. All interested parties, must also send the proposal to the IAEP mailing list and the Localization mailing list, in advance. (not seconded)<br />
<br />
== 2016-04-06 ==<br />
;AGREED MOTION 2016-08: To approve the position of Translation-Community Manager as described at [[Translation-Community Manager]].<br />
;AGREED MOTION 2016-07: That Chris Leonard be named to this position effective immediately.<br />
;AGREED MOTION 2016-06: That the Translation-Community Manager be paid a stipend of $1000/month.<br />
<br />
== 2016-04-01 ==<br />
;AGREED MOTION 2016-05: In keeping with the board 2010's decision on this matter from a different era, it was suggest that if a Board Member (1) fails to vote and attend pre-scheduled Board meetings for more than 12 weeks, (2) resigns or (3) dies, then the Board is empowered and encouraged to appoint a replacement for this seat. Finally, just a clarification that the Replacement Board Member would be required to defend their seat during the very next election.<br />
<br />
== 2016-03-04 ==<br />
;AGREED MOTION 2016-04: Based on [[Translation Proposal]], Tony (and other SLOB members) should write up a job description with goals and reporting structure for a coordinator position to be submitted to the SFC.<br />
;AGREED MOTION 2016-03: Restrict email voting to 1 week going forward, to remove confusion from the current voting process, keeping focus. Board members' email votes would be required to arrive within One Week Maximum (168.0 hours) of the original motion. (Any motion that fails to pass within this 1-week sunset period, can of course be attempted again in future, e.g. if long-term overseas/off-grid/medical absences require another later vote on the same topic).<br />
<br />
== 2016-02-12 ==<br />
;AGREED MOTION 2016-02: Moving regular SLOB meeting dates to the first Friday of the month at 16UTC<br />
;AGREED MOTION 2016-01: Apply for GSoC 2016 (Lionel and Walter as co-admins)<br />
<br />
== 2015-12-17 ==<br />
;FAILED MOTION 2015-07(3 In Favor, 4 Abstentions): to pay Devin Ulibarri $500 for help organize and run the Turtle workshop in Bangkok<br />
(See renewed motion passed on 2016-04-09.)<br />
<br />
== 2015-10-12 ==<br />
;AGREED MOTION 2015-06: Apply to GCI<br />
<br />
== 2015-09-14 ==<br />
;AGREED MOTION 2015-05: funding to file an affidavits required to maintain the registration of Sugar Labs' trademarks with the USPTO.<br />
;ACTION: Walter to recruit mentors for GCI<br />
<br />
== 2015-07-06 ==<br />
;ACTION: acknowledged the numerous contributions to Sugar from the late Marco Presenti Gritti.<br />
<br />
== 2015-05-06 ==<br />
;AGREED MOTION 2015-04: via email to add Samson Goody to the Membership Committee (DONE)<br />
<br />
== 2015-05-04 ==<br />
;AGREED MOTION 2015-03: to share survey results with community (DONE)<br />
;ACTION: Gonzalo to post results (DONE)<br />
;ACTION: Gonzalo to write to each of the respondents<br />
;AGREED MOTION 2015-02: that Claudia and Walter go to NI to discuss Sugar/OLPC future with the Zamoras<br />
;ACTION: Walter to make a first pass at culling the decisions from past meetings into one page (this page)<br />
<br />
== 2015-04-06 ==<br />
;AGREED MOTION 2015-01: appoint Icarito and Caryl to the election committee and to try to recruit a youth member to the committee.<br />
<br />
== 2015-01-14 ==<br />
;ACTION: organize a summit to discuss the future of Sugar<br />
;ACTION: do a survey to solicit feedback from deployments<br />
0<br />
== 2014-10-07 ==<br />
;ACTION: Recruit mentors for GCI<br />
;ACTION: Recruit candidates for oversight board<br />
<br />
== 2014-07-08 ==<br />
;AGREED MOTION 2014-02: on a .UY venue for a summit in September 2014. Jose Miguel and Daniel will get back to us about specifics.<br />
<br />
== 2014-03-03 ==<br />
;ACTION: everyone solicit students for GSoC<br />
<br />
== 2014-02-05 ==<br />
;AGREED MOTION 2014-01: to Gonzalo and Manuq's proposal for Background Image Contest<br />
<br />
== 2013-11-04 ==<br />
;AGREED MOTION 2013-06: Luke to run election for oversight board again<br />
;AGREED MOTION 2013-05: to give cjl discretion over the i18n funds in the Trip Advisor grant<br />
<br />
== 2013-10-18 ==<br />
;AGREED MOTION 2013-04: we would apply again to Google Code In<br />
<br />
== 2013-03-21 ==<br />
;AGREED MOTION 2013-03: the next release will be Sugar 1.0<br />
<br />
== 2013-02-25 ==<br />
;AGREED MOTION 2013-02: to establish a category for Sugar Labs advisors/educators/friends<br />
;ACTION: Claudia and Walter will meet to start planning Turtle Art Day<br />
;AGREED MOTION 2013-01: to apply for Google Summer of Code 2013<br />
<br />
== 2013-01-07 ==<br />
;ACTION: ClaudiaU agreed to share ''Making Learning Visible'' with SLOB members (and Tonyf and JT4Sugar)<br />
<br />
== 2012-05-30 ==<br />
;AGREED MOTION 2012-05: to modify the Trademark and Local Labs pages in the wiki (See [[/Oversight_Board/Meeting_Minutes-2012-05-30#1._Updates_to_the_TM_policy_.28Trademark.29|TM Policy]] and [[Oversight_Board/Meeting_Minutes-2012-05-30#2._Updates_to_the_Local_Lab_wiki_.28Local_Labs.29|Local Labs Policy]])<br />
<br />
== 2012-05-03 ==<br />
;AGREED MOTION 2012-04: We approved a budget of up to US $5000 for two servers.<br />
;AGREED MOTION 2012-03: Sugar Labs joins the SFC GPL enforcement program<br />
;ACTION MOTION 2012-02: Walter to bring code-of-conduct discussion to the community.<br />
;ACTION MOTION 2012-01: SLOB members to get signed agreements to the SFC regarding new SFC by-laws.<br />
<br />
== 2011-12-02 ==<br />
;AGREED MOTION 2011-09: The Sugar Labs Oversight Board thanked Bernie Innocenti and Mel Chua for their dedicated service to the community in their role as members of the oversight board.<br />
<br />
== 2011-09-16 ==<br />
;AGREED MOTION 2011-08: to keep the GSoC 2010 mentor funds as our general funds.<br />
<br />
== 2011-08-05 ==<br />
;AGREED MOTION 2011-07: to award Sugar participation certificates (See [[Oversight_Board/2011/Meeting_Minutes-2011-08-05#Certificate_program|Certificate Program]]).<br />
;AGREED MOTION 2011-06: to give North Dakota State University authority to establish a local Sugar Lab.<br />
<br />
== 2011-06-09 ==<br />
;AGREED MOTION 2011-05: to endorse Free Software as defined here: http://www.gnu.org/philosophy/free-sw.html<br />
<br />
== 2011-05-08 ==<br />
;AGREED MOTION 2011-04: Bernie (head of infrastructure team) is authorized to approve spending tickets filed on the bug tracker up to $200.<br />
;AGREED MOTION 2011-03: to update the governance page.<br />
<br />
== 2011-02-10 ==<br />
;AGREED MOTION 2011-02: SL endorses the idea that community members have kids: means more Sugar hackers in the future !!<br />
;AGREED MOTION 2011-01: Local labs can issue Sugar certificates (and charge for this service whatever they want) but only if: (1) they maintain a page on our wiki explaining what content they use for training, where to download it, and what pricing they use; and (2) all the content they use for training is licensed under one of the licenses recommend by http://opensource.org/docs/osd and/or http://fedoraproject.org/wiki/[…]ing#Good_Licenses.<br />
<br />
== 2010-12-13 ==<br />
;AGREED MOTION 2010-10: [[Oversight_Board/Project_Motion]]<br />
;AGREED MOTION 2010-09: SL would like to acknowledge and celebrate the marriage of acaire11 and icarito : the first Sugar marriage!!!<br />
<br />
== 2010-12-01 ==<br />
;AGREED MOTION 2010-08: Each active team and local lab should propose a few delegates from that team to SLOBs. We will invite the delegates to SLOBs meetings, and rotate scheduled times during SLOBs meetings to hear reports from their team or lab.<br />
;AGREED MOTION 2010-07: The default time/day of the week for SLOBs meetings will be Thursdays at 15:00 EST (20:00 UTC)<br />
;AGREED MOTION 2010-06: If a SLOB member misses one month of regular weekly meetings in a row, twice during one calendar year, SLOBs may find a replacement for their seat.<br />
<br />
== 2010-09-28 ==<br />
;AGREED MOTION 2010-05: We, the SLOB, acknowledge and praise the efforts of the release team for bringing us 0.90!!<br />
<br />
== 2010-05-07 ==<br />
;AGREED MOTION 2010-04: to a [[Trademark]] policy.<br />
<br />
== 2010-03-05 ==<br />
;AGREED MOTION 2010-03: (1) Bundles with non-Sugar dependencies be clearly marked in ASLO; (2) We work towards a mechanism for supporting access to non-Sugar dependencies--a specific endorsement of being open; and (3) We do not restrict ASLO while we progress towards #2.<br />
<br />
== 2010-02-26 ==<br />
;AGREED MOTION 2010-02: to authorize Bernie to spec out a machine around $2000, send details to systems@ for review, decide exactly where it will be hosted, then buy it.<br />
<br />
== 2010-01-22 ==<br />
;AGREED MOTION 2010-01: to authorize Luke Faraone to ship some used hardware from the Wikipedia Foundation (12 servers) to various hosting sites. The cost should not exceed US$300.<br />
<br />
== 2009-12-18 ==<br />
;AGREED MOTION 2009-18: Sugar Labs encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure. SL Marketing may strategically decide to focus resources towards specific distributions in the interest of promoting Sugar more effectively.<br />
;AGREED MOTION 2009-17: Yes, "Sugar on a Stick" should be reserved by Sugar Labs for use by the SoaS-Fedora distribution so that Sugar can be marketed effectively, until such time when a trademark policy, agreement, and process is put in place: SoaS will be the first project to go through that process.<br />
<br />
== 2009-12-11 ==<br />
;AGREED MOTION 2009-16: to adopt http://opensource.org/docs/osd as a set of guidelines for what is permitted on ASLO, for both software and content, and http://fedoraproject.org/wiki/Licensing#Good_Licenses's opinions on specific licenses where applicable, and always asking the SFC for advice when a particular license is under question.<br />
;AGREED MOTION 2009-15: SL is and should be a GNU/Linux distributor.<br />
;AGREED MOTION 2009-14: SL wishes to spread the use of Sugar and consequently works with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.<br />
;AGREED MOTION 2009-13: SL should not be completely neutral about promoting distros, but it should only choose to more strongly promote a distro based on technical merit and maintainer activity, and should publish the criteria it uses for making that decision. Furthermore, SL should be neutral about providing infrastructure resources (hosting, etc) to distros."<br />
<br />
== 2009-12-04 ==<br />
;AGREED MOTION 2009-12: when a DP fails to meet a deadline, the decision passes to SLOBs.<br />
<br />
== 2009-11-20 ==<br />
;AGREED MOTION 2009-11: Close the slobs@ list to just SLOBs, move current slobs@ traffic to iaep@ with a [SLOBS] subject line tag where at all possible.<br />
;AGREED MOTION 2009-10: Give a two-week deadline to the Soas DP<br />
<br />
== 2009-09-25 ==<br />
;AGREED MOTION 2009-09: We appointed a decision panel (by a vote of 3 for, 0 against, 1 abstain, 3 absent) with the following mandate:<br />
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:<br />
:"Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"<br />
:"Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"<br />
:"Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"<br />
:Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"<br />
<br />
== 2008-09-05 ==<br />
;AGREED MOTION 2009-08: The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.<br />
<br />
== 2009-07-18 ==<br />
;AGREED MOTION 2009-07: There was consensus that we have made sufficient outreach to the community that the initial list is a fair representation of Sugar Labs; we look forward to having the Membership Committee take it from http://selectricity.org/<br />
;AGREED MOTION 2009-06: There was consensus that Walter would put together a strawman election process based upon the Selectricity tool. We are targeting an August election.<br />
;AGREED MOTION 2009-05: There was consensus that we begin with just Oversight and Members committees.<br />
;AGREED MOTION 2009-04: We agreed for the need to solicit more feedback in the wiki for the design direction being proposed by Luca.<br />
;AGREED MOTION 2009-03: We agreed that further discussions with the SFLA about the merits of trademark protection is needed.<br />
;AGREED MOTION 2009-02: We agreed on the desirability of Sugar Labs participation at conferences around the world, but hope to meet the need by utilizing locals to whatever extent possible. We also discussed the desirability to have a meeting of Sugar Labs developers a couple of times per year. We discussed the possibility of an on-line meeting that leverages resources above and beyond IRC.<br />
;AGREED MOTION 2009-01: on the necessity of Sugar Labs participation in the learning community, but don't yet have a good handle on the best and most efficient means of accomplishing this.</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Talk:Licensing&diff=66661Talk:Licensing2011-06-26T00:48:48Z<p>MartinDengler: add "me too"</p>
<hr />
<div>'''DRAFT of new Licensing text as per the discussion at the 9 June 2011 SLOBs meeting'''<br />
<br />
Sugar Labs adheres to the principles of Free Software. An [http://www.gnu.org/philosophy/free-sw.html overview of these principles] is provided by the Free Software Foundation (FSF). The Open Source Initiative (OSI) has a [http://opensource.org/docs/osd set of guidelines for Free and Open Source software] that characterize the intentions of our community.<br />
<br />
All software and content distributed by Sugar Labs, including activity bundles uploaded to http://activities.sugarlabs.org, must be released under a license that conforms to the principles and guidelines referred to above.<br />
<br />
You may use any license on the Fedora Project's [http://fedoraproject.org/wiki/Licensing#Good_Licenses list of Good Licenses] or the FSF's [http://www.gnu.org/licenses/license-list.html list of Free Software Licenses]. If you wish to use a license not on one of these two lists and believe that it fits our guidelines, please contact the [[Oversight Board]].<br />
<br />
----<br />
<br />
This policy was determined during a [[Oversight_Board/2009/Meeting_Minutes-2009-12-11#Non-FOSS_content|2009-12-11 board meeting]] and clarified at the [http://meeting.sugarlabs.org/sugar-meeting/2011-06-09#i_2671836 2011-06-09 board meeting].<br />
<br />
Please contact the [[Oversight Board]] if you have questions about our licensing policy.<br />
<br />
<br />
----<br />
<br />
+1 to the above text from me! [[User:Bernie|bernie]] 03:29, 15 June 2011 (EDT)<br />
<br />
+1 from Cjb, with the fix to one of the links that I just made. [[User:Cjb|Cjb]] 09:45, 15 June 2011 (EDT)<br />
<br />
----<br />
''The language seems sloppy to me. Fedora lists both good and bad licenses on the linked page, so saying "You may use any license" from there is not quite what is meant. Secondly, the FSF link goes only to the GNU licenses, perhaps their [http://www.gnu.org/licenses/license-list.html list of Free Software Licenses] is more appropriate?'' [[User:Bert|Bert]] 09:15, 24 June 2011 (EDT)<br />
<br />
:Sorry. I realize I had the wrong link. Should be http://www.gnu.org/licenses/license-list.html which includes many non-GNU licenses. --[[User:Walter|Walter]] 09:21, 24 June 2011 (EDT)<br />
:The problem with the Fedora link was a typo. Should link directly to http://fedoraproject.org/wiki/Licensing#Good_Licenses now. --[[User:Walter|Walter]] 09:23, 24 June 2011 (EDT)<br />
:: Maybe just to be explicit, write "Good Licenses" instead of "acceptable licenses"? [[User:Bert|Bert]] 09:54, 24 June 2011 (EDT)<br />
::: Yes. I agree... consistency. --[[User:Walter|Walter]] 10:02, 24 June 2011 (EDT)<br />
''Another nit pick: I find the second link to the GNU.org website distracting and unnecessary. I'd replace ''"is found on the [http://gnu.org GNU.org website]"'' with ''"is provided by the FSF"''. The FSF is mentioned again later, so it's better to use the same name. [[User:Bert|Bert]] 10:04, 24 June 2011 (EDT)<br />
:Nitpicking is right... but I made the change :) --[[User:Walter|Walter]] 10:51, 24 June 2011 (EDT)<br />
:: That's better, though I'd remove that link altogether. It adds nothing to the official Sugar Labs Licensing page. My suggestion was "is provided by the FSF", with no embedded link at all. [[User:Bert|Bert]] 11:11, 24 June 2011 (EDT)<br />
:::Sure... less is more. But I decided to spell out our acronyms when first used (and OSD->OSI) :P --[[User:Walter|Walter]] 11:19, 24 June 2011 (EDT)<br />
---- <br />
<br />
+1, having Fedora list of good licences will simplify workflow on ASLO to make it automatic, ie, activities-testing.sugarlabs.org [[Activity_Library/Editors/Policy/Licensing|sees]] to the {{Code|licence}} tag in the {{Code|activitiy.info}} to accept/reject any new upload. [[User:Alsroot|alsroot]] 09:32, 24 June 2011 (EDT)<br />
<br />
+1 FWIW [[User:MartinDengler|MartinDengler]] 20:48, 25 June 2011 (EDT)</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Education_Team/Lesson_Plan_resources&diff=66182Education Team/Lesson Plan resources2011-06-03T02:22:28Z<p>MartinDengler: move related topics to the end because this page is quite useful on its own and not just as a stepping stone to the related topics pages</p>
<hr />
<div>== Lesson plan templates/formats ==<br />
<br />
* sugar [[Lesson plan template]]<br />
* A few different ones: http://www.internet4classrooms.com/links_grades_kindergarten_12/lesson_plans_templates.htm<br />
* others?<br />
<br />
== Lesson plans ==<br />
<br />
*http://www.nea.org/tools/LessonPlans.html<br />
*http://www.curriki.org/xwiki/bin/view/Main/Browse<br />
*http://www.halcyon.com/marcs/lessons.html<br />
*http://www.thegateway.org/<br />
*http://www.internet4classrooms.com/lesson.htm<br />
*http://learning.blogs.nytimes.com/category/lesson-plans/<br />
*http://www.mcrel.org/lesson-plans/<br />
*http://www.bbc.co.uk/schools/teachers/ ("Lesson Plans and Worksheets" section)<br />
**http://www.bbc.co.uk/schools/teachers/keystage_1/topics/maths_ks1.shtml (for example)<br />
*http://wiki.laptop.org/go/Category:Hackety_Lesson_Plan<br />
*http://www.awesomelibrary.org/Library/Materials_Search/Lesson_Plans/Science.html<br />
<br />
== Lesson plan ideas ==<br />
<br />
* New group just created at http://www.curriki.org/xwiki/bin/view/Group_SugaronaStick/. Looking for interested teachers to contribute lesson plans to grow this into a repository. If you need a lesson plan template [[Media:Sugar_Lesson_Plan_Template.dotx|this one]] may be used as is or is easily adapted.<br />
<br />
* [http://dir.yahoo.com/education/k_12/teaching/lesson_plans/ Yahoo Directory of Lesson Plans]<br />
<br />
* dmoz.org lesson plans:<br />
** http://www.dmoz.org/Arts/Education/Language_Arts/Lesson_Plans_and_Reproducibles/<br />
** http://www.dmoz.org/Reference/Education/K_through_12/Educators/Lesson_Plans/<br />
** meta: [http://search.dmoz.org/cgi-bin/search?search=lesson%20plans&utf8=1&locale=en_gb&morecat=1 dmoz.org Directory of Lesson Plans]<br />
<br />
*EtoysIllinois has a great collection of Etoys projects and resources for teachers for curriculum integration<br />
**http://www.squeakcmi.org/library.php<br />
**http://www.squeakcmi.org/resources.php<br />
<br />
*List of free teaching software (german) <br />
**http://wiki.skolelinux.de/LernSoftware maintained by the German team of skolelinux <br />
**http://www.skolelinux.de<br />
*Skolelinux has integrated using the KDE-Education project<br />
**http://edu.kde.org/<br />
*Teacher training project (german) <br />
**http://www.seminarix.org/files/start.html<br />
<br />
*Collection of free teaching software with tagged OS and screenshots, more than 80 pages in PDF<br />
**http://www.skolelinux.de/download/education_FOSS_catalog.pdf<br />
<br />
*How about some outreach to a group committed to produce curriculum materials for grades 4 to 12 using Python and E-toys for use in South Africa? They are funded by the Shuttleworth Foundation (Ubuntu money and major commitment to open everything—being phased out, unfortunately).<br />
**http://www.kusasa.org<br />
<br />
*Try to seek aligned interests with any of the other open and collaborative efforts like Free High School Science Texts, who's goal is to develop a set of complete textbooks for Maths, Physics and Chemistry for grades 10-12 will be completed by early 2008, all under GDFL licensing.<br />
**http://www.fhsst.org/<br />
<br />
<br />
*Interesting on-line high school physics course<br />
**http://online.cctt.org/<br />
<br />
*http://www.free.ed.gov/<br />
<br />
*http://computerlearning.org/<br />
<br />
*Teachers pay Teachers - an open marketplace for educators (some free content, some paid)<br />
**http://www.teacherspayteachers.com/Home<br />
<br />
*Anytime Anywhere Learning Foundation (AALF)<br />
**http://www.aalf.org/<br />
:AALF is a 501(c) 6 not for profit association whose mission is to serve as an advocacy vehicle for anytime, anywhere learning. <br />
<br />
*http://www.nea.org/tools/SubmitYourLesson.html<br />
<br />
Etoys shares features with other drag and drop programming environments such as Game Maker and Click & Play. The lesson plans, samples and pedagogies developed in classrooms can be easily adapted to Etoys<br />
* http://www.mindtools.tased.edu.au/default.htm<br />
* http://www.users.on.net/~billkerr/g/int.htm<br />
* http://rupert.id.au/schoolgamemaker/<br />
<br />
"ReadWriteThink is a partnership between NCTE, the International Reading Association (IRA), and the MarcoPolo Education Foundation, established in April of 2002."<br />
* http://www.ncte.org/profdev/online/rwt BROKEN LINK<br />
<br />
MERLOT - Multimedia Educational Resources for Learning and Online Teaching <br />
*http://www.merlot.org/merlot/index.htm<br />
<br />
----<br />
**Some papers by Alan Kay<br />
<br />
* http://www.vpri.org/pdf/OLPCCountries_RN-2007-006-a.pdf<br />
* http://www.vpri.org/pdf/etoys_n_authoring.pdf<br />
* http://www.vpri.org/pdf/etoys_n_learning.pdf<br />
----<br />
<br />
*Tapping Epistemological Resources for Learning Physics<br />
** http://www.informaworld.com/smpp/content~content=a785041701~db=all<br />
<br />
*Naive Physics Reasoning: A Commitment to Substance-Based Conceptions<br />
** http://www.informaworld.com/smpp/content~content=a783760369~db=all<br />
<br />
*On the Nature of Naïve Physics<br />
** http://www.springerlink.com/content/kl44571021758m33/<br />
<br />
*Open source 2D physics engine Box2D<br />
** http://box2d.org<br />
and the Physics activity (and the Elements/pybox2d development being done in its branch)<br />
** http://wiki.laptop.org/go/Physics_%28activity%29<br />
** http://dev.laptop.org/git?p=activities/physics<br />
<br />
== Related topics ==<br />
* [[Replacing Textbooks]]<br />
* [[Open Education Resources]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Taxonomy&diff=66130Taxonomy2011-06-01T03:10:08Z<p>MartinDengler: reorder layer sections to match diagram</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<br />
<br />
== The SUGAR stack: ==<br />
[[Image:Sugar Taxonomy.png|400px]]<br />
<!-- The original file is called: Sugar Taxonomy.svg --><br />
*''Note: See discussion for details about the OS/Ribose stacking''<br />
<br />
*Current implementations of Sugar elements can be found at [[Supported systems]]<br />
<br />
==Stack Components==<br />
<br />
===Starch(es): A complete disk image for Sugar===<br />
<br />
''(starch is composed of multiple sugars bonded together)''<br />
<br />
Description: We often distribute complete disk images for Sugar, ready to<br />
boot. These images are composed of multiple elements of the above stack.<br />
<br />
Each image series should be named separately, to minimize confusion. For cutesy codenames, we could have a development build ("glycogen", a starch used to produce Glucose) and a stable build ("cellulose", an extremely stable starch).<br />
<br />
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.<br />
<br />
<br />
===Honey: activities developed by 'in the wild' vendors===<br />
<br />
''a sweet fluid made by bees, mostly Fructose''<br />
<br />
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].<br />
~ For example, Skype, printer capability, IM software <br />
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)<br />
<br />
<br />
===Sucrose: The interface, plus a set of demonstration activities===<br />
<br />
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''<br />
<br />
Description: Sucrose consists of both Glucose and Fructose. It therefore<br />
represents a complete example Sugar environment, ready to be installed<br />
through a package manager. The purpose of Sucrose is so that prospective<br />
deployers can install the "sugar-sucrose" package, and immediately say<br />
"Wow! Look at all the cool capabilities that this system has!".<br />
<br />
<br />
===Glucose: The base Sugar environment===<br />
<br />
''(the fundamental, simple sugar used by all life forms)''<br />
<br />
Description: Glucose is the minimal system that must be added to a<br />
standard GNU/Linux distribution in order to enable Activities to run. This<br />
includes all the python code and graphics files that implement the shell,<br />
as well as the Journal. Glucose's dependencies may include xorg-server,<br />
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br />
marked optional by distributions. Glucose does not include any Activities<br />
except those like the Journal that are non-optional.<br />
<br />
===Fructose: The set of demonstration activities===<br />
<br />
''(the main sugar in fruit, which is how we're supposed to get our sugar)''<br />
<br />
Description: The Sugar developers will need some example set of<br />
activities with which to demonstrate Sugar. This set is Fructose. The<br />
packages in Fructose should be selected to make the resulting environment<br />
as impressive as possible for a potential client or user. Packages should<br />
therefore be stable, polished, and exercise the widest possible range of<br />
features. Fructose may also serve as an example for people constructing<br />
their own Activity sets.<br />
<br />
===Ribose: The operating system components developed for Sugar===<br />
<br />
''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''<br />
<br />
Description: Ribose is the set of hardware-centric software components<br />
that have been developed throughout this project. It includes the XO<br />
kernels, OHM, any init-script customizations, etc. Ribose should be<br />
construed as including all components necessary to boot the system, enough<br />
to install Glucose if it has not yet been installed.<br />
<br />
== Related concepts ==<br />
<br />
===Sweet: The abstract design of the experience===<br />
<br />
''(the taste of sugar)''<br />
<br />
Description: "Sweet" is the abstract design of the interface's appearance<br />
and behavior, independent of any code actually implementing this design, and by extension&mdash;the learner experience.<br />
The mockups at [[Design Team/Designs]] represent this<br />
component's second major release, or perhaps 2.0-alpha.<br />
<br />
===Galactose: a future Sugar base designed for alternate computing forms===<br />
<br />
''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''<br />
<br />
Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].<br />
<br />
: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]<br />
<br />
==Humour / One-liners==<br />
<br />
* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].<br />
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub><br />
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub><br />
* ''Caramel: a "feature freeze" on Sucrose''<br />
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub><br />
* ''Molasses: a beta, unfinished release of Sugar''<br />
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub><br />
* ''How sweet it is!'' <sub>Jackie Gleason</sub><br />
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub><br />
<br />
== Glossary ==<br />
<br />
See [[Glossary]].</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Taxonomy&diff=66129Taxonomy2011-06-01T03:07:45Z<p>MartinDengler: remove commented-out ascii art (it's in the history)</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<br />
<br />
== The SUGAR stack: ==<br />
[[Image:Sugar Taxonomy.png|400px]]<br />
<!-- The original file is called: Sugar Taxonomy.svg --><br />
*''Note: See discussion for details about the OS/Ribose stacking''<br />
<br />
*Current implementations of Sugar elements can be found at [[Supported systems]]<br />
<br />
==Stack Components==<br />
<br />
===Sweet: The abstract design of the experience===<br />
<br />
''(the taste of sugar)''<br />
<br />
Description: "Sweet" is the abstract design of the interface's appearance<br />
and behavior, independent of any code actually implementing this design, and by extension&mdash;the learner experience.<br />
The mockups at [[Design Team/Designs]] represent this<br />
component's second major release, or perhaps 2.0-alpha.<br />
<br />
===Glucose: The base Sugar environment===<br />
<br />
''(the fundamental, simple sugar used by all life forms)''<br />
<br />
Description: Glucose is the minimal system that must be added to a<br />
standard GNU/Linux distribution in order to enable Activities to run. This<br />
includes all the python code and graphics files that implement the shell,<br />
as well as the Journal. Glucose's dependencies may include xorg-server,<br />
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br />
marked optional by distributions. Glucose does not include any Activities<br />
except those like the Journal that are non-optional.<br />
<br />
===Fructose: The set of demonstration activities===<br />
<br />
''(the main sugar in fruit, which is how we're supposed to get our sugar)''<br />
<br />
Description: The Sugar developers will need some example set of<br />
activities with which to demonstrate Sugar. This set is Fructose. The<br />
packages in Fructose should be selected to make the resulting environment<br />
as impressive as possible for a potential client or user. Packages should<br />
therefore be stable, polished, and exercise the widest possible range of<br />
features. Fructose may also serve as an example for people constructing<br />
their own Activity sets.<br />
<br />
===Sucrose: The interface, plus a set of demonstration activities===<br />
<br />
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''<br />
<br />
Description: Sucrose consists of both Glucose and Fructose. It therefore<br />
represents a complete example Sugar environment, ready to be installed<br />
through a package manager. The purpose of Sucrose is so that prospective<br />
deployers can install the "sugar-sucrose" package, and immediately say<br />
"Wow! Look at all the cool capabilities that this system has!".<br />
<br />
===Ribose: The operating system components developed for Sugar===<br />
<br />
''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''<br />
<br />
Description: Ribose is the set of hardware-centric software components<br />
that have been developed throughout this project. It includes the XO<br />
kernels, OHM, any init-script customizations, etc. Ribose should be<br />
construed as including all components necessary to boot the system, enough<br />
to install Glucose if it has not yet been installed.<br />
<br />
===Starch(es): A complete disk image for Sugar===<br />
<br />
''(starch is composed of multiple sugars bonded together)''<br />
<br />
Description: We often distribute complete disk images for Sugar, ready to<br />
boot. These images are composed of multiple elements of the above stack.<br />
<br />
Each image series should be named separately, to minimize confusion. For cutesy codenames, we could have a development build ("glycogen", a starch used to produce Glucose) and a stable build ("cellulose", an extremely stable starch).<br />
<br />
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.<br />
<br />
===Honey: activities developed by 'in the wild' vendors===<br />
<br />
''a sweet fluid made by bees, mostly Fructose''<br />
<br />
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].<br />
~ For example, Skype, printer capability, IM software <br />
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)<br />
<br />
==Future components==<br />
<br />
===Galactose: a future Sugar base designed for alternate computing forms===<br />
<br />
''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''<br />
<br />
Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].<br />
<br />
: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]<br />
<br />
==Humour / One-liners==<br />
<br />
* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].<br />
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub><br />
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub><br />
* ''Caramel: a "feature freeze" on Sucrose''<br />
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub><br />
* ''Molasses: a beta, unfinished release of Sugar''<br />
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub><br />
* ''How sweet it is!'' <sub>Jackie Gleason</sub><br />
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub><br />
<br />
== Glossary ==<br />
<br />
See [[Glossary]].</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Taxonomy&diff=66128Taxonomy2011-06-01T03:00:35Z<p>MartinDengler: move diagram to the top - an picture is worth a thousand words, etc.; reorganize sections to match organization of diagram</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<br />
<br />
== The SUGAR stack: ==<br />
<!-- Before editing this ASCII block diagram, please consider creating a raster or vector-based version. That would be delicious. Thanks! -jcarroll <br />
<br />
+---------------------------------------------------------------+<br />
| SWEET: The abstract design of the experience |<br />
| |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| STARCH: A complete disk image for Sugar |<br />
| |<br />
| +---------------------------------------------------------+ |<br />
| | SUCROSE: The environment, plus a set | |<br />
| | of demonstration activities | |<br />
| | | |<br />
| | +------------------------------+ +--------------------+ | |<br />
| | | FRUCTOSE: A set of demo | | | | |<br />
| | | activities | | | | |<br />
| | | | | | | |<br />
| | +------------------------------+ | | | |<br />
| | +--------------------------------+ | | |<br />
| | | GLUCOSE: The base Sugar environment | | |<br />
| | | | | |<br />
| | +-----------------------------------------------------+ | |<br />
| +---------------------------------------------------------+ |<br />
| |<br />
| +--------------------------------------------------------+ |<br />
| | OPERATING SYSTEM +-----------------+ | |<br />
| | | RIBOSE | | |<br />
| | | | | |<br />
| | +-----------------+ | |<br />
| +--------------------------------------------------------+ |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| HARDWARE |<br />
| |<br />
+---------------------------------------------------------------+ --><br />
[[Image:Sugar Taxonomy.png|400px]]<br />
<br />
<!-- The original file is called: Sugar Taxonomy.svg --><br />
*''Note: See discussion for details about the OS/Ribose stacking''<br />
<br />
*Current implementations of Sugar elements can be found at [[Supported systems]]<br />
<br />
==Stack Components==<br />
<br />
===Sweet: The abstract design of the experience===<br />
<br />
''(the taste of sugar)''<br />
<br />
Description: "Sweet" is the abstract design of the interface's appearance<br />
and behavior, independent of any code actually implementing this design, and by extension&mdash;the learner experience.<br />
The mockups at [[Design Team/Designs]] represent this<br />
component's second major release, or perhaps 2.0-alpha.<br />
<br />
===Glucose: The base Sugar environment===<br />
<br />
''(the fundamental, simple sugar used by all life forms)''<br />
<br />
Description: Glucose is the minimal system that must be added to a<br />
standard GNU/Linux distribution in order to enable Activities to run. This<br />
includes all the python code and graphics files that implement the shell,<br />
as well as the Journal. Glucose's dependencies may include xorg-server,<br />
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br />
marked optional by distributions. Glucose does not include any Activities<br />
except those like the Journal that are non-optional.<br />
<br />
===Fructose: The set of demonstration activities===<br />
<br />
''(the main sugar in fruit, which is how we're supposed to get our sugar)''<br />
<br />
Description: The Sugar developers will need some example set of<br />
activities with which to demonstrate Sugar. This set is Fructose. The<br />
packages in Fructose should be selected to make the resulting environment<br />
as impressive as possible for a potential client or user. Packages should<br />
therefore be stable, polished, and exercise the widest possible range of<br />
features. Fructose may also serve as an example for people constructing<br />
their own Activity sets.<br />
<br />
===Sucrose: The interface, plus a set of demonstration activities===<br />
<br />
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''<br />
<br />
Description: Sucrose consists of both Glucose and Fructose. It therefore<br />
represents a complete example Sugar environment, ready to be installed<br />
through a package manager. The purpose of Sucrose is so that prospective<br />
deployers can install the "sugar-sucrose" package, and immediately say<br />
"Wow! Look at all the cool capabilities that this system has!".<br />
<br />
===Ribose: The operating system components developed for Sugar===<br />
<br />
''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''<br />
<br />
Description: Ribose is the set of hardware-centric software components<br />
that have been developed throughout this project. It includes the XO<br />
kernels, OHM, any init-script customizations, etc. Ribose should be<br />
construed as including all components necessary to boot the system, enough<br />
to install Glucose if it has not yet been installed.<br />
<br />
===Starch(es): A complete disk image for Sugar===<br />
<br />
''(starch is composed of multiple sugars bonded together)''<br />
<br />
Description: We often distribute complete disk images for Sugar, ready to<br />
boot. These images are composed of multiple elements of the above stack.<br />
<br />
Each image series should be named separately, to minimize confusion. For cutesy codenames, we could have a development build ("glycogen", a starch used to produce Glucose) and a stable build ("cellulose", an extremely stable starch).<br />
<br />
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.<br />
<br />
===Honey: activities developed by 'in the wild' vendors===<br />
<br />
''a sweet fluid made by bees, mostly Fructose''<br />
<br />
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].<br />
~ For example, Skype, printer capability, IM software <br />
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)<br />
<br />
==Future components==<br />
<br />
===Galactose: a future Sugar base designed for alternate computing forms===<br />
<br />
''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''<br />
<br />
Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].<br />
<br />
: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]<br />
<br />
==Humour / One-liners==<br />
<br />
* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].<br />
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub><br />
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub><br />
* ''Caramel: a "feature freeze" on Sucrose''<br />
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub><br />
* ''Molasses: a beta, unfinished release of Sugar''<br />
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub><br />
* ''How sweet it is!'' <sub>Jackie Gleason</sub><br />
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub><br />
<br />
== Glossary ==<br />
<br />
See [[Glossary]].</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Taxonomy&diff=66127Taxonomy2011-06-01T02:51:51Z<p>MartinDengler: formatting fix to Starch section</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<br />
==Sweet: The abstract design of the experience==<br />
<br />
''(the taste of sugar)''<br />
<br />
Description: "Sweet" is the abstract design of the interface's appearance<br />
and behavior, independent of any code actually implementing this design, and by extension&mdash;the learner experience.<br />
The mockups at [[Design Team/Designs]] represent this<br />
component's second major release, or perhaps 2.0-alpha.<br />
<br />
==Glucose: The base Sugar environment==<br />
<br />
''(the fundamental, simple sugar used by all life forms)''<br />
<br />
Description: Glucose is the minimal system that must be added to a<br />
standard GNU/Linux distribution in order to enable Activities to run. This<br />
includes all the python code and graphics files that implement the shell,<br />
as well as the Journal. Glucose's dependencies may include xorg-server,<br />
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br />
marked optional by distributions. Glucose does not include any Activities<br />
except those like the Journal that are non-optional.<br />
<br />
==Fructose: The set of demonstration activities==<br />
<br />
''(the main sugar in fruit, which is how we're supposed to get our sugar)''<br />
<br />
Description: The Sugar developers will need some example set of<br />
activities with which to demonstrate Sugar. This set is Fructose. The<br />
packages in Fructose should be selected to make the resulting environment<br />
as impressive as possible for a potential client or user. Packages should<br />
therefore be stable, polished, and exercise the widest possible range of<br />
features. Fructose may also serve as an example for people constructing<br />
their own Activity sets.<br />
<br />
==Sucrose: The interface, plus a set of demonstration activities==<br />
<br />
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''<br />
<br />
Description: Sucrose consists of both Glucose and Fructose. It therefore<br />
represents a complete example Sugar environment, ready to be installed<br />
through a package manager. The purpose of Sucrose is so that prospective<br />
deployers can install the "sugar-sucrose" package, and immediately say<br />
"Wow! Look at all the cool capabilities that this system has!".<br />
<br />
==Ribose: The operating system components developed for Sugar==<br />
<br />
''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''<br />
<br />
Description: Ribose is the set of hardware-centric software components<br />
that have been developed throughout this project. It includes the XO<br />
kernels, OHM, any init-script customizations, etc. Ribose should be<br />
construed as including all components necessary to boot the system, enough<br />
to install Glucose if it has not yet been installed.<br />
<br />
==Galactose: a future Sugar base designed for alternate computing forms==<br />
<br />
''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''<br />
<br />
Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their [[wikipedia:J._C._R._Licklider#Global_computer_network |Galactic Neighborhood]].<br />
<br />
: See these threads: [http://www.mail-archive.com/fonc@vpri.org/msg01775.html Fundamentals of New Computing] & [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg10877.html It's An Education Project (For Sugar Everywhere, ...)]<br />
<br />
==Starch(es): A complete disk image for Sugar==<br />
<br />
''(starch is composed of multiple sugars bonded together)''<br />
<br />
Description: We often distribute complete disk images for Sugar, ready to<br />
boot. These images are composed of multiple elements of the above stack.<br />
<br />
Each image series should be named separately, to minimize confusion. For cutesy codenames, we could have a development build ("glycogen", a starch used to produce Glucose) and a stable build ("cellulose", an extremely stable starch).<br />
<br />
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.<br />
<br />
== The SUGAR stack: ==<br />
<!-- Before editing this ASCII block diagram, please consider creating a raster or vector-based version. That would be delicious. Thanks! -jcarroll <br />
<br />
+---------------------------------------------------------------+<br />
| SWEET: The abstract design of the experience |<br />
| |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| STARCH: A complete disk image for Sugar |<br />
| |<br />
| +---------------------------------------------------------+ |<br />
| | SUCROSE: The environment, plus a set | |<br />
| | of demonstration activities | |<br />
| | | |<br />
| | +------------------------------+ +--------------------+ | |<br />
| | | FRUCTOSE: A set of demo | | | | |<br />
| | | activities | | | | |<br />
| | | | | | | |<br />
| | +------------------------------+ | | | |<br />
| | +--------------------------------+ | | |<br />
| | | GLUCOSE: The base Sugar environment | | |<br />
| | | | | |<br />
| | +-----------------------------------------------------+ | |<br />
| +---------------------------------------------------------+ |<br />
| |<br />
| +--------------------------------------------------------+ |<br />
| | OPERATING SYSTEM +-----------------+ | |<br />
| | | RIBOSE | | |<br />
| | | | | |<br />
| | +-----------------+ | |<br />
| +--------------------------------------------------------+ |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| HARDWARE |<br />
| |<br />
+---------------------------------------------------------------+ --><br />
[[Image:Sugar Taxonomy.png|400px]]<br />
<br />
<!-- The original file is called: Sugar Taxonomy.svg --><br />
*''Note: See discussion for details about the OS/Ribose stacking''<br />
<br />
*Current implementations of Sugar elements can be found at [[Supported systems]]<br />
<br />
==Deepening the concept==<br />
<br />
===Honey: activities developed by 'in the wild' vendors===<br />
<br />
''a sweet fluid made by bees, mostly Fructose''<br />
<br />
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].<br />
~ For example, Skype, printer capability, IM software <br />
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)<br />
<br />
==One-liners==<br />
<br />
* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].<br />
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub><br />
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub><br />
* ''Caramel: a "feature freeze" on Sucrose''<br />
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub><br />
* ''Molasses: a beta, unfinished release of Sugar''<br />
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub><br />
* ''How sweet it is!'' <sub>Jackie Gleason</sub><br />
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub><br />
<br />
== Glossary ==<br />
<br />
See [[Glossary]].</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_Camp_Q2_2011&diff=63115Sugar Camp Q2 20112011-03-06T12:16:29Z<p>MartinDengler: add google maps links for the gographically challenged</p>
<hr />
<div>There are several proposals for a Sugar Camp for late Q1 or early Q2 of 2011.<br />
<br />
Candidate dates and venues include:<br />
<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Dates !! Venue !! Host/Co-event !! Would you be able to attend?<br />
|-<br />
|5-7 May||[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Montevideo,+Uruguay&aq=0&sll=22.302697,114.161998&sspn=0.010581,0.020964&ie=UTF8&hq=&hnear=Montevideo,+Uruguay&z=11 Montevideo]||[[Uruguay Summit 2011|CeibalJAM!]] and presummit [[Conozco Uruguay Tour|"Conozco Uruguay" Community Exploration Tour]]||<br />
|-<br />
|26-28 May||[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Montevideo,+Uruguay&aq=0&sll=22.302697,114.161998&sspn=0.010581,0.020964&ie=UTF8&hq=&hnear=Montevideo,+Uruguay&z=11 Montevideo]||[http://squeakland.org Squeakfest]/Universidad Católica del Uruguay||<br />
|-<br />
|15-24 April||[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Montevideo,+Uruguay&aq=0&sll=22.302697,114.161998&sspn=0.010581,0.020964&ie=UTF8&hq=&hnear=Montevideo,+Uruguay&z=11 Montevideo]||[[Vuelta_a_Uruguay]]||<br />
|-<br />
|24-25 March||[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Miami,+FL,+USA&aq=1&sll=-34.883333,-56.166667&sspn=0.300223,0.670853&ie=UTF8&hq=&hnear=Miami,+Miami-Dade,+Florida&z=12 Miami]||OLPC||<br />
|-<br />
|27 June-3 July ||[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Bogota,+Colombia&aq=1&sll=25.788969,-80.226439&sspn=0.164765,0.335426&ie=UTF8&hq=&hnear=Bogot%C3%A1,+Bogota,+Colombia&z=10 Bogota]||[http://www.campus-party.com.co/2011/el-evento.html Campus Party]||<br />
|}<br />
<br />
Please add your self to the table above so we can get a rough idea of which dates/venues work for the most people.<br />
<br />
We are looking into funding to help defray some of the travel costs. But what ever money we can raise will undoubtedly be limited.<br />
<br />
We are also debating topics for the Camp. While who can attend will impact our choice of topic, some ideas that have been discussed include:<br />
<br />
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"<br />
|-style="background:#787878; color: white;"<br />
! Topic !! Rationale<br />
|-<br />
|Python 'introspection' and GTK3 sprint||"right now we're stuck on deprecated code (pygtk) that no-one wants to maintain any more"<br />
|-<br />
|Activity sprint||Bring all of the Sugar activities to a consistent, up-to-date standard (including consideration of ^^)<br />
|-<br />
|Collaboration sprint||Update Sugar collaboration to reflect advances made since we developed our model.<br />
|-<br />
|Multitouch sprint||Requires GTK3 support.<br />
|-<br />
|Your idea here||...<br />
|}</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Pulsing_icon_delayed_by_5_seconds&diff=62730Pulsing icon delayed by 5 seconds2011-03-01T17:51:12Z<p>MartinDengler: add gonzalo's solution</p>
<hr />
<div>==Pulsing icon delayed by 5 seconds==<br />
<br />
<br />
===Description===<br />
SugarLabs bug [http://bugs.sugarlabs.org/ticket/2080 #2080] was raised because whenever an activity is started in sugar OS , we get to see a few seconds delay after clicking on the activity icon on the home screen and before the appearance of the pulsing icon animation. The delay also seems to be directly proportional to the complexity of the icon of the activity.<br />
<br />
===Proposed solutions and their End Results===<br />
<br />
<br />
===FIX # 1 ===<br />
Tried to reduce the time laag by increasing the duration between the occurrence of two consecutive frames of the pulsing icon animation.<br><br />
'''Result:''' This approach can be used to fix the case of an animation which has more than required FPS and hence couldbe smoothed out using this measure, but it did nothing to solve the main problem of reducing the preanimation delay.<br />
<br />
<br />
===FIX # 2 === <br />
Tried to use the concept of “Frame Skipping” ( a concept commonly used in video games to improve the performance of the game).<br><br />
'''Result:''' This approach couldbe used to fix the case of a laggy animation which runs on low FPS , but it can be used only after the animation starts so it doesnt help in improving the launch time of the pulsing icon animation.<br />
<br />
<br />
===FIX # 3 ===<br />
Tried to tweak the nature of animation by changing the animation to a ZOOM IN animation only from a ZOOM IN and ZOOM OUT animation. i.e. Tried to alter the pulsing nature by restricting the animation by both ZOOMING OUT and ZOOMING IN to only ZOOMING IN.<br><br />
'''Result:''' This approached completely changed the appearance of the pulsing icon but still didnt provide good enough delay reduction.<br />
<br />
<br />
===FIX # 4 ===<br />
Tried to stop the first frame of the animation from being filled with colors , so that upon starting the animation we would get to see a raw grayscale svg icon of the activity for the first frame only and then it would be seamlessly continued with the pulsing icon animation. The patch could be found [http://patchwork.sugarlabs.org/patch/314/ here]. <br><br />
'''Result :''' The idea was to reduce the rendering time of the first frame so as to speed up the appearance of the first frame of the animation and hence reduce the delay. This fix seems to work as per expectations and has reduced the delay time by more than 50% as noted in the logs and reported by the community.We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_v5_result_1.jpg|200px]]<br />
[[File:Patch_v5_result_2.jpg|200px]]<br />
[[File:Patch_v5_result_3.jpg|200px]]<br />
[[File:Patch_v5_result_4.jpg|200px]]<br />
<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix''<br />
<br>.<br />
<br />
===FIX # 5 ===<br />
Here the idea was suggested and implemented by Martin dengler <martin@martindengler.com>. We can find his patch [http://www.martindengler.com/tmp/sl.o-2080/pulsingicon.py-set-new-colors-in-one-go-to-avoid-multiple-calls-to-SVG-rendering.patch here]. <br><br />
Here the idea was to replace the calls to set_stroke_color() and set_fill_color() with set_xo_color(), which does both and then calls _emit_paint_needed_icon_area() which effectively halves the no. of render_cairo() calls hence reducing the workload for the pulsing icon operation by nearly 50%.<br><br />
'''Result :''' The applied patch reduces the delay by more then 60%, as confirmed by the community, but it's worth a note that the zoom in effect is still lost for most svg icons, only for the very simple icons effect is visible (Log icon is simple enough to show it, Distance icon is not quick enough).We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_MD_result_1.jpg|200px]]<br />
[[File:Patch_MD_result_2.jpg|200px]]<br />
[[File:Patch_MD_result_3.jpg|200px]]<br />
[[File:Patch_MD_result_4.jpg|200px]]<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix.''<br />
<br>.<br />
<br />
===FIX # ===<br />
<br />
Gonzalo came up with a patch that uses Cairo to eliminate much of the re-drawing. He published [http://dev.laptop.org/~gonzalo/alpha-pulsingicon/ a version] that is now being polished for merging.<br />
<br />
==Conclusion==<br />
<br />
Gonzalo's fix is preferred.<br />
<br />
===Contact===<br />
<br />
Anurag Chowdhury<br />
<br />
anurag<at>seeta<dot>in</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Taxonomy&diff=61868Taxonomy2011-02-17T11:51:47Z<p>MartinDengler: /* Starch(es): A complete disk image for Sugar */ remove obsolete mention of joyride</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<br />
==Sweet: The abstract design of the experience==<br />
<br />
''(the taste of sugar)''<br />
<br />
Description: "Sweet" is the abstract design of the interface's appearance<br />
and behavior, independent of any code actually implementing this design, and by extension&mdash;the learner experience.<br />
The mockups at [[Design Team/Designs]] represent this<br />
component's second major release, or perhaps 2.0-alpha.<br />
<br />
==Glucose: The base Sugar environment==<br />
<br />
''(the fundamental, simple sugar used by all life forms)''<br />
<br />
Description: Glucose is the minimal system that must be added to a<br />
standard GNU/Linux distribution in order to enable Activities to run. This<br />
includes all the python code and graphics files that implement the shell,<br />
as well as the Journal. Glucose's dependencies may include xorg-server,<br />
xulrunner, squeakvm, rainbow, etc. Some of these dependencies may be<br />
marked optional by distributions. Glucose does not include any Activities<br />
except those like the Journal that are non-optional.<br />
<br />
==Fructose: The set of demonstration activities==<br />
<br />
''(the main sugar in fruit, which is how we're supposed to get our sugar)''<br />
<br />
Description: The Sugar developers will need some example set of<br />
activities with which to demonstrate Sugar. This set is Fructose. The<br />
packages in Fructose should be selected to make the resulting environment<br />
as impressive as possible for a potential client or user. Packages should<br />
therefore be stable, polished, and exercise the widest possible range of<br />
features. Fructose may also serve as an example for people constructing<br />
their own Activity sets.<br />
<br />
==Sucrose: The interface, plus a set of demonstration activities==<br />
<br />
''("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined)''<br />
<br />
Description: Sucrose consists of both Glucose and Fructose. It therefore<br />
represents a complete example Sugar environment, ready to be installed<br />
through a package manager. The purpose of Sucrose is so that prospective<br />
deployers can install the "sugar-sucrose" package, and immediately say<br />
"Wow! Look at all the cool capabilities that this system has!".<br />
<br />
==Ribose: The operating system components developed for Sugar==<br />
<br />
''(the sugar used by all life forms to control their hardware, in the form of RNA. It's important, but not sweet)''<br />
<br />
Description: Ribose is the set of hardware-centric software components<br />
that have been developed throughout this project. It includes the XO<br />
kernels, OHM, any init-script customizations, etc. Ribose should be<br />
construed as including all components necessary to boot the system, enough<br />
to install Glucose if it has not yet been installed.<br />
<br />
==Galactose: a future Sugar base designed for alternate computing forms==<br />
<br />
''(an [[wikipedia:epimer|epimer]] of Glucose, a component of lactose, milk sugar, for the Milky Way galaxy of computing forms searching for something sweet)''<br />
<br />
Description: A hypothetical new Sugar variation that begins to support Learner collaboration with the super nova of new computing forms, especially the [[wikipedia:Template:Mobile_operating_systems|mobile operating systems]], such as, [[wikipedia:Android_(operating_system)#Linux_compatibility|Android]], [[wikipedia:WebOS#Platform|webOS]], [[wikipedia:MeeGo#Technical_foundations|MeeGo]], [[wikipedia:IOS_(Apple)#Development|iOS]], [[wikipedia:Windows_Phone_7#Development|Phone 7]], etc. There is trend towards ubiquitous computing that inspires Learners to great expectations. It will require us to develop clever new [[wikipedia:Monosaccharide_nomenclature|aldoses]], like our XO's Ribose, to meet our children's demand for seamless collaboration without discrimination in their Galactic Neighborhood.<br />
<br />
==Starch(es): A complete disk image for Sugar==<br />
<br />
''(starch is composed of multiple sugars bonded together)''<br />
<br />
Description: We often distribute complete disk images for Sugar, ready to<br />
boot. These images are composed of multiple elements of the above stack.<br />
Each image series should be named separately, to minimize<br />
confusion. For cutesy codenames, we could have a development build<br />
("glycogen", a starch used to produce Glucose) and a stable build<br />
("cellulose", an extremely stable starch).<br />
* In July 2010, Paraguay Educa chose the name '''[[Dextrose|Dextrose]]''' (approximately acronymized from "DEployments' Xo OS") for their release of Sugar 0.88 on Fedora 11 for XO laptops ([http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01213.html announcement]). The molecule [[wikipedia:Dextrose|Dextrose]] is the dextrorotatory form of glucose or D-glucose, the sugar in blood and other living systems. So, it represents a vital infusion for the project.<br />
<br />
== The SUGAR stack: ==<br />
<!-- Before editing this ASCII block diagram, please consider creating a raster or vector-based version. That would be delicious. Thanks! -jcarroll <br />
<br />
+---------------------------------------------------------------+<br />
| SWEET: The abstract design of the experience |<br />
| |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| STARCH: A complete disk image for Sugar |<br />
| |<br />
| +---------------------------------------------------------+ |<br />
| | SUCROSE: The environment, plus a set | |<br />
| | of demonstration activities | |<br />
| | | |<br />
| | +------------------------------+ +--------------------+ | |<br />
| | | FRUCTOSE: A set of demo | | | | |<br />
| | | activities | | | | |<br />
| | | | | | | |<br />
| | +------------------------------+ | | | |<br />
| | +--------------------------------+ | | |<br />
| | | GLUCOSE: The base Sugar environment | | |<br />
| | | | | |<br />
| | +-----------------------------------------------------+ | |<br />
| +---------------------------------------------------------+ |<br />
| |<br />
| +--------------------------------------------------------+ |<br />
| | OPERATING SYSTEM +-----------------+ | |<br />
| | | RIBOSE | | |<br />
| | | | | |<br />
| | +-----------------+ | |<br />
| +--------------------------------------------------------+ |<br />
+---------------------------------------------------------------+<br />
<br />
+---------------------------------------------------------------+<br />
| HARDWARE |<br />
| |<br />
+---------------------------------------------------------------+ --><br />
[[Image:Sugar Taxonomy.png|400px]]<br />
<br />
<!-- The original file is called: Sugar Taxonomy.svg --><br />
*''Note: See discussion for details about the OS/Ribose stacking''<br />
<br />
*Current implementations of Sugar elements can be found at [[Supported systems]]<br />
<br />
==Deepening the concept==<br />
<br />
===Honey: activities developed by 'in the wild' vendors===<br />
<br />
''a sweet fluid made by bees, mostly Fructose''<br />
<br />
Description: Activities that are packaged by outside developers, sometimes ports of activities to Sugar from other OS. It might enhance Sugar and the Sweet experience, but "honey frequently contains dormant endospores of the bacterium Clostridium botulinum, which can be dangerous to infants" [http://en.wikipedia.org/wiki/Honey Wikipedia].<br />
~ For example, Skype, printer capability, IM software <br />
: as a former beekeeper I can tell you that not all honey is organic, though we all wish it were so (antibiotics taint a lot of it, especially in developing countries) [[User:Yamaplos|Yamaplos]] 15:04, 17 May 2008 (UTC)<br />
<br />
==One-liners==<br />
<br />
* Lead acetate: An implementation of Sweet on Windows. Sweeter than sugar, but [http://www.healthychildrenproject.org/pdf/PPLEAD.pdf toxic to young brains].<br />
* ''[http://en.wikipedia.org/wiki/Aspartame_controversy aspartame] - once thought better than sugar, but possibly connected with brain tumors''<sub>[[User:Morgs|Morgs]] 11:44, 17 May 2008 (UTC)</sub><br />
* ''So you're saying Sugar is now suite? ''<sub>Kevin Cole</sub><br />
* ''Caramel: a "feature freeze" on Sucrose''<br />
* ''Diabetic OS: an OS that cannot handle Sugar yet'' <sub>Yama Ploskonka</sub><br />
* ''Molasses: a beta, unfinished release of Sugar''<br />
* ''High Fructose Corn Syrup: Apparently similar, but made of patented materials'' <sub>Morgan Collett</sub><br />
* ''How sweet it is!'' <sub>Jackie Gleason</sub><br />
* ''Insulin: what Microsoft needs to make Sugar go away.'' <sub>davewa</sub><br />
<br />
== Glossary ==<br />
<br />
See [[Glossary]].</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Release/Modules&diff=59454Development Team/Release/Modules2010-11-20T09:42:03Z<p>MartinDengler: Glucose: sugar is unmaintained</p>
<hr />
<div><noinclude>[[Category:Development Team]]<br />
See also [[:Category:Platform Cycle]].<br />
<br />
:Bug Tracking: http://bugs.sugarlabs.org/<br />
<br />
:Home page: http://sugarlabs.org/<br />
</noinclude><br />
== Glucose ==<br />
:<span style="font-size: 150%">(Core modules)</span><br />
<br />
{| class="wikitable"<br />
|-<br />
!Module<br />
!Lead Maintainer<br />
!Co-maintainers<br />
!Code Repository<br />
|-<br />
|sugar<br />
|unmaintained<br />
|[[User:Erikos|Simon Schampijer]] <br> [[User:Alsroot|Aleksey Lim]] (Journal) <br> [[User:MartinDengler|Martin Dengler]]<br />
|http://git.sugarlabs.org/projects/sugar<br />
|-<br />
|sugar-base<br />
|[[User:Erikos|Simon Schampijer]]<br />
|[[User:MartinDengler|Martin Dengler]]<br />
|http://git.sugarlabs.org/projects/sugar-base<br />
|-<br />
|sugar-datastore<br />
|[[User:Alsroot|Aleksey Lim]]<br />
|[[User:sascha_silbe|Sascha Silbe]]<br />
|http://git.sugarlabs.org/projects/sugar-datastore<br />
|-<br />
|sugar-presence-service<br />
|unmaintained<br />
|[[User:Cassidy|Guillaume Desmottes]]<br />
|http://git.sugarlabs.org/projects/sugar-presence-service<br />
|-<br />
|sugar-toolkit<br />
|[[User:Erikos|Simon Schampijer]]<br />
|[[User:MartinDengler|Martin Dengler]] <br> [[User:Alsroot|Aleksey Lim]]<br />
|http://git.sugarlabs.org/projects/sugar-toolkit<br />
|-<br />
|sugar-artwork<br />
|[[User:BenjaminBerg|Benjamin Berg]]<br />
|[[User:Erikos|Simon Schampijer]] <br> [[User:Garycmartin|Gary C. Martin]]<br />
|http://git.sugarlabs.org/projects/sugar-artwork<br />
|-<br />
|hulahop<br />
|unmaintained<br />
|<br />
|http://git.sugarlabs.org/projects/hulahop<br />
|}<br />
<br />
== Fructose ==<br />
:<span style="font-size: 150%">(Base activities)</span><br />
===chat===<br />
:Lead Maintainer: unmaintained<br />
:Co-maintainers: [[User:Alsroot|Aleksey Lim]]<br />
:Code Repository: http://git.sugarlabs.org/projects/chat<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Chat, [[Activities/Chat]]<br />
<br />
===browse===<br />
:Lead Maintainer: [[User:Lucian|Lucian Branescu Mihaila]], [[User:sascha_silbe|Sascha Silbe]]<br />
:Co-maintainers: <br />
:Code Repository: http://git.sugarlabs.org/projects/browse<br />
:Release tarballs: <br />
:Bug Tracking: [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Browse bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Browse, [[Activities/Browse]]<br />
<br />
===read===<br />
:Lead Maintainer: [http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
:Co-maintainers: [[User:Erikos|Simon Schampijer]]<br />
:Code Repository: http://git.sugarlabs.org/projects/read<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Read, [[Activities/Read]]<br />
<br />
===calculate===<br />
:Lead Maintainer: Reinier Heeres<br />
:Co-maintainers: <br />
:Code Repository: http://git.sugarlabs.org/projects/calculate<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Calculate, [[Activities/Calculate]]<br />
<br />
===log===<br />
:Lead Maintainer: unmaintained<br />
:Co-maintainers: [http://edsiper.linuxchile.cl Eduardo Silva], [[User:Alsroot|Aleksey Lim]]<br />
:Code Repository: http://git.sugarlabs.org/projects/log<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Log<br />
<br />
===write===<br />
:Lead Maintainer: [http://uwog.net/ J.M. Maurer]<br />
:Co-maintainers: [http://msevior.livejournal.com/ Martin Sevior]<br />
:Code Repository: http://git.sugarlabs.org/projects/write<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Write, [[Activities/Write]]<br />
<br />
===terminal===<br />
:Lead Maintainer: [http://git.sugarlabs.org/projects/terminal/repos/mainline/blobs/master/MAINTAINERS MAINTAINERS], [http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
:Co-maintainers: [http://edsiper.linuxchile.cl Eduardo Silva], [[User:Wade|Wade Brainerd]]<br />
:Code Repository: http://git.sugarlabs.org/projects/terminal<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Terminal, [[Activities/Terminal]]<br />
<br />
===pippy===<br />
:Lead Maintainer: [http://git.sugarlabs.org/projects/pippy/repos/mainline/blobs/master/MAINTAINERS MAINTAINERS], [[User:m_anish|Anish Mangal]]<br />
:Co-maintainers: [[User:Cjb|Chris Ball]], [http://cscott.net C. Scott Ananian]<br />
:Code Repository: http://git.sugarlabs.org/projects/pippy<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Pippy, [[Activities/Pippy]]<br />
<br />
===etoys===<br />
:Lead Maintainer: [[User:Bert|Bert Freudenberg]]<br />
:Co-maintainers: Squeakland developers<br />
:Code Repository: http://dev.laptop.org/git/projects/etoys/ and http://etoys.laptop.org/svn/trunk/etoys/<br />
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/glucose/etoys/<br />
:Bug Tracking: http://tracker.squeakland.org/<br />
:Home page: http://www.squeakland.org/<br />
<br />
===etoys-activity===<br />
:Lead Maintainer: [[User:Bert|Bert Freudenberg]]<br />
:Co-maintainers: Squeakland developers<br />
:Code Repository: http://dev.laptop.org/git/projects/etoys/<br />
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/<br />
:Bug Tracking: http://tracker.squeakland.org/<br />
:Home page: http://wiki.laptop.org/go/Etoys, [[Activities/Etoys]]<br />
<br />
===imageviewer===<br />
:Lead Maintainer: [http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
:Co-maintainers: <br />
:Code Repository: http://git.sugarlabs.org/projects/imageviewer<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Image Viewer<br />
<br />
===jukebox===<br />
:Lead Maintainer: [http://kushaldas.in Kushal Das]<br />
:Co-maintainers:<br />
:Code Repository: http://git.sugarlabs.org/projects/jukebox<br />
:Release tarballs: <br />
:Bug Tracking: [http://bugs.sugarlabs.org/ bugs.sl.o]<br />
:Home page: http://wiki.laptop.org/go/Jukebox<br />
<br />
===turtleart===<br />
:Lead Maintainer: [[User:Walter|Walter Bender]]<br />
:Co-maintainers: Raúl Gutiérrez Segalés <br><br />
:Code Repository: http://git.sugarlabs.org/projects/turtleart<br />
:Release tarballs: http://download.sugarlabs.org/sources/sucrose/fructose/TurtleArt/<br />
:Bug Tracking: [http://bugs.sugarlabs.org bugs.sl.o] <br><br />
:Home page: [[Activities/Turtle Art]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Contacts&diff=59453Design Team/Contacts2010-11-20T09:11:23Z<p>MartinDengler: /* Team Members */ add MartinDengler</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Design Team|roadmap_link=Design Team/Vision|roadmap_label=Vision}}</noinclude>{{TOCright}}<br />
<br />
== Coordinators ==<br />
{{:Design Team/Coordinator}}<br />
<br />
== IRC channel ==<br />
Sugar designers (and developers) hang out in the [irc://irc.freenode.net/sugar #sugar] channel on irc.freenode.net.<br />
<br />
== Team Members ==<br />
Please add yourself to the list if you're interested in participating!<br />
<br />
*[[User:Eben | Eben Eliason]]<br />
*[[User:christianmarcschmidt | Christian Marc Schmidt]]<br />
*[[User:Josh | Josh Williams]]<br />
*[[User:garycmartin | Gary C Martin]]<br />
*[[User:MartinDengler | Martin Dengler]]<br />
<br />
<br />
[[Category:Design Team]]<br />
[[Category:Contact]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=User:MartinDengler&diff=58940User:MartinDengler2010-11-07T08:05:25Z<p>MartinDengler: update & tidyup</p>
<hr />
<div>====Martin Dengler====<br />
<br />
I program in python for a [http://www.martindengler.com/resume.pdf living], and got interested in Sugar/XO through OLPC's G1G1 program.<br />
<br />
====Sugar review queue====<br />
<br />
[http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&keywords=~r%2B Approved but not committed]<br />
[http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&keywords=~r%3F Review requested]<br />
<br />
====See also====<br />
<br />
See also [http://wiki.laptop.org/go/User:MartinDengler My wiki.laptop.org user page]<br />
<br />
====Contact====<br />
email: martin at martindengler.com<br />
<br />
irc: mtd at FreeNode (#sugar, #olpc)<br />
<br />
====Commentaries====<br />
<br />
[[/Commentaries:SoaSonXO|SoaS on XO]]<br />
<br />
[[/Commentaries:SoaSReleaseNaming|SoaS Release naming]]<br />
<br />
[[/Commentaries:SoaSPancakePage|SoaS Pancake Page]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58939Oversight Board/2010-2011-candidates2010-11-07T07:51:34Z<p>MartinDengler: /* Election */ correct open seats from three to four</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
==Election==<br />
Four (4) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2010-2011: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]], and [[User:Tomeu|Tomeu Vizoso]]'s seats.<br />
<br />
==Candidates==<br />
Here are the candidates:<br />
<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]], [http://lists.sugarlabs.org/archive/iaep/2010-October/011885.html look-reform-in-the-eye proposal])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog], [http://www.youtube.com/watch?v=kDbGHeVblmg "Teorema de Pitágoras"], [http://www.youtube.com/watch?v=mNmBzdHi0ws "Ciclo de la esponja vegetal"], [http://www.youtube.com/watch?v=1ttrLD4LyPk "Porcentajes"], [http://www.youtube.com/watch?v=6eh7EOmo6es "Fracciones equivalentes"])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
* [[User:Sebastian|Sebastian Silva]] ([http://somosazucar.org/2010/11/06/candidatura-para-sugar-labs-2010/ Ver Propuesta])<br />
* [[User:Alsroot/SLOBs_election_platform|Aleksey Lim]], [[User:Alsroot/Sugar_Architecture|"Sugar Architecture"]]<br />
* [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea]<br />
* [[User:Pacita|Pacita Peña]] de Paraguay Educa, [http://departamentodeeducacion-pyeduca.blogspot.com/ ver blog!]<br />
<br />
==Candidate list is CLOSED==<br />
<br />
The candidate list is CLOSED (frozen) as of November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Pulsing_icon_delayed_by_5_seconds&diff=58884Pulsing icon delayed by 5 seconds2010-11-05T10:33:39Z<p>MartinDengler: finally get link right</p>
<hr />
<div>==Pulsing icon delayed by 5 seconds==<br />
<br />
<br />
===Description===<br />
SugarLabs bug [http://bugs.sugarlabs.org/ticket/2080 #3080] was raised because whenever an activity is started in sugar OS , we get to see a few seconds delay after clicking on the activity icon on the home screen and before the appearance of the pulsing icon animation. The delay also seems to be directly proportional to the complexity of the icon of the activity.<br />
<br />
===Proposed solutions and their End Results===<br />
<br />
<br />
===FIX # 1 ===<br />
Tried to reduce the time laag by increasing the duration between the occurrence of two consecutive frames of the pulsing icon animation.<br><br />
'''Result:''' This approach can be used to fix the case of an animation which has more than required FPS and hence couldbe smoothed out using this measure, but it did nothing to solve the main problem of reducing the preanimation delay.<br />
<br />
<br />
===FIX # 2 === <br />
Tried to use the concept of “Frame Skipping” ( a concept commonly used in video games to improve the performance of the game).<br><br />
'''Result:''' This approach couldbe used to fix the case of a laggy animation which runs on low FPS , but it can be used only after the animation starts so it doesnt help in improving the launch time of the pulsing icon animation.<br />
<br />
<br />
===FIX # 3 ===<br />
Tried to tweak the nature of animation by changing the animation to a ZOOM IN animation only from a ZOOM IN and ZOOM OUT animation. i.e. Tried to alter the pulsing nature by restricting the animation by both ZOOMING OUT and ZOOMING IN to only ZOOMING IN.<br><br />
'''Result:''' This approached completely changed the appearance of the pulsing icon but still didnt provide good enough delay reduction.<br />
<br />
<br />
===FIX # 4 ===<br />
Tried to stop the first frame of the animation from being filled with colors , so that upon starting the animation we would get to see a raw grayscale svg icon of the activity for the first frame only and then it would be seamlessly continued with the pulsing icon animation. The patch could be found [http://patchwork.sugarlabs.org/patch/314/ here]. <br><br />
'''Result :''' The idea was to reduce the rendering time of the first frame so as to speed up the appearance of the first frame of the animation and hence reduce the delay. This fix seems to work as per expectations and has reduced the delay time by more than 50% as noted in the logs and reported by the community.We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_v5_result_1.jpg|200px]]<br />
[[File:Patch_v5_result_2.jpg|200px]]<br />
[[File:Patch_v5_result_3.jpg|200px]]<br />
[[File:Patch_v5_result_4.jpg|200px]]<br />
<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix''<br />
<br>.<br />
<br />
===FIX # 5 ===<br />
Here the idea was suggested and implemented by Martin dengler <martin@martindengler.com>. We can find his patch [http://www.martindengler.com/tmp/sl.o-2080/pulsingicon.py-set-new-colors-in-one-go-to-avoid-multiple-calls-to-SVG-rendering.patch here]. <br><br />
Here the idea was to replace the calls to set_stroke_color() and set_fill_color() with set_xo_color(), which does both and then calls _emit_paint_needed_icon_area() which effectively halves the no. of render_cairo() calls hence reducing the workload for the pulsing icon operation by nearly 50%.<br><br />
'''Result :''' The applied patch reduces the delay by more then 60%, as confirmed by the community, but it's worth a note that the zoom in effect is still lost for most svg icons, only for the very simple icons effect is visible (Log icon is simple enough to show it, Distance icon is not quick enough).We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_MD_result_1.jpg|200px]]<br />
[[File:Patch_MD_result_2.jpg|200px]]<br />
[[File:Patch_MD_result_3.jpg|200px]]<br />
[[File:Patch_MD_result_4.jpg|200px]]<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix.''<br />
<br>.<br />
<br />
===Contact===<br />
<br />
Anurag Chowdhury<br />
<br />
anurag<at>seeta<dot>in</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Pulsing_icon_delayed_by_5_seconds&diff=58883Pulsing icon delayed by 5 seconds2010-11-05T10:33:26Z<p>MartinDengler: /* Pulsing icon delayed by 5 seconds */</p>
<hr />
<div>==Pulsing icon delayed by 5 seconds==<br />
<br />
<br />
===Description===<br />
SugarLabs bug [[http://bugs.sugarlabs.org/ticket/2080 #3080] was raised because whenever an activity is started in sugar OS , we get to see a few seconds delay after clicking on the activity icon on the home screen and before the appearance of the pulsing icon animation. The delay also seems to be directly proportional to the complexity of the icon of the activity.<br />
<br />
===Proposed solutions and their End Results===<br />
<br />
<br />
===FIX # 1 ===<br />
Tried to reduce the time laag by increasing the duration between the occurrence of two consecutive frames of the pulsing icon animation.<br><br />
'''Result:''' This approach can be used to fix the case of an animation which has more than required FPS and hence couldbe smoothed out using this measure, but it did nothing to solve the main problem of reducing the preanimation delay.<br />
<br />
<br />
===FIX # 2 === <br />
Tried to use the concept of “Frame Skipping” ( a concept commonly used in video games to improve the performance of the game).<br><br />
'''Result:''' This approach couldbe used to fix the case of a laggy animation which runs on low FPS , but it can be used only after the animation starts so it doesnt help in improving the launch time of the pulsing icon animation.<br />
<br />
<br />
===FIX # 3 ===<br />
Tried to tweak the nature of animation by changing the animation to a ZOOM IN animation only from a ZOOM IN and ZOOM OUT animation. i.e. Tried to alter the pulsing nature by restricting the animation by both ZOOMING OUT and ZOOMING IN to only ZOOMING IN.<br><br />
'''Result:''' This approached completely changed the appearance of the pulsing icon but still didnt provide good enough delay reduction.<br />
<br />
<br />
===FIX # 4 ===<br />
Tried to stop the first frame of the animation from being filled with colors , so that upon starting the animation we would get to see a raw grayscale svg icon of the activity for the first frame only and then it would be seamlessly continued with the pulsing icon animation. The patch could be found [http://patchwork.sugarlabs.org/patch/314/ here]. <br><br />
'''Result :''' The idea was to reduce the rendering time of the first frame so as to speed up the appearance of the first frame of the animation and hence reduce the delay. This fix seems to work as per expectations and has reduced the delay time by more than 50% as noted in the logs and reported by the community.We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_v5_result_1.jpg|200px]]<br />
[[File:Patch_v5_result_2.jpg|200px]]<br />
[[File:Patch_v5_result_3.jpg|200px]]<br />
[[File:Patch_v5_result_4.jpg|200px]]<br />
<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix''<br />
<br>.<br />
<br />
===FIX # 5 ===<br />
Here the idea was suggested and implemented by Martin dengler <martin@martindengler.com>. We can find his patch [http://www.martindengler.com/tmp/sl.o-2080/pulsingicon.py-set-new-colors-in-one-go-to-avoid-multiple-calls-to-SVG-rendering.patch here]. <br><br />
Here the idea was to replace the calls to set_stroke_color() and set_fill_color() with set_xo_color(), which does both and then calls _emit_paint_needed_icon_area() which effectively halves the no. of render_cairo() calls hence reducing the workload for the pulsing icon operation by nearly 50%.<br><br />
'''Result :''' The applied patch reduces the delay by more then 60%, as confirmed by the community, but it's worth a note that the zoom in effect is still lost for most svg icons, only for the very simple icons effect is visible (Log icon is simple enough to show it, Distance icon is not quick enough).We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_MD_result_1.jpg|200px]]<br />
[[File:Patch_MD_result_2.jpg|200px]]<br />
[[File:Patch_MD_result_3.jpg|200px]]<br />
[[File:Patch_MD_result_4.jpg|200px]]<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix.''<br />
<br>.<br />
<br />
===Contact===<br />
<br />
Anurag Chowdhury<br />
<br />
anurag<at>seeta<dot>in</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Pulsing_icon_delayed_by_5_seconds&diff=58882Pulsing icon delayed by 5 seconds2010-11-05T10:33:09Z<p>MartinDengler: /* Pulsing icon delayed by 5 seconds */</p>
<hr />
<div>==Pulsing icon delayed by 5 seconds==<br />
<br />
<br />
===Description===<br />
SugarLabs bug [[http://bugs.sugarlabs.org/ticket/2080|#3080] was raised because whenever an activity is started in sugar OS , we get to see a few seconds delay after clicking on the activity icon on the home screen and before the appearance of the pulsing icon animation. The delay also seems to be directly proportional to the complexity of the icon of the activity.<br />
<br />
===Proposed solutions and their End Results===<br />
<br />
<br />
===FIX # 1 ===<br />
Tried to reduce the time laag by increasing the duration between the occurrence of two consecutive frames of the pulsing icon animation.<br><br />
'''Result:''' This approach can be used to fix the case of an animation which has more than required FPS and hence couldbe smoothed out using this measure, but it did nothing to solve the main problem of reducing the preanimation delay.<br />
<br />
<br />
===FIX # 2 === <br />
Tried to use the concept of “Frame Skipping” ( a concept commonly used in video games to improve the performance of the game).<br><br />
'''Result:''' This approach couldbe used to fix the case of a laggy animation which runs on low FPS , but it can be used only after the animation starts so it doesnt help in improving the launch time of the pulsing icon animation.<br />
<br />
<br />
===FIX # 3 ===<br />
Tried to tweak the nature of animation by changing the animation to a ZOOM IN animation only from a ZOOM IN and ZOOM OUT animation. i.e. Tried to alter the pulsing nature by restricting the animation by both ZOOMING OUT and ZOOMING IN to only ZOOMING IN.<br><br />
'''Result:''' This approached completely changed the appearance of the pulsing icon but still didnt provide good enough delay reduction.<br />
<br />
<br />
===FIX # 4 ===<br />
Tried to stop the first frame of the animation from being filled with colors , so that upon starting the animation we would get to see a raw grayscale svg icon of the activity for the first frame only and then it would be seamlessly continued with the pulsing icon animation. The patch could be found [http://patchwork.sugarlabs.org/patch/314/ here]. <br><br />
'''Result :''' The idea was to reduce the rendering time of the first frame so as to speed up the appearance of the first frame of the animation and hence reduce the delay. This fix seems to work as per expectations and has reduced the delay time by more than 50% as noted in the logs and reported by the community.We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_v5_result_1.jpg|200px]]<br />
[[File:Patch_v5_result_2.jpg|200px]]<br />
[[File:Patch_v5_result_3.jpg|200px]]<br />
[[File:Patch_v5_result_4.jpg|200px]]<br />
<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix''<br />
<br>.<br />
<br />
===FIX # 5 ===<br />
Here the idea was suggested and implemented by Martin dengler <martin@martindengler.com>. We can find his patch [http://www.martindengler.com/tmp/sl.o-2080/pulsingicon.py-set-new-colors-in-one-go-to-avoid-multiple-calls-to-SVG-rendering.patch here]. <br><br />
Here the idea was to replace the calls to set_stroke_color() and set_fill_color() with set_xo_color(), which does both and then calls _emit_paint_needed_icon_area() which effectively halves the no. of render_cairo() calls hence reducing the workload for the pulsing icon operation by nearly 50%.<br><br />
'''Result :''' The applied patch reduces the delay by more then 60%, as confirmed by the community, but it's worth a note that the zoom in effect is still lost for most svg icons, only for the very simple icons effect is visible (Log icon is simple enough to show it, Distance icon is not quick enough).We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_MD_result_1.jpg|200px]]<br />
[[File:Patch_MD_result_2.jpg|200px]]<br />
[[File:Patch_MD_result_3.jpg|200px]]<br />
[[File:Patch_MD_result_4.jpg|200px]]<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix.''<br />
<br>.<br />
<br />
===Contact===<br />
<br />
Anurag Chowdhury<br />
<br />
anurag<at>seeta<dot>in</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Pulsing_icon_delayed_by_5_seconds&diff=58881Pulsing icon delayed by 5 seconds2010-11-05T10:32:38Z<p>MartinDengler: add link to #3080</p>
<hr />
<div>==Pulsing icon delayed by 5 seconds==<br />
<br />
<br />
===Description===<br />
SugarLabs bug #3080 was raised because whenever an activity is started in sugar OS , we get to see a few seconds delay after clicking on the activity icon on the home screen and before the appearance of the pulsing icon animation. The delay also seems to be directly proportional to the complexity of the icon of the activity.<br />
<br />
===Proposed solutions and their End Results===<br />
<br />
<br />
===FIX # 1 ===<br />
Tried to reduce the time laag by increasing the duration between the occurrence of two consecutive frames of the pulsing icon animation.<br><br />
'''Result:''' This approach can be used to fix the case of an animation which has more than required FPS and hence couldbe smoothed out using this measure, but it did nothing to solve the main problem of reducing the preanimation delay.<br />
<br />
<br />
===FIX # 2 === <br />
Tried to use the concept of “Frame Skipping” ( a concept commonly used in video games to improve the performance of the game).<br><br />
'''Result:''' This approach couldbe used to fix the case of a laggy animation which runs on low FPS , but it can be used only after the animation starts so it doesnt help in improving the launch time of the pulsing icon animation.<br />
<br />
<br />
===FIX # 3 ===<br />
Tried to tweak the nature of animation by changing the animation to a ZOOM IN animation only from a ZOOM IN and ZOOM OUT animation. i.e. Tried to alter the pulsing nature by restricting the animation by both ZOOMING OUT and ZOOMING IN to only ZOOMING IN.<br><br />
'''Result:''' This approached completely changed the appearance of the pulsing icon but still didnt provide good enough delay reduction.<br />
<br />
<br />
===FIX # 4 ===<br />
Tried to stop the first frame of the animation from being filled with colors , so that upon starting the animation we would get to see a raw grayscale svg icon of the activity for the first frame only and then it would be seamlessly continued with the pulsing icon animation. The patch could be found [http://patchwork.sugarlabs.org/patch/314/ here]. <br><br />
'''Result :''' The idea was to reduce the rendering time of the first frame so as to speed up the appearance of the first frame of the animation and hence reduce the delay. This fix seems to work as per expectations and has reduced the delay time by more than 50% as noted in the logs and reported by the community.We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_v5_result_1.jpg|200px]]<br />
[[File:Patch_v5_result_2.jpg|200px]]<br />
[[File:Patch_v5_result_3.jpg|200px]]<br />
[[File:Patch_v5_result_4.jpg|200px]]<br />
<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix''<br />
<br>.<br />
<br />
===FIX # 5 ===<br />
Here the idea was suggested and implemented by Martin dengler <martin@martindengler.com>. We can find his patch [http://www.martindengler.com/tmp/sl.o-2080/pulsingicon.py-set-new-colors-in-one-go-to-avoid-multiple-calls-to-SVG-rendering.patch here]. <br><br />
Here the idea was to replace the calls to set_stroke_color() and set_fill_color() with set_xo_color(), which does both and then calls _emit_paint_needed_icon_area() which effectively halves the no. of render_cairo() calls hence reducing the workload for the pulsing icon operation by nearly 50%.<br><br />
'''Result :''' The applied patch reduces the delay by more then 60%, as confirmed by the community, but it's worth a note that the zoom in effect is still lost for most svg icons, only for the very simple icons effect is visible (Log icon is simple enough to show it, Distance icon is not quick enough).We can see the below attached screenshots showing the visual effects, after the application of the patch on an XO-1.5 <br />
<br><br />
[[File:Patch_MD_result_1.jpg|200px]]<br />
[[File:Patch_MD_result_2.jpg|200px]]<br />
[[File:Patch_MD_result_3.jpg|200px]]<br />
[[File:Patch_MD_result_4.jpg|200px]]<br />
<br><br />
''The screenshots sequentially show the frames of the pulsing icon animation after the application of the above fix.''<br />
<br>.<br />
<br />
===Contact===<br />
<br />
Anurag Chowdhury<br />
<br />
anurag<at>seeta<dot>in</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58692Oversight Board/2010-2011-candidates2010-10-31T07:33:28Z<p>MartinDengler: Blanked the page</p>
<hr />
<div></div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=User_talk:MartinDengler&diff=58573User talk:MartinDengler2010-10-28T17:47:07Z<p>MartinDengler: Created page with "test"</p>
<hr />
<div>test</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58544Oversight Board/2010-2011-candidates2010-10-27T04:19:27Z<p>MartinDengler: break out candidate section</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
==Election==<br />
Three (3) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2010-2011: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]]'s seats.<br />
<br />
==Candidates==<br />
Here are the candidates:<br />
<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
<br />
==Candidate list is OPEN==<br />
<br />
PLEASE ADD YOUR NAME and a link to some background information or position statement.<br />
<br />
==Candidate list CLOSING deadline==<br />
<br />
The candidate list will be CLOSED (frozen) on November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58543Oversight Board/2010-2011-candidates2010-10-27T04:17:30Z<p>MartinDengler: </p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
==Election==<br />
Three (3) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2010-2011: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]]'s seats.<br />
<br />
A link may be included to some background information or position statement for the candidate.<br />
<br />
<br />
==Candidates==<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
<br />
(PLEASE ADD YOUR NAME HERE! By November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58542Oversight Board/2010-2011-candidates2010-10-27T04:16:57Z<p>MartinDengler: explicitly reference staggered seats</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
==Election==<br />
Three (3) seats are open ([[Sugar Labs/Governance#Oversight_Board|due to staggered seat terms]]) for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2010-2011: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]].<br />
<br />
A link may be included to some background information or position statement for the candidate.<br />
<br />
<br />
==Candidates==<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
<br />
(PLEASE ADD YOUR NAME HERE! By November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58541Oversight Board/2010-2011-candidates2010-10-27T04:16:04Z<p>MartinDengler: add sections, tighten up & cross-reference summary</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
==Election==<br />
[[Sugar Labs/Governance#Oversight_Board|Three (3) seats are open]] for election / re-election to the [[Oversight Board|Sugar Labs Oversight Board]] for 2010-2011: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]].<br />
<br />
A link may be included to some background information or position statement for the candidate.<br />
<br />
<br />
==Candidates==<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
<br />
(PLEASE ADD YOUR NAME HERE! By November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Oversight_Board/2010-2011-candidates&diff=58540Oversight Board/2010-2011-candidates2010-10-27T04:05:54Z<p>MartinDengler: add that three seats are up for re-election</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}</noinclude><br />
<br />
Below are the candidates for the Sugar Labs Oversight Board for 2010–2011.<br />
<br />
Three (3) seats are open for election / re-election: [[User:cjb|Chris Ball]], [[User:Holt|Adam Holt]], [[User:SeanDaly|Sean Daly]].<br />
<br />
A link may be included to some background information or position statement for the candidate.<br />
<br />
* [http://google.com/search?q=adam+holt+mit Adam Holt] ([[User:Holt|7-point platform]])<br />
* [[User:SMParrish|Steven Parrish]]<br />
* [[User:cjb|Chris Ball]]<br />
* Rosamel Norma Ramirez Mendez ([http://www.blogedu-rosamel.blogspot.com/ blog])<br />
* Gerald Ardito ([http://web.me.com/geraldar/The_Shape_of_Disruption/Welcome.html/ doctoral work website])<br />
<br />
(PLEASE ADD YOUR NAME HERE! By November 1st 11:59PM [http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html EDT], 2010)<br />
<br />
==References==<br />
* [[Oversight_Board/2009-2010-candidates]]<br />
* 23 September 2009 - [http://lists.sugarlabs.org/archive/iaep/2009-September/008620.html Oversight Board election procedure update]<br />
* [[Sugar Labs/Governance]]<br />
* [[Oversight Board]]<br />
* [[Archive/Current Events/2009-08-05#Help_wanted]]<br />
* [[Sugar Labs/Members]]<br />
<br />
[[Category:Oversight board]]<br />
[[Category:Governance]]<br />
<br />
[[Category:Team]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_Labs/Governance&diff=58539Sugar Labs/Governance2010-10-27T03:56:16Z<p>MartinDengler: /* Sugar Labs Rules of Governance */ s/comment in-line/comment/ - in-line comments in rules of governance is TEH MADNES</p>
<hr />
<div><noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude><br />
{{TOCright}}<br />
==Sugar Labs Rules of Governance==<br />
Please comment on the [[Talk:Sugar Labs/Governance|discussion page]].<br />
<br />
----<br />
<br />
One of the challenges that free software projects face is the impact of governance on their community members: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary.<br />
<br />
Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making. <br />
<br />
===Software Freedom Conservancy===<br />
<br />
Sugar Labs is a member of the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar.<br />
<br />
The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]).<br />
<br />
==== Transactions ====<br />
<br />
As a fiscal sponsor for FOSS projects, the Conservancy provides member projects with financial and administrative services:<br />
<br />
* [[Sugar_Labs/Governance/Transactions#Request_for_payment|Request for payment]]<br />
* [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]]<br />
* [[Sugar_Labs/Governance/Transactions#License_request|License request]]<br />
<br />
===Oversight Board===<br />
<br />
The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]].<br />
<br />
Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Oversight Board/Minutes]]).<br />
<br />
The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board.<br />
<br />
The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters.<br />
<br />
====Decision Panels====<br />
<br />
The Oversight Board's role is to manage the day-to-day affairs of Sugar Labs and to help the community to build consensus. On the rare occasion of a contentious issue on which no general consensus can be reached, the Oversight Board is responsible for convening a Decision Panel. The Oversight Board will be responsible for determining when a Decision Panel is required and for selecting members for the Decision Panel. Members of the Oversight Board are not permitted to serve on a Decision Panel. A Decision Panel will solicit community input, discuss (in private if they deem it necessary), reach a conclusion internally, and produce a report documenting their conclusion. (Anyone may submit advice to a Decision Panel.) The Oversight Board will review and ratify Decision Panel reports.<br />
<br />
===Advisory Board===<br />
<br />
The [[Sugar Labs/Governance/Advisory Board|Advisory Board]] is made up of organizations and companies that support Sugar Labs. The Advisory Board has no decision-making authority but provides a vehicle for its members to communicate with the Oversight Board and help the Directors guide the overall direction of Sugar and the Sugar Labs Project. The Advisory Board will appoint (up to) three (3) members who will be non-voting attendees of Oversight Board meetings. The Advisory Board will meet up to twice per year.<br />
<br />
The Advisory Board consists of representatives from the following Sugar Labs Foundation member corporations and projects.<br />
<br />
Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project.<br />
<br />
===Committees===<br />
<br />
The Oversight Board is responsible for establishing [[Sugar Labs/Governance/Committees|committees]] as necessary.<br />
<br />
Each committee will include one member from the Oversight Board (non-voting), who will server as a recording secretary, and three (3) to five (5) additional members (initially appointed by the Oversight Board and subsequently elected) from the community.<br />
<br />
Special Interest Groups (SIGs) may be established by any member. They can be formed around any topic and, if they prove to be useful, can be designated as official committees.<br />
<br />
Advisory committees will provide input in advance of Oversight Board meetings and may be asked on occasion to send a representative to a meeting of the Oversight Board.<br />
<br />
{{Transclude|Sugar Labs/Members|heading=<nowiki></nowiki>}}<br />
<br />
===Sugar Labs Referenda===<br />
<br />
At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org. <br />
<br />
A 75% vote of all of the members can override an Oversight Board decision.<br />
<br />
=== Subpages ===<br />
<br />
{{Special:PrefixIndex/{{PAGENAMEE}}/}}<br />
<br />
[[Category:General public]]<br />
[[Category:Governance]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=56825Development Team/Jhbuild2010-09-14T02:29:01Z<p>MartinDengler: moved time-specific hulahop issue note to new section at end</p>
<hr />
<div><noinclude>{{Translations}}{{TOCright}}</noinclude><br />
<br />
Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.<br />
Below are generic instructions on how to use jhbuild to get up and running with Sugar.<br />
<br />
==Compatible platforms==<br />
<br />
Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.<br />
<br />
See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).<br />
<br />
==Check distro-specific instructions==<br />
<br />
Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]). <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Communication channels#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Communication channels#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
<br />
Install everything depscheck complains about. [[#Check distro-specific instructions|Read the distro-specific instructions]] for how to do this.<br />
Now build all Sugar packages in sugar-jhbuild:<br />
<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].<br />
<br />
If everything worked out fine, you can now [[#Run Sugar|run Sugar]].<br />
If it doesn't run or you have other problems read on.<br />
<br />
=== Dealing with dependencies ===<br />
<br />
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [https://bugs.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips===<br />
<br />
A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build without -n will update first anyway, so run update separately if you want to see what changed more easily.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build -n -a --clean<br />
./sugar-jhbuild run sugar-emulator<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
=== If build breaks after an update ===<br />
<br />
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
If your problem persists for more than a day (and even though you installed all missing packages), please [https://bugs.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].<br />
<br />
== Run Sugar ==<br />
<br />
Note: if you have a non-US keyboard, please follow the instructions on [[#Running sugar in a VNC session|running Sugar in a VNC session]] instead.<br />
<br />
This command launches Sugar in a nested X session:<br />
<br />
./sugar-jhbuild run sugar-emulator<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended. The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running sugar in a VNC session ==<br />
<br />
Many users and developers have reported problems with running sugar-emulator in its default window manager, Xephyr. As an alternative, you can run sugar-emulator in a VNC session. To accomplish this, install a complete set of VNC packages (both server and client) and create a <code>~/.vnc/xstartup</code> file containing the code below:<br />
<br />
#!/bin/sh<br />
exec ~/sugar-jhbuild/sugar-jhbuild run dbus-launch --exit-with-session sugar<br />
<br />
Note: The above code assumes that sugar-jhbuild is installed in the <code>~/sugar-jhbuild/</code> directory.<br />
<br />
Now, you may run Sugar by creating a VNC session and accessing it using a VNC viewer. E.g.:<br />
vncserver :1<br />
vncviewer :1<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch ''bundle_name''<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Xephyr ==<br />
<br />
You can make Xephyr run fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
== From within Sugar ==<br />
Once you have Sugar running, here are some useful commands (these are not specific to sugar-jhbuild or sugar-emulator, but work in all Sugar sessions):<br />
<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
== Customize ==<br />
<br />
To customize the build you can modify the configuration file named <code>sugar.jhbuildrc</code> or create a copy of it and pass <code>--file /path/to/your/new/config</code> to sugar-jhbuild.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
== Compiling using 2 or more CPU cores ==<br />
<br />
Before running <code>./sugar-jhbuild build</code>, append this to <code>sugar.jhbuildrc</code>:<br />
<br />
<pre><br />
os.environ["MAKEFLAGS"] = "-j4 -l4"<br />
</pre><br />
<br />
Adjust the numbers to be twice the number of CPU cores in your machine.<br />
<br />
== Using ccache to speed up rebuilds ==<br />
<br />
To speed up full rebuilds of sugar-jhbuild (i.e. running <code>./sugar-jhbuild build</code> after removing the <code>source</code> directory) you can use [http://ccache.samba.org/ ccache]. Install it and append the following to <code>sugar.jhbuildrc</code>:<br />
<br />
<pre><br />
os.environ["CCACHE_DIR"] = os.path.join(os.path.dirname(__file__), "ccache")<br />
os.environ["PATH"] = "/usr/lib/ccache:"+os.environ["PATH"]<br />
</pre><br />
<br />
Adjust <code>/usr/lib/ccache</code> to the path used by your distribution and create the <code>ccache</code> directory (inside your <code>sugar-jhbuild</code> checkout).<br />
<br />
== Building specific version of Sugar ==<br />
<br />
To build a specific version of Sugar do the following:<br />
<br />
* Open ''sugar.jhbuildrc'' and find line:<br />
<pre>modulesets = 'sugar'</pre><br />
* Set this to:<br />
<pre>modulesets = 'sugar-0.86'</pre><br />
customizing the latter to your specific needs.<br />
* Copy ''sugar.jhbuildrc'' to ''~/.jhbuildrc''<br />
* <code>./sugar-jhbuild</code><br />
<br />
=== Suggestions === <br />
<br />
* Copy all your sugar-jhbuild to sugar-jhbuild-0.84 (for example) or check the repositories out again.<br />
* <code>rm -r install source/</code><br />
* If you want to keep the <code>source</code> directory to save bandwidth, you need to be extra careful: delete all unpacked tarballs and cleanup all git repositories with <code>git clean -d -a</code>.<br />
* Don't forget to delete or modify ''.jhbuildrc'' after building the specific version of Sugar if you still want to receive the latest updates from the repositories, '''OR'''<br />
* Create another user.<br />
<br />
==Useful Internal Links==<br />
* [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
<br />
<br />
== Known issues==<br />
<br />
==known issue with hulahop ===<br />
<br />
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick&diff=54636Sugar on a Stick2010-07-23T05:46:21Z<p>MartinDengler: TOC pushes pancake button "below the fold"</p>
<hr />
<div><noinclude><!--{{ Translations | [[Sugar_on_a_Stick|english]] &#124; [[Sugar_on_a_Stick/lang-es|español]] &#124; [[Sugar_on_a_Stick/lang-fr|français]]}}--><br />
[[Category:Project]]<br />
[[Category:Live USB]]<br />
[[Category:Sugar on a Stick]]<br />
</noinclude><br />
<br />
== What is Sugar on a Stick? ==<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.'''<br />
<br />
'''Turn your computer into a Sugar on a Stick Creation Station:''' A related project is the [[Sugar Creation Kit]], a downloadable DVD which includes the materials you need to create Mirabelle sticks and install additional Activities on it, along with documentation and previous versions of Sugar on a Stick.<br />
|}<br />
<br />
__NOTOC__<br />
<br />
=== Want to use Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
|-<br />
|<br />
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]<br />
|-<br />
|<br />
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.<br />
<br />
After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.<br />
|}<br />
<br />
=== Want to contribute to Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]<br />
| style="border: 0; border-width: 0;" |<br />
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.<br />
|}<br />
<br />
== New contributors start here! ==<br />
<br />
Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].<br />
<br />
== What can you do? ==<br />
<br />
There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].<br />
<br />
=== Get Activities on the Stick ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:<br />
<br />
* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''<br />
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''<br />
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''<br />
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''<br />
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''<br />
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].<br />
<br />
| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]<br />
|}<br />
<br />
=== Get Sticks into Schools ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]<br />
| style="border: 0; border-width: 0;" | <br />
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.<br />
<br />
Some things you can do to help:<br />
<br />
* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!<br />
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].<br />
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.<br />
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.<br />
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.<br />
|}<br />
<br />
=== Get Contributors ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.<br />
<br />
Some things you can do:<br />
<br />
* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!<br />
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/<br />
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.<br />
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).<br />
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!<br />
<br />
| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]<br />
|}<br />
<br />
== What's happening? ==<br />
<br />
=== Meetings ===<br />
<br />
We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.<br />
<br />
=== Release schedule ===<br />
<br />
Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].<br />
<br />
{|border="1" cellspacing="0" width="100%"<br />
|-<br />
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released<br />
|-<br />
| Planning & Development Begins<br />
|-<br />
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)<br />
|-<br />
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-08-17 || Alpha Release<br />
|-<br />
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-09-21 || Beta Release<br />
|-<br />
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)<br />
|-<br />
| 2010-10-14 || Compose Release Candidate<br />
|-<br />
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release<br />
|-<br />
|}<br />
<br />
=== Contributor stories ===<br />
<br />
To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].<br />
<br />
== Related work ==<br />
<br />
While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)<br />
<br />
* [[Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle|Introduction to Mirabelle]]<br />
* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access<br />
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.<br />
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.<br />
<br />
== Previous versions and subpage index ==<br />
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick}}}}</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Talk:More_robust_iso&diff=53371Talk:More robust iso2010-06-17T09:41:54Z<p>MartinDengler: </p>
<hr />
<div>[http://puredyne.org/ Puredyne] seems to do what we are looking for ([http://bazaar.launchpad.net/~puredyne-team/bouilloncube/devel/annotate/head:/sh/syslinux/make-live-device.sh make-live-device.sh script]).<br />
<br />
Yup - we did it for Blueberry, too:<br />
<br />
http://cgit.sugarlabs.org/soas/mainline/tree/livecd-iso-to-bootable-tree.sh?h=blueberry<br />
http://cgit.sugarlabs.org/soas/mainline/tree/bootable-tree-to-fulldisk-img.sh?h=blueberry<br />
http://cgit.sugarlabs.org/soas/mainline/tree/make_fake_device.sh?h=blueberry<br />
<br />
We also need to worry about the cyl/head data in the MBR:<br />
<br />
<pre><br />
00:15 < bernie> dsd_, mtd: apparently, these numbers where on some crap consumer media like the iomega zip and bios writers of course felt the urge to hard-code the parameters of these devices in their boot code<br />
00:16 < bernie> dsd_, mtd: the bios reads the partition table to tell the difference between USB-ISO, USB-Floppy and USB-HD<br />
00:16 < dsd_> alright, a USB oddity then<br />
00:17 < bernie> because the ISO fs skips the first 2KB and the floppy and hd layouts can be intermixed with some clever tricks, there are tools around to create bootable USB sticks that work with all 3 methods<br />
00:18 < bernie> but they told me that some stupid bioses which would boot fine from USB-HD will be tricked into trying, say, the ISO way and then choke at some later steps.<br />
</pre></div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Talk:More_robust_iso&diff=53370Talk:More robust iso2010-06-17T09:39:22Z<p>MartinDengler: </p>
<hr />
<div>[http://puredyne.org/ Puredyne] seems to do what we are looking for ([http://bazaar.launchpad.net/~puredyne-team/bouilloncube/devel/annotate/head:/sh/syslinux/make-live-device.sh make-live-device.sh script]).<br />
<br />
Yup - we did it for Blueberry, too:<br />
<br />
http://cgit.sugarlabs.org/soas/mainline/tree/livecd-iso-to-bootable-tree.sh?h=blueberry<br />
http://cgit.sugarlabs.org/soas/mainline/tree/bootable-tree-to-fulldisk-img.sh?h=blueberry<br />
http://cgit.sugarlabs.org/soas/mainline/tree/make_fake_device.sh?h=blueberry</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Release&diff=53334Development Team/Release2010-06-16T16:38:12Z<p>MartinDengler: make components of release cycle subheadings of the release cycle heading</p>
<hr />
<div><noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude><br />
{{TOCright}}<br />
== Goals and modules proposal ==<br />
<br />
At the beginning of each release [[:Category:Platform Cycle|cycle]], maintainers will work on a set of goals, document them and assign owners. See the upcoming stable release, [[{{Upcoming Stable Release}}/Roadmap]]. (These goals typically involve major interventions or the addition of new components, e.g., someone develops a speech engine specially for his mother tongue and wants it in Sugar. Hence, the process described below is primarily for module maintainers. If you are a developer with a feature or bug fix, you may want to refer to the [[Features/Feature Template|new feature process]].)<br />
<br />
=== New modules proposal ===<br />
<br />
The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following information:<br />
<br />
(See [[Features/Feature Template]].)<br />
<br />
* Short description of the features.<br />
* Screenshots or screencasts.<br />
* Are you willing to follow the [[Development Team/Release/Roadmap#Schedule|Schedule]]?<br />
* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)<br />
* System components the activity depends on.<br />
* Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web.<br />
* Status of internationalization.<br />
* Code repository.<br />
* Bug tracking system.<br />
* Homepage.<br />
<br />
Criteria for approval will be:<br />
<br />
* Supports internationalisation and localisation.<br />
* Does not duplicate the functionalities of other activities.<br />
* Provide functionality that the community judges as important for reaching the goals of the project.<br />
* Maintainer responsiveness and willingness to provide regular releases. <br />
<br />
<!-- Not required but preferred:<br />
<br />
* Use the Sugar Labs infrastructure. --><br />
<br />
== Module release ==<br />
<br />
For both intermediates and final releases module maintainers are responsible to announce the module release and make the sources available. Note that the release number of the module does not need to match the Sucrose release number.<br />
More in detail:<br />
<br />
=== Glucose ===<br />
* Build a source tarball <br />
<br />
make distcheck<br />
<br />
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).<br />
<br />
* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is: <br />
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/ <br />
which translates to: <br />
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/ <br />
<br />
* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.<br />
<br />
=== Fructose ===<br />
* Build a source tarball<br />
If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.<br />
<br />
python setup.py dist_source<br />
<br />
The tarball will be generated inside the dist directory.<br />
<br />
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).<br />
<br />
* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. <br />
<br />
The preferred location for fructose components is: <br />
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/ <br />
which translates to: <br />
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/ <br />
<br />
* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.<br />
<br />
=== Using the release script ===<br />
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.<br />
<br />
You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):<br />
<br />
./release --help<br />
<br />
== Sugar release cycle==<br />
<br />
Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:<br />
<br />
* Ensure that all the module releases are available by the scheduled date.<br />
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.<br />
* If issues arise coordinate with the relevant module maintainers to solve them.<br />
* Announce the release on sugar-devel@lists.sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.<br />
<br />
=== Roadmap Update ===<br />
<br />
The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:<br />
<br />
* Detailed schedule of release dates and freeze points.<br />
* List of modules and external dependencies.<br />
* Reference to all the tickets considered for the release.<br />
* References to the new feature proposals.<br />
<br />
=== Feature freeze ===<br />
No new modules or features will be accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.<br />
<br />
This allows developers to concentrate on refining the new features instead of adding yet more functionality. <br />
<br />
The feature freeze affects all the modules included in the release and comprise also ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], referencing the patches you would like to land. It will have to be granted by two [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.<br />
<br />
=== UI Freeze ===<br />
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.<br />
<br />
This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated. <br />
<br />
If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.<br />
<br />
=== String cooling===<br />
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [[http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.<br />
<br />
=== String Freeze===<br />
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.<br />
<br />
=== Stabilizing ===<br />
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:<br />
|TestCase|<br />
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.<br />
<br />
=== Hard code freeze ===<br />
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[Development Team/Release/Contacts#People|members]] of the team.<br />
<br />
=== Branching ===<br />
<br />
After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.<br />
<br />
A new branch is created on the Pootle server, e.g., Fructose-0.82 and Fructose-0.84. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.<br />
<br />
You can create a remote branch like this (in your repository):<br />
<br />
git branch sucrose-0.84<br />
git push origin sucrose-0.84<br />
<br />
And to work on it (in your repository):<br />
<br />
git checkout -b sucrose-0.84 origin/sucrose-0.84<br />
git pull<br />
<br />
<br />
== Bug triaging ==<br />
<br />
Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.<br />
<br />
Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases.<br />
<br />
== Automation ==<br />
<br />
TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.<br />
<br />
==Subpages==<br />
{{Special:PrefixIndex/{{PAGENAME}}/}}<br />
See [[:Category:Release Notes]]<br />
[[Category:Development Team/Release]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Release&diff=53333Development Team/Release2010-06-16T16:35:55Z<p>MartinDengler: Sugar release -> Sugar release cycle</p>
<hr />
<div><noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude><br />
{{TOCright}}<br />
== Goals and modules proposal ==<br />
<br />
At the beginning of each release [[:Category:Platform Cycle|cycle]], maintainers will work on a set of goals, document them and assign owners. See the upcoming stable release, [[{{Upcoming Stable Release}}/Roadmap]]. (These goals typically involve major interventions or the addition of new components, e.g., someone develops a speech engine specially for his mother tongue and wants it in Sugar. Hence, the process described below is primarily for module maintainers. If you are a developer with a feature or bug fix, you may want to refer to the [[Features/Feature Template|new feature process]].)<br />
<br />
=== New modules proposal ===<br />
<br />
The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following information:<br />
<br />
(See [[Features/Feature Template]].)<br />
<br />
* Short description of the features.<br />
* Screenshots or screencasts.<br />
* Are you willing to follow the [[Development Team/Release/Roadmap#Schedule|Schedule]]?<br />
* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)<br />
* System components the activity depends on.<br />
* Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web.<br />
* Status of internationalization.<br />
* Code repository.<br />
* Bug tracking system.<br />
* Homepage.<br />
<br />
Criteria for approval will be:<br />
<br />
* Supports internationalisation and localisation.<br />
* Does not duplicate the functionalities of other activities.<br />
* Provide functionality that the community judges as important for reaching the goals of the project.<br />
* Maintainer responsiveness and willingness to provide regular releases. <br />
<br />
<!-- Not required but preferred:<br />
<br />
* Use the Sugar Labs infrastructure. --><br />
<br />
== Module release ==<br />
<br />
For both intermediates and final releases module maintainers are responsible to announce the module release and make the sources available. Note that the release number of the module does not need to match the Sucrose release number.<br />
More in detail:<br />
<br />
=== Glucose ===<br />
* Build a source tarball <br />
<br />
make distcheck<br />
<br />
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).<br />
<br />
* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is: <br />
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/ <br />
which translates to: <br />
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/ <br />
<br />
* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.<br />
<br />
=== Fructose ===<br />
* Build a source tarball<br />
If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.<br />
<br />
python setup.py dist_source<br />
<br />
The tarball will be generated inside the dist directory.<br />
<br />
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).<br />
<br />
* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. <br />
<br />
The preferred location for fructose components is: <br />
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/ <br />
which translates to: <br />
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/ <br />
<br />
* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.<br />
<br />
=== Using the release script ===<br />
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.<br />
<br />
You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):<br />
<br />
./release --help<br />
<br />
== Sugar release cycle==<br />
<br />
Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:<br />
<br />
* Ensure that all the module releases are available by the scheduled date.<br />
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.<br />
* If issues arise coordinate with the relevant module maintainers to solve them.<br />
* Announce the release on sugar-devel@lists.sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.<br />
<br />
== Feature freeze ==<br />
No new modules or features will be accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.<br />
<br />
This allows developers to concentrate on refining the new features instead of adding yet more functionality. <br />
<br />
The feature freeze affects all the modules included in the release and comprise also ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], referencing the patches you would like to land. It will have to be granted by two [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.<br />
<br />
== UI Freeze ==<br />
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.<br />
<br />
This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated. <br />
<br />
If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.<br />
<br />
== String cooling==<br />
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [[http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.<br />
<br />
== String Freeze==<br />
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.<br />
<br />
== Stabilizing ==<br />
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:<br />
|TestCase|<br />
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.<br />
<br />
== Hard code freeze ==<br />
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[Development Team/Release/Contacts#People|members]] of the team.<br />
<br />
== Branching ==<br />
<br />
After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.<br />
<br />
A new branch is created on the Pootle server, e.g., Fructose-0.82 and Fructose-0.84. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.<br />
<br />
You can create a remote branch like this (in your repository):<br />
<br />
git branch sucrose-0.84<br />
git push origin sucrose-0.84<br />
<br />
And to work on it (in your repository):<br />
<br />
git checkout -b sucrose-0.84 origin/sucrose-0.84<br />
git pull<br />
<br />
== Roadmap ==<br />
<br />
The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:<br />
<br />
* Detailed schedule of release dates and freeze points.<br />
* List of modules and external dependencies.<br />
* Reference to all the tickets considered for the release.<br />
* References to the new feature proposals.<br />
<br />
== Bug triaging ==<br />
<br />
Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.<br />
<br />
Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases.<br />
<br />
== Automation ==<br />
<br />
TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.<br />
<br />
==Subpages==<br />
{{Special:PrefixIndex/{{PAGENAME}}/}}<br />
See [[:Category:Release Notes]]<br />
[[Category:Development Team/Release]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Release/Modules&diff=53331Development Team/Release/Modules2010-06-16T16:32:20Z<p>MartinDengler: change lists to tables</p>
<hr />
<div><noinclude>{{TOCright}}</noinclude><br />
<br />
See also [[:Category:Platform Cycle]].<br />
<br />
== Glucose ==<br />
<br />
Bug Tracking: http://bugs.sugarlabs.org/<br />
<br />
Home page: http://sugarlabs.org/<br />
<br />
{| class="wikitable"<br />
|-<br />
!Module<br />
!Lead Maintainer<br />
!Co-maintainers<br />
!Code Repository<br />
|-<br />
|sugar<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [[User:Alsroot|Aleksey Lim]] (Journal)<br />
|[[User:Erikos|Simon Schampijer]] <br> [[User:MartinDengler|Martin Dengler]]<br />
|http://git.sugarlabs.org/projects/sugar<br />
|-<br />
|sugar-base<br />
|[[User:Erikos|Simon Schampijer]]<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [[User:MartinDengler|Martin Dengler]]<br />
|http://git.sugarlabs.org/projects/sugar-base<br />
|-<br />
|sugar-datastore<br />
|[[User:Alsroot|Aleksey Lim]]<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [[User:sascha_silbe|Sascha Silbe]]<br />
|http://git.sugarlabs.org/projects/sugar-datastore<br />
|-<br />
|sugar-presence-service<br />
|[[User:Tomeu|Tomeu Vizoso]]<br />
|[[User:Cassidy|Guillaume Desmottes]]<br />
|http://git.sugarlabs.org/projects/sugar-presence-service<br />
|-<br />
|sugar-toolkit<br />
|[[User:Erikos|Simon Schampijer]]<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [[User:MartinDengler|Martin Dengler]] <br> [[User:Alsroot|Aleksey Lim]]<br />
|http://git.sugarlabs.org/projects/sugar-toolkit<br />
|-<br />
|sugar-artwork<br />
|[[User:BenjaminBerg|Benjamin Berg]]<br />
|[[User:Erikos|Simon Schampijer]] <br> [[User:Garycmartin|Gary C. Martin]]<br />
|http://git.sugarlabs.org/projects/sugar-artwork<br />
|-<br />
|hulahop<br />
|unmaintained<br />
|[[User:Tomeu|Tomeu Vizoso]]<br />
|http://git.sugarlabs.org/projects/hulahop<br />
|}<br />
<br />
== Fructose ==<br />
<br />
{| class="wikitable"<br />
|-<br />
!Module<br />
!Lead Maintainer<br />
!Co-maintainers<br />
!Code Repository<br />
!Release tarballs<br />
!Bug Tracking<br />
!Home page<br />
|-<br />
|chat<br />
|[[User:Alsroot|Aleksey Lim]]<br />
|<br />
|http://git.sugarlabs.org/projects/chat<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Chat<br />
|-<br />
|browse<br />
|[[User:Lucian|Lucian Branescu Mihaila]], [[User:sascha_silbe|Sascha Silbe]]<br />
|[[User:Tomeu|Tomeu Vizoso]]<br />
|http://git.sugarlabs.org/projects/browse<br />
|<br />
|[https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=Browse bugs.sl.o]<br />
|http://wiki.laptop.org/go/Browse<br />
|-<br />
|read<br />
|[http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [[User:Erikos|Simon Schampijer]]<br />
|http://git.sugarlabs.org/projects/read<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Read<br />
|-<br />
|calculate<br />
|Reinier Heeres<br />
|<br />
|http://git.sugarlabs.org/projects/calculate<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Calculate<br />
|-<br />
|log<br />
|unmaintained<br />
|[http://edsiper.linuxchile.cl Eduardo Silva] <br> [[User:Alsroot|Aleksey Lim]]<br />
|http://git.sugarlabs.org/projects/calculate<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]<br />
|http://wiki.laptop.org/go/Log<br />
|-<br />
|write<br />
|[http://uwog.net/ J.M. Maurer]<br />
|[http://msevior.livejournal.com/ Martin Sevior] <br> [[User:Tomeu|Tomeu Vizoso]]<br />
|http://git.sugarlabs.org/projects/write<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Write<br />
|-<br />
|terminal<br />
|[http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
|[[User:Tomeu|Tomeu Vizoso]] <br> [http://edsiper.linuxchile.cl Eduardo Silva] <br> [[User:Wade|Wade Brainerd]]<br />
|http://git.sugarlabs.org/projects/terminal<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Terminal<br />
|-<br />
|pippy<br />
|[[User:Bjordan|Brian Jordan]]<br />
|[[User:Cjb|Chris Ball]] <br> [http://cscott.net C. Scott Ananian]<br />
|http://git.sugarlabs.org/projects/pippy<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Pippy<br />
|-<br />
|etoys<br />
|[[User:Bert|Bert Freudenberg]]<br />
|Squeakland developers<br />
|http://dev.laptop.org/git/projects/etoys/ and http://etoys.laptop.org/svn/trunk/etoys/<br />
|http://download.sugarlabs.org/sources/sucrose/glucose/etoys/<br />
|http://tracker.squeakland.org/<br />
|http://www.squeakland.org/<br />
|-<br />
|etoys-activity<br />
|[[User:Bert|Bert Freudenberg]]<br />
|Squeakland developers<br />
|http://dev.laptop.org/git/projects/etoys/<br />
|http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/<br />
|http://tracker.squeakland.org/<br />
|http://wiki.laptop.org/go/Etoys<br />
|-<br />
|imageviewer<br />
|[http://sayamindu.randomink.org/ Sayamindu Dasgupta]<br />
|None<br />
|http://git.sugarlabs.org/projects/imageviewer<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Image_Viewer<br />
|-<br />
|jukebox<br />
|[http://kushaldas.in Kushal Das]<br />
|None<br />
|http://git.sugarlabs.org/projects/jukebox<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|http://wiki.laptop.org/go/Jukebox<br />
|-<br />
|turtleart<br />
|[[User:Walter|Walter Bender]]<br />
|Raúl Gutiérrez Segalés<br />
|http://git.sugarlabs.org/projects/turtleart<br />
|<br />
|[http://bugs.sugarlabs.org bugs.sl.o]/<br />
|[[Activities/Turtle Art]]<br />
|}</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=The_Undiscoverable&diff=53289The Undiscoverable2010-06-15T13:49:48Z<p>MartinDengler: reference FLOSS manuals more prominently.</p>
<hr />
<div><noinclude>{{TOCright}}</noinclude><br />
<br />
Some ideas are not easy to discover; the concept of guided [[discovery]], where a mentor helps point a learner in a fruitful direction, can accelerate the pace of learning. Some Sugar features are not easy to discover and while we are working to improve upon this, we provide some guides to discovery below.<br />
<br />
If possible, rather than adding to the below list, the official documentation at <br />
[http://www.flossmanuals.net/ FLOSS Manuals] should be updated instead (it's a wiki, too).<br />
<br />
No matter how well we do in making Sugar discoverable, there are necessarily some things that even a born lever-puller and button-clicker will not find easily, or will not understand fully. This page contains a list of such things, ranging from the almost but not quite obvious to the entirely opaque. We can consider whether some of these can be improved, but we know that there is a limit. So we have to alert teachers to these issues, and assist them to alert the children.<br />
<br />
Nothing is 100% discoverable or 100% undiscoverable. There are many features of Sugar that can be discovered, without their use cases being in any way obvious. The question, then, is how to provide discovery projects where we know that a particular usage is appropriate, and include a hint on the feature in the lesson plan. In other cases, the children understand immediately what a function is for, as soon as they know it exists. In those cases, you generally don't have to show them twice.<br />
<br />
Many things that would not be discovered by one individual before getting frustrated will be rapidly discovered by one child in the group and shared before any of the group get frustrated. In teaching science, Alan Kay calls this a "Galileo moment". Is this an an adequate standard of discoverability for software, or should features be discoverable by a child in isolation? Where they are not, we want teachers to know that, and we want to plan accordingly.<br />
<br />
Many of the Activities would benefit from a Help feature.<br />
<br />
We should probably create a subpage for each of these issues, or point to an existing Wiki page that has the information.<br />
<br />
Again, all of these items should be clearly documented and even specially called out in the [http://www.flossmanuals.net/ FLOSS Manuals] Sugar and XO documents.<br />
<br />
==Sugar UI==<br />
<br />
* Views: Neighborhood, Friends, Home, current Activity<br />
<br />
* Wireless mesh channels and access points<br />
<br />
==Icon colors and user names==<br />
:Personalized icons? Drawings? Pictures? How can kids make their own icon? It's a surprisingly big thing to est. an iconic identity for many... just look at forums where kids(and adults!) hang out.--[[User:Dennis Daniels|Dennis Daniels]] 16:13, 4 August 2009 (UTC)<br />
<br />
==Search wireless connections and people by name==<br />
Easier to find your friend if you recognize their icon. --[[User:Dennis Daniels|Dennis Daniels]] 16:15, 4 August 2009 (UTC)<br />
<br />
==Right-click/hover menus==<br />
Point to an icon and wait a second for its name to appear. Wait a bit longer for the accompanying menu to appear. Or, without having to wait, just right-click (o-button on an XO) to see the name and menu.<br />
::Nice if view source was there too. --[[User:Dennis Daniels|Dennis Daniels]] 16:15, 4 August 2009 (UTC)<br />
<br />
==Activities==<br />
In home view (hotkey F3), there are buttons to switch between the view of favorites in a ring and a list of all installed Activities. Select the star by an Activity to make it a Favorite. The hover menu for a Favorite includes the option to remove it from favorites without deleting it, and also an Erase option which deletes that activity! <br />
::For a school admin trying to keep machines uniform for the next wave of kids to descend upon the computer lab the erase key can pose problems, right? --[[User:Dennis Daniels|Dennis Daniels]] 16:08, 4 August 2009 (UTC)<br />
* Frame: Views and Activities on top; Friends on the right; hardware on the bottom; open documents on the left.<br />
<br />
* [[The undiscoverable/Collaboration|Collaboration]]<br />
<br />
* Use of Keep button: Keep places a checkpoint of the current state of your application in the Journal, including a screen shot, Activity state, and metadata. The user can rename the session from the name of the Activity to something specific to the session, and add a description and tags. Users do not agree on why and when to use Keep.<br />
<br />
===Screen capture===<br />
An important use case for the Keep button. How do we store just the image, without the software state? Some Activities, including Turtle Art, have a button for this purpose. <br />
*: <Alt> + 1 captures the screen and stores a screenshot in the Journal. <br />
<br />
===View source?===<br />
Not fully implemented. On the menu in several applications.<br />
<br />
:What's the hotkey to view source? Is there a hotkey to view the log for that specific acitivity?--[[User:Dennis Daniels|Dennis Daniels]] 16:10, 4 August 2009 (UTC)<br />
<br />
* Copy and paste between activities? (Sometimes)<br />
<br />
===How to quit an activity===<br />
''Most'' activities have a "stop-sign" icon under the Activity Tab on the toolbar at the top of the screen. (GCompris activities have a "exit-door" icon in the toolbar on the bottom of the screen. Some other activities may have a quit menu item.) ''Every'' activity has Stop in the hover menu associated with the Activity icon in the Frame.<br />
<br />
::Not all activities respond to the 'stop-sign' especially when there are system/activity crashes caused by bugs. How do users and teachers(!) kill _that_ activity?--[[User:Dennis Daniels|Dennis Daniels]] 16:09, 4 August 2009 (UTC)<br />
<br />
* Start an Activity without resuming last session: Select Start from hover menu.<br />
<br />
===Sugar-Emulator Screen Size Adjustment===<br />
* In terminal:<br />
sugar-emulator -i 600x500 fits the screen for a 10" Netbook<br />
* Help for Sugar-Emulator<br />
sugar-emulator --help<br />
<br />
* for a permanent solution Applications/Education/sugar<br />
<right click><add launcher to desktop><br />
*right click on icon on desktop<br />
*Properties/Command:/usr/bin/sugar-emulator '''-i 600x500'''<br />
*close<br />
<br />
*now the icon will start the smaller Xephyr window<br />
<br />
===Localization===<br />
* [[The undiscoverable/Change keyboard|Change keyboard]]<br />
<br />
* [[The undiscoverable/Change UI language|Change UI language]]<br />
<br />
* [[The undiscoverable/Fonts|Fonts]]<br />
<br />
=== Remote collaboration ===<br />
Using Community Jabber servers (Listings and how to change):<br />
* [OLPC:Community_Jabber_Servers OLPC Community Jabber servers]<br />
<br />
* [[Community Jabber servers|local display of the OLPC Community Jabber servers]]<br />
* see Terminal listing below for how to change<br />
<br />
==Icons==<br />
<br />
Although there is no such thing as an intuitive icon, it is sometimes possible to use icons that relate to experience, and it is generally possible to make icons mnemonic, so that they don't have to be explained more than once. Note that the common icon for saving a file in GUIS for Linux, Mac, and Windows is the obsolete floppy disk. A billion people have learned it, so it has become almost unchangeable. We have started over in Sugar.<br />
<br />
* File types. <br />
* InfoSlicer<br />
<br />
==Journal==<br />
<br />
* The default text in each entry is the name of the Activity used to create it, or the name of a downloaded file. Users can edit this text to provide a meaningful title. The Description does not display in the main Journal view. Renamed sessions saved in the Journal show up on the right-click/hover menu for that Activity's icon in the Home view.<br />
<br />
* Tags: Poor man's database. You can tag by topic, by project, or whatever else meets your needs.<br />
<br />
* Searches examine the unnamed Title field, the Description, and the Tags texts. You don't have to examine entries one at a time to look for particular tags.<br />
<br />
* Resume session: Left-click a Journal entry to start where you left off the last time. Right-click to get the list of Activities that can open this file. Save in Record, open in Paint, for example.<br />
<br />
* Install Activities: Cannot install .xo over yum package. Delete Activity from /usr/share/sugar/activities, then download .xo from [http://activities.sugarlabs.org Activities repository]. Where is the result installed?<br />
<br />
* Copy to and from USB stick: Drag Journal entries to USB icon.<br />
<br />
* Copy file to Journal entry. With the appropriate file name and MIME type: <br />
copy-to-journal tamyblock.py -m text/x-python<br />
<br />
* When you download an image, it doesn't have a preview. Open it and close it immediately to generate one. [http://dev.sugarlabs.org/ticket/1106 Ticket #1106]<br />
===Saving Work===<br />
<br />
Basically, we need a Save as... functionality, not just a Save that overwrites the previous version and a clumsy Save on Exit where you have to go roundabout to start up again. All of this should be bugged as a Feature Request.<br />
<br />
<pre>On Thu, Oct 8, 2009 at 6:42 PM, Caroline Meeks <caroline@solutiongrove.com> wrote:<br />
> Today we worked with two groups on multiplication. They made squares with<br />
> each side being a different multiplication problem that had the same answer.<br />
> http://screencast.com/t/sUbiof2H<br />
><br />
> We also had them reflect in their Journals about what they did. <br />
> All of this went well.<br />
><br />
> What was horrible was trying to get the right point in the project saved to<br />
> the Journal and then navigating to the correct place to write.<br />
> The solution I suggest is when you click the Keep button (Journal Icon) from<br />
> an activity that the Journal reflection dialog box appears.<br />
> Here are the problems we had.<br />
><br />
> Hard to get to the Journal, no easy F# short cut.<br />
> Hard to find the little arrow that gets you to where you can write.<br />
> Especially since if the Frame is active, which it has to be to get to the<br />
> Journal, the little bitty arrow you need to click is covered.<br />
> When students did their assigned task they were eager to go back to<br />
> exploring with Sugar and wrote over their work without it being saved, or<br />
> using the same name as the assigned activity. This was probably the worst<br />
> outcome because then it was like they hadn't done the assignment, they had<br />
> nothing to show for their work and we'll want to use it later for a<br />
> portfolio.<br />
><br />
> clicking the Activity Tab to write down the name is a PITA (this one is<br />
> fixed in .88 I think).<br />
><br />
> After they reflected they wanted to immediately go back to exploring in TA<br />
> and we had to stop them, make them change the name again. They were very<br />
> perplexed by this because they didn't know what to name their new file<br />
> because they hadn't done anything yet.<br />
><br />
> The word "Description" is not very friendly. I like "What did you do?"<br />
> Walter wants to expand it even further, I'm not sure about that, its pretty<br />
> challenging for the students to type so I'm not sure we want more boxes.<br />
> Confusion between the Keep button and the samples and the snapshot icons.<br />
> No feedback when you click Keep so there is a tendency to click it<br />
> repeatedly.<br />
</pre><br />
<br />
==Activities==<br />
<br />
* What version of this activity am I running? The list view in Home gives the number.<br />
* Add and Remove Favorites. WARNING: Erase is '''not''' Remove Favorite.<br />
<br />
===[http://wiki.laptop.org/go/Xo-get xo-get]===<br />
<br />
The obsolete xo-get script and Activity accessed a repository of Activities for installation and updates. Use [http://Activities.sugarlabs.org/ Activities.sugarlabs.org] instead.<br />
<br />
* [http://wiki.laptop.org/go/Xo-get#Installation_of_xo-get Script] [http://xo-get.olpc.at/xo-get.py Download] <br />
* [http://wiki.laptop.org/go/Xo-get#Installation_of_xo-get_GUI Activity]<br />
<br />
===Terminal===<br />
<br />
* XO laptop keyboard sends screen the "erase" key as the ascii code NULL (back erases) and sees "fn+erase" as code DEL (forward erase)<br />
* The entire [[The undiscoverable/Command line|command line]] repertoire plus scripting<br />
* Documentation: man, info, apropos<br />
* Linux file system: /, ., .., cd, pwd, mkdir, rmdir, cat, touch, rm, mount, umount, /etc/fstab<br />
* Standard IO: >, >>, <, |<br />
* Users and groups: root, /home, su, sudo, /etc/sudoers, sudoedit, visudo, chown<br />
* Permissions: chmod drwxrwxrwx ugoa<br />
* Regular expressions: [0-9][a-zA-Z]?, grep<br />
* File globbing: *<br />
* Editors: vi, pico. The emacs editor is not installed by default.<br />
* copy-from-journal copy-to-journal: Journal entries are in ~/.sugar/default/datastore. Each entry has a metadata subdirectory.<br />
* sugar-control-panel command: (aboutme/network/datetime/aboutcomputer/Frame/power/language) settings. Use this command (small L) to list available functions.<br />
sugar-control-panel -l <br />
* File browser: Install Midnight Commander (mc)<br />
<br />
See FLOSS Manuals [http://en.flossmanuals.net/CommandLineIntro/AboutThisManual Introduction to the GNU/Linux Command Line] for a gentle introduction to these functions and features<br />
<br />
===Etoys===<br />
<br />
* It's a programming language.<br />
* It's huge.<br />
* The tutorials are excellent as far as they go, but they stop short.<br />
* [[The undiscoverable/Projects|Projects]]? What are projects? How do I do that?<br />
* Program tiles<br />
* Make tile<br />
* Objects<br />
* Code viewer<br />
* Multimedia<br />
* Presentations<br />
<br />
===Pippy===<br />
<br />
* You can edit the programs and run the changed versions.<br />
* You can create your own programs. Click Clear, enter a Pythonic name to replace Pippy Activity, and Keep.<br />
* You can import libraries.<br />
* Turtle Art has a programmable tile that holds a single Python expression.<br />
* Turtle Art has a programmable tile that reads tamyblock.py. Right-click on it in the Journal to open it in Pippy.<br />
* Python is a large programming language. How do I learn it?<br />
* How do I tackle the [http://api.sugarlabs.org/ Sugar API]?<br />
* What is the difference between Keeping as a Python file and as a bundle?<br />
<br />
===Turtle Art===<br />
<br />
* Color space: The image below shows the colors that the Turtle draws for inputs in the range 0-399. The range repeats after 200. The 100-199 and 300-399 ranges are the reverse of the 0-99 and 200-299 ranges.<br />
[[File:TA_Colors.png]]<br />
* Shades: The image below shows all color and shade combinations in the ranges 0-99.<br />
[[File:TAShadesAndColors.png]]<br />
<br />
===Write===<br />
<br />
* When unformatted text is selected the Style menu appears with only one item visible: None. Unless the user notices the little up arrowhead and moves the cursor up to reveal the rest of the menu, Styles remain a mystery.<br />
* When text is selected, and the color palette opened, clicking outside the palette window dismisses the palette. Not a problem so far. However, if the user clicks in the edit window, the previously selected text is deselected and no color applied. Clicking anywhere on the toolbar applies the color and leaves the text selected. It has been suggested in [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg08918.html mailing list thread] that adding 'OK' and 'Cancel' buttons, as in the color palette in Paint, would solve this problem.<br />
<br />
===[[The undiscoverable/Calculate|Calculate]]===<br />
<br />
* Graphing<br />
* Help<br />
<br />
===Measure===<br />
<br />
* Frequency and amplitude settings<br />
<br />
===Library===<br />
<br />
* I'm sorry, what is this for? Oh, wait, is this what the Journal was supposed to be? No, it only shows one entry for each activity. I can't list individual sessions or documents. So what is it for?<br />
<br />
===Browse===<br />
<br />
* [[The undiscoverable/Bookmarks|Bookmarks]]<br />
* You can use browse to browse the file system and .py files<br />
* Uploading from Journal<br />
* [[wikipedia:About:config|about]]:config (Enter this in the address bar to see and set Browse configuration values, such as for [[olpc:Our software#Proxy configuration]])<br />
<br />
===Jukebox===<br />
<br />
* Where is the music?<br />
<br />
===IRC===<br />
* Change name: click on name in right bottom corner, edit, hit <enter><br />
* /join #''channel'' command<br />
<br />
*How to change the autologon channels on the XoIRC application in sugar:<br />
*in terminal enter gedit then open and edit the file ircactivity.py <br />
in .../Activities/IRC.activity subdirectory. ( install gedit with yum install.)<br />
*add "client.add-channel ('sugar') "lines with the different #channels <br />
inside quotes that you want to open on startup, Then save the changed file.<br />
Now autologon to those channels works on startup<br />
<br />
==Programming==<br />
<br />
We have activities for the Smalltalk, Python, and Logo languages. Etoys includes a different version of turtle graphics. We have to provide an appropriately graded curriculum on the basic concepts of programming, starting with simple actions, such as Turtle Art drawing commands. Then we have to deal with variables, subroutines, control flow, functions or methods, and so on up to object class definitions and libraries. The laptops also have FORTH and Perl installed, and we will want materials for those, starting no doubt in later grades.<br />
<br />
We also need to bring in the Computer Science idea that the deep structure of a program is not the surface syntax, but is much more like the trees that we build in Turtle Art.<br />
<br />
==Subject matter==<br />
<br />
Whether in math, science, music, art, or any other subjects, there is much that cannot be discovered in unguided exploration, that has taken thousands of years of human history to achieve. The chief task in building new learning materials will be discovering ways to structure learning to maximize the amount of discovery the children can achieve, with the minimum of direction.<br />
<br />
We also need to be clear about skills that need practice more than discovery, as in music and sports, or keyboarding or language. What is the proper balance? On this point, see Muska Mosston, The Spectrum of Teaching Styles: From Command to Discovery. Longman, 1989. ISBN 0801303508 (out of print)<br />
<br />
==Hardware==<br />
<br />
Sugar runs on hardware and there are some hardware specific interactions that can be difficult to discover. For example, the function keys (F1–F4) map to the Sugar zoom levels/neighborhood views. This mapping is evident on the OLPC XO-1 hardware, which has dedicated symbols on those keys, but not as easy to discover on generic keyboards. Similarly, there is a key dedicated to the Frame on the OLPC XO-1 keyboard. The Frame is accessed through a keyboard shortcut on a generic keyboard (Alt-F). Unfortunately, this shortcut does not work in [[SoaS]] in VirtualBox.<br />
<br />
Listed below are some of the undiscoverable features specific to hardware.<br />
<br />
===OLPC XO-1===<br />
<br />
* Power button: In many target countries, many will not be familiar with international symbols.<br />
* Left and right "mouse" buttons: Young children may have even more trouble with left and right than grownups. For this reason, the left button is marked 'x', and the right button, 'o'.<br />
* Opening: The latching mechanism is a hidden part of the antennae. Readily discoverable by children, but not by all adults, some of whom have to be shown more than once. This puzzle aspect of the XO is actually beneficial in some ways.<br />
* Position of antennae. They work better in a generally upright position, parallel to each other.<br />
* Rotate screen button: Easy to find, but what's it for?<br />
* Book reader mode and page controls: You also need to know about screen rotation to make this work properly.<br />
* Keyboard switching key, replacing ×÷ on keyboards for countries and languages using a non-Latin alphabet or other kind of writing system.<br />
* Keyboard sends screen the "erase" key as the ascii code NULL (back erase) and sees "fn+erase" as code DEL (forward erase).<br />
<br />
====Open Firmware====<br />
<br />
This is presently only relevant to OLPC XO hardware, which uses Open Firmware instead of a BIOS.<br />
<br />
On an unlocked XO,<br />
<br />
* At boot time, press and hold the escape key to get into Open Firmware.<br />
* In the Terminal activity, execute the command <br />
<br />
echo y > /proc/sysrq-trigger<br />
<br />
See [http://wiki.laptop.org/go/FORTH FORTH] for a brief introduction to the FORTH programming language, which Open Firmware is written in, plus links to other resources.<br />
<br />
Be careful with OFW. You can seriously mess up or brick your XO with it. You might want to experiment in gForth first.<br />
<br />
==Subpages==<br />
<br />
{{Special:PrefixIndex/{{PAGENAMEE}}/}}<br />
<br />
[[Category:Help]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=The_Undiscoverable/Change_keyboard&diff=53288The Undiscoverable/Change keyboard2010-06-15T13:49:16Z<p>MartinDengler: reference FLOSS manuals for changing the keyboard on more recent Sugar</p>
<hr />
<div>= Current Sugar =<br />
For Sugar installation from 2009, Sugar now has an easier way to change the keyboard layout that's discoverable from the Control Panel. See [http://en.flossmanuals.net/Sugar/Personalising Personalising Sugar].<br />
<br />
= Older Sugar =<br />
<br />
For the OLPC XO-1 sugar version: the XO can be set up for more than one writing system and locale. In this case, the ×÷ key may be replaced by a key to switch keyboards. This is essential in areas that have the same language written in different alphabets, notably India and Pakistan with Hindi in Devanagari and Urdu in Arabic. It is also essential in areas where more than one official language is in use, and they are written in different alphabets. Again, India is the leading case, with 22 official ("Scheduled") languages written in 10 different alphabets. <br />
<br />
Instructions for configuring the ×÷ to switch between two languages, or cycle between more than two, are provided at [http://wiki.laptop.org/go/Customizing_NAND_images#Keyboard Customizing NAND images#Keyboard]. This procedure is not intended for end users, since it requires editing system configuration files.<br />
<br />
Whether or not there is such a key on a particular XO, it cannot support all of the languages, writing systems, and keyboard layouts that may be desired. Thus it is necessary to know how to change keyboards by other means. In Terminal, the command<br />
<br />
setxkbmap dvorak<br />
<br />
will change to a US Dvorak keyboard, and the command <br />
<br />
setxkbmap us<br />
<br />
will change to a US keyboard. [http://wiki.laptop.org/go/Keyboard_layouts Commands for other layouts] are provided in the OLPC Wiki. It is useful to make a script file to change back. Thus, one could have the files<br />
<br />
Name: aoeu<br />
<br />
#!/bin/bash<br />
setxkbmap us<br />
<br />
and <br />
<br />
Name: asdf<br />
<br />
#!/bin/bash<br />
setxkbmap dvorak<br />
<br />
where the names asdf and aoeu are typed on the same keys, at the left end of the home row.<br />
<br />
or, to go between US Latin and Russian Cyrillic,<br />
<br />
Name: ru<br />
<br />
#!/bin/bash<br />
setxkbmap ru<br />
<br />
Name: фыва<br />
<br />
#!/bin/bash<br />
setxkbmap us<br />
<br />
That way you will have a Cyrillic name, also typed at the left end of the home row, to get out of Cyrillic.</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Features/Revised_Browse_default-bookmarks.html&diff=53256Features/Revised Browse default-bookmarks.html2010-06-14T19:06:47Z<p>MartinDengler: /* UI Design */ page should not be changed without due consideration</p>
<hr />
<div><noinclude><br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature|<Feature Name>]]<br />
<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
*Point Sugar.Browse default "start new" screen to:<br />
file:///usr/share/bookmarks/default-bookmarks.html<br />
* "We'll use something slightly different so we don't conflict." pbrobinson <br />
<br />
<br />
*instead of sugars's default:<br />
file:///usr/share/sugar/activities/Browse.activity/data/index.html<br />
<br />
<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
mchua: I'm trying to get you to come up with a summary of the feature - not the implementation, but the feature itself.<br />
and then we'll start with that to figure out what needs to be done (codewise, maintainer-poking wise, etc) to accomplish what you want the feature to do.<br />
<br />
'''mchua: 2 ways to address it 1) improve the default browse page with a few well documented links that upstream agrees with 2) we do a custom default page that accomplishes the same but specifically for SoaS.<br />
This is a better idea of what I am trying to accomplish here satellit 06/14/2010'''<br />
<br />
mtd: a customizable start page exists. the best way to change that is not as simple as it may seem, since "best" means a lot of things. I think mchua is helping direct things constructively here.<br />
<br />
old concept:Point the "start new" default Browse start-up page to the page that is downloaded from fedora repository.'''fedora-bookmarks-13-1.noarch.rpm 5.4 kB''<br />
<br />
== Owner ==<br />
<br />
* Name: [[User:satellit|Tom Gilliard]]<br />
<br />
* Email: satellit@bendbroadband.com<br />
<br />
== Current status ==<br />
* Targeted release: SoaS_v4_Feature<br />
* Last updated: (06/12/2010)<br />
* Percentage of completion: 90%<br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#AN_ON-LINE_VERSION_OF_THE_DVD_: added links in anticipation of conversion to bookmarks.html write (06/11/2010)<br />
<br />
'''TESTING'''<br />
* Tested on sugar-emulator in f12 (file locations and names may be different in Soas)<br />
* copied file:///usr/share/bookmarks/default-bookmarks.html to desktop,<br />
* opened and edited with OooWriter<br />
* added hyperlinks and saved<br />
* renamed index.html<br />
* opened terminal<br />
su<br />
gedit<br />
*opened modified file<br />
*saved as file:///usr/share/sugar/activities/Browse.activity/data/index.html<br />
*Started "sugar-emulator" and Browse as "Start new" <br />
*took this screenshot:<br />
<br />
<br />
http://people.sugarlabs.org/Tgillard/Modified-default-bookmark.png<br />
<br />
<br />
==='''Change-Browse.activity index.html-to-use-Modified-Browse-html in a live USB'''===<br />
<br />
*In booted USB-soas-i386-20100611.15.iso:<br />
<br />
*In Sugar Terminal; <br />
su<br />
yum install wget<br />
wget http://people.sugarlabs.org/Tgillard/Modified-Browse.html<br />
cd /home/liveuser<br />
chmod 777 Modified-Browse.html<br />
cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html <br />
[root@localhost ~]# cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html<br />
cp: overwrite `/usr/share/sugar/activities/Browse.activity/data/index.html'? y<br />
[root@localhost ~]# <br />
<br />
'''It worked after this. Browse has a new "Start-New" screen. SUCCESS (06/12/2010)'''<br />
<br />
*'''Note: One step farther:'''<br />
su<br />
mkdir /usr/share/library-common<br />
cp /usr/share/sugar/activities/Browse.activity/data/index.html usr/share/library-common/index.html<br />
* Sets up Firefox v 6 .xo (experimental on ASLO) to use the same index.html as Browse uses.<br />
*On live USB Stick (06/13/2010)<br />
<br />
== Detailed Description ==<br />
'''In a discussion with Peter Robinson last night I discovered that a custom Browse bookmark can be downloaded from the fedora repository. I propose to use this "Feature" to allow a custom set of bookmarts to be maintained that would have a series of links ie: e-books; Floss Manuals; wiki.sugarlabs.org, all of the proposed links to files in SugarCreationKit DVD + The NormalBrowse Google Screen'''<br />
<br />
*This should be a simple edit in Browse to point to file:///usr/share/bookmarks/default-bookmarks.html instead of file:///usr/share/sugar/activities/Browse.activity/data/index.html. <br />
<br />
* Repointing the default-screen allows us to have fedora supply our revised "Start New" screen ( or maybe several depending on the deployment or schools requirements to Soas v4)<br />
<br />
===Current Example (see screen-shot above) works well as an Starting Screen=== <br />
*'''Contains the normal Browse links:'''<br />
*Home<br />
*Wiki<br />
*Bugs<br />
*Activites<br />
*'''plus'''<br />
*MENU- which points to an On line Version of the SugarCreationKit DVD, (with all of the links to the sources.)<br />
# CLICK THIS LINK TO TEST: http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#INDEX_OF_Soas_Features<br />
*'''AND'''<br />
*The fedora '''Personal Toolbar Folder''' with all of it's links<br />
<br />
<br />
<br />
*'''This Modified index-html needs to be customized by fedora and used for the build of the Browse.appliance in the v4 Soas-spin '''<br />
<br />
== Benefit to Sugar ==<br />
'''A simple enhancement to sugar.browse'''<br />
<br />
[[User:MartinDengler|MartinDengler]] 13:51, 14 June 2010 (EDT) In fact this is not an enhancement, it's a hack. The browse homepage should be made configurable (perhaps via gconf) and have a sensible default. In fact, you should do some research before you hack an app to pieces: this customisation is already possible and designed-for...see http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n354 and http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n162. The desired homepage should go in /usr/share/library-common/index.html . Please can we do some research before we flail about doing stuff. Sorry about the language but I don't have time to say this more nicely.<br />
<br />
== Scope ==<br />
* Edit the Browse activity to point to default-bookmarks.html or some other file specified by fedora<br />
<br />
==UI Design==<br />
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''<br />
<br />
<br />
:This is the first thing a SoaS user will see when the Sugar web browser is launched. This is a critically important page. I don't think we should accept anything util these groups have looked at it:<br />
<br />
* Existing SoaS deployments<br />
* Other sugar deployments<br />
* SL Marketing<br />
* Fedora Marketing (not sure if this is applicable)<br />
<br />
At least as much thought should go into changing the page as went into creating it in the first place.<br />
<br />
[[User:MartinDengler|MartinDengler]] 15:06, 14 June 2010 (EDT)<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
* When Browse is started with '''Start new''' or for first time, this page will open. Custom content with links to web pages will be displayed.<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''<br />
<br />
* The advantage is that the Modified default-bookmarks file is updated from fedora in a normal way to Soas and is part of the build of v4<br />
<br />
== Contingency Plan ==<br />
'''Alternate path: edit /usr/share/sugar/activities/Browse.activity/data/index.html. This would allow sugarlabs to maintain the list.'''<br />
* the Browse.xo on ASLO would also need to be changed<br />
* > In this case: the Browse.xo on ASLO would also need to be changed as<br />
> > installed activities seem to be stored in a different location than .xo<br />
> > files -(I think)<br />
<br />
Nope. This will only be changed in the Browse shipped with SoaS. While<br />
ASLO is a resource for SoaS users what resides there is a generic<br />
resource used by many. pbrobinson<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''<br />
* Discussed with pbrobinson initially and mchua today 06/12/2010 on #sugar-meeting<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
* not a release in normal sense<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Features/Revised_Browse_default-bookmarks.html&diff=53250Features/Revised Browse default-bookmarks.html2010-06-14T17:51:28Z<p>MartinDengler: /* Benefit to Sugar */ flame about "benefits". I don't have time to say this more nicely.</p>
<hr />
<div><noinclude><br />
[[Category:Feature Page Incomplete]]<br />
[[Category:Feature|<Feature Name>]]<br />
<br />
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example <br />
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --><br />
</noinclude><br />
<br />
'''Comments and Explanations:'''<br />
<br />
*Point Sugar.Browse default "start new" screen to:<br />
file:///usr/share/bookmarks/default-bookmarks.html<br />
* "We'll use something slightly different so we don't conflict." pbrobinson <br />
<br />
<br />
*instead of sugars's default:<br />
file:///usr/share/sugar/activities/Browse.activity/data/index.html<br />
<br />
<br />
<br />
<!-- All fields on this form are required to be accepted.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace --><br />
<br />
== Summary ==<br />
''Point the "start new" default Browse start-up page to the page that is downloaded from fedora repository.'''fedora-bookmarks-13-1.noarch.rpm 5.4 kB''<br />
<br />
== Owner ==<br />
<br />
* Name: [[User:satellit|Tom Gilliard]]<br />
<br />
* Email: satellit@bendbroadband.com<br />
<br />
== Current status ==<br />
* Targeted release: SoaS_v4_Feature<br />
* Last updated: (06/12/2010)<br />
* Percentage of completion: 90%<br />
<br />
* http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#AN_ON-LINE_VERSION_OF_THE_DVD_: added links in anticipation of conversion to bookmarks.html write (06/11/2010)<br />
<br />
'''TESTING'''<br />
* Tested on sugar-emulator in f12 (file locations and names may be different in Soas)<br />
* copied file:///usr/share/bookmarks/default-bookmarks.html to desktop,<br />
* opened and edited with OooWriter<br />
* added hyperlinks and saved<br />
* renamed index.html<br />
* opened terminal<br />
su<br />
gedit<br />
*opened modified file<br />
*saved as file:///usr/share/sugar/activities/Browse.activity/data/index.html<br />
*Started "sugar-emulator" and Browse as "Start new" <br />
*took this screenshot:<br />
<br />
<br />
http://people.sugarlabs.org/Tgillard/Modified-default-bookmark.png<br />
<br />
<br />
==='''Change-Browse.activity index.html-to-use-Modified-Browse-html in a live USB'''===<br />
<br />
*In booted USB-soas-i386-20100611.15.iso:<br />
<br />
*In Sugar Terminal; <br />
su<br />
yum install wget<br />
wget http://people.sugarlabs.org/Tgillard/Modified-Browse.html<br />
cd /home/liveuser<br />
chmod 777 Modified-Browse.html<br />
cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html <br />
[root@localhost ~]# cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html<br />
cp: overwrite `/usr/share/sugar/activities/Browse.activity/data/index.html'? y<br />
[root@localhost ~]# <br />
<br />
'''It worked after this. Browse has a new "Start-New" screen. SUCCESS (06/12/2010)'''<br />
<br />
*'''Note: One step farther:'''<br />
su<br />
mkdir /usr/share/library-common<br />
cp /usr/share/sugar/activities/Browse.activity/data/index.html usr/share/library-common/index.html<br />
* Sets up Firefox v 6 .xo (experimental on ASLO) to use the same index.html as Browse uses.<br />
*On live USB Stick (06/13/2010)<br />
<br />
== Detailed Description ==<br />
'''In a discussion with Peter Robinson last night I discovered that a custom Browse bookmark can be downloaded from the fedora repository. I propose to use this "Feature" to allow a custom set of bookmarts to be maintained that would have a series of links ie: e-books; Floss Manuals; wiki.sugarlabs.org, all of the proposed links to files in SugarCreationKit DVD + The NormalBrowse Google Screen'''<br />
<br />
*This should be a simple edit in Browse to point to file:///usr/share/bookmarks/default-bookmarks.html instead of file:///usr/share/sugar/activities/Browse.activity/data/index.html. <br />
<br />
* Repointing the default-screen allows us to have fedora supply our revised "Start New" screen ( or maybe several depending on the deployment or schools requirements to Soas v4)<br />
<br />
===Current Example (see screen-shot above) works well as an Starting Screen=== <br />
*'''Contains the normal Browse links:'''<br />
*Home<br />
*Wiki<br />
*Bugs<br />
*Activites<br />
*'''plus'''<br />
*MENU- which points to an On line Version of the SugarCreationKit DVD, (with all of the links to the sources.)<br />
# CLICK THIS LINK TO TEST: http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#INDEX_OF_Soas_Features<br />
*'''AND'''<br />
*The fedora '''Personal Toolbar Folder''' with all of it's links<br />
<br />
<br />
<br />
*'''This Modified index-html needs to be customized by fedora and used for the build of the Browse.appliance in the v4 Soas-spin '''<br />
<br />
== Benefit to Sugar ==<br />
'''A simple enhancement to sugar.browse'''<br />
<br />
[[User:MartinDengler|MartinDengler]] 13:51, 14 June 2010 (EDT) In fact this is not an enhancement, it's a hack. The browse homepage should be made configurable (perhaps via gconf) and have a sensible default. In fact, you should do some research before you hack an app to pieces: this customisation is already possible and designed-for...see http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n354 and http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n162. The desired homepage should go in /usr/share/library-common/index.html . Please can we do some research before we flail about doing stuff. Sorry about the language but I don't have time to say this more nicely.<br />
<br />
== Scope ==<br />
* Edit the Browse activity to point to default-bookmarks.html or some other file specified by fedora<br />
<br />
==UI Design==<br />
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
== User Experience ==<br />
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''<br />
* When Browse is started with '''Start new''' or for first time, this page will open. Custom content with links to web pages will be displayed.<br />
<br />
== Dependencies ==<br />
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''<br />
<br />
* The advantage is that the Modified default-bookmarks file is updated from fedora in a normal way to Soas and is part of the build of v4<br />
<br />
== Contingency Plan ==<br />
'''Alternate path: edit /usr/share/sugar/activities/Browse.activity/data/index.html. This would allow sugarlabs to maintain the list.'''<br />
* the Browse.xo on ASLO would also need to be changed<br />
* > In this case: the Browse.xo on ASLO would also need to be changed as<br />
> > installed activities seem to be stored in a different location than .xo<br />
> > files -(I think)<br />
<br />
Nope. This will only be changed in the Browse shipped with SoaS. While<br />
ASLO is a resource for SoaS users what resides there is a generic<br />
resource used by many. pbrobinson<br />
<br />
== Documentation ==<br />
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''<br />
* Discussed with pbrobinson initially and mchua today 06/12/2010 on #sugar-meeting<br />
<br />
== Release Notes ==<br />
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''<br />
* not a release in normal sense<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --></div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick&diff=53096Sugar on a Stick2010-06-11T11:52:53Z<p>MartinDengler: edit out remaining "user" verbiage per SeanDaly/mchua (IRC)</p>
<hr />
<div><noinclude><!--{{ Translations | [[Sugar_on_a_Stick|english]] &#124; [[Sugar_on_a_Stick/lang-es|español]] &#124; [[Sugar_on_a_Stick/lang-fr|français]]}}--><br />
[[Category:Project]]<br />
[[Category:Live USB]]<br />
[[Category:Sugar on a Stick]]<br />
</noinclude><br />
<br />
== What is Sugar on a Stick? ==<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.'''<br />
<br />
'''Turn your computer into a Sugar on a Stick Creation Station:''' A related project is the [[Sugar Creation Kit]], a downloadable DVD which includes the materials you need to create Mirabelle sticks and install additional Activities on it, along with documentation and previous versions of Sugar on a Stick.<br />
|}<br />
<br />
__TOC__<br />
<br />
=== Want to use Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]<br />
|-<br />
|<br />
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]<br />
|-<br />
|<br />
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.<br />
<br />
After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.<br />
|}<br />
<br />
=== Want to contribute to Sugar on a Stick? ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]<br />
| style="border: 0; border-width: 0;" |<br />
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.<br />
|}<br />
<br />
== New contributors start here! ==<br />
<br />
Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].<br />
<br />
== What can you do? ==<br />
<br />
There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].<br />
<br />
=== Get Activities on the Stick ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:<br />
<br />
* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''<br />
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''<br />
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''<br />
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''<br />
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''<br />
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].<br />
<br />
| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]<br />
|}<br />
<br />
=== Get Sticks into Schools ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]<br />
| style="border: 0; border-width: 0;" | <br />
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.<br />
<br />
Some things you can do to help:<br />
<br />
* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible, just go for it!<br />
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].<br />
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.<br />
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.<br />
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.<br />
|}<br />
<br />
=== Get Contributors ===<br />
<br />
{|<br />
|-<br />
| style="border: 0; border-width: 0;" | <br />
<br />
Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.<br />
<br />
Some things you can do:<br />
<br />
* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!<br />
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/<br />
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.<br />
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).<br />
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is where the [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity] starts off. Help new joiners past initial questions and provide instant help!<br />
<br />
| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]<br />
|}<br />
<br />
== What's happening? ==<br />
<br />
=== Meetings ===<br />
<br />
We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.<br />
<br />
=== Release schedule ===<br />
<br />
Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].<br />
<br />
{|border="1" cellspacing="0" width="100%"<br />
|-<br />
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released<br />
|-<br />
| Planning & Development Begins<br />
|-<br />
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)<br />
|-<br />
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-08-17 || Alpha Release<br />
|-<br />
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)<br />
|-<br />
| 2010-09-21 || Beta Release<br />
|-<br />
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)<br />
|-<br />
| 2010-10-14 || Compose Release Candidate<br />
|-<br />
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release<br />
|-<br />
|}<br />
<br />
=== Contributor stories ===<br />
<br />
To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].<br />
<br />
== Related work ==<br />
<br />
While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)<br />
<br />
* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access<br />
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.<br />
* [[The undiscoverable]] is an unofficial FAQ for tips, tricks, and solutions to common problems that may otherwise be tricky to find. These are being considered for inclusion in the official SoaS documentation.<br />
<br />
== Previous versions and subpage index ==<br />
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Decision_panels/SOAS&diff=43766Decision panels/SOAS2010-02-05T17:04:32Z<p>MartinDengler: /* Conclusion */ remove extra pipe char</p>
<hr />
<div>{{TOCright2|limit=2}}<br />
<br />
==Overview==<br />
<br />
A 12-person Sugar-on-a-Stick (SoaS) decision panel was appointed by a [[Oversight_Board/Meeting_Minutes-2009-09-25#Decision_Panel|September 25, 2009]] Oversight Board decision.<br />
<br />
The Oversight Board requested a final report, but none was received [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|by 2009-12-04]]. The Oversight Board then assumed responsibility for deciding the mandated questions (ibid.). A summary [[#Conclusion|is below]].<br />
<br />
==Mandate==<br />
<br />
{{quote|<br />
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:<br />
:* <nowiki>[Question 1]</nowiki> "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"<br />
:* <nowiki>[Question 2]</nowiki> "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"<br />
:* <nowiki>[Question 3]</nowiki> "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"<br />
:* Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"<br />
}}<br />
<br />
<br />
==Members==<br />
<br />
* Sebastian Dziallas<br />
* Luke Faraone<br />
* Martin Dengler<br />
* Bill Bogstad<br />
* Faisal Khan<br />
* Benjamin M. Schwartz<br />
* Samuel Klein<br />
* Sean Daly<br />
* Tabitha Roder<br />
* Caryl Bigenho<br />
* Daniel Drake<br />
* Abhishek Indoria<br />
<br />
<br />
== Procedures ==<br />
<br />
The [[:Decision panels#Procedures|Decision Panel procedures]] were adopted.<br />
<br />
Discussion took place on the [http://lists.sugarlabs.org/archives/soas SoaS mailing list] with subject lines beginning with the text "[DP]".<br />
<br />
<br />
<br />
== Report ==<br />
<br />
{{:Decision panels/SOAS/Report}}<br />
<br />
<br />
== Conclusion ==<br />
<br />
In the [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|absence]] of a final report the Oversight board decided [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|Question 1,]] [[Oversight_Board/Meeting_Minutes-2009-12-18#Revisit_Motion_4_from_last_week|Question 2,]] and [[Oversight_Board/Meeting_Minutes-2009-12-18#Resolve_outstanding_Sugar_on_a_Stick_decision_.28Q3.29|Question 3]]:<br />
<br />
{{quote|<br />
:* <nowiki>[Question 1]</nowiki> "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|No]].<br />
:* <nowiki>[Question 2]</nowiki> "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-18#Revisit_Motion_4_from_last_week|No.]] SL may promote one distribution in its marketing campaign, but encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure.<br />
:* <nowiki>[Question 3]</nowiki> "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-18#Resolve_outstanding_Sugar_on_a_Stick_decision_.28Q3.29|Yes.]]<br />
:* Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|Sugar Labs' intent to promote Sugar as widely as possible]] means that SL will work with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.<br />
}}<br />
<br />
==Further ideas==<br />
<br />
* discussion of potential naming conventions.<br />
* discussion of ''how'' to support products such as SOAS, and what that means<br />
* exploration of what it means to "produce a distribution", which some active contributors felt was a huge effort and others felt was already being done, with most effort happening upstream. Better agreement within the community about what is being done may help avoid distracting meta-debates about direction.<br />
<br />
[[category:decision panels]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Decision_panels/SOAS&diff=43765Decision panels/SOAS2010-02-05T17:00:41Z<p>MartinDengler: add results of 2009-12 Oversight Board discussions</p>
<hr />
<div>{{TOCright2|limit=2}}<br />
<br />
==Overview==<br />
<br />
A 12-person Sugar-on-a-Stick (SoaS) decision panel was appointed by a [[Oversight_Board/Meeting_Minutes-2009-09-25#Decision_Panel|September 25, 2009]] Oversight Board decision.<br />
<br />
The Oversight Board requested a final report, but none was received [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|by 2009-12-04]]. The Oversight Board then assumed responsibility for deciding the mandated questions (ibid.). A summary [[#Conclusion|is below]].<br />
<br />
==Mandate==<br />
<br />
{{quote|<br />
:"Investigate the situation of how SoaS should be treated by Sugar Labs, and related questions, including answers to the following:<br />
:* <nowiki>[Question 1]</nowiki> "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"<br />
:* <nowiki>[Question 2]</nowiki> "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"<br />
:* <nowiki>[Question 3]</nowiki> "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"<br />
:* Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"<br />
}}<br />
<br />
<br />
==Members==<br />
<br />
* Sebastian Dziallas<br />
* Luke Faraone<br />
* Martin Dengler<br />
* Bill Bogstad<br />
* Faisal Khan<br />
* Benjamin M. Schwartz<br />
* Samuel Klein<br />
* Sean Daly<br />
* Tabitha Roder<br />
* Caryl Bigenho<br />
* Daniel Drake<br />
* Abhishek Indoria<br />
<br />
<br />
== Procedures ==<br />
<br />
The [[:Decision panels#Procedures|Decision Panel procedures]] were adopted.<br />
<br />
Discussion took place on the [http://lists.sugarlabs.org/archives/soas SoaS mailing list] with subject lines beginning with the text "[DP]".<br />
<br />
<br />
<br />
== Report ==<br />
<br />
{{:Decision panels/SOAS/Report}}<br />
<br />
<br />
== Conclusion ==<br />
<br />
In the [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|absence]] of a final report the Oversight board decided [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|Question 1,]] [[Oversight_Board/Meeting_Minutes-2009-12-18#Revisit_Motion_4_from_last_week|Question 2,]] and [[Oversight_Board/Meeting_Minutes-2009-12-18#Resolve_outstanding_Sugar_on_a_Stick_decision_.28Q3.29||Question 3]]:<br />
<br />
{{quote|<br />
:* <nowiki>[Question 1]</nowiki> "Should Sugar Labs be a GNU/Linux distributor, rather than just an upstream producing Sugar releases?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|No]].<br />
:* <nowiki>[Question 2]</nowiki> "Should SL be neutral about distributions containing Sugar, and refuse to endorse one over another?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-18#Revisit_Motion_4_from_last_week|No.]] SL may promote one distribution in its marketing campaign, but encourages all GNU/Linux distributions to package and distribute Sugar, and if possible will assist with hosting and infrastructure.<br />
:* <nowiki>[Question 3]</nowiki> "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid using unless they refer to the SoaS-Fedora distribution?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-18#Resolve_outstanding_Sugar_on_a_Stick_decision_.28Q3.29|Yes.]]<br />
:* Any other question the Decision Panel deems required to provide an answer to the original question:"Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution?"<br />
:** Answer: [[Oversight_Board/Meeting_Minutes-2009-12-11#SoaS_DP|Sugar Labs' intent to promote Sugar as widely as possible]] means that SL will work with GNU/Linux distros to produce and offer downloadable versions. This work can include helping to promote distros, and hosting them.<br />
}}<br />
<br />
<br />
==Further ideas==<br />
<br />
* discussion of potential naming conventions.<br />
* discussion of ''how'' to support products such as SOAS, and what that means<br />
* exploration of what it means to "produce a distribution", which some active contributors felt was a huge effort and others felt was already being done, with most effort happening upstream. Better agreement within the community about what is being done may help avoid distracting meta-debates about direction.<br />
<br />
[[category:decision panels]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick&diff=39812Sugar on a Stick2009-11-02T10:55:37Z<p>MartinDengler: local support is part of deployability.</p>
<hr />
<div><noinclude>{{ Translations | [[Sugar_on_a_Stick|english]] &#124; [[Sugar_on_a_Stick/lang-es|español]] &#124; [[Sugar_on_a_Stick/lang-fr|français]]}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}<br />
[[Category:Project]]<br />
[[Category:Live USB]]</noinclude><br />
<br />
<br />
{{/Pancake page}}<br />
<br />
<br />
{{TOCright}}<br />
== Introduction ==<br />
Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (stick) that can starts any computer with the student's personalized Sugar environment. We would like to see [[Sugar]]'s presence, journal, and clarity principles usable on any machine &mdash; at school, at home, and anywhere there is a suitable computing device.<br />
<br />
{| class="wikitable"<br />
|[[Image:Soas-1.png|180px|link=0.86/Notes]]<br />
|<br />
'''What exactly is on the Stick?''': Sugar + Fedora GNU/Linux. Taking advantage of [[wikipedia:Live USB|Live USB]] technology, it's possible to store everything you need to run Sugar on a single, [[wikipedia:USB flash drive|USB flash memory stick]]. Compressed file systems are used to save space, and persistent overlay files are used to save changes to the system and user's files. See our [[Sugar on a Stick/Resources| '''resources page''']] to learn about different component configurations we are designing to offer the option to use [[wikipedia:Virtual machine|virtual machines]] on existing computers to host Sugar from a portable Stick and save the [[Human Interface Guidelines/The Laptop Experience/The Journal|Sugar Journal]] (the learner's work) and personal settings on the Stick for use at another workstation.<br />
|}<br />
<br />
== Project Principles ==<br />
* ''Portability'' - One's Sugar environment, saved Activities, and Journal are available wherever one has access to suitable computing devices, at home, school, library, clubhouse in order to permit resumable, extended, and deep exploration of concepts and phenomena.<br />
* ''Customizability'' - Deployments, as well as users, can build their own SoaS easily.<br />
* ''Deployability'' - SoaS is easy to deploy, both for individual sticks and for multiple-instances deployed in computer labs.<br />
<br />
'''Would you like to help?''' ...this is entirely a volunteer-run effort. Please [[/Getting Involved| get involved]]!<br />
<br />
== Getting Sugar on a Stick ==<br />
Follow the instructions for our most stable, [[Sugar on a Stick/Strawberry| Strawberry release]].<br />
<br />
Developers and testers can help us debug the v2 Beta test builds. See [[Sugar on a Stick/Beta]].<br />
<br />
Please let us know how it goes. You can always [[Sugar on a Stick/Contacts| get in touch]] with us!<br />
<br />
== More information ==<br />
<br />
For general questions, please see the [[/FAQ|Frequently Asked Questions (FAQ) page for Sugar on a Stick]]. You can learn more from [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Walter Bender's interview with Xconomy], [http://www.olpcnews.com/software/sugar/sugar_on_a_stick_netbooks.html Wayan Vota's video] and [http://www.flickr.com/photos/curiouslee/sets/72157613785006745/ Mike Lee's pictures].<br />
<br />
== Related work ==<br />
<br />
See these other [[:Category:Live USB|portable Sugar distributions]] that share some of these goals.</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick&diff=39811Sugar on a Stick2009-11-02T10:55:07Z<p>MartinDengler: remove language that is so sappy it makes kittens cry, so wishy-washy I could do the dishes with it, or so redundant that it's redundant. Reorganise a bit too.</p>
<hr />
<div><noinclude>{{ Translations | [[Sugar_on_a_Stick|english]] &#124; [[Sugar_on_a_Stick/lang-es|español]] &#124; [[Sugar_on_a_Stick/lang-fr|français]]}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}<br />
[[Category:Project]]<br />
[[Category:Live USB]]</noinclude><br />
<br />
<br />
{{/Pancake page}}<br />
<br />
<br />
{{TOCright}}<br />
== Introduction ==<br />
Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (stick) that can starts any computer with the student's personalized Sugar environment. We would like to see [[Sugar]]'s presence, journal, and clarity principles usable on any machine &mdash; at school, at home, and anywhere there is a suitable computing device.<br />
<br />
{| class="wikitable"<br />
|[[Image:Soas-1.png|180px|link=0.86/Notes]]<br />
|<br />
'''What exactly is on the Stick?''': Sugar + Fedora GNU/Linux. Taking advantage of [[wikipedia:Live USB|Live USB]] technology, it's possible to store everything you need to run Sugar on a single, [[wikipedia:USB flash drive|USB flash memory stick]]. Compressed file systems are used to save space, and persistent overlay files are used to save changes to the system and user's files. See our [[Sugar on a Stick/Resources| '''resources page''']] to learn about different component configurations we are designing to offer the option to use [[wikipedia:Virtual machine|virtual machines]] on existing computers to host Sugar from a portable Stick and save the [[Human Interface Guidelines/The Laptop Experience/The Journal|Sugar Journal]] (the learner's work) and personal settings on the Stick for use at another workstation.<br />
|}<br />
<br />
== Project Principles ==<br />
* ''Portability'' - One's Sugar environment, saved Activities, and Journal are available wherever one has access to suitable computing devices, at home, school, library, clubhouse in order to permit resumable, extended, and deep exploration of concepts and phenomena.<br />
* ''Customizability'' - Deployments, as well as users, can build their own SoaS easily.<br />
* ''Deployability'' - SoaS is easy to deploy, both for individual sticks and for multiple-instances deployed in computer labs.<br />
* ''Local Support'' - We must encourage and foster the growth of local community involvement in deployments. We must build things in a way that deployers can take over design and construction and fix most of their own problems.<br />
<br />
'''Would you like to help?''' ...this is entirely a volunteer-run effort. Please [[/Getting Involved| get involved]]!<br />
<br />
== Getting Sugar on a Stick ==<br />
Follow the instructions for our most stable, [[Sugar on a Stick/Strawberry| Strawberry release]].<br />
<br />
Developers and testers can help us debug the v2 Beta test builds. See [[Sugar on a Stick/Beta]].<br />
<br />
Please let us know how it goes. You can always [[Sugar on a Stick/Contacts| get in touch]] with us!<br />
<br />
== More information ==<br />
<br />
For general questions, please see the [[/FAQ|Frequently Asked Questions (FAQ) page for Sugar on a Stick]]. You can learn more from [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Walter Bender's interview with Xconomy], [http://www.olpcnews.com/software/sugar/sugar_on_a_stick_netbooks.html Wayan Vota's video] and [http://www.flickr.com/photos/curiouslee/sets/72157613785006745/ Mike Lee's pictures].<br />
<br />
== Related work ==<br />
<br />
See these other [[:Category:Live USB|portable Sugar distributions]] that share some of these goals.</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Sugar_on_a_Stick/FAQ&diff=39760Sugar on a Stick/FAQ2009-10-31T22:13:22Z<p>MartinDengler: tidyup - tiny grammar/sense edits; remove some only-relevant-to-the-past questions, a non-frequently-asked (and/or very stupid) question</p>
<hr />
<div><noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}<br />
<big>Frequently Asked Questions about Sugar on a Stick</big><br />
</noinclude><br />
: '''[[Talk:Sugar on a Stick/FAQ | Post questions here]]''' for the [[Sugar on a Stick]] project team.<br />
<div class="visualClear"></div><br />
<noinclude><br />
<br />
See the Sugar Labs community [[Sugar Labs/FAQ|FAQ]] for more answers.<br />
</noinclude><br />
<br />
===What is it - learning games, homework help, search engines?===<br />
<br />
: Sugar on a Stick provides a consistent, child friendly environment with learning games, software for music, graphics, text, and software creation, a calculator and physics modeling Activities, an Internet browser and chat programs, an electronic book reader, and a tool for teachers to select and package web-based content for students for offline exploration. Additional learning software is available for download in the [http://activities.sugarlabs.org Sugar Activity Library]. The software on the portable memory device allows students to have the same learning tools at school and at home. The teacher can use it to assign homework, but it does not in itself provide homework help. The web browser can be used as a search engine.<br />
<br />
===What do I have to obtain to make it work?===<br />
<br />
: The software can be run on must personal computer systems, but at this point, Sugar on a Stick in-school deployment is in Beta testing stage, starting its first [[Gardner Pilot Academy|pilot deployment]] at a school in Boston, Massachusetts, USA. We would welcome other pilot deployments, but this is still technology in its early stages. At this stage, one might need a technical person who can interface with the Sugar community to make it work.<br />
<br />
===How much does each stick cost?===<br />
: (Note that Sugar Labs does not sell hardware, software, or services.) You will need at minimum a 1-GB stick for each student. Check your local computer store for prices. Right now, it's about $8 USD. To deploy on a large scale, you will also need either very dedicated volunteers or a bulk copy device. We are using one from NeXcopy that retails for about $1200. You should also budget for some USB stick loss.<br />
<br />
===Can I try some of it out?===<br />
: The full software package can be downloaded from [[Sugar on a Stick/Strawberry]]. You can use this download to install Sugar on a Stick onto a USB flash memory drive and test it out.<br />
<br />
===Is it the whole Sugar Learning Platform?===<br />
<br />
: No. We refer to the Sugar Learning Platform as platform because it is a complete software environment for learning. You will need a computer to run Sugar on a Stick, and for school deployments, you will also want an administrator's computer for the [[olpc:School server|School Server]]. The server software is free, but also in a Beta testing phase. The School Server does not need to be high powered: a $500 to $1000 server hardware budget should be sufficient for a pilot program.<br />
<br />
===Is it an effective learning tool?===<br />
<br />
: Please see the first question on this FAQ, [[Government FAQ]].<br />
<br />
===What answers can you provide to common questions about deployments?===<br />
<br />
: Please see this FAQ list, [[Government FAQ]], prepared for common questions from governmental officials.<br />
<br />
===What hardware is it known to work on and what are the known hardware releated bugs?===<br />
<br />
{| border=1<br />
!computer!!comments<br />
|-<br />
|OLPC-XO-1||Works (but doesn't support all XO features, such as power management, special keys)<br />
|-<br />
|Intel Classmate||Works great on the Magellan version<br />
|-<br />
|HP Compaq 6715b||Works great<br />
|-<br />
|Acer Aspire One||Works<br />
|-<br />
|Toshiba Satellite||Works great; boots very quickly<br />
|-<br />
|IBM Thinkpad X60||Works great<br />
|-<br />
|IBM Thinkpad T43||Works great<br />
|-<br />
|Eee PC 900A||Works great<br />
|-<br />
|Dell Latitude 600||No network due to proprietary driver<br />
|-<br />
|Dell Latitude 610||Network with Intel Pro Wireless works<br />
|-<br />
|EeePC1000HE||No Wireless ; Wired works, use VMPlayer for wireless<br />
|}<br />
<br />
:Please add your results to the table above.<br />
<br />
===Have the resolution issues, which used to be a major issue w/ running Sugar on a non-XO, been solved?===<br />
:While not every activity has been modified, most now accommodate variable screen sizes. All of the activities at http://activities.sugarlabs.org work at variable sizes and resolutions as far as I know.<br />
<br />
====What about font sizes?====<br />
:This is also fixed in Sucrose 0.84<br />
<br />
===Do all the activities (incl. collaboration) work reliably on SoaS these days?===<br />
:Collaboration on SoaS is as robust as collaboration anywhere. (There is a Google Summer of Code project that will be addressing one general issue of collaboration robustness--this will be relevant to SoaS and non-SoaS deployments.)<br />
<br />
:There are some Network Manager issues that need to be worked out in general regarding Sugar on non-OLPC kernels, but this impacts connectivity, not collaboration.<br />
<br />
:We saw some issues at FOSSVT on some laptops and netbooks accessing wireless, others worked great. <br />
<br />
:As you pointed out development is going very quickly right now. As we take this out into the world we are finding and fixing bugs. Our main goal right now is to get volunteers to help us do this and keep track of what hardware is working.<br />
<br />
===Does SoaS allow for power-management to kick in on netbooks?===<br />
:Yes, but currently not the special OLPC XO-1 features.<br />
<br />
===Are there networking or audio issues?===<br />
:AFAIK, any audio problems were fixed in the Beta release. There is a discussion upstream about the best way to handle csound support in Fedora.<br />
<br />
:We had found some issues with connectivity with a small number of machines--this seems to be a Fedora issue, not a Sugar issue, and is being worked on upstream.<br />
<br />
===How do I set the keyboard map for a non-US keyboard?===<br />
:Open the Terminal activity and run the <code>setxkbmap</code> program, specifying the code for your keyboard.<br />
:For Spanish:<br />
setxkbmap es<br />
:For Portuguese:<br />
setxkbmap pt<br />
:To make the change permanent, add the command to the end of your .Xclients file found in the home directory.<br />
/home/liveuser/.Xclients<br />
<br />
[[Category:FAQ]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=39648Development Team/Jhbuild2009-10-29T01:16:04Z<p>MartinDengler: the one FAQ was not FA - rephrased</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
Below are generic instructions on how to use jhbuild to get up and running with Sugar.<br />
<br />
==Compatible platforms==<br />
<br />
Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.<br />
<br />
See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).<br />
<br />
==Check distro-specific instructions==<br />
<br />
Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]). <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
Distro packaging guidelines vary, so please don't worry if jhbuild requires twice/half the packages in one distro that it did an another.<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
<br />
=== Dealing with dependencies ===<br />
<br />
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips===<br />
<br />
A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
<br />
=== known issue with hulahop ===<br />
<br />
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands<br />
<br />
=== If build breaks after an update ===<br />
<br />
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].<br />
<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch ''bundle_name''<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
You can make Sugar run fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
== From within Sugar ==<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=39647Development Team/Jhbuild2009-10-29T01:13:55Z<p>MartinDengler: /* Check distro-specific instructions */ whitespace</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
Below are generic instructions on how to use jhbuild to get up and running with Sugar.<br />
<br />
==Compatible platforms==<br />
<br />
Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.<br />
<br />
See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).<br />
<br />
==Check distro-specific instructions==<br />
<br />
Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]] (some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]). <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
:Q: <br />
::<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
:A:<br />
::<sdziallas> dgd: this can be caused by different packaging policies...<br />
::<dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
<br />
=== Dealing with dependencies ===<br />
<br />
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips===<br />
<br />
A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
<br />
=== known issue with hulahop ===<br />
<br />
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands<br />
<br />
=== If build breaks after an update ===<br />
<br />
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].<br />
<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch ''bundle_name''<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
You can make Sugar run fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
== From within Sugar ==<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=39646Development Team/Jhbuild2009-10-29T01:13:15Z<p>MartinDengler: group tips together</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
Below are generic instructions on how to use jhbuild to get up and running with Sugar.<br />
<br />
==Compatible platforms==<br />
<br />
Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.<br />
<br />
See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).<br />
<br />
==Check distro-specific instructions==<br />
<br />
Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
:Q: <br />
::<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
:A:<br />
::<sdziallas> dgd: this can be caused by different packaging policies...<br />
::<dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
<br />
=== Dealing with dependencies ===<br />
<br />
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips===<br />
<br />
A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
<br />
=== known issue with hulahop ===<br />
<br />
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage, or add "-a" to the build / buildone commands<br />
<br />
=== If build breaks after an update ===<br />
<br />
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].<br />
<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch ''bundle_name''<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
You can make Sugar run fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
== From within Sugar ==<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Jhbuild&diff=39642Development Team/Jhbuild2009-10-28T21:07:38Z<p>MartinDengler: /* Build sugar base system and its dependencies */ no need to convince us flash is annoying and workable</p>
<hr />
<div><noinclude>{{Translations}}{{GoogleTrans-en}}{{TOCright}}</noinclude><br />
<br />
Sugar-jhbuild will automatically download the latest of Sugar's dependencies as well as Sugar itself directly from their source repositories, rather than relying on source packages that may have become stale.<br />
It can also run a Sugar session in a window on your desktop using the [[wikipedia:Xephyr]] nested X window server.<br />
Below are generic instructions on how to use jhbuild to get up and running with Sugar.<br />
<br />
==Compatible platforms==<br />
<br />
Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it.<br />
<br />
See the distribution-specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).<br />
<br />
==Check distro-specific instructions==<br />
<br />
Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding:<br />
<br />
* [[/Debian | Debian]]<br />
* [[/Fedora | Fedora]]<br />
:Here are some [http://www.youtube.com/profile?user=pleabargain&view=videos&query=jhbuild videos of the Fedora jhbuild install process]. <br />
* [[/Ubuntu | Ubuntu]]<br />
* [[/Mandriva | Mandriva]]<br />
<br />
==Some general advice==<br />
<br />
Note: Like most other Unix applications, sugar-jhbuild should never be run as root. It may easily screw up your whole system and/or break in unexpected ways if you do. If you get any permissions error, there's something wrong with your installation that should be fixed.<br />
<br />
If you're stuck or if you get strange errors, feel free to ask for help on the [[Sugar_Labs/Contacts#irc.freenode.net_channels|#sugar IRC channel]] or the [[Sugar_Labs/Contacts#Developer_Lists|sugar-devel mailing list]]. Don't waste too much time chasing strange problems: usually it's caused by some basic, easy to fix problem. You might also want to check the [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar-jhbuild bug tracker] to see if it's a known issue.<br />
<br />
==Jhbuild FAQ==<br />
:Q: <br />
::<dgd> jhbuild build on fedora11 requires 29 packages but on Ubuntu904 38... should I be concerned with the difference in number?<br />
:A:<br />
::<sdziallas> dgd: this can be caused by different packaging policies...<br />
::<dgd> sdziallas, ergo not a reason for concern, thanks!<br />
<br />
definitely do not compile as root with jhbuild -- you'll run into funky problems -- Colin A. :)<br />
<br />
==Prerequisites==<br />
; python<br />
: The sugar-jhbuild command is a Python script, so you need the Python interpreter.<br />
; git<br />
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <tt>git</tt> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core".<br />
; svn<br />
: A few packages (as of September 2009, only squeak) do not yet use git, and you need the <tt>svn</tt> command-line tool from the Subversion version control system to get their source code.<br />
<br />
These should be enough to run sugar-jhbuild on a typical Linux or Mac installation. Running <tt>sugar-jhbuild depscheck</tt> (see below) will probably list dozens of additional required packages.<br />
<br />
==Check out sugar-jhbuild==<br />
<br />
In a suitable directory (i.e. usually your user's home directory i.e. /home/yourusername/~), execute<br />
git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
<br />
::Make sure you are in the _user's_ home directory<br />
:: video http://www.youtube.com/watch?v=Tdr1bs4rQ_s<br />
<br />
You'll know if it worked if you get something like this:<br />
<pre><br />
localhost ~]$ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild<br />
Initialized empty Git repository in /home/denny/sugar-jhbuild/.git/<br />
remote: Counting objects: 4688, done.<br />
remote: Compressing objects: 100% (1998/1998), done.<br />
remote: Total 4688 (delta 2759), reused 4488 (delta 2638)<br />
Receiving objects: 100% (4688/4688), 1.86 MiB | 197 KiB/s, done.<br />
Resolving deltas: 100% (2759/2759), done.<br />
</pre><br />
<br />
==Build sugar base system and its dependencies==<br />
<br />
Go into the directory you created and start the build. It takes about 30 minutes on a 1.6ghz machine with a wireless G connection.<br />
<br />
cd sugar-jhbuild<br />
./sugar-jhbuild update<br />
./sugar-jhbuild depscheck<br />
./sugar-jhbuild build<br />
::[http://www.youtube.com/results?search_query=pleabargain+jhbuild&search_type=&aq=f Here are videos of the process].<br />
<br />
And now run it.<br />
./sugar-jhbuild run<br />
<br />
If it doesn't run or you have other problems read on.<br />
=== Dealing with dependencies ===<br />
<br />
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).<br />
<br />
If you notice that there's a package missing from the <code>./sugar-jhbuild depscheck </code> output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].<br />
<br />
===Some tips and known issues===<br />
* hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again.<br />
*25 Aug 9: hulahop doesnt' build correctly. http://lists.sugarlabs.org/archive/sugar-devel/2009-August/018540.html The 'fix' is running autoconf.<br />
::Question. How do you run autoconf to fix this problem?<br />
::: when you get asked because of the error, choose the configure stage<br />
<br />
== Run Sugar ==<br />
<br />
This command launches the Sugar emulator in a nested X session:<br />
<br />
./sugar-jhbuild run<br />
<br />
To exit the emulator, press Alt-Q.<br />
<br />
To set debug variables, modify <code>~/.sugar/debug</code> (this file will be created on first run of Sugar).<br />
<br />
Note that due to a [http://dev.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.<br />
<br />
The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.<br />
<br />
== Running multiple instances ==<br />
To run an additional instance of sugar, you can start the second instance in the following way:<br />
<br />
SUGAR_PROFILE=2 ./sugar-jhbuild run<br />
<br />
This will create a new profile in ~/.sugar/, i.e. ~/.sugar/2/. You will find logs and configuration for this instance here. The default profile is ~/.sugar/default/<br />
<br />
== Run an individual activity ==<br />
<br />
Within sugar, e.g. in Terminal, this command launches an individual activity for testing:<br />
<br />
sugar-launch ''bundle_name''<br />
<br />
You will see debug output appearing in Terminal.<br />
<br />
== Configure the mode and resolution of Sugar ==<br />
<br />
You can make Sugar run fullscreen or specify a size (in pixels):<br />
<br />
./sugar-jhbuild run sugar-emulator --fullscreen<br />
./sugar-jhbuild run sugar-emulator --dimensions 1200x900<br />
<br />
The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).<br />
<br />
== Other commands ==<br />
<br />
JHBuild has several other commands that can be useful for development. You can get an overview with:<br />
<br />
./sugar-jhbuild --help-commands<br />
<br />
A useful sequence of commands for building Sugar, from the [http://mailman.laptop.org/pipermail/sugar/2007-February/001352.html Sugar mailing list]: (Note that build will update first anyway, so run update separately if you want to see what changed more easily.)<br />
<br />
./sugar-jhbuild update<br />
./sugar-jhbuild build -a --clean<br />
./sugar-jhbuild run<br />
<br />
The use of -a and --clean flags are needed when a file is removed so that autogen.sh is run. '''Note:''' Some packages, e.g., squeak and etoys, don't have a ''make clean''. Just ignore the error.<br />
<br />
== If build breaks after an update ==<br />
<br />
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run<br />
./sugar-jhbuild depscheck<br />
regularly and install the missing packages.<br />
<br />
If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].<br />
<br />
== From within Sugar ==<br />
Once you have Sugar running, here are some useful commands:<br />
*'''Alt+Shift+F''' makes the frame appear and disappear<br />
*'''Ctrl-Q''' quits an activity<br />
*'''Alt+Shift+Q''' quits Sugar<br />
*'''Alt+Shift+O''' opens the search<br />
*'''Alt+Shift+R''' rotates the screen<br />
<br />
== Customize ==<br />
<br />
To customize the build create a configuration file, named ''.sugar.jhbuildrc'', in your home directory.<br />
<br />
=== Write access to the repositories ===<br />
<br />
If you have write access to the repositories you can add this (if your login name happens to be marco):<br />
repos['gnome.org'] = ':ext:marco@cvs.gnome.org:/cvs/gnome'<br />
repos['mozilla.org'] = ':ext:marco%gnome.org@cvs.mozilla.org:/cvsroot'<br />
repos['dev.laptop.org'] = 'git+ssh://marco@dev.laptop.org/git/'<br />
repos['dev.laptop.org/projects'] = 'git+ssh://marco@dev.laptop.org/git/projects/'<br />
<br />
==Useful Internal Links==<br />
* [[Development Team/Understanding the Code|Understanding Sugar Code]]<br />
* [[Taxonomy]] -- explains the components of Sugar (Glucose, Fructose, Sugar, Starches)<br />
* [[Sugar Instructions]] -- how to actually use Sugar once you have it running[http://en.flossmanuals.net/sugar]<br />
<br />
==External links==<br />
<br />
* [http://library.gnome.org/devel/jhbuild/unstable/ JHBuild manual]<br />
* [http://www.redhatmagazine.com/2007/02/23/building-the-xo-introducing-sugar/ Red Hat Magazine article: Introducing Sugar]<br />
* [http://learn.laptop.org/tinderbox/ Tinderbox] (see the "Sugar JHBuild" tab). The old [http://dev.laptop.org/~cjb/sugar-tinder/ sugar-jhbuild tinderbox].<br />
<br />
[[Category:Installing Sugar]]<br />
[[Category:Jhbuild]]</div>MartinDenglerhttps://wiki.sugarlabs.org/index.php?title=Lesson_plan_template/Wiki_Version&diff=39583Lesson plan template/Wiki Version2009-10-26T23:52:46Z<p>MartinDengler: /* Instructional Procedures */ whitespace</p>
<hr />
<div>{{TOCright}}<br />
=== Overview ===<br />
<br />
==== Lesson Summary ====<br />
Briefly describe the procedures and purposes of the lesson.<br />
<br />
==== Estimated Duration ====<br />
Include an estimate of the time needed for instruction.<br />
<br />
<br />
====Commentary====<br />
Any important, up-front-visible comments should go here.<br />
<br />
<br />
===Assessment===<br />
<br />
====Pre-Assessment====<br />
<br />
Identify strategies to pre-assess student knowledge of the selected standard(s), benchmark(s) and indicator(s). Data from pre-assessment helps educators select specific instructional strategies and determine appropriate complexity and pacing for the lesson. Pre-assessments may be as informal as a reflection on students’ prior learning, a conversation about concepts or warm-up problems at the beginning of class that are not scored. They may be more formally structured, such as a quiz or an assigned writing topic.<br />
<br />
=====Scoring Guidelines=====<br />
Define scoring guidelines for the pre-assessment, which may take the form of teacher judgment, a checklist or another scoring format. Scoring guidelines should reveal whether or not student has met the indicator or benchmark so that instruction can be modified and targeted to learners accordingly.<br />
<br />
Teachers should conduct ongoing teacher assessment and student self assessment throughout instruction. These can be planned or conducted as opportunities for observation or reflection arise. If planned, describe here.<br />
<br />
====Post-Assessment====<br />
Identify strategies to assess student learning as a result of the lesson. Data that results should help to plan subsequent instruction.<br />
<br />
=====Scoring Guidelines=====<br />
Define scoring criteria for the post-assessment, which may take the form of a rubric or another scoring format. Scoring criteria should reveal whether or not student has met the indicator or benchmark so that instruction can be targeted accordingly. If possible, assessment and scoring criteria should be developed to reflect student process as well as product.<br />
<br />
===Instructional Procedures===<br />
<br />
Describe the instructional steps that will be taken to implement the lesson.<br />
<br />
An introductory lesson plan [http://lists.sugarlabs.org/archive/iaep/2009-October/009083.html might comprise]:<br />
<br />
# Brief overview of what might be possible with each Activity<br />
# Introduction of one or two key functions<br />
# Exploration time -- encourage sharing between participants, particularly when they learn something new<br />
# Introduction of another key function<br />
# Exploration time (as before)<br />
# Discussion - how do they see using the Activity with their students<br />
# Create a project/sample lesson plan from good ideas in the discussion<br />
<br />
<br />
==== Step 1 ====<br />
<br />
==== Step 2 ====<br />
<br />
==== Step 3 ====<br />
<br />
==== Etc ====<br />
<br />
=== Materials and Resources ===<br />
<br />
====For teachers====<br />
List the materials needed for the teacher.<br />
<br />
====For students====<br />
List the materials needed for the students.<br />
<br />
====Key Vocabulary====<br />
List key terms that need to be defined prior to or as part of instruction.<br />
<br />
====General Tips====<br />
Record observations and suggested modifications to facilitate instruction and student learning in the lesson.<br />
<br />
====Attachments====<br />
List and attach any additional materials created for the lesson, including student handouts, blackline masters, overheads, etc.<br />
<br />
<br />
===Adaptation and Connections===<br />
<br />
====Differentiated Instructional Support====<br />
<br />
Describe how instruction can be differentiated according to learner needs, to help all learners either meet the intent of the specified indicator(s) or, if the indicator is already met, to advance beyond the specified indicator(s).<br />
<br />
====Extension====<br />
These are ideas for all students to continue learning on this topic -- in class or outside of class.<br />
<br />
<br />
====Homework Options and Home Connections====<br />
Describe work that will be assigned to students outside of the classroom.<br />
<br />
====Interdisciplinary Connections====<br />
Tell how the lesson can be integrated with other content areas to strengthen student learning.<br />
<br />
====Technology Connections====<br />
Suggest ideas for integrating technology into the lesson.<br />
<br />
====Research Connections====<br />
Include research that supports the content or methods of instruction within the lesson.<br />
<br />
<br />
<br />
=== Colophon ===<br />
<br />
====Content Standards====<br />
<br />
This lesson plan was written by *Author*.<br />
<br />
It is released under the "[http://creativecommons.org/licenses/by/3.0/ Attribution 3.0 Unported]" license.</div>MartinDengler