How to Contribute: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Overview = | |||
Our modules have been [http://blog.jausoft.com/2009/07/08/svn-to-git-migration-1/ migrated to git], | Our modules have been [http://blog.jausoft.com/2009/07/08/svn-to-git-migration-1/ migrated to git], | ||
| Line 21: | Line 20: | ||
[http://whygitisbetterthanx.com/#any-workflow Collaboration] using a [http://whygitisbetterthanx.com/#distributed distributed SCM] is easy. | [http://whygitisbetterthanx.com/#any-workflow Collaboration] using a [http://whygitisbetterthanx.com/#distributed distributed SCM] is easy. | ||
= Steps = | |||
* fork a [[Jogamp SCM Repositories|SCM repository]] | * fork a [[Jogamp SCM Repositories|SCM repository]] | ||
| Line 37: | Line 36: | ||
= Git References = | |||
* http://help.github.com/git-installation-redirect | * http://help.github.com/git-installation-redirect | ||
* http://help.github.com/git-email-settings/ | * http://help.github.com/git-email-settings/ | ||
* http://help.github.com/ | * http://help.github.com/ | ||
* [http://git.or.cz/course/svn.html GIT Manual for SVN Experts] | * [http://git.or.cz/course/svn.html GIT Manual for SVN Experts] | ||
Revision as of 00:29, 26 November 2010
Overview
Our modules have been migrated to git,
thanks to the great git toolchain.
In the past we were using a centralized repository only, SVN,
and you really needed access to a central repository.
Chose a media to offer your branch to the module maintainer. This may be via
Surely it's most easy for us to access your git repository via the git protocol you may host on a free git server like [github].
Just create a branch of your own and make it available, then you may ask
the module maintainer to pull, review and merge your branch.
Collaboration using a distributed SCM is easy.
Steps
- fork a SCM repository
- do with it as you please while obeying the modules license and the law.
- tell us about the earth shaking improvements you made via the mailinglists/forum and contact the module maintainer
- if everything works fine we will probably integrate it soon, if
- you include a a junit test reflecting your changes / feature
- you comply the the modules license and contribute under it's terms
- we can somehow verify your identity, at least you use your full name in your git commits
To actually build the beast, please refer to the following manuals: