Contributing...
If you feel like contributing to this project, here are a few suggestions.
...in terms of testing:
Just use it! And afterwards let us know how you like it. Send your bug reports, feature requests, suggestions or just your personal opinion to our mailing list. You can file a bug to our bug tracker as well - but maybe you want to discuss it first (on IRC or mailing list).
If you found a bug or managed to crash darktable, please submit a helpful backtrace! Instructions are below.
...in terms of translations:
If you want to translate darktable into your language (in case it didn't already happen) we have a short introduction how to do that. You can find that file in our git repository, it's called TRANSLATORS.
You can find a list of the currently included languages on the features page.
...a color matrix for your camera:
You can help us by providing a color matrix for your specific camera. Color matrices are specifications on how camera native color is transformed into something that an end user might like, and ideally will be correct when viewed on a calibrated display. Read more about this in Pascal's detailed blog post or watch his screencast.
Coding
Write image operation plugins! Submit patches! Help to track down bugs by supplying backtraces!
How to produce a backtrace:
Pascal recorded a detailed screencast describing the procedure. For convenience here are the minimal steps:
$ make && sudo make install
$ gdb darktable
..crash dt here..
(gdb) thread apply all bt full
Post this backtrace along with your bugreport. Or even better: Try a few prints and figure out
what seems to be the problem. Best: Fix it and supply a patch!
How to supply a patch
to current, possibly changed git master branch:
..make your important changes..
$ git commit -a
$ git pull
$ git rebase master
$ git format-patch master
Maybe you want your name and email in your .git/config, so it will appear
in darktable's git log:
$ git config --global user.email "user@domain.tld"