KDE Herd Testers Project Team

Jorge Vicetto  Author
Stefan Schweizer  Author
Tobias Heinlein  Contributor

Updated December 9, 2007

1.  Introduction

As defined by GLEP 41, an HT is a trustworthy user who is able to help with testing packages, identifying issues and finding fixes.

2.  What you get

All HTs receive a /gentoo/contributor/${NAME} IRC cloak, are added to the "Arch/Herd Tester" group on the Gentoo forums, get auto-voice in #gentoo-kde, are added to the kde@gentoo.org mail alias and are assigned editbugs privileges on the Gentoo Bugzilla.

3.  What to do

HTs usually test packages, provide guidance on bug reports, communicate with the KDE team through the team's IRC channel (#gentoo-kde) and mail to the kde@gentoo.org mail alias. HTs are also invited to help users on forums, mailing lists and IRC channels.

4.  Requirements

We expect people to do good testing, show good knowledge about Gentoo in general and to be active (taking into account RL constraints).

5.  Participating

If you think your comments and patches submitted to Bugzilla and willingness to help other users on IRC, mailinglists and/or forums justifies HT status you can talk to the KDE herd. Users will also be invited to become HTs by members of the KDE herd that notice their work, abilities and desire to help the KDE herd.

To become an HT, the user will have to complete the ebuild quiz and have a review session with the AT lead (hparker).

Interested users should read the Gentoo Development Guide/DevManual and the Gentoo Developer Handbook and should work with the other members of the herd to address the questions on the quiz. The KDE HT lead will work closely with all HTs, helping them prepare for the quiz and the interview, and will coordinate their work on the herd.