-
-
Notifications
You must be signed in to change notification settings - Fork 123
Issue Guidelines and Policies
Time is precious and limited. Don't waste people's time.
Filing issues that are incomplete, non-sensical, or are you basically asking for free programming help, run counter to what open-source software is all about. By using any open-source software you are implicitly gaining value from the community that provides that software. The implicit consequence of that fact, is that you become part of the community, and as such, have a responsibility to that community. You should desire to give back, or at least not be a drain on a community that provides you with such a gift.
Considering that we all have a limited number of heartbeats in this life, and that I've provided this library to the community out of the kindness of my beating heart, you should not waste my time or that of any others in the community.
Because I care about your time and in order to save precious heartbeats for us all, I have provided a template for you to use when creating an issue. This template is automatically populated in the "New Issue" form. The questions in the issue template are there because experience has shown that the information being asked for is usually relevant in helping me (and others) solve your issue.
All issue requests MUST answer ALL questions in the provided template. Please do NOT ignore any of the questions in the template, even if you think they are self-explanatory, irrelevant, or stupid.
Failure to follow these simple rules will most likely result in your issue being closed and not addressed, and may lead to public shaming. :)
All help is welcome and appreciated! If you know the answer to an issue, please feel empowered! You are part of the community. If you would like to become an official part of the community, I'd welcome it, so please let me know!
If you do want help with a more general, "How do I do X?" question, please do consider buying me a beer or two in exchange.
If you need help with a project, I'm open to that too. Please send me an email or find me on LinkedIn so we can talk about it.