But we were getting closer!! 
2 Likes
I never said there should be a deadline. They had it ready a year ago. If there were issues forcing delays. Of course i would understand.
Open source is special but it does not mean a free pass. We can point out issues when they occur. Open source does not mean untouchable.
Maybe my misinterpretation. I get the feeling people are treating this as if libraw is the poster child for open source. There are millions of other open source projects both big and small. Does libraw act respectively towards the community? You decide.
2 Likes
you can point out your issue, but that’s just freedom of speech. But also there’s no such thing as an obligation to listen or try to meet everybody’s demands.
If you don’t like the freedom of the developer to prioritize their time and work then you’re free to pay someone to fulfill your expectations. Or fork and do it better 
I think most of the feedback is from open source developers who struggle to manage a real life - open source dev balance.
I have 2 projects that are over a year old, bringing group persistence across database instances to darktable and adding the lua-scripts to darktable releases. Group persistence was almost complete 9 months ago and then my life turned into a Lemony Snickets A Series of Unfortunate Events book. In just the last week I’ve picked it back up and am trying to finish it.
As far as adding the lua-scripts to the release I did some preliminary work and figured out a course of action and then it fell by the wayside when real life took over. It’s still my plan to do it, but it doesn’t have a timeline at present.
I’m not even going to mention the other open source areas I’ve neglected, but there are some.
A year sounds like a lot of time to get something done. When I was young and single, responsible for only myself, it truly was. Now that I’m older and have numerous responsibilities, some of which I have little control over, I find a year FLYS by.
3 Likes
Actually quite the opposite. Most opensource licenses have a clause like:
“because the program is licensed free of charge, there is no warranty for the program, to the extent permitted by applicable law. except when otherwise stated in writing the copyright holders and/or other parties provide the program “as is” without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. the entire risk as to the quality and performance of the program is with you. should the program prove defective, you assume the cost of all necessary servicing, repair or correction.”
1 Like
For the record, I do agree with this completely. I would prefer libraw to act much faster. That would be more respectful of the community, and better for the ecosystem.
But I also know from my own experience that you sometimes just… can’t. It is ultimately up to dev(s?), not me, and I trust they have good reasons for doing the things the way they’re doing them. I’m grateful they’re doing the work at all – while at the same time wishing they’d do it faster. But I often can’t bring myself to do things faster either, because
sometimes.
On a different note, I highly respect that, @pilgrim, you stayed calm and polite throughout this exchange. This is unusual, and praiseworthy. Thank you for that.
1 Like
I believe libraw delays the relaese so their pay-for products get it first and keep their “market advantage.” They don’t seem to take pull requests and it is a true “throw it over the fence” open source. I don’t think there is a “community” around it. So in that case, you either take it or leave it, and we’ve chosen to take it, despite the draw backs, to get CR3 support which Roman was unable or uninterested in supporting in rawspeed. “It is what it is” is the correct turn of phrase here.
6 Likes