On Wednesday, November 27, 2024 7:19:46 AM MST Colin King (gmail) wrote: > Hi Soren, > > Thanks for offering to sponsor this package. However, is having > packaging hosted in a Git repo necessary for getting the package > sponsored? Although it's a nice to do thing, I've had 24 other packages > sponsored without this requirement in the past.
No, it is not a requirement of Debian. However, it is a personal requirement for any package I sponsor, because it makes collaborative development so much easier (including things like NMUs). I could write a long description of why, and would be happy to do so if anyone has any questions. Otherwise, I might simply point out that there are various discussions about making it either highly recommended for Debian contributions or mandatory (with some strenuous pushback by some Debian Developers, because, of course, the is Debian, and people have strong feelings about their workflows), and some Debian teams do make it mandatory. For example, see: https://lists.debian.org/debian-devel/2024/08/msg00433.html https://salsa.debian.org/python-team/tools/python-modules/blob/master/ policy.rst > Are there any specific instructions on how to host the packaging in Salsa? Let me offer you two recommendations. I will sponsor your packages even if you choose not to use these, but my personal experience is that they make your life as a packager so much better that I often recommend them to people. 1. Use gbp (Git-Buildpackage) to manage the packaging repository. Wrapping your mind around gpb takes a little bit of work. I would offer you two links. One is a basic explanation I wrote previously on Debian Mentors: https://lists.debian.org/debian-mentors/2024/09/msg00057.html The second is the link to the official wiki page: https://wiki.debian.org/PackagingWithGit 2. Enable the default Salsa CI. To do so, follow the TL;DR instructions at: https://salsa.debian.org/salsa-ci-team/pipeline#basic-use -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.