I am proposing some new functionality for metatools called "community logging", or "project-oriented logging".

When metatools does a production tree regeneration, it does an exhaustive scan of the tree and also detects and logs any errors to stdout and maybe a global log. While this works for ME, since I can view these logs since they run on a machine I control, this doesn't really work for the project-oriented structure we are building in Funtoo.

Ideally, all metatools logs would be split up by release and kit, and made available publicly over HTTPS, so that project maintainers can directly see any errors or warnings that were logged during production tree regens and other phases of Funtoo tree generation and maintenance. Then these tasks can be fired off via a cron or other method, and generate logs of interest for the entire project.

This is more than just a logging improvement. It can very well be the foundation for a Funtoo version of "repoman" (the original tool I created for QA in Gentoo). The only difference is that this evolution would be more suitable for CI and the nature of the tree in Funtoo. But I think this would also be much more convenient than requiring everyone to run repoman locally.

Eventually, we can launch a "beta" tree and we can require error-free logs for changes to be incorporated into mainline Funtoo. So there is a path forward here for a very thorough QA infrastructure for CI.