Round-up / Newsletter of this group
Matthew Parsons PublicSeen by 508Dear most active members (of whom I am not one),
This Loomio group has seen a lot of activity recently, and like most Loomio groups, this has involved a minority of the total membership base.
I would like to make a request for the active members to reach out to the not-so-active members in the form of a very brief round-up or newsletter of events/decisions/discussions in this group since its inception.
I know - you might think, 'well why don't you just read all the threads and catch-up, if you're interested?'
There is an argument for that, but I think the process of summarisation is actually a powerful process for establishing 'what have we achieved', and 'what are we doing'.
Something like a co-created Google Doc, perhaps drafted by whoever wants to have a crack at it. It could also be sent out to the CoTech membership base by email, so that it is more likely to be read.
Just an idea - discuss!
Great idea, can we do it on our wiki? I made a start on this:
I missed the discussion at Paltform Co-ops but understand from the notes that adding a news / blog section to coops.tech was discussed -- we should post any newsletter that is produced there.
See also this GitHub ticket about adding a news / blog section to the site and probably best follow up there regarding what WordPress plugin would be most suited for allowing people to signup and be sent emails when new content is posted (Jetpack might be the easiest but perhaps there is something better?).
Definitely +1 to blog post updates.
I would also say that some people do like only participating in something when their expertise is specifically sought out.
Finally, we might want to think more broadly about our 'architecture of participation' - but that might be something for Wortley Hal' :)
I think the update needs more of a human touch than a wiki which can feel a bit cold and mechanical, even for techies.
+1 to blog post updates and if they get regular enough a summary e-newsletter to a mailing list will remind people to check in and update themselve and can contain links to recent posts.
Also, one idea for the first blog post is myself and Matthew could collaborate on interviewing someone from the initial team to ask basic questions that can easily be missed...
@marcd I suggested the wiki as a collaborative place to edit the text for the newsletter, not as the only place where the content would exist, I think that once it has been written it would make sense to post it to a news / blog section on coops.tech and for that to also trigger a email to subscribers.
I like the interview idea @marcd - does anyone have objections? Human touch is essential!
Sorry @chriscroome misunderstood.
Shall we take a punt @matthewparsons and pen some questions together at risk for consideration by the group? I'll drop you an email to arrange a chat.
Could it be in the form of a change log?
Cotech v1.8.1 kind of thing.
I was about to pen the very same thing myself. I am keen to engage and a summary would help me see how we at the Creative Coop can contribute. Thank you Matthew for sharing.