Converting community-wide-resources to rst

docs/index.rst

@@ -15,3 +15,10 @@ The vision is that it grows over time as the teams and governance structure evol
    :hidden:
 
    about/what_is_mautic
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Pages
+   :hidden:
+
+   Pages/Community-wide-resources

docs/links/Art-of-community-book.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "The Art of Community" 
+link_text = "The Art of Community"
+link_url = "http://www.artofcommunityonline.org/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/Jono-bacon-video.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Jono Bacon's how to prevent burnout video"
+link_text = "Jono Bacon's how to prevent burnout video"
+link_url = "https://www.youtube.com/watch?v=WC1bpYGoB7s" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/everytimezone.py

@@ -0,0 +1,6 @@
+from . import link
+
+link_name = "everytimezone" 
+link_text = "everytimezone"
+link_url = "https://everytimezone.com/"
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/kubuntu-link.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Kubuntu" 
+link_text = "Kubuntu" 
+link_url = "https://wiki.kubuntu.org/BuildingCommunity/Burnout/Help" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/mautic-google-drive.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Mautic Google Drive" 
+link_text = "Mautic Google Drive"
+link_url = "https://drive.google.com/drive/folders/1lUQyFnrPEZKlrmhP9HedxSnDGY3StMXx" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/mautic-meeting-parser.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Mautic Meeting Parser" 
+link_text = "Mautic Meeting Parser"
+link_url = "https://github.com/RCheesley/mautic-meeting-parser" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/suicide-prevention-lifeline.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Suicide Prevention Lifeline" 
+link_text = "Suicide Prevention Lifeline" 
+link_url = "http://www.suicidepreventionlifeline.org/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/wikipedia.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Wikipedia" 
+link_text = "Wikipedia" 
+link_url = "https://en.wikipedia.org/wiki/List_of_suicide_crisis_lines" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/pages/07.community-wide-resources/.revs/20200310-170715/chapter.rst

@@ -0,0 +1,3 @@
+========================
+Community-wide resources
+========================

docs/pages/07.community-wide-resources/02.meetings/.revs/20200310-170715/chapter.rst

@@ -0,0 +1,13 @@
+========
+Meetings
+========
+
+
+Meetings
+==========
+
+As a widely distributed team of volunteers, we work together
+collaboratively using both synchronous and asynchronous meetings.
+
+This section provides some useful resources and suggestions for how to
+run successful community meetings.

docs/pages/07.community-wide-resources/02.meetings/11.asynchronous-async-meetings/.revs/20200310-170715/docs.rst

@@ -0,0 +1,106 @@
+======================
+Slack (async) meetings
+======================
+
+--------------
+
+Slack threads are a great way to hold meetings because:
+
+- They don’t rely on everybody being available to attend the meeting at
+  a specific time - often async meetings are open for 24 hours
+- They don’t require the ability to keep pace with a verbal
+  conversation, which can be tricky for those with disabilities or for
+  whom English is not their first language
+- There is a written record of the meeting which can be easily exported
+
+We use asynchronous Slack meetings heavily in the Mautic community, and
+it’s likely that you’ll be called upon at some point to run one!
+
+Running an asynchronous Slack meeting
+=====================================
+
+Here are some tips for running a great meeting:
+
+1. Prepare for the meeting as you would for any other - share an agenda
+   at least 24 hours before the meeting is due to start, ideally on
+   Slack and on the forums, to remind people, to give them time to
+   prepare, and to encourage involvement/engagement
+2. Send a reminder 24 hours before the meeting in the relevant Slack
+   channel with the agenda - mention people directly if they are a
+   required attendee
+3. Prepare your topics in advance based on the agenda, so that you can
+   copy and paste them into the Slack channel without manually typing
+   them at the time. You can send them to yourself in Slack, so that you
+   have an easy-to-access record!
+4. Remember to use the welcome post and the introduction thread - this
+   welcomes people, explains how the meeting works, and allows people to
+   say who they are, and what they do - don’t assume that people joining
+   will know this, they might be completely new to the community!
+5. Take the meeting at the normal pace you would a regular meeting -
+   give people time to chime in on the topic and have the discussions
+   before posting the next topic. This helps to avoid distraction during
+   the meeting and thread-jumping!
+6. Always welcome new meeting attendees, and follow up if people have
+   dropped off and stopped attending
+7. Encourage participation by mentioning people who might be interested
+   in discussing the topic, or be interested in taking on a task
+8. Close the meeting by thanking people for joining
+9. Don’t forget to export the notes 24hrs (ish) after the meeting
+   started
+
+Exporting Slack meetings
+========================
+
+We use a fork of a Chrome extension created by the Drupal community in
+order to scrape Slack meeting notes into HTML, which can then be posted
+onto the forums.
+
+Instructions are provided in the Github repo:
+https://github.com/RCheesley/mautic-meeting-parser
+
+Sample meeting structure
+========================
+
+Welcome message
+---------------
+
+Welcome to the team meeting!
+
+If you haven’t done an asynchronous meeting before, please respond in
+threads :slightly_smiling_face:
+
+Also note you can start a reply with :bust_in_silhouette: to be anon, or
+:no_entry_sign: to go off the record and not be included in the notes,
+which will be exported and saved to Google Docs, and posted on the
+Community Forums.
+
+The meeting will be open for 24 hours, after which the notes will be
+exported. People may comment thereafter but these won’t be included in
+the notes.
+
+Let’s get going! :arrow_down:
+
+Topics
+------
+
+:zero:- Introductions : Who are you, where are you based, and how are you
+involved with this team?
+
+:one:- Review last meeting’s notes and actions (Share a link to the notes
+in a threaded reply, and call out any actions as sub tasks)
+
+:one:.:one:- Action item 1 
+:one:.:two:- Action item 2
+
+:two:- Review Trello tasks (share a link to the Trello board in a
+threaded reply, and call out any tasks as appropriate)
+
+:two:.:one:- Task 1 (Link to task in a threaded reply, brief
+explanation of status or actions needed)
+
+(continue through the open tasks)
+
+:three:- Any other business
+
+(Thank people for participating and give the date/time/format for the
+next meeting and who will be leading it)

