From: Evan S. <ev...@dr...> - 2006-10-30 12:06:29
|
Quoting Mark Doliner <ma...@ki...>: > I'm probably in the minority, and I'll probably be overruled, but I > don't like > requiring users to register in order to file bugs, patches, leave > comments, or > modify the wiki. I think it discourages people from contributing, > and creates > a less-friendly culture. I think the barrier to entry should be as low as > possible. A barrier to entry as low as possible leads to sloppy bug reporting, unfortunately. Registration as implemented by Trac w/ AccountManager doesn't require an email address, email confirmation, or any of that; it's literally a 2-click process with immediate access granted. Registration also allows association of an email address with a user name in a non-publically-viewable way so that Trac can send email notifications of changes *without* requiring users to disclose their email publically. > I know Adium had problems with spam on their trac. My best suggestion for > counteracting that is to place a .htpasswd restriction over our entire trac > with a username/password of "gaimtrac/gaimtrac" or something, and put the > username in the auth message that prompts for the username and password. Our initial solution was to just use the Trac antispam measures. They're better than nothing... and not nearly sufficient. We were still overwhelmed by spam. Our next solution was precisely what you describe: username/password 'adium'. There are at least 2 problems with this. 1) Users are then forced, as of Trac 0.10 and later, to list their name as 'adium'. There's absolutely no accountability for bug reports, no ability to contact the user to find out more unless he puts his name in the report itself, etc. It's ugly in addition to nonfunctional. 2) Email change notifications are impossible. I strongly recommend against that solution - it sounded attractive to me before we implemented it, but experience showed it to be really suboptimal. |