Re: [pear-webmaster] [PEAR-BUG] Req #2308 [Opn]: Either remove "email via web form" or add warning

Helgi Þormar <helgi@trance.is> wrote: > On Wed, 2004-10-20 at 19:58, Martin Jansen wrote: > > On Wed Oct 20, 2004 at 07:3613PM +0000, Helgi Þormar wrote: > > > On Wed, 2004-10-20 at 19:23, Martin Jansen wrote: > > > > -1. I don't see a reason why people shouldn't be able to contact PEAR > > > > developers about something. (Don't forget that people's email addresses > > > > are also available in *every* source file of *every* package.) > > > > > > That is true, and I truly hope that placing a big red warning like > > > Alexey proposed and also adding a checkbox which either has to be > > > checked or unchecked, that it will reduce straight support mails to the > > > devs and people will try pear-general first :-) > > > > If you ask me, I don't think it is necessary to complicate the process > > of reaching us: Personally I get very few of these "unsolicited support > > messages", and I usually just reply to the sender that she should ask on > > pear-general. I consider this to be much more friendly than alienating > > people with warnings et.al. > > Still don't see a reason why not point people to email pear-general, in > big red or not, lets just leave it at bold message in black with a > recommendation to email pear-general rather if it's a support request, > that shouldn't make it more complicated I'd think nor less friendly, > what do you think about that approach ? Sounds reasonable to me. However, I would really appreciate it if people who are logged in get to see the email address even if the dev opted not to make the email address public. It certainly would not be public, and abuse would be unlikely. As Martin pointed out, the emails are in the headers of every file, so it's not a privacy concern. This should be in addition to a form, of course. Imho, a form should be displayed regardless of whether the dev's address is public or not. (Don't know that it isn't that way already, but if it's not, it should be :) After seeing the bug comment spam, I think it might not be a bad idea to put captcha in there for submitting the email-a-dev form, too. Just my 2cts Klaus