The best way to familiarise yourself with the internals of OpenCOR is by having a look at its source code.
All of the source code is and must be made available under the
OpenCOR namespace (e.g.
There are only two exceptions to this rule:
[OpenCOR]/src/windows/main.cpp (i.e. OpenCOR’s two main
Although it can technically be done, no work should be carried out on the master branch.
Instead, anyone wanting to contribute to OpenCOR should first fork the Git repository.
Work for issue
#XXX should then be done in a branch called
The work done, a pull request should be created.
This will trigger OpenCOR to be built and tested on Jenkins.
Assuming everything goes well, the project manager will decide whether to merge the pull request.