1  rOpenSci & Our Community

A guide to help people find ways to contribute to rOpenSci

1.1 Our Mission

Our work is driven by our vision and mission.

rOpenSci fosters a culture that values open and reproducible research using shared data and reusable software.

We do this by:

  • Creating technical infrastructure in the form of carefully vetted, staff- and community-contributed R software tools that lower barriers to working with scientific data sources on the web
  • Creating social infrastructure through a welcoming and diverse community
  • Making the right data, tools and best practices more discoverable
  • Building capacity of software users and developers and fostering a sense of pride in their work
  • Promoting advocacy for a culture of data sharing and reusable software

Our goal is to build confidence and a sense of belonging for people of all backgrounds, particularly those who might not see themselves as software developers (as many scientists may not!). We do this through building trust and establishing shared norms for working openly, leveraging and creating open source software and resources that support open, reproducible science.

Everyone in the community, no matter how accomplished they are in their own specialty, comes with a mind open to learning from, with, and for each other. We learn from others by using their code and documentation, their blogs and tutorials, their talks and webinars. We learn with others online through Twitter, discussion forums and Slack channels, and in person through coding clubs, hacky hours, meetups, workshops and conferences. And we learn for others by writing tutorials and blogs about our own learning processes, or adding or fulfilling feature requests, which we can then contribute back to the community.
Julia Stewart Lowndes in “Open Software Means Kinder Science”

1.2 Our Community

Our community is our best asset! Without the secret sauce that is the Humans of rOpenSci, we’re just a lot of (really good) packages and processes. Our community is an ephemeral thing. It’s everywhere and nowhere. It’s people who believe in our mission and share our values, and have a mindset for learning, improving, and innovating together. It’s people who prioritize open, reusable, and reproducible research software while also prioritizing creating inclusive spaces through empathy and building trust. There are no stupid questions at rOpenSci; everyone appreciates the diversity of expertise and entryways to coding in this thing we love called R.

The rOpenSci community is a self-identifying group composed of users and developers of R software tools who, together, contribute to the technical and social infrastructure for open and reproducible research. Our specific focus is on software and best practices that lower the barriers to working with scientific data sources. Community members are people who use, cite and share use cases for rOpenSci packages, attend or present in our Community Calls, write a post for our blog, participated in an rOpenSci unconf, or in our research domain focused communities like rOpenSci-Antarctic and Southern Ocean Research, answer questions in our fora, actively participate in the life of an rOpenSci project reporting problems and recommending or implementing solutions, contribute to, or maintain a package, or participate in rOpenSci peer review as a reviewer, author or editor.

Having a diverse community is important to us. We welcome anyone dedicated to making their science more open and supporting others in that pursuit, no matter their technical expertise, career stage, or work sector. Further, we welcome people of all backgrounds, including but not limited to any sexuality, gender identity, and race. We are anti-racist. We recognize that communities are not inclusive by default, particularly as they grow: they require deliberate attention. We are all supported by rOpenSci’s Community Manager and a Code of Conduct that has clear guidelines for behavior and reporting, and is enforced by a committee including rOpenSci staff and an independent community member.

1.2.1 Humans of rOpenSci

In this section we point to groups of people with various formal and informal roles in our community. This gives some transparency, may help people “recognize themselves” in some roles, and provide a foundation to allow folks to reach out to others to learn about making contributions.

rOpenSci was founded in 2011 by Karthik Ram, Scott Chamberlain, and Carl Boettiger, ecologists who were motivated to make scientific data retrieval reproducible.

Staff are:

Karthik Ram (Executive Director), Jeroen Ooms (Lead Infrastructure Engineer), Yanina Bellini Saibene (Community Manager), Mark Padgham (Software Research Scientist), Maëlle Salmon (Research Software Engineer), Steffi LaZerte (Community Assistant) and Stacey Dorton (Administrative Manager) .

Scott Chamberlain (Technical Lead) and Stefanie Butland (Community Manager) are Staff alumni.

Strategic Advisors

Noam Ross (Software Review Lead), Carl Boettiger (University of California, Berkeley), Jenny Bryan (Posit) and Rich FitzJohn (Imperial College London) volunteer their time.

Software peer review Editors

