As an Open Source project Holochain welcomes many sorts of contributions, bug-report & fixes, code contributes, documentation, tests, feedback and more.
We are committed to foster a vibrant thriving community, including growing a culture that breaks cycles of marginalization and dominance behavior. In support of this, some open source communities adopt Codes of Conduct. We are still working on our social protocols, and empower each team to describe its own Protocols for Inclusion. Until our teams have published their guidelines, please use the link above as a general guideline.
- For task management we use Waffle or for the non-kan-ban view github's issues
- Chat with us on our chat server or Gitter
We use test driven development. When you add a new function or feature, be sure to add the tests shows that it works. Pull requests without tests will most-likely not be accepted!
This section describes our practices and guidelines for using git and making changes to the repo.
- We use Github's pull requests as our code review tool
- We encourage any dev to comment on pull requests and we think of the pull request not as a "please approve my code" but as a space for co-developing, i.e. asynchronous "pair-coding" of a sort.
- We develop features on separate branches identified by the Github issue number, i.e.
124-my-new-feature - We use merge (not rebase) so that commits related to a ticket can be retroactively explored.
- In most repos development happens on a
developbranch which gets merged to master when there's a release.
The default licensing for our repos is currently 
Note: We are considering other 'looser' licensing options (like MIT license) but at this stage are using GPL while we're getting the matter sorted out. See this article for some of our thinking on licensing for distributed application frameworks.
If you contribute code do so knowing that we may change the licensing from GPL to some other form like MIT without notification.