Hello, On Wed 12 Jun 2024 at 06:50am +02, Ansgar 🙀 wrote:
>> THE DESIGN & IMPLEMENTATION ARE LATE-STAGE >> >> We wish to be clear that tag2upload can be deployed without *any* >> code changes to dak. It just needs to be given a suitably trusted >> key, very similar to how buildds have trusted keys. > > And we also remove the Debian Maintainer role as dak would no longer > know who uploaded the package? Debian is larger than only Debian > Developers. > >> Should this GR pass, then the tag2upload project will be unstuck, and >> could be deployed in a matter of months, and the source-only uploads >> of >> as many of us who want it can become just 'git debpush' and done, >> without any other workflow changes or learning. > > If only one could use regular git instead of a custom, non-standard VCS > built on top of Git that makes some workflows impossible and team > maintenance harder by not supporting publishing intermediate work. :-( Russ already replied here, but let me say unambiguously that - we are not proposing changing anything about DMs; and - we are not proposing forcing any non-standard VCS on anyone. tag2upload already supports most existing workflows (including the one you yourself prefer, where only debian/ is committed to git). We would not be proposing this if we were asking people to stop using gbp or something. That would not be a valuable contribution to Debian. -- Sean Whitton
