search

inclusivenaming / org

Pre-release organization info, meeting notes, collaboration, etc.
43 stars 9 forks source link

Document your org’s Use cases for INI terms and tools recommendations #71

Open ddavisjones opened 3 years ago

ddavisjones commented 3 years ago

Defining how our organizations plan to utilize the content produced by INI will help us prioritize workstream activities and produce outcomes that are most meaningful to INI participants.

jasonbrooks commented 3 years ago

see https://github.com/inclusivenaming/org/issues/62#issuecomment-856145800

petermetz commented 3 years ago

Tool (DCI lint) author here: My use case for a machine readable spec file is to sperate the technological concerns from the governance ones, e.g. as a tool author I can fix bugs/add features to the software that does linting, but for the questions/concerns/recommendations regarding the word list people would come to the INI. Having this sort of separation of concerns would save a lot of duplicated effort in the different tools if they all maintained their own machine readable spec files, managed the pull requests to those, etc.

celestehorgan commented 3 years ago

Use case:

I am an open source organization that is looking to remove harmful language from my project to be more inclusive of all my contributors. However, I am not a language expert nor do I have the time to do the research.

As an open source organization leader, I want an external list of terminology I can reference and implement in my projects.