Sugar Labs - User contributions [en]

Archive/Current Events/2008-12-22

2009-04-08T15:38:48Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>

=== Sugar Digest ===

1. Sugar narrative: Caroline Meeks and I participated in a readathon at the Gardner School in Allston last week, giving us an opportunity to spend some time in classrooms in the school where we are planning a Sugar-on-a-Stick pilot. We also had an opportunity to meet with a former classroom teacher who is now focusing full time on curriculum development. There was synergy between all of our goals: good things will happen. However, one thing became obvious very early in the discussion: we are lacking a good narrative about Sugar and how it is used in schools. We have lots of pictures of children with laptops, but few of these pictures are illustrative of learning. We have some data—most notably from the Peru deployment—about the impact of Sugar on learning, but again, these are data illustrating results, not the process of achieving those results. While more deployment guides and lesson plans are being written, we still lack a compelling narrative.

Maybe it is time to dust off an old idea: Why don't we create ''a day in the life of Sugar'', a movie/telenovela/graphic novel about various experiences with Sugar in the classroom? We have loads of material—we just need to start telling the story. Anyone interested in taking the lead on this project?

2. OLPC's Change the World program: It is refreshing to read that OLPC is beginning to embrace programs at a scale that can be launched at a grassroots level. Let's hope that this bottom-up approach is given a chance to get some momentum.

