Skip to content

Commit

Permalink
incorporated feedback from Georg and Elizabeth with slight wording ch…
Browse files Browse the repository at this point in the history
…anges and tweaks to improve the process

Signed-off-by: Dawn M. Foster <dawn@dawnfoster.com>
  • Loading branch information
geekygirldawn committed Aug 30, 2023
1 parent 3d291e8 commit f2598af
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 18 deletions.
11 changes: 3 additions & 8 deletions .github/ISSUE_TEMPLATE/02-chaosscast-episode-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,17 +26,13 @@ Please get approval from the CHAOSScast facilitator before creating a CHAOSScast
* Name calendar event:🎙 CHAOSScast {Topic}
* Start with the microphone emoticon \(🎙 \) to signal recording meeting
* [ ] **Action:** Send out a [confirmation email](https://docs.google.com/document/d/1Pw8OKn-qSSkMw573BZu-EZ4BZualesdZjPbpBEKvzrc/edit) that includes the [“how we podcast” document](https://docs.google.com/document/d/1j5Ng91rrFrx3PdPejv26rBxb1P7UX-O_Q0_I9TCIya0/edit#) to guests and panelists
* [ ] **Action:** Update the episode planning document with recording time and zoom link
* [ ] **Action:** Update the [episode overview table](https://docs.google.com/document/d/1qxmC1k8SayChurIq2r91CR3r_KAThTwaNEMjA6DLGhE/edit#)
* [ ] **Action:** If the episode is more than two weeks out, schedule a [reminder email](https://docs.google.com/document/d/17vKzCOYvRXq5zaIlv_sb80zFapTU19dRgkx5RqRx3xE/edit) for 1 week before the episode recording
* [ ] **Action:** Schedule a [reminder email](https://docs.google.com/document/d/17vKzCOYvRXq5zaIlv_sb80zFapTU19dRgkx5RqRx3xE/edit) for 24-hours before the episode recording
* **Step 3:** Finalize Content \(Organizer\)
* [ ] **Action:** Update the episode planning document with the main topics and questions
* **Step 4:** Post-Episode Thank You Notes \(Georg Link\)
* [ ] **Action:** When the episode is scheduled for release that week, notify guest and get their mailing address
* [ ] **Action:** Sign thank you note and assemble with swag
* [ ] **Action:** Mail out thank you note with swag
* [ ] **Action:** Add date of shipment on [episode overview table](https://docs.google.com/document/d/1qxmC1k8SayChurIq2r91CR3r_KAThTwaNEMjA6DLGhE/edit) to confirm it was sent

### Recording an episode

Expand Down Expand Up @@ -79,11 +75,10 @@ Please get approval from the CHAOSScast facilitator before creating a CHAOSScast
* Header Image: \(ignore, will use default\)
* Transcript: \(ignore\)
* PUBLISH
* [ ] **Action:** When the episode is scheduled for release that week, notify all participants via email, and send guests a link to a webform to get their mailing address
* [ ] **Action:** Update the template [CHAOSScast Calendar](https://calendar.google.com/calendar?cid=NTEzcjQ3YmI3NTZ0MDdscDV0YXQ1bnN1ajBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) event \(🎧 \(TBD\) Release CHAOSScast episode\) for the release date \(i.e., remove `(TBD)` and add epsiode number and title\)
* [ ] **Action:** Post about it on Discourse and Slack \([template](https://docs.google.com/document/d/1TyZAX7xfYmx3gKSFT2i2K5ERIA1ibGAQVfXMnGmFYyg/edit)\)
* [ ] **Action:** Include in upcoming [CHAOSS newsletter](https://docs.google.com/document/d/1N2dbrqHYSxIUF1vXZ1-854aaoGIf86uey0XRhxhgG4o/edit)
* [ ] **Action:** Check ITTT automated \(RSS feed publishing\):
* Schedule a tweet through Tweetdeck
* [ ] **Action:** Post on other social channels (LinkedIn, Mastodon)
* [ ] **Action:** Notify community manager for inclusion in upcoming [CHAOSS newsletter](https://docs.google.com/document/d/1N2dbrqHYSxIUF1vXZ1-854aaoGIf86uey0XRhxhgG4o/edit)
* [ ] **Action:** Post on social channels (LinkedIn, Mastodon)
* [ ] **Action:** Advertise outside of CHAOSS
* SustainOSS Forum \(?\)
10 changes: 0 additions & 10 deletions media-and-outreach/chaosscast.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,16 +97,6 @@ Each recording is scheduled for 1.5 hours for a released episode targeting 30-40
* "what amazing thing did you do?", "what was the community like before it happened?" "when did you realize something needed to change?" "how did you go about getting the thing done?" "what was the end result?" “why dos what you did matter to the listener’s communities?” “what advice do you have to make doing the same thing easier?”
* What are your hopes for CHAOSS in the future?

## 🕙 Automation

Documenting any automation configured to date.

Georg Link has an IFTT recipe to:

* If new item in this RSS feed [https://feeds.fireside.fm/chaosscast/rss](https://feeds.fireside.fm/chaosscast/rss)
* Then tweet it from @CHAOSSproj
* Example tweet: [https://twitter.com/CHAOSSproj/status/1256137855606444032](https://twitter.com/CHAOSSproj/status/1256137855606444032)

## 📖 Procedures

The procedures are for the organizer and facilitator of each episode can be found in the [Issue Template]() in the CHAOSS Community repository. A new issue using this template should be created for each episode.
Expand Down

0 comments on commit f2598af

Please sign in to comment.