Re: Drafting new rules for GURU

> Prior to joining GURU, a new contributor is required to have at least one (ideally a few) non-trivial contributions reviewed and merged via pull requests or mailing list patches. These can involve new packages or fixes to the existing packages. You should aim for proving that you can commit and process feedback.

I think this is too vague and too daunting. This is the sort of language that typically scares me off from even attempting to contribute, because I'll doubt my ability thinking the thresholds for the given metrics (non-triviality and feedback processing) are really high.

I understand that the intent is to filter people, but I think it'd be nice to give some practical examples, and either soften the language (e.g. "we'd like to know you can handle constructive feedback"), or accompanying this ruleset with a more encouraging first-time contributor guide (doesn't have to be very long). It'd be sad to lose honest contributors to this.