>In addition, the team is working with renowned art historian and curator Dr. Lowery Stokes Sims, who is providing additional mentorship and professional development.
In art as in politics - nothing says grassroots like the additional mentorship and professional development by a renowned establishment member.
I recently implemented my own npm vulnerability audit tool for the CIO department of a major org - it just adds 'vulnerability' in red next to any npm-based project in their spreadsheet.
Practically speaking, that's the only approach that can.
Although it's often hard to tell, most software developers aspire to being treated like professionals rather than specialized serfs, and part of being a professional is accepting responsibility for your work.
Of course it doesn't preclude holding their employers responsible as well.
This is a losing proposition that will only lend credence to the inherently violent opt-out approach to data collection.
Instead how about a do-not-hire-or-collaborate-with registry of the individual contributors participating in projects that employ those tactics and see how they like trying to opt out of it.
Hmm, I'm pretty sure that a software engineer developing safety-critical firmware for embedded medical systems does not need to know anything about Apache Kafka. Or a game developer. Or a web frontend developer. Given the title it's surprising how many software engineers can in fact go through life and career without ever knowing anything about Apache Kafka.
>In addition, the team is working with renowned art historian and curator Dr. Lowery Stokes Sims, who is providing additional mentorship and professional development.
In art as in politics - nothing says grassroots like the additional mentorship and professional development by a renowned establishment member.