Do you have code that accompanies a research project or manuscript? How do you review and archive that code before you submit a paper? Our next Community Call will present different perspectives on this hot topic, with plenty of time for Q&A. What’s the culture of the group around feedback and code collaboration? What are the use cases? What are some practices that can adopted?
Join our Community Call on Tuesday, January 30th (January 31 for our Australian friends) Nick Golding, 2017 rOpenSci Fellow, will talk about two R packages he has developed recently. zoon aims to promote open and reproducible research in ecological modeling by helping researchers share their code in a modular way and produce reproducible research artifacts.
Are you thinking about submitting a package to rOpenSci’s open peer software review? Considering volunteering to review for the first time? Maybe you’re an experienced package author or reviewer and have ideas about how we can improve. Join our Community Call on Wednesday, September 13th . We want to get your feedback and we’d love to answer your questions!
Our Community Call on Tuesday, March 7th, 8-9 AM PST, will cover “How to ask questions so they get answered! Possibly by yourself!”. Asking questions about programming is a skill you can develop - we’re not just born with it. The speakers will cover some of the background and skills you’ll need to increase your chances of having your questions answered by your peers or by a busy expert.
Our Community Call on December 15th covered a big topic in tech communities: “How do I create a code of conduct for my event/lab/codebase?”. Here, we cover some of the key themes and considerations that arose from the discussion and point to curated resources and examples to follow when developing a code of conduct (CoC) for your community. Three guest speakers shared different perspectives.
In order to facilitate a transformation towards open and reproducible research, rOpenSci is building and improving not only the technical infrastructure, but the social infrastructure as well. To support this, occasionally a Community Call will focus on a topic that reflects the values of rOpenSci.
On April 21st and 22nd of 2016, we had 40 members of the R community gather in Brisbane, Australia, with the goal of reproducing the rOpensci Unconference events that have been running with great success in San Francisco since 2014. Like every event organisers ever, we went through the usual crisis: Where will it be? Will anyone actually show up? Is the problem space over venue, date, attendees, catering, sponsors convex?
The rOpenSci project is a poster child for the fluid collaboration that has become increasingly common these days thanks to platforms like Twitter and GitHub. It has been really inspring to see open discussions take shape as rough ideas, which rapidly turn into prototype research software, all of which are now happening in the order of few days to weeks rather than months to years.
