Hi Michael, Am Mi., 26. Juni 2024 um 14:40 Uhr schrieb Michael Pujos <pujos.michael@gmail.com>:
Just curious: what is the rationale for offering that alternate git workflow for maintaining packages vs OBS ? Who would use that and for which reason ?
There's been two hypotheses around that: * It is easier to get drive-by contributions as the general familiarity of git + PR workflow is higher than having to sign up for a separate account on a separate web site having to install a separate tool to submit a change (adding a patch, updating a version) * It eases the maintenance of a package in multiple code streams because branches are a first class feature of git, while it is an afterthought in the custom subversion-like source control system of the Open Build Service We can not really validate point two at the moment as there is only one distribution enabled with git so far. Part of this exercise is to find out whether any of those hypotheses are holding up. Greetings, Dirk