Hi Wouter, * Wouter Verhelst <wouter@debian.org> [2022-10-07 13:37]:
I've given this some thought over the past few days, and have come up with something that I believe might work, and I would like to submit it as a proposal to see what others think.
Great idea, thank you for your thoughts! It reminds me of the Debian Enhancement Proposals [1], which aim to solve a similar problem. I have only one remark at this point: By definition, a project has a limited scope and time frame, so at some point it has to end. For things like /usr-merge, or any other transition, this is a good fit. Adding features to Debian which require permanent additional maintenance is more akin to supporting a release architecture. The associated project would be the "incubation phase" where said feature gets introduced and its viability proven, and one success criterion would have to be the formation of a team that commits to the required maintenance work for the future. Similar to the release architectures, features should be evaluated at release time and discontinued if the team can no longer provide the required support. Cheers Timo [1] https://dep-team.pages.debian.net/ -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
Attachment:
signature.asc
Description: PGP signature