| 1 | # Contributing
|
| 2 |
|
| 3 | Thank you for wanting to contribute. stylelint *needs* community contributions to continue to improve.
|
| 4 |
|
| 5 | If you like stylelint and open source software (since you're reading this, you almost certainly do), please consider taking some time to pitch in. Not only will you help stylelint thrive, you will also learn a thing or two — about CSS, PostCSS, Node, ES2015, unit testing, open source software, and more.
|
| 6 |
|
| 7 | **We want to do everything we can to encourage contributions!** So if you want to participate but don't end up doing it for one reason or another, please file an issue and give us feedback about what we could do to better encourage you.
|
| 8 |
|
| 9 | Also: we hope that your participation in the project isn't a one-off. *We'd love to add more members to the organization and see more regulars pop up in issues and pull requests!*
|
| 10 |
|
| 11 | ## Code contributions
|
| 12 |
|
| 13 | The [developer guide](docs/developer-guide.md) outlines how to get started contributing code.
|
| 14 |
|
| 15 | ## Financial contributions
|
| 16 |
|
| 17 | We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/stylelint).
|
| 18 | Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.
|