<div class="gmail_quote"><br>
<div>I believe in informed opt-in. Publishing e-mail addresses without explicit consent is a bad choice and it is arguably a violation of OLPC Privacy Policy <a href="http://wiki.laptop.org/go/OLPC:Privacy_policy" target="_blank">http://wiki.laptop.org/go/OLPC:Privacy_policy</a></div>
<div> </div>
<div>"All user data that is not made public, including email addresses and IPs associated with user accounts, will not be shared with outside parties for any reason unless compelled by law. OLPC does not keep machine logs any longer than necessary to maintain the site."</div>
<div> </div>
<div>You might say that it is not clear that the wiki privacy policy applies to Pootle server, but that is splitting hairs and likely to make people feel like they have been lied to and then go away mad. For me, it has little to do with privacy <em>per se</em>, my "real-world" identity is easy enough to discover by following links on my wiki user page. It is however important to me that organizations with which I do business state their privacy policies and adhere to them scrupulously, even to the point of their own inconvenience.</div>
<div> </div>
<div>Obviously, many of us accept that by posting to an open and archived list, our e-mail address will be come discoverable, even harvestable by a spammer. For that reason (among others) some of us go through the inconvenience of employing a web-mail address (adding a few steps to the e-mail process) in order to leverage Google's investment in anti-spam technology and in a worst-case scenario, to have the ability to abandon the address entirely. There is no real point in making arguments about how effective or ineffective such a strategy may be, in this case, I think OLPC's policy is clear enough that just posting e-mail addresses is NOT an option.</div>
<div> </div>
<div>IMHO, it is however perfectly acceptable for the Pootle administrator to send a mass-mailing (names in BCC-field, not CC) reminding everyone registered on Pootle to create a wiki-user-page and add themselves to the Pootle wikipage, therefore making them available via wiki-mail. Mokurai's idea of automating the provision of a wiki-user-page for Pootle users (wiki-mail link doesn't expose e-mail address) also seems within bounds to me, if you can figure out how to make it happen technically.<br>
</div>
<div>cjl</div>
<div>
<div></div>
<div class="Wj3C7c">
<div><br> </div>
<div class="gmail_quote">On Mon, May 26, 2008 at 11:01 AM, Sayamindu Dasgupta <<a href="mailto:sayamindu@gmail.com" target="_blank">sayamindu@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi all,<br>A number of people have been asking for ways in which they can get in<br>touch with team members of a particular language, and currently the<br>
only way in which this can be done is to go through me (or use the<br>wiki, which is not often always updated).<br>I have been playing with a few python scripts which can generate pages<br>like <a href="http://l10n.gnome.org/teams/" target="_blank">http://l10n.gnome.org/teams/</a> from the Pootle user database, which<br>
can be used by potential and existing translators to get in touch with<br>their team members.<br>The only issue that has been worrying me is the issue of email<br>addresses. While I'll definitely use some minimalistic anti-spam<br>
measures like foo at bar dot com, do you think it is OK for us to show<br>the contributor emails publicly on the website ?<br>Thanks,<br>Sayamindu<br><font color="#888888"><br><br>--<br>Sayamindu Dasgupta<br>[<a href="http://sayamindu.randomink.org/ramblings" target="_blank">http://sayamindu.randomink.org/ramblings</a>]<br>
_______________________________________________<br>Localization mailing list<br><a href="mailto:Localization@lists.laptop.org" target="_blank">Localization@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/localization" target="_blank">http://lists.laptop.org/listinfo/localization</a><br>
</font></blockquote></div><br></div></div></div><br>