3. Sugar Workshop plan: Rafael Ortiz posted [http://sugarlabs.org/go/DeploymentTeam/Deployment_guide_sur/TallerBuinaima the workshop plan] from a teacher workshop that took place at the Bunaima Foundation in Bogota, Colombia.

4. Local labs: We've been discussing frameworks for local/regional Sugar Labs. Please join the weekly discussion of the deployment team on Wednesdays at 14:00 UTC on irc.freenode.net channel #sugar-meeting. We'd appreciate more input from deployment teams around the world. There is a [[Deployment Team/Local_Lab_MOU|draft of a sample memorandum of understanding (MOU)]] between Sugar Labs and any organization that would like to establish a local lab. Please add your comments.

5. There is also [[Deployment Team/Getting Involved#Proposals|Proposals Section]] in the wiki for aggregating information about potential grant opportunities for Sugar Labs and region groups. Please help us identify and pursue funding opportunities.

6. GNOME: I will be representing Sugar on the GNOME foundation board of advisers. If you have any Sugar-related concerns you would like voiced, please let me know.

7. Ignorant and seemingly happy that way: It seems there is still quite a bit of misinformation about free software in Texas (See [http://austinist.com/2008/12/10/aisd_teacher_throws_fit_over_studen.php Teacher Throws Fit]).

=== Community jams, meet-ups, and meetings ===

8. It is not too late to sign up for [http://fedoraproject.org/wiki/FUDCon/FUDConF11 FUDConF11], which will be held at MIT (Cambridge, MA) 9–11 January.

=== Tech Talk ===

9. git.sugarlabs.org: Marco Pesenti Gritti reports that the official repositories for the following modules have moved on git.sugarlabs.org:
* sugar
* sugar-base
* sugar-toolkit
* sugar-datastore
* sugar-presence-service
* sugar-jhbuild
* read
* chat

We are still working out some of the details regarding the process of a general migration to the new server.

10. Sugar team:

Marco's week also included:
* looking into palette bugs in Sugar 0.83;
* starting a [[Development Team/TODO|team TODO]], as substitute for the roadmap, which will be reviewed weekly;
* writing about upstream/downstream relations with Sugar Labs;
* updating jhbuild dependencies (to keep up with Tomeu Vizoso's changes);
* discussing with Mel Chau and Simon Schampijer about testing team and bug squad; and
* thinking about how to involve the community more directly in Sugar development; self-contained bundle vs packages with dependencies; and how to better expose information about core modules and activities to developers.

Marco also made good progress on collaboration dog-fooding, which reminds me: since we use Jabber extensively in Sugar, why aren't we using it for our discussions about Sugar?

Tomeu's week included:
* working on file transfer in the Journal. Collabora Ltd. employees have been very helpful,
especially Guillaume Desmottes.
* adapting http://addons.mozilla.org to Sugar activities (with David Farning)

11. Activities:

Vincent Povirk reports that the Wine activity (Windows emulator) has advanced to the point where he think it is ready for testing by actual users (See http://wiki.winehq.org/SugaredWine).

I've release TurtleArt-23.xo, which does a local caching of the render SVG images, resulting in a great improvement in launch speed (with the exception of the very first time you run it). Next up for TurtleArt, a save option that outputs Logo code.

Food Force is available for testing (See http://code.google.com/pfoodforce/downloads/list).

=== Sugar Labs ===

12. Self-organizing map (SOM): Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2008-December-6-12-som.jpg|SOM]]).

[[Category:Sugar Digest]]

Archive/Current Events/2009-02-10

2009-04-08T15:35:21Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>

=== Sugar Digest ===

Baselines, Part 1: A few months ago, Tomeu Vizoso set a baseline for the Sugar "view source" functionality that had largely gone unrealized in most Activities. In the upcoming (March) release of Sugar, the default behavior of all Activities will be to have their source code opened inside of Pippy, the Python editor written by Chris Ball and maintained by C. Scott Ananian. (This is already the default behavior of Chat—try it, you'll like it.)

While this is a baseline, it is clear that for many Activities, it is not sufficient. In some Activities, such as Browse, view source is geared towards the content being browsed, rather than the Browser itself. In a manner similar to the Mosaic web browser—and most browsers built since—view-source shows the HTML content from which the page is created. Browse puts a copy of the HTML content into the Journal from where it can be viewed and modified by the Write Activity.

It has often been argues by me (and many others) that view source is what made the web transparent and enabled any consumer of web content to become a producer. Indeed, this was the threshold through which a generation has passed—remix is a part of our culture, not just something for Trekkies and other fringe groups as observed by Henry Jenkins in the mid 1980s.

I have been thinking about view source within the content of Turtle Art lately. I had gotten immersed in Turtle Art when some teachers on the Sur list began asking for some extensions. At the time I tried to get them to make the extensions themselves, but the floor was too high. I jumped in in order to document the process of modifying an Activity and also to try to understand first hand where the difficulties laid. My early attempts are described in the wiki ([[Activities/Turtle_Art/Patching|Patching Turtle Art]]).

Between Bill Kerr's subsequent questions ([[Talk:Patching_Turtle_Art|Talk:Patching Turtle Art]]) and my own experiences, I was awakened to the fact that we have a long ways to go in terms of making view source meaningful to the teacher, the student, and the potential Sugar contributor.

View source was central to the discussion I had with Bill Kerr and Tony Forster last week in Melbourne. We agreed that it worthwhile exploring the impact of the addition of some more steps between using an Activity and viewing the project's Python code; indeed, it would be necessary if any but the most dedicated would venture forth. Tony has braved the GNU/Linux shell to try to modify Turtle Art; he has been documenting his efforts ([http://tonyforster.blogspot.com/ Tony Forster blog]) Previously I had added an export function to Turtle Art so that the psuedo Logo generated in the graphical interface could be viewed inside a text-based, fully featured Logo environment—a one-way path towards more sophisticated programming concepts.

As a result of the Melbourne discussion, I decided to take a slightly different approach. I have added two new blocks to Turtle Art (actually, at the moment, just to Turtle Art Portfolio, a fork of Turtle Art).

One block lets you try Python code directly into it. It can be used for simple, in-line extensions, such as added new functions from the math library. It uses a simple set of assumptions: there is one input (int or float) and one output (float), e.g., typing sin(x) into the block turns the block into the sine function. It is similar to the programmable extensions found in may environments, such as [http://rupert.id.au/schoolgamemaker/morethan.htm Gamemaker]. While I expect that this will satisfy the needs of many of those who are looking for simple extensions to the Turtle Art environment, I don't think it addresses the question of how to provide a stepping stone towards modifying Turtle Art itself—in fact, it may discourage many from every bothering to view the source code because they can make changes without having to "look under the hood."

I have higher hopes for the second block I introduced. Internally it calls a Python procedure, myblock, that is currently a "nop"—it simply returns without executing any code. The idea is that myblock, which is loaded as a separate module, will be modified by the end user. When Turtle Art Portfolio is launched for the first time, it makes a copy of myblock in the Journal. It can be opened in Pippy, where it can be modified and saved back to the Journal. From within Turtle Art, you can reload the myblock module by selecting a new module from the Journal.

I've put some commented-out examples of what you can do with myblock into the Python code: a dotted line; some string manipulations; and the extension of the Turtle Art color space to include chroma (gray) in addition to hue and value.

In using myblock, my typical work cycle is to switch between Turtle Art Portfolio, Pippy, and Log Viewer (so that I can see the error messages from the Python interpreter—I make a lot of mistakes as I code). The major limitation I face in the current implementation is that within Pippy I don't have access to the Turtle Art environment. I need all but rudimentary syntactic debugging in Turtle Art itself and I need to know what resources are available within that environment, which I can only find out by looking at more of the source code. (I am hoping that enough examples will help in regard to the latter issue.) Nonetheless, I hypothesize that the barrier to entry into making real modifications to Turtle Art is much lower now. I cannot wait to get feedback from the field to see if I am heading down the right path.

I am hoping that other Activity developers go beyond the baseline set by Tomeu. I am sure that there are many creative ways to engage in the appropriation of the tools we are creating.

----

Baseline, Part 2: There has been an interesting discussion this week about setting a baseline for Sugar collaboration. The discussion began, ironically, when James Simmons, author of the Etexts and View Slides Activities asked how he could turn off collaboration, as it too bandwidth intensive. He got a number of replies in regard to mechanisms for removing the sharing menu on the toolbar, e.g.,

# Hide the sharing button from the activity toolbar
activity_toolbar = self.tbox.get_activity_toolbar()
activity_toolbar.share.props.visible = False

But Carol Farlow Leche took the discussion in to a different direction.

:I'm guessing someone has already suggested this on some list or other, but in my experience kids like to watch over each other's shoulder, and a default collaboration of "everyone watches, one person types" VNC would in my opinion be the 80 of a collaboration 80–20 rule. I think this ought to be implemented in the Sugar infrastructure, and then let activities that have an obvious extended collaboration (such as two person games or shared authorship documents) do something more.

This led to a (renewed) discussion of using VNC as a default collaboration baseline for all Activities. Chris Ball has already done a lot of the ground work necessary to make this happen (See his great demo at [http://blog.printf.net/articles/2009/01/26/multi-pointer-remote-desktop multi-pointer remote desktop]). With a bit of UI glue, we could have shared desktops in Sugar, although I don't think we'll land this feature as part of 0.84 in March.

Many others joined the discussion, including Eben Eliason, Wade Brainerd, Andrés Ambrois, Gary Martin, Martin Langhoff, C. Scott Ananian, Morgan Collett, and Ben Schwartz. Together, they came up with a nice model where by any Activity that was already "full" from the perspective of joining would be available for watching—by default through VNC.

As with view source, collaboration is a core Sugar affordance for learning. Much of the original inspiration for the Sugar collaboration comes from observing how people collaborate on the Web. But also in the classroom. As Carol observes, looking over shoulders represents a large portion of the collaboration that happens in the classroom. Undoubtedly, we should support simple mechanisms for this, although I would argue that we should not lose sight of the fact that the easiest way to look over someone's shoulder is to get out of our chair, walk over, and look. Much of the time we don't need to impose technology between children or their teachers.

So how should we be thinking about the VNC model? A common use of VNC in classrooms is for the teacher to single out several students to share their work with the entire class for discussion. Often a mosaic of up to 16 screens are projected in front of the class. A less common, but in my opinion just as interesting model is one that was developed in Chile: the children are assigned to small groups to work on problems. Each group is tasked with coming to consensus. The teacher then asks different groups to present their work and their hypotheses to the class as a whole.

The simplest, and arguably most powerful example of Sugar collaboration is peer editing in Write. To always be just one "click" away from inviting someone to edit your work is revolutionary. When Ben first demonstrated the Distance Activity (aka Acoustic Tape Measure) it was a revelation. It is great to see a new wave of interest in Sugar collaboration. I look forward to more awakenings.

=== Community jams, meet-ups, and meetings ===

The minutes of the most recent meeting of the Sugar Oversight Board are posted in the wiki (See [[Sugar_Labs/OversightBoard/Meeting_Minutes-2009-02-02|Minutes:2009-02-02]]).

There will be a Sugar gather in Brussels at FOSDEM, the free and open-source developers' European meeting (See [[Marketing Team/Events/FOSDEM_2009|FOSDEM 2009]]). The Fedora booth will feature a create your own Sugar-on-a-Stick station.

While I was unable to recruit a Sugar representative to [http://scale7x.socallinuxexpo.org/ SCALE], there will be several community members. Send email to the list if you will be attending.

=== Help Wanted ===

We continue to advance towards the release of Sugar 0.84 in March. Testers are critical at this time. Please see [[BugSquad/Getting Involved|the BugSquad page]] for more information on how you can help.

I had a conversation with a colleague at the World Bank yesterday. We discussed their textbook efforts and how it would be worth exploring some remixing ideas within the context of Sugar. Info slicer, a tool to enable teachers to quickly and easily select web-based content to edit, package, and distribute as teaching materials, comes to mind (See [[Activities/Info Slicer|Info Sclicer]]). Let me know if you'd be interested in participating in a follow-up conversation.

=== Tech Talk ===

New versions of [http://sugarlabs.org/wiki/images/9/9f/Info Slicer-1.xo Turtle Art], [http://sugarlabs.org/wiki/images/6/60/TurtleArtPortfolio-11.xo Turtle Art Portfolio], and [http://sugarlabs.org/wiki/images/9/9f/InfoSlicer-1.xo InfoSlicer] are available for testing.

=== Sugar Labs ===

Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2009-January-24-30-som.jpg|SOM]]). He is also looking for feedback on his algorithm:

:I've been putting in some more time on the SOM code the last couple of weeks (high resolution contour lines being one improvement). I wanted to bounce 2 (low-res) maps of this weeks IAEP content off the list for feedback. The first (2009-January-24-30-3-mean) uses the same fully normalized procedure as per the last month of maps (i.e height == term link density); the second (2009-January-24-30-3-corrected) has an identical cluster layout, but has its topographic height re-adjusted to bring back in the term frequency (i.e height == term link density * term frequency). I think this 2nd map gives us the undistorted term layout as seen in maps of the past month, while allowing term frequency to have some influence again over the topography (maps last year all had term frequency frequency).

See [[Sugar_Labs/SOM|the SOM overview page]] for more details.

[[Category:Sugar Digest]]

Summer of Code

2009-04-08T15:32:48Z

Dfarning-bot: fix camelcase links

Sugar Labs

2009-04-08T15:27:52Z

Dfarning-bot: fix camelcase links

<noinclude>{{TeamHeader|Sugar Labs|home=Community Home|meeting_link=Events|meeting_label=Events Calendar}}</noinclude>
===Mission===
The mission of Sugar Labs is to produce, distribute, and support the use of the Sugar learning platform; it is a support base and gathering place for the community of educators and developers to create, extend, and teach with the Sugar learning platform.

See this Community news post from [[Sugar Labs/Current Events/Archive/2009-03-17|10-Mar-2009, on ...our '''“Big Overarching Vision Goals for 2009”''']]...
{{TOCright}}

== [[:Category:Team|Teams]] ==
Sugar Labs is organized around overlapping Teams. Please use the '''Community''' panel in the wiki sidebar to visit and explore the work and events for each team.
This [[:Category:Team | ''Team'' category page]] collects all Sugar Labs wiki pages with a ''Team'' tag.
== [[:Category:Project|Projects]] ==
Sugar Labs is supporting a few projects focused on delivering specific goals in a defined time period. Please see these project home pages:

| [[Sugar on a Stick]] | [[Gardner Pilot Academy]] | [[Shaw Elementary School]] | [[Math4Team |Math4 Project]] |

| [[Summer of Code]] |

==[[Sugar Labs/Current Events|Community News]]==
A [[Sugar Labs/Current Events|current events page]] updated each week (usually on Monday morning) with notes from the Sugar Labs community. (The Sugar Digest is also sent to the <span class="plainlinks">[http://lists.sugarlabs.org/listinfo/community-news community-news at lists.sugarlabs.org] list and blogged at [http://walterbender.org/ walterbender.org].) If you would like to contribute, please send email to [[User:walter|walter]] at sugarlabs.org by the weekend. (Also visit [http://planet.sugarlabs.org planet.sugarlabs.org].</span>)

An '''[[Sugar Labs/Current Events/Archive|archive]]''' of Sugar Digests is available.

==[[Sugar Labs/Events | Events Calendar]]==
Sugar [[Sugar Labs/Events | community events]] are posted in a public calendar within the Google Calendar system. The calendar is available in a variety of formats: <span class="plainlinks"> [http://www.google.com/calendar/feeds/6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com/public/basic http://wiki.sugarlabs.org/images/b/b9/XML.gif] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics http://wiki.sugarlabs.org/images/1/19/ICal.gif] [http://www.google.com/calendar/embed?src=6n9a99dr5knag9tp0obc0rncug%40group.calendar.google.com&ctz=America/New_York http://wiki.sugarlabs.org/images/0/0c/HTML.gif].</span>

Please contact [[User:Walter]] if you'd like to post an event to the calendar. Or simply post it below and it will be included.

==[[:Category:Roadmap|Roadmap]]==
The [[Sugar Labs/Roadmap|Sugar community roadmap]] is used to guide our community efforts:
* Mission, Vision, Values
* Distribution
* Deployments
* Quality Assurance
* Infrastructure

== Sugar Labs: a learning and software-development community ==
The Sugar development platform is available under the open-source GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, which is in the process of joining the Software Freedom Conservancy (a non-profit foundation to produce and distribute and support the use of free software) serves as a support base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible applications.

=== Education Goals ===
Sugar is useful only to the extent it is used by the learning community. Thus Sugar Labs is working with educators around the world to focus on these learning challenges:

* To make Sugar and Sugar activities freely and readily available to learners everywhere;
* To explore and share best practices
* To provide a forum for discussion and support for technology for learning
* To provide mechanism for evaluation and dissemination of results.

=== Technical Goals ===
Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” Thus Sugar puts an emphasis on “activities” rather than “applications.” The foundation will focus on solving the challenges that are relevant to these aspects of the interface, namely:

* To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.
* To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every distribution and every virtual machine—removing hardware-related dependencies wherever possible.
* To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.
* To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.

=== Community Goals ===
Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. Sugar Labs would like to help community members start projects that help sustain and grow the Sugar technology and learning communities:

* To provide local and regional technical and pedagogical support.
* To create new learning activities and pedagogical practice.
* To provide localization and internationalization of software, content, and documentation.
* To provide integration and customization services.

=== Principles ===
In order for Sugar to be successful, it needs the participation of a large number of people who share common goals while maintaining independence, so that each participant has the ability to act independently. For these reasons, Sugar Labs subscribes to the principles described [http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/ here], which are the author's own translation of an [http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta original text in Spanish.]

====Identity====
* Clear mission – Full disclosed objectives.
* Declared commitments – Affinities and aversions explained.
* Explicit connections outside – Relationships with other organizations listed.

====Structure====
* Horizontal organization – Teams and facilitators work on responsibilities and agreements.
* Identified contributors – Who is who, people are reachable.
* Clear responsibilities – Who is in charge of what.
* Activities described – All the ongoing work is acknowledged.
See [[Wiki_Team/Guide/Wiki_Structure | Wiki Structure]] for a guide to how the wiki models Sugar Labs structure.

====Operation====
* Open participation – Anybody can access the information and get a first responsibility.
* Meritocracy – Responsibilities are acquired (or lost) based on own skills and contributors’ support.
* Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.

====Information====
* Regular reports – Reported activities and future plans allow monitoring and participation.
* Information accessible – Even internal operational information is available by default.
* Explicit confidentiality – It is explained what areas are confidential, why and who can access them.

====Goods====
* Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion [[Sugar Labs/Funding|here]].)
* Resources – Inventory of items detailing who contributed what and why.
* Public accounts – It’s clear where the money comes from and where it goes.
* A special [[Sugar Labs/Thank You|thanks]] to our contributors.

=== [[Sugar Labs/Governance|Governance]] ===
Informed by the above principles, Sugar Labs has a [[Sugar Labs/Governance|governance model]].

{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}

== Subpages ==

{{Special:PrefixIndex/Sugar_Labs/}}

[[Category:General public]]
[[Category:Team]]

Welcome to the Sugar Labs wiki/lang-ps

2009-04-08T15:09:34Z

Dfarning-bot: fix camelcase links

<noinclude>{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]]}}</noinclude>
__NOTOC__
__NOEDITSECTION__

<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar reinvents how computers can be used for education.''' It promotes sharing and collaborative learning and gives children the opportunity to use their laptops on their own terms. Children — and their teachers — have the freedom to reshape, reinvent, and reapply their software, and content. Sugar is based on GNU/Linux, a free and open-source operating system. </p>

[[Image:home_sharing.png|left]]

=== د شوګر اسانتياوې، شريكونه....===

ماشومان كولاى شي، چې يو څۀ وليكي او يا په ګډه سره ټنګ ټكور كمپوز كړي.
<div class="visualClear"></div>

[[Image: home_activities.png|left]]

=== هېڅ دوتنه، لاسوند او يا اپلېكېشن نشته. ===

كوم كار چې تاسې كوئ يواځې يو <em>فعاليت</em> دى، او دا فعاليت د اپلېكېشنونه او ستا ټوله ډېټا او مالومات تشكيلوي.

<div class="visualClear"></div>

[[Image: home_backup.png|left]]

=== دا خبرنه تقريبا د نه منلو ده، چې تاسې خپله ډېټا له لاسه وركړئ. ===

هرڅۀ خوندي دي، او په خپلكاري توګه بياترلاسه كېداى شي.

<div class="visualClear"></div>

[[Image: home_journal.png|left]]

=== ډېټا ته د لاسرسي لپاره تاسې ورځپاڼه كاروئ. ===

It's like a diary of stuff that you made.

<div class="visualClear"></div>

[[Image: home_opensource.png|left]]

=== دا وړيا او پرانيستې-سرچينو ساوتري دي. ===

There are no strings attached and updates will <em>always</em> respect users' freedom.

<div class="visualClear"></div>

==وروستي خبرونه==
* A draft proposal for a governance model for Sugar Labs has been posted to the wiki (Please see [[Sugar Labs/Governance|the governance page]]). Feel free to make corrections and [[talk:Sugar Labs/Governance|add comments]].
* [[Development Team/Release/Releases/Sucrose/0.81.2|Sucrose 0.81.2]] (Development Release) has been released.
* Wolfgang Rohrmoser reports that a new release (080607) of the Livebackup XO-LiveCD is available ([http://dev.laptop.org/pub/livebackupcd/build-708+joyride-2024 XO-LiveCD]).

د شوګرلېب په اړه نورو مالوماتو لپاره، مهرباني وكړئ [[Sugar Labs/Current Events|Current Events page]] وګورئ.

==شوګر لېب څه دى؟==
Sugar is available under the free software GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, a (soon to be established) non-profit foundation will serve as a support base and gathering place for the community of educators and software developers who want to extend the platform and create Sugar-compatible applications. Sugar Labs software is found on the XO laptop. You can find more out about the project at laptop.org.

<p style="font-size: 1.2em;">[[What is Sugar? | Learn more about Sugar...]] or [[Sugar Labs | learn about Sugar Labs, the organization behind Sugar]]'''</p>

== فعاليتونه==

Sugar applications are called [http://wiki.laptop.org/go/Activities Activities]. This is a list of some Activities that are installed by default. There is a proposal for an [[Activity Library]].

<table border="0">
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-journal.png|40px]]
=== [http://wiki.laptop.org/go/Journal ورځپاڼه] ===
Object and activity browser
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-pippy.png|40px]]
=== [http://wiki.laptop.org/go/Pippy پي پي] ===
Python Programming language/environment
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-web.png|40px]]
=== [http://wiki.laptop.org/go/Browse Browse] ===
Web browser based on Mozilla Firefox
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-etoys.png|40px]]
=== [http://wiki.laptop.org/go/Etoys Etoys] ===
Learning / programming / authoring environment
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-read.png|40px]]
=== [http://wiki.laptop.org/go/Read لوستل] ===
Book/PDF reader
</td>
<td width="33%" style="text-align: center;">
[[Image:Activity-turtleart-grey.png|40px]]
=== [http://wiki.laptop.org/go/Turtle_Art د شمشتۍ فن] ===
Pseudo-Logo graphical programming language
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-write.png|40px]]
=== [http://wiki.laptop.org/go/Write Write] ===
Word processor</td>
<td width="33%" style="text-align: center;">
[[Image:activity-calculate.png|40px]]
=== [http://wiki.laptop.org/go/Calculate شمۍرل] ===
Basic calculator
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-news.png|40px]]
=== [http://wiki.laptop.org/go/News_Reader خبرونه لوستونكې] ===
News reader
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-measure.png|40px]]
=== [http://wiki.laptop.org/go/Measure اندازه كول] ===
Oscilloscope and Data Logging
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-draw.png|40px]]
=== [http://wiki.laptop.org/go/Paint رنګول] ===
Simple paint activity
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-acousticmeasure.png|40px]]
=== [http://wiki.laptop.org/go/Distance واټن] ===
Measure distance between two laptops
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-record.png|40px]]
=== [http://wiki.laptop.org/go/Record رېكارډ] ===
Still, video, and audio capture
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-analyze.png|40px]]
=== Analyze ===
An activity version of the Sugar analyze tool
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-log.png|40px]]
=== [http://wiki.laptop.org/go/Log Log] ===
An activity version of the Sugar logging tool
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-terminal.png|40px]]
=== [http://wiki.laptop.org/go/Terminal ټرمينل] ===
An activity version of the Sugar terminal
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-tamtamjam.png|40px]]
=== [http://wiki.laptop.org/go/Tamtam ټم ټم] ===
Music composition and synthesis.
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-chat.png|40px]]
=== [http://wiki.laptop.org/go/Chat بنډار] ===
Collaborative discussion
</td>
</tr>
<tr>
<td width="33%" style="text-align: center;">
=== And more ===
[http://wiki.laptop.org/go/GCompris Dozens more are available].
</td>
</tr>
</table>

==دا هم وګورئ==

[[Image:sugarlabs_logo_big.png|right|150px]]

* [[Sugar Labs/GettingInvolved|Getting involved!]]
* A Sugar [[taxonomy]] and a matrix of [[supported systems]]
* The Sugar [[Development Team/Release]] and [[Development Team/Release/Roadmap]] discussion pages
* Other pages of interest to [[:Category:Developer|developers]]
* A [[Sugar Labs/Background|background]] discussion on [[What_is_Sugar%3F|Sugar]] and [[Sugar Labs]]
* [http://wiki.laptop.org/go/Category:Sugar The Sugar category] on olpcwiki for more.
* Help us [[Design Team/Logo Ideas|design a logo]] for Sugar Labs
* [[Sugar Labs/FAQ|Frequently asked questions]]

[[Category:General public]]

Archive/Current Events/2008-06-09

2009-04-08T15:09:02Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>

=== Sugar Digest ===

1. Software Freedom Conservancy: Sugar Labs is entering discussions
with the Software Freedom Conservancy (Please see
http://conservancy.softwarefreedom.org/overview/). If we are accepted
into the Conservancy, we'd join projects such as Inkscape, Samba, and
Wine. The Conservancy provides member projects with free financial and
administrative services, but does not involve itself with
technological and artistic decisions.

2. Governance: We will be gathering in Milan at the end of the month
of June to discuss, among other things, possible models of governance
for Sugar Labs. More details will follow soon.

3. Linux Foundation: Walter Bender and Jim Zemlin (Executive Director
of the Linux Foundation) met to discuss ways in which we could work
together. The Linux Foundation "hosts collaboration events among the
Linux technical community, application developers, industry, and end
users", manages a "Technical Fellowships Fund" to ensure key projects
get accomplished, and helps promote Linux regionally. Obviously lots
of synergy with the Sugar Labs mission!

4. UMPC abundance: The success of the OLPC XO and the ASUS Eee PC
seems to have attracted the attention of the industry: it has been a
busy week in the world of ultra-mobile PCs. Dell (See
http://www.engadget.com/2008/05/29/dells-mini-inspiron-eee-pc-killer-revealed/),
Acer (See http://www.engadget.com/2008/05/29/first-pics-of-acers-aspire-one-eee-pc-twin/),
Wizbook (http://www.theinquirer.net/gb/inquirer/news/2008/05/28/noon-eee-pc-wizbook-hits),
Elonix (See http://www.desktoplinux.com/news/NS8294433279.html), and
Kanguru (See http://pc.kanguru.pt/Home/) were all making headlines.
Each of these machines represents yet another potential platform for
running Sugar.

=== Community jams and meetups ===

5. PyOhio: Catherine Devlin is helping to organize a regional
miniconference on Python programming Saturday, July 26, in Columbus,
Ohio (Please see http://pyohio.org). Ralph Hyre, a Sugar community
organizer in Cincinnati, suggested that someone might be willing to
present on Sugar (and OLPC project). It is just past the date for
their "call for proposals", but they may be willing to accept a late
submission. (Please email Mat Kovach <matkovach@gmail.com> or call at
216-798-3397.)

===Tech Talk===

6. Sugar tip of the week: How to install activities. There a several
ways to manually install new activities in Sugar:
(A) You can use xo-get from the Terminal activity (See
http://wiki.laptop.org/go/Xo-get for the details). Find activities by
typing:

./xo-get.py list

Install activities by typing:

./xo-get.py install <activity-name>

e.g.,

./xo-get.py install simcity

or

./xo-get.py install /media/<USB stick name>/simcity.xo

(B) You can also install pre-bundled activities from the Terminal
activity or, if you have an XO laptop, from a customization key (See
http://wiki.laptop.org/go/Customization_key):

./sugar-install-bundle /media/<USB stick name>/<Activity name.xo>

(C) You can install activities from the browser, either over the
internet or from USB (See
http://wiki.laptop.org/go/Browse#Install_an_activity for details):

:a. open the Browse Activity
:b. point it to an activity bundle, e.g., http://web.media.mit.edu/~jmaloney/scratch-xo/Scratch-5.xo or file:///media/<USB stick name>/Scratch-5.xo
:c. When the download is complete, a journal entry will have been created. "Resume" the activity from the journal. Hence forth, it will appear in the list of installed activities.

7. SocialCalc: Dan Bricklin has been hard at work on the base
SocialCalc code. In the next few weeks he hopes to have a new build
for availale. It will include a new tab with "Settings" that shows all
of the attributes of the current cell and sheet; it provides access to
all of the formatting options, including custom formats and colors,
padding, fonts, etc. Also, it should be better suited for localization
in that it will have a single Constants file with pretty much all of
the customizable values for the spreadsheet engine (but not the UI
above the sheet yet). At the point of this new release, Dan thinks we
should have something very useful for people to try.

8. Metacity: Sayamindu Dasgupta has been experimenting with replacing
Matchbox with a Metacity as the window manager that runs behind Sugar.
Despite the fact that the Sugar UI is different from a standard
desktop, it is almost completely implemented using standard window
manager hints and properties, thus a move to a more compliant window
manager will make it possible to run standard desktop applications
directly within Sugar (Please follow the discussion at
http://wiki.sugarlabs.org/go/WindowManagement).

A RPM of Sayamindu's patch is available for download
(http://dev.laptop.org/~sayamindu/sugar_metacity/metacity-2.23.21-2.olpc2.i386.rpm),
however, he warns that you should *not* install this patch on your
standard desktop machine yet. Things which have not been resolved yet
include: (1) Some activities tend to go into full screen mode
automatically; (2) Activity switching does not work yet; (3) Some
palettes and windows are placed incorrectly; (4) The mouse cursor
theme switches back to the normal (default??) one; and (5) Memory
usage with compositing enabled is high.

9. Rainbow: Michael Stone released rainbow-0.7.13 with a fix for
#6989, a problem that was interfering with the launching of the Browse
activity.

10. Automated testing: Michael has offered Xen hosting for Sugar Labs'
automated testing efforts. (Xen is a FOSS standard for
virtualization—please see http://xen.org for details.)

11. Wikipedia activity: Chris Ball has made the first release of the
Wikipedia activity, which contains a
30,000 article offline snapshot of the Spanish Wikipedia with 3,000
images. The activity is based on code from Patrick Collison's
"wikipedia-iphone" project; this version was mostly developed by
community volunteers: thanks to Wade Brainerd (porting from the
wikipedia-iphone code to a Python activity, fixing parser bugs), Ben
Schwartz (image download and scaling, bug-fixing) and Madeleine Ball
(algorithms for article and image selection). Please see
http://dev.laptop.org/~cjb/eswiki/ and
http://wiki.laptop.org/go/WikiBrowse for the download and more
details.

12. Chat: Morgan Collett worked on private invites for Chat, although
his final testing was blocked by a palette problem in Sugar. Morgan
has also filed a patch for Ticket #5767 that uses black text on light
fill colors to improve legibility.

13. Browse: Tomeu Visozo has added some more palette options to
content in Browse, including copy, paste, undo, redo commands to the
Browse toolbar. (Tomeu also fixed a problem with activity order in the
activity list and shell.)

14. Icons: Scott Ananian has added a bit of functionality to his
(still incomplete) icon-draw-activity; it is on the path to becoming a
complete "convert SVGs into proper Sugar icons" tool. (Please see
http://dev.laptop.org/git?p=users/cscott/icon-draw-activity for
details.) Scott also filed bugs with improved icons for scratch
(#7140), gcompris (#7138), paint (#7139), turtle art (#6836), and
wikibrowse.

=== Sugar Labs ===

15. LinuxTag: Simon reports that Members of the Sugar community
(Please see http://wiki.sugarlabs.org/go/Image:LinuxTag-2008-Bernie-Reinier-Marco-Simon-Bert-Tomeu.jpg)
met this weekend at the Linuxtag 2008 (http://www.linuxtag.org/2008/)
in Berlin. Besides meeting people in person and the usual putting
faces to names, they discussed the current situation of Sugar: hot
topics Sugar on multiple platforms and the structure Sugar Labs.

Thanks to OLPC Germany and especially to Holger Levsen, there was also
an opportunity to give an introduction to Sugar to the winners of an
Idea Contest (http://wiki.olpc-deutschland.de/Start?action=AttachFile&do=view&target=LinuxTag-2008-OLPC-Deutschland-Developers.jpg).
Robert Krahn gave a tutorial about using Squeak on the XO and Wolfgang
Rohrmoser handed out a
XO-Live CD (ftp://rohrmoser-engineering.de/pub/XO-LiveCD/) to people
who were interested in trying out Sugar on their machines.

16. SOM: Gary Martin has prepared this weeks SOM of the
its.an.education.project list (Please see
http://wiki.sugarlabs.org/go/Image:2008-May-24-30-som.jpg).
Organization and governance seem to be hot topics (The list archive
can be found at
http://lists.lo-res.org/pipermail/its.an.education.project/).

17. Wiki: David Farning has been very busy organizing the Sugar Labs
wiki. His focus has been on building a framework to support teams
within the community:
* Accessibilty Team - Responsible for accessibility issues within Sugar.
* BugSquad - Responsible for locating and fixing bugs.
* Build Team - Responsible for creating daily and release builds.
* Development Team - Responsible for Developing the software modules
within Sugar.
* Documentation Team - Responsible for writing both user and technical
documentation.
* Education Team - Responsible for setting the Educational goals for
the sugar Community.
* Marketing Team - Responsible for marketing the Sugar brand and product.
* Development Team/Release - Responsible for shipping the current release and
planning for up coming releases.
* Sugar Labs - Responsible for governance and fund raising.
* Wiki Team/Translation - Responsible for the translation needs of the community.
* Design Team - Responsible for the User interface.
* Wiki Team - Responsible for the Sugar Labs wiki.

The community portal (http://wiki.sugarlabs.org/go/Community) has a
link to each teams' section within the wiki.

[[Category:Sugar Digest]]

Oversight Board/2008/Meeting Minutes-2008-06-30

2009-04-08T15:07:58Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>

==Sugar Labs meeting, Monday, 30 June 2008==

Via Monte Napoleone, Milano, IT

Attending in person: Marco Pesenti Gritti, Paul Noja, Tomeu Vizoso, Walter Bender, Carlo Falciola, Franco Lodato, Luca Ferrari, Karen Sandler

Participating by [[Sugar_Labs/Meeting_Minutes-30-06-2008/irc-log|IRC (See log)]]: bernie, mostro, mk8, BryanWB, arjs, shenki, jg, cjb, reed, dwmw2, mtd, walter, marcopg

[[Image:Sugar-labs-meeting-milano.jpg|thumb|Sugar Labs meeting in Milano, Via Monte Napoleone]]

;Logs: [[Sugar_Labs/Meeting_Minutes-30-06-2008/irc-log]]

===Governance and the Software Freedom Conservancy===

Karen led a discussion about the implications of Sugar Labs joining the Conservancy. The SFC is a home for FOSS projects as an umbrella organization: FOSS projects become part of the Conservancy; they get tax-free status in the US; and the projects set up a day-to-day governance structure that is generally autonomous.

Shenki asked a question regarding any downsides. While there is always a unilateral mechanism to spin out from the Conservancy, by joining,

# We would be making a commitment to remain a non-profit organization in regard to any project assets (funds that we might raise, any copyrights or trademarks we might own);
# No projects have ever spun out on their own, so there may be some unknown obstacles; and
# There would be some administrative oversight (but we need it from somewhere).

The Conservancy has some concern that Sugar Labs might get so big as to incur too big of a burden for the Conservancy to pick up all administrative expenses without some mutually agreed mechanism of help from Sugar Labs.

Sugar Labs must designate one or two people to be the central point for communicating with the Conservancy regarding expenditures, reimbursements, etc. handled by the Conservancy on our behalf.

Joining the Conservancy means a commitment to both FOSS and non-profit status. However, there is and should be room for for-profit entities to grow up around Sugar Labs, offering support, extra services, such as ports, etc.

A question was raised in regard to working outside of the United States (the Conservancy is a US-based 501(c)(3)); while it hasn't been a problem, if necessary, projects within the Conservancy can work with organizations elsewhere—e.g., the Conservancy could help with administration of non-US programs without having to be involved in the funding—money can be raised and stay local, under local laws.

Karen made some in-line edits (mostly in the form of questions) to the Governance page in the wiki. We need to achieve a bit more clarity about a few topics, such as [[Sugar Labs/Initial Members List|Initial Membership]], terms of office, voting mechanics, etc. as part of the process of joining the Conservancy.

===What are we (Sugar Labs) trying to accomplish?===

Sugar Labs is the focal point for a community project that is providing the engineering and support for Sugar, a FOSS project that is designed to facilitate a collaborative and reflective set of learning activities. Sugar Labs is the upstream maintainer for the work and helps to promote it, but the development work itself is done downstream, in the community, both by volunteers and groups that want to offer services, in some cases for profit. There was consensus that Sugar Labs should manage the release process and the review process.

Bryan posited that the “conceptual integrity” and quality control of Sugar as a product needs to be maintained by Sugar Labs, but that Sugar Labs shouldn't try to constrain the educational approaches used by schools.

Shenki asked how OLPC and RedHat fit in. OLPC (and other platform providers) are downstream and should be pushing patches up to Sugar Labs, making their needs and point of view known to the community. We (the Sugar community) should strive to make our code work for everyone, not just OLPC, so that there is a broader context for support.

It was suggested that we set up a page in the wiki to let people advertise engineering and support services.

===Sugar distributions: what are the issues?===

The bulk of the discussion revolved around what are the best forms of distribution to facilitate people trying Sugar (and if they like it, installing it). We discussed targeting old Windows computers that might be in a school, for example—a version that teachers and students can use.

Carlo suggested that we make a matrix that explains more clearly what you get/don't get from different distribution models, such as a LiveCD, QEMU, etc. It was suggested that distributing Sugar on a USB image is perhaps the best option, since it lets you install additional activities, save files, etc.

Another topic was the need for better documentation: for example, the Sugar session on Ubuntu: Lot of undocumented little details, such as you cannot log out, so you need to either restart X (Ctrl-Alt-Backspace) or do a reboot (from the shell or the Homepage menu); and that you can copy activities directly into ~/Activities. The FLOSS Manuals project has offered to help with documentation; we are considering using the existing Trac system for documentation requests, bug reports, etc.

===Sugar Labs look and feel: a graphic design review===

Luca Ferrari and Franco Lodato presented some designs for a “corporate identity” for Sugar Labs. The designs are [[Design Team/Logo Ideas#Designs_by_Luca_Ferrari_and_Franco_Lodato|posted in the wiki]] for feedback. (Karen pointed out the importance of trademarks with in the context of FOSS projects.)

===Sugar on mobile phones: is it possible? does it make sense?===

We also had a discussion about mobile devices. This is a topic that has been raised repeatedly in recent months and, while it doesn't seem to have a direct connection to Sugar's educational goals, it does seemingly broaden the developer community for Sugar (“growing the community”) and bring more people into the circle of collaboration with learners using Sugar-enabled devices.

Further, Sugar would probably make a pretty decent phone interface, especially in light of its clarity of design and its collaborative model.

Still, it was argued that a cellphone screen is a bad environment for learning and that it would not be a substitute for a laptop. Chris Ball asked, “What are the minimum requirements for expressiveness and learning when we work on a port of Sugar?”

We had some discussions about what would be involved in such a port and whom might be interested in doing it. (The Nokia N800 was suggested as a possible point of departure.)

===Sugar Labs: models of support===

This was in part a continuation of the discussion about purpose. The issue of long-term stability—both perception and reality were discussed: up-take of Sugar will be increased if there is a sense that it is going to be here and supported for the long run. It was argued that we need to help establish local and regional champions, ownership, and support.

:In “biologically inspired” architectures one is much more interested in how the organism and ecologies of them are to be sustained, and how the dynamical systems can be understood, fixed, changed, evolved, reformulated, etc., while they are running and with the help of tools that work within them. Just as a cell, and especially e. g. a human baby, is not made by hand, we are more interested in making growth processes that can be influenced with far more ease than direct construction. So, most objects are made by other objects acting under conditions that include the dynamic state in which they will become part of the ecology. —Alan Kay

What are the Sugar growth processes?

===Fund-raising: how much and from whom?===

We didn't really get into this topic in any detail accept to agree that order 10s of thousands of dollars would probably be adequate for currently anticipated needs: meeting support, outreach, etc.

We do need to discuss what venues would be useful in light of reaching both the developer and user (primarily learning) communities.

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

Oversight Board/2008/Meeting Minutes-2008-09-05

2009-04-08T15:07:05Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>

== Oversight Board Meeting Minutes 2008-09-05 ==

;Logs: [[Sugar Labs/OversightBoard/Minutes/Log-2008-09-05]]
;Attending: walter, gregdek, marcopg, tomeu, erikos, bernieXO (AKA NerdyNipple-f169), dfarning, cjb, cjl, davidb

The Oversight Board acknowledged and celebrated the great job Simon has been doing on managing the 0.82 release.

=== Administrative ===

* OB meeting protocols
:''We'll appoint someone to take minutes each meeting; We'll announce the meetings on the Sugar and IAEP lists (they are already announced on Sugar Digest and in the wiki). Agendas are set in the wiki.''
* Additional OB representatives (learning, design, deployment)
:''We agreed that having representation from these areas is important. We'll make explicit invitations to ensure these voices are heard. Walter will follow up.''
* Finalize SFC agreement
:''Moving ahead, but still waiting for final agreement from SFC for the OB to sign.''
* Appoint (Membership)
: Dfarning will organize/liaison with the Membership committee; Gregdek will organize/liaison with the Events committee; Bernie will organize/liaison with the Infrastructure committee; Simon will organize/liaison with the Test committee; Walter will organize/liaison with the Deployment committee''
* Appoint Ombudsman
:''If Bert is willing, we'd like to make his acting role permanent.''
* Proposals
: ''We discussed a process whereby Sugar Labs vets proposals: a public discussion of the general ideas and an approval by the OB regarding the specifics.''
* Fund raising
: ''Walter will prepare a report for the next meeting about various possibilities. The idea of helping external groups form to share in the development and support burden was seen as a favorable strategy. Raising money for "events" was seen as important.''
* Logo
: ''We discussed a new logo proposal (See'' [[Design Team/Logo Ideas#Christian.27s_take_on_this_theme|'''sugar'''labs]]'') and agreed to have Christian Schmidt take charge of this decision.''

=== Infrastructure status ===
* Hardware
* Hosting
* @sugarlabs.org
: ''We agreed to give members email addresses at sugarlabs.org''
* etc.

=== Key issues ===
* Engineering
** Ports
** Stability
** QA
** Updates
** Accessibility
: ''Walter will follow up with a UT proposal to partner in an accessibility proposal. We need someone to volunteer to champion this effort.''
** growing the community of contributors
* Learning
** Outreach
** Feedback
** growing the community of contributors

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

Welcome to the Sugar Labs wiki/lang-ru RU

2009-04-08T15:06:23Z

Dfarning-bot: fix camelcase links

<noinclude>{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ru_RU|русский]] |}}</noinclude>
__NOTOC__
__NOEDITSECTION__
<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar переосмысляет то, как компьютеры можно использовать в образовании.''' Sugar развивает совместное обучение, способность делиться с другими своими знаниями, и способность рефлексировать. Благодаря присущей Sugar "прозрачности идеи (design)", дети и их учителя могут использовать вычислительную технику именно для своих целей; они могут свободно вносить изменения, заново изобретать, и по новому использовать как программное обеспечение, так и учебные материалы, преобразуя их в мощный инструмент разнообразной образовательной активности (activities). Sugar - это проект [[Sugar Labs/GettingInvolved|сообщества]]; он основа на GNU/Linux, свободно распространяемой операционной системе с открытыми исходными текстами.</p>

[[Image:home_sharing.png|left]]

=== Sugar облегчает сотрудничество и дает возможность делиться своими знаниями. ===

Дети с легкостью пишут тексты, деляться книгами и картинами, или вместе создают музыку.

<div class="visualClear"></div>

[[Image: home_activities.png|left]]

=== Нет никаких файлов, папок или программных приложений. ===

Основная единица взаимодействия - <em>активность (activity)</em>; он включает как соответствующее приложение, данные, так и историю взаимодействия с тем, чтобы можно было возобновить эту активность в любой момент.

<div class="visualClear"></div>

[[Image: home_backup.png|left]]

=== Практически невозможно потерять данные. ===

Все сохраняется и копируется автоматически.

<div class="visualClear"></div>

[[Image: home_journal.png|left]]

=== Журнал используется для доступа к данным. ===

Журнал - это дневник тех вещей, которые Вы сделали и тех действий, которые вы совершили; это место, где можно размышлять о проделанной работе.

<div class="visualClear"></div>

[[Image: home_opensource.png|left]]

=== Sugar - свободно распространяемое программное обеспечение с открытыми исходными текстами. ===

Sugar выпускается под лицензией [http://www.gnu.org/licenses/gpl.html GPL]; обновления будут <em>всегда</em> уважать свободу его пользователей и дальше.

<div class="visualClear"></div>

==Последние новости==
* Мы находимся в процесс интенсивного писательского усилия с целью создать руководство по использованию Sugar. Пожалуйста, следите за нашими успехами на [http://en.flossmanuals.net Floss Manuals]. Вы всегда можете создать собственный аккаунт и помочь с написанием, иллюстрированием и редактированием.
* [[User:Aaron|Aaron Kaplan]] спортировал Sugar на Intel Classmate 2. Вы можете прочитать об этом на [http://www.olpcnews.com/software/operating_system/sugarizing_it_intel_classmate_2.html здесь].
*[[Development Team/Release/Releases/Sucrose/0.82|Sucrose 0.82]] (Development Release) has been released.
* Мы начали процесс выборов наблюдательного совета Sugar Labs; опрос заканчивается 31 августа. Список кандидатов можно найти [[Sugar_Labs/Oversight_Board_Candidates_August_2008|здесь]].
* [[Sugar_Labs/OversightBoard/Minutes#Friday_1_August_2008_-_14.00_.28UTC.29|Протокол]] заседания Sugar Labs от 1 августа 2008 года.
* Sugar получил серебряную медаль на International Design Excellence Awards '08 (См. [http://www.idsa.org/IDEA_Awards/gallery/2008/award_details.asp?ID=772])
* Модель структуры управления Sugar Labs размещена на странице wiki (Пожалуйста, смотрите [[Sugar Labs/Governance|страницу структура управления (the governance page)]]). Вы можете оставить свои [[_talk:Sugar Labs/Governance|комментарии]].

* Wolfgang Rohrmoser сообщает, что доступен новый релиз (080607) Livebackup XO-LiveCD ([http://dev.laptop.org/pub/livebackupcd/build-708+joyride-2024 XO-LiveCD]).

Чтобы прочитать о других новостях Sugar Labs, пожалуйста, посетите [[Sugar Labs/Current Events|страницу текущих событий]].

==Что такое Sugar Labs?==
Sugar доступен под лицензией открытого программного обеспечения GNU General Public License (GPL) каждому, кто хочет распространять его. “Sugar Labs” - некоммерческий фонд, который вскоре будет создан и который будет призван служить поддержкой и местом сбора сообщества педагогов и разработчиков программного обеспечения, которые хотят развивать эту платформу и создавать совместимые с Sugar программные приложения. Программное обеспечение Sugar Labs устанавливается на лэптоп XO. Вы может найти дополнительную информацию об этом проекте на сайте laptop.org.

<p style="font-size: 1.2em;">[[What is Sugar? | Узнать больше о Sugar...]] ли [[Sugar Labs | узнать больше о Sugar Labs, организации, стоящей за Sugar]]</p>
<p style="font-size: 1.2em;">[[Sugar Labs/GettingInvolved | Как участвовать]] в [[Development Team | разработке]] Sugar и усилиях [[Sugar Labs/GettingInvolved#Join_a_Team | сообщества]].</p>

==Попробуй Sugar/Скачай Sugar==
''Попробуй'' Sugar, запустив его поверх используемой тобой системы (Пожалуйста, смотрите страницу [[Downloads|Попробуй Sugar]]).

Есть много способов ''скачать'' Sugar: как '''[[Supported_systems#Starch|отдельный образ диска]]''' для существующей машины; как '''[[Supported_systems#Sucrose|сессию в дистрибутиве Linux]]'''; или как часть '''[[Supported_systems#Systems|законченной программно-аппаратной платформы]]'''. (Пожалуйста, смотрите инструкции по загрузке Sugar для Вашего дистрибутива Ubunty на [[Community/Distributions/Ubuntu|Sugar на Ubuntu]].)

== Активности ==
Приложения Sugar называются [http://wiki.laptop.org/go/Activities Активности]. Вот список некоторых активностей, которые устанавливаются по умолчанию. Это предложение по [[Activity Library | Порталу активностей]].

<table border="0">
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-journal.png|40px]]
=== [http://wiki.laptop.org/go/Journal Journal] ===
Браузер объектов и активности
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-pippy.png|40px]]
=== [http://wiki.laptop.org/go/Pippy Pippy] ===
Язык/среда программирования Python
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-web.png|40px]]
=== [http://wiki.laptop.org/go/Browse Browse] ===
Веб-браузер на основе Mozilla Firefox
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-etoys.png|40px]]
=== [http://wiki.laptop.org/go/Etoys Etoys] ===
Среда для обучения / программирования / творчества
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-read.png|40px]]
=== [http://wiki.laptop.org/go/Read Read] ===
Инструмент для чтения книг / PDF
</td>
<td width="33%" style="text-align: center;">
[[Image:Activity-turtleart-grey.png|40px]]
=== [http://wiki.laptop.org/go/Turtle_Art Turtle Art] ===
Псевдо-Logo графический язык программирования
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-write.png|40px]]
=== [http://wiki.laptop.org/go/Write Write] ===
Текстовой редактор</td>
<td width="33%" style="text-align: center;">
[[Image:activity-calculate.png|40px]]
=== [http://wiki.laptop.org/go/Calculate Calculate] ===
Простой калькулятор
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-news.png|40px]]
=== [http://wiki.laptop.org/go/News_Reader News Reader] ===
Инструмент для чтения новостных лент
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-measure.png|40px]]
=== [http://wiki.laptop.org/go/Measure Measure] ===
Oscilloscope and Data Logging
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-draw.png|40px]]
=== [http://wiki.laptop.org/go/Paint Paint] ===
Простой инструмент для рисования
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-acousticmeasure.png|40px]]
=== [http://wiki.laptop.org/go/Distance Distance] ===
Измеритель расстояния между двумя лэптопами
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-record.png|40px]]
=== [http://wiki.laptop.org/go/Record Record] ===
Инструмент для записи аудио, видео и фото
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-analyze.png|40px]]
=== [http://wiki.laptop.org/go/Analyze Analyze] ===
Инструмент Sugar для анализа системы как активность
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-log.png|40px]]
=== [http://wiki.laptop.org/go/Log Log] ===
Инструмент Sugar для чтения логов как активность
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-terminal.png|40px]]
=== [http://wiki.laptop.org/go/Terminal Terminal] ===
Терминал Sugar как активность
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-tamtamjam.png|40px]]
=== [http://wiki.laptop.org/go/Tamtam TamTam] ===
Инструмент для сочинения и синтеза музыки.
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-chat.png|40px]]
=== [http://wiki.laptop.org/go/Chat Chat] ===
Инструмент для коллективных обсуждений
</td>
</tr>
<tr>
<td width="33%" style="text-align: center;">
=== И многое другое ===
[http://wiki.laptop.org/go/GCompris Вам доступны много десятков других активностей].
</td>
</tr>
</table>

==Смотрите также==

[[Image:sugarlabs_logo_big.png|right|150px]]

* [[Sugar Labs/GettingInvolved|Как участвовать!]]
* [[taxonomy|Таксономия]] Sugar и таблица [[supported systems|поддерживаемых систем]]
* The Sugar [[Development Team/Release]] and [[Development Team/Release/Roadmap]] discussion pages
* Другие страницы, интересные [[:Category:Developer|разработчикам]]
* [[Sugar Labs/Background|Обсуждение]] основополагающих принципов, лежащих в основе [[What_is_Sugar%3F|Sugar]] и [[Sugar Labs]]
* Смотрите [http://wiki.laptop.org/go/Category:Sugar категорию The Sugar] на olpcwiki для получения дополнительной информации.
* Помогите нам с [[Design Team/Logo Ideas|дизайном логотипа]] Sugar Labs
* [[Sugar Labs/FAQ|Часто задаваемые вопросы (FAQ)]]

[[Category:General public]]

Design Team/FAQ

2009-04-08T15:05:49Z

Dfarning-bot: fix camelcase links

Wiki Team/Meetings

2009-04-08T15:05:17Z

Dfarning-bot: fix camelcase links

Category:Sugarlabs logo

2009-04-08T15:04:50Z

Dfarning-bot: fix camelcase links

This is a category for logo/mascot ideas. Look on the page [[Design Team/Logo Ideas]] for more ideas not included in the category.

Marketing Team/Meetings/12-9-2008

2009-04-08T15:04:20Z

Dfarning-bot: fix camelcase links

<pre>
<gregdek> All right.
Agenda:
http://sugarlabs.org/go/MarketingTeam/TODO
From the top.
* tomeu1 puts greg's word in his pocket
<gregdek> 1. Make the "Get Involved" page amazing.
So I put together a high-level "Get Involved" page, and it's a start.
But I'd hardly call it amazing yet.
<caroline_> I think there should be a link to Get involved under Get Help too
<gregdek> Is there any chance we could move the sidebar "Get Involved" up to the top left?
caroline_: Exactly.
<caroline_> are thre supposed to be images?
<gregdek> We *did* but a "Get Involved" link on the left nav, but we put it at the bottom. It should be at the top.
Christian from Pentagram will take this page and create some killer images.
<marcopg> someone (caroline?) made the point that the page seemed to be more about sugar labs organization then about ways to get involved
<caroline_> Greg, this is looking pretty good.
<gregdek> We're waiting on his design of the static Sugar site, which the "Get Involved" page will also be a part of.
<caroline_> the new one is much better
<jt4sugar> can you put link on marketing team page
--> walter (n=chatzill@209-6-218-51.c3-0.nwt-ubr2.sbo-nwt.ma.cable.rcn.com) has joined #sugar-meeting
<marcopg> oh wow
this is not the page I had in mind!
<tomeu1> gregdek: do you know if christian has all the text blurbs he was needing?
<walter> oh wow what
<marcopg> looks great
hehe
hi walter
about new GettingInvolved page
<walter> I owe him some text still
<caroline_> I think we also need to assume that people who want to write content and lesson plans will go through this page and we should point them to where tey need to go.
<walter> hello to all...
<caroline_> actually I think the content writer is a good start
<dirakx> i have to send him also some text /me just lurking
<walter> aside: SFC finally issued a press release about Sugar Lans and we are listed on their member projects page!!
<caroline_> Maybe change content writer to Writer then make it clear we need marekting, documentation and educatiol content and how to contriubute in those areas.
<marcopg> walter: awesome :)
<caroline_> Also I'd like to see "Teacher" explictly somewhere.
<gregdek> I'm still uncomfortable with the absence of particular calls to action.
--> erikos (n=erikos@e178192044.adsl.alicedsl.de) has joined #sugar-meeting
<caroline_> Agreed, its a deep issue beyond just text. We really don't understand what we want people to do specifically it feels like. how we want them to start engaging.
<gregdek> Yep.
This is where the notion of "on-ramp" projects is useful. And I'm still not clear what those projects are.
<tomeu1> erhaps we should see at stuff that people have done after popping into sugar scene
<walter> I think if we link to the per-term TODO pages, we address this issue.
<tomeu1> and try to make more easy to replicate that
<gregdek> walter: I think that helps, yes.
<walter> But we need to flesh out those pages too.
<gregdek> Which is on the team leads.
So how about...
<caroline_> I also think QA needs to be our biggest onramp. Is Mel here today?
* erikos looks up because of the word QA
<caroline_> Try Sugar and let us know what doesn't work, then let us know what cool things you'd like it to do, then help us make those happen.
* gregdek hrms.
<gregdek> We need better TODO pages, so let's all do our best to make our TODO pages actionable.
<walter> +1
<gregdek> Once we've done that, let's modify the Getting Started page to reflect that.
<erikos> caroline_: about the exact use cases for the QA team (bugsquad, testing group) we meet tomorrow
<caroline_> erikos I'll try to make it. Ping me if you can.
<erikos> caroline_: ok sure - it is 16.30 (UTC)
once those are defined we have to clean up the wiki for sure
<marcopg> gregdek: I'll try to come up with better TODO for dev this week, and discuss it in the weekly meeting
<gregdek> OK.
Also: walter, any objection to moving the "get involved" link to above the fold in the left nav, right under "get help"?
<walter> no objection. It is part of the standard template that David designed, so we'll have to make an exception for the front page
<gregdek> Wait... why? Shouldn't it be in the template?
--> cjl (n=chatzill@12.44.50.248) has joined #sugar-meeting
<walter> you are right. I misunderstood.
<gregdek> ok. :)
<walter> I can make the change.
<gregdek> Very good.
<jt4sugar> Need very basic How to on each page for newcomers
<gregdek> jt4sugar: That's what we hope the get involved page will be.
Moving on...
<caroline_> I think the project has an incredible supply and potential supply of enthusiastic volunteers and a huge need for leaders with intiative.
sorry,
<gregdek> 2. Create a sponsorship program.
(sok, caroline_, agreed, I just want to keep moving.)
So I've got that walter will check in with us on this next week.
<caroline_> agreed!
<gregdek> Unless walter has something to tell us this week, we can move on. walter?
<walter> nothing new excpet I am spending the rest of the day defining what a local sugar labs is...
<tomeu1> nice
<gregdek> walter: Brilliant!
All right, moving on:
3. Elevator Pitch.
Looks like we've got tons of pitches:
http://sugarlabs.org/go/MarketingTeam/ElevatorPitch
We can generate more, we can vote on the ones we have, and so on and so on.
One thing I *would* like to do:
Put the winning pitch on the business card.
<marcopg> how do we go about figuring out the winning one? ;)
<gregdek> But I think we've got a bit of work to do yet before we get there.
marcopg: Exactly. :)
<caroline_> I wonder if we can get some votes by people not in our community. because how it plays to an outsider seems more important then whether us insiders like it
<gregdek> caroline_: Good point. What do you suggest?
<marcopg> caroline_: good point
<caroline_> I can mail my TIE school cohort when we are ready that is about 30 people.
<gregdek> That would be great.
<caroline_> maybe mail some outside mailing lists that are friendly?
<tomeu1> sounds a pretty good idea
<jt4sugar> Narrow down to top ten-ask friends
<walter> also, Greg, let's run our ideas past Dennis and Scott
<caroline_> also we can ask people to email friend and family and put up a poll.
<marcopg> I wonder if we should also give more opportunities to the community to write pitches
<gregdek> We can do all of these things.
<marcopg> it was probably asked only in meetings and marketing list
<gregdek> The question is, in what order?
Well, I did make the pitch announce beyond marketing-list.
<marcopg> walter: who are Dennis and Scott?
<marcopg> gregdek: aaah ok, ignore me then!
<marcopg> was just a little surprised that not many people contributed
<gregdek> Dennis and Scott are marketing pros.
<walter> Dennis and Scott are volunteers who are professional marketers
<gregdek> walter: I will ask them this week.
<marcopg> ah great
<gregdek> So let's give this another week or two to bake, see how many pitches we can get, and then hand to caroline_ and others to get some independent evaluation, how does that sound?
<caroline_> +1
<walter> when we do ask people, we should take the author names off.
<marcopg> sounds good
<gregdek> walter: Yes, we can do that.
<jt4sugar> +1
>walter< Remind me of Dennis and Scott's last names again?
<gregdek> OK, moving on:
4. Get everyone's blog aggregated at planet.sugarlabs.org.
How's this going?
* gregdek looks.
* marcopg has setup a blog
marcopg didn't yet convince himself to post
<marcopg> (in general going pretty well I think!)
* tomeu1 hasn't managed yet to get erikos and marcopg to _read_ his blog
<gregdek> The blurb is good, but we're flat at 23 feeds since last week.
<marcopg> tomeu1: huh? I do read it :)
<tomeu1> marcopg: ok, then write comments!
* erikos is about to set up his blog as well
<gregdek> So if we're doing it right... pl.sl.o becomes the place where we all go to see "what's interesting" at a high level.
<caroline_> can I get an RSS feed of the aggregation to feed into google reader?
<gregdek> caroline_: Yep.
<marcopg> tomeu1: will do, or will answer from my blog ;)
<unmadindu_> gregdek: it may make sense to add a bit of blurb on the planet page itself on how to get added to the planet
<gregdek> unmadindu_: YES.
<marcopg> there is
not very visible
<gregdek> Oh, wait, it's there. :)
<caroline_> Contact the planetmaster to see your blog added here.
<gregdek> That's sufficient, I think.
<unmadindu_> oops - sorry :-P
yes
<gregdek> So unmadindu_, contact the planetmaster. ;)
<marcopg> hehe
* unmadindu_ does that
<gregdek> Anyway, blurb is done and that's good, so some progress.
<marcopg> yup blurb is very nice
<gregdek> Moving on...
5. Business card design.
<marcopg> people like scott and tomeu started to post more also, which is progress too ;)
(and mchua)
<gregdek> I guess the card design is done, yes?
Can someone remind me of the url?
<walter> I put a series of images in the wiki...
* gregdek searches the wiki without success...
<gregdek> having a page titles "business cards" might help... hm.
<marcopg> http://lists.sugarlabs.org/archive/marketing/2008-December/000028.html
<gregdek> Ah, good.
* gregdek looks under Design Team.
<marcopg> so http://sugarlabs.org/go/Design Team
might be good to have examples of the finished card
so that people sees what they can get in the end
<gregdek> Why doesn't that page show up under "business cards" when I search the wiki? Weird. The text "business cards" is right there.
Hm.
Well, those are just images, anyway.
That's not exactly what I'd consider a "finished" business card, with sample text and so forth.
But maybe you don't need all that stuff with Moo.
<marcopg> right, that would be cool to have
<walter> The idea is that the image is on one side and text (of some sort) is on the other...
<gregdek> OK.
<walter> With a moo card, you enter the text when you order them: up to 6 lines.
We could come up with some sort of template.
<gregdek> Yeah, I think that's what we need.
Another thing:
Who does Moo serve>
?
Is it global?
<walter> (It is something I asked Christian about, because the format is awkward)
Moo is a UK company and I think they ship anywhere
<gregdek> http://fedoraproject.org/wiki/Business_cards
<marcopg> yup
<jt4sugar> Person name on front-getting involved info on back
<marcopg> right there in the homepage:
MOO ships all over the world. Find out more about Christmas delivery dates
<gregdek> So I'm a bit leery of yoking us to a single vendor, I must say, especially a vendor that has a non-standard card format.
<caroline_> people can still do thier own thing
I like the nonstandard format, it goes with out out of the box image
<walter> Yeah. Christian was looking into other ways to get cards made, cheaply.
<marcopg> maybe we should provide both moo and something more standard
<gregdek> They can. I just want to make it *dead easy*.
marcopg: +1.
<jt4sugar> Template with Fed-ex kinkos
<walter> moo is dead easy
<tomeu1> gregdek: what uses fedora for the ambassadors, etc?
<gregdek> I don't want people to have to think too much about "how should my card look".
tomeu1: Mostly, Fedora ambassadors print their own.
From the link that I provided.
<walter> well, let's ask Christian to design a standard card... we have a moo solution already
<tomeu1> oh, sorry
<gregdek> walter: Does Christian have time?
It would be great for everyone to have their own cards by FUDCon... :)
<walter> I think can do this pretty quickly.
<gregdek> OK.
I will leave this to walter, who will proxy to Christian.
<cjl> gregdek: where is agenda and what stage are you at . . . and which meeting is this? :-)
<gregdek> cjl: Sugar marketing.
Agenda at: http://sugarlabs.org/go/MarketingTeam/TODO
And we just finished our agenda.
<cjl> thanks
<gregdek> New business... caroline_?
<caroline_> I think this falls under marketing.
<walter> FYI, I just sent email to Christian to ask if he has time to make a template
<caroline_> I think teachers are a key demographic to market to.
<-- msata (n=ceibal@r190-0-131-42.dialup.adsl.anteldata.net.uy) has left #sugar-meeting
<caroline_> Moodle seems to have been sucessful due to teacher involvement
and if we want to impact education, clearly we need more then Geeks to do it!
so one thought I had with Mel was "end user" workshops for teachers and parents.
<walter> According to Nicholas, the teachers are the problem... or was that the software is the problem?
<cjl> Caroline_ walter are you guys familiar with http://www.exelearning.org/ ?
<gregdek> (thanks walter)
<cjl> These New Zealanders are up to something interesting, they would be good people to be in touch with, getting exelearning onto the XO would seem to be a perfect complement to having Moodle on the XS
It fills an important gap in that it is a teacher's tool for authoring content (without needing to know XML) that exports Moodle-compatible packages (also compatible with other courseware-type systems).
<gregdek> So my thoughts:
1. brilliant idea.
<caroline_> I have a classmate at Harvad with 14 years of teaching experience and teacher professional training experience.
<gregdek> 2. a whole new project.
<walter> @cjl: I am not familiar with it.
<gregdek> 3. a whole new team for governance purposes, perhaps.
<tomeu1> walter: I think someone should introduce the teachers in olpc-sur to NN, he may be surprised
<walter> I am chasing after Lesley University, the leading teacher training college in the US. I want access to their alumni...
<jt4sugar> Teachers are the conduit-must get them on board
<caroline_> my thought is we should get her, or someone, to create and give reusable, intro to Sugar workshops.
<walter> @tomeu: I think he must have meant teachers writing software is the problem :)
<tomeu1> yes, I think SL realizes that teachers have an important role to play
<caroline_> If we charge even a modelst amount for them we should be able to cover the cost of the internship, as she has workstudy money so we only pay 30%.
<tomeu1> heh
<walter> We were making some progress a few years ago: I got FISL to add a teachers day to the end of the conference.
<caroline_> and she speaks some spanish so she can get help from the Sur list.
<jt4sugar> Teacher-Sit beside the Developer program
<walter> My DML proposal--which I haven't heard back on yet--was to do the same at all the major Linux venues
<gregdek> Ok, so a lot of ideas here.
How do we transform these ideas into action?
<walter> We need to offer a certification... one more reason to get Lesley involved
Capture them as action items in the TODO list to start
<caroline_> have you talked to Lesley, whats our path on that?
<walter> I am working my way through the bureaucracy.
I have good people inside getting me to the decison makers
<jt4sugar> Evangeline may have good thoughts on this
<walter> +1
* gregdek is now a mere secretary, waiting for action items to fall out. :)
<gregdek> In fact...
<caroline_> nod, do you want me to take more action on the Harvard intern or wait?
<gregdek> ...I'm afraid I have to run.
So let's do this:L
<tomeu1> jt4sugar: aha! you are john tierney
<gregdek> caroline_: Can you boil this down a bit and add some items to the agenda for next week?
<walter> JT would make a great member of the Education team!!
<tomeu1> yup
jt4sugar: nice to have you around here, btw
<caroline_> wil do
<jt4sugar> Thanks
<gregdek> All right.
Hate to meet-and-run, but I'm out.
A reminder:
If you have any marketing issues you want to address, just ADD THEM TO THE TODO.
* gregdek bangs gavel.
<gregdek> Oh...
5... 4... 3... 2... 1...
1/2...
* gregdek bangs gavel.
</pre>

Human Interface Guidelines/Introduction/lang-pt-br

2009-04-08T15:03:42Z

Dfarning-bot: fix camelcase links

<noinclude><div style="background-color: #F5F5F5;">
{{OLPC}}
{{Translation | lang = pt | source = OLPC Human Interface Guidelines/Introduction | version = 25009 | source_display = OLPC-HIG-Introduction}}

</noinclude>
<div style="background-color: #FFF; margin-left:auto; margin-right: auto; border-left:1px solid #888; border-right:1px solid #888; width: 95%;">
{{hig-nav-lang|prev=Introduction|curr=Introduction|next=Core Ideas|lang=pt-br}}
<div style="margin: 8px;">

{{anchor|Introduction}}
==Introdução==

{{anchor|Who Should Read This Document}}
===Quem deve ler esse documento===

Essas diretrizes têm como principal foco desenvolvedores que estão construindo ferramentas para o laptop da OLPC. Ela provê um visão aprofundada das diversas funcionalidades do [[Sugar]], a interface gráfica do laptop, e focam nas partes da UI que se referem diretamente ao desenvolvimento do software e as diversas formas nas quais as aplicações, chamadas de "[[Design Team/Human_Interface_Guidelines/Activities/lang-pt-br|atividades]]," interagem com o sistema operacional.

Entretanto, como essas diretrizes tem o objetivo de propiciar uma visão geral compreensível da interface gráfica, essas páginas também devem ser de interesse geral. Espera-se que a descrição dos vários elementos da interface gráfica, especialmente na seção [[Design Team/Human_Interface_Guidelines/The_Laptop_Experience/lang-pt-br|Laptop Experience]], irão saciar a sede de todos que desejam compreender melhor o projeto e seus objetivos.

{{anchor|How to Read This Document}}

===Como ler este documento===

Sem dúvidas, muitos daqueles que estão lendo esse documento já leram ao menos um guideline de interfaces no passado. No entanto, nós solicitamos que você leia o conteúdo desse documento na integra. Muitos dos termos aqui contidos serão bem familiares. Nós incentivamos que você os revise de qualquer forma, pois nossa abordagem para a experiência do usuário foge do modelo tradicional. Sendo assim, esse documento pode introduzir algumas idéias não familiares sobre esses termos familiares em outras circunstâncias e os quais você deve considerar ao longo do desenvolvimento.

Enquanto nós incentivamos você a ler esse documento uma vez do início até o final, o uso extensivo de tanto hiperlinks internos quanto externos permitem que você se aprofunde no conteúdo segundo sua vontade. Espera-se que isso permita a visitação de partes específicas dos guidelines de forma rápida e fácil, e permite que você encontre mais facilmente os detalhes que estão mais pertinentes a você. Adicionalmente, o documento foi formatado em uma estrutura de três camadas — documento, capítulos e páginas. Sinta-se a vontade para ler o documento por completo para ter uma visão geral ou imprimí-lo, ou usar a navegação integrada para ir para um capítulo ou página a qualquer momento.

{|border=1 cellpadding=1 cellspacing=0 style="float: right; width: 175px; border: 1px #666666 solid; border-collapse: collapse; background: #f9f9f9;"
!style="background:#D6784C"|API Reference
|-
|Inline references to related APIs appear throughout.
|}

Além disso, quando pertinente, nós incluímos links para as APIs de forma a fazer as relações entre o design e a implementação mais claros. Por favor, beneficie-se disso a medida em que desenvolve para o laptop.

{{anchor|Providing Feedback}}
===Retornando o Feedback===

Esse documento ainda encontra-se em estado de fluxo a medida em que o projeto avança. Nós valorizamos qualquer feedback que você posso ter, e gostaríamos de pedir que você compartilhe qualquer idéia ou sugestão por meio das páginas de discussão(''talk pages''). As discussões serão em torno de cada camada do documento, se você possuí comentários específicos, por favor incluá-os na discussão da página correspondente. Para comentários mais gerais, sinta-se livre para utilizar as páginas de discussão(talk pages) no nível do capítulo ou do documento como um todo. Os links para as páginas de discussão encontam-se próximos aos cabeçalhos das seções.

<br clear='all'>
</div>{{hig-nav-lang|prev=Introduction|curr=Introduction|next=Core Ideas|lang=pt-br}}</div>
<noinclude>

</div></noinclude>

Welcome to the Sugar Labs wiki/lang-pt BR

2009-04-08T15:02:38Z

Dfarning-bot: fix camelcase links

<noinclude>{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]]}}</noinclude>
__NOTOC__
__NOEDITSECTION__

<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar reinventa como os computadores podem ser utilizados para a educação.''' Promovendo o compartilhamento e a aprendizagem colaborativa, dando às crianças a oportunidade de utilizar seus portáteis em sus proprios termos. As crianças — e seus professores — têm a libertade para reformular, reinventar e refazer seu software e o seu conteúdo. Sugar é baseado em GNU/Linux, um sistema operacional livre e de código aberto. </p>

{{ Translated text |
<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar reinvents how computers can be used for education.''' It promotes sharing and collaborative learning and gives children the opportunity to use their laptops on their own terms. Children — and their teachers — have the freedom to reshape, reinvent, and reapply their software, and content. Sugar is based on GNU/Linux, a free and open-source operating system. </p>
| display = none }}

