cs_content_header = cs_long_name
The easiest and best way to contribute to CAT-SOOP is to use it, to report any issues you find, and to tell your colleagues if you like it!
Please see below for some guidelines about contributing more directly to CAT-SOOP, and please don’t hesitate to reach out if you have questions.
We’re happy to help! There are a couple of options for asking questions:
If you have found a security vulnerability, please do not post publicly. In
that case, please instead send e-mail to
or send e-mail directly to Adam (
firstname.lastname@example.org), optionally encrypting your
message with his public key.
For other issues, as a first step, please ensure that they were not already reported by looking through the issue tracker. If you’re unable to find an open issue addressing the problem, feel free to report your issue in any of the ways described above.
Regardless of how you report the issue, please be as descriptive as you can, and please try to include an example that demonstrates the issue if possible.
If you have questions about the bug reporting process, or if are unsure whether you’ve found a bug, please don’t hesitate to reach out via e-mail, IRC, or the issue tracker.
A good place to start is to suggest your change in the
~email@example.com mailing list or in the IRC room, and to read
through the hacker’s guide for information on the process
for contributing code, as well as information about coding style, tests, etc.
We really appreciate it!
If you are comfortable doing so, the best way to submit documentation changes
is by the same process described above, as described in the hacker’s
But we’ll accept documentation changes in any format! Feel free just to e-mail
your changes/suggestions (in any format) to