Changes between Version 51 and Version 52 of PLATFORM_STANDARDS_GENERAL


Ignore:
Timestamp:
11/04/08 13:19:23 (17 years ago)
Author:
todor
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PLATFORM_STANDARDS_GENERAL

    v51 v52  
    3737These should be linked into the Implementation section. If needed, additional wiki pages should be created and linked as TASK_NAME/PART where PART should describe the containing of this wiki page. 
    3838In different revisions same results can be linked, but revision result should be described. 
     39= Naming conventions for wiki pages = 
     40It looks like we need to specify the naming convention for the wiki 
     41pages explicitly. Here is what I propose for now. 
     42 * Pages for tasks are written in UPPER_CASE (as the task id). Like "PLATFORM_NFR_USABILITY_R0". 
     43 * If the result of the task is a wiki page, nice candidate for this page is the task name (without the revision). E.g. "PLATFORM_NFR_USABILITY". 
     44 * If the result of the task consists of several wiki page, then the "/" convention for trac sub-pages can be used. E.g. "PLATFORM_NFR_USABILITY/Commons", "PLATFORM_NFR_USABILITY/SuperSpecific", etc. 
     45 * When a page, is not directly related to a task (like the Commons in this example) it is named in the usual (CamelCase). 
     46 * In rare cases, we may create pages, that do not relate to a specific schedule item. They should be also named in CamelCase, but creation of such pages should be discussed with the leader.