[Bug 31650] New: We should publish our coding guidelines more openly
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31650 Bug ID: 31650 Summary: We should publish our coding guidelines more openly Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea@gmail.com Reporter: martin.renvoize@ptfs-europe.com 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. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31650 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julian.maurice@biblibre.com --- Comment #1 from Julian Maurice <julian.maurice@biblibre.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31650 Liz Rea <wizzyrea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wizzyrea@gmail.com --- Comment #2 from Liz Rea <wizzyrea@gmail.com> --- Why don't we put this in the website somewhere? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31650 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #3 from David Cook <dcook@prosentient.com.au> --- (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-c... -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org