4 ms·

> current biggest grip with dt... why are those damn arrows at the edges of the screen so tiny??? Expanding and retracting the side panels requires pixel-perfec

by thg 4y ago

> current biggest grip with dt... why are those damn arrows at the edges of the screen so tiny??? Expanding and retracting the side panels requires pixel-perfect accuracy on a ~20px target. I know I could use keyboard shortcuts, but my brain isn't wired for them yet. You can make them bigger through some CSS tweaks: https://docs.darktable.org/usermanual/development/en/preferences-settings/general/ https://docs.darktable.org/usermanual/development/en/prefere...

sneak 4y ago
It's open source, you can change anything. The UI shouldn't be so annoying and hostile out of the box regardless. I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.
- michaelmrose 4y ago
  Most projects have an issue tracker where one proposes changes or reports bugs. The IRC channel is labeled "Support channel for darktable" rather than "Tell the developer how they ought to better serve me for free" People have a finite slice of their life to give you for nothing. Putting specific suggestions on the issue tracker seems more respectful of their time.
  - iasay 4y ago
    I raised a ticket on an open source project about a defect. It was open for 6 months with no comment. So I fixed it and did a PR. The PR was still sitting there open after 6 months. More interesting PRs to the developers have been merged. Attention and stewardship are not universal.
    - rglullis 4y ago
      What I usually do when I see promising projects and slow devs. 1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?" 2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get this issue merged and to have some sort of prioritization when triaging issues. 3. Failing those: write a blog post and propose a fork. This is usually the quickest way to get a reaction from narcissistic developers.
      - tomcam 4y ago
        Maybe some of these developers are just, you know… busy.
        rglullis 4y ago
        It's the busiest developers who would be interested in receiving PRs. If they go unanswered for six months, it is a clear signal that there is something stopping else them from action.
        account42 4y ago
        > It's the busiest developers who would be interested in receiving PRs. Depends on the PR. Bugfixes sure, but new features mean more work for the maintianer in the future.
        rglullis 4y ago
        It is also an opportunity for someone to feel involved and eventually join the group, perhaps even become a maintainer. Speaking as a project maintainer that is starting to see some traction: I'd love to see people coming with PRs for features. It would mean a big amount of validation.
        tomcam 4y ago
        Do you think busy devs who also run open source projects tend to have plenty of time to set a high priority on FOSS?
        rglullis 4y ago
        Is Dark Table just a side-project from one busy developer?
- iasay 4y ago
  Having tried to improve things on multiple projects and being ignored or got hostile responses I gave up on open source contribution. I bought a Mac and use Lightroom and I’m happy to give them both my money.
  - berkes 4y ago
    There are loads of friendly and welcoming OpenSource communities. I'm sorry you did not stumble into them, but instead in the few hostile ones. It's a pity that made you give up. A general tip, I give to people wishing to contribute to OSS is to first watch from the sideline. Read issues, threads, subscribe to an ML etc. Then to ask. Don't just throw in PR or feature request, but ask: is this welcome? How do you work? Any particular details that you wish me to pay extra attention to (tabs, spaces, tests, documentation, design). As a FLOSS maintainer myself, it can be very intimidating to have someone throw a PR at you that rewrites everything (it comes across as: you suck, your software sucks, but watch me fix all that), or that disregards things that I deem critical (tests, architecture) It is really hard to review it, without coming across as an arrogant bastard. And often software that I put on a back burner will require me significant effort to get back into. So merging a simple typo fix or dependency update might cost half a day, just to get the dev env back up.
    - iasay 4y ago
      I certainly wasn't arrogant with the last one. Hey dudes, there's a pointer dereferencing crash here which occurs when I do X, Y then Z. Added one line change to fix it. SILENCE. There are no test cases for most projects either.

by thg 4y ago

sneak 4y ago

It's open source, you can change anything. The UI shouldn't be so annoying and hostile out of the box regardless. I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.

michaelmrose 4y ago
Most projects have an issue tracker where one proposes changes or reports bugs. The IRC channel is labeled "Support channel for darktable" rather than "Tell the developer how they ought to better serve me for free" People have a finite slice of their life to give you for nothing. Putting specific suggestions on the issue tracker seems more respectful of their time.
- iasay 4y ago
  I raised a ticket on an open source project about a defect. It was open for 6 months with no comment. So I fixed it and did a PR. The PR was still sitting there open after 6 months. More interesting PRs to the developers have been merged. Attention and stewardship are not universal.
  - rglullis 4y ago
    What I usually do when I see promising projects and slow devs. 1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?" 2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get this issue merged and to have some sort of prioritization when triaging issues. 3. Failing those: write a blog post and propose a fork. This is usually the quickest way to get a reaction from narcissistic developers.
    - tomcam 4y ago
      Maybe some of these developers are just, you know… busy.
      - rglullis 4y ago
        It's the busiest developers who would be interested in receiving PRs. If they go unanswered for six months, it is a clear signal that there is something stopping else them from action.
        account42 4y ago
        > It's the busiest developers who would be interested in receiving PRs. Depends on the PR. Bugfixes sure, but new features mean more work for the maintianer in the future.
        rglullis 4y ago
        It is also an opportunity for someone to feel involved and eventually join the group, perhaps even become a maintainer. Speaking as a project maintainer that is starting to see some traction: I'd love to see people coming with PRs for features. It would mean a big amount of validation.
        tomcam 4y ago
        Do you think busy devs who also run open source projects tend to have plenty of time to set a high priority on FOSS?
        rglullis 4y ago
        Is Dark Table just a side-project from one busy developer?
iasay 4y ago
Having tried to improve things on multiple projects and being ignored or got hostile responses I gave up on open source contribution. I bought a Mac and use Lightroom and I’m happy to give them both my money.
- berkes 4y ago
  There are loads of friendly and welcoming OpenSource communities. I'm sorry you did not stumble into them, but instead in the few hostile ones. It's a pity that made you give up. A general tip, I give to people wishing to contribute to OSS is to first watch from the sideline. Read issues, threads, subscribe to an ML etc. Then to ask. Don't just throw in PR or feature request, but ask: is this welcome? How do you work? Any particular details that you wish me to pay extra attention to (tabs, spaces, tests, documentation, design). As a FLOSS maintainer myself, it can be very intimidating to have someone throw a PR at you that rewrites everything (it comes across as: you suck, your software sucks, but watch me fix all that), or that disregards things that I deem critical (tests, architecture) It is really hard to review it, without coming across as an arrogant bastard. And often software that I put on a back burner will require me significant effort to get back into. So merging a simple typo fix or dependency update might cost half a day, just to get the dev env back up.
  - iasay 4y ago
    I certainly wasn't arrogant with the last one. Hey dudes, there's a pointer dereferencing crash here which occurs when I do X, Y then Z. Added one line change to fix it. SILENCE. There are no test cases for most projects either.