omigroup · fire · Nov 30, 2022
diff --git a/README.md b/README.md
@@ -1,25 +1,29 @@
 # Media and Content Strategy Working group
 
-## About: 
-This group is focused on media, content-curation and events. Coordinating material, curation, and timing of our content. We explore things like using our blog to republish content from our community, and collaboratively champion an Open Metaverse. 
+## About:
 
-## How you can get involved: 
-- The group meets on the second Tuesday every month at 15:30 - 16:30 UTC (24:00 Format) 
+This group is focused on media, content-curation and events. Coordinating material, curation, and timing of our content. We explore things like using our blog to republish content from our community, and collaboratively champion an Open Metaverse.
+
+## How you can get involved:
+
+- The group meets on the second Tuesday every month at 15:30 - 16:30 UTC (24:00 Format)
 - We track our active tickets with our [Github Projects Kanban Backlog](../../projects/1?add_cards_query=is%3Aopen)
 - We organize our backlog with intent using github [Milestones](../../milestones) which makes it easier to track progress based on desired outcomes and objectives.
-- We discuss our efforts using [github discussions](../../discussions). This is where we have all of our major discussions, and it is the preferred method of communicating ideas and asking questions. 
-- We also have a [# OMI-Media discord channel](https://discord.gg/FkkjWGW7Nw), for general chatter, but not ideal for planning. 
-- Any questions? Contact the designated working group lead(s) Shirley (LMB | LittleMissBold on Discord / @pcsmgnt on Github) or Evo (@evo on Discord and @lightlodges on github) or Jesse (mrmetaverse#0001 on discord / @mrmetaverse on github). 
+- We discuss our efforts using [github discussions](../../discussions). This is where we have all of our major discussions, and it is the preferred method of communicating ideas and asking questions.
+- We also have a [# OMI-Media discord channel](https://discord.gg/FkkjWGW7Nw), for general chatter, but not ideal for planning.
+- Any questions? Contact the designated working group lead(s) Shirley (LMB | LittleMissBold on Discord / @pcsmgnt on Github) or Evo (@evo on Discord and @lightlodges on github) or Jesse (mrmetaverse#0001 on discord / @mrmetaverse on github).
+
+Our Commitments:
 
-Our Commitments: 
 - Recurring meeting is on the second Tuesday every month at 16:00 - 17:00 UTC (24:00 Format) to accommodate MSF commitments. 15:30 - 16:30 UTC was the old time.
 - Our [working agreement can be found here](../../discussions) on github discussions
 - We have a quick group retrospective at the start of every meeting, to reflect on what is going well, what could be improved, and what we will do differently next cycle. (NEED ANALYTICS DASHBOARD -> create ticket)
 - We will / or will not be recording our meetings and you can or can not find those meeting recordings here
-- We will create an agenda before our recurring meetings, and take notes during our meeting. 
+- We will create an agenda before our recurring meetings, and take notes during our meeting.
 
-## Our media channels: 
-- Twitter 
+## Our media channels:
+
+- Twitter
 - Twitch
 - Youtube
 - Discord
@@ -28,6 +32,7 @@ Our Commitments:
 - LinkedIn
 - Reddit
 
-Upcoming efforts: 
+Upcoming efforts:
+
 - content sprint 1 - see issue #3
 - NEED ANALYTICS DASHBOARD - see issue #6
diff --git a/WORKING_AGREEMENT.md b/WORKING_AGREEMENT.md
@@ -1,9 +1,11 @@
 ## Team Norms
+
 _Team Norms are explicit agreements on how we’ll behave together and what we’ll do if an agreement is broken. It’s everyone’s responsibility to set and uphold these agreements, but it’s truly the Team Leader’s role to ensure the team lives by these norms._
 
-## 1. Team Ground Rules 
+## 1. Team Ground Rules
+
 How do we want to treat each other? (Try to keep the list to the most essential 3-5.)
-Rule #1: 
+Rule #1:
 Rule #2:
 Rule #3:
 
@@ -13,30 +15,31 @@ _We conduct routine retrospectives to air out the good, the bad, and the improva
 _Be on time!_  
 _If you’re going to be late, post in the team discord channel to let the team know (be accountable)_
 
-## 2. When we meet / Ceremonies 
-Recurring meeting day and cadence: 
-Demo days: 
-Retrospective: 
+## 2. When we meet / Ceremonies
+
+Recurring meeting day and cadence:
+Demo days:
+Retrospective:
 
-_Examples remove any that don't fit your working group or that you do not want_ 
+_Examples remove any that don't fit your working group or that you do not want_
 
-- Daily standup - discord check in 
+- Daily standup - discord check in
 - Sprint Review - have sprint review prep (last day of the sprint for 15 min)
-sprint review/checklist will be created in Confluence
+  sprint review/checklist will be created in Confluence
 - **Sprint Retros - anonymous entries, but able to own it if you want be open, honest and respectful to your teammates**
 - Sprint Planning - this should be capacity and velocity planning with PREVIOUSLY groomed stories from our backlog
 - Grooming
 
 ## 3. Keeping Ourselves Accountable
+
 Now that we have our norms, how will we hold ourselves accountable? What will we do if we see ourselves or someone else break a rule?
 Method 1:
 Method 2:
 
 _Ideas: (delete after you decide on yours)_
 _We chat in discord, but we track efforts on our github backlog_
 _Discord bot to send a prompt to remind group members with omi-chan role of upcoming meetings_
-_Simple Google form survey every 4 weeks to rate ourselves on a scale of 1 to 5, and suggest improvements (maybe instead of a actual proper retro, but I still recommend a retro)_ 
-_We review our working agreement at every retro._ 
-
+_Simple Google form survey every 4 weeks to rate ourselves on a scale of 1 to 5, and suggest improvements (maybe instead of a actual proper retro, but I still recommend a retro)_
+_We review our working agreement at every retro._
 
-###### Note: The system should flex to your needs, not the other way around. Make sure you adopt processes that fit your needs and availability. There is nothing worse than resentment of process which leads to avoidance and eventually the entire effort fizzling out. We adopt these simple standards to make it easier for folks to get involved, and increase the chances of us finishing the the things we say we will do. Declaring yourself as blocked is not bad! It helps let the rest of the group know that they can help, etc. 
+###### Note: The system should flex to your needs, not the other way around. Make sure you adopt processes that fit your needs and availability. There is nothing worse than resentment of process which leads to avoidance and eventually the entire effort fizzling out. We adopt these simple standards to make it easier for folks to get involved, and increase the chances of us finishing the the things we say we will do. Declaring yourself as blocked is not bad! It helps let the rest of the group know that they can help, etc.
diff --git a/w3c.json b/w3c.json
@@ -1,5 +1,5 @@
 {
   "group": [130919],
   "contacts": ["robertlong"],
-  "repo-type":  "cg-report"
+  "repo-type": "cg-report"
 }