Hi, Carsten Munk wrote: > Would it be possible to restructure your reports such as: > > http://wiki.meego.com/Coreweekly20100709 > http://wiki.meego.com/Coreweekly20100702 > http://wiki.meego.com/AavaSanity20100713 > and so on? > > Would it be possible for you to use /'s in your wiki page names and > set up a structure/proper pattern. > > Such as /QA/Core/Weekly-20100709 or whatever structure that makes > sense. The current approach creates a lot of unstructured pages in the > main namespace and it clutters the wiki and does not show where the > pages belong to / which team / which work in MeeGo / etc.
I would suggest using names which follow the loose guidelines I put up in the wiki: http://wiki.meego.com/Wiki_contribution_guidelines That is: > * Page names should be short and to the point. > o The page name is a label, not a sentence. > o Use spaces. NoCamelCase (i.e., use "Root access" instead of "RootAccess"). > o Use sentence capitalization for page titles. Only proper nouns should be > capitalised after the first word (eg. Contributing to MeeGo is OK, > Contributing To The Wiki is not) > o When using sub-pages, please ensure that you are really grouping several > related pages under a common root. Deep hierarchies make for long names. As a > general rule, use no more than two levels for subpages (eg. Community > Office/Meetings is OK, Community Office/Meetings/Meeting minutes from May 11 > 2010 is not) > > For more information, see the Wikipedia Style Guide. I would suggest creating a "Testing team" page which could be used to collect report templates, document the testing team and its processes, and also collect all the test reports. Something like Testing team Testing team/Test report template Testing team/Sanity report template Testing team/Grouped report template Testing team/Core test suites (=MeeGo_Core_Test_Suites_Packaging_draft) Testing team/Core test suites development guidelines Testing team/Test plan Testing team/Test packaging Testing team/Weekly reports (collection of the following links) Testing team/Core testing report 20100702 Testing team/Core testing report 20100709 ... Testing team/Handset reports Testing team/Aava sanity test 20100713 Testing team/Aava sanity test 20100712 Testing team/Aava sanity test 20100711 Testing team/Aava sanity test 20100710 Testing team/Aava sanity test 20100709 Testing team/Aava sanity test 20100708 ... Testing team/UX report 20100706 Testing team/UX report 20100702 ... Testing team/Glossary (replaces "Quality Assurance Glossary QA Glossary") etc.... In general, if the testing team are going to be generating weekly test reports, then unless there is historical interest in keeping old test reports around, I would suggest that they be archived somewhere, and that only the latest test reports (and, perhaps, the last test results from a release to compare for regressions) be kept around. How does that sound? Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
