RE: [PHP-QA] List Idea

Sounds like we have some real good ideas. Let me know what I can do. Jason > -----Original Message----- > From: Zak Greant [mailto:zak@nucleus.com] > Sent: Friday, June 30, 2000 2:47 PM > To: php-qa@lists.php.net > Subject: Re: [PHP-QA] List Idea > > > Hello All, > > As several people have pointed out, one of the first needs that > we have it > to be able to keep track of the QA team members that are > available for testing. > > I have reviewed waldschrott's excellent suggestions and have prepared a > more complete list of features and functions for the QA team > member tracker. > > Please let me know what you think. > > > QA Team Manager > --------------- > The application would be built using PHP and MySQL. (Of course) > > Here is the initial feature list: > - allow testers to enter in basic contact information > > - allow the testers to change their user details in an password > protected > area. > > - allow testers to set their status - they can choose to be listed as: > - active: meaning that they are eagerly awaiting new tasks :) > - on call: meaning that are available to accept a task if > others are busy > or their particular skills are needed > - inactive: meaning that they are not currently accepting new tasks > > - allow developers to view tester information > > - allow testers to define the platforms that they are testing on. > - the tables that support platform information is organized > in a simple > modular fashion. > Each part that makes up a platform (like the OS, server > software, php, > etc...) is a separate component in the platform_details table. > > The components in the platform_detail table are organized into a > 'platform' in the link_dev_to_platform table. Testers will be able to > create multiple platforms. > > This structure, when combined with a few handy editors, should help > testers quickly and accurately define their platforms. This should also > cut down the amount of data entry required. Once someone has > entered their > platform, it is a simple task to update or change a few details. > > Here are the basic tables that I was planning on using. > > create table developer > ( > id int unsigned not null > auto_increment primary key, > handle char (12) not null, > password char (12) not null, > name char (64) not null, > email char (255) not null, > status enum ('active','on > call','inactive') not null > ) > > create table link_dev_to_platform > ( > developer int unsigned not null primary key, > group_name char (12) not null, > platform_detail int unsigned not null > ) > > create table platform_detail > ( > id int unsigned not null > auto_increment primary key, > type enum('Apache Module','Hardware > Details','Operating System','Other > Software','Perl','PHP','PHP Module','Server') not > null, > name char(64) not null, > vartype char(64) not null, > version char(64) not null, > language char(64) not null, > notes text not null > ) > > Ciao, > Zak Greant > Creative Director > Nucleus Information Service Inc. > > "A camel is a horse designed by a committee." > - Alex Issigonis (Designer of the Mini) > > > -- > PHP Quality Assurance Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-qa-unsubscribe@lists.php.net > For additional commands, e-mail: php-qa-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > _______________________________________________________ Site Design, Hosting, and E-Commerce at www.webpipe.net