Skip to content

Commit

Permalink
Update participation-communication-strategy.md
Browse files Browse the repository at this point in the history
  • Loading branch information
lottycoupat authored Apr 30, 2021
1 parent 31afb3f commit 6bf6fc8
Showing 1 changed file with 61 additions and 3 deletions.
64 changes: 61 additions & 3 deletions project-communications/participation-communication-strategy.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,28 +35,86 @@ The aim of the meet-ups is to discuss and work on different areas of the project

### Co-working (TBC)

The aim of these sessions would be for

### Knowledge Share (TBC)

These sessions would be to knowledge share on a specific aspect/topic of the project to keep all memebers updated on what is going on int he different branches of the project.
These could be schedueld in relation to the need of them.
For example, if the topic has been worked on extensively in both the meet-ups and co-working, and needs a longer slot to update the group, then this can be done.

## Offline Communications
## Online Communications

The aim of offline communications
The aim of online communications is to keep contributors engaged in the periods between project (in-person) sessions.

### Newsletter

Every month, a newsletter will be distributed to those subscribed to it.
It inlcudes project updates as well as any information, resources or opportunities associated with AutSPACEs.

This comment has been minimized.

Copy link
@GeorgiaHCA

GeorgiaHCA May 27, 2021

Collaborator

includes

It will also include nformation about the upcoming events as part of the project.

### Slack Channel

We will use Slack as a way to keep regular contact with the members and contributors both in a formal and informal manner.
It will be set up with multiple channels where contributors can ask questions about any related topic.
It will also allow for questions that are out of scope, and therefore not part of discussions in project specific events, to be discussed and evaluated with contributors.
Slack will be a new platform for many individuals, and therefore it will be crucial to ensure that new members and contribtuors know how to use this platform.
This will be engrained in the onboarding process.

### Twitter

### Interation with Autistica and Open Humans
Our twitter platform will also be a way to regularly inform followers of our progress and keep in touch with our contributors.
But it will also be a key way to increase our participation by promoting and spreading the word of the project to increase contributors and members.

### Intergration with Autistica and Open Humans

We will ensure that there the project has continuous connections between Autistica, Open Humans and the Alan Turing Institute.
This can be in the form of talks and presentations as well including them in all our communciations.
Throughout the project we will continously seek out opportunities to integrate these communitities.

### Progress Report (TBC)

The progress report will be key in informing participants of updates on the project.
It will include key information such as:
- Number of Issues raised and closed
- Number of Pull Requests raised and closed
- Community updates
- Software Development Updates
- Project Management Update
- Tasks Completed this week
- Upcoming tasks for next week

This will be created and uploaded on our GitHub on a fortnightly basis.
It will also be included/linked to in our newsletter and presented as an agenda piece in our meet-ups.

## Frequency of Communications

Meeting | Engagement
----|------
Autistica/Turing Citizen Science Meet-up | Every 2nd and 4th Thursday of the month, Pre-engagement, Post-engagement
Autistica/Turing Citizen Science Co-working sessions | Weekly, Pre-engagement, Post-engagement
Knowledge Sharing Sessions | Fortnightly, Pre-engagement, Post-engagement
Newsletter | Monthly distribution
Onboarding calls | 1:1 chats, introduction at Mett-ups
Leadership meetings | Weekly
Twitter | Continuous
Slack - Continuous

### Pre-engagement

The aim of these communications will be to specifically advertise up-coming events/meetings.

They will be used to inform of the topics that will be discussed as well as allowing for topics to be proposed. This could be via a HackMD/Google doc to also allow people to "sign up" so that we have an idea of who is coming to the meeting.

Links to the meeting and calendar invites will be included.

Link to previous meeting summary will also be available with a small explanation of what was discussed.

### Post-engagement

The aim of these communications will be to capture what happened in the meeting that has occured.

This will include a link to the most recent summary of the meeting, in which those that attended can be reminded of what happened and those who did not attend can catch up.

Link to the recording of the meeting (?)

3 comments on commit 6bf6fc8

@SuziQpid
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are typos in the section .... newsletter. Need to add an i to information. In frequency of meetings you need to say meet-ups where you have metup. I can offer to proofread pieces like this and do necessary typo corrects with small grammatical errors where it doesn’t change the sense if l correct it.

@GeorgiaHCA
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @SuziQpid !

@GeorgiaHCA
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a lot of stuff on the repository so if you read through and proofread anything you feel like and point out any errors that would be amazing !! I'll also be adding things soon later today so grateful if you want to look at that when you have a moment @SuziQpid. I can proofread other people but I'm terrible at proofreading my own writing!!

Please sign in to comment.