There is some nuance to this. Adding comments to the stated goal <i>"Everyone who interacts with Debian source code (1) should be able to do so (2) entirely in git</i>:<p>(1) <i>should be able</i> does not imply <i>must</i>, people are free to continue to use whatever tools they see fit<p>(2) Most of Debian work is of course already git-based, via Salsa [1], Debian's self-hosted GitLab instance. This is more about <i>what</i> is stored in git, how it relates to a source package (= what .debs are built from). For example, currently most Debian git repositories base their work in "pristine-tar" branches built from upstream tarball releases, rather than using upstream branches directly.<p>[1]: <a href="https://salsa.debian.org" rel="nofollow">https://salsa.debian.org</a>
Oh, yes. This seems like nothing short of necessary for the long term viability of the project. I really hope this effort succeeds, thank you to everyone pushing this!
<a href="https://archive.ph/vp6rp" rel="nofollow">https://archive.ph/vp6rp</a>
Now if a consequence of that could be that one (as an author of a piece of not-yet-debianized software) can have the possibility to decently build Debian packages out of their own repository and, once the package is qualified to be included in Debian, <i>trivially</i> get the publish process working, that would be a godsend.<p>At the moment, it is nothing but pain if one is not already accustomed and used to building Debian packages to even get a local build of a package working.
The problem is that "once the package is qualified to be included in Debian" is _mostly_ about "has the package metadata been filled in correctly" and the fact that all your build dependencies also need to be in Debian already.<p>If you want a "simple custom repository" you likely want to go in a different direction and explicitly do things that wouldn't be allowed in the official Debian repositories.<p>For example, dynamic linking is easy when you only support a single Debian release, or when the Debian build/pkg infrastructure handles this for you, but if you run a custom repository you either need a package for each Debian release you care about and have an understanding of things like `~deb13u1` to make sure your upgrade paths work correctly, or use static binaries (which is what I do for my custom repository).
They could take a look at how pkgsrc [1] works.<p>[1] <a href="https://www.pkgsrc.org/" rel="nofollow">https://www.pkgsrc.org/</a>