We are sorry to inform you that we had to disable comments on this website. Currently there are more than 21 thousand messages in the spam queue plus another 2.6 thousand in the review queue. There is no way we can handle those. If you want to get in touch with us then head over to the contact page and find what suits you best – mailing lists, IRC, bug tracker, … We hope to be able to get some alternative up and running, but that might take some time as it’s not really a high priority for us.

Continue Reading →

**Update: **the git repository officially resides in github now.

Today we are moving our git repo from sf.net to github, as it was agreed in the developer meeting that took place yesterday. This will happen today 22:00 – 23:00 CEST

What should I do now?

Depends on the role you play in the project.

1. You have commit rights into current sf.net repository: please open an account in github if you don’t have any and make me know it. I will give you those permits there, but do not push there for now, your changed will be lost.
2. You don’t have commit rights but regularly contribute back patches to darktable: please consider doing a fork of our repo in github and make a branch there for your patches. Later on make a pull request to let us know that we should pull from your branch.
3. If you make some patches, but not in a regular way, you can also benefit of having your own fork … it will allow to publish your changes, access them from remote places, and have a backup place for your repo in case of disaster.
4. You only track the repo. Wait until the switch is made and follow the instructions in this post.

What is going to happen just before the switch?

Continue Reading →