Issues Usage

Issues Usage:

ACCEPTABLE ISSUES:

• Bug Reports Before posting a bug, please try to isolate the issue by testing and narrowing down variables involved if you can and definitely explain more detail about what you did when the bug was experienced, providing the steps so we can try to reproduce it. This will save us a lot time wasted replying with the generally same set of first questions…
• Feature Suggestions/Requests/Proposals New features are exciting for sure, but before jumping the gun, please check thoroughly that there isn't an existing ticket for your feature or a similar one (try searching multiple ways and keywords) before posting.
• Planned Features/Actionable Tasks* …not "issues" persay, but features planned for future releases that we are using Issues to track and assign as we work toward milestones. *This is more for the core collaborators really as consensus is drawn up for action plans

NOT AN ISSUE:

• General Questions Check the Wiki and take a look at existing Issues and Pull Requests (as they can be submitted independently from an open issue) first.
• Open Discussions We are looking into a better place for this, which is part of this thread's purpose…continue below
• Issueless Gratitude I think we all appreciate the gratitude, but the Issues isn't the place for it unless it's used to soften the blow of a bug report or feature request, in which case: by all means… Otherwise, please use twitter, or whatever open discussion platform we end up using.

Good Practice:

• Before posting…
  • Check the Wiki.
  • Read the Readme.
  • Search the Issues! (and please try a few searches with different keywords).
  • Take a look at the open Pull Requests.
• Don't derail the issue.
  • Keep your comments on the issue topic.
  • If needed, open new ticket for unrelated issues found in the issue troubleshoot.