Setting up a Quality Team within KDE

Aleix Pol aleixpol at
Fri Apr 6 13:23:17 BST 2012

On Thu, Apr 5, 2012 at 1:42 PM, Anne-Marie Mahfouf
<annemarie.mahfouf at> wrote:
> Hi,
> We would like to setup a Quality Testing Team within KDE in order to better
> test our next KDE SC and make the beta process more efficient.
> Attached is the first draft of the ideas I brainstormed. Source .odt of this
> document is available at
> (We can make it a public Google doc if it is more convenient or an
> etherpad).
> The document roughly describes 2 areas of action:
> - reinforcement (labelled "Reinforce") of existing structures (mainly
> targetted to developers and mainly relevant before the beta stage of the
> release). This could
> be used as guidelines for new developers. Of course it won't be newbies
> which will develop Unit Tests or check the code quality. But some guidelines
> can
> be useful for libs outside Frameworks.
> An area of relevant reinforcement that can be currently done is the Review
> process for new integration.
> - new infra-structures: this is labelled "New" in the doc: this is what I
> would see to happen for the 4.9 release.
> A new mailing list has been set up in order to discuss all this: please
> subscribe to it if you would like to be part of this
> An IRC channel also was created on Freenode:
> #kde-quality
> Please join the mailing list and the IRC channel so we can setup a plan to
> start putting all this in gear!
> Thanks in advance,
> Anne-Marie and Myriam

I think this project is a very interesting idea and definitely
something we need. Said that, I'd like to propose some small changes
on how this should be done.

In the document there are some actions to be taken that sound a bit
too technical, for example it specifies reinforcing the unit testing.
This is something that we should have been doing already and I don't
see someone from the Quality Team going to a development team and
improving that.

What I'd like to see is this new team testing KDE and its applications
from a user perspective, specifying the different perspectives the KDE
end user will face (different OS, different form factors, etc) and
reporting problems (not necessarily bugs, as in crashes) and proposing
new solutions.

I'm really hopeful about such a team, I think it's a good opportunity
for KDE to be able to reach contributions for a less common sector of
our community and keep working together for a greater KDE experience.


More information about the kde-core-devel mailing list