Reconsidering the open access model to GURU

Hello, everyone.

Given that we had some problems within GURU recently (nothing serious,
but still troubling) made me keep wondering recently if our fully "open"
access model is the right approach.  While I'd like GURU to remain open
to people and have a low entry barrier, I don't think it's exactly
healthy to give people access only to cause conflicts and have it
revoked a short while afterwards.  Given the more general situation
around FLOSS nowadays, I'm also having more and more doubts when
handling access requests.

What I'd like to propose is that going forward, _before_ requesting push
access to GURU, one has to get one or more pull requests or patches
merged first.  They would be reviewed by existing GURU members, and
referenced in the access request.

Just to make it clear, I don't want to raise the bar significantly.  The
goal wouldn't be so much to expect perfect commits, but rather to get
one to learn the rough workflow and to make sure that they can respond
well to feedback.

That said, I'd like GURU to remain mostly self-maintained, so the
proposal is mostly aimed at feedback from the existing GURU members.

WDYT?

-- 
Best regards,
Michał Górny

-----BEGIN PGP SIGNATURE-----

iKQEABYKAEwWIQQcFD0bEK7NPNmWHtiOMjR69AVa6AUCakFBHhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDISHG1nb3JueUBnZW50b28ub3JnAAoJEI4yNHr0BVro
6ecBANWdPuOxRQfc6qgv3FG6dnbrvucUYfOqzVNbEmHP58s6AP9fhrqDT4KqbIf6
jBkbB/HlAd7Xobvl5Z+QvaQHauz1BQ==
=C7bD
-----END PGP SIGNATURE-----