14  Marketing your package

Also refer to the blog post “Marketing Ideas For Your Package”.

We will help you promoting your package but here are some more things to keep in mind.

• If you hear of an use case of your package, please encourage its author to post the link to our discussion forum in the Use Cases category, for a toot (Mastodon post) from rOpenSci and inclusion in the rOpenSci monthly newsletter. We also recommend you to add a link to the use case in a “use cases in the wild” section of your README.

• Post about your package on social media (Mastodon, Bluesky, LinkedIn…) using the “#rstats” hashtag and tag rOpenSci if rOpenSci is present on that platform! This might help with contributor/user engagement. Example posts from rOpenSci itself: A package a day, Help wanted post, Use cases, Welcome post.

• When you release a new version of your package or release it to CRAN for the first time,

  • Make a pull request to R Weekly with a line about the release under the “New Releases” section (or “New Packages” for the first GitHub/CRAN release).

  • Consider submitting a short post about the release to rOpenSci tech notes. Contact rOpenSci Community Manager, (e.g. via Slack or info@ropensci.org). Refer to the guidelines about contributing a blog post).

  • Submit your package to lists of packages such as CRAN Task Views.

• If you choose to market your package by giving a talk about it at a meetup or conference (excellent idea!) read this article of Jenny Bryan’s and Mara Averick’s.