tighten compliance requirement for CoC #16
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CoC has components that apply to corporate users, and in particular in ways that may clash with entire business models ("Do not ... Use ml5.js to build tools of mass surveillance"). "all practical steps", while perhaps appropriate for a notice requirement, is perhaps an out clause for use that would otherwise require a change in business model (impractical for most businesses!)
This PR tightens the language, in light of that concern.
Note that accepting this PR may make the conversation proposed in issue #2 (already unlikely to be easy) more complex.