Juan <[email protected]> writes: > Hi team, > > siso (RFP #1051557, Chromium's Ninja replacement) is ready for review: > https://salsa.debian.org/mendezr/siso > > It uses dh-golang with 80 Build-Depends, partial vendoring of 6 > Chromium/Bazel-internal modules in debian/vendor/ (documentedin > debian/vendor/README.md following the usql pattern), and one patch > removing the Google Cloud metrics subsystem (84 now not needed > unpackaged modules).
Sounds good! Did you consider packaging dependencies instead of vendoring? At least consider asking upstream to properly make public releases of those modules. > I'd like to transfer the following repos to go-team/packages before > uploading to mentors: > https://salsa.debian.org/mendezr/siso > https://salsa.debian.org/mendezr/golang-github-kelindar-simd(ITP#1135383) > https://salsa.debian.org/mendezr/golang-github-kelindar-bitmap (ITP #1135384) > If this is appropriate, could someone grant me access to create > projects under go-team/packages, or fork them from my namespace? The best process that I've learned is that you grant someone in the go team 'Owner' rights to your project, and ask that person to move into the go-team namespace. Then you will have permissions to the new project, and there is no unnecessary forking or duplicate copies of the project, and your old URLs will be redirected. I'm happy to move it this way if you add 'jas' as owner to that project. And could make some lightweight review of the packaging as well. Do you need a sponsor for the upload? /Simon
signature.asc
Description: PGP signature
