Newsletter Q1 2015

[rufuspollock]

Put together a simple newsletter of some of the latest developments.

• Mail the list to ask for announcements
• Quick scan of latest blog posts
• Ping local groups to see if they have any interesting developments (RP?)
• Post the newsletter
• Tweet and ping the list!

@loleg @danfowler @davidmiller @markbrough @mchelen @teleyinex @pwalsh - who would be up for being the editor for this edition?

[pwalsh]

BTW, Open Australia are using Github to manage the creation of their monthly newsletters: Repo Contributing Example

[rufuspollock]

@pwalsh great suggestion

[pwalsh]

I'll edit, and I'd like to follow the pattern used by Open Australia as linked above.

How do I ping local groups?

[rufuspollock]

there is a slack channel. i think what we really want is a list of "local labs leads" in fact - i know this could be yak-shaving but i may try to recruit that for you now (cc'ing you on the email). Basic idea would be an email alias / list of folks (ultimately we would want them on okfnlabs.org/members - but let's not over-complicate)

[pwalsh]

(FYI didn't get the cc)

[pwalsh]

@rgrp I'll have some time over coming weekend to do some prep. I thought to:

• hard fork the OA newsletter repo (the acknowledge the idea)
• start collecting ideas there via issues

WDYT for repo: okfn/labs-newsletter

[rufuspollock]

@pwalsh do we need a separate repo - would be nice to keep it as part of this one given that we will post on this site as a blog post etc (or maybe i don't understand the OA newsletter process)

[pwalsh]

No need: the flow there is: open an issue with a suggestion for inclusion, then a pull request for the newsletter notifies on the fact of inclusion and closes the issue.

Exact same thing could be done here: possibly using a "newsletter" label to identify as such.

[rufuspollock]

@pwalsh sounds good and forge ahead!

[pwalsh]

Created a submission gist here: https://gist.github.com/pwalsh/09a2646bd00cd94e7f51

Can move this into the site later, as a newsletters page or something.

[rufuspollock]

@pwalsh any update here - would be nice to ship ...

[pwalsh]

@rgrp yes I let it slip. So, let's aim to publish this Thursday 7th. You think we can still go with the Q1 theme, or too late?

[rufuspollock]

yes, let's go with Q1 and next one will be q2 ;-)

[pwalsh]

Draft (ready for publication unless others want to add/edit) is here: #346

[rufuspollock]

@pwalsh can we close this as fixed with link to published newsletter?

[pwalsh]

fixed: http://okfnlabs.org/blog/2015/05/11/newsletter.html