Here’s a parallel topic for SIG Build contributors we can also discuss here: container extensibility and collaboration. With regards to “what should be in the containers?”, I am strongly for saying that the “Officially Supported” Dockerfiles should only contain code that the DevInfra team has pledged to commit. We still need to decide exactly what this is, but here are some of the user stories I’ve considered and my own thoughts on whether they’ll get official support, based on matching our current testing needs:

Yes: Build and test on x86 (test targets need better definition)
Yes: Contributor utilities like pylint, clang-tidy rules
Yes: Support currently-receiving-security-upgrades release branches
Needs decision: custom-op functions for SIG Addons, IO, etc. (I want to get backing from leadership to guarantee support)
Needs decision: TF Lite tests / mobile builds (DevInfra is disconnected from this)
No: Other platforms like ARM, PowerPC, etc. DevInfra can’t support this.

I want the Dockerfiles to be good enough such that interested parties could copy the directory into a separate project that they maintain for their special needs (for example: minimized containers, containers for non-x86 platforms, containers for accelerators other than CUDA).
Any thoughts on any of this?