|
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +To help us deliver great features and support the Renovate Open Source project we ask that you: |
| 4 | + |
| 5 | +- are polite |
| 6 | +- pay attention to details |
| 7 | +- keep in mind that most maintainers are volunteers |
| 8 | +- are respectful of the time and effort of the maintainers |
| 9 | + |
| 10 | +## Our priorities |
| 11 | + |
| 12 | +We want to keep this project sustainable. |
| 13 | +This means we support our maintainers and contributors, who spend their free time to help others. |
| 14 | + |
| 15 | +Maintainers getting stressed is a big threat to Open Source projects, like ours. |
| 16 | +Stressed maintainers quit, or reduce their time spent on the project. |
| 17 | +Often a few users behave badly, where most users are nice. |
| 18 | + |
| 19 | +We want to avoid maintainers getting stressed out by bad behavior from contributors. |
| 20 | +That's why we have these rules. |
| 21 | + |
| 22 | +## Politeness |
| 23 | + |
| 24 | +Sadly, it's common in Open Source projects for a few users to behave in an aggressive and rude way. |
| 25 | +A user might say something like: "You should have fixed this bug already!", or "Why am I still waiting for this feature?". |
| 26 | +We do not allow this kind of behavior. |
| 27 | + |
| 28 | +We expect basic politeness, do not act rude. |
| 29 | +For example: it is okay if you ask a question and do not thank us afterwards. |
| 30 | +But avoid writing mean comments like: "Pity the documentation didn’t say that." or "Thanks for nothing.". |
| 31 | + |
| 32 | +## Respect the time of those who help you |
| 33 | + |
| 34 | +Respect goes both ways, but time is limited. |
| 35 | +When you ask for help, please remember that the maintainer's time is valuable. |
| 36 | +We get many questions each week and do our best to answer each one. |
| 37 | +To get the help you need, please be prepared to give detailed logs or descriptions of your issues. |
| 38 | +If you do not want to spend the effort giving us enough information, it's likely you will not get the help you need. |
| 39 | + |
| 40 | +Remember, most of the support provided by our team, including the Mend.io staff, is _unpaid_. |
| 41 | + |
| 42 | +## Blocking and unblocking |
| 43 | + |
| 44 | +We quickly deal with rudeness in the community with: |
| 45 | + |
| 46 | +- automated comments |
| 47 | +- temporary blocks |
| 48 | +- permanent bans |
| 49 | + |
| 50 | +If you keep breaking the rules or challenge our guidelines openly, you will be blocked. |
| 51 | +For example: if you keep spamming the maintainers with `@mentions` or challenge our rules openly, you will be blocked. |
| 52 | + |
| 53 | +We generally do not argue about these decisions, but we are willing to reverse a block if a you show that you understand and respect the rules, or if there was a misunderstanding. |
| 54 | +Please reach out to the project's lead maintainer Rhys Arkins by email if so (the shorter the better). |
| 55 | + |
| 56 | +Simply put: we block and unblock swiftly, what matters is how you follow the rules going forward. |
| 57 | + |
| 58 | +## How we prioritize work |
| 59 | + |
| 60 | +Renovate's core contributors and maintainers focus on work that: |
| 61 | + |
| 62 | +- Helps a lot of users, or |
| 63 | +- Fixes regressions (errors introduced by recent changes), or |
| 64 | +- Is required by a customer of Mend.io, or |
| 65 | +- Is sponsored by third parties after independent validation, or |
| 66 | +- We personally need or want to implement |
| 67 | + |
| 68 | +You may be disappointed when we focus on other work ahead of your feature or bug, but you should understand and accept this. |
| 69 | + |
| 70 | +## Maintaining Issue and Code quality |
| 71 | + |
| 72 | +We use GitHub Discussions to start and sort issues. |
| 73 | +Only maintainers are allowed to create new issues. |
| 74 | +If we confirm a bug or agree with a feature idea, and if it's well-documented, we will turn it into an official issue. |
| 75 | +This way most issues are ready to work on, either by us or the community. |
| 76 | + |
| 77 | +We may reject ideas that are too specialized, or that would make the project too hard to maintain. |
| 78 | + |
| 79 | +We have strict coding standards and reviews to keep our code in good shape. |
| 80 | +A feature or fix must of course work, but it must also be well designed to stay maintainable. |
| 81 | +We may ask you to improve your code several times in a row, which can be difficult for you. |
| 82 | +We only do this to keep the project sustainable. |
| 83 | + |
| 84 | +## If you have urgent work |
| 85 | + |
| 86 | +People working for big companies might push too hard in Open Source projects. |
| 87 | +It’s often hard for them to understand that our maintainers cannot spend much time to solve their issues quickly. |
| 88 | +Frequent requests for updates like "@rarkins how can we move this forward?" are _not_ helpful. |
| 89 | + |
| 90 | +Please remember, unless you are a Mend.io customer, this project does not owe you the level of response or support you might expect. |
| 91 | +Mend.io customers should use their designated support channels for urgent needs. |
| 92 | + |
| 93 | +## Getting more help |
| 94 | + |
| 95 | +If you need more assistance than what this project offers, you have two options: |
| 96 | + |
| 97 | +1. Become a Mend.io customer, such as by buying Renovate Enterprise, or |
| 98 | +1. Hire an experienced Renovate contributor privately for consulting. Mend.io staff do _not_ offer this service, but one of our volunteer maintainers, [`@secustor`](https://github.com/secustor), does |
| 99 | + |
| 100 | +## Feedback |
| 101 | + |
| 102 | +We welcome respectful discussions about these rules and accept suggestions that improve this text. |
| 103 | +We avoid debates on social media or going off-topic in GitHub Discussions. |
| 104 | + |
| 105 | +Because we enforce all these rules, we can deliver new features and give excellent support to the community. |
0 commit comments