closes #366 OSS pillars and hackathon calendar blog

[rossfarrugia]

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

• Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
• Ensure your new post folder is of the form "posts/zzz_DO_NOT_EDIT_<your post title>". This is so that the post date can be auto-updated upon the merge into main.
• Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
• Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Python", "Community", "Conferences", "Submissions", "Technical", "DEI") for your blog post. If you cannot find anything that fits your blog post, propose a new tag to the maintainers! Note: if you use a tag not from this list, the "Check Post Tags" CICD pipeline will error. We occasionally tidy up all tags for consistency.
• Add a short description for your blog post in the description field at the top of the markdown document.
• Blog post is short, personalized, reproducible and readable
• Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
  This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
• Address all merge conflicts and resolve appropriately
• Assign two of us (@aaehmann, @ashley-tarasiewicz, @chrisprice-phuse) as reviewers in the PR.
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[rossfarrugia]

@orladoylenvs and @bms63 - please can you do an initial sanity check for this blog? looking to post it by end of the week if possible.

some questions i wasn't sure on:

• xportr / logrx - should we already pick dates and add them here? pending final agreement from Ben that he can help run these
• should we already include sign up details here?

[orladoylenvs]

Hi Ross - this is great! I didn't have any suggested changes - you covered everything really well!

Re - how to sign up: I think we need to figure our the mechanism? We've used eventbrite with R/Pharma but maybe PHUSE could help with options?

Re the date for xportr / logrx - I guess it would be good to confirm this before we publish the blog as it's quite soon so we might want to either firm this up or agree that we push it out? @bms63 - let's not add too much to your plate :)

[rossfarrugia]

Thanks @orladoylenvs - yes agree probably too early for the sign ups until we get clarity from PHUSE - let's chat tomorrow on that.

Will wait for Ben to confirm around the dates

[bms63]

Will send the mail today - apologies!!

[rossfarrugia]

Final actions before we can tag blog team reviewers:

• @bms63 to confirm xportr proposed date is OK
• @orladoylenvs to make a commit to add xportr session sign up details to the table column i added pending what we hear back from phuse

[bms63]

FYI: I am out of office April 1st- April 3rd

[rossfarrugia]

FYI: I am out of office April 1st- April 3rd

ah what are the chances 😆 do you want to make a commit here and update with whichever date you prefer but earlier April is better so as not to clash with R/Medicine teal one? don't worry if its during my holiday dates as we have plenty of options to help support you.

[bms63]

Does April 9th work? It is close to teal one.

Not to derail us - but since we are so close to teal's/R Medicine hackathon should we just reschedule this one for a later date? We could include logrx as well

[rossfarrugia]

If @orladoylenvs is available 9th then it should work. We were hoping to start with a pharmaverse/phuse-hosted first event to build momentum before the R/Medicine one, and we wanted you to have the first opportunity as it was your great idea!

[bms63]

If @orladoylenvs is available 9th then it should work. We were hoping to start with a pharmaverse/phuse-hosted first event to build momentum before the R/Medicine one, and we wanted you to have the first opportunity as it was your great idea!

I'm game for whatever!!!

[orladoylenvs]

I will be on holiday that week but I don't want to be a blocker. I could ask someone to step in for me?

[bms63]

Hey both - if neither of you are around, then I think this is a good signal that we should just postpone. Apologies for derailing this.

I'm excited about the hackathon!! maybe we can include metatools and metacore in with logrx and xportr as well?

[rossfarrugia]

Hey Ben, check Slack - we took this chat offline there and no worries about moving this one later. We were trying to keep hackathons focused on one package each time so as not to overwhelm new contributors (unless the packages are closely linked like cards/gtsummary example). I imagine there could be a metacore/metatools hackathon some time but we'd have to add that to the list for next year given how many we have lined up already