I think this task is a bit too vague to be too useful.

For bindings mostly there's agreement on putting things with the relevant framework and subtasks doing that.

I agree, this is too vague, and therefore not actionable. @knauss do you want to make the task more targeted, or should I (somehow) delete it?

Maybe close it as invalid?

For the bindings point, is it a decision worth mentioning in https://community.kde.org/Frameworks/Policies ?

For T11551 we talked a bit about C++ library guidelines. It probably would make sense to go over stuff like the wiki/documentation to check if stuff in there is still correct/could be improved in a C++17 world