Skip to content
This repository has been archived by the owner on Jan 5, 2024. It is now read-only.

Newsletter Content Suggestions #210

Closed
robynbergeron opened this issue Jul 20, 2017 · 2 comments
Closed

Newsletter Content Suggestions #210

robynbergeron opened this issue Jul 20, 2017 · 2 comments

Comments

@robynbergeron
Copy link
Contributor

robynbergeron commented Jul 20, 2017

There are many existing, open-source newsletters to look to for suggested content. A basic outline -- for a newsletter audience consisting of "users of Ansible" -- is listed below.

  • Big News (releases, mostly.)
  • News: Relevant / interesting blog posts, videos, news articles / reviews.
  • "Tweet of the week": find a fun tweet about Ansible, add it to the newsletter.
  • Events: Upcoming meetups. larger conferences with any Ansible content, CFPs of interest.
  • Community-related news: New modules, new contributor highlights and thank-yous; potential linking to "how to get started contributing" + selected "easy-fix" type issues; rotate through various WGs and provide a "what's up in the $whatever working group" short but sweet synopsis."
  • "haz news to suggest? do so here in $locationTBD" (see Newsletter "decisions" #211 for this dependency).
@robynbergeron robynbergeron self-assigned this Jul 20, 2017
This was referenced Jul 20, 2017
@gundalow gundalow added this to To do (Medium) in Community Aug 16, 2018
@gundalow gundalow added this to To Triage in Contributor Experience Sep 25, 2018
@decentral1se
Copy link

I enjoyed scrolling the 'call for participation' section of https://haskellweekly.news/issues/127.html.

That pretty much lines up with the 'easy fix' tickets. Good idea.

@gundalow
Copy link
Contributor

gundalow commented Jan 25, 2021

All done apart from "Tweet of the week", which has been added to #546

Contributor Experience automation moved this from To Triage to Done Jan 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
No open projects
Community
  
Needs prioritizing
Development

No branches or pull requests

3 participants