PLClub Talk Pipeline

[euisuny]

Instead of adding talks on the website and sending e-mail notifications separately, we could have a streamlined pipeline for adding PLClub Talks.

Proposed Pipeline (as per @Zdancewic 's suggestion) :

1. Future speakers make a talk pull request for their upcoming talk.
2. The talk gets merged into master.
3. Some mail app service sends out an e-mail to the PLClub listserv.

[dunnl]

I have two questions:

• What makes something a "talk" PR? (Can it be a label?)
• Where would the mail service be running?

This sounds plausible using Github's webhooks but it would require an HTTP server waiting to react to the merge. Then I presume it would need to parse the talk announcement, e.g. pulling out the "title" attribute, and put this into some kind of template. Then send out an email using some stored credentials?

Seems like a lofty goal although plausible.

Another possibility is to write a script that is executed as part of stack exec site deploy since the talk announcement does have to be deployed.