Re: Re: PHP|QA Member Names in phpinfo()

> I believe that this is partially my fault - my contribution is at > times ineffective and poorly organized. If leadership in the open > source community is by example, then my example has been well- > intentioned, but otherwise poor. On the contrary, I think your contributions have always been effective and well-organized! On the rare occasions that you were "absent" you informed everybody well in advance, and have been there pushing regularly. Jeez, you even remembered to resurrect that thread about re-naming functions after the insanity of a release gave us breathing room. That's just one perfect example of *many* where you've excelled. > I think that everyone's hope for the QA team was to have a dedicated > group of people working individually or in small teams on tackling the > problems involved in creating and maintaining an effective QA process > for PHP. Some people do this - they take on one or more aspects of QA > and devote time to it regularly. I feel that others like the idea of > being part of the QA team, but rarely respond when the call goes out > for help, feedback or testing. That is the nature of the beast. Just be happy it's not like hanging flyers for a music gig where about 1,000 flyers turns into 1 attendee. :-) More seriously, I think the QA team has made excellent progress -- integration into the release process with the PHP Developers and a more reasonable timeline for that process is probably the only "major" obstacle at this point. Even that, I think, might be more of a dream than a goal: A little tweaking of the process and a couple days for QA can happen, but a couple days isn't really enough, with the resources at hand, for a true QA. Still, this has been a major step in the right direction, and as it proves its success there will be more volunteers, and more structure for those volunteers to meaningfully contribute. On that note -- the "who's testing what application" and the Bug-tracking application are probably the best projects for the QA team to focus on, right after integration with PHP-Dev release cycle. A lot of the pieces and infrastructure are still in progress, but I, for one, really believe this has been extremely effective and will be even more so as time goes by. > I know that everyone involved in this is a volunteer and that work, > family, sanity and leisure have to come first - however, staying up to > date with the QA team can be a pretty trivial investment of time. At *least* reading the list and either responding or losing your "bitching rights" [not that I thought anybody was bitching in the first place!] sounds like a very reasonable requirement to me. And certainly for inclusion in phpinfo() under PHP|QA. Inclusion elsewhere in phpinfo() is really not within the pervue of this forum, IMHO. -- Visit the Zend Store at http://www.zend.com/store/ Wanna help me out? Like Music? Buy a CD: http://l-i-e.com/artists.htm Volunteer a little time: http://chatmusic.com/volunteer.htm