J'ai un peu de retard, ce qui fait que ceci n'est pas le premier commentaire de la dépêche, excusez-m'en.
Avec l'accord de Johannes Hanika, la version originale, donc ce commentaire, sont sous licence CC-BY-SA 4.0.
— Could you please introduce yourself and your background?
hi, i'm jo, the project founder of darktable. i studied media informatics with emphasis on computer graphics, and am currently working as researcher for weta digital (wellington) and kit (karlsruhe).
— What pushed you to create Darktable in the first place? On the official repository, we can see that the first commit appeared around the 5 April 2009; did you actually worked on it before that time?
i started to work on this just after new years 2008/2009. i was trying to set up a raw workflow on my machine on linux and there was simply nothing there that worked satisfactorily for me. at the time rawtherapee wasn't open source and my custom compiled glibc wouldn't allow to run the binary, ufraw produced great results but would just work on one single image at a time, and rawstudio didn't have the refined pipeline it has today. so i simply couldn't produce the results i was after, at least not for 1000s of images.
— The main team working on the software is composed of about 15 members. What do you think about the help from the rest of the community?
i have to say i really love our community. everybody is nice and constructive, there are great photographers, hardcore users who battle-test every feature we release, and of course a couple of very clever coders. we all have different priorities of what we think is important for darktable, but everybody is driven by their own enthusiasm to create something great. and i think we do a good job at combining all those different approaches.
— Darktable is not available on Windows. Do you think it would directly face Adobe Lightroom users if it were?
i'm not sure i understand. i know next to nothing about windows. and of course everybody is welcome to use darktable or any other software they like better, it doesn't really matter. the only thing i care about is maintaining a nice community, so it stays fun working on dt.
— Darktable does not seem to have a time-based release. Are there any rules to know what should make it to the next major release, and when?
as i mentioned, we're all driven by what we think would be a great addition to darktable. unfortunately we also have lives, so everybody contributes their new feature by the time it is done.
— Darktable participated to the Google Summer of Code in 2011. How did this experience go? Do you think Darktable will renew this experience in the future?
quick answer: no, because we're short in mentors, and we can't use the money. the mentoring thing has two issues. first, since most of us have very busy lives, we can't reliably contribute mentoring time over a certain period. second, we would probably implement the gsoc feature ourselves a lot faster than any student could possibly do it (because we already know our way around in the code), maybe even in less time than the mentoring would take. the issue with the money (also true for donations) is that we don't currently have any not-for-profit organisation associated with darktable, so accepting money is a taxation nightmare. also the amount we could hope to raise would probably be as much as one ticket for the movies for every developer per month or so.
— According to you, what part of Darktable needs more polishing and on which the help of the community would be welcomed?
we're always happy to include better support for newer camera models, which requires test shots of various sorts from users (lens distortions, white balance presets, noise profiles, base curves, etc). also translating dt and the user manual is a lot of work and could need help. creating (video) tutorials and styles (dtstyle.net) are great resources to teach new users.
— Darktable is licenced under the GPLv3. This version of the GPL is known to divide people amongst the free software community. Today, what do you think about this choice? Would you choose the same licence if you could?
i think i can speak for most people in the team and say that we don't really care about licensing. at the time we were using some GPLv3 code which mostly got removed now, so dt was forced to use that licence, too. for my part i'm happy to relicense to whatever if there is a need for it.
— What do you have in mind for the (long) future of Darktable? Do you have any secret inspiration muse for that?
as i said, it's a community effort. for my part, dt has been feature complete for quite some time now. but new devs come with new ideas and implement things which turn out to be useful for my workflow, too.
# Version originale en anglais
Posté par Jiehong (site web personnel) . En réponse à la dépêche Darktable : entrevue avec Johannes Hanika. Évalué à 5. Dernière modification le 05 décembre 2014 à 02:43.
J'ai un peu de retard, ce qui fait que ceci n'est pas le premier commentaire de la dépêche, excusez-m'en.
Avec l'accord de Johannes Hanika, la version originale, donc ce commentaire, sont sous licence CC-BY-SA 4.0.
— Could you please introduce yourself and your background?
hi, i'm jo, the project founder of darktable. i studied media informatics with emphasis on computer graphics, and am currently working as researcher for weta digital (wellington) and kit (karlsruhe).
— What pushed you to create Darktable in the first place? On the official repository, we can see that the first commit appeared around the 5 April 2009; did you actually worked on it before that time?
i started to work on this just after new years 2008/2009. i was trying to set up a raw workflow on my machine on linux and there was simply nothing there that worked satisfactorily for me. at the time rawtherapee wasn't open source and my custom compiled glibc wouldn't allow to run the binary, ufraw produced great results but would just work on one single image at a time, and rawstudio didn't have the refined pipeline it has today. so i simply couldn't produce the results i was after, at least not for 1000s of images.
— The main team working on the software is composed of about 15 members. What do you think about the help from the rest of the community?
i have to say i really love our community. everybody is nice and constructive, there are great photographers, hardcore users who battle-test every feature we release, and of course a couple of very clever coders. we all have different priorities of what we think is important for darktable, but everybody is driven by their own enthusiasm to create something great. and i think we do a good job at combining all those different approaches.
— Darktable is not available on Windows. Do you think it would directly face Adobe Lightroom users if it were?
i'm not sure i understand. i know next to nothing about windows. and of course everybody is welcome to use darktable or any other software they like better, it doesn't really matter. the only thing i care about is maintaining a nice community, so it stays fun working on dt.
— Darktable does not seem to have a time-based release. Are there any rules to know what should make it to the next major release, and when?
as i mentioned, we're all driven by what we think would be a great addition to darktable. unfortunately we also have lives, so everybody contributes their new feature by the time it is done.
— Darktable participated to the Google Summer of Code in 2011. How did this experience go? Do you think Darktable will renew this experience in the future?
quick answer: no, because we're short in mentors, and we can't use the money. the mentoring thing has two issues. first, since most of us have very busy lives, we can't reliably contribute mentoring time over a certain period. second, we would probably implement the gsoc feature ourselves a lot faster than any student could possibly do it (because we already know our way around in the code), maybe even in less time than the mentoring would take. the issue with the money (also true for donations) is that we don't currently have any not-for-profit organisation associated with darktable, so accepting money is a taxation nightmare. also the amount we could hope to raise would probably be as much as one ticket for the movies for every developer per month or so.
— According to you, what part of Darktable needs more polishing and on which the help of the community would be welcomed?
we're always happy to include better support for newer camera models, which requires test shots of various sorts from users (lens distortions, white balance presets, noise profiles, base curves, etc). also translating dt and the user manual is a lot of work and could need help. creating (video) tutorials and styles (dtstyle.net) are great resources to teach new users.
— Darktable is licenced under the GPLv3. This version of the GPL is known to divide people amongst the free software community. Today, what do you think about this choice? Would you choose the same licence if you could?
i think i can speak for most people in the team and say that we don't really care about licensing. at the time we were using some GPLv3 code which mostly got removed now, so dt was forced to use that licence, too. for my part i'm happy to relicense to whatever if there is a need for it.
— What do you have in mind for the (long) future of Darktable? Do you have any secret inspiration muse for that?
as i said, it's a community effort. for my part, dt has been feature complete for quite some time now. but new devs come with new ideas and implement things which turn out to be useful for my workflow, too.