[[Image:home_sharing.png|left]]

{{anchor|Sugar facilitates sharing and collaboration}}

=== Sugar facilita o intercâmbio e a colaboração. ===

As crianças podem escrever documentos ou fazer música juntos com facilidade.

{{ Translated text |
Children can write documents or make music together with ease.
| display = none }}

<div class="visualClear"></div>

[[Image: home_activities.png|left]]

{{anchor|There are no files, folders or applications}}
=== Não há arquivos, pastas ou aplicações. ===

O que você faz é uma <em>atividade</em> que inclui a aplicação e todos os seus dados. Se pode reabrir qualquer atividade em qualquer momento.

{{ Translated text |
What you do is an <em>activity</em> and that includes the application and all your data.
You can resume any activity at any time.
| display = none }}

<div class="visualClear"></div>

[[Image: home_backup.png|left]]

{{anchor|You can hardly lose data.}}
=== Dificilmente se pode perder os dados. ===

Tudo é guardado e são feitas cópias de segurança automaticamente.

{{ Translated text |
Everything is saved and backed up automatically.
| display = none }}

<div class="visualClear"></div>

[[Image: home_journal.png|left]]

{{anchor|You use a journal for accessing data.}}
=== Você usa um diário para acessar os dados. ===

É como um diário das coisas que você fez.
{{ Translated text |
It's like a diary of stuff that you made.
| display = none }}

