Document how to contribute to various parts of the game
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
There should be documentation for how anyone can contribute to the OpenRCT2 project. The documentation should cover:
- Coding
- Graphics
- Translation
- Reporting Bugs
- Suggesting Features
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points; start by inspecting the docs repository structure and any existing contribution guidance. Done means contributor-facing documentation covers coding, graphics, translation, bug reports, and feature suggestions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100