Updating docs with Community section.

docs/community/discord.md

@@ -0,0 +1,11 @@
+# Lagoon Community on Discord
+
+Our official community meeting space is the Lagoon [Discord](https://discord.gg/te5hHe95JE).
+
+We’re starting this community as a place for all Lagoon users to collaborate, solve problems, share ideas, and contribute back to the Lagoon project. We’re working to consolidate our community as it’s currently spread out over Slack and various other places. We also wanted to invite all of our users and customers to join so that everyone can benefit from the community, no matter how they’re using Lagoon.
+
+_Please remember that this is not to replace your current support channels - those will remain the same. This is a place to connect with other users as well as the Lagoon maintainers._
+
+We ask that all community members review our [Participation](participation.md) and [Moderation](moderation.md) Guidelines, as well as the [Code of Conduct](../code-of-conduct.md).
+
+In addition to our [Zoom Community Hours](https://dev.to/uselagoon/lagoon-community-hours-2022-4bd4), we'll also be hosting Community Hours on Discord in 2023!

docs/community/moderation.md

@@ -0,0 +1,24 @@
+# Lagoon Moderation Guidelines
+
+_These guidelines have been adapted from [Drupal Diversity & Inclusion’s Moderation Guidelines](https://www.drupaldiversity.com/docs/moderation-guidelines)._
+
+In Lagoon spaces, strive to promote understanding, empathy, and increase personal awareness of all people. This includes people from across the Drupal Community and the greater Technical Community, even those you may personally disagree with.
+
+If kicked from the Discord, the kicked user can send a private message (PM) to the kicker or another Moderator, if desired, for re-admittance. If a disruptive person is engaging in what appears to be intentionally inflammatory, bullying, or harassing behavior provoking hostile responses (or acting in a hostile manner), kicking is faster and easier than trying to placate a disruptive person whose behavior is causing distress to other channel members.
+
+The kick is not a ban. There are times when disruptive or triggering comments and statements are genuine and break the lines of communication between two parties. By speaking with a Moderator, the (potentially) disruptive person can be coached on using more sensitive, inclusive, and diverse-aware language, and on engaging in a more constructive manner.
+
+## Tiered Responses
+
+1. Tier One Response
+    User is welcomed in the channel, asked to read some scroll back, and given a link to participation guidelines.
+2. Tier Two Response
+    User is gently reminded in channel to keep posts on topic, and/or of participation guidelines.
+3. Tier Three Response
+    User is PM’d by available Moderator to explain the problem(s) with their posts and given suggestions of what to do differently.
+4. Tier Four Response
+    If behavior continues, User is kicked for no less than 24 hours from the Discord.
+
+## Non-Tiered Response Banning
+
+Intentionally disruptive individuals get kicked, not tiered. Repeated offenses will result in a ban.

docs/community/participation.md

@@ -0,0 +1,55 @@
+# Lagoon Participation Guidelines
+
+We ask that all members of our community, in any spaces, virtual or physical, adhere to our [Code of Conduct](../code-of-conduct.md).
+
+_These guidelines have been adapted from [Drupal Diversity & Inclusion’s Participation Guidelines](https://www.drupaldiversity.com/docs/participant-guidelines)._
+
+1. Listen actively, read carefully, and be understanding.
+    - If joining a conversation, read the backlog. Give other Participants the opportunity to communicate effectively.
+    - Assume good intent behind other Participants’ statements. The open-source software community is very diverse, with Participants from all over the globe. Be aware of cultural and linguistic quirks.
+    - There are also many Participants who are new to this space. Assume that they have good intent but have not yet mastered the language or ideas. We want to help them!
+2. Speak from your own experience, instead of generalizing. Recognize the worth of others’ experience. Try not to speak for others.
+    - Use “I” instead of “they,” “we,” and “you”.
+    - All Participants should recognize that other Participants have their own unique experiences.
+    - Don’t invalidate another Participant’s story with your own spin on their experience. Instead, share your own story and experience.
+3. Challenge ideas, feelings, concerns, or one another by asking questions. Refrain from personal attacks. Focus on ideas first.
+    - Avoid verbal challenges, backhanded insults, gender/race/region stereotyping, etc.
+4. Take part to the fullest of your ability and availability.
+    - Community growth depends on the inclusion of individual voices. The channel wants you to speak up and speak out. Everyone has a different amount of time to contribute. We value participation here if you can give 5 minutes or 5 hours.
+    - We do welcome those who quietly come to lurk and learn, or “lurk,” but please introduce yourself and say hello!
+5. Accept that it is not always the goal to agree.
+    - There are often many different “right” answers to technical issues, even though they may not work for your setup.
+6. Be conscious of language differences and unintended connotations.
+    - “Text is hard” - be aware that it is difficult to communicate effectively via text.
+7. Acknowledge individuals’ identities.
+    - Use stated names and pronouns. Do not challenge a person’s race, sexuality, disability, etc.
+    - If you are unsure how to address someone, ask them discreetly and respectfully. For example, if you are unsure what pronouns to use, send a private message and ask. Using the correct pronouns will help others.
+8. Some off-topic conversation is okay.
+    - Some cross posting of announcements is okay. The following is not permitted:
+        - Thread hijacking
+        - Spamming
+        - Commercial advertising
+        - Overt self-promotion
+        - Excessive going off-topic, especially during official meeting times or focused conversations
+    - Consider announcing more appropriate places or times for in-depth off-topic conversations.
+    - If you are not sure what’s appropriate, please contact an admin.
+9. Sharing content from inside Lagoon spaces must only be done with explicit consent. Any sharing must also be carefully considered, and without harassment or intent to harm any Participants.
+    - This forum should be considered public. Assume that anyone can and may read anything posted here.
+    - When sharing any Lagoon content, permission from all Participants must be obtained first. This applies whether content is quoted, summarized, or screenshotted. This includes sharing in any public medium: on Twitter, in a blog post, in an article, on a podcast, etc. These spaces are where the discussion and work in progress is taking place. Removing snippets of a conversation takes away context. This can distort and discourage discussion, especially when this is done without the goal of driving the Lagoon project forward.
+    - As stated above, if you take screenshots and post them to social media or other forums, you must get permission from the person that posted it. When getting permission, include the option of removing identifying information. Permission is still needed even if identifying information is removed. This includes any content from Discord, Github, or any other Lagoon medium.
+    - If you want to share something, just ask! “Hey, is it ok to share this on Twitter? I’m happy to credit you!”
+    - If it is necessary for a participant to take a screenshot to report harassing behavior to Lagoon moderators, this may be done without obtaining permission. It is not, however, acceptable to take screenshots to publicly or privately shame an individual. Again, this applies only to reporting harassing behavior.
+10. Address complaints between one another in the space when safe and appropriate.
+    - When safe, try to clarify and engage in the space where the conflict happened. For example, in the Discord channel.
+    - Ping admins or Community Manager (Alanna) when conflict is escalating.
+    - Ask for help.
+    - If the topic of conflict is off-topic for Lagoon, move the conversation to a more appropriate channel.
+
+Additional considerations for in-person Lagoon spaces
+
+1. Follow the event’s Code of Conduct, if there is one. If not, our Code of Conduct applies.
+2. Do not touch people, their mobility devices, or other assistive equipment without their consent. If someone asks you to stop a certain behavior, stop immediately.
+3. Report any issues to the event’s staff.
+If an issue involves Lagoon team members, report to [email protected].
+
+The Lagoon team reserves the right to terminate anyone’s access to the Lagoon spaces.

mkdocs.yml

@@ -124,12 +124,16 @@ nav:
 - Contributing to Lagoon:
   - Contributing: contributing.md
   - Developing Lagoon: contributing-to-lagoon/developing-lagoon.md
-  - Code of Conduct: contributing-to-lagoon/code-of-conduct.md
+  - Code of Conduct: code-of-conduct.md
   - Documentation: contributing-to-lagoon/documentation.md
   - Tests: contributing-to-lagoon/tests.md
   - API Debugging: contributing-to-lagoon/api-debugging.md
-- Resources:
+- Community:
   - Code of Conduct: code-of-conduct.md
+  - Discord: community/discord.md
+  - Participation Guidelines: community/participation.md
+  - Moderation Guidelines: community/moderation.md
+- Resources:
   - FAQ: resources/faq.md
   - Glossary: resources/glossary.md
   - Tutorials, Webinars, and Videos: resources/tutorials-and-webinars.md