<div class="visualClear"></div>

[[Image: home_opensource.png|left]]

{{anchor|It's all Free and Open-Source Software.}}
=== Tudo é Software Livre e de Código Aberto ===
Não há textos anexados e as atualizações <em>sempre</em> respeitarão a liberdade dos usuários.
{{ Translated text |
There are no strings attached and updates will <em>always</em> respect users' freedom.
| display = none }}

<div class="visualClear"></div>

{{anchor|What are the Sugar Labs?}}
== Quem são Sugar Labs? ==

O Sugar está disponivel sob a licença pública geral GNU (GPL sigla em inglês) para qualquer pessoa que queira ampliá-lo. “Sugar Labs”, uma fundação (que se estabelecerá em breve) sem fins lucrativos que servirá como base de suporte e ponto de referência para a comunidade de educadores e desenvolvedores de software que queiram extender a plataformam e criar aplicações compatíveis com o Sugar. O software do Sugar Labs se encontra nos laptops XO. Você poderá encontrar mais informações sobre o projeto em laptop.org.

{{ Translated text |
Sugar is available under the free software GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, a (soon to be established) non-profit foundation will serve as a support base and gathering place for the community of educators and software developers who want to extend the platform and create Sugar-compatible applications. Sugar Labs software is found on the XO laptop. You can find more out about the project at laptop.org.
| display = none }}

<p style="font-size: 1.2em;">[[What is Sugar?/lang-pt_BR | Aprenda mais sobre o Sugar...]] ou [[Sugar Labs/lang-pt_BR | Aprenda sobre o Sugar Labs, a organização por trás do sugar]]'''</p>

{{ Translated text |
<p style="font-size: 1.2em;">[[What is Sugar? | Learn more about Sugar...]] or [[Sugar Labs | learn about Sugar Labs, the organization behind Sugar]]'''</p>
| display = none }}

{{anchor|Activities}}
== Atividades ==

