Skip to content

Latest commit

 

History

History
48 lines (28 loc) · 2.82 KB

CONTRIBUTING.md

File metadata and controls

48 lines (28 loc) · 2.82 KB

Contribution guide

You are reading the contribution guide for the Server Edition. Interested in contributing to other parts of Fullstaq Ruby? Check the Fullstaq Ruby Umbrella contribution guide.

Thanks for considering to contribute! 😀 Your help is essential to keeping Fullstaq Ruby great. We welcome all contributions, no matter who you are, and no matter whether it's big or small (see also our Code of Conduct). With this guide, we aim to make contributing as clear and easy as possible.

What counts as a contribution?

Anything that helps improving the project, whether directly (through a pull request) or indirectly (by engaging with us) counts as a contribution. Here's a non-exhaustive list:

  • Reporting an issue.
  • Triaging issues: determining whether an issue report is clear enough, whether the issue still persists, and whether it is reproducible.
  • Updating documentation.
  • Proposing an improvement.
  • Sending a pull request.
  • Reviewing someone else's pull request.

Not sure how to get started?

Have a look at our issue tracker. Issues with the following labels are good starting points:

  • "good first issue" if you're looking for something easy.
  • "help wanted" if you're in for a challenge, or if you want to help with a high-impact issue.

Development handbook

To learn how the Fullstaq Ruby Server Edition codebase works and how to develop it, please read our development handbook.

Stuck? Need help?

Please post something on our discussion forum.

Joining the team

Anyone who wishes to contribute regularly to Fullstaq Ruby Server Edition, or who wishes to assume responsibility for the health and progress of this project, is welcome to join the team!

To learn more about what it means to be a team member, see Responsibilities & expectations.

Trust

Because joining the team means gaining access to protected resources, trust is essential. We judge trustworthiness through the following manners:

  • Having an established relationship with either the Fullstaq Ruby project, or the wider Ruby community. The longer the better.
  • A contractual relationship (such as employment) with Fullstaq B.V.. Contractual relationships carry legal weight and provide greater likelihood of a stable trust relationship; at a minimum they establish strong legal accountability.

Apply

If you wish to join, please apply by submitting an issue.