docs/pages/07.community-wide-resources/02.meetings/11.asynchronous-async-meetings/docs.rst

@@ -0,0 +1,106 @@
+======================
+Slack (async) meetings
+======================
+
+--------------
+
+Slack threads are a great way to hold meetings because:
+
+- They don’t rely on everybody being available to attend the meeting at
+  a specific time - often async meetings are open for 24 hours
+- They don’t require the ability to keep pace with a verbal
+  conversation, which can be tricky for those with disabilities or for
+  whom English is not their first language
+- There is a written record of the meeting which can be easily exported
+
+We use asynchronous Slack meetings heavily in the Mautic community, and
+it’s likely that you’ll be called upon at some point to run one!
+
+Running an asynchronous Slack meeting
+=====================================
+
+Here are some tips for running a great meeting:
+
+1. Prepare for the meeting as you would for any other - share an agenda
+   at least 24 hours before the meeting is due to start, ideally on
+   Slack and on the forums, to remind people, to give them time to
+   prepare, and to encourage involvement/engagement
+2. Send a reminder 24 hours before the meeting in the relevant Slack
+   channel with the agenda - mention people directly if they are a
+   required attendee
+3. Prepare your topics in advance based on the agenda, so that you can
+   copy and paste them into the Slack channel without manually typing
+   them at the time. You can send them to yourself in Slack, so that you
+   have an easy-to-access record!
+4. Remember to use the welcome post and the introduction thread - this
+   welcomes people, explains how the meeting works, and allows people to
+   say who they are, and what they do - don’t assume that people joining
+   will know this, they might be completely new to the community!
+5. Take the meeting at the normal pace you would a regular meeting -
+   give people time to chime in on the topic and have the discussions
+   before posting the next topic. This helps to avoid distraction during
+   the meeting and thread-jumping!
+6. Always welcome new meeting attendees, and follow up if people have
+   dropped off and stopped attending
+7. Encourage participation by mentioning people who might be interested
+   in discussing the topic, or be interested in taking on a task
+8. Close the meeting by thanking people for joining
+9. Don’t forget to export the notes 24hrs (ish) after the meeting
+   started
+
+Exporting Slack meetings
+========================
+
+We use a fork of a Chrome extension created by the Drupal community in
+order to scrape Slack meeting notes into HTML, which can then be posted
+onto the forums.
+
+Instructions are provided in the Github repo:
+https://github.com/RCheesley/mautic-meeting-parser
+
+Sample meeting structure
+========================
+
+Welcome message
+---------------
+
+Welcome to the team meeting!
+
+If you haven’t done an asynchronous meeting before, please respond in
+threads :slightly_smiling_face:
+
+Also note you can start a reply with :bust_in_silhouette: to be anon, or
+:no_entry_sign: to go off the record and not be included in the notes,
+which will be exported and saved to Google Docs, and posted on the
+Community Forums.
+
+The meeting will be open for 24 hours, after which the notes will be
+exported. People may comment thereafter but these won’t be included in
+the notes.
+
+Let’s get going! :arrow_down:
+
+Topics
+------
+
+:zero:- Introductions : Who are you, where are you based, and how are you
+involved with this team?
+
+:one:- Review last meeting’s notes and actions (Share a link to the notes
+in a threaded reply, and call out any actions as sub tasks)
+
+:one:.:one:- Action item 1 
+:one:.:two:- Action item 2
+
+:two:- Review Trello tasks (share a link to the Trello board in a
+threaded reply, and call out any tasks as appropriate)
+
+:two:.:one:- Task 1 (Link to task in a threaded reply, brief
+explanation of status or actions needed)
+
+(continue through the open tasks)
+
+:three:- Any other business
+
+(Thank people for participating and give the date/time/format for the
+next meeting and who will be leading it)