Jump to: navigation, search

Difference between revisions of "UI Best Practices Update Process"

(Have things reviewed)
(Have things reviewed)
Line 16: Line 16:
  
 
* Change the status of the bug to resolved with resolution fixed.  This will trigger review.
 
* Change the status of the bug to resolved with resolution fixed.  This will trigger review.
* Wait a while.  If there is violent objection someone will reopen the bug.  Discussion can happen on the bug thread or UI Best Practices Working Group mailing list.  This can also be brought up at one of the meetings.
+
* Wait a while.  If there is violent objection someone will reopen the bug.  Discussion can happen on the bug thread or UI Best Practices Working Group mailing list.  Issues can also be brought up at one of the meetings.
  
 
== Merge your changes into the drafts ==
 
== Merge your changes into the drafts ==
  
 
* Move your content from the sandbox to the draft pages here: [[UI Best Practices v3.x]]
 
* Move your content from the sandbox to the draft pages here: [[UI Best Practices v3.x]]

Revision as of 21:17, 6 February 2007

Process for Updating the UI Best Practices Guidelines

Make a request

  • Look at the discussion page Talk:User_Interface_Guidelines and see if there is already a request. If not:
  • File a bugzilla with component “UI Guidelines”
  • Track the bug. The bug will get reviewed and voted on. If it gets enough votes it will be assigned (probably to you if you volunteered to do the work). Otherwise it will be resolved as will not fix.

Add your content

Have things reviewed

  • Change the status of the bug to resolved with resolution fixed. This will trigger review.
  • Wait a while. If there is violent objection someone will reopen the bug. Discussion can happen on the bug thread or UI Best Practices Working Group mailing list. Issues can also be brought up at one of the meetings.

Merge your changes into the drafts