Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
65 lines (43 loc) · 3.62 KB

CONTRIBUTING.md

File metadata and controls

65 lines (43 loc) · 3.62 KB

Contributing to the ISO/IEC 42001 AI Governance Toolkit

Thank you for your interest in improving this toolkit. It is used by GRC teams, AI governance leads, internal auditors, and certification candidates, so accuracy and clarity matter.

Ways to Contribute

Contribution How
Report an issue Open a GitHub Issue with the template, clause reference, and expected vs. actual content
Suggest a new template Open an Issue tagged enhancement with the clause/control it supports
Fix a typo or clarify wording Submit a Pull Request directly
Add a sector example Submit a PR updating the Annex D sector applications file
Add a regulatory mapping Submit a PR under the relevant mapping file

Ground Rules

  1. Every change must cite the ISO/IEC 42001:2023 clause or Annex A control it affects.
    1. Templates must remain vendor-neutral and jurisdiction-neutral unless explicitly scoped.
      1. Do not include any real organisational data, personal data, or client-identifying information in examples.
        1. Language is British English for prose; tables use standard AI governance terminology.

          1. Keep one topic per Pull Request. Large multi-file changes are harder to review.

          3. Pull Request Process

            1. Fork the repository and create a topic branch from main (e.g. feat/annex-c-healthcare).
              1. Make your changes. Keep the existing file structure and numbering.
                1. Update CHANGELOG.md under the ## [Unreleased] section.
                  1. Open a Pull Request describing:
                    • What clause / control the change supports
                      • Why the change is needed
                        • What audit evidence the change helps produce

                          1. A maintainer will review and may request edits.

                          3. Commit Message Convention

                          4. Use short, imperative commit messages. Recommended prefixes:

                            • docs: documentation changes
                              • feat: new template, procedure, or script
                                • fix: correction to existing content

                                  • refactor: structural change without content change

                                    • chore: repo hygiene

                                    • Example: feat(clause7): add competence matrix template

                                    Code of Conduct

                                    All contributors are expected to follow CODE_OF_CONDUCT.md. Be respectful, constructive, and assume good intent.

                                    Licence

                                    By contributing you agree your contributions are licensed under the MIT License that covers the project.