We should have a list of words with their definitions that we commonly use when talking about InnerSource. This glossary should come with translations to languages that we would like to translate to (read: where we have volunteers to do the translation)

1. User story: summary of expected behavior

⌦ Describe what you want to accomplish, in what role/capacity,
⌦ and why it's important to you.

As a potential contributor,
I want source code development guidelines
In order to increase the likelihood of contributing changes.

2. Acceptance criteria

We'll be done when:

• 1. A succinct README provides:
• 1.1. Recomme

Can we consider adding CHANGELOG to the standards, as per https://keepachangelog.com/en/1.0.0/?

I think it's really useful for consumed libraries, certainly, and helps enforce semver. The git commit histories are woefully bad at providing a concise / consistent view of additions/changes.

1. User story summary

As a consultant helping researchers publish their codes,
I want to find this repo under a topic that similar projects also use
In order to point people to the topic page rather than to a list of individual repos.

2. Acceptance criteria

• 1. this repo shows up on [GitHub.com/topics/documentation-quality](ht