Re: Proposing commit access for 'unmatched-paren'

[bokr]

Hi,

TL;DR: IMO commit access is too dangerous to grant on the basis of
appreciating help, and/or workflow convenience.

Trusted committers are defenders of FLOSS.

There must be very strict trust requirements for commit access
or FLOSS will become vulnerable to "mistakes" with plausible denial,
like over-eagerness to help, oops, introduced by anti-FLOSS grinches.

Temporary introduced problems, even if not dangerous, work as a form
of denial-of-service attack on the development process itself.

They also promote a not-ready-for-production-use view of the whole project,
despite the great sucess and adoption stories.

No one is perfect, so there will be dumb mistakes to forgive,
but IMO recruiting committers should be thought of as recruiting
defenders of the holiest treasure of s/w.

On +2022-11-15 10:32:45 -0800, Felix Lechner wrote:
> Hi,
> 
> As a new user, I needed lots of help. I also use software that is not
> packaged in Guix.
> 
> In preparing my patches for submission I relied extensively on the
> guidance so generously offered by the IRC user 'unmatched-paren'. I
> thoroughly appreciated their advice, both on the technical as well as
> on the human level.
> 
> Now I learned that 'unmatched-paren' would like to request commit
> access to the Guix repository, but they were humbled by their own
> uncertainty on how to illustrate their value. I then offered to write
> this letter.
> 
> Please consider 'unmatched-paren' for commit access. Thank you!
> 
> Kind regards,
> Felix Lechner
> 
> P.S. Anyone who reads this and agrees with me, please chime in by
> replying to this message. Thanks!
> 
--
Regards,
Bengt Richter