Contributors page can be found at https://phab.lubuntu.me/w/contributors/

(belated) ACK on wiki page list of contributors.
I've not got much further with this, but I'll provide a summary.

@guiverc I like this idea of having a list of contributors. Feel free to start a page on the wiki here.

I used to take notes in my discrete math classes in LaTeX, so if help is needed there, I can probably assist. However, I suspect that @lynorian's Sphinx skills will likely suffice.

Thanks for setting up Jenkins.

Thanks @teward for your assistance with CI. We may have some further sysadmin things dealing with this task once we figure out what we want to do with this.
I want to go on the record and say this is fantastic @apt-ghetto! Very nice work.
One minor thing, in the task you mentioned looking at the output and tweaking the CSS. I think we need to poke at the TOC if possible. I am not sure what our options are there but it gets all bunched up and the sub-chapters are not visible in the Table.
We still have some TODO's left, I will edit the task so those items are check boxes indicating where we stand with the task.

Fixed. Needed another plugin added (HTML Publisher). Working now.

However, you still get brokenness:

PDF builds should work now. At least, Docker can execute. The container Jenkins is in did not have nesting enabled. We're no longer getting instant failures.

Yes, Jenkins is running inside an LXD environment. I can try and set up nested dockerization in that.

General (wiki) looking & some minor editing.. Comments & discoveries so far

Docker in LXC

I have a feeling the Jenkins host is running in LXD. @teward?

@wxl give me the valid link and I'll poke it in.

@tsimonq2 it doesn't seem like this is resolved when https://manual.lubuntu.me/lts doesn't seem to go anywhere or rather it seems to go to https://manual.lubuntu.me/stable/lts which is obviously not valid. Perhaps this one is @teward's fault????

In case I didn't make myself clear, Lyn, I do not envision this as another thing to lump on your plate. I mean, hey, if you want to add to your TODO list, knock yourself out, but you already do so much.

This seems like it would be a nice enhancement to the fantastic manual we already have. I would be willing to help with this project as time permits. I know AntiX / MX linux has a fair bit for video content that Dolphin Oracle put together. It seems to be a well utilized resource for them. I don't think there are too many other distros that have as much content as they do. I think like the current manual this could be something that could evolve over time, continually improving on the last iteration so I don't think we should focus too much about the initial quality.

Thing is I have never edited videos before. I also hate listening to the sound of my own voice.

The plan is that manual.lubuntu.me would automatically redirect to the stable branch.

I was asking more for where https://manual.lubuntu.me/ what to have redirect to. I think almost all of the branches are named that other than LXDE which 18.04 is basically a copy as I could not find an easy way to rename a git branch rather than take a new branch with a new name and delete the old and did not delete the old.

Bump, because I'd like to deploy this on release day if it's feasible.

That's a good idea. What about renaming the old branches to follow XX.YY? We could then follow the existing procedure, and you could go ahead and delete branches when you think it's necessary.

Agreed this is is similar to what I want right now. I mean I don't see the point in keeping old realeases published without support. I really don't think getting rid of the branches in the git tree would be best. I say keep old versions of source in branches around as that is easy if say we end up switching back to an program from a previous release So I don't have to start over from scratch. This is really similar to what I wanted. The only other question is what would just the old manual url link to if say someone had a URL saved to get to it.

I made a Pull Request on Github to fill the content of the release notes a bit. A lot of the content I have copy&pasted from the previous release notes and adjusted some numbers.