Agree, and all handset test reports have been restructured like: http://wiki.meego.com/Quality/HandsetTestReport/UXWeekly20100706
Thanks, Fan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Yu, Jerry Sent: Wednesday, July 14, 2010 9:40 AM To: [email protected] Subject: Re: [MeeGo-dev] QA guys: Wiki clutter? Agree with you all for the wiki pages layout suggestion! Since the portal page for QA stuff is http://wiki.meego.com/Quality We will struct the test report archive like: http://wiki.meego.com/Quality/CoreTestReports where will only highlight the latest 5 weekly reports. http://wiki.meego.com/Quality/CoreTestReports/weekly20100709 Thanks! Jerry ------------------------------ > >Message: 22 >Date: Tue, 13 Jul 2010 17:39:10 +0200 >From: Carsten Munk <[email protected]> >To: meego-dev <[email protected]> >Subject: [MeeGo-dev] QA guys: Wiki clutter? >Message-ID: > <[email protected]> >Content-Type: text/plain; charset=ISO-8859-1 > >Hi QA guys, > >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. > >Thank you in advance, >Carsten Munk > > >------------------------------ > >Message: 23 >Date: Tue, 13 Jul 2010 09:07:52 -0700 >From: "Foster, Dawn M" <[email protected]> >To: "Development for the MeeGo Project (discussion list)" > <[email protected]> >Subject: Re: [MeeGo-dev] QA guys: Wiki clutter? >Message-ID: <[email protected]> >Content-Type: text/plain; charset="us-ascii" > > >On Jul 13, 2010, at 8:39 AM, Carsten Munk wrote: > >> >> 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. >> > >In particular, pages like this one: http://wiki.meego.com/Editing create >confusion, since it >isn't clear whether this refers to the wiki in general or some sub-team in >MeeGo. Based on >the page content, I'm assuming it is QA. > >It would be very helpful if all of the QA pages were something more like >http://wiki.meego.com/QA/Editing > >We have some additional guidelines that cover wiki naming and more here: >http://wiki.meego.com/Wiki_contribution_guidelines > >A good example of best practices is the Release Engineering team. Examples: >http://wiki.meego.com/Release_Engineering >http://wiki.meego.com/Release_Engineering/Release_Timeline >http://wiki.meego.com/Release_Engineering/Process > >The main Release Engineering page has team members, summaries and links to key >pages. Their pages are clearly named, which makes it easy for people to >understand the >purpose of the page at a glance. > >Regards, >Dawn > > > >------------------------------ > >Message: 24 >Date: Tue, 13 Jul 2010 18:13:53 +0200 >From: Dave Neary <[email protected]> >To: "Development for the MeeGo Project (discussion list)" > <[email protected]> >Subject: Re: [MeeGo-dev] QA guys: Wiki clutter? >Message-ID: <[email protected]> >Content-Type: text/plain; charset=ISO-8859-1 > >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] > > > >------------------------------ > >Message: 25 >Date: Tue, 13 Jul 2010 09:33:49 -0700 >From: "Foster, Dawn M" <[email protected]> >To: "Development for the MeeGo Project (discussion list)" > <[email protected]> >Subject: Re: [MeeGo-dev] QA guys: Wiki clutter? >Message-ID: <[email protected]> >Content-Type: text/plain; charset="us-ascii" > >On Jul 13, 2010, at 9:13 AM, Dave Neary wrote: > >> >> 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 >... > >We should probably use Quality Assurance or QA instead of testing team to keep >things >consistent with the naming of teams on the governance page: >http://meego.com/about/governance/quality-assurance > >> >> 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. >> > >This is a very good suggestion. Keep in mind that since the wiki keeps a >history of previous >edits, you might be able to keep your reports grouped on a single page. Here's >an >example: > >Title: QA/Core testing reports >Subheadings for each week's report: Core testing report 20100709 >You could keep the most recent 5 reports on that page, and just delete the >older ones >from the page. The "deleted" content would still exist in the history for >viewing. > >The you would have fewer pages, and it would be easier to find the information. > >Regards, >Dawn > > > >------------------------------ > >_______________________________________________ >MeeGo-dev mailing list >[email protected] >http://lists.meego.com/listinfo/meego-dev > > >End of MeeGo-dev Digest, Vol 6, Issue 14 >**************************************** _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
