As a project leader, your code could be hosted as a repository on the OWASP GitHub site. If you are interested, this page provides the information required in order for you to get up and running using the OWASP GitHub site.
Git is an open source, distributed version control system used by numerous projects including the linux kernel, ruby on rails, android, debian, etc. It is proving to be the next big thing in version control leaving CVS , Subversion, Mercurial and Visual SourceSafe miles behind. The one amazing thing about Git is that branching and merging are really trivial to perform.
If you are interested in finding out more about Git, here is a link to Linus's talk at google about it:
GitHub is a website for establishing the collaboration that Git offers. It has put together for public, open source projects, as well as private, proprietary code bases. Within OWASP, all codes are public, but you do have the option to fork your own private repository.
Enough fluff, on with the game.
Step 1: Create a GiHub Account
You will need to create your own github account. Visit:
While signing up, please provide the email address that OWASP knows you as a leader.
Sign up for the free plan. The only reason for signing up relates to OWASP being able to set you up as a collaborator to your OWASP related-repositories.
Finally, you will not require an SSH public key for any OWASP repository. Public keys can be setup for any private repos that you might choose to setup outside of your OWASP repositories. You can do that at a later stage.
Step 2: OWASP needs to create your New Repository
Email Yiannis (email@example.com) with your request for a new repository. Please include in the subject line: [GitHub] and be sure to provide:
- Your GitHub username
- Project Name (e.g. WebScarab)
- Description (a short project description)
- Homepage URL
If you are using subversion, you can provide the URL to import your project from. In the case of JBroFuzz that is/was hosted on sourceforge, with the URL being:
The structure of the subversion repository for JbroFuzz worked without any problems. If your subversion repository contains a non-standard directory structure, this import process will probably not work for you. Check out our Guide for running the import yourself.
We promote the use of and should only import from public subversion repositories.
What will happen:
- We will contact the project leader to check that the account on GitHub is actually their account.
- Based on the GitHub username provided, you will be set as a collaborator for the project name above.
- An email will be sent to you confirming that you have been added as a collaborator and your project is good to go
Happy collaborative coding!
This category currently contains no pages or media.