Lucas Nussbaum <lu...@debian.org> writes: > Maybe, instead than retrofitting a policy on the debian salsa group, a > good way to both clarify the situation and allow an opt-in mechanism > would be to create another group on salsa, with rules clearly defined > from the start, and let maintainers decide of the maintenance model they > want for the package they currently maintain. After all it's very simple > to move projects between groups in salsa, and just requires an upload to > update the VCS fields.
This would have my vote. I moved my packages to the debian namespace to ease git access for others, also for the case that a package might have to be passed to another maintainer. At the time the debian namespace was introduced, I've read nothing about implied upload rights. If I had, I wouldn't have put my packages there. It was only later that some people wrote about supposed upload rights, but I never saw a source cited for the claim. - Carsten
