Bill, Thanks for the clarification! See, as someone who doesn't know how to write code, those are things that I wouldn't even KNOW to think of! And why I was cautious about the way I worded my questions. As Rumsfeld said, "We don't know what we don't know." And what you've laid out makes perfect sense. It all gives me a clearer picture of why things are the way they are. Would I LIKE to help out with the documentation? Yeah, I would. Do I have the time to actually lend a hand? Sadly not. I already struggle to keep up with my own self-imposed timetable for putting out new videos.
*That we want to correctly document the way the software actually works?* Yeah, good point! I'll get back in my box now. :) What the developers do on this project is nothing short of amazing. I reckon darktable ranks as one of the shining lights in the world of FOSS. It's awesome. Thanks to yourself and everyone else involved. Cheers. ---------- Forwarded message --------- From: William Ferguson <wpfergu...@gmail.com> Date: Wed, Jun 26, 2024 at 11:35 AM Subject: Re: [darktable-user] darktable 4.8.0 released To: darktable-user <darktable-user@lists.darktable.org> On Tue, Jun 25, 2024 at 7:40 PM Bruce Williams <stu...@audio2u.com> wrote: > Pascal, > I was just having a conversation about this very topic with Chris. > Who took the stance that developers can submit new features/modules/etc > WITHOUT providing documentation? > I think up a module that will turn an "a" into a "b". You have to push this, pull that, twist something, etc, etc, etc. I start writing the module and realize I made some bad assumptions, counted on things to work differently than they do, etc, etc, etc. In the end I have a module that takes an "a" and turns it into a "b" but to make it work you kick this, shove that, etc. Then I submit a PR so that others can test my new module. Someone does something that I didn't think of and then I change the behavior again. And another bug is found, etc, etc, etc. At the end of this journey I have a working module that turns an "a" into a "b". It looks and works differently than I thought it would. At this point, I can document the module because it's in its final form. If I documented at the start, the documentation wouldn't match the software. There are ~20 developers and probably less than half are native English speakers. There are 2 darktable manual maintainers. Feature freeze is 30 days before release. Bug fixing continued up until the release tarballs were created and 4.8.1 already has multiple fixes in it. We need more people helping with the documentation. Want to sign up? That seems like such an odd stance to take. > That we want to correctly document the way the software actually works? Apologies if it sounds like I'm trying to stir up trouble... not my > intention! > Just trying to understand why the maintainer (whoever that might be) would > allow new software to be released to the public without supporting > documentation. > Most open source projects have just a readme file. I don't recall documentation being stressed prior to Mica and Chris taking over the manual, but now it is. So in some ways we're better, but we have lots of room for improvement. Bill Cheers. > > > ---------- Forwarded message --------- > From: Pascal Obry <pas...@obry.net> > Date: Wed, Jun 26, 2024 at 6:22 AM > Subject: Re: [darktable-user] darktable 4.8.0 released > To: Willy Williams <grayc...@bolthole.net>, < > darktable-user@lists.darktable.org> > > > Le mardi 25 juin 2024 à 10:05 -0400, Willy Williams a écrit : > > Have to ask - when will the manual accompanying v4.8.0 be released, > > or am I once again looking in the wrong place? > > You are at the right place and the answer is easy... when it is done. > > If you want to help, please contact the doc maintainers. > > Thanks, > > -- > Pascal Obry / Magny Les Hameaux (78) > > The best way to travel is by means of imagination > > http://photos.obry.net > > gpg --keyserver keys.gnupg.net --recv-key F949BD3B > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > > ____________________________________________________________________________ > darktable user mailing list to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
