Hi 45mg,
45mg <45mg.wri...@gmail.com> writes:
There are many possible consequences of this. One is that GCDs
like this
one would be seen by fewer people, so there would be less
useful
discussion and feedback. And in general, people outside of a
small
circle of old contributors already subscribed to the lists
will not
participate in, or even be aware of, core community
discussions.
So, I do feel that this is necessary to discuss, as one of the
likely
drawbacks (or opportunities!) presented by this GCD.
I’ve had good success in professional settings with a PR workflow
for this kind of thing. If you have a repo with the GCDs, new
ones can be added with a PR to the repo, and discussion can take
place by leaving comments on it. It was also beneficial to have
the discussion and output of prior discussions shares, as context
about current systems was easy to find.
These were all internal engineering departments with <100
programmers, so I’m not sure how well it’d scale to a project the
size of Guix. I’ve also noticed that when fully bought into forge
systems, PRs often become the hammer that solves every problem,
and this could arguably be a stretch -- certainly I have seen very
inadvisable things managed through PRs. But in this case, I think
it provided some value and may be worth considering in the future.
-- Ian
