|Open||Keegan||T138339 Create a systematic approach to community engagement for product development teams|
|Resolved||Keegan||T138436 Technical Collaboration Guideline - translations|
T131581 look to me to be a sort of "Translation Hub," where people can go to find resources for translation and things to translate that are not just messages on meta - so documentation on mw.org, system messages on translate wiki, etc.
The "Translations" sections of the TCG is intended to outline how one gets their material translated, and then how to deliver said translated material. Its focus is on communication and delivery.
I have the impression that the root of the problem is that it is unclear what we want to say about translations in the TCG. This is mainly a recommendation for development teams and communities, so the basic recommendations could point to (I'm just writing down ideas that come to mind, this doesn't aim to be a draft of anything):
- Wikimedia is a multilingual and multicultural community. Be ready for this when planning strings for your software, project descriptions, announcements, and requests for feedback.
- Wikimedia has a community of translators willing to help, but their time, energy, and patience is limited.
- Be conscious about new requests for translation. For instance, English-only is fine for regular updates targeting developers.
- Volunteers are moved by their own interest and availability. They don't owe you anything. If you have tight deadlines, it is not their problem. Plan well in advance anything needing translations, involving translators in your plans, and the results will be a lot better.
- Be concise. Shorter texts to the point have higher chances to be translated faster in more languages.
- Think global and standard. Cultural references, slang, word plays... are very difficult to translate and most probably not required.
- Most people in the World and in Wikimedia are not fluent English speakers. Don't forget this when asking for feedback, when reading volunteers' feedback, when discussing with them, and also when thinking about the users who are not participating because of language barriers
- In order to soften these barriers and increase participation of non-English speakers, collaborate with tech ambassadors so they bring those discussions to their communities and/or think of basic translatable surveys with multiple options, not requiring writing text.
In terms of form, we have apparent duplicity of content at
I would add to Quim's list:
- define your context - translate something with technical terms and no definition for them will not be translated
- define a glossary first
- limit the number of updates - have a section with "future changes" (that are sure to be done) written at present tense and move these sections to the appropriate ones will be much better than asking to review translations
There was quite a bit of discussion at https://www.mediawiki.org/wiki/Topic:Te1rmc80rl239set about how to prevent translation overload by writing concisely, keep a rather descriptive style, try to organize information in modules that can be reused... None of that is mentioned in the guideline. Please reconsider.