How to contribute

  • If you’d like to contribute, but don’t have a specific project in mind:
    • Message a Community Maintainer saying “I want to help!”. They’ll work with you to find an area for you to contribute.
    • Browse the issues labelled help wanted on the Corda GitHub issues page. Issues labeled good first issue are ideal for first-timers.
  • If you have a specific contribution in mind, message the #contributing channel of the Corda Slack or contact one of the Community Maintainers directly to confirm if it is appropriate before starting development.

One of the things that makes Corda special is its coherent design. That’s why we have defined some guidelines to ensure new contributions only ever enhance the project:

Quality: Code in the Corda project should meet the Corda coding style guidelines, with sufficient test cases, descriptive commit messages, evidence that the contribution does not break any compatibility commitments or cause adverse feature interactions, and evidence of high-quality peer review.

  • Size: The Corda project’s culture is one of small pull requests (PRs) submitted regularly. The larger a PR, the more likely it is that you will be asked to resubmit as a series of self-contained and individually-reviewable smaller PRs.
  • Scope: To ensure the Corda project remains coherent and focused, so we ask that the feature’s scope is within the definition specified in the Corda Technical Whitepaper.
  • Maintainability: If the feature requires ongoing maintenance (for example, support for a particular brand of database), we may ask you to accept responsibility for maintaining it.
  • Non-duplicative: If the contribution duplicates features that already exist or are in progress, you may be asked to work with the project maintainers to reconcile this. As the major contributor to Corda, many employees of R3 are working on features at any given time. To avoid surprises and foster transparency, our Jira work tracking system is public. If in doubt, reach out to one of the Community Maintainers.

In addition, there are a number of additional requirements that apply to large contributions.

  1. Create a fork of the Corda repo.
  2. Clone the fork to your local machine.
  3. Build Corda.
  4. Be sure to work from the appropriate branch for your changes (see below).
  5. Make the changes in accordance with the code style guide.

Corda does not use the master branch for development. Instead, all development work is done on the branch named according to the release that it represents. The following pattern is used for branch naming: release/os/{major version}.{minor version}

Note that release is always part of the name of the branch, even for unreleased versions of Corda. The default Github branch is always the current development branch of Corda. Development work should target the default branch unless the work is needed in a specific version of Corda. In that case, development work should target the oldest version of Corda for which the work would be appropriate. For instance, if a pull request would be applicable to Corda 4.6 and Corda 4.11, it would be appropriate to open a pull request for release/os/4.6. That work would then be merged forward from release/os/4.6 to release/os/4.11. If the work is only applicable to Corda 4.8, a pull request need only be opened against release/os/4.11.

  • Use error handling best practices: Errors should not leak into the UI. Add try/catch blocks when writing tools intended for end users, like the node or command line tools. Write meaningful error messages. For example, instead of throwing an OutOfMemoryError, indicate that a file is missing, a network socket was unreachable, etc. Tools should not show stack traces to the end user.
  • Look for API breaks: We have an automated checker tool that runs as part of our continuous integration pipeline, but it can’t catch semantic changes where the behavior of an API changes in ways that might violate app developer expectations.
  • Suppress inevitable compiler warnings: Compiler warnings should have a @Suppress annotation if they are expected and cannot be avoided.
  • Remove deprecated functionality: Make sure you remove deprecated uses in the codebase.
  • Avoid making formatting changes as you work: New style guide rules were implemented in Kotlin 1.2.20. The new Kotlin style guide is significantly more detailed and IntelliJ knows how to implement the new rules. Re-formatting the codebase creates a lot of diffs that make merging more complicated.
  • Things to consider when writing CLI apps: Make sure any changes to CLI applications conform to the CLI UX Guide.

If you are interested in extending the flow state machine, you can find instructions on how to do this here.

