Skip to content

Commit 4c402d0

Browse files
andrewgazelkaandrewgazelka
authored
docs: add governance and code of conduct (#886)
1 parent a4eedad commit 4c402d0

File tree

2 files changed

+150
-0
lines changed

2 files changed

+150
-0
lines changed

‎CODE_OF_CONDUCT.md

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
# Hyperion Code of Conduct
2+
3+
## Our Pledge
4+
5+
We, the Hyperion community, pledge to make participation in our project a harassment-free and productive experience for everyone. We value technical excellence, direct communication, and solution-oriented collaboration while ensuring respect for all community members regardless of age, ethnicity, gender identity and expression, race, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
### Technical Conduct
10+
Examples of behavior that contributes to a productive technical environment:
11+
12+
* Focusing on technical merit rather than who wrote the code
13+
* Providing clear, evidence-based feedback on contributions
14+
* Backing up opinions with benchmarks, code examples, or technical reasoning
15+
* Proposing solutions alongside criticisms
16+
* Being direct and candid in technical discussions while remaining respectful
17+
* Valuing performance, correctness, and maintainability
18+
19+
### Community Conduct
20+
Examples of behavior that contributes to a positive community environment:
21+
22+
* Demonstrating empathy and kindness toward other people
23+
* Being respectful of differing opinions, viewpoints, and experiences
24+
* Giving and gracefully accepting constructive feedback
25+
* Accepting responsibility for mistakes and learning from experience
26+
* Focusing on what's best for the overall community and project
27+
28+
### Unacceptable Behavior
29+
Examples of unacceptable behavior include:
30+
31+
* Personal attacks, public or private harassment
32+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
33+
* Trolling, insulting/derogatory comments, and personal or political attacks
34+
* Publishing others' private information without explicit permission
35+
* Persistent unconstructive criticism that offers no solutions
36+
* Other conduct which could reasonably be considered inappropriate in a professional setting
37+
38+
## Balance of Values
39+
40+
Hyperion values both:
41+
* Candid, direct technical communication that doesn't sugarcoat problems
42+
* A respectful, inclusive environment where everyone can participate
43+
44+
These values can coexist. Direct feedback should focus on the work, not the person. Technical debates are encouraged, but should remain professional and evidence-based.
45+
46+
## Enforcement Responsibilities
47+
48+
Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior. They will take appropriate and fair corrective action in response to any behavior deemed inappropriate, threatening, offensive, or harmful.
49+
50+
## Enforcement Guidelines
51+
52+
### 1. Correction
53+
**Impact**: Use of inappropriate language or behavior deemed unprofessional.
54+
**Response**: A private message explaining the issue and why the behavior was inappropriate. A public apology may be requested.
55+
56+
### 2. Warning
57+
**Impact**: A pattern of inappropriate behavior or a single serious incident.
58+
**Response**: A warning with consequences for continued behavior, potentially including a specified period of no interaction.
59+
60+
### 3. Temporary Ban
61+
**Impact**: Serious or sustained violations of community standards.
62+
**Response**: Temporary ban from community interaction for a specified period.
63+
64+
### 4. Permanent Ban
65+
**Impact**: Pattern of serious violations or harassment.
66+
**Response**: Permanent ban from community participation.
67+
68+
## Reporting and Contact
69+
70+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers at `andrew.gazelka@gmail.com`. All complaints will be reviewed and investigated promptly and fairly.
71+
72+
## Scope
73+
74+
This Code of Conduct applies to all community spaces and when representing the community in public spaces.
75+
76+
## Attribution
77+
78+
This Code of Conduct combines elements from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, with project-specific standards focused on technical excellence and productive collaboration.

‎GOVERNANCE.md

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
# Hyperion Governance
2+
3+
This document outlines the simple governance structure for Hyperion, a high-performance Minecraft game engine.
4+
5+
## Project Roles
6+
7+
### 1. Project Lead
8+
- Project founder (@andrewgazelka) and other designated leads
9+
- Has final authority on project direction
10+
- Controls access to critical resources (repositories, hosting, domains)
11+
- Resolves disputes when consensus cannot be reached
12+
13+
### 2. Core Contributors
14+
- Demonstrated consistent high-quality contributions
15+
- Push access to all repositories
16+
- Can approve significant changes
17+
- Help shape project direction
18+
19+
### 3. Contributors
20+
- Anyone who has contributed to the project
21+
- No special permissions, but acknowledged for their work
22+
- May be nominated for Core Contributor status
23+
24+
## Decision Making
25+
26+
### Code Changes
27+
- Minor changes (bug fixes, small improvements) need one Core Contributor approval
28+
- Major changes (API, architecture) need discussion and two Core approvals
29+
- Core Contributors can merge their own minor changes for areas they maintain
30+
- Always prioritize performance, scalability, and stability
31+
32+
### Project Direction
33+
- Major decisions are discussed openly in GitHub issues or Discord
34+
- Core Contributors aim for consensus on important matters
35+
- If consensus cannot be reached, Project Lead makes the final decision
36+
- Technical merit and alignment with project goals are primary criteria
37+
38+
## Becoming a Core Contributor
39+
40+
1. Make consistent contributions to the project
41+
2. Get nominated by an existing Core Contributor
42+
3. A plurality of Core Contributors votes to approve (must all be @'d in Discord and have four days to respond)
43+
44+
## Code Review
45+
46+
We value quick iteration while maintaining technical excellence:
47+
48+
- Focus reviews on correctness, performance, and maintainability
49+
- Include performance benchmarks for changes to critical paths
50+
- Ensure adequate test coverage for new features
51+
- Use GitHub Pull Requests for all changes
52+
- Prefer small, focused changes over large changes
53+
- Document design decisions that affect scalability
54+
55+
## Communication
56+
57+
- GitHub Issues: Technical discussions and bug reports
58+
- Discord: Community support and development coordination
59+
- Technical discussions should be direct and solution-oriented
60+
- Focus on the work, not the person
61+
62+
## Conflict Resolution
63+
64+
1. Technical disagreements should first be discussed on relevant issues/PRs
65+
2. If unresolved, Core Contributors discuss and seek consensus
66+
3. Project Lead makes final decision when consensus cannot be reached
67+
68+
## Moderation
69+
70+
- Follow the Hyperion Code of Conduct
71+
- Violations can be reported to project leads via Discord DM or email
72+
- Project Lead will review reports and determine appropriate action

0 commit comments

Comments
 (0)