Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
With rOpenSci turning 15 this year, it’s hard to believe that I’ve been part of it for 10 of those years.
My involvement started in Brisbane in 2016, at the first Australian rOpenSci Unconference. I’d known about rOpenSci and its work for some time before then. When rOpenSci was founded in 2011, I’d just moved from the US to the Philippines for work. During the five years I lived and worked there, I became familiar with its packages and the people behind them. I was interested in what rOpenSci was doing, but wasn’t sure how I might get involved. I did recognise the value of being part of the R community, though, and joined the Manila R User Group.
Brisbane 2016: just the beginning
I moved to Australia for work in January 2016 and, as luck would have it, was living close enough to Brisbane to attend the rOpenSci Unconf in April. The event was organised by a group of researchers at QUT, including Nick Tierney, Miles McBain and Jessie Roberts.
As it happened, my first R package, {GSODR}, had just been accepted onto CRAN. That was the fact I shared when introducing myself to the other attendees. I was an experienced researcher and R user, but still very much a newcomer to developing and publishing R packages.
I was nervous about attending. I was new to Australia and had never been to an event quite like it. But the chance to bring Australian R users together to work on practical research problems was exciting, and I soon settled in.
The format was very hands-on. We shared unfinished ideas, learned from one another and built things together. I found this a great way to learn, and it helped me gain confidence. I was one of the few attendees with experience working with geospatial data and a particular interest in weather data, which led me to connect with A/Prof Ivan Hanigan.
Ivan had some R code for downloading AWAP grids, AWAP_GRIDS, and I was able to help improve it. I also contributed a vignette describing how to work with Australian weather data, which went on to influence several packages that followed.
It was the first time I felt I had something useful to contribute to a wider group of R users, including people I’d never met before. I came away from Brisbane with a much better sense of what I could do and who I could do it with.
From an idea to a package: learning to develop openly
After the Unconf, I returned home and soon submitted GSODR to rOpenSci for software peer review.
I’d already seen how welcoming the people involved were, and I understood the value of peer review from my day job. Now I had the chance to go through that process with code. I’d written a few R packages for internal use, but nothing intended for a wider audience.
The feedback from the editors and reviewers helped sharpen the package’s focus and improve its reproducibility and robustness. I also began to understand that making a package available to other people involved rather more than getting data from an API (or, in those days, FTP) and wrangling it into a usable format. Good documentation, testing and a willingness to keep maintaining the package as data sources and the R ecosystem changed were just as important.
I went on to develop several other weather and climate-related packages, providing access to a range of data sources. {getCRUCLdata} grew out of scripts I’d written for my PhD research, while {bomrang} (now superseded by {weatherOz}) grew out of ideas from the Brisbane Unconf and the 2016 GovHack Hackathon. My team went on to win the national Paddock to Plate Award.
Perhaps the best known of my rOpenSci packages, {nasapower}, had a longer history. I’d started working on it around 2011, but it really took shape during the peer-review process, when the NASA-POWER team released a dedicated API. I ended up rewriting the package from the ground up during the review. That taught me a great deal about working with REST APIs and testing code that depends on remote services. In particular, I learned to use {vcr} to record and replay HTTP interactions, so tests could run without an internet connection.
Since then, much of my package development has been about making data easier for other researchers to access. One of the best parts of that work is hearing from a student who has finally been able to get the data they need after struggling to find it or work out how to access it. It’s a good reminder of why I started doing this in the first place.
From contributor to reviewer: giving back
In 2019, I was invited to review packages for rOpenSci. I was delighted to have the chance to give something back to a group that had helped me so much. I reviewed {stats19} and {bib2df}.
A few years later, I had a nice reminder of how these connections can come full circle. I reviewed {rnassqs} for Nicholas Potter, who went on to review my package {read.abares}.
Reviewing other people’s packages also made me a better package developer. Seeing how other authors approached problems, and thinking carefully about their code and documentation, gave me a different perspective on my own work.
In 2021, Noam Ross invited me to serve as a guest editor for {allodb}. I was surprised, but grateful, and accepted. I stumbled a little while learning to use the rOpenSci bot and manage the submission, but it was a valuable experience. The authors learned, I learned, and the package came out of the process in better shape.
That experience led to another invitation from Noam: joining the rOpenSci editorial board. I gladly accepted. Since then, I’ve been able to contribute beyond my own packages, supporting authors and reviewers and helping keep the software peer-review process running.
I particularly value rOpenSci’s approach to working together and its Code of Conduct, which sets clear expectations for everyone involved. Being on the editorial board has also helped me keep up with changing standards in research software, while giving me the chance to help make the process welcoming rather than intimidating for new contributors.
Beyond packages: building a wider open science community
rOpenSci’s influence on my work hasn’t stopped at package development or editorial duties.
In 2018, Dr Emerson Del Ponte and I founded the Open Plant Pathology community. We saw a need in the global plant pathology community much like the one rOpenSci had addressed for R users: a place where people could share ideas, data and code, and help one another, wherever they happened to be in the world.
A lot of what I’d learned from rOpenSci shaped how we approached Open Plant Pathology. For several years, we published blog posts with ideas, examples and code that others in plant pathology could use. We also developed an R package, {hagis}, based on work that Dr Austin McCoy and Dr Zachary Noel wanted to share with the wider community.
In 2025, with changes in our jobs and difficulties engaging with the community, we decided to wind down Open Plant Pathology and focus our efforts elsewhere. For me, that included taking on a statistics editor role at rOpenSci, alongside my existing editorial responsibilities.
Looking back, I think Open Plant Pathology worked in part because we had a good example to follow. rOpenSci had shown us that the value of a community isn’t just in the software or other technical contributions people make. It’s also in the relationships people build, and in having a place where they can share their work and help one another improve it.
Ten years on: what rOpenSci has meant
A lot has changed over the past ten years. I’ve had three jobs and lived in two Australian states. I’ve gone from being a newcomer whose first R package had just been accepted onto CRAN to having several packages reviewed, reviewing other people’s work, joining the editorial board and becoming part of the rotating editor-in-chief team.
I never had any formal training in software development. My only real introduction before working with R was a single undergraduate semester writing macros for spreadsheets. Most of what I’ve learned has come from the people around me, starting with my PhD research and continuing through groups like rOpenSci.
I think that’s worth saying because you don’t need to be an expert software developer to contribute to open-source or open research software. You need to be curious, willing to learn and able to find people who will help you along the way. rOpenSci has been an important part of that for me, and has helped make research software development feel like a recognised and valued part of doing science.
It’s more than just software
But when I think about what has kept me involved for ten years, it’s not just what I’ve learned or the software I’ve helped develop. It’s also the people I’ve met along the way. Attending the Unconf in 2016 was also the start of friendships and working relationships that have lasted ever since.
Ivan Hanigan and I are now both on staff at Curtin University, where we continue to collaborate and find reasons to work together. Nick Tierney and I became friends, and when he moved to Perth, we spent plenty of time together taking photographs. Noam Ross and I have met several times to discuss disease-modelling ideas across plant, animal and human health. I wish we had more opportunities for those conversations. Maëlle Salmon has also been a great help in sorting out some particularly finicky time-zone issues in {weatherOz}. We spent a fair amount of time on a video call getting them sorted. Sam Rogers reviewed {weatherOz} for rOpenSci. We now work together on a large national project, have both contributed to the rOpenSci package {nert}, and collaborate on other projects outside the R community. I’d also be remiss not to mention the people who helped build {bomrang} and later {weatherOz}. Several were also part of the rOpenSci community. They generously gave their time and expertise to these packages, often without me having to ask. Together, {bomrang} and {weatherOz} became some of the largest collaborative open-source projects I’ve worked on, and I’m indebted to everyone who contributed. Among those who contributed were Mark Padgham, Hugh Parsonage, James Goldie, Jono Carroll (who I first met in 2016 at the Unconf), Dean Marchiori, Keith Pembleton, Paul Melloy, and of course, Rodrigo Pires who maintains {weatherOz}.
These relationships are a big part of why I’ve stayed involved. Wherever I find myself, there’s a good chance there’s someone from rOpenSci I can get in touch with for a coffee and a chat.
Looking forward: an invitation to get involved
If there’s one thing I’d say after ten years, it’s don’t be afraid to get involved.
I’ve been using R since the early 2000s and have watched a fantastic community grow around it. I’ve also seen what a difference it makes when people make an effort to be kind, supportive and welcoming. rOpenSci is a good example of that.
Getting involved doesn’t have to mean writing an R package. You could open an issue to report a bug, help improve some documentation or write an example vignette showing others how to use a package. If you’ve found a useful way to do something with a package, someone else might benefit from seeing it too (just check with the package author first!).
Reviewing is another good way to contribute. You’ll learn a lot about your own coding by looking at someone else’s work and thinking about how it could be improved. rOpenSci’s review process is intended to be supportive, friendly and constructive, and that makes it worthwhile for authors and reviewers alike. If you are interested in reviewing, rOpenSci maintains a database of potential reviewers that is open for you to volunteer.
From my perspective as an editor, rOpenSci needs to keep adapting as the tools and practices of research software development change, as it has done throughout its history. New technologies bring opportunities, but also questions about how to maintain quality, support contributors and keep peer review useful, particularly as the demands on editors and reviewers grow.
Whatever changes, I think the community will remain central to rOpenSci’s work. If we keep that focus, we’ll continue to serve the needs of the R community.
I hope rOpenSci can make the most of what’s changing without losing the things that made me want to be involved in the first place: thoughtful reviews, useful feedback and people who are willing to help one another do better work. After ten years, that’s what stands out to me. The software matters, of course, but so do the people I’ve met, the things I’ve learned and the friendships that have come out of it.
And I’m very glad I made it to Brisbane in 2016.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
