Bluntly copied from the github archive:
Similar to the process of posting new blog articles, we also host most of our learner materials as gh-pages and use the usual Github-Tools to manage them: Wikis, Issues, Forks and Pull-Requests. But as every material is unique in its way, they usually provide a Readme.md in the main directory to guide you through the process of setting it up and how to contribute if the process deviates far from what is described here.
On Site: Issue tracking
While you are coaching and your material goes through the highest of all tests - learners approval - you might notice some clinches, bugs or mistakes. Share them with your fellow coaches and discuss them when you have a minute and then quickly add them as actionable issues to the repository. Maybe even someone already volunteered to fix them, assign them then.
Translation: submit via Pull-Requests
When you want to create a localisation of the material, we recommend creating a fork and work on it separately in your own repository for a while. As such a task might be bigger it makes sense to invite some other contributors to help you with that. Once you are done, please submit your translation as via Pull-Request into the main repository.
Our Learner Materials are all under the Creative Commons Attribution-ShareAlike 3.0 Unported License. Everyone is free to share and edit them as long as they keep staying under this licence and there is an attribution for where they got it from - generally saying and linking to the OpenTechSchool-Version of the material is considered sufficient.
By willingly submitting your content you agree to that the material is licenced as such and your attribution being granted through the version-history feature of Git/Github and/or through a "Contributors"-File inside the main directory. Being mentioned in the later is the responsibility of the person submitting changes.