To test your changes:

  1. Add tests: Unit tests and integration tests for external API changes must cover Java and Kotlin. For internal API changes these tests can be scaled back to Kotlin only.
  2. Run the tests: Your changes must pass these tests.
  3. Perform manual testing: Before you send code for review, test the user experience manually. Automated tests are not a substitute for dogfooding.
  4. Build against the selected development branch: You can test your changes against CorDapps defined in other repos.
  5. Run the API scanner: Your changes must not break compatibility with existing public API. We have an API scanning tool that runs as part of the build process. Use this to flag any accidental changes.

Document any changes to Corda’s public API:

  1. Add comments and javadocs/kdocs. API functions must have javadoc/kdoc comments and sentences must be terminated with a full stop. We also start comments with capital letters, even for inline comments. Where Java APIs have synonyms (e.g. %d and %date), we prefer the longer form for legibility reasons. You can configure your IDE to highlight these in yellow.
  2. Update the relevant .md file(s).
  3. Include the change in the changelog if the change is external and therefore visible to CorDapp developers and/or node operators.
  4. Build the docs locally and check that the resulting .html files render correctly.
  5. If relevant, add a sample. Samples are one of the key ways users learn what the platform can do. If you add a new API or feature and don’t update the samples, your work will have less impact.
  1. Create a pull request (PR) from your fork to the equivalent branch of the Corda repo.

    • Complete the PR checklist in the comments box.
      • Have you run unit, integration and smoke tests?
      • If you added/changed public APIs, did you write/update the JavaDocs?
      • If the changes are of interest to application developers, have you added them to the changelog and release notes where applicable?
      • If you are contributing for the first time, please read the contribution guidelines above and indicate your agreement.
    • Add a clear description of the purpose of the PR.
    • Add the following statement to confirm that your contribution is your own original work: “I hereby certify that my contribution is in accordance with the Developer Certificate of Origin.”
  2. Request a review by reaching out in the #contributing channel of the Corda Slack or contacting one of the Community Maintainers directly. The reviewer will either:

    • Accept and merge your PR.
    • Leave comments requesting changes via the GitHub PR interface.
  3. Make the changes by pushing directly to your existing PR branch. The PR updates automatically.

  4. Optional: Open an additional PR to add yourself to the contributors list. The format is generally firstname surname (company). You can omit the company name.

A “large” contribution is one that meets one or more of the following criteria:

  • It would require users to modify or recompile their CorDapps.
  • It would introduce a new user-facing feature or configuration option.
  • It would negatively impact performance or security (e.g. by introducing a new dependency).
  • It would take a long time to implement - two weeks or more.
  • It would significantly increase the project’s QA or support costs.

Large contributions can be disruptive - both for users of the Corda platform, and for platform developers who are modifying the same parts of the software as part of the established product roadmap. In addition, the work of reviewing and maintaining these contributions diverts the team’s resources from other efforts. Generally, it is more effective to put in a feature request via the corda-dev mailing list instead.

The process for contributing a large change to Corda is as follows:

  1. Raise a discussion of your proposed contribution on the corda-dev mailing list.

    • Please search the mailing list archives first for similar proposals that may have been discussed and declined in the past.

    • You will need to provide evidence that you are capable of delivering a large change to the platform. This can be done by contributing smaller changes to Corda first, or by otherwise showing your ability and commitment to delivering large changes to complex, established projects.

  2. The project maintainers will feed back on your proposal. Some of the criteria they will be evaluating the proposal against include:

    • The contribution is/is not aligned with Corda’s mission statement (as outlined in the Corda Introductory Whitepaper).

    • The contribution will/will not negatively impact the ability of R3 and other project contributors to deliver improvements to the platform.

    • The contribution will/will not require the project maintainers to have access to proprietary hardware or software resources.

    • The contribution will/will not impact the project’s QA or support costs.

  3. If the proposal is accepted, please raise a design PR on the Corda GitHub project. The design should give the rationale for the change, how the change will be implemented, and what alternative designs were rejected. The engineering team will review your design and indicate any required changes.

  4. Once the design is approved, please go ahead with the change according to the guidelines for small and medium contributions. In addition to those guidelines, we require that large contributions be fully exercised by tests, including any exception paths and error handling.

All contributions to this project are subject to the terms of the Developer Certificate of Origin reproduced below:

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.