Confirm
1,567
edits
Changes
→whiteboard keywords for categorizing the issues: adding needscontact
We are using a set of keywords in the whiteboard field to help us figuring out priorities, languages, etc.
; [clientsniff] : When the sniffing is happening on the client-side such as HTML or JS
; [contactready] : Once the Web site has been analyzed for Web compatibility issuesAND we found a contact (so after [needscontact]). Someone can take the bug and contact the Web site for achieving a resolution. [http://mzl.la/1awGwHK List of Web sites to contact]
; [country-ISOCODE] : Some websites are dedicated to a specific country. For example, a French Web site can be classified as [country-fr], a japanese Web site as [country-jp], for international Web sites you can use [country-all]
; [js] : JavaScript issue
; [lib-foo] : When related to a specific JS lib being used. Example [lib-yui] [lib-jquery] [lib-mootools]
; [needscontact] : Finding the right contact is a bit like black magic. It requires a certain set of skills. Before contacting and switching the bug to [contactready], we need to find how/who to talk to.
; [notcontactready] : Sometimes a bug has a dependency or is in the process of being further investigated, hence it is not ready for being formally contacted.
; [serversniff] : When the sniffing is happening on the server-side such as HTTP redirection and/or different content being served on the same domain
