-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider addressing relationship with Google in CoC #2
Comments
I support the impulse to be explicit about this. I am not entirely sure that the CoC is the best place for it (although I am not entirely sure that the CoC is not the best place for it either...). I suspect it makes sense to draft the language first and then figure out the best place for it to live. |
I wonder if maybe in our Acknowledgements/Sponsors section it would make sense to have some notes there that parse some of these ideas. I have the feeling that there's a lot of layers to unpack, particularly in the case with Google as a large corp entity > Google Brain > Google PAIR project > TensorflowJS team. Then there's Creative Lab which is a whole different island/onion with different layers in relation to the org. In any case, I think all parties would benefit from the clarity on what our relationships look like in general. |
After reading our CoC, I can imagine myself/someone asking: "This is a statement about ml5.js's commitment to AI ethics, but they work with Google and use Google technology. What is ml5.js's perspective on how Google conducts itself regaring AI ethics, or is this just an extension of Google's concerning approach to AI ethics?" I also think it's important to discuss this in the aftermath of the treatment and firing of Timnit Gebru (who used to be a leader on the AI Ethics team at Google). To me, this conversation about sponsors and how they influence our values might makes sense to be included in or linked in the "Overview" section of the CoC document, where we make statements about what we as a team believe. |
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.
I believe that this Code of Conduct could be improved by considering ml5.js's relationship with our sponsor Google. ML work that Google has done (or may do in the future) possibly falls outside of the domain of the uses we support for ml5.js. Highlighting the contradiction/complexity in this document could be a helpful way to get ahead of confusion. It would also be helpful to clarify what strings are attached with their sponsorship of this project, or possibly with any of our sponsors.
The text was updated successfully, but these errors were encountered: