How to contribute to Scalpel?

So, you installed and tested Scalpel and would like to contribute now?

First step: contributor documentation

To be able to somehow contribute to Scalpel, you need to get a good picture of how it works, how the different steps are handled, what the key types are, and so on. You can achieve that by reading the contributor documentation.

Get in touch with us

Ok, you now have a pretty good picture how the way Scalpel works. It’s time you start getting in touch with us! Drop by our IRC channel and join us on the development mailing list, telling us a bit about you, why you are interested in Scalpel and what you would like to work on, for example.

What you can do

There are tons of things people can do around Scalpel. Currently, the main to-be-finished task is the comprehensive semantic graph construction. But by the time you drop by this page, there may be others. Anyway, the first thing you can do is check the bug & issue tracker to see if there is something you are willing to work on. If not, you also can come with your own ideas, suggesting them on the mailing list or IRC, for example.

How you can do it

There are two ways of actually contributing to the code:

• use GitHub’s fork & merge request system to make modifications and then ask for integrating them to the main source tree;
• ask to be added as a Scalpel contributor on GitHub, which will give you commit rights on the repository.

Thanks for your interest in Scalpel!