[LG V20 Guides, News, & Discussion] emdroidle:
Indeed it isn't nice. Problem is I looked and [MENTION=5184450]USA-RedDragon[/MENTION]'s work isn't that great. Since you're implicitly asking for specifics, it is time to get into technical detail (sorry to bore anyone who doesn't have the background to understand these criticisms):

First, they did in fact link to their source code on GitHub, here. Should be pretty obvious they've got most of Linux's history in their git repository. One troublesome issue is they uploaded their repository without using GitHub's "fork" feature. As a result it is troublesome to figure out where the code originated from. The start of [MENTION=5184450]USA-RedDragon[/MENTION]'s branch was pretty obvious merely by reading commit messages, here is the last parent commit. In order to find the parent repository though I had to contact one of the people in the history, at which point I learned the parent is here. Nothing malicious here, but annoying nonetheless.

So the very first commit is this. This does accomplish the stated goal, but the problem is there are far better ways to accomplish this! It is better to keep it around since it does help system security, just need to load a different set of policies (such as the ones packaged with the debug kernel).

Then we've got the pretty early commit here. Problem is this commit is an example of one of the canonical things you should not do to! Introducing large binary blobs is very bad for revision control systems. They're designed for handling text files and due to their nature they have to keep a second copy of the data around. Try cloning both repositories and then asking your OS how large they are. The LineageOS repo: 2.5GB; [MENTION=5184450]USA-RedDragon[/MENTION]'s repo: 3GB. 0.5GB for everyone downloading, merely for "convienence".

Commit messages are supposed to give you an idea of what was done and possibly why, so look here. "Build stuff", my what a useless commit message, though I suppose it is better than just "?" All of the commit messages before [MENTION=5184450]USA-RedDragon[/MENTION]'s are at least a full paragraph, none of [MENTION=5184450]USA-RedDragon[/MENTION]'s are more than a single line.

Here [MENTION=5184450]USA-RedDragon[/MENTION] decided to enable compressed swap. Problem is due LG had already taken rather stronger measures on this exact issue. At a shell on your V20 try typing `cat /proc/swaps`. Turns out the swap device /dev/block/zram0 is a ramdisk compressed with LZ4. This is a rather better compression algorithm than the GZIP used for compressed swap. This change will at best have minimal effect, but is very likely to significantly slow your device down if your device gets low on memory.

Then we've got the releases, here and here. Problem is there is something missing; there are no tags! If you click here you won't find any notation on which versions the releases were based on!

I must concede, [MENTION=5184450]USA-RedDragon[/MENTION] did take a substantial step forward by building LineageOS's kernel source and discovering it is able to deal with how the debug bootloader sets up the graphics chip. There is no denying this is a valuable discovery. Having written that, I must still strongly recommend moving off of [MENTION=5184450]USA-RedDragon[/MENTION]'s kernel once someone else puts one out (hopefully I'll have a near-stock build out soon, but life is complicated and things take time).