Re: Re: An alternate view of PEAR QA, so what?

From: Date: Mon, 26 Jan 2004 14:38:59 +0000
Subject: Re: Re: An alternate view of PEAR QA, so what?
References: 1 2 3 4  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-405@lists.php.net to get a copy of this message
On Mon, 26 Jan 2004 15:35:02 +0100 (CET) "Tobias Schlitt" <tobias@schlitt.info> wrote: > I guess the optimal processes and access rights will become clearer, > announcment of the PEAR group:"The group's first task is to regulate > itself." So, that would be the first task for the QA group, too. That is exactly what I said. Thanks for the reminder :) And here it is again: 1. Set the team 2. The team writes some RFC regarding their taks/processes 3. We (peardev, group) valid them, again the whole things can change. We have to be flexible on this point. > IMHO it is not so dangerouse to grant cvs and pearweb admin access to > a number of 3-5 selected QA core members, to enable them to react > fast. Are there objections against that? I fully follow Jon's point of view on this topic. That means there is no need to have a full access to pearweb. > A problem I currently see, is that there are 3 willing guys to take > that part of the job, but all 3 are from Germany... :) Don't know, if > there are objections from the PEAR group or generally the community > side. who is the third? I read Bertrand is interested too. > Maybe it's a good idea to place a QA group as acting, with the > condition to increase their member count from 3 to 5 people, as soon > as there are any appliers, esteemed to fit into that group. Well, I like to wait a bit more and see what will happen. For now I would like to know the QA members, regardless about the core team or not. And, as a good showcase, PEAR 1.3b6 is out. Any of you has already tested it? pierre

« previous php.pear.qa (#405) next »