New dtdocs maintainer(s) needed

Mica & Elstoc are no more interested in maintaining the Darktable documentation.

We can thanks them for all the work done on this part of the project up to now. Thanks!

That being said, the documentation has no more maintainers and we need some people to take the this position. I’m not sure about all the work involved but the first important point is to handle the PR on dtdocs (commenting with the authors about needed changes, and finally merge them when ready).

If you feel like working on this part of the project, please reply so that we can coordinate and give you the permissions to handle PR.

Thanks in advance for the Darktable community.

4 Likes

Let’s be clear: it was your combination of action and inaction, @Pascal_Obry, from your position of power as maintainer of the project that lead to me leaving the project.

I didn’t roll my ass out of bed one morning and go “huh i guess i don’t care about that anymore.”

But adding insult to injury just seems to be how you do things.

8 Likes

I agonised over the decision for really a very long time (dtdocs is my baby and it’s hard to let go of it) but ultimately felt it was better for the project for me to stand aside. I wish all success to whoever takes over.

11 Likes

Dear Pascal,

After reading all the sad posts I’ve come across here on this sad topic in the nearer past, I have to say that the wording you’ve chosen brings the whole thing to an even sadder conclusion and represents an - from my point of view - inaccurate oversimplification that completely ignores the context. I’m truly disappointed.

Thanks to @elstoc and @paperdigits for all your effort you have put into this really wonderful project. Kudos and my deep respect for your decision.

Best regards, Lars.

3 Likes

The debate has already happen, we are not going over this again, right? The project needs new maintainers. You are not volunteering, please don’t spam this thread. TIA.

3 Likes

I don’t think I am qualified to maintain anything, but I’ll gladly take a look at the repo and try to find ways to be involved.

4 Likes

I would like to try to help out here but previously felt a bit lost on how to contribute to this. I would be interested in trying to learn how.

1 Like

Thanks Chris for all this work and the various discussions and corrections you provided over the years on a wide range of topics…

2 Likes

Thanks for all the support on the doc, @paperdigits and @elstoc . I know it can be thankless work.

5 Likes

That is unfortunate, but sometimes people need to move on.

Thank you @paperdigits and @elstoc for your dedication. Without you, the docs, and dt for that matter, would not be as high calibre as they are (though its state cannot keep up with the speed of development :stuck_out_tongue:). I know you still care a lot about the project and will continue to use dt in the foreseeable future.

@Pascal_Obry Even though I do not use dt, thank you for maintaining it. I know it is hard work and harder still to engage with the community. It did not go well in the past while, but I am sure others will fill in the void. Hope you can find those you can work well with. It may just be a matter of having a new person on board.

I would be interested in helping. I don’t, however, have the copy editing expertise we have been used to, and I don’t currently use any of the AI features. If there are people who do have that expertise, they would be better placed to help.

I’m comfortable with using github, and I’d be happy working with others who have different skills. :grinning:

It’s interesting that you assume from my post I don’t want to volunteer. I was actually considering, because this kind of stuff makes kind of fun, but after this, I don’t feel like it anymore.

To be honest, I did not read from your post either, that you was considering it. Unfortunately, that you are not considering anymore.

I think that Pascal just want to express that he has no appetite in the debate again.

For Elstoc, Mica, Pascal and others it has been rather a emotional time. Shall we all be a little bit more gracious towards them?

7 Likes

Well said martinus.

I’m up for helping on the content department. Will need support on how the docs are actually maintained though.

I have some limited experience working on the docs so I know enough to maybe help people to get started.

I don’t think I have the capacity to really take charge of things but I do have some ideas.

There’s a few different tasks / roles and there’s room for people to be involved in different aspects of the documentation:

  • Maintaining the git repo, reviewing PRs, etc
  • Understanding and providing guidance on doing things with hugo
  • Triaging documentation needs from the darktable repo (determining if a PR in darktable requires a docs change)
  • Actually writing and submitting docs changes
1 Like

I have started to list the work to be done on dtdocs:

This is a first iteration to help the new volunteers.

3 Likes

@elstoc, @paperdigits Can you give an idea of what it takes, time, effort, skills? Something like “a day in life of dtdocs maintainer”. Technical.

Sorry, not trying to be difficult here, but I’m no longer contributing to the project. Most stuff is pretty well documented within the repository though and it looks like Pascal is already starting to knock up some sort of a guide.

2 Likes

Same as @elstoc, my contributions to the project have ceased.

2 Likes

Why not have the submitters of PRs document their own work? In decades of professional SW development I have never seen developers doing just code, and somebody else do the documentation.

Also I am always puzzled about the almost complete lack of inline documentation / comments in most of the source code - never seen this in corporate SW development and especially my area of safety critical SW.

Sorry, I do not want to troll, just wondering as a relative newcomer to FOSS.

5 Likes