-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lottycoupat comms strategy #461
base: master
Are you sure you want to change the base?
Changes from all commits
31afb3f
6bf6fc8
d2500f6
25f08c0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,131 @@ | ||||||
# Participation and Communication Strategy | ||||||
|
||||||
This is where you will find all information and strategic direction of our communicaion and engagement to ensure participation on the AutSPACEs Project. | ||||||
|
||||||
## Mountain of Engagement | ||||||
|
||||||
Our Mountain of Engagement (MoE) can be seen in the below image. | ||||||
|
||||||
[insert image here] | ||||||
|
||||||
It shows the levels of engagement and participation that there is within the Project. | ||||||
It is important to note that there is not a hierarchy in relation to how important you are to the project. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is great! |
||||||
Each level is crucial and fundamental to the success of the project. | ||||||
|
||||||
The MoE allows us to map out where contributors lie and where we can provide opportunities to allow individuals to increase their participation to the next level. | ||||||
A key difference between each level is the responsibility the individual has to the project. | ||||||
As the level increases so does that individuals responsibility accordingly. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
The MoE seeks out opportunities for contrbutors to move up the scale if they are happy to do so and the community manager will ensure this happens and opportunities are available. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## Onboarding New Members | ||||||
|
||||||
When new members show interest in being a part of the project, they will be onboarded and briefed on the project's aims and objectives as well as progress update. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
This will be in the form of an onboarding pack which includes all materials that is needed to succesfully understand the project, as well as a 1:1 chat with the Community Manager who will ensure all information is understood. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the 1:1 chat something we can offer as the project grows? If you have capacity to do this, that's great! The strategy can also be changed if needed. |
||||||
|
||||||
There is also an onboarding checklist to ensure that all new members receive all the required information. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fab! |
||||||
|
||||||
|
||||||
## In person Communications | ||||||
|
||||||
This engagement will involve face to face communication with and between contributors of the project. Due to the current COVID circumstances as well as the geographically spread out nature of this project, this will be in the form of online video conferencing (Zoom). | ||||||
|
||||||
### Meet-ups | ||||||
|
||||||
Currently we have meet-ups scheduled every 2nd and 4th Thursday of the month, where anyone who is interested in the project can participate. | ||||||
|
||||||
One key channel in which individuals find out about these meet-ups is through connection with Autistica and through Twitter. | ||||||
Therefore these are two engagement pathways that will be continnuously active to ensure maintenance and increase in participation. | ||||||
|
||||||
The aim of the meet-ups is to discuss and work on different areas of the project as well as a space for onboarding. | ||||||
|
||||||
The google doc, which provides the Agenda and a way to sign up to the session and it's breakout rooms, will be distributed to a mailing list of individuals. | ||||||
A link to the summary of notes will also be distributed after the session to ensure engagement after the session and ahead of the next one. | ||||||
|
||||||
### Co-working (TBC) | ||||||
|
||||||
The aim of these sessions would be for contributors to come together and work on specific topics together. | ||||||
It will also be a space in which individuals can come together and work in collaboaration on different topics and porvide support wherever needed. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
### Knowledge Share (TBC) | ||||||
|
||||||
These sessions would be to knowledge share on a specific aspect/topic of the project to keep all members updated on what is going on in the different branches of the project. | ||||||
These could be schedueld in accordance 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 session can be used for that. | ||||||
|
||||||
## Online Communications | ||||||
|
||||||
The aim of online communications is to keep contributors engaged in the periods between project (in-person) sessions. | ||||||
These will be through various online platforms as explained below. | ||||||
|
||||||
### 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. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
It will also include information 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. | ||||||
|
||||||
|
||||||
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 | ||||||
Project Team Meetings | Fortnightly | ||||||
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. | ||||||
This will also include the next date, where possible, of the next meeting. | ||||||
|
||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very clear and great to have this all in one place! Maybe it would be best to have it as a folder in the main repo?