Skip to content

Introduce versioning for the document #189

@bruno-gelb

Description

@bruno-gelb

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions