Closed equivalentideas closed 9 years ago
As soon as we have an idea of what this will be about, let's make a signup for and send it out via twitter, the oa email list and do a blog post so people can sign up while we're getting things together.
A couple of examples of similar concepts:
I think the Thursday morning before the Pub Meet would be a good time to send out the email. That gives people coming the pub meet a few days and a weekend to find some time for a read, and for others it's a nice relaxed later in the week time so that it's in people minds for the weekend. Web Directions send out their weekly email on a Friday for example.
If that's when we want to send it out, then the first one will be the Thursday, 19th of February.
If that's when we want to send it out, then the first one will be the Thursday, 19th of February.
:+1: SGTM!
TODO as discussed with @equivalentideas:
For the collection of links for the newsletter, here's the plan @henare and I are thinking:
Have a /newsletter repo, people can create issues with links they'd like to be included and we can then close them once added.
The content of the email can be a markdown document named for the date it will be sent. Once the content is finalised then generated HTML can be copied into a blog post and into the newsletter builder in mailchimp.
Nice things about having it in a repo:
Here's the repo https://github.com/openaustralia/newsletter
This is now all being handled on the openaustralia/newsletter repo. I'm closing this ticket.
This newsletter is a way to engage and support people interested in civic tech projects like those run by the OpenAustralia Foundation.
It should be published shortly before the OAF pub meetup so anything arising of interest can be discussed there.
It should be succinct and use headings/links to make any extended content scannable. People are smart and busy remember.
What should the scope of the newsletter be?