Add follow-up to data licensing post

[joshwlambert]

This PR adds a follow-up post to the Dual licensing R packages with code and data blog post authored by @chartgerink and myself.

This post provides a short summary of the original post and then provides an update to the Licensing code and data in one R package section including our experience since writing the blog post developing {epiparameter} and getting it hosted on CRAN.

I've added a callout to the the first version of the blog post in the Licensing code and data in one R package section to direct readers to updated blog post.

This PR provides an alternative option to PR #359. The preferred option can be merged and the other PR can be closed without merging.

• The post specifies a license if you don't want to use the default CC BY
• All authors have an ORCID iD
• Relevant keywords / tags has been added. In particular, if you want your post to be shared on R-bloggers, you must tag it with R
• Images or other external resources have been committed and pushed
• The post uses pure quarto syntax, rather than HTML or R code, unless necessary

Right before merging:

• The date field has been updated
• All reviewers have been acknowledged in a short paragraph
• A PR has been opened in the blueprints to link to this post
• The post has been re-rendered and content of the _freeze/ folder is up-to-date

/schedule 2025-01-27T08:00

[netlify]

✅ Deploy Preview for tourmaline-marshmallow-241b40 ready!

Name	Link
🔨 Latest commit	daf994b
🔍 Latest deploy log	https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/678fd0d7e13070000701286b
😎 Deploy Preview	https://deploy-preview-360--tourmaline-marshmallow-241b40.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[joshwlambert]

@chartgerink once you've had time to review and compare both options please let me know what you prefer and feel free to suggest changes.

[chartgerink]

This is looking good. It makes more sense to me this way, as the chronology is clearer and there is less reading between the lines necessary.

I left a few suggestions, and my only question is whether I should even be an author on this, because you did virtually all of the work!

[joshwlambert]

Thanks for the suggestions @chartgerink. Given your involvement in discussing and formulating the structure of the post and what to include, your contribution was still substantial and warrants authorship in my opinion.

I'm happy for this to be merged.

[github-actions]

✅ Merge Schedule
Scheduled on 2025-01-27T08:00 (UTC) successfully merged