On 17691 March 1977, Lucas Nussbaum wrote:
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.
Other way round makes more sense IMO. Instead of yet another huge group
that needs to be maintained in some way, keep the existing one the only
such large monster. And anyone who put things there and now has a
different opinion can move their package out of that into a different
small group just for that package (or a set of packages). That will be a
way smaller overhead.
--
bye, Joerg
