How to Contribute: Difference between revisions
Jump to navigation
Jump to search
(Added new link for more build details) |
(Added link to new page on feature/fix contribution) |
||
| Line 1: | Line 1: | ||
= Overview = | = 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], thanks to the great git toolchain.<br> | ||
thanks to the great git toolchain.<br> | In the past we were using a centralized repository only, ''SVN'', and you really needed access to a central repository. | ||
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 [[Maintainer and Contacts#Maintainer|module maintainer]]. | Chose a media to offer your branch to the [[Maintainer and Contacts#Maintainer|module maintainer]]. | ||
| Line 28: | Line 26: | ||
** you comply with the module's license and contribute under it's terms | ** you comply with the module's license and contribute under it's terms | ||
** we can <i>somehow</i> verify your identity, at least you use your <b>full name</b> in your [http://help.github.com/git-email-settings/ git commits] | ** we can <i>somehow</i> verify your identity, at least you use your <b>full name</b> in your [http://help.github.com/git-email-settings/ git commits] | ||
For more details, see [[Contributing a new feature or fix|these instructions on how to contribute a new feature or fix]]. | |||
Revision as of 23:27, 10 January 2011
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 with the module's license and contribute under it's terms
- we can somehow verify your identity, at least you use your full name in your git commits
For more details, see these instructions on how to contribute a new feature or fix.
To actually build the beast, please refer to the following manuals: