[Adium-devl] Gearing up for SoC

[David Smith]

Accidentally sent this to Chris instead of Adium-Devl. Sorry for the  
dupe-spam, Chris.

On Apr 24, 2006, at 2:06 PM, Christopher Forsythe wrote:

>
> 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.
Unlikely. We'd probably review the branch as a whole. Easier to just  
co it and try it out, then to co trunk, merge a ginormous patch, and  
then try it. Once we know it works, we can figure out how to merge.

									David