Maintaining a package can be a lonesome activity, which sometimes poses a problem if you prefer team work or if you encounter a very thorny-for-you problem.Beside belonging to a supportive community of maintainers (like rOpenSci 😉), for collaborative help and commiseration you can try to build a community of contributors around your package!In this post, we’ll explore one tool helping you towards that goal: “help wanted” issues, with which your

I’m thrilled to share that CRediTas has passed peer review and been accepted to rOpenSci as well as to CRAN. I am glad to acknowledge the editor Emily Riedered and the two reviewers Marcelo S. Perlin and João Martins. Their comments and support were really insightful. CRediTas is a tiny package to facilitate the tedious job of creating CRediT authors statements for scientific publications.

Say you have a bug report or feature request to make to a package.How can you use information on GitHub to manage your expectations (will there be a quick fix) and actions (should you go ahead and fork the repository)?In this post, we shall go over sources of information and explain how they can be used.In the end, there is no magical recipe, except perhaps graciousness, as software is made by humans.

Last Thursday we held a Community Call discussing how to set up a Package to Foster a Community. This call included speakers Maëlle Salmon, Hugo Gruson and Steffi LaZerte, and was moderated by Stefanie Butland. Summarizing the community call Scientific software development - and with that R packages - is a community effort.