Translation Team

2010-02-25T17:44:51Z

Micky1: /* Subpages */

<noinclude>{{GoogleTrans-en}}
{{TeamHeader|Translation Team}}</noinclude>{{TOCright}}

==Mission==
{{:Translation Team/Mission}}

== Welcome to the Translation Team ==

Welcome to the Sugar Labs Translation, Localization and Internationalization Team.

The goal of the Sugar Labs translation team is to make Sugar available in as many languages as possible at the highest quality.

We work on a number of translation related projects
* Localizing the Sugar Learning Platform
* Localizing Sugar Activities
* Translating the Sugar Documentation
* Translating the Sugar Labs wiki. See [[Translation Team/Wiki Translation]].
* Other translation and localization needs of Sugar Labs

== General information ==

The sugar Learning platform and Sugar Activities are localized at http://translate.sugarlabs.org/ . Please see http://translate.sugarlabs.org/doc/en/index.html for for information specific to our pootle server and our localization work flow. For a quick primer, http://people.sugarlabs.org/sayamindu/pootleforxo2_5.pdf is highly recommended.

The Sugar Documentation is written in partnership with FLOSS Manual at http://en.flossmanuals.net/ . Translation of that documentation uses FLOSS Manual tools.

=== Language Teams ===

While Sugar translations are open to everyone to contribute, Sugar Language teams act as quality assurance team. There is one language team appointed to each language. Language teams often work closely with Sugar Local Labs.

Below is a list of activities associated with localization teams:

* Check and review the work of translators
* Help new translators with feedback and guidance
* Check the translation inclusion into pootle and report problems developers.
* Keep in touch with people from other translation projects (upstream project) and synchronize the translation work, assure same translations do not need to be made twice
* Keep in touch with other Sugar Language teams and help establish new Sugar Language teams, exchange best practices with other teams

=== Resources for Translators ===
* [[Template:GoogleTrans-en]] can be used to connect a page to Google's machine translation service. Translators can help improve that service by going to a Google translated page and hovering over a sentence. A option to contribute a better translation is provided in the popup widget.

=== Package Maintainers ===

All UI translations for sugar packages are to be made available for translations using pootle.

Please tag related bug using "i18n" or "l10n".

== Resources for maintainers ==

== Subpages ==
{{Special:PrefixIndex/Translation_Team/}}
[http://www.bestessays.com term papers]

[[Category:Team]]

Marketing Team

2010-02-25T17:40:08Z

Micky1: /* Subpages */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}

== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar Stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==
[http://www.bestessays.com paper writing services]
{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Sugar Labs - User contributions [en]

Translation Team

Marketing Team