while <a href="mailto:account@fp.o">account@fp.o</a> is technically easier, <a href="mailto:first.last@fp.o">first.last@fp.o</a> looks better and is more professional. If we can keep it, I'd rather do!<br>A check for ASCII characters only + uniqueness might be all that's needed in the web app as suggested
<br><br><div><span class="gmail_quote">On 1/21/07, <b class="gmail_sendername">Elliot Lee</b> <<a href="mailto:sopwith@gmail.com">sopwith@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Jan 18, 2007, at 15:57 , Mike McGrath wrote:<br><br>> At present we provide two @<a href="http://fedoraproject.org">fedoraproject.org</a> addresses to everyone who<br>> has a fedoraproject account.<br>><br>
> <a href="mailto:account@fp.o">account@fp.o</a><br>> and<br>> <a href="mailto:first.last@fp.o">first.last@fp.o</a><br>><br>><br>> Notting pointed out that its only a matter of time before we have a<br>> collision in
first.last. Should we just get rid of it? I don't know<br>> of anyone using it.<br><br>Another possible solution - add a 'UNIQUE' constraint onto the<br>human_name field in the db...<br><br>Best,<br>-- Elliot
<br><br><br>_______________________________________________<br>Fedora-infrastructure-list mailing list<br><a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list">
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list</a><br></blockquote></div><br>