Conference Agenda

Overview and details of the sessions of this conference. Please select a date or location to show only sessions at that day or location. Please select a single session for detailed view (with abstracts and downloads if available).

 
 
Session Overview
Session
1A - Community and Outreach 1
Time:
Monday, 05/July/2021:
4:45pm - 6:15pm

Session Chair: Erin LeDell
Zoom Host: s gwynn sturdevant
Replacement Zoom Host: Linda Jazmín Cabrera Orellana
Location: The Lounge #talk_community_outreach_1
Session Topics:
Community and Outreach

Session Sponsor: ixpantia
Session Slide

Presentations
4:45pm - 5:05pm
Talk-Live
ID: 260 / ses-01-A: 1
Regular Talk
Topics: Community and Outreach
Keywords: community, infrastructure, maintenance, non-profit sector, open source

rOpenSci’s Model for Managing a Federated Open Source Software Community

Stefanie Butland1, Lou Woodley2, Karthik Ram1,3

1rOpenSci; 2Center for Scientific Collaboration and Community Engagement; 3University of California, Berkeley

rOpenSci hosts over 350 staff- and community-contributed R packages. We have evolved a unique model of community management to support the complex needs of people who develop, review, and use these packages.

The Community Participation Model from the Center for Scientific Collaboration and Community Engagement (http://doi.org/10.5281/zenodo.3997802) provides a framework to assess how community members interact with programs and each other. The four modes on a continuum are: Convey/Consume; Contribute; Collaborate; Co-create. Engagement among rOpenSci community members happens primarily in the first three modes. 1) Convey/Consume. One-way dissemination of information via a newsletter, and Community Contributing Guide (https://contributing.ropensci.org/) that helps people match their motivations and skills to different ways to contribute. 2) Contribute. Opportunities for members to share knowledge e.g. via our package development guide (https://devguide.ropensci.org/), and blog posts written by members that draw attention to their work. 3) Collaborate. Scaffolded activities where members work together e.g. in open software peer-review as authors, reviewers, or editors. Additional programming, such as community calls, provides opportunities for multiple modes of participation at once e.g. by collaborating on developing topics and presenting, contributing by sharing resources and questions and consuming by attending presentations or reading the recaps.

Strong social facilitation by a full-time community manager and a team that values trust-based relationships supports community members in modes 1 - 3. We have recently explored what might be required to provide more opportunities for co-creation - mode 4 in the CSCCE Community Participation Model. An interviews-based assessment of community needs and audit of current programming aims to help us understand what people get from the rOpenSci community that they can’t get elsewhere, and how we can best facilitate productive and valuable collaboration and co-creation. We’ll present the results of this work as a methodology for others to consider how to review their own community engagement activities.



5:05pm - 5:25pm
Talk-Video
ID: 297 / ses-01-A: 2
Regular Talk
Topics: Community and Outreach
Keywords: bug fixing, contribution, outreach, R development

R Developer's Guide

Saranjeet Kaur Bhogal1, Heather Turner2, Michael Lawrence3

1Savitribai Phule Pune University, India; 2University of Warwick; 3Genentech

The R Developer's Guide (https://github.com/forwards/rdevguide) is an open-source project that aims to facilitate the on-boarding of new contributors to R Core development. New contributors to R are often not aware of where they can start contributing to the development of R. This guide helps in providing ways by which you could start contributing. How would you report a bug? What is the procedure to submit a patch? How could you help improve the documentation? These are some of the questions which new contributors may not have an idea about. In this talk, I will discuss these procedures. I will also walk through this guide for new contributors interested in referring to it for their contributions.

Link to package or code repository.
https://github.com/forwards/rdevguide


5:25pm - 5:45pm
Talk-Video
ID: 228 / ses-01-A: 3
Regular Talk
Topics: Community and Outreach
Keywords: community

Packages submission and reviews; how does it work?

Lluís Revilla Sancho1,2

1IDIBAPS; 2CIBEREHD

We benefit from others’ work on R and also by shared packages and for our programming tasks. Occasionally we might generate some piece of software that we want to share with the community. Usually sharing our work with the R community means submitting a package to an archive (CRAN, Bioconductor or others). While each individual archive has some rules they share some common principles.

If your package follows their rules about the submission process and has a good quality according to their rules it will be included. All submissions have some common sections: First, an initial screening; second, a more profound manual review of the code. Then, if the suggestions are applied or correctly replied then the package is included in the archive.

On each step some rules and criteria are used to decide if the package moves forward or not. Understanding what these rules say, common problems and comments from reviewers will help avoiding submitting a package to get it rejected. Reducing the friction between sharing our work, providing useful packages to the community and minimizing reviewers’ time and efforts.

Looking at the review process of three archives of R packages, CRAN, Bioconductor and rOpenSci, I’ll explain common rules, patterns, timelines and checks required to get the package included, as well as personal anecdotes with them. The talk is based on the post analyzing reviews available here: https://llrs.dev/tags/reviews/

Link to package or code repository.
https://llrs.dev/tags/reviews/