On Wed, 12 Jun 2024 at 21:32, Russ Allbery <r...@debian.org> wrote: > > Luca Boccassi <bl...@debian.org> writes: > > > But you don't push to snapshot, it's just a backup method, it doesn't > > take any input from DDs (AFAIK? Am I wrong?). Given > > https://browse.dgit.debian.org/ exists and has tons of stuff already, > > and this proposal for tag2upload doesn't exist yet, I gather that dgit > > is already a thing that is used independently of tag2upload? > > Correct. I've been using dgit to upload my packages for years now. The > packages are all maintained on Salsa. dgit push-source (the command to > upload a package) both pushes to the dgit-repos server and runs dput, > along with a few other things including source package construction and > signing. > > (dgit, the command-line tool, is independent of the tag2upload server. > You do not have to use dgit to use tag2upload.) > > > So I don't think this analogy works. One couldn't say "let's remove > > archive.debian.org, just push to snapshot.debian.org", but one could say > > "let's remove salsa.debian.org, just push to dgit.debian.org". > > In what sense could one say that? What do you think pushing to > dgit.debian.org would do? I think you have some confusion here about what > the dgit-repos server is for and what it does, but I'm having a hard time > figuring out the exact source of the confusion. > > If you're saying that if one doesn't care about making work in progress > available, doesn't want pull requests, doesn't want multiple people to be > able to work on a package together, and doesn't want CI, but only and > exclusively wants a Git server to archive a record of what Git trees were > uploaded as source packages, one could use only the dgit-repos server and > not Salsa, then yes, that's true.
Yes, that's the argument - all Salsa features are bad and "bloat": issues are bad, teams are bad, CIs are bad, merge requests are bad, the only thing needed is to push&pull to some git backend, everything else is bad and unneeded.
