So, that was my change.  Justin called that section “Be careful expressing surprise”.  I felt that that was too general and might result in rules-lawyering (“You mean I can’t be surprised that GNU finally gave up on Hurd??!!”).  I was attempting to use ignorance in the literal sense of the word.  I realize it carries a lot of stigma, but I was out of ideas.  I’ll rephrase and give you an updated pull request addressing this and the other 3 things.

On Feb 26, 2014, at 8:25 PM, Adam Glasgall <notifications@github.com<mailto:notifications@github.com>> wrote:


In code-of-conduct.txt:

> @@ -27,7 +43,7 @@ better, but please don't do so in a way that suggests that they're bad
>  person for doing what they did, that they should have done better, or
>  that their contribution wasn't worth making.
>
> -No feigning surprise
> +Avoid expressing surprise at ignorance


This reads as just plain insulting to me. We don't want people to feel like they're ignorant because they don't know about some obscure technical detail!

—
Reply to this email directly or view it on GitHub<https://github.com/aglasgall/sipb-code-of-conduct/pull/4/files#r10108705>.