This is the contribute.md of 52°North project WorldViz. Great to have you here! Here are a few ways you can help!
You are interesting in contributing the 52°North Triturus and you want to pull your changes to the 52N repository to make it available to all?
Best way to get started is to start with these:
- Mailing list: http://52north.org/resources/mailing-list-and-forums/
- IRC channel: #52north on irc.freenode.net
- Website: http://52north.org/
- Get involved in 52°North: http://52north.org/about/get-involved/
- Benno Schmidt @BennoSchmidt
- Christian Danowski, @cDanowski
- Martin May, ([email protected])
52°North requires all contributors to sign a contributors license agreement (CLA). This is not scary but essential for open source projects to live beyond projects and individual contributions.
Find all information on our licensing page at http://52north.org/about/licensing/ and our CLA FAQ at http://52north.org/about/licensing/cla-guidelines.
This section includes advice on how to build new features for the project & what kind of process it includes.
- Before you start working on a new feature, create a new issue and start a discussion on the mailing list.
- We follow the fork & pull development model: https://help.github.com/articles/using-pull-requests
Don’t get discouraged! We estimate that the response time from the maintainers is around 4 days.
You can help report bugs by filing them here: https://github.com/52North/triturus/issues
- Don't forget to check the existing ones first and take a look at the mailing list guidelines - going through these steps makes it likely that you can fix the bug yourself: http://52north.org/resources/mailing-list-and-forums/mailinglist-guidelines
- Look at existing bugs and help us understand if the bug is reproducible. Is it reproducible in other environments (browsers)? What are the steps to reproduce?
All documentation is either in README.md file or in the 52°North 3D wiki, and a critical read as well as feedback and documentation extensions are always welcome.
- If you have further questions, contact Benno: @BennoSchmidt, [email protected]