|
From: Egon W. <eg...@us...> - 2005-06-13 14:09:43
|
On Wednesday 1 June 2005 11:32, Egon Willighagen wrote:
> are three people interested in setting up a quality-assurrance team? A team
> that ensures that the quality of CDK is OK?
There seems to be critical mass to set this up. I've setup a mailing list [1]
for getting things organized.
What needs to done, IMHO, is this:
- subscribe to cdk...@li...
- define someone who is to lead this endeavor
this basically involves being the one people can ask questions on the
project and who will overlook what's being done within the QA project,
maintain a list of team members, and make sure that a realistic list
of things-to-do is written down
- setup a QA team
being a team member will mean that you participate in discussions
and/or do practical QA work
- setup a QA-task report mechanism
to make sure test results don't get lost, QA test results should be
reported in a proper way. The report should likely include a proper
description of what the test project is about, who is involved, what
source code was used, and, obviously, the results.
As CDK News editor I welcome such reports to be published in CDK News.
- setup a list of things to do
it will totally be up to the team to see what they want to do, and
QA team members can define tasks they want to do and propose
this on the list
To make a few things clear:
- giving other things I'm working on I can be team member but not project
leader
- the actual amount of work is totally up to the team itself; the team leader
just tries to organize all QA work done within the CDK project (and some work
has already be done), and tries to ensure that results are reported back to
the CDK project in some way
- the leader may chose whatever option to reduce the work he has to do :),
just as long as he is the (after the QA mailing list) a personal to go to for
information
Egon
1. http://lists.sourceforge.net/lists/listinfo/cdk-qassurance
--
eg...@us...
GPG: 1024D/D6336BA6
|