Bugzilla Posting Rules

1. Create a single user

Create one user, with your Cal Poly Email. 

2. Create a product for each project

For Project1, Project2, etc. create one product each.  Give each product a single component: “main”.

3. Monitor for bugs regularly

Check bug postings at least daily.  For each bug, resolve it in exactly one of these four ways:

invalid

fixed

worksforme

duplicate

You get to decide how it’s resolved, but:

a. Mark it “invalid” only if it reports behavior that is to-spec or if it is so poorly explained that you cannot repeat it.

b. Mark it “fixed” only after you’ve created and posted a fix.  If you don’t fix it carefully, you are inviting a second bug post against the bug in question.  That’s 2 points if so.

c. Mark it “works for me” only if you have carefully followed the instructions for repeating the bug, and cannot repeat it.

d. Mark “duplicate” only against bugs that are currently open.  In particular, you may not make a duplicate assignment to a bug you’ve already resolved.  Either the new bug is pointing out an incomplete fix, in which case it’s a valid bug, or it’s incorrectly identifying behavior that is already repaired, in which case it’s “works for me”.

4. Post bugs carefully

Test others websites and post bugs that you find against them.  But, be sure:

1. That you review existing outstanding bugs to be sure you’re not being a nuisance by posting a duplicate.

2. That you describe the bug clearly.

If you find a bug in one implementation, be sure to check others for the same error.  You can rack up good points this way.

5. Read others’ bug posts, including those against other applications

This will give you good hints on what to fix in advance in your own application.  This is fair game.

6. Negotiate in lab on any disagreements on “resolution”.

If you cannot reach agreement after in-person discussion, I will do final adjudication.

7. Point System

For each bug resolved as “FIXED” (or left as NEW at the end of the quarter) the reporter gains a point and the author of the application loses a point.  It’s a zero-sum game. :)