| 1 |
It is, if that decision is being made by a random developer being asked for |
| 2 |
an endorsement and not a recruiter. |
| 3 |
|
| 4 |
That is why I wanted to emphasize that if we DO use GPG endorsements, we |
| 5 |
bear in mind the practical realities. |
| 6 |
|
| 7 |
On Thu, Jan 5, 2017 at 2:40 PM, Kristian Fiskerstrand <k_f@g.o> |
| 8 |
wrote: |
| 9 |
|
| 10 |
> On 01/05/2017 11:28 PM, Raymond Jennings wrote: |
| 11 |
> > That said, how do we make sure that new developers don't get screwed out |
| 12 |
> of |
| 13 |
> > devship by politics? Can we make sure that someone isn't going to |
| 14 |
> refuse a |
| 15 |
> > GPG endorsement based on, say..."I know who you are and I believe you are |
| 16 |
> > who you say you are, but I don't like you/think you stink as a |
| 17 |
> > developer/whatever else so I'm not going to endorse you anyway"? |
| 18 |
> |
| 19 |
> Arguably, from this point of view, you would consider the signature an |
| 20 |
> endorsement from existing developers. If they don't believe it is a good |
| 21 |
> fit for the community, is it really a bad thing? |
| 22 |
> |
| 23 |
> -- |
| 24 |
> Kristian Fiskerstrand |
| 25 |
> OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 26 |
> fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
| 27 |
> |
| 28 |
> |
Archives