Changes between Version 3 and Version 4 of BugTrackerEtiquette


Ignore:
Timestamp:
May 18, 2009, 1:45:25 AM (16 years ago)
Author:
mmadia
Comment:

modified first "no personal abuse" and "attachments"

Legend:

Unmodified
Added
Removed
Modified

  • BugTrackerEtiquette

    v3 v4  
    11There are a few social rules that are expected to be observed by all contributors of [http://dev.haiku-os.org Haiku's Bug Tracker]. Some of this content is either directly influenced by or in parts copied verbatim from [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Mozilla's Bugzilla Etiquette].
    22
    3   * '''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 attitude being displayed on this bug tracker, then you may have your account disabled. If you don't like this possibility, become a respected project contributor. This implies abiding by this rule.
     3  * '''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.
    44
    55  * '''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.
    … …  
    1313  * '''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 [http://www.haiku-os.org/community/ml mailing list] or [http://www.haiku-os.org/community/irc IRC Channel]. Any tickets deemed to be user-error will be closed as invalid.
    1414
    15   * '''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. In both cases, it is preferred to provide a [http://en.wikipedia.org/wiki/Md5sum md5sum checksum] of the file. 
     15  * '''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 [http://en.wikipedia.org/wiki/Md5sum 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.
    1616
    1717{{{