[Adium-devl] Gearing up for SoC

Christopher Forsythe chris at growl.info
Mon Apr 24 21:06:57 UTC 2006


On Apr 24, 2006, at 3:58 PM, Colin Barrett wrote:

> On Apr 24, 2006, at 4:49 PM, Christopher Forsythe wrote:
>
>> We should probably handle this like we handle patches from anyone  
>> else.
>>
>> On Apr 24, 2006, at 6:37 AM, Colin Barrett wrote:
>>
>>>   - Should we give them their own branch, all branched from the same
>>> r? We should consider how we're gonna handle that (e.g. externals,
>>> merging back in, etc).
>>
>
> Really? I know Gaim gave people branches. Patches are annoying to  
> use for large changes, and that's what they're going to be doing.  
> Imagine if we had to manage everything in Adium by hand with a  
> bunch of patch files.

I don't see the point of giving them commit without giving them  
access to trunk though. We have source control for a reason. The only  
reason I said patches was because I was under the impression from  
your original post there that we should keep their stuff separate,  
but if your reasoning is to keep it separate but easy to maintain, I  
really don't see the point of a branch to be honest.

I also said patches because, even though we'd eventually either give  
them a branch, trunk access, or do this via patches, they'd probably  
still hand patches to folks for review. Now if you disagree with that  
point and think that it's not worth the time of the developers to  
review patches, then what's the point of a branch either? At that  
point we might as well just give them trunk and be done with it, and  
if anything blows up we can revert it.

Chris




More information about the devel mailing list