R-Ladies Global's disapproval of DataCamp

This blog post is a slightly extended version of the official statement the R-Ladies Global organization made via Twitter, in a form that is easier to share. The views expressed here are the views of the R-Ladies Global Team signing at the end of this post and do not represent the R-Ladies community at large.

Why we condemn DataCamp’s handling of sexual assault

We are very disappointed by the way DataCamp handled the sexual assault of an employee by a C-level executive. We strongly support the target who is a member of our community and condemn DataCamp for their lack of accountability and transparency around this issue. As remarked by no_reply, DataCamp “quietly published a “community” post, in which they admit an executive sexually assaulted (“uninvited physical contact”) an employee.”

We applaud the collective action from the DataCamp instructor community for pushing for this accountability and transparency, with countless hours of working with the assault target, DataCamp employees, executives, content developers, and members of the R Community at large. As explained by Erin LeDell, “After many months of collective negotiating by the instructor community to demand more transparency & accountability, [DataCamp] still did nothing. Their public announcement is a response to a letter we sent to DataCamp one day prior, signed by over 100 DataCamp instructors.”.

We are not satisfied with the response from DataCamp. As underlined by Julia Silge and Mara Averick, the post used “details in victim-blaming ways”.

How could you stand up for more accountability?

If you are unsatisfied with DataCamp’s actions and response, you could use your voice and your wallet to vote for more accountability. Below we have summarized ideas about how you can show your disapproval of DataCamp’s response, as collected from a thread started by Jesse Mostipak, with contributions from Chris Engelhardt, Laura Ación, Bruna Wunderwald, and Erin LeDell.

  1. Cancel your subscription.

  2. Cancel your organization’s subscription.

  3. Remove links/recommendations to use DataCamp from your material.

  4. Stop developing content/lectures for them. Folks who are not customers can alter behavior as well.

  5. Take your DataCamp stickers off your laptop/car/water bottle/ etc.

  6. Just say “No” when they ask you to do a podcast.

  7. Don’t accept DataCamp as a sponsor of events you organize.

  8. Delete your account (even if you don’t have a paid subscription anymore).

  9. Remove your tweets containing “DataCamp" by searching DataCamp from:@youruser (replace @youruser by your own handle) in Twitter search and deleting the old tweets that endorsed them in any way.

  10. Unfollow Datacamp from social media like Twitter, Facebook, etc.

  11. If you are working on a course or project for DataCamp, you can put your work on hold until you feel that appropriate and sufficient action has been taken on behalf of DataCamp.

These are ideas of what you could do. It is up to you to decide what you want or can do, given your personal situation.

We feel for anyone who finds themselves in a difficult situation regarding their involvement (whether as employees or content developers) with DataCamp. Please be assured that our criticism is directed at the leadership team of DataCamp who made these decisions and who have the opportunity and power to rectify this situation.

Any women or gender minorities who want to discuss this matter (or any other) with other R-Ladies, please join our community slack.

Let’s keep working on a safe community for everyone!

The R-Ladies Global Leadership Team (Gabriela de Queiroz, Hannah Frick, Erin LeDell, and Claudia Vitolo) with Laura Ación and Maëlle Salmon (members of the R-Ladies Global Team)

[Update] Other posts and tweets from the community about DataCamp

`An open invite to all #datacamp instructors (and others willing to help): If you have (or know of) open source blogs/vignettes/materials that can stand in for particular DC courses/content, please post them in this thread. I’ll aggregate and make a GitHub repo. #rstats #python— Chris Engelhardt (@EngelhardtCR) April 12, 2019


Author: R-Ladies Global Leadership Team

This post was last edited on 26 June 2024 with the message"Add new prospective organizers of a new chapter in Zagreb, Croatia (#328)"