Understanding the definitions and expectations of our membership processes

[Michael Bienia]

On 2011-07-27 12:55:08 -0700, Chase Douglas wrote:
> Imo, What we should be looking for is two-fold:
> 
> Packaging:
> 1. Has the applicant properly worked on packages in the past?
> 2. Is the applicant aware of the limits of their packaging competency?
> 3. Does the applicant seek out guidance when confronted with packaging
> they are not competent with?
> 
> (Note that questions 2 and 3 should be answered through endorsements.)
> 
> Overall Trust:
[...]
> 2. Do endorsements provide positive feedback about the trustworthiness
> of the applicant?

This leads to the next question: how much do you trust the person
writing the endorsement?

Of course I trust endorsements from long-standing dev members with a
great reputation where I trust their ability to judge the packaging
skills and trustworthiness of the applicant. But should I apply the same
trust to e.g. a dev member who got accepted himself a month ago?

In most cases all I've got are a couple lines in a endorsement from
persons I've worked with to different degrees and who have a different
amount of reputation. As I've never met anyone from the dev community in
person till now, it makes it harder to build up a trust relationship to
them.

Michael