You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

16 lines
1.1 KiB

10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
  1. # Submitting issues
  2. **Must read:** [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
  3. ### IMPORTANT
  4. 1. When you file an issue, your **responsibility** is to provide **ALL** the exact steps needed for me to reproduce an issue.
  5. 1. Ideally, never should I have to _guess_ how to reproduce an issue.
  6. - Hence this is why very detailed steps must be very carefully written down **the first time** the issue is filed.
  7. - Never assume an important step is "obvious".
  8. 1. Every single step, in order, must be provided, with **ALL** relevant details.
  9. 1. Screenshots are nice, but use common sense: I can't cut and paste important text information from screenshots.
  10. - Regarding screenshots: common sense. Too much of a thing can easily end up as noise.
  11. 1. Open source quality software comes from contributors carefully **crafting** code: conversely, issues must also be carefully **crafted**.
  12. - In other words: you benefit from the carefully crafted code, return the favor by **carefully** crafting issues/bug reports.
  13. 1. If your mindset is that your time is more precious than that of my time, refrain from filing issues.