Configure org level topic standards #3
Description
It is currently difficult for the public and OpenMined community members to explore and discover the 50+ repositories that this organisation houses. This issues proposes to apply a standard to applying topics for OpenMined repos.
The benefits are:
- Applying standardized topics to each repo will enable simple navigation from the topics panel on www.github.com/OpenMined.
- Allows creating topic based views for dashboards related to overall organisation contributions
- Provides a simpler engagement channel for community members looking for something to work on
Terminology
Topic - A tag applied at the repository level that provides a brief description of a related subject
Repository name (also "repo name") - This is the literal name of the GitHub repository
The Convention
Each repository will have the following topics applied:
- Capability (or capabilities) - Minimum of one core OpenMined capability. Some repos will apply to more than one capability
- Languages / Frameworks - Versioning should not included. This should generally only include one or two (e.g. Python and TensorFlow is fine, no need to include Numpy, Pandas etc...). The non-technical repos should include descriptive terms like "templates", "graphics" etc...
- Related Products - Once OpenMined's updated Product Roadmap is published, any related products need to be included as topics
- Repo owners discretion - The repo owner may add additional topics that apply to the repos.
Capabilities
- cryptography
- design
- differential-privacy
- federated-learning
- identity
- mobile
- natural-language-processing
- private-set-intersection
- pygrid
- secure-multiparty-compute
- security
- syft
- web
- writing
Languages / Tools / Frameworks
- C++, Clojure, Java, JavaScript, TypeScript, Python,Rust etc..
Products
To be completed once road map is released