[Adium-devl] Version Control

[Peter Hosey]

On Feb 06, 2008, at 21:00:02, Chris Forsythe wrote:
> Can hg for instance save a username per hostname in the global  
> config file?

No.

> Is this even a problem?

No.

Really, hg doesn't seem to require us to use email addresses at all.  
hg seems to be just fine with the username field being only a name,  
not an email address.

So two questions stand:

1. Do we need email addresses?
2. If 1, why should these email addresses be @adiumx.com/@pidgin.im?

The answer to question 1 is mostly yes: Names are not enough to  
identify people. There are many sets of humans with the exact same  
name. We use usernames with SVN, but usernames don't scale to the  
DVCS world, where anybody can pick and use their own username.  
(Imagine if somebody named Charlie Barrett sends us a patch.) Email  
addresses work as an identifier.

As for question 2, I can think of one concrete reason to have project- 
identifying email addresses: Evan.

Evan, as Colin noted, works on both Adium and Pidgin. So, if he  
commits+pushes something to Pidgin's hypothetical hg repository, he  
would use his @pidgin.im address; when he pulls it into Adium's repo,  
it will keep that address, and we'll know that he committed it as a  
Pidgin developer. When he commits+pushes directly to Adium, he'd use  
his @adiumx.com address, and we'll know that he committed it as an  
Adium developer.

More generally, a project-identifying email address clearly says at a  
glance that the committer is or is not affiliated with our project or  
Pidgin. We don't even need to look at the username: if the domain is  
either adiumx.com or pidgin.im, it's an official patch; otherwise,  
it's a user-submitted patch.

Are there any other answers, whether they agree with mine or not?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20080206/16c378a6/attachment.sig>