Hi Dan, On 2023-04-20 09:01, Dan Čermák wrote:
Hi Richard,
thank you for this detailed write-up!
(more inline below)
Richard Brown <rbrown@suse.de> writes:
*snip*
Therefore, the current working plan is as follows:
- All SUSE ALP Products will be built in SUSE's Internal Build Service, using sources that originated from openSUSE:Factory - All packages used to build SUSE ALP Products will be copied to openSUSE's Open Build Service without alteration - All SUSE ALP Products will be copied from SUSE's IBS to openSUSE's OBS with the only alterations being the obvious necessary rebranding - Any future changes to the SUSE's ALP development workflow (eg. the possible future introduction of a git-based workflow for submitting changes into IBS/OBS) would be also introduced for any openSUSE ALP Products
Would you know where the primary development will take place? OBS or IBS?
If it is moved to IBS, then that will make community contributions quite challenging, as they already are with Leap at the moment. Would it be an option that development happens on OBS and the sources are mirrored/copied/submitted to IBS? That's our current workflow for SLE-BCI and I'd say it works reasonably well, albeit I am not sure if it would scale.
For the SUSE ALP Products and the Packages/Containers/Stuff making up those SUSE ALP Products, the primary development will take place in IBS. This is mandatory for the certifications that SUSE require for ALP. Development cannot happen in OBS. There will be no path for community contribution to that part of the SUSE developed ALP stuff in the short term. After discussing with Lubos it is pretty clear to me that the Leap/SLE-BCI style mirroring/copying of submissions absolutely will not scale. Any proper solution isn't just a technical challenge of getting OBS and IBS to copy/mirror submissions and keep them in sync, but also process changes (possibly to both openSUSE and SUSE) to ensure everything is done in a way that be certified when in SUSE's ALP Products. Let me be absolutely clear though, this is NOT ideal, we don't want to keep it this way, I just don't see a plausible solution that can be put in place in time that wouldn't disrupt SUSE's plans for making ALP Products AND make it harder/add more delays to openSUSE being able to make use of SUSE's ALP stuff. However, I do not see this is as the end of the world, because after all, ALP is meant to be adaptable. openSUSE will be able to make it's own ALP Products based on the SUSE ALP stuff. For those openSUSE ALP Products, the primary development will take place in OBS, and have a typical openSUSE-style contribution path. This is playing to the benefits we have with the ALP design, and I expect openSUSE will do an awesome job pushing the 'Adaptability' aspect of ALP to it's limit. The question really though is, given the above, what does the openSUSE community want to build? (yes..I know, I'm repeating the main question from my original post..but we really do need to have some discussions on that else the answer will be 'nothing') -- Richard Brown Distributions Architect SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman