[Epic] Post Updates to Social Media

[D1M1TR10S]

Summary ⭐️

Every time a new submission is approved and deployed to Ersilia's CLI, we want to trigger a GitHub Actions workflow that posts an update to platforms like Slack, Twitter, LinkedIn, etc.

Objective 🎯

Engage with Ersilia's community of contributors, volunteers, and scientists – by sharing updates every time a new model is deployed.

Supporting Details ✏️

Next: Discuss our strategy and data flow around this workflow. We'll start with Slack and Twitter. We're waiting on the new model submissions to be complete before starting this one, since it's dependent upon that model flow.

Checklist:

• [ ] 1. Define high-level goals, audience, and roadmap. Identify the initial platform to start with for V1. (Slack, Twitter or LinkedIn)
• [ ] 2. Architect our workflow for the 1st platform we choose
• [ ] 3. Build out the API integration
• [ ] 4. Write copy for posts announcing new model submissions – with dynamic fields for {model name}, {contributor}, and {summary?}
• [ ] 5. Build the GitHub Actions workflow that's triggered by the specified event in GitHub (branch merged, PR approved, new model deployed, etc.)
• [ ] 6. Run, test, and stabilize the workflow
• [ ] 7. Deploy the workflow to production We'll then repeat this same process for each platform.

Sound good @GemmaTuron @miquelduranfrigola?

Dependencies 🖇

Slack and Twitter have open source Actions templates for setting up automated posts that are triggered by GitHub events. Keep in mind, there is some security/stability risk when using a marketplace Action that's not verified. It may be best for us to fork the original repo into our own codebase, rather than reference the Actions by label (as it could change without us knowing)

Slack:

• Understand policies and review API docs
• Marketplace Actions template to use Slack API for automated posts: https://github.com/slackapi/slack-github-action
• Slack's Workflow Builder sounds like the easiest option, but requires a paid Slack instance. We have alternative options if needed.

Twitter

• Understand policies and review API docs
• Actions template to use Twitter API for automated posts: https://github.com/marketplace/actions/send-tweet-action
• Twitter Developer Docs

LinkedIn

• Understand policies and review API docs
• Looks like there aren't any open source Actions templates for posting to LinkedIn.
• Based on this article it sounds like it's possible to do this via the API, but could be somewhat difficult. Given that we don't have a marketplace Action to reverse-engineer, I propose that we save this one for last.

Team 🏀

DRI: @megamanics Backup: TBD

Timeline 🗓

Documentation 📓

[sayantani11]

@D1M1TR10S Like do we want automation or manual?

[D1M1TR10S]

Hi @sayantani11 ! I'll share whatever details I have in the top-level comment.

To answer your question: Yes! We want this process of posting to Social Media to be automated with GitHub Actions.

So every time a new submission is approved and deployed to Ersilia's CLI, we want to trigger an event that posts to platforms like Twitter, LinkedIn, etc.

I'd like to plan and coordinate this project with you, me, @GemmaTuron and @miquelduranfrigola. Should we add @sayantani11 to the Slack channel? And/or schedule a quick call to plan this one out?

[GemmaTuron]

Hi @D1M1TR10S and @megamanics thanks for taking the lead on this! I 'd start with

• Twitter
• Slack

What do you need from us at this point?

[D1M1TR10S]

Sure thing @GemmaTuron. We're going to kick this off once the new Model Submissions Flow is complete, since this would depend on that workflow.

For the kickoff, here's what I think we'll need:

• Ersilia's login info for the Twitter and Slack accounts
• Either grant admin access to @megamanics on Twitter and Slack so he can get the API tokens for each platform, and set them up as endpoints for the workflows. Or if you prefer not to grant access, you can pair with Ski to share the API tokens + any other important info required for the integration. Granting access might make it easier for Ski to test the workflows.
• Align on copy for the automated posts. (What are they going to say?)
• Define the trigger event kicking off this workflow. (Will it be a new PR being merged? Or a deployment of a new model?)

Does that all sound right @megamanics?

[D1M1TR10S]

Once the Airtable dependency is removed, this workflow will be ready to continue working on.

We can go through the approval process when there's a new PR. Once the PR works on local, we can initiate a Slack message.

[GemmaTuron]

• [ ] Create a template of the post (what information is there) -- @miquelduranfrigola and @GemmaTuron
• [ ] Create a workflow dispatch
• [ ] The action will be manually triggered

[D1M1TR10S]

Before posting to the public (like LinkedIn or Twitter) we'll need to have automated testing in Slack. These two platforms can be deprioritized for the current scope of work.

Save for the next round

Can be done manually in the meantime

• Create content on Medium dynamically based on what each model does. Add a template structure to the input form on the template repo: "What does this model do? Who is it for? How does it work?"
• Then automatically post this blog article to Twitter and LinkedIn. (might be best to do less posts, but with higher quality)

[GemmaTuron]

For the issue creation in GitHub, we need to create a list of users that will be selected randomly to test a model once it is ready

[megamanics]

@GemmaTuron List of test users can be updated using the below url

https://github.com/organizations/ersilia-os/settings/variables/actions