Hello Andreas, I've got some reservations about some of your package salvaging work, in particular how you've been using the ITS process (I've expressed these on d-devel and won't repeat them here). This is why I am not comfortable granting you full access to the team's repositories.
If someone approached the team from a different angle (i.e. because they were specifically interested in CL in Debian) they would receive ordinary salsa group membership, instead of repository-per-repository access. So I would rather we do things package-by-package for now. Let me go through your items: Andreas Tille [15/Jan 6:25pm +01] wrote: > While dh-lisp has moved to the Salsa team space, its Vcs-* fields > haven't been updated in an upload yet. This makes the move invisible to > those who don't check Salsa before an NMU. To fix this, I'm volunteering > to perform a team upload (or NMU, whichever you prefer). I've also > attached a commit to upgrade the package to Standards-Version 4.7.3, and > I'm happy to submit this as a MR at your preference. Please go ahead and submit an MR. I will merge it and then do the upload. > Additionally, cl-regex (Bug #1117525) has reverse dependencies that > prevent its removal. I'm happy to create a repository for it on Salsa to > ensure it remains maintainable. Should I place this in the Common Lisp > team space, or would you prefer it move to the Debian team space if no > specific uploader steps forward? How about looking into replacing the reverse dependency, first? It might be very easy. Let's assess that before putting the package on further life support. > Streamlining Team Contributions > > On a broader note, I've found the contribution workflow for the Common > Lisp team a bit restrictive compared to other Debian teams. Currently, > permissions seem to be granted on a per-repository basis (as was the > case when I worked on cl-launch), which can be a time-consuming barrier > for contributors. > > Would the team be open to granting broader Salsa permissions to > experienced packagers? This "low-threshold" approach used by many other > teams encourages more proactive maintenance and reduces the > administrative burden of asking for access for every individual > repository. Addressed above. > Updating unmaintained cl-* packages > > Finally, there are about 35 cl- packages* currently associated with > Dimitri Fontaine that appear to be unmaintained, with none, outdated or > inaccessible Vcs-Git fields. I'm willing to help clean these up and > clarify maintainership. > > Before I start, I'd like to know if the Common Lisp team would prefer to > keep these within the team (with the necessary permissions to work on > them effectively) or if I should look into migrating them to the Debian > team. Can you list the packages, please? Have you checked that they actually don't have repositories under the team's salsa group? There might be repositories there, in which case nothing special is needed. -- Sean Whitton
