Hi, On Thu, 13 Feb 2025, Simon Josefsson wrote: > can sympathize with. But compared to the cost of changing URLs once > every five year depending on which group happens to be healthy, I don't > think it is worth that cost any more. Well, I can certainly sympathize with that. It's why I really believe that we should have a few large teams more than many very small teams. But the actual change of URL is not that impactful with Gitlab since the old URL continue to work when things are renamed or moved properly in Gitlab. I think the pkg-security team has reached the stage where it's large enough for this to not be a concern for the future. > If there was a collaborative package maintainer team that was > all-inclusive, that would fit better with how I would like to work. /debian/ is certainly close to that, but the other side effect is that you have no consistent policy across all the projects. And I do think that there's value in keeping up some consistent policy across all the packages maintained in a team. For the benefit of newcomers and regular contributors. We do have tools to apply those policies in some consistent ways but that (usually) only works if the repositories are in the place where they are expected to be... > doesn't hold underversally. So take this as a mild plea to allow use > of /debian/ namespace for packages maintained by pkg-security. And take this feedback as a mild plea to not lose the main benefit of a team just because you fear URL changes every few years. :-) Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hertzog@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
Attachment:
signature.asc
Description: PGP signature