|
2 | 2 |
|
3 | 3 | We love receiving pull requests. We use them ourselves for reviewing new features |
4 | 4 | and fixing issues in modm. If you want to contribute, but don't exactly know what |
5 | | -or how, have a look at the [issues we tagged with "help wanted"][help_wanted]. |
| 5 | +or how, have a look at the [issues we tagged with "help wanted"][help_wanted] or |
| 6 | +the [threads tagged with "💡 Ideas"][ideas]. |
6 | 7 |
|
7 | 8 | To start contributing, please fork modm and then start a new branch on top of |
8 | 9 | the `develop` branch. We prefer to fast-forward merges, instead of creating a |
@@ -36,13 +37,14 @@ The dedicated maintainers of modm are [@salkinium](https://github.com/salkinium) |
36 | 37 | and [@rleh](https://github.com/rleh) and you can always ping them. |
37 | 38 |
|
38 | 39 | If you want to add a new platform, or other significant functionality, we |
39 | | -[ask you to discuss that in an issue first][issues]. We are very open to new |
40 | | -helping hands, but all of this is still fairly complicated and we want to |
| 40 | +[ask you to discuss that in a thread first][ideas]. We are very open to |
| 41 | +new helping hands, but all of this is still fairly complicated and we want to |
41 | 42 | provide you with tips and additional explanations along the way. |
42 | 43 |
|
43 | 44 | Communication is cheap, implementation is expensive and we don't want to |
44 | 45 | frustrate you. |
45 | 46 |
|
46 | 47 | [issues]: https://github.com/modm-io/modm/issues |
47 | 48 | [pulls]: https://github.com/modm-io/modm/pulls |
| 49 | +[ideas]: https://github.com/modm-io/modm/discussions/categories/ideas |
48 | 50 | [help_wanted]: https://github.com/modm-io/modm/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted+🛠%22 |
0 commit comments