(#ubf3aba@twtxt) @prologic@twtxt.net What do you think about using gitolite and cgit, with a mailing list for patches?

I don’t know if I should set it up, I know that for my personal projects
it will be sufficient, but I don’t know how well it’d scale with a
pubnix-like system. I know the linux kernel uses gitolite but I don’t
know, as the use by us would be completly different, it’d be more suited
to giteaforgejo, (because they offer the ability to make
organizations), but I also dislike not having the gitolite ui in gitea,
so I might think about making custom scripts to let you make projects
(that are outside your user namescope, but assigning you privileges, (I
think I’d need to or a) make the script directly add the projects, thus
making me git pull the gitolite-admin repo, but I’d alredy have to do
that as I’d use sskm, or b) Having the requests come in to my mailbox
and I manually add their respective config block to gitolite’s config in
the gitolite-admin )

@prologic@twtxt.net I see the threadings properly on my email client, seems weird (I used the fork-conversation feature so maybe that’s why?)

I have fixed the weird tags thing, I removed it from the twtxt manually, I don’t think it’ll affect anything? I wrote a patch for jenny (twtxt to mbox converter), and I did test it in a sense in that messsage, because jenny wasn’t making RFC compliant emails and aerc in newer versions needs the emails to be compliant, else it doesn’t seem to be able to do threading.