Contribute

Bug Reports

Please report us any bugs or feature requests on our bug tracker system. It's the best way to keep track about issues.

Found a bug? Please report it on the KDE issue tracker. Don't forget to follow the issue reporting guidelines! Most importantly, don't forget to include the version number of Rolisteam that you are using.

Warning: Failing to provide the information required in the bug report template will result in the bug report being automatically closed.

New Features and Bug Fixes

Please, take a look at the Rolisteam roadmap.

Do you know how to code? Follow these steps:

  1. Submit an issue for your feature or bug on the KDE issue tracker.
    Note: This step is necessary to ensure that the new feature meets the project goals or that the bug isn't really a feature. You will also want to coordinate what areas of code you will be updating to avoid merge conflicts in case someone else is working on that same area of code as well.
  2. After discussion for your new issue, code your feature or bug fix. Please follow the [Rolisteam coding style guide]{32_coding.md}. Important: Please keep your code focused on the issue at hand. Unrelated changes to the code belong to separate issues/merge requests to make code review and testing easier.
  3. Submit a pull request against the master branch with your code updates.
    Important: Please squash your commits in git before submitting the pull request!
  4. Wait for a brief code review and at least two other volunteers to test your feature or bug fix.
  5. Make updates to your pull request as you receive feedback.
  6. Once your pull request is approved by at least two other volunteer testers, your pull request will be merged.

Learn how to compile rolisteam

Go to this page in order to learn how to build Rolisteam from source.

Code Reviews

Do you know how to code and have an eye for details? Volunteer to peer review new merge requests!

  1. Look for a new merge request, and add a comment that you are volunteering to code review it.
  2. Submit code review comments.
  3. Wait for updates to the merge request (if needed).
  4. Continue providing feedback until you are confident the code is sound.
  5. Leave a comment with your approval of the merge request.
  6. Once at least two volunteer testers submit their approval, the merge request will be merged.

Some tips can be found on coding guidelines

Testing

Volunteer to review code and test new features and bug fixes! Follow these steps:

  1. Look for a new merge request, and add a comment that you are volunteering to test it.
  2. Build the merge request on your platform.
  3. Test the feature/bug fix and try to break it!
  4. Provide feedback on test results in the merge request.
  5. Wait for updates to the merge request (if needed).
  6. Continue testing and providing feedback until you are confident the code is working.
  7. Leave a comment with your approval of the merge request.
  8. Once at least one other volunteer tester submits their approval, the merge request will be accepted.

Translations

Please consider joining the KDE localization team to translate your favorite applications into other languages.

Contact Us

You want to contribute, but don't know where to start ?  To contact humans directly, the best way is our Discord server.