Translation-Community Manager - Revision history

Davelab6: Tighening up copy, mark for graduation

2016-06-07T05:45:33Z

Tighening up copy, mark for graduation

Davelab6: Fix typos, link all URLs

2016-04-06T22:17:54Z

Fix typos, link all URLs

← Older revision		Revision as of 18:17, 6 April 2016
Line 19:		Line 19:

	* Sugar Activities		* Sugar Activities
	:: Sugar provides a library, ASLO (activities.sugarlabs.org), of several hundred individual activities that a user can install and run. (Note that many Sugar activities can run independently from the Sugar Desktop, e.g., the GNOME Desktop, the Sugarizer environment, or in a web browser.)		:: Sugar provides a library, ASLO (https://activities.sugarlabs.org), of several hundred individual activities that a user can install and run. (Note that many Sugar activities can run independently from the Sugar Desktop, e.g., the GNOME Desktop, the Sugarizer environment, or in a web browser.)

	Internationalization (I10n) prepares the Sugar Desktop and Sugar Activities for localization (L10n).		Internationalization (I10n) prepares the Sugar Desktop and Sugar Activities for localization (L10n).
Line 28:		Line 28:

	* L10n		* L10n
	::~~Sugarlabs~~ provides a service hosted at http://translate.sugarlabs.org that supports localization of Sugar. It is based on Pootle, a process and software to facilitate localization. In particular, it stores files with the original text for Sugar and its activities and files with the strings for local language		::Sugar Labs provides a service hosted at http://translate.sugarlabs.org that supports localization of Sugar. It is based on Pootle, a process and software to facilitate localization. In particular, it stores files with the original text for Sugar and its activities and files with the strings for local language

	:The overall process is fail-safe in the sense that if an alternate language is selected but there is no string available in that language, Sugar displays the original string found in the code (most often English). http://translate.sugarlabs.org saves translated strings that are immediately available for use in subsequent releases, leaving localizers to provide strings for new text in the release. If that text is not provided, the original text is displayed.		:The overall process is fail-safe in the sense that if an alternate language is selected but there is no string available in that language, Sugar displays the original string found in the code (most often English). http://translate.sugarlabs.org saves translated strings that are immediately available for use in subsequent releases, leaving localizers to provide strings for new text in the release. If that text is not provided, the original text is displayed.
Line 38:		Line 38:
	In most cases localization is done by language specialists under the umbrella of Pootle (http://pootle.translatehouse.org/). This process requires technical skills and effective access to the internet.		In most cases localization is done by language specialists under the umbrella of Pootle (http://pootle.translatehouse.org/). This process requires technical skills and effective access to the internet.

	Translation requires language skills in the target language and the source language (e.g. English, Spanish, French). If possible, I18n and specific language help arranged by the Translation-Community Manager should enable Sugar users to perform this localization on their own laptops. The installation or updating of the localization on translate.sugarlabs.org should be arranged by the Translation-Community Manager. (Also, providing a common intermediary language, such as Spanish, when translating to an indigenous language, such as Aymara, falls under the responsibility of the Translation-Community Manager: there are many more Aymara speakers who know Spanish than English.)		Translation requires language skills in the target language and the source language (e.g. English, Spanish, French). If possible, I18n and specific language help arranged by the Translation-Community Manager should enable Sugar users to perform this localization on their own laptops. The installation or updating of the localization on https://translate.sugarlabs.org should be arranged by the Translation-Community Manager. (Also, providing a common intermediary language, such as Spanish, when translating to an indigenous language, such as Aymara, falls under the responsibility of the Translation-Community Manager: there are many more Aymara speakers who know Spanish than English.)

	==Software Environment==		==Software Environment==
Line 45:		Line 45:

	* Touch screen replacing trackpad and mouse keys, and, often, the keyboard;		* Touch screen replacing trackpad and mouse keys, and, often, the keyboard;
	* Move to Android and Web ~~sevrices~~, which do not directly support Python;		* Move to Android and Web services, which do not directly support Python;
	* Developer focus on HTML5, CSS3, and JavaScript as an implementation environment for activities (and the Sugar experience itself).		* Developer focus on HTML5, CSS3, and JavaScript as an implementation environment for activities (and the Sugar experience itself).

Line 55:		Line 55:
	* Advise the Sugar Labs Oversight Board of supporting projects that need funding and to manage these projects, if approved;		* Advise the Sugar Labs Oversight Board of supporting projects that need funding and to manage these projects, if approved;
	* Develop and maintain the I18n capabilities of Sugar and its activities;		* Develop and maintain the I18n capabilities of Sugar and its activities;
	*# Arrange for development and maintenance of the I18n infrastructure such as translate.sugarlabs.org;		*# Arrange for development and maintenance of the I18n infrastructure such as https://translate.sugarlabs.org;
	*# Arrange for an inventory of Sugar activities in ASLO (activities.sugarlabs.org) showing the current I18n and L10n status of each;		*# Arrange for an inventory of Sugar activities in ASLO (https://activities.sugarlabs.org) showing the current I18n and L10n status of each;
	*# Arrange for development and maintenance of I18n infrastructure to support new and emerging platforms and software environments for Sugar;		*# Arrange for development and maintenance of I18n infrastructure to support new and emerging platforms and software environments for Sugar;
	* Work with the community to identify schools and institutions that have deployed Sugar and to arrange for members of the community to reach out to these deployments to offer help with localization or other needs;		* Work with the community to identify schools and institutions that have deployed Sugar and to arrange for members of the community to reach out to these deployments to offer help with localization or other needs;

Sebastian: Defined as paid delegation. Added language about prior teams.

2016-04-06T04:43:11Z

Defined as paid delegation. Added language about prior teams.

← Older revision		Revision as of 00:43, 6 April 2016
Line 1:		Line 1:
	The Translation-Community Manager leads and co-ordinates the efforts of the Sugar community to		The Translation-Community Manager leads and co-ordinates the efforts of the Sugar community to enable users to experience Sugar in their own language. This is a paid delegation currently being debated by SLOBs.
	enable users to experience Sugar in their own language.
			This delegation is not meant to eclipse [[Translation Team]], its [[Translation_Team/Coordinator\|coordinators]], or any other party interested in helping out with localization.

	== Background ==		== Background ==

Walter: /* Duties */ edits for readability

2016-04-04T17:58:40Z

Duties: edits for readability

← Older revision		Revision as of 13:58, 4 April 2016
Line 66:		Line 66:
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.

	The Sugar Labs ~~Oversight Board~~ must affirm continuation or renewal of the contract before the end of each 4-month cycle. ~~This last part~~ is largely a rubber-~~stamp, as~~ the expectation is that the contract ~~should~~ renew, insofar as funds allow while the translation community strengthens ~~-- but at the same time it~~ is ~~an absolutely~~ critical check ~~and balance (Dead Man's Switch)~~ to keep us each & ~~all~~ conscientiously engaged, accountable, and involved!		The Sugar Labs Oversight Board must affirm continuation (or renewal) of the contract before the end of each 4-month cycle. (It is anticipated that this will largely be a "rubber-stamping" procedure; the expectation is that the contract will renew—insofar as funds allow—while the translation community strengthens. But this "dead man's switch" is a critical check to keep us—each and all—conscientiously engaged, accountable, and involved.)

Davelab6: s/Board/Sugar Labs Oversight Board/ :)

2016-04-04T17:57:36Z

s/Board/Sugar Labs Oversight Board/ :)

← Older revision		Revision as of 13:57, 4 April 2016
Line 66:		Line 66:
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.

	The ~~Board~~ must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!		The Sugar Labs Oversight Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

Holt: /* Duties */

2016-04-04T17:53:42Z

Duties

← Older revision		Revision as of 13:53, 4 April 2016
Line 65:		Line 65:
	*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?		*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.
	* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!
			The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

Holt: /* Duties */

2016-04-04T17:43:20Z

Duties

← Older revision		Revision as of 13:43, 4 April 2016
Line 61:		Line 61:
	*# Arrange for a simple and well-documented procedure for these deployments to provide their own translation and to share the results with the community;		*# Arrange for a simple and well-documented procedure for these deployments to provide their own translation and to share the results with the community;
	* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.		* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.
	* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:		* Report every 4 months on tactical/strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:
	*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)		*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)
	*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?		*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.
	* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!		* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

