|
1 | 1 | # How to contribute? |
| 2 | + |
2 | 3 | ## Report bugs |
3 | | -You use your Pinetime and find a bug in the firmware? [Create an issue on Github](https://github.com/JF002/InfiniTime/issues) explaining the bug, how to reproduce it, the version of the firmware you use... |
| 4 | + |
| 5 | +Have you found a bug in the firmware? [Create an issue on Github](https://github.com/JF002/InfiniTime/issues) explaining the bug, how to reproduce it, the version of the firmware you use... |
| 6 | + |
4 | 7 | ## Write and improve documentation |
| 8 | + |
5 | 9 | Documentation might be incomplete, or not clear enough, and it is always possible to improve it with better wording, pictures, photo, video,... |
6 | 10 |
|
7 | 11 | As the documentation is part of the source code, you can submit your improvements to the documentation by submitting a pull request (see below). |
| 12 | + |
8 | 13 | ## Fix bugs, add functionalities and improve the code |
| 14 | + |
9 | 15 | You want to fix a bug, add a cool new functionality or improve the code? See *How to submit a pull request below*. |
| 16 | + |
10 | 17 | ## Spread the word |
11 | | -The Pinetime is a cool open source project that deserves to be known. Talk about it around you, on social networks, on your blog,... and let people know that we are working on an open-source firmware for a smartwatch! |
| 18 | + |
| 19 | +The Pinetime is a cool open source project that deserves to be known. Talk about it around you, on social networks, on your blog,... and let people know that we are working on an open source firmware for a smartwatch! |
12 | 20 |
|
13 | 21 | # How to submit a pull request ? |
14 | 22 |
|
15 | 23 | ## TL;DR |
| 24 | + |
16 | 25 | - Create a branch from develop; |
17 | 26 | - Work on a single subject in this branch. Create multiple branches/pulls-requests if you want to work on multiple subjects (bugs, features,...); |
18 | 27 | - Test your modifications on the actual hardware; |
19 | 28 | - Check the code formatting against our coding conventions and [clang-format](../.clang-format) and [clang-tidy](../.clang-tidy); |
20 | 29 | - Clean your code and remove files that are not needed; |
21 | | - - Write documentation related to your new feature is applicable; |
22 | | - - Create the pull-request and write a great description about it : what does your PR do, why, how,... Add pictures and video if possible; |
| 30 | + - Write documentation related to your new feature if applicable; |
| 31 | + - Create a pull request and write a great description about it : what does your PR do, why, how,... Add pictures and video if possible; |
23 | 32 | - Wait for someone to review your PR and take part in the review process; |
24 | 33 | - Your PR will eventually be merged :) |
25 | 34 |
|
26 | | -Your contribution is more than welcome! |
| 35 | +Your contributions are more than welcome! |
27 | 36 |
|
28 | | -If you want to fix a bug, add a functionality or improve the code, you'll first need to create a branch from the **develop** branch (see [this page about the branching model](./branches.md)). This branch is called a feature branch, and you should choose a name that explains what you are working on (ex: "add-doc-about-contributions"). In this branch, **focus on only one topic, bug or feature**. For example, if you created this branch to work on the UI of a specific application, do not commit modifications about the SPI driver. If you want to work on multiple topics, create one branch per topic. |
| 37 | +If you want to fix a bug, add functionality or improve the code, you'll first need to create a branch from the **develop** branch (see [this page about the branching model](./branches.md)). This branch is called a feature branch, and you should choose a name that explains what you are working on (ex: "add-doc-about-contributions"). In this branch, **focus on only one topic, bug or feature**. For example, if you created this branch to work on the UI of a specific application, do not commit modifications about the SPI driver. If you want to work on multiple topics, create one branch for each topic. |
29 | 38 |
|
30 | 39 | When your feature branch is ready, **make sure it actually works** and **do not forget to write documentation** about it if it's relevant. |
31 | 40 |
|
32 | | -I **strongly discourage to create a PR containing modifications that haven't been tested**. If, for any reason, you cannot test your modifications but want to publish them anyway, **please mention it in the description**. This way, other contributors might be willing to test it and provide feedback about your code. |
| 41 | +**Creating a pull request containing modifications that haven't been tested is strongly discouraged.** If, for any reason, you cannot test your modifications but want to publish them anyway, **please mention it in the description**. This way, other contributors might be willing to test it and provide feedback about your code. |
33 | 42 |
|
34 | 43 | Also, before submitting your PR, check the coding style of your code against the **coding conventions** detailed below. This project also provides [clang-format](../.clang-format) and [clang-tidy](../.clang-tidy) configuration files. You can use them to ensure correct formatting of your code. |
35 | 44 |
|
36 | | -Do not forget to check the files you are going to commit and remove those who are not necessary (config files from your IDE, for example). Remove old comments, commented code,... |
| 45 | +Don't forget to check the files you are going to commit and remove those which aren't necessary (config files from your IDE, for example). Remove old comments, commented code,... |
37 | 46 |
|
38 | | -Then, you can submit a pull-request for review. Try to **describe your pull request as much as possible**: what did you do in this branch, how does it work, how is it designed, are there any limitations,... This will help the contributors to understand and review your code easily. You can add pictures and video to the description so that contributors will have a quick overview of your work. |
| 47 | +Then, you can submit a pull request for review. Try to **describe your pull request as much as possible**: what did you do in this branch, how does it work, how it is designed, are there any limitations,... This will help the contributors to understand and review your code easily. You can add pictures and video to the description so that contributors will have a quick overview of your work. |
39 | 48 |
|
40 | 49 | Other contributors can post comments about the pull request, maybe ask for more info or adjustments in the code. |
41 | 50 |
|
42 | | -Once the pull request is reviewed and accepted, it'll be merge in **develop** and will be released in the next release version of the firmware. |
| 51 | +Once the pull request is reviewed and accepted, it'll be merged into **develop** and will be released in the next version of the firmware. |
43 | 52 |
|
44 | 53 | ## Why all these rules? |
45 | | -Reviewing pull-requests is a **very time consuming task** for the creator of this project ([JF002](https://github.com/JF002)) and for other contributors who take the time to review them. Every little thing you do to make their lives easier will **increase the chances your PR will be merge quickly**. |
46 | 54 |
|
47 | | -When reviewing PR, the author and contributors will first look at the **description**. If it's easy to understand what the PR does, why the modification is needed or interesting and how it's done, a good part of the work is already done : we understand the PR and its context. |
| 55 | +Reviewing pull requests is a **very time consuming task** for the creator of this project ([JF002](https://github.com/JF002)) and for other contributors who take the time to review them. Everything you do to make reviewing easier will **get your PR merged faster**. |
48 | 56 |
|
49 | | -Then, reviewing **a few files that were modified for a single purpose** is a lot more easier than to review 30 files modified for many reasons (bug fix, UI improvements, typos in doc,...), even if all these changes make sense. Also, it's possible that we agree on some modification but not on some other, and we won't be able to merge the PR because of the changes that are not accepted. |
| 57 | +When reviewing PRs, the author and contributors will first look at the **description**. If it's easy to understand what the PR does, why the modification is needed or interesting and how it's done, a good part of the work is already done : we understand the PR and its context. |
50 | 58 |
|
51 | | -We do our best to keep the code as consistent as possible, and that means we pay attention to the **formatting** of the code. If the code formatting is not consistent with our code base, we'll ask you to review it, which will take more time. |
| 59 | +Then, reviewing **a few files that were modified for a single purpose** is a lot more easier than to review 30 files modified for many reasons (bug fix, UI improvements, typos in doc,...), even if all these changes make sense. Also, it's possible that we agree on some modification but not on some other, so we won't be able to merge the PR because of the changes that are not accepted. |
52 | 60 |
|
53 | | -The last step of the review consists in **testing** the modification. If it doesn't work out of the box, we'll ask your to review your code and to ensure that it works as expected. |
| 61 | +We do our best to keep the code as consistent as possible. If the formatting of the code in your PR is not consistent with our code base, we'll ask you to review it, which will take more time. |
54 | 62 |
|
55 | | -It's totally normal for a PR to need some more work even after it was created, that's why we review them. But every round trip takes time, and it's good practice to try to reduce them as much as possible by following those simple rules. |
| 63 | +The last step of the review consists of **testing** the modification. If it doesn't work out of the box, we'll ask your to review your code and to ensure that it works as expected. |
| 64 | + |
| 65 | +It's totally normal for a PR to need some more work even after it was created, that's why we review them. But every round trip takes time, so it's good practice to try to reduce them as much as possible by following those simple rules. |
56 | 66 |
|
57 | 67 | # Coding convention |
| 68 | + |
58 | 69 | ## Language |
59 | | -The language of this project is **C++**, and all new code must be written in C++. (Modern) C++ provides a lot of useful tools and functionalities that are beneficial for embedded software development like `constexpr`, `template` and anything that provides zero-cost abstraction. |
60 | 70 |
|
61 | | -It's OK to include C code if this code comes from another library like FreeRTOS, NimBLE, LVGL or the NRF-SDK. |
| 71 | +The language of this project is **C++**, and all new code must be written in C++. (Modern) C++ provides a lot of useful tools and functionalities that are beneficial for embedded software development like `constexpr`, `template` and anything that provides zero-cost abstraction. |
| 72 | + |
| 73 | +C code is accepted if it comes from another library like FreeRTOS, NimBLE, LVGL or the NRF-SDK. |
62 | 74 |
|
63 | 75 | ## Coding style |
| 76 | + |
64 | 77 | The most important rule to follow is to try to keep the code as easy to read and maintain as possible. |
65 | 78 |
|
| 79 | +Using an autoformatter is highly recommended, but make sure it's configured properly. |
| 80 | + |
| 81 | +There are preconfigured autoformatter rules for: |
| 82 | + |
| 83 | + * CLion (IntelliJ) in .idea/codeStyles/Project.xml |
| 84 | + |
| 85 | +If there are no preconfigured rules for your IDE, you can use one of the existing ones to configure your IDE. |
| 86 | + |
66 | 87 | - **Indentation** : 2 spaces, no tabulation |
67 | 88 | - **Opening brace** at the end of the line |
68 | 89 | - **Naming** : Choose self-describing variable name |
|
0 commit comments