Local language communities

• Currently, most of P2PU is focused around English courses, interface, community etc
• We have a Spanish interface translation, but not sure if there is still a vibrant community in Spanish
• What kind of tech support do language communities need? Tagging of courses by language? Courses in a given language highlighted when that language is chosen as interface? 
• How could language communities be organized? Would a school metaphore be appropriate? How can we support vibrant long-lasting language communities? 
• Is there room for local (geographically based) P2PU groups? P2PU Norway? What would these do? How would we organize them? 
• Currently, translation into Chinese is underway, and I've been talking to people about creating "P2PU Nordic"

Discussion: Should we put effort into making p2pu available in other languages? 

Action: Look into ubuntu types of translation (using a web interface, not having to extract from GitHub etc - especially important to make it easy to maintain translations, and collaborating on translations) 
Action: Get all the Spanish courses on top when switching to Spanish. Use tags Espanol or add a language label/pulldown menu in course settings. Can also feature English courses below, especially for languages which don't have as many courses.
Action: Move language-selector to top of front page, make people aware that there are other languages available.

What are priorities for translation into a new language: Wikipedia is a long process. Do we want to have: there is a minimum standard before you can get live. 
For example: translate the main interface, a few key pages (how to get involved), and at least one course? Set up a mailing list in that language.

Having a landing page for a language - links to language specific info like contact person, mailing list, ways to get involved? Use Schools framework?

Challenge: Right now P2PU website is spread out quite wide (help.p2pu.org, qa.p2pu.org, p2pu.org, wiki.p2pu.org, blog.p2pu.org, pad.p2pu.org, Big Blue Button etc) - all have different translation systems. Which ones are "core ones" that should be translated, and which ones are less important? 

Website is changing very rapidly, and it is hard for translators to keep up with that, even the Spanish translation is already "behind". 

What content needs to be translated, and what are mechanisms for keeping these up to date? How to get involved, about us, licensing info, course handbook... 

Case study:
Translating P2PU into Dutch.

Problem 1: Language button in bottom right corner

Solutions:
Update translation instructions in GitHub (you can easily begin editing the page while you are logged in, and it will automatically fork and create a pull message). Create a short screencast showing how to do this (Stian).