Most of that conversation is here - https://gitlab.gnome.org/World/ShellExtensions/extensions-rebooted/-/issues/1
and thank you for volunteeering!! I’m also working on some new onboarding concepts in regards to this.
So there are two things. One is release engineering - which is when a new gnome shell release happens and then we test the extensions against it as part of the release process. The idea then is to test all the extensions and find out which breaks and then setup a system to alert extension writers that their extension is broken and needs to be fixed as part of compliance to be listed on extensions.gnome.org. That isnt’ really in the works yet because we really need to focus on the infra.
The second and most active work now is build out of the infra to test extensions. That means we want to have a ci container that will run the stable version of gnome-shell and test the extension against it. Right now that testing is just a smoke test of ‘does it load’, but as we understand more we can start making it more intelligent - this is where community needs to jump in and help. I think building these tests might be a bit tricky. The other thing is that we want to automate reviews as much as possible.
The current status is that I have a container that can run gnome-shell (using distro version) and it can load and unload extensions headless. From here we need to:
- build a docker container that will do the same thing (I’m using podman/buildah) and that will recreate everything I need to run gnome-shell. The tricky bits are being able to run dbus-session in the container and then finding a way to launch gnome-shell with it.
- some thoughts on the architecture
This is a real fun project with a great payback and a time saving for GNOME. Really excited to work on it.