Skip to content

Commit 90bc4df

Browse files
authored
chore: add governance doc (#28)
1 parent 05bb18b commit 90bc4df

3 files changed

Lines changed: 40 additions & 1 deletion

File tree

AUTHORS.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Authors
2+
3+
This project was built during a hackathon by:
4+
5+
- **Javier Manotas Ruiz** ([@javimanotas](https://github.com/javimanotas))
6+
- **Javi Nogueira Vera** ([@vicho1822](https://github.com/vicho1822))
7+
- **Daniel Queijo Seoane** ([@daniqss](https://github.com/daniqss))
8+
9+
We are a group of developers who decided to make a tool to make beginner programmers lifes easier.

CONTRIBUTING.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ Please make sure to:
1111

1212
- Read the README carefully
1313
- Check existing issues to avoid duplicates
14-
- Follow the Code of Conduct
14+
- Follow the [Code of Conduct](./CODE_OF_CONDUCT.md)
15+
- Review our [Governance model](./GOVERNANCE.md)
1516

1617
## Reporting Bugs
1718

GOVERNANCE.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Governance
2+
3+
This project was born during a hackathon and follows a simple, collective governance model to ensure fast iteration and shared ownership.
4+
5+
## Roles
6+
7+
### Core Maintainers
8+
The project is currently maintained by its three original authors:
9+
- **Javier Manotas Ruiz**
10+
- **Javier Nogueira Vera**
11+
- **Daniel Queijo Seoane**
12+
13+
All core maintainers have equal rights to the codebase, including merging pull requests and managing project configuration.
14+
15+
## Decision Making
16+
17+
Given our small team and the fast-paced nature of a hackathon:
18+
19+
1. **Consensus-First**: We aim for consensus on all major architectural and feature decisions.
20+
2. **Agile Execution**: For minor bug fixes, documentation, or non-breaking changes, any maintainer can merge after a quick peer review or if they are confident in the change.
21+
3. **Conflict Resolution**: In the rare case of a deadlock, a majority vote (2 out of 3) will be used to move forward.
22+
23+
## Contributions
24+
25+
We welcome contributions from the community! All external contributions must be reviewed and approved by at least one core maintainer before being merged.
26+
27+
## Longevity
28+
29+
As the project evolves beyond the hackathon, we may transition to a more formal governance model (e.g., Benevolent Dictator for Life or a formal Steering Committee) if the scope and community grow significantly.

0 commit comments

Comments
 (0)