OpenTTD-patches/CONTRIBUTING.md

Contributing to OpenTTD

Looking to contribute something to OpenTTD? Here's how you can help.

Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.

Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.

Using the issue tracker

The issue tracker is the preferred channel for bug reports, but please respect the following restrictions:

• Please do not use the issue tracker for help playing or using OpenTTD. Please try irc, or the forums

• Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.

• Please do not post comments consisting solely of "+1" or "👍". Use GitHub's "reactions" feature instead. We reserve the right to delete comments which violate this rule.

• Please do not open issues or pull requests regarding add-on content in NewGRF, GameScripts, AIs, etc. These are created by third-parties. Please try irc or the forums to discuss these.

Bug reports

A bug is a demonstrable problem that is caused by the code in the repository. Good bug reports are extremely helpful, so thanks!

Guidelines for bug reports:

0. Please don't report issues with games where you changed NewGRFs.

1. Please don't report issues with modified versions of OpenTTD (patchpacks and similar).

2. Use the GitHub issue search --- check if the issue has already been reported.

3. Check if the issue has been fixed --- try to reproduce it using the latest nightly build of OpenTTD, available from https://www.openttd.org

4. Isolate the problem --- ideally create reproduceable steps with an attached savegame and screenshots. Try to use few or no NewGRFs, AIs etc if possible.

A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report.

• What is your environment?
• What steps will reproduce the issue?
• Which operating system(s) experience the problem?
• What would you expect to be the outcome?

All these details will help people to fix any potential bugs.

Example:

Short and descriptive example bug report title

A summary of the issue and the OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.

1. This is the first step
2. This is the second step
3. Further steps, etc.

Attached savegame Attached screenshots showing the issue Crashlogs if the bug causes a crash

Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).

Feature requests

Before opening a feature request, please take a moment to find out whether your idea fits with the scope and aims of the project.

It's up to you to make a strong case to convince the project's developers of the merits of this feature.

Please provide as much detail and context as possible. This means don't request for a solution, but describe the problem you see and how/why you think it should be fixed.

For feature request we have a strict policy.

Keeping issues around with "a good idea" or "not really a bug but we should maybe fix it" turns out to have the reversed effect: nobody looks at it anymore.

Although we really appreciate feedback and ideas, we will close feature requests that we don't expect to fulfill in the next year.

Many of those ideas etc do have a place on the forums; and if enough people like it, someone will stand up and make it.

It's usually best discuss in irc before opening a feature request or working on a large feature in a fork. Discussion in irc can take time, but it can be productive and avoid disappointment :)

Pull requests

Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.

Please ask first before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.

Please adhere to the coding guidelines used throughout the project (indentation, accurate comments, etc.) and any other requirements (such as test coverage).

Adhering to the following process is the best way to get your work included in the project:

1. Fork the project, clone your fork, and configure the remotes:

git clone https://github.com/<your-username>/OpenTTD.git openttd
git clone https://github.com/OpenTTD/OpenTTD-git-hooks.git openttd_hooks
cd openttd
git remote add upstream https://github.com/OpenTTD/OpenTTD.git
cd .git/hooks
ln -s ../../../openttd_hooks/hooks/* .

2. If you cloned a while ago, get the latest changes from upstream:

git fetch upstream

3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:

git checkout upstream/master -b <topic-branch-name>

4. Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely to be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.

5. Locally rebase the upstream development branch into your topic branch:

git fetch upstream
git rebase upstream/master

6. Push your topic branch up to your fork the first time:

git push --set-upstream origin <topic-branch-name>

And any time after that:

git push

7. Open a Pull Request with a clear title and description against the master branch.

IMPORTANT: By submitting a patch, you agree to the License.

Pull request validation

Continuous integration (CI) tools monitor pull requests, and help us identify build and code quality issues.

The results of the CI tests will show on your pull request.

By clicking on Details you can further zoom in; in case of a failure it will show you why it failed. In case of success it will report how awesome you were.

Code guidelines

Code style must be adhered to for pull requests to be accepted

License

By contributing your code, you agree to license your contribution under the GPL v2.

Attribution of this Contributing Guide

This contributing guide is adapted from Bootstrap under the Creative Commons Attribution 3.0 Unported License terms for Bootstrap documentation.