On Aug 23, 2009, at 18:03, John Owens wrote:
> Ryan Schmidt writes:
>
>> You should request commit access to the Google Code project, and
>> create a branch there, which can then be merged back to the trunk
>> when it's done.
>
> Oh, that'll work fine, I can totally do that. Duh. Didn't know
> Google Code could support that. Thanks Ryan.
Good. :) It will of course be up to the owners of the Google Code
project in question whether they give you commit access or not. But
doing your work there would be much better from a collaboration and
communication standpoint. Google Code is for open-source projects,
meaning they are developed in the open, so it's better that you don't
hide your work away in some separate repository. Do it in the main
repository, and commit to your branch early and often, so that other
project members see your changes and can provide feedback on them.
It's always good to have more eyes on your code, looking at it in
different ways than you might. They might point out issues you never
thought of. And it's much easier for someone to review small
individual changes as you're developing them than a single huge
change once you're done.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2386596
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-24 01:16:34 CEST