darktable-org / darktable-org/darktable
Future Direction Strawpoll <Please rename me>
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
[!NOTE]
Please refrain from bikeshedding in this issue.
cc @TurboGit, i'm not sure who else.
I'd like to disscuss two interconnected things.
While i expected to first hook up RS.RS into vkdt,
that program does not do "fall back to other loader
if the first one fails", so it's a little pointless
to integrate RS.RS into vkdt right now.
But at the same time, not having it integrated
at least somewhere is not an ideal solution either.
So i'm wondering if i could put it into darktable itself.
Are there any general objections on that?
CMake does not support Rust's cargo. But Meson does.
And Meson seems to be a kind-of better buildsystem nowadays.
While i'm sure that i will manage to get it working with CMake,
i'm wondering what are y'all thoughts on switching over to Meson.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion about integrating RS.RS into darktable or vkdt and the proposed move from CMake to Meson. Determine which direction the project accepts and document the resulting integration or build-system plan; the issue does not name files or tests, so completion depends on an agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100