Proposal: Remove "english" criterion

[david-a-wheeler]

We have never required that projects conduct their activities in any particular natural language, and of course we have localized the BadgeApp external interface to a variety of languages. However, in the process of capturing what successful projects do, we captured this SHOULD criterion "english":

The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. [english]

I propose that we remove it. It's only a SHOULD, and it's pretty limited. And yes, English is still widely used. However, machine translation systems have become good enough that the need for this criterion appears less strong to me. Clearly there are some OSS projects (e.g., tax systems) where it's unlikely that English would even be useful.

Under our governance rules, it's easier to drop criteria than add them, since removing a criterion cannot cause a project to lose a badge.

[david-a-wheeler]

@jdossett - thoughts?

[TonyLHansen]

I'm not convinced that machine translation systems are "good enough" yet. Having tried some round trip translations with various texts, I think it's still fraught with danger.

Being a SHOULD doesn't prevent a project from avoiding it.