Hi all, Small reminder about the issue to this list as well (thanks Dave for the reminder at http://bugs.meego.com/show_bug.cgi?id=8690). It seems that there are still a lot of test reports in wiki. According to http://wiki.meego.com/Wiki_contribution_guidelines pages can be marked to be deleted by doing the following: "Place pages that you would like deleted in the "Die die die" category by adding this line to the page to be deleted: [[Category:Die die die]]"
I haven't noticed any comments regarding Jari's proposal about deleting all but the 6 latest test reports of each area. Could we now proceed with this? If we can proceed, I can help in marking the reports that I find to be deleted as described above but of course the actual testing teams could know better what to delete and what should be preserved so help might be needed in any case. The second issue mentioned below was about the naming of our wiki pages. The instructions can be found at http://wiki.meego.com/Wiki_contribution_guidelines#Style. Renaming already existing pages of course affect the current links but this shouldn't be too big issue when using re-direct. I can also help in this but I preferred not to start renaming other people's pages without a warning so please let me know if you'd like to have my help. There are some other issues with Quality wiki pages as well (e.g. too deep hierarchies Quality/Something/Something/Etc...) but we could start by doing these two first and follow the wiki contribution guidelines better when creating something new. Br, Arto ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, November 08, 2010 1:53 PM To: [email protected] Subject: [Meego-qa] MeeGo QA wiki gardening ... Hi all, Let's start to clean out Quality wiki area: - Delete old pages not needed anymore (I sent out question to meego-community for instructions how to do it - by moving pages somewhere or by "labeling" them some way) o I suppose we could clean all test reports from June, July, August and September. o for every test area (Acceptance, Sanity, ...) we could have only 6 latest test reports stored - Follow the naming according rules. E.g. for Handset UX Sanity on N900 test report one have either [[Quality/Reports/Handset N900 Sanity 20101108 | Handset-ARM-N900-Sanity Test Report for 20101108 ]] or [[Quality/Reports/handset-n900-sanity-20101108 | Handset-ARM-N900-Sanity Test Report for 20101108 ]] I suppose at the same time when doing all the other things one can also revise structure ... how do you feel about the following? o Quality/Plans * Summary (page where we are having explanations and links to pages in this "directory") * Core Test Plan * Handset Test Plan * Netbook Test Plan * IVI Test Plan * <project> test plan * <component> test plan * Could we have all templates and process related stuff also under this area? * .... o Quality/Reports * Summary (progress graphs for all of the testing) * Core OS QA Summary (progress graphs for Core OS testing) * Handset UX QA Summary (progress graphs for Handset Testing) * Netbook UX QA Summary (progress graphs for Netbook Testing) * IVI UX QA Summary (progress graphs for IVI Testing) * <project> QA Summary (progress graphs for <project> Testing) * <project> <HW> <Testing> <date/release> (few latest test reports available - maybe we can start with 6 latest ones) Individual test reports are not needed after qa-reports is fully in use · Quality/TestSuite o Test asset related pages here * Core OS Test Suite (current MCTS page) * Handset UX Test Suite * Netbook UX Test Suite * <project> test suite o Quality/QA-tools * Tooling related pages under this · Quality/Compliance o Compliance related stuff under this I'm wondering placing for bugzilla and bug management related documentation so please provide your opinion also for this. Please share your ideas and after short discussion just let's make it happen. I already started to do things last weekend according ideas presented here ... and will continue to do so if you are not saying stop. Br, Jari
_______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
