search

rubyberlin / code-of-conduct

http://rubyberlin.github.io/code-of-conduct/
81 stars 181 forks source link

Introduce versioning for the document #189

Open bruno-gelb opened 5 years ago

bruno-gelb commented 5 years ago

The issue

There are many translations of the CoC (I'm not even talking cached versions, etc.), and sometimes translations are not quite up-to-date with the original.

How can we confidently enforce some rule on the level of 300-ppl European conference..

..while such rule itself highly depends on the language button you've clicked on?

The suggested solution

Let's introduce some sort of semantic versioning to the document. Let's say English (original) version would become 1.1, that means Russian version 1.0 should be updated soon. This is an explicit and transparent way of handling things.

hagenburger commented 5 years ago

We already got an issue for versioning (#7).

@1000miles @yuiofthesun @skade: Did you get the chance to work on this? I’ve seen the tags in the repository but not on the website. The case of different versions for different languages is very valid from my perspective.