roc-lang/roc
1
1
Fork 0
mirror of https://github.com/roc-lang/roc.git synced 2024-11-11 16:51:53 +03:00
Code Issues Packages Projects Releases Wiki Activity
3c5355aa2d
roc/CONTRIBUTING.md
Ayaz Hafiz e37109f7ea
Advertise larger Roc project ideas in CONTRIBUTING 
This document summarizes larger implementation- or research-heavy
projects that may be suitable for someone who wants to contribute to Roc
via a self-contained project. Most of these projects are expected to
require sustained effort, which also makes them possibly suitable for
academic theses.

Feel free to message me on Zulip to get edit rights to the document!
2022-09-20 13:36:32 -05:00

3.3 KiB
Raw Blame History

Contributing

Code of Conduct

We are committed to providing a friendly, safe and welcoming environment for all. Make sure to take a look at the Code of Conduct!

How to contribute

All contributions are appreciated! Typo fixes, bug fixes, feature requests, bug reports are all helpful for the project.

If you are looking for a good place to start, consider reaching out on the #contributing channel on Roc Zulip. Before making your first pull request, definitely talk to an existing contributor on Roc Zulip first about what you plan to do! This can not only avoid duplicated effort, it can also avoid making a whole PR only to discover it won't be accepted because the change doesn't fit with the goals of the language's design or implementation.

If you are interested in larger, implementation- or research-heavy projects related to Roc, check out Roc Project Ideas and reach out to us on Zulip! These projects may be suitable for academic theses, independent research, or even just valuable projects to learn from and improve Roc with.

Building from Source

Check Building from source for instructions.

Running Tests

Most contributors execute the following commands befor pushing their code:

cargo test
cargo fmt --all -- --check
cargo clippy --workspace --tests -- --deny warnings

Execute cargo fmt --all to fix the formatting.

Contribution Tips

  • If you've never made a pull request on github before, this will be a good place to start.

  • Create an issue if the purpose of a struct/field/type/function/... is not immediately clear from its name or nearby comments.

  • You can find good first issues here.

  • Fork the repo so that you can apply your changes first on your own copy of the roc repo.

  • It's a good idea to open a draft pull request as you begin working on something. This way, others can see that you're working on it, which avoids duplicate effort, and others can give feedback sooner rather than later if they notice a problem in the direction things are going. Click the button "ready for review" when it's ready.

  • All your commits need to be signed to prevent impersonation:

    1. If you have a Yubikey, follow guide 1, guide 2 and skip the steps below.
    2. Make a key to sign your commits..
    3. Configure git to use your key.
    4. Make git sign your commits automatically:
    git config --global commit.gpgsign true

Can we do better?

Feel free to open an issue if you think this document can be improved or is unclear in any way.