Understanding the definitions and expectations of our membership processes

[Jordon Bedwell]

Hola,

On Fri, July 29, 2011 11:01 am, Michael Bienia wrote:
> 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?

Why should you not trust that persons judgement unless there is compelling
reason to believe their judgement should not be trusted.  It seems
counter-intuitive to okay them for inclusion and then default on your own
judgement of them by not trusting them without a very good reason to not
trust them.

Yes, it's just fine to review an endorsement they give, like any open
ecosystem would and does currently do, but flat out not trusting their
judgement seems like you feel they don't belong there in the first place
which leads to two questions: Why did you okay them them for inclusion at
all if you aren't going to trust their judgement on skill?  Why would you
okay him/her for inclusion if you have any reasonable doubt about their
judgement on skill?

> 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.