Hello! Am Tue, Apr 21, 2026 at 11:32:09AM +0200 schrieb Gabriel Wicki: > At this point I am not sure whether you read the (current) revision of > GCD007. Nobody lets anyone go. The GCD proposed in 007 is without the > discussion period—the content of the (addended) GCD is crafted within > the maintainers collective and neither the report of their activity, nor > the proposal on who should be part of the collective the following year > is bound for discussion. This does not change to what currently is > happening: the maintainers collective decides in what group they > (continue to) work.
Now I am a bit confused, but I think I did read the part on the maintainers in the latest versions; I checked out the pull request and ended up at commit commit 60b95802c96078e9ab9fac248ddbfafeb3e90887 (HEAD, pulls/pr/11) Author: Gabriel Wicki <[email protected]> Date: Mon Apr 20 12:03:43 2026 +0200 007: Whitespace (line length). * 007-teams-special-teams-and-memberships.md: Adjust line length. There it says: "The maintainers collective report about their annual activity and suggest for approval the composition of their team for the upcoming term in a GCD." A GCD is a GCD, with a process defined in GCD 001, and takes a long time. Later it says: "The maintenance team crafts a yearly addendum to a GCD to approve their next terms in the group they feel fittest for the task." which is unclear - above it was a GCD, here it is an addendum to a GCD, but which GCD? What is an addendum to a GCD? What is the process for an addendum, since GCD 001 does not speak about it? If it is a different process from a GCD, without discussion period, this needs to be defined, and given a different name. Andreas
