OpenRailAssociation / OpenRailAssociation/website
Document governance
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 9
- Avg merge
- 22h 39m
- Merged PRs (30d)
- 14
Description
In the spirit of openness we want to document the governance structures of the OpenRail Association publicly. This includes the relevant rules such as the bylaws, charters of working bodies, and internal regulations.
- Overview of governance (https://openrailassociation.org/about/)
- Governance of AISBL (https://github.com/OpenRailAssociation/website/pull/17)
- Bylaws of the association (https://openrailassociation.org/documents/OpenRail-Association-Statutes.pdf)
- Antitrust policy (https://openrailassociation.org/documents/OpenRail-Compliance-and-Antritrust-Policy.pdf)
- List of working bodies (https://openrailassociation.org/about/#structure)
- Charter of the Technical Committee (https://github.com/OpenRailAssociation/technical-committee/blob/main/charter.md)
- Charter of the OpenRail Team
- Scheme for project governance
- Define Open Governance
- Provide templates (https://github.com/OpenRailAssociation/project-template)
- How to find governance docs for each project
It also includes the composition of the relevant groups, such as the board and the working bodies.
- Composition of the board (https://openrailassociation.org/about/#board)
- Composition of the Technical Committee (https://github.com/OpenRailAssociation/technical-committee#members)
- Composition of the OpenRail Team (https://openrailassociation.org/about/#openrail-team)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the website's linked governance pages and the unchecked checklist items: the OpenRail Team charter and project-governance scheme. Review the existing governance and project-template links to determine the expected structure, then update the website with the missing documentation and links so every checklist item is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hugo
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100