On Tue, 2008-09-16 at 10:39 +0200, Samuel Murray (Groenkloof) wrote: > G'day everyone > > I wish to address the following three issues from my previous mail: > > > The assumption is that the e-mail address a user uses for contact with > > Pootle will be the same e-mail address he wants to use for attribution > > in the PO file (assuming he is aware of the attribution). > > > What's more, many people munge their addresses in PO headers... > > > Another somewhat related problem I have, is that there is no mechanism > > for users to contact each other. > > Currently, the registration page and the profile page (options.html) > contain fields for the Name, Email, Password and Confirm password. I > propose that two extra fields be added to it: > > * Display Name (used for attribution purposes): > [________________] > > * Address where other users may contact me: > [________________] > > When a user registers, the above two fields are filled in automatically > (using JavaScript, I think) after the user has typed in his name and > e-mail address (although users can change/delete them). > > The autogenerated display name should contain the user's name and munged > mail address. So if his name is Joe Soap and his mail address is > [EMAIL PROTECTED], the autogenerated Display Name would be: > > Joe Soap <joe[at]soap[dot]com> > > The autogenerated name where a user wants to be contacted, should be the > same as his display name, but not munged (so that it can easily be > imported into a mail program): > > Joe Soap <[EMAIL PROTECTED]> > > Of course, the user can remove and/or change these entries if he wants > to, but by default they are entered, and if the user clicks "Register", > he automatically gives permission that the information be used as stated. > > I don't know what is the best way to store this information, but at > least the name/address where a user can be contacted should be stored in > a separate file that can easily be downloaded as-is by anyone with read > access to the server-side, so that project administrators can use the > information (eg to introduce translators to each other, or to send a > newsletter to translators). > > Your thoughts?
I think we're making this way too complicated for an issue that I think can be got around by the user themselves. If they want to work in secret, register on Pootle as a secret user. I'm in favour of munging email addresses for people who fear spam. And I think we can simply do that automatically without making many confusing options. The last item of a list of email addresses, that should become simpler as we move to a database. I'd rather look at that after 1.2 but it can be done with a simple script that can read the users.prefs file if someone wants to give it a go. -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * The birth of the GNU generation http://www.translate.org.za/blogs/dwayne/en/content/birth-gnu-generation * Firefox users experience discrimination * RPM packages for py lib 0.9.2 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
