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.
- 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.
- 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.
- 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.
- You only track the repo. Wait until the switch is made and follow the instructions in this post.
We are going to disable push rights of the people in sf.net, so nothing is pushed there, and we are going to make a mirror to github, enabling in that moment the rights to push to github. What should I do when the switch is made?When things are in place, you have to set your repo to point to the right place. To do that the command is (I suppose that origin is pointing to sf.net, if not, change the name):
git remote set-url origin email@example.com:darktable-org/
git remote set-url origin git://github.com/darktable-
A hook will be set so it pushes changes for a time to sf.net repo, while the transition is completed. After several months, it will be removed, but by default do not count that repo as being canonical any more.I am sure this change will engage more people in sending patches and contributing code to darktable. And we need your time, skills, and ideas.