Hi everyone, awesome work, Anne-Marie, thanks for that!
On Fri, May 11, 2012 at 8:00 PM, Anne-Marie Mahfouf <[email protected]> wrote: > Hi all, > > Here is I hope a summary of the tasks we're aiming for the next 4.9 release. > Current wiki pages: > http://community.kde.org/Getinvolved/Testing > http://community.kde.org/Getinvolved/Testing/Brainstorming > > Don't forget that you can use https://trello.com/kdetesting (ask Myriam or > me for account) Either by mail or on IRC, I am usually around in #kde-quality, just ping me ... > 2) Make bugs.kde.org ready for testers: annma submitted a sysadmin bugreport > https://bugs.kde.org/show_bug.cgi?id=299703 > Explain this to testers in the bigzilla training stage Sysadmin bugs are usually private and not accessible to other people, shouldn't you have filed a bug against b.k.o instead? So unless this bug is made public no-one can access and subscribe to it but the sysadmins and you. > > 3) Write Dot Article http://quality.notes.kde.org/1 opened to everyone > should be published the 29th May > Write blogs from May 30th and afterwards Tell me if you need help for that article > > 4) Bugzilla training: who? > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting (has some Kubuntu specific > parts, but the topic "how to write good reports" is still valid) > http://aseigo.blogspot.co.uk/2009/01/bugskdeorg.html > http://itscommonsensestupid.blogspot.co.uk/2008/07/tips-to-write-good-bug-report.html > Martin's blogs > http://blog.martin-graesslin.com/blog/2012/04/blog-series-bugs-kde-org-for-developers/ > Myriam's blog: > http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/ I can help with that > 5) Contact distributions: annma => setup a wiki page with informations about > this beata packages and how to install. > Current situation: > Slackware: > The packages will be obtainable at http://alien.slackbook.org/ktown/ > The instructions for usage will be posted on > http://alien.slackbook.org/blog/ > Arch Linux: > A dedicated [kde-unstable] repository. This repo only > contains KDE/Calligra beta releases (and their unstable deps); when the > stable > version is out, the packages are removed. > Installation steps are at: > https://wiki.archlinux.org/index.php/KDE#Official_kde-unstable > and https://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users > Fedora: there is an unofficial kde-unstable/kde-testing and > a kde-stable repo maintained by Rex Dieter - the place where the newest > bits come for already released stuff. But Fedora Rawhide is always the > first place for all builds. > Gentoo: provides scm versions (ebuilds) for master/trunk & stable branch, > betas > and rc's in an extra repository (overlay). Detailed install instructions can > be found here: > http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml Kubuntu: there is a beta PPA maintained by the Kubuntu developers: https://launchpad.net/~kubuntu-ppa/+archive/beta Right now it is inactive as there are no recent beta versions, but you can already add it to your sources list and un-comment it. I will ask Jonathan (in Cc:) to get it ready in time for the beta release. Have an eye on http://kubuntu.org/news for the beta package availability > 6) IRC based "bug squashing days": do we want to propose some dates for > that. I think we need to have people on IRC in #kde-quality and #kde-bugs on > May 29th, 30th and maybe we can set the next week-end as formal "bug > week-end" (that would be 2 and 3rd June) > To do in coordination with the current bugsquad (write them a mail). Who? > https://mail.kde.org/mailman/listinfo/bugsquad Most triagers are available in #kde-bugs on a regular basis. For specific bug days the developers of the project should be around as well, or at least somebody knowing the application well enough to give a hand when questions arise. I can handle that, except I will not be around on the 1st June weekend as I have a German FSFE meeting. > > 7) Logo for the Quality Team? > For blogs Can we ask Eugene? That would be great to have, yes! > > 8) Rewards for Testers? > Good incentive and would make people feel part of the community. > See > http://community.kde.org/Getinvolved/Testing/Brainstorming#Personalized_Thank_You_Letter > and > http://community.kde.org/Getinvolved/Testing/Brainstorming#Competition_For_Best_Bug_Reporters Again my question: how do we measure that?It seems quite difficult and rather arbitrary to me. Since we want a Testing Team logo, could we also have badges for distinguished helpers? Regards, Myriam. -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
