[Ctk-developers] CTK GitHub push policy

[Patrick Cheng]

Hi all,

Here are some tutorial information on the CMake wiki page:
http://www.cmake.org/Wiki/CMake/Git

Git does take sometime to get use to. I would suggest we have a small 
hands-on session at the start of the next hackfest.

I agree that we should also have a simple and easy to follow policy to 
keep the main branch in good standing.

Patrick

On 4/23/2010 7:27 AM, Marco Nolden wrote:
> Hi Steve,
>
> I totally agree that git's tools are very complex and we need some
> simple howto for that. http://help.github.com/forking/ could be a start,
> but there are a lot of others out there, too.
> I think another important question is how code gets into the master on a
> non-technical base. An example would be:
>
> 1. Create a branch or fork of pieper/CTK
> 2. (Optional) Announce its purpose/topic to ctk-developers
> 3a: Hack, hack, hack,
> 3b: Commit to your branch/fork, push it to github
> 3c: Share results with other people for testing / review: this can be
> done by mail, direct communication, whatever
> 3d: repeat a,b,c
> 4. Before pushing to the master, send mail to ctk-developers and ask
> people for comments
> 5. Push to master or send pull request, if you don't have write
> permissions on master
>
> The nice thing in Github is that you can follow the forks and branches
> you're interested in by just pressing the "Watch" button in the web
> interface.
>
> This is just a very raw sketch but maybe we can use it to start some
> discussion.
>
> -Marco
>
> Am 23.04.2010 15:06, schrieb Steve Pieper:
>> Hello Heidelberg!
>>
>> Good idea - git/github offer great tools for to help us manage all the
>> complexity. The problem (at least for me) is that the specific workflow
>> and related commands aren't obvious.
>>
>> For svn, we put together this little FAQ that give the basic workflow we
>> wanted to support:
>>
>> http://www.na-mic.org/Wiki/index.php/Engineering:Subversion_Repository
>>
>> I'd like to put together a similar one for CTK's git usage. This may be
>> possible in advance, or maybe at the hackfest we can develop the
>> workflow and wikify it...
>>
>> Does anyone have an example of what that workflow should be?
>>
>> -Steve
>>
>>
>> On Apr/23/10 8:35 AM, Marco Nolden wrote:
>>> Dear all,
>>>
>>> we thought it could be a good idea to discuss our push policy on github
>>> before we enter the next hackfest. At the moment a lot of things are
>>> going on, which is great, but it is not easy to follow for everyone.
>>> Since we're already using Git and a social coding platform like GitHub,
>>> we should leverage this potential and make more use of features like
>>> topic branches and pull requests. This would also allow the community to
>>> take more part in what gets into CTK, purpose of changes and things like
>>> that. What do you think?
>>>
>>> Best regards from Heidelberg,
>>>
>>> Sascha, Ivo& Marco
>>>
>
>