Guidance for content translations

[csarven]

Action of https://github.com/solid/team/blob/main/meetings/2022-04-13.md#community-contributions-to-translate-content

People in the Solid community would like to make content translations. We should provide a guide on how they can contribute.

While content translations is useful across the project, it is particularly welcomed for Solid specifications ( see https://github.com/solid/specification/blob/main/CONTRIBUTING.md#translations ). We can call for contributions elsewhere.

• What can/should be translated?
• How can people find out what's called for?
• ...

[VirginiaBalseiro]

The Code of Conduct can be translated and it would be very helpful. Since it is based off the Contributor Covenant, a big portion of the text can be copied from here: https://www.contributor-covenant.org/translations/

[jeff-zucker]

When we have a reviewed copy of the glossary, it will make a good choice for translation - unlikely to change often, a key onboarding tool. I should have the glossary ready for review soonish.

[VirginiaBalseiro]

What can/should be translated?
How can people find out what's called for?

I think we need to set up a translation project and plan it out (as in languages, items, who will review/how we will do quality checks). I volunteer to carry this out, as I have previous experience (both as a translator in publishing and in open source software projects).