Updates to the ClojureBridge curriculum are welcome and encouraged. We would not have anything without the input and guidance of the volunteers who put organize and attend ClojureBridge workshops.
Also, feel free to make forks of the curriculum and not contribute back. Make different curricula, too. these contribution guidelines are simply meant to provide guidance for the management of the main ClojureBridge curriculum.
- Create a GitHub account, if you don't have one, already.
- Fork the repository by navigating to the main intermediate-clojure repository page, then clicking on the "Fork" button in the upper-right corner.
TBD.
This repository is based upon Cognitect's clojure-lab, which is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Accordingly, details of that original license take precedence over any other licensing information in this repository. In practice, this means that you may
- Share, copy, and redistribute this material in any medium or format, as well as
- Adapt, remix, transform, and build upon this material.
However, you must
- Give appropriate credit to both Cognitect and ClojureBridge;
- Not use this material for commercial purposes; and
- Distribute any and all forks, remixes, transformations, or additions to this material under the same Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License as the original Cognitect repository.
- Push your committed changes to your local fork of the repository.
- Create a pull request (PR).
- Submit the pull request to the main ClojureBridge/intermediate-clojure repository.
The ClojureBridge intermediate-clojure curriculum team will review and discuss the pull request comments on the PR. Once two curriculum team members have given the PR a thumbs up, the PR will be accepted and merged!
You may be asking, "Wait, why does the curriculum team get to say which PRs get accepted?"
I'm glad you asked!
If you contribute more than two patches to this repository, you too will become part of the curriculum team. Curriculum team members are given commit rights to the curriculum.
Note that commit rights are meant for approving PRs, not for making direct commits, and making direct commits may result in having your commit rights revoked.
There is also a ClojureBridge curriculum Google Group for discussing curriculum direction.
- Workshops or chapters that are using the main ClojureBridge curriculum should fork the curriculum in their chapter's GitHub, as seen here.
- Chapters should give teachers commit rights to their chapter's fork of the curriculum.
- Chapters are encouraged to contribute changes back to this main repository via PR!