All posts (Page 57 of 120)
In early September, the version 2.0.0 of rmangal was approved by rOpenSci, four weeks later it made it to CRAN. Following-up on our experience we detail below the reasons why we wrote rmangal, why we submitted our package to rOpenSci and how the peer review improved our package.
🔗
Mangal, a database for ecological networks
Ecological networks are defined as a set of species populations (the nodes of the network) connected through ecological interactions (the edges). Interactions are ecological processes in which one species affects another. Although predation is probably the most known and documented interaction, other less noticeable associations are just as essential to ecosystem functioning. For instance, a mammal that unintentionally disperses viable seeds attached to its fur might help plants to thrive. All of these interactions occur simultaneously, shaping ecosystem functioning and making them as complex as they are fascinating.
...🔗
rOpenSci HQ
What would you like to hear about in an rOpenSci Community Call? We are soliciting your “votes” and new ideas for Community Call topics and speakers. Find out how you can influence us by checking out our new Community Calls repository.
Videos, speaker’s slides, resources and collaborative notes from our Community Call on Reproducible Workflows at Scale with drake are posted.
Help wanted! We encourage rOpenSci package authors to help us help you get more contributors to your package. If you label an issue “help wanted” (no hyphen or emojis), those issues can be found in a search of the rOpenSci organization.
...
We want to know how you use rOpenSci packages and resources so we can give them, their developers, and your examples more visibility.
It’s valuable to both users and developers of a package to see how it has been used “in the wild”. This goes a long way to encouraging people to keep up development knowing there are others who appreciate and build on their work. This also helps people imagine how they might use a package to address their research question, and provides some code to give them a head-start.
...If you have an R package on CRAN, you probably know about CRAN checks. Each package on CRAN, that is not archived on CRAN1, has a checks page, like this one for ropenaq:
https://cloud.r-project.org/web/checks/check_results_ropenaq.html
The table above is results of running R CMD CHECK on the package on a combination of different operating systems, R versions and compilers. CRAN maintainers presumably use these as a basis for getting in touch with maintainers when these checks are failing.
...As announced in February, we now have an online book containing all things related to rOpenSci software review. Our goal is to update it approximately quarterly - it’s time to present the third version. You can read the changelog or this blog post to find out what’s new in our dev guide 0.3.0!
🔗
Updates to our policies and guidance
🔗
Scope
We’ve introduced an important change for anyone thinking of submitting a package. We ask authors to select a category in our Aims and Scope under which to submit. We found that the “reproducibility” category was confusing, as almost any R package can be related to reproducibility. We split “reproducibility” into four new categories that fit the narrower topics it previously included. They are:
...
