Skip to content

Commit b9e56e4

Browse files
mcj-coderclaude
mcj-coder
and
claude
authored
docs: add CODE_OF_CONDUCT.md and GOVERNANCE.md (#367)
* docs: add CODE_OF_CONDUCT.md and GOVERNANCE.md Add missing governance files per innersource-governance-bootstrap skill: - CODE_OF_CONDUCT.md with Contributor Covenant v2.1 - GOVERNANCE.md with decision-making process and maintainer responsibilities - README.md updated to link both files Refs: #294 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: correct ADR link in GOVERNANCE.md Fix broken link to ADR-0000 (was incorrectly referencing ADR-0001). Refs: #294 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
1 parent f0f91b9 commit b9e56e4

File tree

3 files changed

+229
-0
lines changed

3 files changed

+229
-0
lines changed

‎CODE_OF_CONDUCT.md‎

Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual
10+
identity and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
- Demonstrating empathy and kindness toward other people
21+
- Being respectful of differing opinions, viewpoints, and experiences
22+
- Giving and gracefully accepting constructive feedback
23+
- Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
- Focusing on what is best not just for us as individuals, but for the overall
26+
community
27+
28+
Examples of unacceptable behavior include:
29+
30+
- The use of sexualized language or imagery, and sexual attention or advances of
31+
any kind
32+
- Trolling, insulting or derogatory comments, and personal or political attacks
33+
- Public or private harassment
34+
- Publishing others' private information, such as a physical or email address,
35+
without their explicit permission
36+
- Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement by opening a
63+
[confidential issue](https://github.com/mcj-coder/development-skills/issues/new?labels=conduct&title=Code+of+Conduct+Report)
64+
or by contacting the repository owner [@mcj-coder](https://github.com/mcj-coder)
65+
directly. All complaints will be reviewed and investigated promptly and fairly.
66+
67+
All community leaders are obligated to respect the privacy and security of the
68+
reporter of any incident.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series of
87+
actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or permanent
94+
ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within the
114+
community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119+
version 2.1, available at
120+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121+
122+
Community Impact Guidelines were inspired by
123+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124+
125+
For answers to common questions about this code of conduct, see the FAQ at
126+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127+
[https://www.contributor-covenant.org/translations][translations].
128+
129+
[homepage]: https://www.contributor-covenant.org
130+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131+
[Mozilla CoC]: https://github.com/mozilla/diversity
132+
[FAQ]: https://www.contributor-covenant.org/faq
133+
[translations]: https://www.contributor-covenant.org/translations

‎GOVERNANCE.md‎

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
# Governance
2+
3+
This document describes the governance model for the development-skills
4+
repository, including decision-making processes, maintainer responsibilities,
5+
and contribution acceptance criteria.
6+
7+
## Maintainers
8+
9+
The current maintainers of this repository are defined in
10+
[.github/CODEOWNERS](.github/CODEOWNERS).
11+
12+
| Role | GitHub Handle | Responsibilities |
13+
| --------------- | ------------------------------------------ | ------------------------- |
14+
| Lead Maintainer | [@mcj-coder](https://github.com/mcj-coder) | All repository governance |
15+
16+
## Maintainer Responsibilities
17+
18+
Maintainers are responsible for:
19+
20+
- Responding to issues and pull requests within documented SLA
21+
- Ensuring CI/CD pipeline remains healthy
22+
- Reviewing and merging contributions meeting quality bar
23+
- Maintaining documentation accuracy
24+
- Managing releases and versioning
25+
- Communicating breaking changes and deprecations
26+
- Enforcing the [Code of Conduct](CODE_OF_CONDUCT.md)
27+
28+
### Review Turnaround Expectations
29+
30+
| Activity | Target |
31+
| --------------- | ---------------------------------------------- |
32+
| Acknowledgement | Within 2 business days |
33+
| Initial review | Within 5 business days |
34+
| Merge decision | Within 10 business days of addressing feedback |
35+
36+
## Contribution Acceptance Criteria
37+
38+
Before a contribution can be accepted:
39+
40+
1. **Issue first** - All non-trivial changes require a linked GitHub issue
41+
2. **Branch naming** - Follow repository conventions (`feat/`, `fix/`, `docs/`)
42+
3. **PR template** - Use provided template with required sections filled
43+
4. **Code review** - Minimum one approval from CODEOWNERS
44+
5. **CI passing** - All automated checks must pass (linting, tests)
45+
6. **Documentation** - User-facing changes require docs updates
46+
7. **TDD compliance** - All changes require failing test/checklist first
47+
48+
See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed contribution guidelines.
49+
50+
## Decision-Making Process
51+
52+
All significant decisions follow a transparent process:
53+
54+
1. **Proposed** - Create an issue or ADR with context and options
55+
2. **Discussed** - Allow comment period (varies by category)
56+
3. **Decided** - Document rationale and decision maker
57+
4. **Communicated** - Announce in appropriate channels
58+
59+
### Decision Categories
60+
61+
| Category | Decision Maker | Comment Period |
62+
| -------------------- | -------------------- | ---------------- |
63+
| Bug fixes | Any maintainer | None required |
64+
| Minor features | Component owner | 2 business days |
65+
| Major features | Lead maintainer | 5 business days |
66+
| Architecture changes | Maintainer consensus | 10 business days |
67+
| Governance changes | All maintainers | 10 business days |
68+
69+
### Architecture Decision Records (ADRs)
70+
71+
Major architectural decisions are documented in [docs/adr/](docs/adr/). ADRs
72+
follow the format defined in [ADR-0000](docs/adr/0000-use-adrs.md).
73+
74+
## Conflict Resolution
75+
76+
1. **Discussion** - Attempt resolution through discussion on the issue/PR
77+
2. **Mediation** - Escalate to lead maintainer for mediation
78+
3. **Escalation** - If unresolved, escalate to organisation's technical
79+
leadership
80+
81+
## Changes to Governance
82+
83+
Changes to this governance document require:
84+
85+
- A GitHub issue describing the proposed change
86+
- 10 business days comment period
87+
- Approval from all active maintainers
88+
- PR with the change referencing the issue
89+
90+
## References
91+
92+
- [Code of Conduct](CODE_OF_CONDUCT.md)
93+
- [Contributing Guide](CONTRIBUTING.md)
94+
- [Architecture Decision Records](docs/adr/)

‎README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -300,6 +300,8 @@ Requirements for all skills:
300300
This repository follows standard InnerSource/OpenSource documentation practices:
301301

302302
- **[CONTRIBUTING.md](CONTRIBUTING.md)** - How to contribute and create skills
303+
- **[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)** - Community standards and enforcement
304+
- **[GOVERNANCE.md](GOVERNANCE.md)** - Decision-making process and maintainer responsibilities
303305
- **[docs/getting-started.md](docs/getting-started.md)** - Developer onboarding and project setup
304306
- **[docs/architecture-overview.md](docs/architecture-overview.md)** - Architectural patterns, boundaries, and structure
305307
- **[docs/coding-standards.md](docs/coding-standards.md)** - Code style, naming conventions, and patterns

0 commit comments

Comments
 (0)