tighten compliance requirement for CoC #16
Conversation
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 ml5js#2 (already unlikely to be easy) more complex.
|
Uf, yeah, this is one that I would love to hear from the rest of the team on. The current "take all practical steps" language gives a good faith actor some wiggle room in case there are legitimate reasons that they cannot come into compliance within 30 days. On the other hand, that wiggle room can be abused by bad actors. I don't think there is an empirically right answer to this one - it mostly turns on how we want to structure this for the community. My general inclination on this type of thing is to design in order to make it easy for good actors to be good, but this is one of those situations that at least tests that starting inclination. |
|
Could make it explicit in the CoC rather than the license that, if the CoC
team thinks there is a good-faith reason why 30 days is too soon, the CoC
team can say "not actually in violation, license not suspended, pending
resolution".
…On Wed, Feb 3, 2021 at 9:21 AM Michael Weinberg ***@***.***> wrote:
Uf, yeah, this is one that I would love to hear from the rest of the team
on.
The current "take all practical steps" language gives a good faith actor
some wiggle room in case there are legitimate reasons that they cannot come
into compliance within 30 days. On the other hand, that wiggle room can be
abused by bad actors. I don't think there is an empirically right answer to
this one - it mostly turns on how we want to structure this for the
community.
My general inclination on this type of thing is to design in order to make
it easy for good actors to be good, but this is one of those situations
that at least tests that starting inclination.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFBIPME3OXYEZJLAIRMOQDS5GAZVANCNFSM4XAFOKPA>
.
|
|
As per @tieguy's suggestion, we have moved this to the CoC. It is now explicit that the CoC team can extend the 30 day window in order to accommodate an investigation. |
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.