Karthik Ram (Executive Director), Maëlle Salmon (Research Software Engineer), Noam Ross (Software Review Lead), Anna Krystalli (Research Software Engineering consultant / Data Scientist), Mauro Lepore (2 Degrees Investing Initiative), Laura DeCicco (USGS), Julia Gustavsen (Agroscope), Emily Riederer (Capital One), Adam Sparks (Department of Primary Industries and Regional Development), Jeff Hollister (US Environmental Protection Agency), Rebecca Killick (Lancaster University), Paula Moraga (King Abdullah University of Science and Technology), Toby Hocking (Northern Arizona University), Emi Tanaka (Biological Data Science Institute, Australian National University) and Jouni Helske (University of Jyväskylä, Finland) volunteer their time.

Scott Chamberlain (Technical Lead), Lincoln Mullen (George Mason University), Brooke Anderson (Colorado State University), Melina Vidoni (RMIT University), Ben Bolker (McMaster University), Stephanie Hicks (Johns Hopkins University) and Leonardo Collado-Torres (Lieber Institute for Brain Development) are Editor alumni.

Read posts introducing Laura DeCicco, Julia Gustavsen, Mauro Lepore, Brooke Anderson and Melina Vidoni, and Anna Krystalli and Lincoln Mullen. We occasionally recruit guest editors for some package reviews.

Headshots of the rOpensci team

Get to know some of the more experienced folks in our community by reading the .Rprofile series of posts for which Kelly O’Briant interviewed Mara Averick, Jenny Bryan, Julia Stewart Lowndes (with assistance from Sean Kross), Karthik Ram, Noam Ross, Julia Silge, and David Smith.

Over 150 people have reviewed 135 packages from 803 authors!

More than 35 people have presented in our Community Calls attended by people in more than 25 countries.

You can get to know some community members by reading the blog posts and tech notes they’ve written about their packages, their reviewer experiences, the Community Calls they’ve presented in, or their career paths in R. We have an authors page on our website that allows you to find these people by name. The authors page does not yet include rOpenSci package authors.

Screenshot of the rOpenSci authors page showing thumbnails of author avatars next to their names

Many of rOpenSci’s tools are developed by practicing scientists and other researchers who foster strong communities among users and developers in their research domains and openly share their expertise in discussions of best practices.

Many in the rOpenSci community participate in related organizations and communities like R-Ladies, The Carpentries, Latin American R community, the MiR community for underrepresented minority users of R, AfricaR, and Bioconductor.

We believe in giving credit to people for their contributions and sharing our gratitude. Our Thank You, 2019 post, acknowledging individual contributors, is one example of how we do that. For package authors participating in software peer review, we encourage “gratitude through semantic metadata” with the option to acknowledge reviewers in the package DESCRIPTION (with reviewers’ consent).

1.2.2 The special case of rOpenSci unconfs

Between 2014 and 2019 we held in-person hackathon-flavored unconferences - five in the US and four in Australia. The “rOpenSci unconf” became a place where people met, created and developed projects together, and got to know each other. You can get a feel for our unconfs by reading blog posts about the events and projects and by listening to the Credibly Curious podcast episode recorded during ozunconf18 by Nick Tierney and Saskia Freytag. Through these we fostered a community of trust that functions online effectively and with kindness. Our unconfs empowered many participants to run their own local unconferences, make new projects happen, build new communities, build relationships that led to collaborations and career moves. Perhaps the biggest impact of rOpenSci unconfs was on peoples’ confidence and their perceptions of the value they each bring to the world of R in open research.

Rest assured, we’re pondering how to continue building this trust network through collaborative online events.

The rOpenSci model has contributed much hidden skills and relationship infrastructure that has helped #rstats flourish. It’s been a delight to participate in this and see people that got a start at an unconf gain confidence and grow into heavyweight community contributors and leaders over the years.
Miles McBain on Twitter

My life took a turn thanks to rOpenSci - the community I was welcomed into there gave me deep friendships, new skills & confidence to get out of my comfort zone. And the #rstats world as a whole is better for rOpenSci’s existence.
Jennifer Thompson on Twitter

Group photo from unconf17 showing a crowd of people waving at the camera; photo credit Karthik Ram