As aplicações do Sugar são chamadas [http://wiki.laptop.org/go/Activities Atividades]. Esta é uma lista de algumas das Atividades que estão instaladas por padrão. Há uma proposta para um [[Activity Library | Portal de Atividades]].

{{ Translated text |
Sugar applications are called [http://wiki.laptop.org/go/Activities Activities]. This is a list of some Activities that are installed by default. There is a proposal for an [[Activity Libraryf]].
| display = none }}

<table border="0">
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-journal.png|40px]]
{{anchor|[http://wiki.laptop.org/go/Journal Journal]}}
=== [http://wiki.laptop.org/go/Journal Diario] ===
Navegador de objetos e atividades
{{ Translated text |
Object and activity browser
| display = none }}
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-pippy.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Pippy Pippy]}}
=== [http://wiki.laptop.org/go/Pippy Peppy] ===
Ambiente/Linguagem de Programação Python
{{ Translated text |
Python Programming language/environment
| display = none }}
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-web.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Browse Browse]}}
=== [http://wiki.laptop.org/go/Browse Navegar] ===
Navegador web baseado no Mozilla Firefox
{{ Translated text |
Web browser based on Mozilla Firefox
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-etoys.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Etoys Etoys]}}
=== [http://wiki.laptop.org/go/Etoys Etoys] ===
Ambiente de Aprendizagem / programação / autoria
{{ Translated text |
Learning / programming / authoring environment
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-read.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Read Read]}}
=== [http://wiki.laptop.org/go/Read Ler] ===
Leitor de Livros/PDF
{{ Translated text |
Book/PDF reader
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:Activity-turtleart-grey.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Turtle_Art Turtle Art]}}
=== [http://wiki.laptop.org/go/Turtle_Art TortuArte] ===
Linguagem de Programação gráfica Pseudo-Logo
{{ Translated text |
Pseudo-Logo graphical programming language
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-write.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Write Write]}}
=== [http://wiki.laptop.org/go/Write Escrever] ===
Processador de textos
{{ Translated text |
Word processor
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-calculate.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Calculate Calculate]}}
=== [http://wiki.laptop.org/go/Calculate Calcular] ===
Calculadora básica
{{ Translated text |
Basic calculator
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-news.png|40px]]
{{anchor||[http://wiki.laptop.org/go/News_Reader News Reader]}}
=== [http://wiki.laptop.org/go/News_Reader Leitor de Notícias] ===
Leitor de Notícias
{{ Translated text |
News reader
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-measure.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Measure Measure]}}
=== [http://wiki.laptop.org/go/Measure Medir] ===
Osciloscópio e Registros de dados
{{ Translated text |
Oscilloscope and Data Logging
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-draw.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Paint Paint]}}
=== [http://wiki.laptop.org/go/Paint Desenho] ===
Atividade simples para desenhos
{{ Translated text |
Simple paint activity
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-acousticmeasure.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Distance Distance]}}
=== [http://wiki.laptop.org/go/Distance Distância] ===
Mede a distância entre dois laptops
{{ Translated text |
Measure distance between two laptops
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-record.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Record Record]}}
=== [http://wiki.laptop.org/go/Record Gravar] ===
Captura de fotos, videos e áudio
{{ Translated text |
Still, video, and audio capture
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-analyze.png|40px]]
{{anchor||Analyze}}
=== Analizar ===
Uma versão atividade da ferramenta de análises do Sugar
{{ Translated text |
An activity version of the Sugar analyze tool
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-log.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Log Log]}}
=== [http://wiki.laptop.org/go/Log Registrar] ===
Uma versão atividade da ferramenta de registros do Sugar
{{ Translated text |
An activity version of the Sugar logging tool
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-terminal.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Terminal Terminal]}}
=== [http://wiki.laptop.org/go/Terminal Terminal] ===
Uma versão atividade do terminal do Sugar
{{ Translated text |
An activity version of the Sugar terminal
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-tamtamjam.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Tamtam TamTam]}}
=== [http://wiki.laptop.org/go/Tamtam TamTam] ===
Composicão e síntese de músicas.
{{ Translated text |
Music composition and synthesis.
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-chat.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Chat Chat]}}
=== [http://wiki.laptop.org/go/Chat Chat] ===
Discussão colaborativa
{{ Translated text |
Collaborative discussion
| display = none }}
</td>
</tr>
<tr>
<td width="33%" style="text-align: center;">
{{anchor||And more}}
=== E mais... ===
[http://wiki.laptop.org/go/GCompris Dezenas de atividades disponíveis].
{{ Translated text |
[http://wiki.laptop.org/go/GCompris Dozens more are available].
| display = none }}
</td>
</tr>
</table>

{{anchor||See also}}
==Veja também==

[[Image:sugarlabs_logo_big.png|right|150px]]

* [[Sugar Labs/GettingInvolved|Envolva-se!]]
* Uma [[taxonomy | taxonomía]] do Sugar e uma relação de [[supported systems | sistemas suportados]]
* A [[Development Team/Release | Equipe de liberação]] do Sugar e as páginas de discussão do [[Development Team/Release/Roadmap | Plano de trabalho da equipe de liberação]]
* Outras páginas de interresses para [[:Category:Developer|desenvolvedores]]
* Uma discussão do [[Sugar Labs/Background|contexto]] sobre [[What_is_Sugar%3F|Sugar]] e [[Sugar Labs]]
* [http://wiki.laptop.org/go/Category:Sugar A categoria Sugar] em olpcwiki para mais.
* Ajude-nos [[Design Team/Logo Ideas|desenhando um logo]] para o Sugar Labs
* [[Sugar Labs/FAQ|Perguntas frequentes]]
{{ Translated text |
* [[Sugar Labs/GettingInvolved|Getting involved!]]
* A Sugar [[taxonomy]] and a matrix of [[supported systems]]
* The Sugar [[Development Team/Release]] and [[Development Team/Release/Roadmap]] discussion pages
* Other pages of interest to [[:Category:Developer|developers]]
* A [[Sugar Labs/Background|background]] discussion on [[What_is_Sugar%3F|Sugar]] and [[Sugar Labs]]
* [http://wiki.laptop.org/go/Category:Sugar The Sugar category] on olpcwiki for more.
* Help us [[Design Team/Logo Ideas|design a logo]] for Sugar Labs
* [[Sugar Labs/FAQ|Frequently asked questions]]
| display = none }}

[[Category:General public]]

Welcome to the Sugar Labs wiki/lang-es

2009-04-08T15:01:59Z

Dfarning-bot: fix camelcase links

<noinclude>{{Translations | [[Sugar Labs/Welcome to Sugar Labs|english]] | [[Sugar Labs/Welcome to Sugar Labs/lang-es|español]] | [[Sugar Labs/Welcome to Sugar Labs/lang-pt_BR|português brasil]] | [[Sugar Labs/Welcome to Sugar Labs/lang-ps|پښتو]]}}{{ GoogleTrans-es | en =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
__NOTOC__
__NOEDITSECTION__

<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar reinventa cómo los computadores pueden ser utilizados para la educación.''' Promueve el intercambio y el aprendizaje colaborativo y da a los niños la oportunidad de utilizar sus portátiles en sus propios términos. Los niños — y sus profesores — tienen la libertad para reformar, reinventar, y rehacer su software, y el contenido. Sugar está basado en GNU/Linux, un sistema operativo libre y de codigo abierto. </p>

{{ Translated text |
<p style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">'''Sugar reinvents how computers can be used for education.''' It promotes sharing and collaborative learning and gives children the opportunity to use their laptops on their own terms. Children — and their teachers — have the freedom to reshape, reinvent, and reapply their software, and content. Sugar is based on GNU/Linux, a free and open-source operating system. </p>
| display = none }}

[[Image:home_sharing.png|left]]

{{anchor|Sugar facilitates sharing and collaboration}}

=== Sugar facilita el intercambio y la colaboración ===

Los niños pueden escribir documentos o hacer música juntos con facilidad.

{{ Translated text |
Children can write documents or make music together with ease.
| display = none }}

<div class="visualClear"></div>

[[Image: home_activities.png|left]]

{{anchor|There are no files, folders or applications}}
=== No hay archivos, carpetas o aplicaciones ===

Lo que se hace es una <em>actividad</em> e incluye la aplicación y todos sus datos. Se puede reanudar cualquier actividad en cualquier momento.

{{ Translated text |
What you do is an <em>activity</em> and that includes the application and all your data.
You can resume any activity at any time.
| display = none }}

<div class="visualClear"></div>

[[Image: home_backup.png|left]]

{{anchor|You can hardly lose data.}}
=== Difícilmente se puede perder los datos. ===

Todo está guardado y se hacen copias de seguridad automáticamente.

{{ Translated text |
Everything is saved and backed up automatically.
| display = none }}

<div class="visualClear"></div>

[[Image: home_journal.png|left]]

{{anchor|You use a journal for accessing data.}}
=== Puedes usar un diario para acceder a los datos. ===

Es como un diario de las cosas que has hecho.
{{ Translated text |
It's like a diary of stuff that you made.
| display = none }}

<div class="visualClear"></div>

[[Image: home_opensource.png|left]]

{{anchor|It's all Free and Open-Source Software.}}
=== Todo es Software Libre y de Código Abierto ===

No hay cadenas adjuntas y actualizaciones <em>siempre</em> se respetará la libertad de los usuarios.
{{ Translated text |
There are no strings attached and updates will <em>always</em> respect users' freedom.
| display = none }}

<div class="visualClear"></div>

{{anchor|What are the Sugar Labs?}}
== ¿Qué son Sugar Labs? ==

Sugar está disponible bajo la licencia pública general de GNU (GPL por sus siglas en inglés) para cualquier persona que quiera ampliarlo. “Sugar Labs”, una fundación (que se establecerá prontamente) sin ánimo de lucro servirá como una base de soporte y lugar de reunión para la comunidad de educadores y desarrolladores de software que quieran extender la plataforma y crear aplicaciones compatibles con Sugar. El software de Sugar Labs se encuentra en los portátiles XO. Puede encontrar más información sobre el proyecto en laptop.org.

{{ Translated text |
Sugar is available under the free software GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs”, a (soon to be established) non-profit foundation will serve as a support base and gathering place for the community of educators and software developers who want to extend the platform and create Sugar-compatible applications. Sugar Labs software is found on the XO laptop. You can find more out about the project at laptop.org.
| display = none }}

<p style="font-size: 1.2em;">[[What is Sugar? | aprende más sobre Sugar...]] o [[Sugar Labs | Aprende acerca de Sugar Labs, la organización detrás de sugar]]'''</p>

{{ Translated text |
<p style="font-size: 1.2em;">[[What is Sugar? | Learn more about Sugar...]] or [[Sugar Labs | learn about Sugar Labs, the organization behind Sugar]]'''</p>
| display = none }}

{{anchor|Activities}}
== Actividades ==

Las aplicaciones de Sugar son llamadas [[Activity_Team Actividades]]. Esta es una lista de algunas Actividades que están instaladas por omisión. Hay una propuesta para un [[Activity Library | Portal de Actividades]].

{{ Translated text |
Sugar applications are called [Activities Activities]. This is a list of some Activities that are installed by default. There is a proposal for an [[Activity Library]].
| display = none }}

<table border="0">
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-journal.png|40px]]
{{anchor|[http://wiki.laptop.org/go/Journal Journal]}}
=== [http://wiki.laptop.org/go/Journal Diario] ===
Navegador de objetos y actividades
{{ Translated text |
Object and activity browser
| display = none }}
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-pippy.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Pippy Pippy]}}
=== [http://wiki.laptop.org/go/Pippy Peppy] ===
Leguaje/Entorno de programación en Python
{{ Translated text |
Python Programming language/environment
| display = none }}
</td>

<td width="33%" style="text-align: center;">
[[Image:activity-web.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Browse Browse]}}
=== [http://wiki.laptop.org/go/Browse Navegar] ===
Navegador web basado en Mozilla Firefox
{{ Translated text |
Web browser based on Mozilla Firefox
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-etoys.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Etoys Etoys]}}
=== [http://wiki.laptop.org/go/Etoys Etoys] ===
Entorno de Aprendizaje / programación / autoria
{{ Translated text |
Learning / programming / authoring environment
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-read.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Read Read]}}
=== [http://wiki.laptop.org/go/Read Leer] ===
Lector de Libros/PDF
{{ Translated text |
Book/PDF reader
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:Activity-turtleart-grey.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Turtle_Art Turtle Art]}}
=== [http://wiki.laptop.org/go/Turtle_Art TortuArte] ===
Lenguaje de Programación gráfico Pseudo-Logo
{{ Translated text |
Pseudo-Logo graphical programming language
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-write.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Write Write]}}
=== [http://wiki.laptop.org/go/Write Escribir] ===
Procesador de palabras
{{ Translated text |
Word processor
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-calculate.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Calculate Calculate]}}
=== [http://wiki.laptop.org/go/Calculate Calcular] ===
Calculadora básica
{{ Translated text |
Basic calculator
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-news.png|40px]]
{{anchor||[http://wiki.laptop.org/go/News_Reader News Reader]}}
=== [http://wiki.laptop.org/go/News_Reader Lector de Noticias] ===
Lector de Noticias
{{ Translated text |
News reader
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-measure.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Measure Measure]}}
=== [http://wiki.laptop.org/go/Measure Medir] ===
Osciloscopio y Registro de datos
{{ Translated text |
Oscilloscope and Data Logging
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-draw.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Paint Paint]}}
=== [http://wiki.laptop.org/go/Paint Dibujar] ===
Actividad para dibujos sencillos
{{ Translated text |
Simple paint activity
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-acousticmeasure.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Distance Distance]}}
=== [http://wiki.laptop.org/go/Distance Distancia] ===
Mide la distancia entre dos portátiles
{{ Translated text |
Measure distance between two laptops
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-record.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Record Record]}}
=== [http://wiki.laptop.org/go/Record Grabar] ===
Captura de fotogramas, video y audio
{{ Translated text |
Still, video, and audio capture
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-analyze.png|40px]]
{{anchor||Analyze}}
=== Analizar ===
Una versión de la actividad de la herramienta de análisis de Sugar
{{ Translated text |
An activity version of the Sugar analyze tool
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-log.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Log Log]}}
=== [http://wiki.laptop.org/go/Log Registrar] ===
Una versión de la actividad de la herramienta de registro de Sugar
{{ Translated text |
An activity version of the Sugar logging tool
| display = none }}
</td></tr>
<tr>
<td width="33%" style="text-align: center;">
[[Image:activity-terminal.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Terminal Terminal]}}
=== [http://wiki.laptop.org/go/Terminal Terminal] ===
Una versión de la actividad de terminal de Sugar
{{ Translated text |
An activity version of the Sugar terminal
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-tamtamjam.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Tamtam TamTam]}}
=== [http://wiki.laptop.org/go/Tamtam TamTam] ===
Composición y síntesis de música.
{{ Translated text |
Music composition and synthesis.
| display = none }}
</td>
<td width="33%" style="text-align: center;">
[[Image:activity-chat.png|40px]]
{{anchor||[http://wiki.laptop.org/go/Chat Chat]}}
=== [http://wiki.laptop.org/go/Chat Charla] ===
Discusión colaborativa
{{ Translated text |
Collaborative discussion
| display = none }}
</td>
</tr>
<tr>
<td width="33%" style="text-align: center;">
{{anchor||And more}}
=== Y más ===
[http://wiki.laptop.org/go/GCompris Docenas de actividades disponibles].
{{ Translated text |
[http://wiki.laptop.org/go/GCompris Dozens more are available].
| display = none }}
</td>
</tr>
</table>

{{anchor||See also}}
==Vea también==

[[Image:sugarlabs_logo_big.png|right|150px]]

* [[Sugar Labs/GettingInvolved|Involucrate!]]
* Una [[taxonomy | taxonomía]] de Sugar y una matriz de [[supported systems | sistemas soportados]]
* El [[Development Team/Release | Equipo de liberación]] de Sugar y las páginas de discusión del [[Development Team/Release/Roadmap | Plan de trabajo del equipo de liberación]]
* Otras páginas de interés para [[:Category:Developer|desarrolladores]]
* Un discusión de [[Sugar Labs/Background|contexto]] sobre [[What_is_Sugar%3F|Sugar]] y [[Sugar Labs]]
* [http://wiki.laptop.org/go/Category:Sugar La categoria Sugar] en olpcwiki para mas.
* Ayúdanos [[Design Team/Logo Ideas|diseñando un logo]] para Sugar Labs
* [[Sugar Labs/FAQ|Preguntas frecuentes]]
{{ Translated text |
* [[Sugar Labs/GettingInvolved|Getting involved!]]
* A Sugar [[taxonomy]] and a matrix of [[supported systems]]
* The Sugar [[Development Team/Release]] and [[Development Team/Release/Roadmap]] discussion pages
* Other pages of interest to [[:Category:Developer|developers]]
* A [[Sugar Labs/Background|background]] discussion on [[What_is_Sugar%3F|Sugar]] and [[Sugar Labs]]
* [http://wiki.laptop.org/go/Category:Sugar The Sugar category] on olpcwiki for more.
* Help us [[Design Team/Logo Ideas|design a logo]] for Sugar Labs
* [[Sugar Labs/FAQ|Frequently asked questions]]
| display = none }}

[[Category:General public]]

Design Team/Logo Ideas

2009-04-08T15:00:53Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TOCright}}
Please add your logo ideas to the image gallery.
====Sugar Logo based on Activity Icons====

[[Image:Sugaros_square_vsm2.gif‎]]

Goal: simple, reproduces well at large or very small sizes (down to favicon), building on familiarity of previous logo yet emphasizing Activities that draw kids in -- chatting, TamTam, art - to give a playful feel. Intention: to be accessible and memorable to both kids and adults, building on previous brand equity, as well as saying what Sugar "is". Animated version could rotate through various activity icons.

Question: should the Sugar Labs logo and Sugar OS logo be one and the same? Perhaps Sugar Labs should have a separate logo, in order to allow for variants on OS, and other projects.

-TK

====Designs by Luca Ferrari and Franco Lodato====

[[Image:Luca-logo-1.jpg|150px]]

[[Image:Luca-logo-2.jpg|150px]]

[[Image:Luca-logo-3.jpg|150px]]

[[Image:Luca-logo-4.jpg|150px]]

[[Image:Luca-logo-5a.jpg|150px]]

[[Image:Luca-logo-5b.jpg|150px]]

[[Image:Luca-logo-5c.jpg|150px]]

[[Image:Luca-logo-5d.jpg|150px]]

[[Image:Luca-logo-5e.jpg|150px]]

=====Simplified versions=====

[[Image:Luca-logo-5wb.png|150px]]

[[Image:Luca-logo-5wb2.png|150px]]

[[Image:Luca-logo-5wb3.png|150px]]

[[Image:Luca-logo-5wb5.png|150px]]

[[Image:Luca-logo-5wb4.png|150px]]

==== XO-based Logo ====

[[Image:SugarLabsLogo30.png|150px]] [[Image:SugarLabsLogo2.png|150px]]

I have the SVG source available if either of these logos is selected.
The second has the allusion of an infinity symbol and has a bit
smoother look.

Designed by Murray Altheim

====variation on theme====

[[Image:SL_logo_concept2.png|150px]]

[[User:Cjl|Cjl]] 04:49, 4 June 2008 (UTC)

====Current Logo====
[[Image:Sugarlabs wiki logo.png]]

I got this from the upper left hand corner of the wiki site. It is optimized for a black background - sorry. But I really like this since it is slightly different from the XO logo - by being thicker and having a hard candy pattern. It's my favorite from the list so far.--[[User:ThePlaz|ThePlaz]] 17:16, 26 May 2008 (UTC)

====Molecule====
{|
| http://upload.wikimedia.org/wikipedia/commons/c/c1/Ribofuranose-2D-skeletal.png Ribose Sugar
|-
| http://en.wikipedia.org/wiki/Image:Beta-D-glucose-3D-vdW.png Glucose Sugar
|-
|}

==== Sugar Bowl ====
[[Image:Sugarlabs2.png|150px]]
[[Image:Sugarlabs.png|150px]]

Individual grains of sugar fill the bowl. Attempting to be whimsical in use of color and simple in form. The font is [http://www.myfonts.com/fonts/paragraph/bentwood/ Bentwood].

Designed by Marc Williams

==== "Peace" / Sugar cubes ====

[[Image:Peace-sugarlabs.png|250px]]

Designed by Gaurav Bhushan, a student of Information Design, National Institute of Design India.

Comments and feedback welcome.

====Another Sugar Cube====
This logo variation is an axonometric sugar cube with the name sugar labs wrapping around the base. The name is set in Tempo heavy Condensed.
[[Image:Dk_sugar_labs_logo_v1.png]]
<br clear="all" />
:May violate [[Talk:Design Team/Logo-ideas#Sugar_CRM|Sugar CRM]]'s trademark.

====Sugar Cube====
[[Image:logo_proposal.eben.png|150px]]
[[Image:logotype_proposal.eben.png|150px]]
:May violate [[Talk:Design Team/Logo Ideas#Sugar_CRM|Sugar CRM]]'s trademark.

====Building Blocks====
Here's a derivative idea, based on the "Sugar cube" proposal from before. If we consider representing Sugar as a building block, we could treat Sugar Labs as community structure composed of those blocks, emphasizing both construction(ism) and collaboration. Please note that this is a really quick sketch, and details such as size, placement, color, font, and even the rendition of the cube should be considered in detail, if this direction seems worth exploring.
[[Image:sugarlabs_proposal.eben.png|left|150px]]
==
<br clear="all" />

====Letter blocks====
Inspired by eben's building blocks. A "to-the-point" design. Have sugar be spelled using letter blocks. It immediately conveys the "kids learning" purpose of Sugar, plus hints at the enjoyment that goes along with learning. Rough mockup to show the idea.

[[Image:Sugarlabs-spelling-blocks.png|150px]]

[[Image:Sugarlabs-logo-2.png]]
[[Image:Sugarlabs-logo-1.png]]
[[Image:Sugarlabs-logo-4.png]]
====A connected community of learners====
[[Image:Cubes.png|left|150px]]
I like the cube idea, I was inspired looking at the earlier Sugar Cube designs and wanted to build something. My ideal is to connect a lot of parts, LEGO-style. So I adapted a Rubics cube design to build an apartment community with the Python team, the Sugar team, and so forth. Please choose and letter your sides, something wonderful could happen.

You could use this to document software/API layers, or anything that could be boxed, the dBus and other system software would be helpful to visualize, as well as children in different area using the mesh networking.

==

<br clear='all'>
====Text in pseudo-Sugar icon style====
The colors and line weights need adjusting, but just to give an idea. It is simple and flexible and it intends to give the impression of multiple elements making a whole--in this case a word.
[[Image:sugarlabs_text1.png|left|150px]]

<br clear='all'>

====Christian's take on this theme====
[[Image:suagrlabs-text2.png|left|300px]]

<br clear='all'>
[[Image:suagrlabs-text3.png|left|300px]]

<br clear='all'>
=====the color orange=====
[[Image:suagrlabs-text4.png|left|300px]]

<br clear='all'>

====Eye Metaphor====
I considered trying something different. Our eyes are the organs we humans absorb the most information with, especially when using a computer. Also, Sugar Labs may represent an eye for its users gathering information from all over the world. This metaphor was also incorporated in the rest of the suite, while each logo incorporates the function/tool it represents in a metaphorical way.
An other thing that was taken into consideration is that the Sugar Labs logo can be recognized/memorized easily and additionally it is functional in some cases on its own, without the need of the "Sugar Labs" badge. Hope this helps
[[Image:Sugarlabs_project.png|left|150px]]

<br clear='all'>
====Introduce "Lab" visual element?====

[[Image:Spoon-flask3.png]]

[[Image:sugarlabs.test-tube.eben.png|150px]]I had taken a crack at a similar idea myself, when working with the "droplet of sugar" idea.

=> http://img151.imageshack.us/img151/9929/39924994ey8.jpg Working atop of your image, I came with that result. To me, the thing should be green like the laptop (until XOXO) and I added a bit of sugar, or at least tried to represent some kind of sugarized treat with a cherry.

====Sugarcane====
[[Image:SugarLabsLogo.JPG|150px]] Just to give idea about logo based on "Sugarcane" image with SUGAR painted on it, and pieces of Sugarcane making "LABS" structure

[[Image:Lolbulb.png|150px]] Galaxy looking lollipop w/ lightbulb, also looks a bit like candyfloss - the sugariest, sweetest thing I've ever tasted.

====Sugar Glider (australian possum)====
Here are various attempts using this theme: (Note, this is a mascot and not a logo)

[[Image:Bigsuggie-xo.svg|200px]] first try

[[Image:Suggie glidie.svg|200px]] second try

[[Image:Suggie glidie 3.svg|200px]] third try

==== Sugar Shell ====

[[Image:Sugar-shell.jpg]]

[[User:Bernie|bernie]] 14:07, 27 January 2009 (UTC)

[[Category:Design Team]] [[Category:Sugarlabs logo]]

The icon for Sugarlabs should have the following qualities in order to appeal to children
:: I think this may be both "appeal to children" and "call up childlike images in the minds of adults" - just saying that most of us are not exactly in our target user base. ;) [[User:Mchua|Mchua]] 03:00, 18 January 2009 (UTC)
* Simple
* bright colors
* not overly polished

==== Sun/Starfish/Acorn/Dandelion ====

Here is a suggestion:
[[Image:Sugar-icon-v1.png]]

I like the sun logo because:
* The sun represents knowledge in many cultures
* It looks a little bit like a child

[[Image:Logodraft-starfish.png|300px|frame|none|Inspired by Greg, Caroline, and "The Starfish and the Spider." Also somewhat boring and generic.]]

[[Image:Logodraft-starfishweb.png|300px|frame|none|The starfish learns to spin a web, the starfish surfs the web, the starfish has a network... unfortunately, this could also be read as "the starfish got stuck in the web."]]

[[Image:Logodraft-acorn.png|300px|frame|none|Somewhat boring and generic, but acorns are often a symbol for youth, trees a symbol of knowledge.]]

[[Image:Logodraft-dandelion.png|300px|frame|none|Dandelions sprout just about everywhere. Their flowers and seeds are often played with (and spread by) young children. They are also native to temperate areas of the northern hemisphere.]]

[[Image:Logodraft-dandelion-seed.png|300px|frame|none|A dandelion seed in flight, one of billions off to explore the world and find a place to grow...]]

[[Image:Logodraft-dandelion-head.png|300px|frame|none|A dandelion head ready to be picked up and blown on by a child.]]

[[Category:Design]]

Design Team/Logo Ideas

2009-04-08T14:59:25Z

Dfarning-bot: fix camelcase links

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>{{TOCright}}
Please add your logo ideas to the image gallery.
====Sugar Logo based on Activity Icons====

[[Image:Sugaros_square_vsm2.gif‎]]

Goal: simple, reproduces well at large or very small sizes (down to favicon), building on familiarity of previous logo yet emphasizing Activities that draw kids in -- chatting, TamTam, art - to give a playful feel. Intention: to be accessible and memorable to both kids and adults, building on previous brand equity, as well as saying what Sugar "is". Animated version could rotate through various activity icons.

Question: should the Sugar Labs logo and Sugar OS logo be one and the same? Perhaps Sugar Labs should have a separate logo, in order to allow for variants on OS, and other projects.

-TK

====Designs by Luca Ferrari and Franco Lodato====

[[Image:Luca-logo-1.jpg|150px]]

[[Image:Luca-logo-2.jpg|150px]]

[[Image:Luca-logo-3.jpg|150px]]

[[Image:Luca-logo-4.jpg|150px]]

[[Image:Luca-logo-5a.jpg|150px]]

[[Image:Luca-logo-5b.jpg|150px]]

[[Image:Luca-logo-5c.jpg|150px]]

[[Image:Luca-logo-5d.jpg|150px]]

[[Image:Luca-logo-5e.jpg|150px]]

=====Simplified versions=====

[[Image:Luca-logo-5wb.png|150px]]

[[Image:Luca-logo-5wb2.png|150px]]

[[Image:Luca-logo-5wb3.png|150px]]

[[Image:Luca-logo-5wb5.png|150px]]

[[Image:Luca-logo-5wb4.png|150px]]

==== XO-based Logo ====

[[Image:SugarLabsLogo30.png|150px]] [[Image:SugarLabsLogo2.png|150px]]

I have the SVG source available if either of these logos is selected.
The second has the allusion of an infinity symbol and has a bit
smoother look.

Designed by Murray Altheim

====variation on theme====

[[Image:SL_logo_concept2.png|150px]]

[[User:Cjl|Cjl]] 04:49, 4 June 2008 (UTC)

====Current Logo====
[[Image:Sugarlabs wiki logo.png]]

I got this from the upper left hand corner of the wiki site. It is optimized for a black background - sorry. But I really like this since it is slightly different from the XO logo - by being thicker and having a hard candy pattern. It's my favorite from the list so far.--[[User:ThePlaz|ThePlaz]] 17:16, 26 May 2008 (UTC)

====Molecule====
{|
| http://upload.wikimedia.org/wikipedia/commons/c/c1/Ribofuranose-2D-skeletal.png Ribose Sugar
|-
| http://en.wikipedia.org/wiki/Image:Beta-D-glucose-3D-vdW.png Glucose Sugar
|-
|}

==== Sugar Bowl ====
[[Image:Sugarlabs2.png|150px]]
[[Image:Sugarlabs.png|150px]]

Individual grains of sugar fill the bowl. Attempting to be whimsical in use of color and simple in form. The font is [http://www.myfonts.com/fonts/paragraph/bentwood/ Bentwood].

Designed by Marc Williams

==== "Peace" / Sugar cubes ====

[[Image:Peace-sugarlabs.png|250px]]

Designed by Gaurav Bhushan, a student of Information Design, National Institute of Design India.

Comments and feedback welcome.

====Another Sugar Cube====
This logo variation is an axonometric sugar cube with the name sugar labs wrapping around the base. The name is set in Tempo heavy Condensed.
[[Image:Dk_sugar_labs_logo_v1.png]]
<br clear="all" />
:May violate [[Talk:Design Team/Logo-ideas#Sugar_CRM|Sugar CRM]]'s trademark.

====Sugar Cube====
[[Image:logo_proposal.eben.png|150px]]
[[Image:logotype_proposal.eben.png|150px]]
:May violate [[Talk:DesignTeam/Logo-ideas#Sugar_CRM|Sugar CRM]]'s trademark.

====Building Blocks====
Here's a derivative idea, based on the "Sugar cube" proposal from before. If we consider representing Sugar as a building block, we could treat Sugar Labs as community structure composed of those blocks, emphasizing both construction(ism) and collaboration. Please note that this is a really quick sketch, and details such as size, placement, color, font, and even the rendition of the cube should be considered in detail, if this direction seems worth exploring.
[[Image:sugarlabs_proposal.eben.png|left|150px]]
==
<br clear="all" />

====Letter blocks====
Inspired by eben's building blocks. A "to-the-point" design. Have sugar be spelled using letter blocks. It immediately conveys the "kids learning" purpose of Sugar, plus hints at the enjoyment that goes along with learning. Rough mockup to show the idea.

[[Image:Sugarlabs-spelling-blocks.png|150px]]

[[Image:Sugarlabs-logo-2.png]]
[[Image:Sugarlabs-logo-1.png]]
[[Image:Sugarlabs-logo-4.png]]
====A connected community of learners====
[[Image:Cubes.png|left|150px]]
I like the cube idea, I was inspired looking at the earlier Sugar Cube designs and wanted to build something. My ideal is to connect a lot of parts, LEGO-style. So I adapted a Rubics cube design to build an apartment community with the Python team, the Sugar team, and so forth. Please choose and letter your sides, something wonderful could happen.

You could use this to document software/API layers, or anything that could be boxed, the dBus and other system software would be helpful to visualize, as well as children in different area using the mesh networking.

==

<br clear='all'>
====Text in pseudo-Sugar icon style====
The colors and line weights need adjusting, but just to give an idea. It is simple and flexible and it intends to give the impression of multiple elements making a whole--in this case a word.
[[Image:sugarlabs_text1.png|left|150px]]

<br clear='all'>

====Christian's take on this theme====
[[Image:suagrlabs-text2.png|left|300px]]

<br clear='all'>
[[Image:suagrlabs-text3.png|left|300px]]

<br clear='all'>
=====the color orange=====
[[Image:suagrlabs-text4.png|left|300px]]

<br clear='all'>

====Eye Metaphor====
I considered trying something different. Our eyes are the organs we humans absorb the most information with, especially when using a computer. Also, Sugar Labs may represent an eye for its users gathering information from all over the world. This metaphor was also incorporated in the rest of the suite, while each logo incorporates the function/tool it represents in a metaphorical way.
An other thing that was taken into consideration is that the Sugar Labs logo can be recognized/memorized easily and additionally it is functional in some cases on its own, without the need of the "Sugar Labs" badge. Hope this helps
[[Image:Sugarlabs_project.png|left|150px]]

<br clear='all'>
====Introduce "Lab" visual element?====

[[Image:Spoon-flask3.png]]

[[Image:sugarlabs.test-tube.eben.png|150px]]I had taken a crack at a similar idea myself, when working with the "droplet of sugar" idea.

=> http://img151.imageshack.us/img151/9929/39924994ey8.jpg Working atop of your image, I came with that result. To me, the thing should be green like the laptop (until XOXO) and I added a bit of sugar, or at least tried to represent some kind of sugarized treat with a cherry.

====Sugarcane====
[[Image:SugarLabsLogo.JPG|150px]] Just to give idea about logo based on "Sugarcane" image with SUGAR painted on it, and pieces of Sugarcane making "LABS" structure

[[Image:Lolbulb.png|150px]] Galaxy looking lollipop w/ lightbulb, also looks a bit like candyfloss - the sugariest, sweetest thing I've ever tasted.

====Sugar Glider (australian possum)====
Here are various attempts using this theme: (Note, this is a mascot and not a logo)

[[Image:Bigsuggie-xo.svg|200px]] first try

[[Image:Suggie glidie.svg|200px]] second try

[[Image:Suggie glidie 3.svg|200px]] third try

==== Sugar Shell ====

[[Image:Sugar-shell.jpg]]

[[User:Bernie|bernie]] 14:07, 27 January 2009 (UTC)

[[Category:DesignTeam]] [[Category:Sugarlabs logo]]

The icon for Sugarlabs should have the following qualities in order to appeal to children
:: I think this may be both "appeal to children" and "call up childlike images in the minds of adults" - just saying that most of us are not exactly in our target user base. ;) [[User:Mchua|Mchua]] 03:00, 18 January 2009 (UTC)
* Simple
* bright colors
* not overly polished

==== Sun/Starfish/Acorn/Dandelion ====

Here is a suggestion:
[[Image:Sugar-icon-v1.png]]

I like the sun logo because:
* The sun represents knowledge in many cultures
* It looks a little bit like a child

[[Image:Logodraft-starfish.png|300px|frame|none|Inspired by Greg, Caroline, and "The Starfish and the Spider." Also somewhat boring and generic.]]

[[Image:Logodraft-starfishweb.png|300px|frame|none|The starfish learns to spin a web, the starfish surfs the web, the starfish has a network... unfortunately, this could also be read as "the starfish got stuck in the web."]]

[[Image:Logodraft-acorn.png|300px|frame|none|Somewhat boring and generic, but acorns are often a symbol for youth, trees a symbol of knowledge.]]

[[Image:Logodraft-dandelion.png|300px|frame|none|Dandelions sprout just about everywhere. Their flowers and seeds are often played with (and spread by) young children. They are also native to temperate areas of the northern hemisphere.]]

[[Image:Logodraft-dandelion-seed.png|300px|frame|none|A dandelion seed in flight, one of billions off to explore the world and find a place to grow...]]

[[Image:Logodraft-dandelion-head.png|300px|frame|none|A dandelion head ready to be picked up and blown on by a child.]]

[[Category:Design]]

Talk:Human Interface Guidelines

2009-04-08T14:56:41Z

Dfarning-bot: Talk:DesignTeam/Human Interface Guidelines moved to Talk:Design Team/Human Interface Guidelines

See [[Design Team/Vision/Proposals]].

Wiki Team/Guide/Watchlist

2009-03-08T11:38:24Z

Dfarning-bot: WikiTeam/wikiGuide/Watchlist moved to Wiki Team/Guide/Watchlist: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
You can add any page to your '''watchlist''', in which case you will receive an e-mail notice when someone else makes a change to that page.

To '''watch''' an article simply click on the '''watch''' tab at the top of the page. Click that same tab on a watched page to '''unwatch''' it.

There is also a checkbox under the "Summary:" line on the article editing page which allows you to watch a page.

Follow the '''my watchlist''' link in the upper right corner of any page to view and manage your watch list.

See the '''watchlist''' tab in '''my preferences''' to control your watchlist.

== See Also ==
* [[WikiTeam/WikiGuide/UserLinks]]
* [http://www.mediawiki.org/wiki/Help:Tracking_changes MediaWiki Manual: Tracking Changes]

Wiki Team/Guide/Patrolled Edits

2009-03-08T11:38:14Z

Dfarning-bot: WikiTeam/Wikiguide/Patrolled edits moved to Wiki Team/Guide/Patrolled edits: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Some users can be given the '''patrol''' permission, which allows them to review the edits made by others.

If you have the ability to patrol edits, then in the list of [[Special:Recentchanges|Recent Changes]] a revision which has ''not''  been reviewed will be marked with a red exclaimation mark "<font color=RED><b>!</b></font>".

When you '''view the differences''' between versions of an unpatrolled article you will find in the column headers a link which say
<blockquote>
<nowiki>[</nowiki><font color=BLUE>Mark as patrolled</font><nowiki>]</nowiki>
</blockquote>
You should only click on this link if you have reviewed the changes to the article and found nothing clearly unacceptable, such as vandalism.

Patrolling is not a substitute for substantive editing. It's just a way to keep vandalism in check.

== See Also ==
*[http://www.mediawiki.org/wiki/Help:Patrolled_edits MediaWiki Manual: Patrolled edits]
*[http://meta.wikimedia.org/wiki/Patrol Wikimedia Meta: Patrol]

Wiki Team/Guide/User Links

2009-03-08T11:37:44Z

Dfarning-bot: WikiTeam/WikiGuide/UserLinks moved to Wiki Team/Guide/UserLinks: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
The '''user links''' at the top right side of every page give you control of your preferences, let you review your contributions, or see what pages you are watching. There are also links to your own talk and user pages.

* The '''my contributions''' link takes you to a list of all the pages ''you'' have edited or created.

* The '''my watchlist''' link shows the status of all the pages you are watching. Use the '''watch''' tab at the top of any page to add it to the watch list. You will then receive an e-mail whenever that page changes.

* The '''my preferences''' link lets you adjust your viewing and editing preferences.

* The '''my talk''' link takes you to your own "talk" page. Think of it as the white board outside your office door where people can leave you messages, or you can leave a response.

* The link with your name on it takes you to your "User" page, where you can put a little something about yourself for the benefit of the other users. It will help them know more about who you are.

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Navigation#User_Links MediaWiki Manual: Navigation - User Links]

Wiki Team/Guide/Talkpages

2009-03-08T11:37:24Z

Dfarning-bot: WikiTeam/WikiGuide/Talkpages moved to Wiki Team/Guide/Talkpages: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Every article (page) in this wiki has a corresponding '''"discussion" page''', where one can make notes or carry on a discussion about what should be shown in the article itself.

Even if you do not want to edit the article (or don't have permission to do so), you can add to the "discussion" page and thereby contribute to the development of this wiki.

To edit (or create) the discussion page for an article just visit the article and click on the "'''{{MediaWiki:Talk}}'''" tab at the top of the page.

Wiki Team/Guide/Style Guide

2009-03-08T11:37:14Z

Dfarning-bot: WikiTeam/WikiGuide/StyleGuide moved to Wiki Team/Guide/StyleGuide: Robot: Moved page

=Introduction=
The pages in this wiki should be as easy to understand and follow as possible. With this in mind, please take into account the following suggested writing style guidelines:

=Terminology=
*Sugar releases - Always try to specify which versions of Sugar a page is valid for. When referring to Sugar releases, use "Sugar X.XX" - eg. "Sugar 0.82".
*Linux distributions - Capitalize the names of Linux distributions like Fedora, Debian, Ubuntu, etc.
*Operating Systems - Capitalize the names of operating systems like Linux, Ubuntu, Windows, etc.

=Page Titles=
* Be descriptive.
* Avoid using the word "Howto" in the page title (everything here is a howto!).
* Use capital letters and avoid spaces or dashes (WikiName, for example).

=Section Headings=
* Heading text should be short, clear, and descriptive.
* Capitalize in the following manner:
** Initial uppercase letter for the first word and the last word, regardless of part of speech
** Initial uppercase letter for all nouns, adjectives, and verbs
** Initial uppercase letter for conjunctions of four letters or longer
** Initial uppercase letter for prepositions of four letters or longer
** Initial uppercase letter for prepositions that are part of a phrasal verb
** All lowercase letters for conjunctions, articles, and prepositions of less than four letters

(Taken from the GNOME Style Guide)

=Lists=
Bullet lists of links should take the following form: <Bullet> <Link> <Hyphen> <Sentence>.
* For example:
** Skype - Internet telephony software (closed source).

Wiki Team/Guide/Searching

2009-03-08T11:37:04Z

Dfarning-bot: WikiTeam/WikiGuide/Searching moved to Wiki Team/Guide/Searching: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
You can easily find whatever you might be looking for using the '''search box''' in the '''sidebar''' at the left of every page.

There are two search buttons, labeled '''Go''' and '''Search''', and they give you slightly different results.

== Go Button ==
When you use the '''Go''' button you will be taken directly to an article of the name you entered in the search box.

The '''Go''' button is case-'''sensitive'''.

If an article of that name does not exist, you will be given a link which lets you create it. ''and'' you will automatically get a search for that text, as if you had pressed the ''Search'' button.

== Search Button ==
Pressing the '''Search''' button will search through the wiki in two different ways. ''It's not like Google!''.

# First you get a listing of matches to article '''titles'''.
# Then you get a listing of matches to '''text in the body''' of articles.

The '''Search''' button is case-''insensitive''

== Hints ==

* The ''Search'' button will always give you a search.

* The ''Go'' button gives you a search only if an article of that exact name does not exist, and in that case you'll also get a link which lets you create the article.

* If you press the '''Return''' key on your keyboard it's the same as pressing the ''Go'' button with the mouse, not the ''Search'' button.

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Searching MediaWiki Manual: Searching]
* [http://meta.wikimedia.org/wiki/Help:Go_button Wikimedia Meta: Go Button]
* [http://meta.wikimedia.org/wiki/Help:Searching Wikimedia Meta: Searching]

Wiki Team/Guide/Rollback

2009-03-08T11:36:54Z

Dfarning-bot: WikiTeam/WikiGuide/Rollback moved to Wiki Team/Guide/Rollback: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Administrators can easily revert a page to the previous revision.
This is called a '''rollback'''.
Any editor can revert a page to an earlier revision manually, by editing the earlier version and then saving it.
It is possible to '''undo''' the effects of a single edit, even if it was not the most recent edit.

== Administrator Rollback ==
An administrator can quickly revert a page back to the previous revision (back one step).
This is called a '''rollback'''.
To rollback an article:
# visit the article in question, and press the '''history tab'''.
# Press the "'''[rollback]'''" link next to the top entry

== Manual revert ==
Any editor can revert a page back to any earlier revision. The steps are:
# visit the article in question and press the '''history tab'''.
# Find most recent known-good revision of the article and '''click on the date'''.
You get a view of the good page, labeled at the top as an out-of-date version.
# Edit the page (press the '''edit''' tab). Note in the Summary: box that this is a revert, along with a reason.
# Press '''Save page'''

This makes the earlier version the newest version, and effectively reverts all changes made between the two.

== Undo a single edit ==
It is possible to undo the effects of a single edit, even if it was not the most recent change.
This is done using the "diff" view from the page history:
# visit the article in question and press the '''history tab'''.
# Using the radio buttons next to each revision, select the earlier revision you wish to undo, and then press the "'''Compare selected versions'''" button. This shows the "diff" view comparing the differences between the two articles.
# In the heading for the column for the current version (the one on the right) click on the '''(undo)''' link to undo just that edit.

This procedure fails if there are conflicts between the edit you are undoing and later edits.

== See Also ==
*[http://meta.wikimedia.org/wiki/Help:Administration#Rollback Wikimedia Meta: Rollback]
*[http://meta.wikimedia.org/wiki/Help:Reverting_a_page_to_an_earlier_version#How_to_revert Wikimedia Meta: How to revert]
*[http://meta.wikimedia.org/wiki/Help:Reverting_a_page_to_an_earlier_version#Undo Wikimedia Meta: Undo]

Wiki Team/Guide/Redirect

2009-03-08T11:36:44Z

Dfarning-bot: WikiTeam/WikiGuide/Redirect moved to Wiki Team/Guide/Redirect: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
To '''redirect''' one page to another begin the first page with

<nowiki>#REDIRECT [[</nowiki>''pagename''<nowiki>]]</nowiki>

where ''pagename'' is the final target page.

Extra text after the #REDIRECT command and link is ignored. It is rendered only in preview and in a diff.

If you '''move''' a page (basically, changing the article title), a redirect to the new title will automatically be created under the old article title. You can then choose to leave the redirect in place or delete the old title later.

It can be useful to put redirect pages under common alternate terms for the same topic. But don't get carried away.

An alternative to a redirect is a [[Help:Disambiguation|disambiguation]] page, which links to several possible articles under the same title.

== See Also ==
* [http://meta.wikimedia.org/w/index.php?title=Help:Redirect Wikimedia Meta: Redirect]
* [[Help:Disambiguation]]

Wiki Team/Guide/Recentchanges

2009-03-08T11:36:34Z

Dfarning-bot: WikiTeam/WikiGuide/Recentchanges moved to Wiki Team/Guide/Recentchanges: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Visit the page [[Special:Recentchanges]] to view a list of all the recent changes and additions. There is a link to this in the '''sidebar''' to the left of every page.

== Controls ==
The controls at the top of that page let you select how many recent edits to show, or how recent they must be. You can also choose to hide or show minor edits, patrolled edits, or your own edits.

For each change, the "(diff)" link lets you view the differences between the current version of the article and previous versions. The "(hist)" link lets you view the editing history of that article.

For each entry the name of the user is shown, and is a link to his or her "User" page. There is also a link to his or her "talk" page and a link to his or her contributions to the wiki.

== RSS News ==
You can subscribe to an RSS news feed from this page, which will then show you the most recent changes in your favorite RSS news reader.

Wiki Team/Guide/Wiki Structure

2009-03-08T11:36:24Z

Dfarning-bot: WikiTeam/WikiGuide/PageStructure moved to Wiki Team/Guide/PageStructure: Robot: Moved page

==Organization==
Our challenge is how to organize the wiki so that communities can find the information they need.

===First Level===
Teams are the first level of organization for the wiki. Teams are listed on the navigation bar.

===Second Level===
The second level is the standard team header.
{{TeamHeader|WikiTeam}}

*Home --> Team introduction
*Getting involved --> How to start participating in a team
*Contacts --> How to contact the team
*Resources --> Team resource
*FAQ --> Frequently Asked Questions
*Todo --> Tasks the team is working on
*Meeting --> Agenda for upcoming meeting and logs of past meeting

[[Category:Wiki]]

Talk:Wiki Team/Guide/Page Creation

2009-03-08T11:36:15Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/PageCreation moved to Talk:Wiki Team/Guide/PageCreation: Robot: Moved page

David, man, you are not being distribution neutral here! :P -- Marcopg

== OOPS ==

I need to do a s/disto/Sugar Labs/gc -david

Wiki Team/Guide/Page Creation

2009-03-08T11:36:14Z

Dfarning-bot: WikiTeam/WikiGuide/PageCreation moved to Wiki Team/Guide/PageCreation: Robot: Moved page

=Introduction=
This section deals with how to create pages on the Sugar Labs wiki.

=Search and Integrate. Don't Duplicate.=
Before adding a page to the wiki, make sure you do a comprehensive search.

==Search==
*[[Special:RecentChanges|Recent Changes]] - See where people are currently working.
*[[Special:Search|Search]] - Search or browse the database in various ways.
*[[Special:AllPages|All Pages]] - A list of all pages in the wiki.

==Integrate==
* Don't add another page if a guide, article, or document already exists on a particular subject.
* If you think the existing document could be better, is out of date, or missing something, then improve it!
* Either add or integrate the material with the existing page in the appropriate place.

=Create the Page=
There are several ways to create a new page but all of them require that you first Log-in

==By visiting the page==
# Type the address for the new page into the address bar of your browser. Since the page does not exists because you performed the searches discussed above, MediaWiki will suggest to create it.
# Select a template from the left side of the page that opens. DocumentationTemplate is a default template you can use for any page. There are also some specialized templates to choose from.

==Add a link on another page==
# Edit another page
# Add a link to the new page as <nowiki>[[Name With Spaces]]</nowiki>
# Save the page and click the new link
# Click one of the template names
# Edit your new page and save it

==Page structure==

=== Consistency ===
Try to reuse the markup from a sibling page or another page at the same level.

=== Categorize ===
We make extensive use of category tags in the wiki. Please add an appropriate tag to any new page you create. It is simply a matter of adding a category at the end of the page, e.g., <tt><nowiki>[[Category:Wiki]]</nowiki></tt> will add the [[:Category:Wiki|Wiki category]] to a page. See [[Special:Categories]] for all categories.

[[Category:Wiki]]

Wiki Team/Guide/Overview

2009-03-08T11:36:04Z

Dfarning-bot: WikiTeam/WikiGuide/Overview moved to Wiki Team/Guide/Overview: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
<center>
'''''Quick Summary of Wiki Markup in a Nutshell'''''
</center>

These are the basics you need to know to get started. The rest you'll learn as you go along.

* Just type. Whatever text you type will show up in the body of the page.

* Leaving a blank line will start a new paragraph

* You can use HTML for formatting (like <em>changing fonts</em> or making lists), but not for links.

* Enclosing a word or term in double square brackets makes a link to an article on that topic in the wiki. Example: <tt><nowiki>[[glitch]]</nowiki></tt> produces [[glitch]]

* A URL by itself will be turned into a link to that location. Example: http://www.ligo-wa.caltech.edu

* To make a link with specific text enclose with single square brackets the URL followed by a space and then the link text. Example: <tt><nowiki>[http://www.ligo-wa.caltech.edu LIGO Hanford Observatory]</nowiki></tt> produces [http://www.ligo-wa.caltech.edu LIGO Hanford Observatory]

* Use "=" as quotes to indicate sections, subsections, etc, like this:
==Section Title==
===Subsection title===
====sub-subsection title====
The equal signs must start at the beginning of the line for this to work. The more "="'s the more "sub" the section. You can also use HTML header tags for sections.

* Any line which starts with a space will be shown in a box
like this.
This is useful for examples or for statements you want to stand out, or for code examples. It's also bothersome when done accidentally.

* Preview as you go, to see how it looks. Preview often.

* Don't forget to save! You can get used to editing and previewing over and over again and forget to save your changes.

* A good way to learn new things is to edit pages which already exist to see how it's done.

Remember, "''wiki''" means "''quickly''" in Hawaiian, and that is why they called this a '''''wiki''''' -- because you can learn to edit quickly.

Wiki Team/Guide/Navigation

2009-03-08T11:35:54Z

Dfarning-bot: WikiTeam/WikiGuide/Navigation moved to Wiki Team/Guide/Navigation: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
There are many ways you can get around this site to find whatever you are looking for or to do what needs to be done.

Just as with any web page, links to other pages will show up in a different color -- blue for most links, red for articles which do not yet exist. Link text will also "light up" and be underlined when you hover over it.

Links with the "[[Image:external.png]]" symbol will take you to another web site.

''Clicking on the logo in the upper right corner will always take you back to the main page.''

==Sidebar==
The '''sidebar''' at the left of every page provides you with a variety of useful functions:

* The '''navigation box''' helps you get around this wiki.
* The '''search box''' lets you search for things, or go directly to an article if you already know the name.
* The '''toolbox''' contains special links which are appropriate to the page you are viewing. The "navigation" links will always be the same, but the "toolbox" links can change from page to page.

==See Also==
* [[WikiTeam/WikiGuide/UserLinks]]
* [[WikiTeam/WikiGuide/PageCreation]]
* [[WikiTeam/WikiGuide/Searching]]
* [http://www.mediawiki.org/wiki/Help:Navigation MediaWiki Manual: Navigation]

Wiki Team/Guide/Links

2009-03-08T11:35:44Z

Dfarning-bot: WikiTeam/WikiGuide/Links moved to Wiki Team/Guide/Links: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
You cannot use HTML anchor tags to create hyperlinks, but you don't need to. In fact, just typing a URL will make it an active external link in the text. For example: http://www.cern.ch produces a link to CERN.

There are two general types of links, '''internal''' links to an article (page) in this wiki, or '''external''' links to some other web site.

== Internal Links ==
Internal links are links to an article or section in an article in the same wiki:
{| {{Prettytable}}
|-
|bgcolor="#A7C1F2"|'''Link type'''
|bgcolor="#A7C1F2"|'''You type:'''
|bgcolor="#A7C1F2"|'''You get:'''
|-
|Internal link
|<tt>...this leads to the need for a <nowiki>[[Cosmic Ray Detector]]</nowiki></tt>
| ...this leads to the need for a [[Cosmic Ray Detector]]
|-
|Internal link with alternate link text
|<tt> ...which leads to the need for a <nowiki>[[Cosmic Ray Detector|CRD]]</nowiki></tt>
| ...this leads to the need for a [[Cosmic Ray Detector|CRD]]
|-
|Link to section of an article
|<tt> ...as described in <nowiki>[[WikiTeam/WikiGuide/Formatting#Code Examples|the "code examples" section of the "Formatting" help page]]</nowiki></tt>
| ...as described in [[WikiTeam/WikiGuide/Formatting#Code Examples|the "code examples" section of the "Formatting" help page]]
|}

== External Links ==
External links are links to some other web site:
{| {{Prettytable}}
|-
|bgcolor="#A7C1F2"|'''Link type'''
|bgcolor="#A7C1F2"|'''You type:'''
|bgcolor="#A7C1F2"|'''You get:'''
|-
|URL
|<tt>...may be found at <nowiki>http://www.cern.ch</nowiki></tt>
|...may be found at http://www.cern.ch
|-
|External link, unnamed
|<tt> ...has recently been demonstrated by the <nowiki> QuarkNet[http://quarknet.fnal.gov] project.</nowiki></tt>
| ...has recently been demonstrated by the QuarkNet[http://quarknet.fnal.gov] project.
|-
|External link, named
|<tt> ...as explained in the <nowiki>[http://www.nytimes.com New York Times]</nowiki></tt>
| ...as explained in the [http://www.nytimes.com New York Times]
|}

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Links MediaWiki Manual: Links]
* [[WikiTeam/WikiGuide/InterwikiLinking]]

Talk:Wiki Team/Guide/Interwiki Linking

2009-03-08T11:35:35Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/InterwikiLinking moved to Talk:Wiki Team/Guide/Interwiki Linking: Robot: Moved page

Should be adjusted to match the interwiki links table in use here. Or removed if you don't have any. --[[User:Eric Myers|Eric]] 13:50, 16 May 2008 (UTC)

Wiki Team/Guide/Interwiki Linking

2009-03-08T11:35:34Z

Dfarning-bot: WikiTeam/WikiGuide/InterwikiLinking moved to Wiki Team/Guide/Interwiki Linking: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
You can easily create links to other wiki sites for which we have created inter-wiki shortcuts.
For example, the prefix <tt>:mw:</tt> in a wiki link makes it a link to the MediaWiki site rather than this glossary. A simple example of this is:

<pre>[[:mw:Help:Editing pages|Editing pages]]</pre>

which creates the link "[[:mw:Help:Editing pages|Editing pages]]". The prefix <tt>:m:</tt> will create a link to a page on the "meta" site.

Use the prefix <tt>:w:</tt> to create a link to the Wikipedia, as in

<pre>[[:w:QuarkNet|QuarkNet]]</pre>

which creates the link "[[:w:QuarkNet|QuarkNet]]"

== Prefixes ==
The interwiki linking prefixes in use on this site are:
<center>
{| border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;"
| bgcolor="#8DA7D6" align="center"|'''prefix'''
| bgcolor="#8DA7D6" align="center"|'''direction'''
| bgcolor="#8DA7D6" align="center"|'''usage example'''

|-
|glossary
|<nowiki>http://i2u2.spy-hill.net/glossary/</nowiki>
|<code><nowiki>[[glossary:glitch]]</nowiki></code>
|-
|lib
|<nowiki>http://i2u2.spy-hill.net/glossary/</nowiki>
|<code><nowiki>[[glossary:glitch]]</nowiki></code>
|-
|wikipedia
|<nowiki>http://en.wikipedia.org/wiki/</nowiki>
|<code> <nowiki>[[wikipedia:Compass]]</nowiki></code>
|-
|w
|<nowiki>http://en.wikipedia.org/wiki/</nowiki>
|<code> <nowiki>[[w:QuarkNet]]</nowiki></code>
|-
|mediawiki
|<nowiki>http://www.mediawiki.org/wiki/</nowiki>
|<code><nowiki>[[mediawiki:Wiki]]</nowiki></code>
|-
|mw
|<nowiki>http://www.mediawiki.org/wiki/</nowiki>
|<code><nowiki>[[mw:Main Page]]</nowiki></code>
|-
|meta
|<nowiki>http://meta.wikimedia.org/wiki/</nowiki>
|<code><nowiki>[[meta:Main Page]]</nowiki></code>
|-
|m
|<nowiki>http://meta.wikimedia.org/wiki/</nowiki>
|<code><nowiki>[[m:Main Page]]</nowiki></code>
|-
|wiktionary
|<nowiki>http://en.wiktionary.org/wiki/</nowiki>
|<code> <nowiki>[[wiktionary:Main Page]]</nowiki></code>
|-
|wikibooks
|<nowiki>http://en.wikibooks.org/wiki/</nowiki>
|<code><nowiki>[[wikibooks:Main Page]]</nowiki></code>
|-
|wikimedia
|<nowiki>http://wikimediafoundation.org/wiki/</nowiki>
|<code><nowiki>[[wikimedia:Main Page]]</nowiki></code>
|-
|wikiquote
|<nowiki>http://en.wikiquote.org/wiki/</nowiki>
|<code><nowiki>[[wikiquote:Main Page]]</nowiki></code>
|-
|wikisource
|<nowiki>http://en.wikisource.org/wiki/</nowiki>
|<code><nowiki>[[wikisource:Main Page]]</nowiki></code>
|-
|wikispecies
|<nowiki>http://species.wikimedia.org/wiki/</nowiki>
|<code><nowiki>[[wikispecies:Main Page]]</nowiki></code>
|}
</center>

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Interwiki_linking MediaWiki Manual: Interwiki Linking]

Talk:Wiki Team/Guide/Images

2009-03-08T11:35:25Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/Images moved to Talk:Wiki Team/Guide/Images: Robot: Moved page

Should use a different example image. The LHO control room is just what we used on I2U2. --[[User:Eric Myers|Eric]] 13:35, 16 May 2008 (UTC)

I added an image I had of an XO running xeyes, but any representative image will do, so feel free ro replace it with something more appropriate. --[[User:Eric Myers|Eric]] 14:28, 16 May 2008 (UTC)

Wiki Team/Guide/Images

2009-03-08T11:35:24Z

Dfarning-bot: WikiTeam/WikiGuide/Images moved to Wiki Team/Guide/Images: Robot: Moved page

Talk:Wiki Team/Guide/Formatting

2009-03-08T11:35:15Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/Formatting moved to Talk:Wiki Team/Guide/Formatting: Robot: Moved page

==Help with templates==
Please request template help below.

Wiki Team/Guide/Formatting

2009-03-08T11:35:14Z

Dfarning-bot: WikiTeam/WikiGuide/Formatting moved to Wiki Team/Guide/Formatting: Robot: Moved page

Talk:Wiki Team/Guide/File Upload

2009-03-08T11:35:05Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/FileUpload moved to Talk:Wiki Team/Guide/File Upload: Robot: Moved page

The "File:" pseudo-namespace requires a configuration hack. I'll check my notes on what I needed to do and put it here. It's more intuitive for non-technical folk to reference a non-image document file with File: than with Image: (example: [http://www13.i2u2.org/cosmic/library/index.php/QuarkNet_Fellows_Library QuarkNet Fellows Library] where they use the wiki mainly for document distribution). --[[User:Eric Myers|Eric]] 13:40, 16 May 2008 (UTC)

Wiki Team/Guide/File Upload

2009-03-08T11:35:04Z

Dfarning-bot: WikiTeam/WikiGuide/FileUpload moved to Wiki Team/Guide/File Upload: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
* Files which do not contain images may be uploaded with the same upload page used to upload images (which is at [[Special:Upload]]). There is usually a link to this called [[Special:Upload|Upload file or image]] in the '''toolbox''' area of the '''sidebar''' to the left of every page.

* Please be sure to fill in the "Description" field for every file you uplode. Specify both the contents and purpose of the file, as well as the author(s), especially if you are not one of them.

* Please do not upload files which cannot be freely distributed due to copyright restrictions.

* To create a link to an uploaded file use the "File:" pseudo-namespace. The syntax is like this:
<nowiki>[[File:NameOfFile.pdf]]</nowiki>

* As with other links you can also specify alternative text for the link after a "|", as in this example:
<nowiki>[[File:LIGO-I2U2.ppt|Eric's talk at West Point]]</nowiki>

* The allowed file types are <tt>pdf</tt>, <tt>.doc</tt>, <tt>.ppt</tt>, and <tt>xls</tt>. We can easily add something else if there is a need for it.

Wiki Team/Guide/Editing Pages

2009-03-08T11:34:54Z

Dfarning-bot: WikiTeam/WikiGuide/EditingPages moved to Wiki Team/Guide/Editing Pages: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
==How to create a new page==
This is covered on a separate page: [[WikiTeam/WikiGuide/PageCreation]]

==How to edit an existing page==

* To edit an existing page, visit the page and click on the '''edit''' tab at the top of the page. The text of the page will show up in a large text entry window.

* Make whatever changes or additions you need.

* Enter a description of what you've done in the "'''Summary:'''" box.

* Use '''Show preview''' to see your changes before they are saved. Repeat as necessary until you get it right.

* Press '''Save page''' when done.

==How to edit one section==

* Each section has it's own "[edit]" link at the far right of the page. Simply click on that link to edit only that one section.

==Suggestions and Hints==

* If you have lots of text to add or changes to make, do it in steps, saving after each step.

* Don't forget to '''Save page''' when you are done previewing. (It can be too easy to forget this!)

* The '''Editing help''' link at the bottom of the page will give you a quick summary of how to edit, with links to more detailed references, and this will be in a new window or tab.

* If things really get messed up, there is a '''Cancel''' link at the bottom of the editing page.

==See Also==
* [[WikiTeam/WikiGuide/PageCreation]]
* [[WikiTeam/WikiGuide/Overview]] - quick summary of wiki markup
* [[WikiTeam/WikiGuide/Formatting]]

Wiki Team/Guide/Citations

2009-03-08T11:34:44Z

Dfarning-bot: WikiTeam/WikiGuide/Citations moved to Wiki Team/Guide/Citations: Robot: Moved page

#REDIRECT [[WikiTeam/Wikiguide/Citations]]

Talk:Wiki Team/Guide/Categories

2009-03-08T11:34:35Z

Dfarning-bot: Talk:WikiTeam/WikiGuide/Categories moved to Talk:Wiki Team/Guide/Categories: Robot: Moved page

The page says there is a link to [[Special:Categories]] in the sidebar, but there isn't. I'll leave it that way, in hopes that it will get added. --[[User:Eric Myers|Eric]] 13:12, 16 May 2008 (UTC)

Wiki Team/Guide/Categories

2009-03-08T11:34:34Z

Dfarning-bot: WikiTeam/WikiGuide/Categories moved to Wiki Team/Guide/Categories: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Articles may be classified according to categories. Proper classification of articles can make searching the wiki much easier.

An article can be in any number of categories.

== For Readers ==
Use the page [[Special:Categories]] to see a list of categories. There is a link to it in the '''sidebar''' on the left side of every page. <-- OR THERE SHOULD BE! -->

Follow a category link in the list of categories to see all the articles (pages) in that category, organized alphabetically.

The categories for an article are listed at the bottom of the page. Each is a link to a list of all pages in that category.

== For Editors ==
To put an article in a category you simply need to add a category link to the article. A category link looks like:
<nowiki>[[Category:Some topic]]</nowiki>

How you pick the categories is up to you. Be careful to choose reasonable categories that make sense for the subject matter in the wiki. There's no point in having each article in it's own category, or in having all articles in the same category. Use the category mechanism to help divide up the wiki for easier searching.

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Categories MediaWiki Manual: Categories]
* [http://meta.wikimedia.org/wiki/Help:Category Wikimedia Meta: Category]

Wiki Team/Guide/Allpages

2009-03-08T11:34:24Z

Dfarning-bot: WikiTeam/WikiGuide/Allpages moved to Wiki Team/Guide/Allpages: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
Use the page [[Special:Allpages]] to get a list of all pages (articles) contained within the wiki.
You will find it in the list of [[Special:Specialpages|Special pages]], which you can ready from the Toolbox to the left of every page. 

When the list of articles is very large it can be useful to use the control at the top of the page to list only articles at or after a given article name.

The articles (pages) which make up the content of the wiki are in a default namespace called "(Main)". Other supporting pages are in other "namespaces", such as "Talk", "User", "UserTalk", "Help", "Templates", and "Category". You can also use this special page to view a list of all the pages in those special namespaces.

== See Also ==
* [http://www.mediawiki.org/wiki/Help:Templates MediaWiki Manual: Templates]
* [http://www.mediawiki.org/wiki/Help:Categories MediaWiki Manual: Categories]
* [http://www.mediawiki.org/wiki/Help:Namespaces MediaWiki Manual: Namespaces]

Translation Team/Wiki Translation/lang-es

2009-03-08T11:34:04Z

Dfarning-bot: WikiTeam/Translation/lang-es moved to Wiki Team/Translation/lang-es: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
{{TeamHeader|WikiTeam/Translation}}</noinclude>
{{Translation
| lang = es
| source = WikiTeam/Translation
| version = 7185}}
{{TranslationInProgress}}
Participar en proyectos de traducción puede ser divertido y gratificante. Sin embargo, la naturaleza volátil de wiki puede hacer las cosas difíciles para el traductor. Estas complicaciones pueden superarse siguiendo unas reglas simples y usando prácticas de trabajo estandarizadas. Se espera que esto permita a cualquier persona colaborar en el esfuerzo de traducción y, al mismo tiempo divertirse en el proceso.

{{ Translated text |
Taking part in translation projects can be fun and rewarding. However the volatile nature of wiki can make things difficult for the translator. These complications can be overcome by following a few simple rules and using standardised work practices. It is hoped that this will allow anybody to collaborate in the translating effort and at the same time have fun in the process.
| display = none }}

'''Las plantillas de traducir ahora tratan de dar un texto de ayuda para guiarlo a través del proceso. Este texto de ayuda es la mejor guía para la traducción. Pruebe a empezar poniendo la plantilla <nowiki>{{Translations}}</nowiki> en su página de inicio y siga las instrucciones recursivamente, grabando la página correspondiente, y leyendo las nuevas instrucciones. El material que aparece a continuación se conserva en caso de que los textos breves de ayuda lo lleven a confundirse, sin embargo, en algunos casos es obsoleta.'''

{{ Translated text |
'''The translate templates now attempt to give help text to guide you through the process. This help-text is the best guide for translating. Try starting out by putting the <nowiki>{{Translations}}</nowiki> template on your home page and recursively following the instructions, saving the relevant page, and reading the new instructions. The material below is preserved in case the brief help texts leave you confused, yet in some cases it is out-of-date.'''
| display = none }}

== Resumen paso a paso ==

Desde el punto de vista del wiki, hay básicamente tres formas de enlazar una página traducida:

# [[Configurar la página fuente: asegurarse de que haya una plantilla <nowiki>{{Translations}}</nowiki>| modificar la fuente de la página]]&mdash si nunca se ha traducido;
# [[#Modifying the language bar|agragar una referencia]] — apuntar/vincular la traducción de manera estándar, y
# [[#Setting up the translated page|acondicionar la página traducida]] — añadiendo alguna estructura de ayuda.
La mayoría de las veces, los [[translators|traductores]] sólo se enfrentarán con los dos últimos pasos (la creación y la vinculación de la traducción)

{{ Translated text |
From the point-of-view of the wiki, there are basically three tasks to hook up a translated page:
# [[Setting up the source page: ensure it has a <nowiki>{{Translations}}</nowiki> template|modify the source page]] — if it has never been translated;
# [[#Modifying the language bar|adding a reference]] — point/link to the translation in a standard way; and
# [[#Setting up the translated page|conditioning the translated page]] — adding some helper structure.
Most of the time, [[translators]] will only deal with the last two steps (setting up and linking the translation).
| display = none }}
Puede ver una vista general de la [[#Anatomy of a wiki-page|estructura relevante]] de una página, y un [[#Full finished example|ejemplo de acabado completo]] hacia el final de esta página.
{{ Translated text |
You can see an overview of the [[#Anatomy of a wiki-page|relevant structure]] of a page, and a [[#Full finished example|full finished example]] towards the end of this page.
| display = none }}

=== Editando la página fuente: asegurarse que tiene
Si la página a traducir ya tiene una barra de idiomas, puede pasar a [[#Modifying the language bar]]
{{ Translated text |
If the page to translate already has a language bar, you can skip down to [[#Modifying the language bar]].
| display = none }}

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <span style="font-size:80%">''(translated page does not exist—yet)''</span>

|- valign="top"
|
<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|}
</div>

==== Añadiendo la barra de idiomas ====
Aunque es raro, puede que sea necesario traducir una página que nadie más ha traducido antes. En ese caso, debe ser añadida una barra de navegación de las traducciones en la página original.

{{ Translated text |
Although it is rare, it may be necessary to translate a page that nobody else has translated yet. In that case, a translations navigation bar must be added in the original page.
| display = none }}

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <span style="font-size:80%">''(translated page does not exist—yet)''</span>

|- valign="top"
|
'''<nowiki>{{Translations}}</nowiki>'''

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|}
</div>

==== Configurando las traducciones (/translations) ====
Debería seguir el enlace <tt><nowiki>[[Original page/translations]]</nowiki></tt> para editar la página que agrupa las traducciones de una página en particular, y debería verse de esta forma:

{{ Translated text |

You should follow the <tt><nowiki>[[Original page/translations]]</nowiki></tt> link in order to edit the page that groups the translations of a particular page, and should look something like this:
| display = none }}

Para editar la página que agrupa las traducciones de una página en particular, siga el enlace ''<nowiki>[[Original page/translations]]</nowiki>''. Éste debería verse de la siguiente forma:

{{ Translated text |
To edit the page that groups the translations of a particular page, follow the ''<nowiki>[[Original page/translations]]</nowiki>'' link. It should look something like the following:
| display = none }}

<div style="font-size:80%; ">
{| cellspacing=0

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page/translations]]</nowiki>

|- valign="top"
|
<nowiki>{{translationlist | xx | origlang=en}}</nowiki>
|}
</div>

La página resultante tendrá un enlace de color rojo, denotando un enlace perdido/roto a su futura traducción. No se preocupe, arreglará esto en el siguiente paso.

{{ Translated text |
The resulting page will have a red colored link, denoting a missing/broken link to your future translation. Don't worry, you'll fix that in the next step.
| display = none }}

'''NOTA:''' La plantilla Translationlist usa la forma "<tt>[[Sugar Labs/lang-es]]</tt>" para páginas traducidas. Si más tarde desea cambiarlo para que el título de la página esté en el idioma al cual se está traduciendo (p.e. "<tt>[[Azúcar Labs]]</tt>"),utilize la función "mover" ("move") del wiki; esto automáticamente crea un enlace de redirección de forma que los enlaces interlingüísticos aún funcionen.

{{ Translated text |
'''NOTE:''' The Translationlist template uses the form "<tt>[[Sugar Labs/lang-es]]</tt>" for translated pages. If you want to change it later so that the page title is in the target language (e.g. "<tt>[[Azúcar Labs]]</tt>"), use the "move" function of the wiki; this automatically creates a redirect link so that the interlanguage links still work.
| display = none }}

=== Modificando la barra de idiomas ===

Abajo hay un ejemplo de una barra de idiomas típica. La página que puede requerir traducción tendrá un enlace como <tt>'''+/-'''</tt> al extremo derecho de la barra. (La cual no se muestra en este ejemplo.) Éste es un enlace la pa página de edición para la barra de idiomas. Para crear un enlace, por ejemplo cuando se añade un nuevo idioma en la barra de idiomas, siga este enlace <tt>'''+/-'''</tt> para ir a la página de edición. Luego añada el código apropiado para el nuevo idioma.
<div style="font-size:90%; margin-left:5%; margin-right:5%; ">
{{Translations | {{:Sugar Labs/translations}}}}
</div>
{{ Translated text |
Below is an example of a typical language bar. The page that may need translation would have a link shown as <tt>'''+/-'''</tt> to the far right of the bar. (Not shown on this example.) This is a link to the editing page for the language bar. To create a link, for example when adding a new language on the language bar, follow this <tt>'''+/-'''</tt> link to go to the editing page. Then add the appropriate code for the new language.
<div style="font-size:90%; margin-left:5%; margin-right:5%; ">
{{Translations | {{:Sugar Labs/translations}}}}
</div>
| display = none }}

Cuando inserte el enlace a su página, porfavor mantenga las cosas '''en orden alfabético denotado por la secuencia <tt>/lang-[[#lang|xx]]</tt>''' (Si, por ejemplo, está añadiando <tt>/lang-de</tt> debería estar antes del enlace a 'english'). Además, fíjese en los espacios alrededor del ' | ' que separa cada idioma. Vea [[#Configurando las traducciones (/translations)|arriba en <tt>/translations</tt>]] para más información.

{{ Translated text |
{{Translations | {{:Sugar Labs/translations}}}}
</div>
When inserting the link to your page, please keep things '''in alphabetical order denoted by the <tt>/lang-[[#lang|xx]]</tt> sequence''' (if you're adding say <tt>/lang-de</tt> it should go before the link to 'english'). Also, note the spaces around the '|' that separate each language. See [[#Setting up the /translations|above on <tt>/translations</tt>]] for more info.
| display = none }}

=== Creación de la página traducida ===

A pesar de que el traductor tiene tanta libertad para editar y traducir como es posible cuando se traduce el wiki, hay una regla que debe respetarse en todo momento. La página traducida debe declararse como [[Template:Translation|<nowiki>{{Translation}}</nowiki>]]. (Por favor tenga en cuenta el uso del "singular". Plural es para la página original y esta tendrá muchas traducciones.)

{{ Translated text |
Although the translator is given as much freedom to edit and to translate as possible when translating the wiki, there is one rule that must be adhered to at all times. The translated page must be declared as a [[Template:Translation|<nowiki>{{Translation}}</nowiki>]]. (Please note the use of "singular". Plural is for the original page and it will have many translations.)
| display = none }}

Hay otro par de bits de recomendación que pueden mejorar la calidad del proceso de traducción. En primer lugar, por favor mantenga la navegación y la vinculación dentro de las páginas traducidas simple y fácil de seguir. En segundo lugar, preservar el texto original en la traducción puede simplificar la revisión por pares y ayudar con el mantenimiento.

{{ Translated text |
There are couple of other bits of advice that may improve the quality of the translation process. First, please keep navigation and linking within the translated pages simple and easy to follow. Secondly, preserving the original text in the translation may simplify peer review and help with maintenance.
| display = none }}

La forma más rápida de crear una página es volver a la página original, y luego copiar el '''texto-wiki'''. Esto puede hacerse ya sea siguiendo el vínculo ''editar'' (''edit'') o a través de ''ver la fuente'' (view sorce) si la página está protegida. A continuación copie toda la página y péguela en la nueva página.

{{ Translated text |
The quickest way to set up a page is by going back to the
original page, then copying the '''wiki-text'''. This can be done either by following the ''edit'' link or through ''view source'' if the page is protected. Then copy the whole page and paste it onto the new page.
| display = none }}

{{anchor|Adding the [[Template:Translation|Translation template]]}}
==== Agregando la [[Template:Translation|Plantilla de Traducción]] ====

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <nowiki>[[</nowiki>Original page/lang-[[#lang|xx]]<nowiki>]]</nowiki><span style="font-size:80%"><br>''(translated page name)''</span>

|- valign="top"
|
<nowiki>{{Translations}}</nowiki>

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|
'''<nowiki>{{</nowiki>Translation'''
'''| lang = [[#lang|xx]]'''
'''| source = [[#source|Original page]]'''
'''| version = [[#version|yyyy]]<nowiki>}}</nowiki>'''

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|}
</div>

Para una explicación completa de los parámetros, véase las [[#Notes|Notes]] a continuación, en resumen: '''lang '''— es el [http://www.iana.org/assignments/language-subtag-registry código de idioma IANA] (generalmente 2 letras, sin ninguna segmentación adicional— es decir, en lugar de ''<tt>lang-pt-BR </tt>''(portuguese brasileño), simplemente ''<tt>lang - pt</tt>'' (portugués)— sólo para mantener las cosas simples y neutrales.

{{ Translated text |
For a full explanation of the parameters, see the [[#Notes|Notes]] below, in short:
'''lang''' — is the [http://www.iana.org/assignments/language-subtag-registry IANA language code] (usually 2 letters, without any further segmentation—ie: instead of ''<tt>lang-pt-BR</tt>'' (brazilian portuguese), just ''<tt>lang-pt</tt>'' (portuguese)—just to keep things simple and neutral.
| display = none }}

{{anchor|Adding the [[Template:TranslationInProgress|TranslationInProgress template]]}}
==== Agregando la [[Template:TranslationInProgress|Plantilla de Traducción en progreso]] ====

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <nowiki>[[</nowiki>Original page/lang-[[#lang|xx]]<nowiki>]]</nowiki><span style="font-size:80%"><br>''(translated page name)''</span>

|- valign="top"
|
<nowiki>{{Translations}}</nowiki>

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|
<nowiki>{{</nowiki>Translation
| lang = [[#lang|xx]]
| source = [[#source|Original page]]
| version = [[#version|yyyy]]<nowiki>}}</nowiki>
'''<nowiki>{{</nowiki>TranslationInProgress<nowiki>}}</nowiki>'''

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|}
</div>

El objetivo principal de la platilla [[Template:TranslationInProgress|<nowiki>{{TranslationInProgress}}</nowiki>]] es informar a los lectores que una página determinada aún no está terminada, por lo que puede esperar la presencia de texto sin traducir o que no se ha revisado lo suficiente y, por tanto, puede no estar completamente terminada aun. Paralelamente al aviso al lector, el aviso crea un grupo con estas páginas en la [[:Category:TranslationInProgress|TraduccionEnProgreso]] lo que permite que otros traductores las encuentren y colaborar, revisar, hacer comentarios, etc sobre ellas.

{{ Translated text |
The main purpose of the [[Template:TranslationInProgress|<nowiki>{{TranslationInProgress}}</nowiki>]] template is to inform the readers that a particular page is still not finished, therefore they can expect the presence of untranslated text or that it hasn't been reviewed enough and thus may not be quite done yet. Parallel to that notice to the reader, it does a grouping of them in the [[:Category:TranslationInProgress|TranslationInProgress]] thus allowing other translators to find them and collaborate, review, make comments, etc. on them.
| display = none }}

{{anchor|Translating section headers}}
==== Traducción de títulos de sección ====

Cuando traduzca los títulos de sección, la mejor práctica es preservarlas como anchors. A continuación, añada el título traducido debajo del mismo.

{{ Translated text |
When translating section headers, the best practice is to preserve them as anchors. Then add the translated header under it.
| display = none }}

Por ejemplo, si el título de sección se llama "Alguna título de sección" y es traducida al alemán como "Einige Paragraph Kopfzeile". El texto original "Algun título de sección" se conserva envolviéndolo entre llaves como sigue:

<nowiki>{{anchor|Algun título de sección}}</nowiki>

{{ Translated text |
For example if the section header is called "Some Section Header" and it is translated into German in the form of "Einige Paragraph Kopfzeile". Original text "Some Section Header" is preserved by wrapping it between curly braces like the following:

<nowiki>{{anchor|Some Section Header}}</nowiki>
| display = none }}

A continuación, el texto traducido "Einige Paragraph Kopfzeile" se coloca debajo del mismo. Juntos se verán como lo siguiente cuando se haya terminado:

<nowiki> {{anchor|Algun título de sección}} </nowiki><br>
<nowiki> == Einige Paragraph Kopfzeile == </nowiki><br>

{{ Translated text |
Then the translated text "Einige Paragraph Kopfzeile" is placed under it. Together it will look like the following when finished:

<nowiki> {{anchor|Some Section Header}} </nowiki><br>
<nowiki> == Einige Paragraph Kopfzeile == </nowiki><br>
| display = none }}

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <nowiki>[[</nowiki>Original page/lang-[[#lang|xx]]<nowiki>]]</nowiki><span style="font-size:80%"><br>''(translated page name)''</span>

|- valign="top"
|
<nowiki>{{Translations}}</nowiki>

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|
<nowiki>{{</nowiki>Translation
| lang = [[#lang|xx]]
| source = [[#source|Original page]]
| version = [[#version|yyyy]]<nowiki>}}</nowiki>
<nowiki>{{</nowiki>TranslationInProgress<nowiki>}}</nowiki>

'''<nowiki>{{anchor|Some header}}</nowiki>'''
<nowiki>== Un titular ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

'''<nowiki>{{anchor|Another header}}</nowiki>'''
<nowiki>== Otro titular ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|}
</div>

{{anchor|Translating links}}

==== Traduciendo enlaces ====

Cuando traduzca enlaces, el texto original se conserva mediante el uso de lo que se llama "vínculos entubados" (piped links). Al colocar el símbolo "|" entre el texto original y texto traducido, ambos conectados entre sí a través de una tubería. Por ejemplo, si "algun-enlace" se va a traducir al alemán como "einige-link", se terminará viendo como lo siguiente:
<nowiki>[[algun-enlace|einige-link]]</nowiki>

{{ Translated text |
When translating links, the original text is preserved by using what is called "piped links". By placing the symbol "|" between original text and the translated text, both become connected together through a pipe. For example if "some-link" is to be translated into German as "einige-link", it will end up looking like the following:

<nowiki>[[some-link|einige-link]]</nowiki>
| display = none }}

Como resultado, siguiendo "einige-link" se conectará a "algun-enlace". El lector sólo vera el vínculo traducido "einige-enlace".

{{ Translated text |
As a result, following "einige-link" will connect to "some-link". The reader will only see the translated link "einige-link".
| display = none }}

{{anchor|Linking to a page in particular language}}

==== Vinculando a una página en un lenguaje particular ====

Cuando se enlaza a una página traducida a un idioma en particular use / lang-xx para apuntar a esa traducción en particular.

<nowiki>[[algún-vinculo/lang-de|einige-link]]</nowiki>

{{ Translated text |
When linking to a translated page in a particular language use the /lang-xx to point to that particular translation.

<nowiki>[[some-link/lang-de|einige-link]]</nowiki>
| display = none }}

{{anchor| Translating texts}}
==== Traduciendo textos ====

Cuando traduzca un texto, es útil preservar el texto original colocándolo dentro de una función [[Template:Translated_text|<nowiki>{{Translated text}}</nowiki>]]. "display = ''value'' " es un parámetro que se puede utilizar para controlar si el texto original es visible o no para el lector.

{{ Translated text |
When translating text, it is useful to preserve original text by wrapping them inside [[Template:Translated_text|<nowiki>{{Translated text}}</nowiki>]] function. "display = ''value''" parameter
can be used to control whether the original text is visible to the reader or not.
| display = none }}

Texto original invisible para el lector (display = none).
<nowiki>
{{ Translated text |
original text
more original text
yet more original text
final original text
| display = none }}
</nowiki>

{{ Translated text |
Original text invisible to reader (display = none).
<nowiki>
{{ Translated text |
original text
more original text
yet more original text
final original text
| display = none }}
</nowiki>
| display = none }}

Texto original visible para el lector (display = block).

<nowiki>
{{ Translated text |
original text
more original text
yet more original text
final original text
| display = block }}
</nowiki>

{{ Translated text |
Original text visible to reader (display = block).
<nowiki>
{{ Translated text |
original text
more original text
yet more original text
final original text
| display = block }}
</nowiki>
| display = none }}

Por favor, consulte [[Template:Translated_text|aquí]] para más información.

{{ Translated text |
Please see [[Template:Translated_text|here]] for more information.
| display = none }}

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <nowiki>[[</nowiki>Original page/lang-[[#lang|xx]]<nowiki>]]</nowiki><span style="font-size:80%"><br>''(translated page name)''</span>

|- valign="top"
|
<nowiki>{{Translations}}</nowiki>

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|
<nowiki>{{</nowiki>Translation
| lang = [[#lang|xx]]
| source = [[#source|Original page]]
| version = [[#version|yyyy]]<nowiki>}}</nowiki>
<nowiki>{{</nowiki>TranslationInProgress<nowiki>}}</nowiki>

<nowiki>{{anchor|Some header}}</nowiki>
<nowiki>== Un titular ==</nowiki>

Algo de texto bla... <br>bla... '''<nowiki>[[</nowiki>#Another header|Otro titular<nowiki>]]</nowiki>''' <br>... blah
'''<nowiki>{{ Translated text |</nowiki>'''
Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah
'''| display = [[#display|block]]<nowiki>}}</nowiki>'''

<nowiki>{{anchor|Another header}}</nowiki>
<nowiki>== Otro titular ==</nowiki>

Algo más de texto bla... <br>bla... <nowiki>[[</nowiki>Another page'''/lang-[[#lang|xx]]|Otra página'''<nowiki>]]</nowiki> <br>y <nowiki>[[</nowiki>Another page'''/lang-[[#lang|xx]]#section|sección'''<nowiki>]]</nowiki> <br>... bla
'''<nowiki>{{ Translated text |</nowiki>'''
Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
'''| display = [[#display|block]]<nowiki>}}</nowiki>'''
|}
</div>

{{anchor|Handling translated links that point to a non-existent page}}
==== Manejando la traducción de enlaces que apuntan a una página inexistente ====

Al principio, cualquier vínculo que se 'traduzca' muy probablemente apunte a una página que no existe; no se preocupe. Hay dos alternativas:
* deje que el wiki las maneje a través de [[Special:Wantedpages]]
* haga un último esfuerzo de traducción: redirecciones dedicadas.

{{ Translated text |
At the beginning, any link you 'translate' will most likely point to a non-existing page; don't worry. There are two alternatives:
* let the wiki handle them through [[Special:Wantedpages]]
* make one last translating effort: dedicated redirects
| display = none }}

La primera alternativa es la más simple pero también la más difícil para el lector (aterrizar en 'opción de crear una página' es dificilmente la mejor alternativa). Otra desventaja, es que va a ser difícil detectar esas 'páginas requeridas' para un idioma específico, ya que estarán en la misma lista que todas las demás 'páginas traducidas faltantes' en otros idiomas ''mas'' todas las ''páginas naturalmente faltantes'' en el wiki (una larga lista debido a razones históricas).

{{ Translated text |
The first alternative is the simplest but also the hardest on the reader (lands them on the 'create page option' which is hardly the best alternative). Another downside, is that it'll be hard to detect those 'wanted pages' for a specific language, as they will be in the same list as all other 'missing translated pages' in other languages ''plus'' all the ''naturally missing pages in the wiki'' (a long list due to historical reasons).
| display = none }}

La segunda alternativa recomendada, es añadir la plantilla de {{tl|subst:requesttranslation}} a la página de destino. Esta se auto-sustituye con el reemplazo:

{{ Translated text |
The second, recommended alternative, is to add the {{tl|subst:requesttranslation}} template to the target page. This self-substitutes with the replacement:
| display = none }}

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]<nowiki>|annuder paij]]</nowiki>

|- valign="top"
|
<nowiki>#REDIRECT [[Another page]]</nowiki>
<nowiki>[[</nowiki>Category:Translations wanted lang-[[#lang|xx]]<nowiki>]]</nowiki>
|- valign="top"
|
<nowiki>{{translation | lang = es | source = Another page | status = wanted }}</nowiki>
|}
</div>

Nota: la última opción sólo está disponible para los idiomas cuyas " instrucciones de traducción en línea" no son de color rojo en [[Translating#multi-lingual_navigation_templates|esta tabla]]. Utilice los vínculos de ahí para crear las instrucciones para su idioma, basado en Inglés o español, en una plantilla llamada "translation/no translation/lang-xx"

{{ Translated text |
Note: the last option is only available for those languages whose "inline translation instructions" are not red in [[Translating#multi-lingual_navigation_templates|this table]]. Use the links there to create instructions for your language, based on English or Spanish, in a template named "translation/no translation/lang-xx".
| display = none }}

; ADVERTENCIA : '''Asegúrese''' de que la página original '''no''' está vinculando a un '''REDIRECCIONAMIENTO (REDIRECT) '''. Si ese es el caso, debe cambiar la meta a la ''página real y crear allí la subpágina <tt>/lang-[[#lang|xx]]</tt>''. Por ejemplo, si el <tt><nowiki>[[Foo]]</nowiki></tt> es en realidad una redirección a <tt><nowiki>[[Bar]]</nowiki></tt>, entonces usted debe crear '''<tt><nowiki>[[</nowiki>Bar/lang-[[#lang|xx]]<nowiki>]]</nowiki></tt>''' en lugar de <tt><nowiki>[[</nowiki>Foo/lang-[[#lang|xx]]<nowiki>]]</nowiki></tt> y cambiar el enlace de referencia en consecuencia.

{{ Translated text |
; WARNING : Make '''sure''' that the original page is '''not''' linking to a '''REDIRECT'''. If that is the case, you should change the target to the ''real page and create there the <tt>/lang-[[#lang|xx]]</tt> subpage''. For example, if the <tt><nowiki>[[Foo]]</nowiki></tt> actually is a redirect to <tt><nowiki>[[Bar]]</nowiki></tt>, then you should create the '''<tt><nowiki>[[</nowiki>Bar/lang-[[#lang|xx]]<nowiki>]]</nowiki></tt>''' instead of <tt><nowiki>[[</nowiki>Foo/lang-[[#lang|xx]]<nowiki>]]</nowiki></tt> and change the referencing link accordingly.
| display = none }}

Esto servirá a tres propósitos, en primer lugar la página al menos, pondrá al lector en la página correcta (aunque no en el idioma correcto). En segundo lugar, la ''categoría (Category)'' va a permitir una forma sencilla de comprobar 'que falta'. Por último, y utilizando el '' Que enlaza aquí'' de la '''caja de herramientas (toolbox)''' se puede saber cuántas referencias a la página faltante existen, dando un cierto sentido de ''necesidad'' de ella y, por consiguiente, orientar el esfuerzo de traducción.

{{ Translated text |
This will serve three purposes, first the page will at least take the reader to the right page (albeit not in the correct language). Secondly, the ''Category'' will allow a simple way to check 'what is missing'. Finally, and using the ''What links here'' from the '''toolbox''' you can find out how many references to the missing page exist, giving some sense of ''need'' for it and thus guiding the translating efforts.
| display = none }}

'''Por favor NO adicione'''estas ''falsas traducciones rediridas'' a las páginas <tt>/translations</tt>/, ya que no tiene sentido anunciar una traducción que aún no existe. Sólo cuando la redirección (REDIRECT) se hace a una verdadera traducción (en curso o de otro tipo) añada el vínculo a la página de navegación de idiomas.

{{ Translated text |
'''Please do NOT add''' these ''fake translation redirects'' to the <tt>/translations</tt> page, as it doesn't make sense to advertise a translation that doesn't yet exist. Only when the REDIRECT is made into a real translation (ongoing or otherwise) add the link to the language navigation page.
| display = none }}

{{anchor|Full example of a wiki-page}}

== Ejemplo completo de una pagina-wiki ==
{{anchor|Anatomy of a wiki-page}}
=== Anatomía de una página-wiki ===

<div style="font-size:80%; ">
{|
|+ Esta página de 'ejemplo' incluye todos los elementos que requieren algún nivel de consideración cuando se traduce

|- valign="top" style="background:lightgray; "
! <nowiki>[[Página original ]]</nowiki> !! Notas sobre la estructura

|- valign="top"
|
'''<nowiki>== Un título ==</nowiki>'''

Algún texto blah... <br>blah... '''<nowiki>[[#Otro título]]</nowiki>''' <br>... blah

<nowiki>== Otro título ==</nowiki>

Algún otro texto blah... <br>blah... '''<nowiki>[[Otra página]]</nowiki>''' <br>y '''<nowiki>[[Otra página#seccion|seccion]]</nowiki>''' <br>... blah
| <br>
; <tt><nowiki>== Algún Título ==</nowiki></tt> : títulos de sección actúan como anclas, y sus traducciones son sensibles como los vínculos de entrada ''anchor''.
; <tt><nowiki>[[#Otro título]]</nowiki></tt> : vincula secciones en la misma página puede ser simple de mantener como en la misma página (se puede buscar&replazar referencias locales) pero romperá el enlace desde vínculos externos si se cambia.
; <tt><nowiki>[[Otra página]]</nowiki></tt> : El problema más común con los vínculos a otras páginas es saber como ha sido traducido el título de la página...
; <tt><nowiki>[[Otra página#seccion|seccion]]</nowiki></tt> : enlaces a secciones específicas en otras páginas plantean el problema de conocer la traducción tanto del nombre de la página de destino como la traducción del nombre de la sección.
|}
</div>

<div style="font-size:80%; ">
{|
|+ This 'sample' page includes all of the elements that require some level of consideration when translating

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! Notes on the structure

|- valign="top"
|
'''<nowiki>== Some header ==</nowiki>'''

Some text blah... <br>blah... '''<nowiki>[[#Another header]]</nowiki>''' <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... '''<nowiki>[[Another page]]</nowiki>''' <br>and '''<nowiki>[[Another page#section|section]]</nowiki>''' <br>... blah
| <br>
; <tt><nowiki>== Some header ==</nowiki></tt> : section headers act as anchors, and their translation is sensitive as they ''anchor'' incomming links.
; <tt><nowiki>[[#Another header]]</nowiki></tt> : intra-page section linking may be simple to maintain as it's within the same page (you can search&replace local references) but will break external inbound links if changed.
; <tt><nowiki>[[Another page]]</nowiki></tt> : the most common problem with links to other pages is to know how the page title has been translated...
; <tt><nowiki>[[Another page#section|section]]</nowiki></tt> : links to specific sections in other pages pose the conflated problem of knowing ''both'' the target page name '''and''' the section name's translations.
|}
</div>

=== Full finished example ===

<div style="font-size:80%; ">
{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page]]</nowiki> !! <nowiki>[[</nowiki>Original page/lang-[[#lang|xx]]<nowiki>]]</nowiki><span style="font-size:80%"><br>''(translated page name)''</span> !! Translated text deleted...<span style="font-size:80%"><br>''(not really recommended)''</span>

|- valign="top"
|
<nowiki>{{Translations}}</nowiki>

<nowiki>== Some header ==</nowiki>

Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah

<nowiki>== Another header ==</nowiki>

Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
|
<nowiki>{{</nowiki>Translation
| lang = [[#lang|xx]]
| source = [[#source|Original page]]
| version = [[#version|yyyy]]<nowiki>}}</nowiki>
<nowiki>{{</nowiki>TranslationInProgress<nowiki>}}</nowiki>

<nowiki>{{anchor|Some header}}</nowiki>
<nowiki>== Un titular ==</nowiki>

Algo de texto bla... <br>bla... <nowiki>[[#Another header|Otro titular]]</nowiki> <br>... blah
<nowiki>{{ Translated text |</nowiki>
Some text blah... <br>blah... <nowiki>[[#Another header]]</nowiki> <br>... blah
| display = [[#display|block]]<nowiki>}}</nowiki>

<nowiki>{{anchor|Another header}}</nowiki>
<nowiki>== Otro titular ==</nowiki>

Algo más de texto bla... <br>bla... <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]|Otra página<nowiki>]]</nowiki> <br>y <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]#section|sección<nowiki>]]</nowiki> <br>... bla
<nowiki>{{ Translated text |</nowiki>
Some other text blah... <br>blah... <nowiki>[[Another page]]</nowiki> <br>and <nowiki>[[Another page#section|section]]</nowiki> <br>... blah
| display = [[#display|block]]<nowiki>}}</nowiki>
|
<nowiki>{{</nowiki>Translation
| lang = [[#lang|xx]]
| source = [[#source|Original page]]
| version = [[#version|yyyy]]<nowiki>}}</nowiki>

<nowiki>{{anchor|Some header}}</nowiki>
<nowiki>== Un titular ==</nowiki>

Algo de texto bla... <br>bla... <nowiki>[[#Another header|Otro titular]]</nowiki> <br>... blah

<nowiki>{{anchor|Another header}}</nowiki>
<nowiki>== Otro titular ==</nowiki>

Algo más de texto bla... <br>bla... <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]|Otra página<nowiki>]]</nowiki> <br>y <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]#section|sección<nowiki>]]</nowiki> <br>... bla
|}
</div>

Páginas de apoyo

{{ Translated text |
Supporting pages:
| display = none }}

<div style="font-size:80%; ">
{| cellspacing=0

|- valign="top" style="background:lightgray; "
! <nowiki>[[Original page/translations]]</nowiki>

|- valign="top"
|
<nowiki>[[Original page|english]] | [[</nowiki>Original page/lang-[[#lang|xx]]|[[#language name|shortNativeName]]<nowiki>]]</nowiki>
|}

{|

|- valign="top" style="background:lightgray; "
! <nowiki>[[</nowiki>Another page/lang-[[#lang|xx]]<nowiki>]]</nowiki>
! <nowiki>[[Another page]]</nowiki>

|- valign="top"
|
<nowiki>#REDIRECT [[Another page]]</nowiki>
<nowiki>[[Category:Missing translation]]</nowiki>
|
''some untranslated page...''
''maybe the content is mutating rapidly,''
''or is peripheric to the main corpus, etc.''
|}
</div>

{{anchor|Notes}}
== Notas ==

{{anchor|language name}}
; shortNativeName : debe estar en el idioma nativo; <tt>español</tt> en lugar de <tt>spanish</tt>.

{{ Translated text |
; shortNativeName : should be in the native language; <tt>español</tt> instead of <tt>spanish</tt>.
| display = none }}

{{anchor|[[Template:Translation|Translation template]] notes}}
=== [[Template:Translation|Plantilla de traducción]] notas ===

Para la documentación completa, por favor vea [[Template:Translation]].

{{ Translated text |
For the full documentation, please see [[Template:Translation]].
| display = none }}

{{anchor|lang}}
; Lang : Este parámetro identifica el idioma de destino de la traducción. Véase [[WikiTeam/Translation/ISO 639]] para una lista selecta de los códigos que se utilizan en el wiki. (Otra fuente es [http://www.iana.org/assignments/language-subtag-registry codigos IANA's lang]).
: Este sirve a varios propósitos, y se utiliza en varios contextos, aunque debe hacerse de forma homogénea.
: '''En estos momentos estamos utilizando codigos [[WikiTeam/Translation/WikiTeam/Translation/ISO 639-1]] (códigos de dos letras)'''.

{{ Translated text |
; lang : This parameter identifies the target language of the translation. See [[WikiTeam/Translation/ISO 639]] for a select list of codes being used in the wiki. (Another source is [http://www.iana.org/assignments/language-subtag-registry IANA's lang codes]).
: It serves several purposes, and is used in several contexts although it should be done in a homogeneous way.
: '''We are currently using [[WikiTeam/Translation/WikiTeam/Translation/ISO 639-1]] codes (two-letter codes)'''.
| display = none }}

{{anchor|source}}
; source : es el nombre de la página (no el vínculo—en otras palabras, sin lo que está entre corchetes cuadrados).

{{ Translated text |
; source : is the name of the page (not the link—in other words, without the enclosing square brackets).
| display = none }}

{{anchor|version}}


; version : Cada página original tiene un número de versión único. Estos números de versión aparecen en el extremo derecho de la 'barra azul de navegación de lenguaje', y aparecen en la forma: <nowiki>[</nowiki>ID# yyyyy<nowiki>]</nowiki>

{{ Translated text |
; version : Each original page has a unique version number. These version numbers appear on the far right of the 'blue language navigation bar', and appear in the form: <nowiki>[</nowiki>ID# yyyyy<nowiki>]</nowiki>
| display = none }}

Cuando se envia la edición de una página, el número de versión para esa página en particular se incrementa.

{{ Translated text |
: When a page edit is submitted, the version number for that particular page is incremented.
| display = none }}

: Una página traducida por otra parte no tiene un número de versión visible por su propia cuenta. Este debe ser asignado manualmente por el traductor cuando se envie la edición. El número de versión de una página traducida es el mismo que el número de versión de la página original en que se basa.

{{ Translated text |
: A translated page on the other hand does not have a visible version number on its own. It must be manually assigned by the translator when an edit is submitted. The version number of a translated page is the same as the version number of the original page which it is based on.
| display = none }}

: Por ejemplo, si la página original tiene un número de versión ID # 54321, y la traducción se basa en esa versión particular, a la página traducida se da el número de versión ID # 54321.

{{ Translated text |
: For example if the original page has a version number ID<nowiki>#</nowiki> 54321, and the translatation is based on this particular version, the translated page is given the version number ID<nowiki>#</nowiki> 54321.
| display = none }}

: El número de versión de la página traducida se coloca en la parte superior de la página como un parámetro para la función [[Template:Translation|<nowiki>{{</nowiki>Translation<nowiki>}}</nowiki>]]

: <nowiki>{{</nowiki> Translation
:: | lang = de
:: | source = Translating/HowTo
:: | '''version = 54321''' <nowiki>}}</nowiki>

{{ Translated text |

: The version number for the translated page is entered at the top of the page as a parameter for the [[Template:Translation|<nowiki>{{</nowiki>Translation<nowiki>}}</nowiki>]] function.

: <nowiki>{{</nowiki> Translation
:: | lang = de
:: | source = Translating/HowTo
:: | '''version = 54321''' <nowiki>}}</nowiki>
| display = none }}

: Hay un uso que resulta directamente de la anterior asignación manual de un número de versión a la página traducida. Permite al traductor buscar fácilmente que nuevas traducciones se necesitan siguiendo el vínculo de 'cambios', situado al extremo derecha de la 'barra azul de navegación de lenguaje'.

{{ Translated text |
: There is one use which results directly from the above manual assignment of a version number to the translated page. It allows the translator to easily lookup what new translations are needed by following the 'changes' link located to the far right of the 'blue language navigation bar'.
| display = none }}

: Supongamos que el traductor 'A' está haciendo una traducción al español de la página [[Bitfrost]] con la versión número ID # 65535. Según esta guía, el traductor 'A' asigna el número de versión ID # 65535 para la página traducida al español Bitfrost/lang-es. Mientras tanto, el editor 'B' llega y edita la página original [[Bitfrost]] y su número de versión se incrementa al ID # 6553'''6'''. Entonces el Traductor "A" puede ver que nuevas traducciones son necesarias siguiendo el vinculo de 'cambios', situado en la barra azul de navegación. El vínculo de 'cambios' compara las diferencias entre dos versiones de la página original ID # 6553'''5''' y ID # 6553'''6'''. Al observar la salida resultante, el traductor 'A' puede ver fácilmente qué nuevo texto necesita ser traducido.

{{ Translated text |
: Suppose translator 'A' is making a translation of page [[Bitfrost]] with version number ID# 65535 into español. As per this guide, translator 'A' assigns version number ID# 65535 to the Bitfrost/lang-es español translated page. Meanwhile editor 'B' arrives and edits the original [[Bitfrost]] page and its version number is incremented to ID# 6553'''6'''. Translator 'A' then can see what new translations are necessary by following the 'changes' link located on the blue nav bar. The 'changes' link compares the differences of two versions of the original page ID# 6553'''5''' and ID# 6553'''6'''. By observing the resulting output, translator 'A' could easily see what new text needs to be translated.
| display = none }}

{{anchor|[[Template:Translated text|Translated text]] template notes}}
=== [[Template:Translated text|Texto traducido]] notas de la plantilla ===

{{anchor|display}}

; display : se utiliza para mostrar u ocultar texto traducido adjunto.
: Mientras se hace la traducción, resulta útil para comparar el original con la traducción. Cuando haya terminado, se puede reemplazar ''block'' con ''none'' para que el texto original no sea mostrado. A pesar de que agrega un poco de texto y 'ruido' a la fuente de la página traducida, resulta útil cuando se trata de actualizar o sincronizar con cualquier cambio en la página original— después de todo, este ES un wiki y las páginas se supone que mutan!

{{ Translated text |
; display : is used to show or hide the enclosed translated text.
: While doing the translation, it comes in handy for comparing the original with the translation. When finished, you can replace the ''block'' with ''none'' and the source text is not displayed. Although it adds quite a bit of text and 'noise' to the source of the translated page, it comes in handy when trying to update or synchronize it with any changes in the original page—after all, this IS a wiki and pages are supposed to mutate!
| display = none }}

[[Category:WikiTeam/Translation]]
[[Category:HowTo]]

Translation Team/ISO 639

2009-03-08T11:33:54Z

Dfarning-bot: WikiTeam/Translation/ISO 639 moved to Wiki Team/Translation/ISO 639: Robot: Moved page

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
{{stub}}

The subvariant used by OLPC is '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]''' (See [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]).

{| border="1"
|- style="background:lightgray"
! style="background:green" | 639-1 !! 639-2 !! 639-3 !! Language !! !! Native name !! Comments
|-
| style="background:lightgreen" | am || amh || amh || [[Amharic language|Amharic]] || [http://en.wikipedia.org/wiki/Amharic_language W] || {{#language:am}} || [[OLPC Ethiopia|Ethiopia]]
|-
| style="background:lightgreen" | ar || ara || ara + 30 || [[Arabic language|Arabic]] || [http://en.wikipedia.org/wiki/Arabic_language W] || {{#language:ar}} || Standard Arabic is [arb]—[[OLPC Libya|Libya]]
|-
| style="background:lightgreen" | en || eng || eng || [[English language|English]] || [http://en.wikipedia.org/wiki/English_language W] || English || [[OLPC Nigeria|Nigeria]], [[OLPC Rwanda|Rwanda]] & [[OLPC USA|USA]]
|-
| style="background:lightgreen" | af || afr || afr|| [[Afrikaans language|Afrikaans]] || [http://en.wikipedia.org/wiki/Afrikaans_language W] || Afrikaans|| [[OLPC South Africa|South Africa]], [[OLPC Namibia|Namibia]]
|-
| style="background:lightgreen" | es || spa || spa || [[Spanish language|Spanish]] || [http://en.wikipedia.org/wiki/Spanish_language W] || español; castellano || [[OLPC Argentina|Argentina]], [[OLPC Peru|Perú]] & [[OLPC Uruguay|Uruguay]]
|-
| | ''fa'' || ''per/fas'' || prs || [[Dari language|Dari (Persian)]] || [http://en.wikipedia.org/wiki/Dari_%28Persian%29 W] || دری, || Dari only has 639-3 code—[[OLPC Afghanistan|Afghanistan]]
|-
| style="background:lightgreen" | fr || fre/fra || fra || [[French language|French]] || [http://en.wikipedia.org/wiki/French_language W] || français; langue française || [[OLPC Haiti|Haiti]] & [[OLPC Rwanda|Rwanda]]
|-
| style="background:lightgreen" | ha || hau || hau || [[Hausa language|Hausa]] || [http://en.wikipedia.org/wiki/Hausa_language W] || {{#language:ha}} || [[OLPC Nigeria|Nigeria]]
|-
| | ht || hat || hat || [[Haitian Creole language|Haitian Creole]] || [http://en.wikipedia.org/wiki/Haitian_Creole_language W] || {{#language:ht}} || [[OLPC Haiti|Haiti]]
|-
| style="background:lightgreen" | ig || ibo || ibo || [[Igbo language|Igbo]] || [http://en.wikipedia.org/wiki/Igbo_language W] || Igbo || [[OLPC Nigeria|Nigeria]]
|-
| | kh || khm || khm + 1 || [[Khmer language|Khmer]] || [http://en.wikipedia.org/wiki/Khmer_language W] || ភាសាខ្មែរ || [[OLPC Cambodia|Cambodia]]
|-
| | mn || mon || mon+2 || [[Mongolian language|Mongolian]] || [http://en.wikipedia.org/wiki/Mongolian_language W] || {{#language:mn}} || [[OLPC Mongolia|Mongolia]]
|-
| style="background:lightgreen" | ne || nep || nep || [[Nepali language|Nepali]] || [http://en.wikipedia.org/wiki/Nepali_language W] || {{#language:ne}} || [[OLPC Nepal|Nepal]]
|-
| | ps || pus || pus + 3 || [[Pashto language|Pashto]] || [http://en.wikipedia.org/wiki/Pashto_language W] || {{#language:ps}} || [[OLPC Afghanistan|Afghanistan]]
|-
| style="background:lightgreen" | pt || por || por || [[Portuguese language|Portuguese]] || [http://en.wikipedia.org/wiki/Portuguese_language W] || Português || [[OLPC Brazil|Brasil]]
|-
| style="background:lightgreen" | ro || rum/ron || ron || [[Romanian language|Romanian]] || [http://en.wikipedia.org/wiki/Romanian_language W] || română || [[OLPC Romania|Romania]]
|-
| style="background:lightgreen" | ru || rus || rus || [[Russian language|Russian]] || [http://en.wikipedia.org/wiki/Russian_language W] || русский язык || [[OLPC Russia|Russia]]
|-
| style="background:lightgreen" | rw || kin || kin || [[Kinyarwanda language|Kinyarwanda]] || [http://en.wikipedia.org/wiki/Kinyarwanda_language W] || Kinyarwanda || [[OLPC Rwanda|Rwanda]]
|-
| style="background:lightgreen" | th || tha || tha || [[Thai language|Thai]] || [http://en.wikipedia.org/wiki/Thai_language W] || ไทย || [[OLPC Thailand|Thailand]]
|-
| style="background:lightgreen" | ur || urd || urd || [[Urdu language|Urdu]] || [http://en.wikipedia.org/wiki/Urdu W] || {{#language:ur}} || [[OLPC Pakistan|Pakistan]]
|-
| style="background:lightgreen" | yo || yor || yor || [[Yoruba language|Yoruba]] || [http://en.wikipedia.org/wiki/Yoruba_language W] || Yorùbá || [[OLPC Nigeria|Nigeria]]
|- style="background:lightgray"
| colspan=7 style="font-size:80%" | Most relevant [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 codes] for the '''current green countries:'''<br>{{Status green countries}}<br>and other '''[[G1G1]] targets:''' [[OLPC Afghanistan|Afghanistan]], [[OLPC Cambodia|Cambodia]], [[OLPC Haiti|Haiti]], [[OLPC Mongolia|Mongolia]],
|}

== ISO 639 variations ==

[[ISO-639]] is a standard for specifying languages by the use of a code. Several formats exist:
* '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]'''—2002 Codes for the representation of names of languages -- Part 1: Alpha-2 code '''[http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]'''
* [http://en.wikipedia.org/wiki/ISO_639-2 ISO 639-2]—1998 Codes for the representation of names of languages -- Part 2: Alpha-3 code [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes List of ISO 639-2 codes]
* [http://en.wikipedia.org/wiki/ISO_639-3 ISO 639-3]—2007 Codes for the representation of names of languages -- Part 3: Alpha-3 code for comprehensive coverage of languages [http://en.wikipedia.org/wiki/List_of_ISO_639-3_codes List of ISO 639-3 codes]
* [http://en.wikipedia.org/wiki/ISO_639-4 ISO/CD 639-4]—2007? Codes for the representation of names of languages -- Part 4: Implementation guidelines and general principles for language coding
* [http://en.wikipedia.org/wiki/ISO_639-5 ISO/DIS 639-5]—2007? Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups
* ISO/CD 639-6—2007? Codes for the representation of names of languages -- Part 6: Alpha-4 representation for comprehensive coverage of language variation

[[Category:Language support]]
[[Category:Languages (international)]]
[[Category:Localization]]

Translation Team/Wiki Translation

2009-03-08T11:33:44Z

Dfarning-bot: WikiTeam/Translation moved to Wiki Team/Translation: Robot: Moved page