[Adium-devl] Version Control

[Chris Forsythe]

On Feb 6, 2008, at 5:58 AM, Evan Schoenberg wrote:

>
> On Feb 5, 2008, at 2:11 AM, Colin Barrett <timber at lava.net> wrote:
>
>> On Feb 4, 2008, at 9:43 PM, Evan Schoenberg wrote:
>>
>>> On Feb 4, 2008, at 1:55 PM, Augie Fackler wrote:
>>>
>>>> One question I have is do you want all commits to be with
>>>> @adiumx.com
>>>> addresses, or should we use something else?
>>>
>>> I think yes - but not because of a ridiculous security policy that
>>> "adiumx.com = trusted".  Rather, folks committing with authorization
>>> of the Adium project should do so using an @adiumx.com address to
>>> demonstrate clear affiliation.  This allows for the possibility at
>>> some point in the future of committers primarily associated with
>>> other
>>> projects or whose commits are distributed with the repository but  
>>> not
>>> part of an officially accepted changeset.
>>
>> I think that's very confusing and non-obvious.
>>
>> I don't understand your use case -- if they are distributed with
>> "adium-central", how are they not officially accepted? If we get into
>> that situation, people can publish their own clones, I guess? I'm
>> really not sure what you're talking about.
>>
>
> Peter pointed out one use case - folks who might have commit access
> but have primary association with another organization, a difference
> we choose to make clear: a pidgin developer (with access, probably
> enforced only by verbal agreement, to the Purple plugin), an MIT
> person whose involvement is limited to Zephyr, etc...
>
> Another is for patches. I don't know about this system, but mtn allows
> the committee to specify a searate author for the change (the patch
> writer).  Making our affiliations clear keeps -that- clear.
>
> Another is for distributed vcs. This is what I was talking about
> before. A repo (say, by Apple, where they maintain a branch of Adium
> which uses iChat's backend for AIM) may have a branch be pushed to our
> rep with our permission. It's useful to tell at a glance that -these-
> changes came from outside while -those- were made by an Adiym  
> developer.
>
> On the other hand, I see no disadvantages. What do you see?

I like this kind of thing. It's not a big deal either way, and some  
form of uniformity allows for nice things like this.

Plus everyone who commits gets an email, and those are useful.

Chris