rOpenSci 2019 Code of Conduct Transparency Report
In January 2019, we announced the release of rOpenSci’s Code of Conduct version 2.0. This includes a named Committee, greater detail about unacceptable behaviors, instructions on how to make a report, and information on how reports are handled. We are committed to transparency with our community while upholding of victims and people who report incidents. Our Code of Conduct applies to all people participating in the rOpenSci community, including rOpenSci staff and leadership.
rOpenSci Code of Conduct Annual Review
One year ago, we released our new Code of Conduct. At that time, the Code of Conduct Committee (authors of this post) agreed to do an annual review of the text, reporting form, and our internal guidelines. We have made one change to the Code of Conduct text. Because some people who have experienced abuse prefer not to label themselves as a victim, in “We are committed to transparency with our community while upholding the privacy of victims” we edited to “… upholding the privacy of victims and people who report incidents”.
Thank You, 2019
We mean it. On behalf of rOpenSci, thank you to everyone who has contributed their creativity, curiosity, smarts, and time in the last year. We are fortunate to have paid staff who work to build technical and social infrastructure to lower barriers to working with research data. But it is our community, built on trust, that binds us together and helps us see who we are working for. Many people have submitted their R packages for software peer review (31)1, reviewed those packages (~60), contributed some code or documentation to a package (117 people made their first code contribution to rOpenSci this year), (co-)authored a blog post or tech note about their package or an rOpenSci resource (48 authors), shared a use case to help package authors see how their work is being used and help other users imagine how they can apply it (26 people), attended a Community Call (331 people in 23 countries), cited our software (306 citations of 122 packages), asked or answered questions, explored project ideas, or gave us a generous shoutout in a talk, a post, or on Twitter.
Want to Intern with rOpenSci’s Community Manager?
Want to get some hands-on insights into running an open source community? Here’s an opportunity to work with me, rOpenSci’s Community Manager, on some non-code community-related work. I am looking for someone to work 1 day a week for 12 to 14 weeks. Working alongside rOpenSci’s Community Manager, Stefanie Butland, you will use guidelines and checklists to help run some of our established programs like our Blog and Community Calls. Tasks include:
2 Months in 2 Minutes - rOpenSci News, December 2019
rOpenSci HQ rOpenSci Announces a New $896k Award From The Gordon and Betty Moore Foundation to Improve the Scientific Package Ecosystem for R. We’re excited to announce a new member of our team! Introducing Mark Padgham, rOpenSci’s new Software Research Scientist NumFOCUS recognizes Melina Vidoni and Will Landau for their contributions to rOpenSci. Videos, speaker’s slides, resources and collaborative notes from our Community Call on Testing in R are posted.
