Support:PRD: Difference between revisions

1,347 bytes added ,  15 November 2007
update contributor process
(update contributor process)
Line 65: Line 65:


Articles are required to be reviewed, before going live. As our community grows, and we have more reviewers, we will have two separate editorial approval processes: content and style (content can be published initially if correct, even if not style guide needs to be implemented)
Articles are required to be reviewed, before going live. As our community grows, and we have more reviewers, we will have two separate editorial approval processes: content and style (content can be published initially if correct, even if not style guide needs to be implemented)
New articles will initially existing in a staging area, where it can be reviewed and edited, before being visible to people not logged in. Once approved for visibility to the general public, the reviewer will move the article from the staging area to the public knowledge base.


=== Existing documents / edits ===
=== Existing documents / edits ===
Line 71: Line 73:


Major: Same review as new documents
Major: Same review as new documents
All edits need to be made on a staging copy of the article. Once an edit is made, the edit is tagged for review. Contiguous edits by the same contributor will be treated as one edit. Anyone with given permission, can either approve or reject the edit. Once approved, the edit is applied to the KB version of the article. If the editor has reviewer permission, their own edit is automatically approved. Approvals and rejections are done on an edit-by-edit basis; so if there has been more than one edit to a staging copy, each edit has to be approved or rejected.




Line 91: Line 95:
==Technical requirements==
==Technical requirements==
This summarizes our technical requirements for the knowledge base:
This summarizes our technical requirements for the knowledge base:
* Permission to make live edits to live articles should be restricted to those who have already earned our trust. There should never be incorrect information in Firefox Support KB articles.
** Registered users should still be able to submit edits, either to bugs, or by editing a trunk version of the article, which is going to be tricky to make contributor-friendly. [https://bugzilla.mozilla.org/show_bug.cgi?id=392513]
* Need way of knowing which staging copies are not same as live copy. [https://bugzilla.mozilla.org/show_bug.cgi?id=401916]
* Approve and Reject buttons for reviewing article edits. [https://bugzilla.mozilla.org/show_bug.cgi?id=402884]
** If the editor has reviewer permission, their own edit is automatically approved. [https://bugzilla.mozilla.org/show_bug.cgi?id=403869]
** Approving edits should add the contributor credit to the live article. [https://bugzilla.mozilla.org/show_bug.cgi?id=401917]


* If a page doesn't exist for the requested locale, TikiWiki should fallback according to the http accept-language header if not logged in, or according to the user preferences if logged in. [https://bugzilla.mozilla.org/show_bug.cgi?id=398353]
* If a page doesn't exist for the requested locale, TikiWiki should fallback according to the http accept-language header if not logged in, or according to the user preferences if logged in. [https://bugzilla.mozilla.org/show_bug.cgi?id=398353]
** If a page doesn't exist for the requested locale, a box should appear at the beginning of the article explaining that the page is not yet translated to the requested language. [https://bugzilla.mozilla.org/show_bug.cgi?id=398354]  
** If a page doesn't exist for the requested locale, a box should appear at the beginning of the article explaining that the page is not yet translated to the requested language. [https://bugzilla.mozilla.org/show_bug.cgi?id=398354]  
* Permission to make live edits to live articles should be restricted to those who have already earned our trust. There should never be incorrect information in Firefox Support KB articles.
** Registered users should still be able to submit edits, either to bugs, or by editing a trunk version of the article, which is going to be tricky to make contributor-friendly. [https://bugzilla.mozilla.org/show_bug.cgi?id=392513]


* Need a way of tracking article requests/status without using Bugzilla. [https://bugzilla.mozilla.org/show_bug.cgi?id=398760]
* Need a way of tracking article requests/status without using Bugzilla. [https://bugzilla.mozilla.org/show_bug.cgi?id=398760]
1,365

edits