Darktable 2.711/27/2023 1085 respondents answered all questions. Between 20, 66 persons have contributed to darktable source code, so we can expect that at most 6 % of the respondents are developers and contributors of the project. It is to be noted that it was not relayed on Github or any other code hosting platform, though the IRC channel is populated with developers and power-users, so the respondents are expected to be mostly users and not contributors.ġ101 respondents from 59 countries participated between March 6th 2020 and March 20th 2020. possibly on other chats and platforms I am not aware of.The survey was conducted in English, on the internet, using to record answers. It had a total of 26 questions. The link to the survey was posted : In 2020, I ran a survey of the darktable user base to gather actual data. Since these past 2 years have been hectic, dev-wise, I only got to process the data this summer. This is unfortunately overlooked in FLOSS and it is often not well regarded to collect user data. But then, developers will justify their design by referring to the “average user” as a fantasized entity, undefined and certainly not understood. However, it reminds me on another issue #2420 I reported time ago which unfortunately is closed, even I could see from Bruce’s video, that it still can occur.The core basics of design are to know for whom you design, that is who are the users of your solution, what they expect and what they need. It is also necessary to assess if the actual user of your product is the one you designed it for in the first place, that is, who is missing from your user base, to avoid the survivor bias. Still I have some strange multiplication of module entries in history stack, just because I touch the same module several times.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |