This is one of the larger ones, so it is expected to take longer. I think I did manage to get some stuff simplified already (see earlier message), but I'm still not that satisfied with the result. I also think that the code itself makes poor use of available stuff in RCM to begin with, like the html class or the ::gettext() method in the plugin, so I will probably look into that. Stuff like that is a lot more draining than regular cleanup, though, so I'll probably keep it on the side and do a little every now and then. It would definitely help to have the permission to add methods to that class since there are a LOT of repeated statements. For now, I will keep a look out for existing methods that I can call in.
PR #7 is a good example for something that Thomas worried about earlier - I didn't see a commit coming in concerning a plugin that I was working on two days ago. I did a local merge of those changes and pushed them upstream to the PR, so everything is fine there. Not sure whether that was understood earlier, but it is of course primarily my responsibility to keep up with commits and make sure a merge is straightforward for you guys.
The next couple of days, I won't have as much time for cleanup, so I would appreciate if we could use that brief timeout to discuss the finer points and have some final decisions going forward. For smaller stuff, I could probably do quick adjustments to follow what was decided - that would help maybe accepting the first PR(s) into the codebase. Not to be too pushy here, of course, just would appreciate seeing actual confirmation that the work I'm putting in really will end up going somewhere ;-)