Holt: /* Duties */

2016-04-04T17:42:52Z

Duties

← Older revision		Revision as of 13:42, 4 April 2016
Line 63:		Line 63:
	* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:		* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:
	*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)		*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)
	*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we nurture continuous improvement?		*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we tactically nurture continuous improvement?
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.
	* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!		* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

Holt: /* Duties */

2016-04-04T17:41:58Z

Duties

← Older revision		Revision as of 13:41, 4 April 2016
Line 62:		Line 62:
	* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.		* Report monthly to the Sugar Labs Oversight Board and to the community and to the public on the status of the translations program, preferably by blogging informally (blog posts can be any length) to http://planet.sugarlabs.org using plain language that is understandable to almost all.
	* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:		* Report every 4 months on strategic/financial choices; reports can be of any length and should be posted/archived together to a unique URL (linked from http://wiki.sugarlabs.org/go/Translation-Community_Manager) one month prior to the completion of each 4-month cycle, mentioning:
	*# What actually happened 4-month ~~over the current~~ cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)		*# What actually happened over current 4-month cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)
	*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we nurture continuous improvement?		*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we nurture continuous improvement?
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.
	* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!		* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!

Holt: /* Duties */

2016-04-04T17:41:22Z

Duties

← Older revision		Revision as of 13:41, 4 April 2016
Line 64:		Line 64:
	*# What actually happened 4-month over the current cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)		*# What actually happened 4-month over the current cycle and/or since the last report, including community/financial summaries (absolutely fine and no shame at all if actions were different from prior cycle's projections: we learn by doing or we don't learn at all!)
	*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we nurture continuous improvement?		*# What can and should happen over the coming 4-month cycle? Community workflows are never 100% rational: how do we nurture continuous improvement?
	*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is ~~hopefully~~ so inclined.		*# Long-term strategic/impact recommendations on an annual basis. Or optionally more often, if he/she is so inclined.
	* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!		* The Board must affirm continuation or renewal of the contract before the end of each 4-month cycle. This last part is largely a rubber-stamp, as the expectation is that the contract should renew, insofar as funds allow while the translation community strengthens -- but at the same time it is an absolutely critical check and balance (Dead Man's Switch) to keep us each & all conscientiously engaged, accountable, and involved!