Version 4 (modified by mmadia, 12 years ago) ( diff )

modified first "no personal abuse" and "attachments"

There are a few social rules that are expected to be observed by all contributors of Haiku's Bug Tracker. Some of this content is either directly influenced by or in parts copied verbatim from Mozilla's Bugzilla Etiquette.

  • No personal abuse. Haiku's Bug Tracker is a window into the world of Haiku development. The fact that we permit anyone with an account to add a comment does not mean you are allowed to harass, harangue or otherwise hassle contributors. Do not make weak threats like "I won't use Haiku until this bug is fixed!" If a respected project contributor complains about your behavior on this bug tracker, then your account may be disabled. If you do not like this possibility, then become a respected project contributor. This implies abiding by this rule.
  • No obligation. "Open Source" is not the same as "the developers must do my bidding." The only person who has any obligation to fix the bugs you want fixed is yourself. Never act as if you expect someone to fix a bug by a particular date or release. Not only is this obnoxious, it is likely to get the bug ignored.
  • No whining about decisions. If a respected project contributor has marked a bug as invalid, then it is invalid. Someone filing another duplicate of it does not change this. Unless you have further important evidence, do not post a comment arguing that an invalid or junk bug should be reopened.
  • No pointless comments. Unless you have something constructive and helpful to say, do not add a comment to a bug. In bugs where there is a heated debate going on, you should be even more inclined not to add a comment. Unless you have something new to contribute, then the bug owner is aware of all the issues, and will make a judgment as to what to do. Additional "I see this too" or "It works for me" comments are unnecessary unless they are on a different platform or a significantly different build. Constructive and helpful thoughts unrelated to the topic of the bug should go in the appropriate mailing list or website forum.
  • No private email. Unless the bug owner or another respected project contributor has asked you to email them with specific information, please place all information relating to bugs in the bug itself. Do not send them by private email; no-one else can read them if you do that, and they'll probably just get ignored.
  • Not a forum This bug tracker is for reporting issues within Haiku's codebase. User-errors can be resolved through several other means of communication, such as an appropriate mailing list or IRC Channel. Any tickets deemed to be user-error will be closed as invalid.
  • Attachments As of now, Haiku's bug tracker does not send notification of new attachments on tickets. When posting a new attachment, it is preferred to also post a new comment on the ticket. This comment should indicate the nature and reason for the attachment. If a file is too big for our bug tracker, add a comment giving the file size and contents and ask what to do. Alternatively, you can provide a link to the attachment. While not necessary, a md5sum checksum of the file could be included. This is mostly useful for binary attachments. It will allow another person to verify that the downloaded file matches the one that was uploaded.
Note: See TracWiki for help on using the wiki.