Replying from my phone.
On Sun, Jan 21, 2024 at 03:12:41PM +0100, Norwid Behrnd wrote:
> @Loren As an sponsored maintainer and hence subscriber to this mailing list, I
> think a subject line with a specific ticket number, package name and -- in the
> particular case -- the acronym RFS would ease to follow up the progress of
> your work. Ideally it were the template reaching level 4 / Find a sponsor[1]
> offers.
I'm not sure what you mean by the above, but the Request for Sponsorship (RFS) bug will not be closed in the changelog, because you create it after you've finalised and uploaded your updated package.
I think Norwid Behrnd is expressing that your upload fixes existing bug[s], so you should close the applicable one[s] from the changelog. This will require a triage of the existing bugs.
> Are you member of the pkg-rpm-team? If not, and if the package now were
> maintained by you, a successful upload to Debian likely might require an
> update of debian/control, in lines of `Vcs-Browser:` and `Vcs-Git:`.
I have sent a request to join the team from the email in the Maintainers
field. I also looked at the Team page, but they reference a non-existent
mailing list on Alioth.
https://wiki.debian.org/Teams/pkg-rpm
It may also be worthwhile to CC people listed in Uploaders if you don't receive a reply in a reasonable amount of time.
I don't plan to move the Git hosting from Salsa. My branches are based
on the latest tip from the repo on Salsa and my goal is that that are
just merged into that repo.
I don't think there's anything wrong with this in principle, and it does celebrate how git is decentralised 🙂 That said, it imposes additional demands on your sponsor (and/or tram member[s]). Long-term, how will this work in practice? Rather than depend on someone to manually pull from non-Debian infrastructure, why not just register for a Salsa account of your own, and then push directly?
Best,
Nicholas