darktable-org / darktable-org/darktable

RFC: Who is darktable for / What is the "mission statement"

Open
#22,024 17 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

I'm sure we're all more than familiar with the "darktable isn't like X, therefore it sucks" and similar complaints. Recently I became aware of Arch Linux's idea of user centrality, which got me thinking of having something similar for darktable that can be featured on the website in some way. Then I got into arguments with some detractors in the comments of a YouTube video about RapidRAW ("this is the kind of UI darktable should have" etc) and today there was a big discussion on Reddit, all of which prompted me to do this RFC.

Considering that darktable is becoming better known, with more people jumping in blind and/or with the wrong expectations, I suspect that we will only get more of this kind of nonsense, so trying to get in front of at least some of it would be a good idea for everyone's sanity.

So if we can come to some kind of consensus on DT's target user and what the "mission statement" is, I will rewrite the introduction on the front page to make visitors aware of what they are in for and also add a more in-depth FAQ entry along the lines of what Arch Linux has. Longer term I have plans to rewrite the about page, which would also be a good place to have this kind of information.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the RFC and its discussion to understand the proposed consensus on darktable’s target users and mission. If agreement is reached, update the website front-page introduction and add the planned FAQ entry; the longer-term about-page rewrite is also identified as a possible location. Done means the project’s audience and purpose are clearly documented.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.