Re: I should maybe point out here..

On Thu, Sep 09, 2004 at 06:39:15PM +0100, Steph wrote: > Following a discussion with Pierre on irc, it seems there's no > consensus at the PEAR end about the extra info fields anyway > Martin and I have provided our opinions here on the record. You're > willing to go the route of integrating the data into the existing pear > account user interface. So, this seems like the route to go. If > Pierre disagrees, he should speak up here, on the record, and try to > convince us that it's a bad idea or he has a better idea. I disagree. The php.net policy never allowed such datas in the user database, and obviously never allowed to transmit such things. The fields I would like to drop: occupation varchar(255) default NULL, currentjob varchar(255) default NULL, available tinyint(1) default NULL, certified enum('no', 'PHP 4','PHP 5') NOT NULL default 'no', Each user can set his homepage URL. They are free to put whatever they like there. *.php.net is not a jobseeker/hunter site, we provide php related informations and tools, that's all and enough. My 2nd concern is about privacy and relations with commercial companies. For these 2 points, I move the discussion to pear-group, this is our role to discuss such things. Sorry Steph, nothing personnal against you or Zend, I only try to avoid weird situations to raise in the future. Zend asked for this data, what's when other companies would like to get the same? with customs datas? How can we be sure that this data will never be published, sold or used for marketing purposes? I asked many people as well around me, most of them being also involved in php (locally or php itself), their answers and oppinions makes me think I'm right to worry about the possible usages of such datas. And for the record, "Martin and I have provided our opinions here on the record." From when you and Martin are allowed to take such decisions? The rule is to submit such administrative decisions to the group. Please follow it. Regards, --Pierre