Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

We're always looking for contributions! Here are some ways to participate in Cargo's development:

  • By sending feedback to the user or dev mailing lists. The feedback could be about something that does not work, something that could be improved, a feature you'd like to see, etc. Or simply it could be that you're a happy user. Letting us know helps a lot!
  • By answering emails from others on the mailing lists.
  • By sending code patches. In that case there are a few rules you need to know.
  • By spreading the word about Cargo!

Coding rules

If you submit a patch you need to follow these rules:

  • Copyright your code to Vincent Massol (see license explanations)
  • Do not use an @author tag (there was a big discussion on this in Apache land - We need to put the link here)
  • Ensure that your code passes the build. Note that the build contains some Checkstyle checks that your code must pass.
  • Ensure that you have unit tests and/or integration tests (as part of the existing Cargo test suites)
  • Use the same code formatting as the existing code.
  • Create a JIRA issue and attach your patch to it.
  • Create documentation for what you have added (Ask on the list and you'll get access to Cargo's wiki).
  • Add your name on the Credits page.

In addition if you plan to contribute big patches that impact existing code, we recommend discussing it on the mailing list first.


  • No labels