Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Christian W. <cw...@cw...>]

Hi Mark,



> I would love to work on the private key feature if you would like.
That's a good idea; it's a small task that still lets you work on
several parts of SemanticScuttle.
If you like you could write an email sketching out how you
would solve the problem, and we can discuss the issue. If not, just get
on hacking :)


> I'm not going to lie and tell you I know everything about source
> control management but I'm familiar with the basic workings of SVN.
> Working on getting up to speed with GIT.  With that said, my guess is
> that I make a clone of the master branch to make my changes and then
> that will be merged when it is complete?
Yes, that's about it:
1. Create a new branch from the master branch and use that (checkout)
2. Do your changes, commit them to your branch
3. Push the changes in your branch regularly to the semantiscuttle git
   repository. You all should have write access. 
4. When you're done, tell me. I will review your changes, say what
   could be better and finally merge it into the master branch.
5. Please do not commit to the master branch yourself.

If anyone of you have questions, I'm regularly online in irc
(semantiscuttle on freenode) and in jabber - don't hesitate to ask.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-