Project organisation¶
Xymon is maintained by its contributors. What follows is how rights are held in
the xymon-monitoring organisation on GitHub, and what holding one asks of the
person who holds it. Who holds what is not listed here.
Groups¶
A group grants a right and asks for the work behind it.
| Group | Grants | Expects |
|---|---|---|
| Organisation owner | admin on every repository, the organisation's settings and membership | answering for who holds what, and keeping that list short enough to review |
| maintainers | maintain on xymon, and the only bypass of its ruleset |
reviewing others' changes; bypassing only where CONTRIBUTING.md allows |
| contributors | push on xymon |
opening pull requests and seeing them through review |
Anyone can contribute without belonging to a group: open an issue, or a pull request from a fork — see First contribution.
Being an organisation owner is a role in the organisation, not a team, and it comes with admin on every repository by itself. A member who is not an owner has no access to a repository until a team grants it.
Holding a right¶
- Identified and contactable. Anyone holding a right in the organisation can be tied to a person and reached. A right nobody can ask about cannot be reviewed or revoked in good faith.
- Held for the work. A right that nobody exercises is not harmless: it is a gap someone else fills quietly. Holding a group is a decision, not an accumulation, and groups follow actual involvement as it changes.
- Changed traceably. Rights are granted and removed on the record, so that a change of access is never silent.
Decisions¶
Discussion happens on the mailing list and the other channels listed on Project & community. A decision becomes authoritative when it is recorded on GitHub, in the issue or pull request that took it.