Changes between Version 66 and Version 67 of PLATFORM_STANDARDS_GENERAL


Ignore:
Timestamp:
01/29/09 14:04:15 (12 years ago)
Author:
boyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PLATFORM_STANDARDS_GENERAL

    v66 v67  
    106106All reviews should be motivated. A detailed comment about why a task phase fails is required. For a score of 3 a list of things that have to be improved/added should be provided. Comments are encouraged for higher scores as well. Non-integer scores are STRONGLY disencouraged. If you give a task a score of 3.5, then you probably have not reviewed it thoroughly enough and cannot clearly state whether it is good or not. Once a given phase has been reviewed, it cannot be altered. If you think it is wrong, you should request a super review. Currently all super reviews should be discussed with Milo. Make sure you are able to provide clear arguments of what is wrong before you request a super review. 
    107107 
     108== Naming conventions for wiki pages == 
     109When creating a new wiki page, comply with the following conventions: 
     110 * Pages for tasks are written in UPPER_CASE (as the task id). Example: PLATFORM_NFR_USABILITY_R0. 
     111 * If the result of the task is a wiki page, it should be named like the task but without the revision. Example: PLATFORM_NFR_USABILITY. 
     112 * If the result of the task consists of several wiki pages, then the subpages should be created. Example: PLATFORM_NFR_USABILITY/Commons, PLATFORM_NFR_USABILITY/SuperSpecific, etc. 
     113 * When a page is not directly related to a task it is named in CamelCase. Example: ImportantDocs 
     114 
    108115== Other standards == 
    109116This document provides only general rules. For specific ones, take a look at:[[BR]] 
     
    114121[wiki:PLATFORM_STANDARDS_MANUAL_TESTS][[BR]] 
    115122 
    116 == Naming conventions for wiki pages == 
    117 When creating a new wiki page, comply with the following conventions: 
    118  * Pages for tasks are written in UPPER_CASE (as the task id). Example: PLATFORM_NFR_USABILITY_R0. 
    119  * If the result of the task is a wiki page, it should be named like the task but without the revision. Example: PLATFORM_NFR_USABILITY. 
    120  * If the result of the task consists of several wiki pages, then the subpages should be created. Example: PLATFORM_NFR_USABILITY/Commons, PLATFORM_NFR_USABILITY/SuperSpecific, etc. 
    121  * When a page is not directly related to a task it is named in CamelCase. Example: ImportantDocs 
    122  
    123123= Comments = 
    124124 ^Your comment here --developer-id@YYYY-MM-DD