Hi John, John Kehayias <john.kehay...@protonmail.com> writes:
[...] > I'll open a branch merge request issue later today as per new > procedure for QA. Though I believe that only builds 2 branches, which > is occupied at the moment. Or can someone set a separate build job > specifically for mesa-updates, especially if we think it is a good > idea to have this going forward? Do you already have admin access to Cuirass? We can issue client certs for team members needing to create branches on it or restart builds there, etc. >> Do we want a "Mesa team" or something a bit larger? Not sure what >> exactly, since "graphics" is perhaps too broad. Happy to help >> spearhead the Mesa front for Guix (the very package that got me first >> involved in the patching process). >> > > This is still a good question I think, of how we want to have a > team(s) to handle things like xorg, wayland, mesa, and related > packages. They are a bit all over the place in terms of scope and what > they touch. For now I'd like to go ahead with a regular mesa-updates > branch since that sees regular releases and is pretty self-contained > currently. It seems a 'desktop' team could make sense, covering some of the things listed here that makes sense / are already well separated in modules in Guix to avoid being added to two teams: https://www.freedesktop.org/wiki/Software/. -- Thanks, Maxim
