Our coding guidelines are currently hidden deep in th wiki.. to encourage more reference to them, we could publish them more openly as their own mini-site linked directly from the website.. more akin to our manual and API docs sites.
Just an idea: we could move them inside the git repository. That would bring them closer to where they are needed, they can be published using a link to git.koha-community.org, and changes can be proposed using the current patch workflow.
Why don't we put this in the website somewhere?
(In reply to Julian Maurice from comment #1) > Just an idea: we could move them inside the git repository. That would bring > them closer to where they are needed, they can be published using a link to > git.koha-community.org, and changes can be proposed using the current patch > workflow. I was just thinking how a lot of projects have a CONTRIBUTING.md file for this in their git repos. https://github.com/github/docs/blob/main/CONTRIBUTING.md https://github.com/rails/rails/blob/main/CONTRIBUTING.md https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors