From 825b08f669a33a66d13e2ba916fba0e2b2bc1dca Mon Sep 17 00:00:00 2001 From: Craig Buchek Date: Thu, 21 Jun 2018 13:21:50 -0500 Subject: [PATCH 01/43] CoC: A couple small additions Hopefully to clarify some situations I've seen lately. --- content/code-of-conduct.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index b93aedf..c8bbb0f 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -20,9 +20,11 @@ Harassment includes: - Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical - appearance, body size, age, race, or religion. + appearance, body size, age, race, or religion. Note that "offensive" includes + questioning the person's right to equal treatment. - Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment. +- [Concern trolling](http://geekfeminism.wikia.com/wiki/Concern_troll). - Deliberate misgendering or use of ‘dead’ or rejected names. - Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate. From 8934ff5ca4c56f4bbfb3313a667f78f2985935b3 Mon Sep 17 00:00:00 2001 From: beccastevens Date: Wed, 31 Oct 2018 13:20:09 -0500 Subject: [PATCH 02/43] Update member-handbook.md --- content/member-handbook.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/member-handbook.md b/content/member-handbook.md index 9f3f725..cdc551c 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -155,5 +155,8 @@ If you have any problems, use the `/admin` command and someone will respond soon * Rebecca Skinner (@rebecca.skinner) - Admin * Becca Stevens (@beccastevens) - Moderator * Tristan Blease (@thetristan) - Moderator +* Keith Brown (@hellmark) - Moderator +* Craig Buchek (@craigbuchek) - Moderator +* Ryan Colmean (@ryuhhnn) - Moderator Moderators are chosen by the admins for being helpful in community spaces. From 3df322c19af2de3927a4e7ad24e22db573dd52af Mon Sep 17 00:00:00 2001 From: beccastevens Date: Wed, 31 Oct 2018 13:21:03 -0500 Subject: [PATCH 03/43] Update code-of-conduct.md --- content/code-of-conduct.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index b93aedf..de1fb20 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -100,6 +100,9 @@ list below: - Rebecca Skinner (@rebecca.skinner) - Becca Stevens (@beccastevens) - Tristan Blease (@thetristan) +- Keith Brown (@hellmark) +- Craig Buchek (@craigbuchek) +- Ryan Colmean (@ryuhhnn) ## Source From 8cee65b556b8199cdc7221deb4b75097cc0a2811 Mon Sep 17 00:00:00 2001 From: Tristan Blease Date: Sun, 5 May 2019 10:30:58 -0500 Subject: [PATCH 04/43] Update CoC --- content/code-of-conduct.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index e7ca5a6..0c0ca8a 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -28,9 +28,11 @@ Harassment includes: - Deliberate misgendering or use of ‘dead’ or rejected names. - Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate. +- Gratuitous or off-topic discussions of violence or violent behaviour in this + space. - Physical contact and simulated physical contact (eg, textual descriptions like `*hug*` or `*backrub*`) without consent or after a request to stop. -- Threats of violence. +- Threats of violence towards any individual, group, or society at large. - Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm. - Deliberate intimidation. From 7b720e56b0a9e2a5faa6e7b8bfcc8e2a0b034df0 Mon Sep 17 00:00:00 2001 From: Tristan Blease Date: Sun, 5 May 2019 11:10:09 -0500 Subject: [PATCH 05/43] Remove Rebecca, correct typo in Ryan's name --- content/code-of-conduct.md | 3 +-- content/member-handbook.md | 11 +++++------ 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index e7ca5a6..c03e008 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -99,12 +99,11 @@ Tech members or the general public. the incident response team can be reached by directly messaging anyone on the list below: -- Rebecca Skinner (@rebecca.skinner) - Becca Stevens (@beccastevens) - Tristan Blease (@thetristan) - Keith Brown (@hellmark) - Craig Buchek (@craigbuchek) -- Ryan Colmean (@ryuhhnn) +- Ryan Coleman (@ryuhhnn) ## Source diff --git a/content/member-handbook.md b/content/member-handbook.md index cdc551c..1b737cb 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -152,11 +152,10 @@ That said, here are some things we might do, in rough order of severity: The moderation team is here to help you and to guide conversation towards good places. If you have any problems, use the `/admin` command and someone will respond soon. -* Rebecca Skinner (@rebecca.skinner) - Admin -* Becca Stevens (@beccastevens) - Moderator -* Tristan Blease (@thetristan) - Moderator -* Keith Brown (@hellmark) - Moderator -* Craig Buchek (@craigbuchek) - Moderator -* Ryan Colmean (@ryuhhnn) - Moderator +* Becca Stevens (@beccastevens) +* Tristan Blease (@thetristan) +* Keith Brown (@hellmark) +* Craig Buchek (@craigbuchek) +* Ryan Coleman (@ryuhhnn) Moderators are chosen by the admins for being helpful in community spaces. From 31f15acd272201d10431057a483898e4d658fade Mon Sep 17 00:00:00 2001 From: Tristan Blease Date: Mon, 6 Jan 2020 12:48:54 -0600 Subject: [PATCH 06/43] Update CoC to remove Tristan, Ryan --- content/code-of-conduct.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index c1111fe..5064f44 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -102,10 +102,8 @@ the incident response team can be reached by directly messaging anyone on the list below: - Becca Stevens (@beccastevens) -- Tristan Blease (@thetristan) - Keith Brown (@hellmark) - Craig Buchek (@craigbuchek) -- Ryan Coleman (@ryuhhnn) ## Source From bb95b6996bf028b7c283ab56710f9387a663cb04 Mon Sep 17 00:00:00 2001 From: Tristan Blease Date: Mon, 6 Jan 2020 12:49:53 -0600 Subject: [PATCH 07/43] Update Member Handbook to remove Tristan, Ryan --- content/member-handbook.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/member-handbook.md b/content/member-handbook.md index 1b737cb..c8532ad 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -153,9 +153,7 @@ The moderation team is here to help you and to guide conversation towards good p If you have any problems, use the `/admin` command and someone will respond soon. * Becca Stevens (@beccastevens) -* Tristan Blease (@thetristan) * Keith Brown (@hellmark) * Craig Buchek (@craigbuchek) -* Ryan Coleman (@ryuhhnn) Moderators are chosen by the admins for being helpful in community spaces. From 73f956801ce77e4fbb14264ed37280ac315f932f Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Wed, 8 Jan 2020 12:03:54 -0600 Subject: [PATCH 08/43] correct typos, add small amount of content to CoC and Handbook --- content/code-of-conduct.md | 7 ++++--- content/member-handbook.md | 3 ++- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index 5064f44..cd0da9f 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -10,7 +10,7 @@ do not tolerate harassment of participants in any form. This code of conduct applies to all STL Tech spaces, including the STL Tech Slack and Github Repositories, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the -discretion of the the incident response team. +discretion of the the incident response team. **Please note that STL Tech spaces are not public spaces** and that interpretation of this Code of Conduct in matters of sanctioning or expelling participants in violation of same is at the sole discretion of the incident response team. Some STL Tech spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and @@ -26,9 +26,9 @@ Harassment includes: including those related to food, health, parenting, drugs, and employment. - [Concern trolling](http://geekfeminism.wikia.com/wiki/Concern_troll). - Deliberate misgendering or use of ‘dead’ or rejected names. -- Gratuitous or off-topic sexual images or behaviour in spaces where they’re not +- Gratuitous or off-topic sexual images or behavior in spaces where they’re not appropriate. -- Gratuitous or off-topic discussions of violence or violent behaviour in this +- Gratuitous or off-topic discussions of violence or violent behavior in this space. - Physical contact and simulated physical contact (eg, textual descriptions like `*hug*` or `*backrub*`) without consent or after a request to stop. @@ -47,6 +47,7 @@ Harassment includes: - Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse. - Publication of non-harassing private communication. +- Complaining of ‘reverse‘ -isms (‘reverse racism,’ ‘reverse sexism,’, ‘cisphobia’, etc), or otherwise attempting to legitimize the same as discrimination or oppression, will not be tolerated under any circumstances STL Tech prioritizes marginalized people’s safety over privileged people’s comfort. the incident response team will not act on complaints regarding: diff --git a/content/member-handbook.md b/content/member-handbook.md index c8532ad..9e8c46d 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -29,6 +29,7 @@ Here are the channels that likely won't change, and which everyone should know a - **#jobs**: the job board. Please restrict this to primarily job postings - **#careers**: more general disucssion about careers (resumés, job hunting, et cetera.) +- **#welcome**: this is a space for new people to introduce themselves and the community to welcome them to our space! If you want to make a new channel, read the rest of this guide and then do it. If you have any questions, please ask in #meta. @@ -104,7 +105,7 @@ If you're in doubt or have questions, ask in #meta or DM a moderator or admin di New members join frequently. Make sure they feel welcome and supported when they show up. -If they're your coworkers or friends, please introduce them (if they're comfortable) in #everything. +If they're your coworkers or friends, please introduce them (if they're comfortable) in #welcome. If you're new, feel free to introduce yourself! ## Please Don't Do These Things From 610571f4ad19e2e9d6db0680e763e87f4b1a1bb6 Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Wed, 8 Jan 2020 12:05:24 -0600 Subject: [PATCH 09/43] add silug --- content/code-of-conduct.md | 1 + content/member-handbook.md | 1 + 2 files changed, 2 insertions(+) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index 5064f44..fc8f4f2 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -104,6 +104,7 @@ list below: - Becca Stevens (@beccastevens) - Keith Brown (@hellmark) - Craig Buchek (@craigbuchek) +- Steven Pritchard (@silug) ## Source diff --git a/content/member-handbook.md b/content/member-handbook.md index c8532ad..d7ee02c 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -155,5 +155,6 @@ If you have any problems, use the `/admin` command and someone will respond soon * Becca Stevens (@beccastevens) * Keith Brown (@hellmark) * Craig Buchek (@craigbuchek) +* Steven Pritchard (@silug) Moderators are chosen by the admins for being helpful in community spaces. From 052a27a0865e7ba6d05d667dee27202db3320d7c Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Wed, 8 Jan 2020 12:07:14 -0600 Subject: [PATCH 10/43] re-add Rebecca --- content/code-of-conduct.md | 1 + content/member-handbook.md | 1 + 2 files changed, 2 insertions(+) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index 5064f44..4904915 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -104,6 +104,7 @@ list below: - Becca Stevens (@beccastevens) - Keith Brown (@hellmark) - Craig Buchek (@craigbuchek) +- Rebecca Skinner (@rebecca.skinner) ## Source diff --git a/content/member-handbook.md b/content/member-handbook.md index c8532ad..39d1bf3 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -155,5 +155,6 @@ If you have any problems, use the `/admin` command and someone will respond soon * Becca Stevens (@beccastevens) * Keith Brown (@hellmark) * Craig Buchek (@craigbuchek) +* Rebecca Skinner (@rebecca.skinner) Moderators are chosen by the admins for being helpful in community spaces. From 51875e974197a07d079a46707b9e85029d5d7301 Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Wed, 8 Jan 2020 12:15:43 -0600 Subject: [PATCH 11/43] move new not-public note to new line --- content/code-of-conduct.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index cd0da9f..14bb925 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -10,7 +10,9 @@ do not tolerate harassment of participants in any form. This code of conduct applies to all STL Tech spaces, including the STL Tech Slack and Github Repositories, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the -discretion of the the incident response team. **Please note that STL Tech spaces are not public spaces** and that interpretation of this Code of Conduct in matters of sanctioning or expelling participants in violation of same is at the sole discretion of the incident response team. +discretion of the the incident response team. + +**Please note that STL Tech spaces are not public spaces** and that interpretation of this Code of Conduct in matters of sanctioning or expelling participants in violation of same is at the sole discretion of the incident response team. Some STL Tech spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and From 26f1ad1bb2f875cb5d8381f9cb7dfe59e05ee4fa Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Wed, 8 Jan 2020 13:48:41 -0600 Subject: [PATCH 12/43] remove merge garbage, derp --- content/code-of-conduct.md | 1 - content/member-handbook.md | 1 - 2 files changed, 2 deletions(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index a68f0e1..243382d 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -109,7 +109,6 @@ list below: - Craig Buchek (@craigbuchek) - Rebecca Skinner (@rebecca.skinner) - Steven Pritchard (@silug) ->>>>>>> master ## Source diff --git a/content/member-handbook.md b/content/member-handbook.md index b2a5854..b6ab5ce 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -158,6 +158,5 @@ If you have any problems, use the `/admin` command and someone will respond soon * Craig Buchek (@craigbuchek) * Rebecca Skinner (@rebecca.skinner) * Steven Pritchard (@silug) ->>>>>>> master Moderators are chosen by the admins for being helpful in community spaces. From 8d26edacf5fb9d3f92ba5abd978e0f47c637cbb3 Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Thu, 5 Mar 2020 17:22:59 -0600 Subject: [PATCH 13/43] remove rebecca again :( --- content/code-of-conduct.md | 1 - content/member-handbook.md | 1 - 2 files changed, 2 deletions(-) diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md index 243382d..6f50be4 100644 --- a/content/code-of-conduct.md +++ b/content/code-of-conduct.md @@ -107,7 +107,6 @@ list below: - Becca Stevens (@beccastevens) - Keith Brown (@hellmark) - Craig Buchek (@craigbuchek) -- Rebecca Skinner (@rebecca.skinner) - Steven Pritchard (@silug) ## Source diff --git a/content/member-handbook.md b/content/member-handbook.md index b6ab5ce..316e1a4 100644 --- a/content/member-handbook.md +++ b/content/member-handbook.md @@ -156,7 +156,6 @@ If you have any problems, use the `/admin` command and someone will respond soon * Becca Stevens (@beccastevens) * Keith Brown (@hellmark) * Craig Buchek (@craigbuchek) -* Rebecca Skinner (@rebecca.skinner) * Steven Pritchard (@silug) Moderators are chosen by the admins for being helpful in community spaces. From 7e8a63e1d1d28d8201b2ea2d2f012debdd401426 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:22:14 -0500 Subject: [PATCH 14/43] Community Inviter link --- content/slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index 819c10d..2315da1 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use our self-inviter tool located at [slack.stltech.org](http://slack.stltech.org). +You can ask any current STL Tech member for an invitation, or use [Community Inviter](https://communityinviter.com/apps/stl-tech/default). See you soon! Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining. From c27247c4fe794cbd8d673425f702b8bf5cf88729 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:28:54 -0500 Subject: [PATCH 15/43] Add Community Inviter embed code to homepage --- config.yaml | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/config.yaml b/config.yaml index dddafb4..1f1e731 100644 --- a/config.yaml +++ b/config.yaml @@ -19,5 +19,19 @@ languages: title: "STL Tech" description: | The Online Home of the St. Louis Tech Community.
- Join us on Slack; We want to get to know you!
- Slack Status +
+ From 9ab9cd04d5b10277635b09579b78b39611a3766d Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:33:19 -0500 Subject: [PATCH 16/43] trying a fix for netlify --- config.yaml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/config.yaml b/config.yaml index 1f1e731..837c992 100644 --- a/config.yaml +++ b/config.yaml @@ -21,17 +21,17 @@ languages: The Online Home of the St. Louis Tech Community.
From 5d28bf9210d1b8fb1f1be5b5394e221b5a2ce4f7 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:35:53 -0500 Subject: [PATCH 17/43] removing embed code --- config.yaml | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) diff --git a/config.yaml b/config.yaml index 837c992..7048d66 100644 --- a/config.yaml +++ b/config.yaml @@ -18,20 +18,4 @@ languages: weight: 1 title: "STL Tech" description: | - The Online Home of the St. Louis Tech Community.
-
- + The Online Home of the St. Louis Tech Community. From 75db69a54ed0e993cd9b9cdb2698d883772942e2 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:37:08 -0500 Subject: [PATCH 18/43] trying embed code on slack.md --- content/slack.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index 2315da1..afab21f 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,23 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use [Community Inviter](https://communityinviter.com/apps/stl-tech/default). +
+ + See you soon! Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining. From 0ec451588c4be980518d0a645775c41a3cfa1863 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:39:45 -0500 Subject: [PATCH 19/43] "reverting" embed code --- content/slack.md | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/content/slack.md b/content/slack.md index afab21f..8cebdda 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,22 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -
- +You can ask any current STL Tech member for an invitation, or use [Community Inviter](https://communityinviter.com/apps/stl-tech/default). See you soon! From 2269931171d7c39c8352262b463e9e51d0d02622 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Tue, 21 Apr 2020 13:49:22 -0500 Subject: [PATCH 20/43] target blank y'all --- content/slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index 8cebdda..ea1abed 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use [Community Inviter](https://communityinviter.com/apps/stl-tech/default). +You can ask any current STL Tech member for an invitation, or use Community Inviter. See you soon! From 95c966e318737436493c9c6e946632dc87dc15e9 Mon Sep 17 00:00:00 2001 From: Keith Brown Date: Thu, 2 Sep 2021 13:55:16 -0500 Subject: [PATCH 21/43] Update slack.md Update community inviter link --- content/slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index ea1abed..83ff002 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use Community Inviter. +You can ask any current STL Tech member for an invitation, or use Community Inviter. See you soon! From eff7a16ec28e18937f081fbfa57f18858df44897 Mon Sep 17 00:00:00 2001 From: Keith Brown Date: Thu, 2 Sep 2021 13:57:15 -0500 Subject: [PATCH 22/43] Update slack.md --- content/slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index 83ff002..69fac0f 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use Community Inviter. +You can ask any current STL Tech member for an invitation, or use the Community Inviter. See you soon! From 75549a328a81da506cf8f54ba4fb8d1358448a1f Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:26:06 -0500 Subject: [PATCH 23/43] Removing missing dependency --- .gitmodules | 2 +- themes/dimension | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 160000 themes/dimension diff --git a/.gitmodules b/.gitmodules index 3add4d7..d9f4e19 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,3 +1,3 @@ [submodule "themes/dimension"] path = themes/dimension - url = https://github.com/sethmacleod/dimension + url = https://github.com/your-identity/hugo-theme-dimension diff --git a/themes/dimension b/themes/dimension deleted file mode 160000 index e648156..0000000 --- a/themes/dimension +++ /dev/null @@ -1 +0,0 @@ -Subproject commit e6481563275726656c28479744181c2fe686c4be From 9acb8dc47b915bfd8c1bc546314241d828a2c348 Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:27:53 -0500 Subject: [PATCH 24/43] Added replacement theme, which is also the same theme --- themes/dimension | 1 + 1 file changed, 1 insertion(+) create mode 160000 themes/dimension diff --git a/themes/dimension b/themes/dimension new file mode 160000 index 0000000..2474081 --- /dev/null +++ b/themes/dimension @@ -0,0 +1 @@ +Subproject commit 2474081b7846ce0e211c57b86ed84989548a777d From 9fa5050efdbabadc7b235468352f426895b48dbb Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:57:27 -0500 Subject: [PATCH 25/43] Change link to Markdown link, don't worry about target blank --- content/slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/slack.md b/content/slack.md index 69fac0f..3839d22 100644 --- a/content/slack.md +++ b/content/slack.md @@ -7,7 +7,7 @@ weight: 0 Most of the interaction in STL Tech happens on Slack. We invite you to join us! -You can ask any current STL Tech member for an invitation, or use the Community Inviter. +You can ask any current STL Tech member for an invitation, or use the [Community Inviter](https://communityinviter.com/apps/stl-tech/stl-tech). See you soon! From a2c9537fa0b48152da7d4a38bbf41bcffb6a71d8 Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:58:20 -0500 Subject: [PATCH 26/43] Update version number of Hugo to current --- netlify.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/netlify.toml b/netlify.toml index 6fe677b..9de8c76 100644 --- a/netlify.toml +++ b/netlify.toml @@ -3,4 +3,4 @@ command = "git submodule init && git submodule update && hugo" [context.environment] - HUGO_VERSION = "0.26" + HUGO_VERSION = "0.85" From 86facaafae29fc29e67f040eb8bd4e15e6ad596c Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:58:45 -0500 Subject: [PATCH 27/43] Add nix env --- .envrc | 1 + shell.nix | 7 +++++++ 2 files changed, 8 insertions(+) create mode 100644 .envrc create mode 100644 shell.nix diff --git a/.envrc b/.envrc new file mode 100644 index 0000000..051d09d --- /dev/null +++ b/.envrc @@ -0,0 +1 @@ +eval "$(lorri direnv)" diff --git a/shell.nix b/shell.nix new file mode 100644 index 0000000..4688987 --- /dev/null +++ b/shell.nix @@ -0,0 +1,7 @@ +{ pkgs ? import {} }: + +pkgs.mkShell { + buildInputs = [ + pkgs.hugo + ]; +} From cf281f90572b285b6002309386996e4f0ddc2b7e Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 21:58:57 -0500 Subject: [PATCH 28/43] Ignore public folder --- .gitignore | 1 + 1 file changed, 1 insertion(+) create mode 100644 .gitignore diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..a48cf0d --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +public From a6d1d272923a1f09a8e5190e4890a429ef6b7c99 Mon Sep 17 00:00:00 2001 From: sehqlr Date: Thu, 2 Sep 2021 22:14:12 -0500 Subject: [PATCH 29/43] Fixing?? the version number --- netlify.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/netlify.toml b/netlify.toml index 9de8c76..84cbe8a 100644 --- a/netlify.toml +++ b/netlify.toml @@ -3,4 +3,4 @@ command = "git submodule init && git submodule update && hugo" [context.environment] - HUGO_VERSION = "0.85" + HUGO_VERSION = "0.85.0" From 0b129fb2d3efce28c28b9413f80639025c456757 Mon Sep 17 00:00:00 2001 From: Becca Stevens Date: Fri, 3 Sep 2021 14:43:24 -0500 Subject: [PATCH 30/43] change whole site to plain html, css and jquery --- .gitmodules | 3 - archetypes/default.md | 5 - static/images/bg.jpg => assets/bg.jpeg | Bin assets/main.js | 16 ++ assets/stltech_logo.png | Bin 0 -> 20864 bytes assets/style.css | 171 +++++++++++ config.yaml | 23 -- content/code-of-conduct.md | 116 -------- content/member-handbook.md | 161 ----------- content/slack.md | 13 - index.html | 382 +++++++++++++++++++++++++ netlify.toml | 6 - themes/dimension | 1 - 13 files changed, 569 insertions(+), 328 deletions(-) delete mode 100644 .gitmodules delete mode 100644 archetypes/default.md rename static/images/bg.jpg => assets/bg.jpeg (100%) create mode 100644 assets/main.js create mode 100644 assets/stltech_logo.png create mode 100644 assets/style.css delete mode 100644 config.yaml delete mode 100644 content/code-of-conduct.md delete mode 100644 content/member-handbook.md delete mode 100644 content/slack.md create mode 100644 index.html delete mode 160000 themes/dimension diff --git a/.gitmodules b/.gitmodules deleted file mode 100644 index 3add4d7..0000000 --- a/.gitmodules +++ /dev/null @@ -1,3 +0,0 @@ -[submodule "themes/dimension"] - path = themes/dimension - url = https://github.com/sethmacleod/dimension diff --git a/archetypes/default.md b/archetypes/default.md deleted file mode 100644 index 409baa1..0000000 --- a/archetypes/default.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "{{ .BaseFileName | humanize | title }}" -date: "{{ .Date }}" -weight: 0 ---- diff --git a/static/images/bg.jpg b/assets/bg.jpeg similarity index 100% rename from static/images/bg.jpg rename to assets/bg.jpeg diff --git a/assets/main.js b/assets/main.js new file mode 100644 index 0000000..a4b2515 --- /dev/null +++ b/assets/main.js @@ -0,0 +1,16 @@ +jQuery(document).ready(function ($) { + + $('nav li a').click(function(e){ + e.preventDefault(); + let articleID = $(this).attr('href'); + let article = $(articleID); + let articleTop = article.offset().top; + + $("html, body").animate({ scrollTop: articleTop }), 3000; + }); + + $('.backToTop').click(function(e){ + e.preventDefault(); + $("html, body").animate({ scrollTop: 0 }, 1500); + }); +}); diff --git a/assets/stltech_logo.png b/assets/stltech_logo.png new file mode 100644 index 0000000000000000000000000000000000000000..24286c5fa645864318e6b26dd7bb0fd3184af4ff GIT binary patch literal 20864 zcmb@u1z40(`zK6?fS^dHq98~NUD7BZ2ue#gNXJmpt&$2#gGh;VDqRX94br93E#0v9 z_{P59?tk~&Yrk)<3!RzgJm)!a=kNZVdGSbDj_4BgB{VcNA_aL_RWvkocGMpp4t(S3 z6Xgp3;XBGdaX~{PAVvM5qa~$KqM_joJXP05YClvGF?F!xG&XZEG3WHKbA;AtXm=$% z9F0wF%#n;H=9W+G#cpiYHr`--Y9@9=i~k|wp`(ns)l>Or&gN>*l+{h2*_aBO-H;Gx zyz3zX9oU&8jTt@cZ0%h{Jj8DN?N5ZXu;v)X^%Aa;IMaL`d1IK<}Rkr zPaTm@9qbuVJsO)hxFW@Fz)1fw1v|%ocWdwR&t-xI#=b>Yk3~T&m_S4zA9o=J(uSm`teIIEu(Pn;Rn?oYfs1Z2z@UkN!1e zMj08@#t1RqerRm^)E+et*8jN6T-F$AE_Qq4DaehPG1B<|wXvD0h=qf*oiWV%shzQDRaW4HhP_yq-w`49*p3s^6H ze%McLVGdyvegucPg%FRakcF{1kAU&N=KnvBA4C@+!p-|H(fz+3|34SV)XLc2(i{vf z*Ny-C8U3G0=s$+~U(V=1mGS@Q8F8VE?LP#L>wlERzt{f5FvFJq{R*r->g~VX41D;v zqcXRL#c~EWg!O2z4Gryqx`M2fx<|@-s;AyHt*S%CCi|tFu?#5zbg6sq??;MI%9#8R zqTbo=Jh>HXX2H{&$R3+urq_pdob!RgN>d8^;g5*eua7gilfHb$ifsFAbX5;c%55y! z-s;_QPR5ht1G(=rot^n!Hp}nx^Q&ii7rnQS=6+TmXr_AAtPIyLDwSxnQ(^>2K1XNC z5cQX2BvFz=CxDMQ*Gfq6f~_R~zkYDMQiF-N74z!VmDT0tqm;(Ri%iu#_3LjQOzG?E z&)dU`CsBzlzLTYn)Z`RPrmaHIlM5lw3MJHC$Hib5ZM2fr zrJBch2HiA${P^*h?am!8L4JO_i8{|6PbrbW646IZ)Qcoozph@p7AI`}J370iStkoCE4-8Qlg(sn8=L5=PoG$R35l~K(@9zaFouP0Nl09LEh#CfEVt}UqaY)@ zb)`l^=|g@#?@W#BYHm(Wj{fRMvBYhpA4wH1c7aoy*Jiz3SBmgX<-Krn){u>Ge!Xhv z?97S^WbbNmV-&#@Mew>Lx=qT@+W{*h@0$14%t?%u7#z{IR) zVq)_2BD)u0I$cD^%S&gJL;C#czZZ)Ip4 zUVeMKyR<3_3asOIA8~PUrw}9^iOl%O;^AJ> zzWfE3!TZr?;5OwbYwZ`nYj4)5P;esb}T19$PoeMJ{D3Rn86j}m&eBOr($qoxq z8W)G}N=gviH*WlvAm`K*ni?62AEFvn%T?BxZ16c514(>Yy28+MUz?r$=8d-pGky}e zH8szgS^`0m`%T-U^gF+OOSpr)7<+L4e%mDKi`CUt8gt$S5X=BnbGfB+rc&iT(zo*0 z@uc^E1`!*0uH@xflpnbp`klFYnwy)enwb0^G5x`x9Fv?}Ykj=CoS3g!_|kM|6EzuK zL5FFjCMP`!O&^&Ey4yxCNZvf)Kk1iaIAazUpH5$H6n5XxlkxPdww|hSWr)yd92gjQ zfAeaG*$dgLQO1-O0?9Pp7CZHYx}Sz4HIgSjIrs^4a&nq44`g3ax_GFdpm1=sv*`E9 zb7$dw=?aC3tt7glne9Z?`tqAQTJ$O6J|daD7qEKEpIujnqbhAiEdKPL@2^i>tSv4c zOuT#d&J!IS-S<+6^a?2H@AY+}v!s!!DZAzMb-E2$hqa}pzKW_UgVnXQ(`U17kzt2R zBSrePuR%l31al^YbaZq=RZ@gr*>2jnKfl1gqgnleyh_^LC*u6H6SCC^hiyoQsF z+ToU#7Bhmd(sk7J&d$zArSWRtvu70X0x_e?Ses~9OHOwORi?;su91-qRYdBu`_E@&dMH&t{b zd}C8NMQCewP(?y4J<=|aQ7>0H_4ugFyfe+H)`m9Jp!n17?k*vii6m~q*1KY2w+svn zIO*x>>o|V6qqK~SEVc0C$7eY0Tj&B8`^gRsdHN0Bp4X;k-o(Z2f~^=y_Tsu?ihW7j z4R6rM_0P}dSgwY{-_`QWR%!Kn7mEd^ufHQ!}u?zu$`z=H}*R zFBut`A)%-PwKJMPMl(_t<%m}gvSV+7+-Iv+qZYc{q9``B^uj)a7vLBxh(e7pU=gr z^q5WLg5`D>5ERt1=1X#@)LD0T&f2`D)E%GVe7R!3@`p^3%dFvy#C#0$HM9CJgIsGYJa1!+i0HCqU{9juMTP7DtV zbbZa>Hhg;0#B@{R<3HVBT6Hqq-rgQg5%a1_>Zbh0&1)Yt$tl&TW$5FoyR;gB zh0WeP-xPq!!cHjU@#m+4fLr*>mn(^*mD;}3t>(RXTGM_PXS6w9dFh(>eU2JG$T zz*vPg`&-3$&PrXEwR^WadVBqj2C@~`mD=Rft{T~%fK|v{vaPDDBm%dLgXcrnmX9|b zu*G)k)-5q|YSc<}wpl!W{FpBFVfa@QVc*k3*Nk?DLIhFQoU4WH!Iu}L5(8sqUWPG$ zKy!`meuq#*k%KQrPJwcw4!L|av)rG-_wbigMtg63OhEkGvN9e_np!3CKw4qvInj)E z3Hp0~E=LGn$Ha+y{rYtp%vvHxAaSFVjh)?FZfR?WgTZIFKUb;EcW0s7AV)w=P3uODC2fvWd zG4hsLa&>hzmla>ql?1VR1Bs;g_yZOgLz*m%fyH?HW(By;RHb#F^P|O)rL|Xh;%+qf z91Pxnn#FVWzj>i!XJ?fbqE_cdy3hWYIRTL^k0DGhEWK~692Oaj0AohG{hjOW4-}=O zq;9As&xr*{PwO_rEKyIuy)H;AZCw6MnZ7sU78BDfEQ-C&^>!tKh?0k6U$>z`zW5u_AJT}j=|>9 zT7;)7b1^HE*Ia#|^t4NJ`^E>@1X_(MyNP{UEiH=O@vancSQnJlc|M*lxL!-~N zL#+>&J|-HU-Sm*1UKp z4dcdp4Q@7qldJbl2ZZEcMsbv%@>#We+5LZD;|axC^lN5>j%8D$%rKnBPhmstX3m!7j)uySy$mrHtV z)*tXBjNe!##u#h#y9kqx9(f#6S0y?6BlPB`Fv)-=7DKrW3SHo>%>+p@`OXj5&seR^Q<~wosj?qX2USPgD{q&B7{q5iA8P@qr(C*aK z)Z1G3O?wM#;{8rYEi6Gl<-pr7aiIynghq`Kt!B;N4p=Ic6ypZT4@SonCH7+w)D8 zVO3RCzhEN-6UT$jOx)evqK1ct>`W%)f?a>Wo0YXStPN%uv4+0>nFWLf2>C|uqwUeU zx;o3TeJ4F8WXR`8a9UJ)h8rS{v3~k`0&T@u)Xnw9F_#?O#oeaz*McF8nnr& zsv`f)?FtzPZz401tkDvFcwUN-({C1n;ArvVCAFL?9$sFC{?)xqMqM-Az-Z6A1Z%#l zd&iG+uw~iF3GN@`kRTfq37)l>NP=6KReZ~yh&iC8shMQ(Y&m;|yOM&6>d5d?hzZ6U zdm|&X{JgwoP>W^;et!PLrY5v(<%~y4&m$sExpJ!h-k_nWi9zbf@ubX58Py$ajqrvf zdN_K2fB(~WXhFu5nyRYX{A#+8-ZVpKriV3e-2 z>H|oXVXqgM;PKK(B$9eUJWB3S)BEe9qF%<*(in&nGZ~rINBa6xIyw6-t*xKJLPJ$^ z*s18~zJAQl*8t=5Gks;nn(X$Ol9km5MGucdw;UA0F$@VSVZbgvK0ZNNc{xSd=Dd*1 zlDn!GMNK`QZMolTek@jFmvfRAc35tlF?M3|HSD>z`+p*}KsZR$*)%49e+>^PcA%r9 zVWRZ$U<`;y0B z!zs7`)^V~u5h?<)94|+iQUZeDUh$JP9vZKb2sCi7GE`J+>fgL%@F$e0vwA^Bl>cx~ z0zk7%McbM6wKGlXY@DL+`DxL<0LpHrL@ZKfaj3O~>n-S8myk&@0TKOCP8GG_8_@ zsiJ|43UEc2yMMnVDT%txa0k{Z{?^T#U;K9k?I#c4+5swn?G}CY>Qxie74Aw6HMLA? zDs)bBDIbTrAPjPBQMWY@)BgAO9>ko3uc)LEv^P7wL~-Rx>DQs5H>$aV%lBz$XsB3D zWbkB6O=mSzmF242n}>$T!k<4ks=Hg_G~3qOlP+OMFuyG`5CGeKn(X|&R@yVC#J>5#x_+&M_s<8-FV~f-P29yYFZD%+=7CLp=W~; zRJ>_8%c$6{2$GMB*hsNp#{$E~^K^;RKQa{Z#I+;pP2LKe@hSiS$=!4DgWRpr-`mHF zGE0z>@a@~T^(qVzH{eJBWS-@C?j5ON=nK+Ha0d5_)>ocsxO3VY2E1( zGhyB2VQ|-*W+OCvrv!jGT5Sz@+c9q&odx#w_0@g*CjWDF0sti&0f%Y5t{(hJdQ}x1;6;XNo<9TUmj}AKx=G5pm^f6UVi)|$f)1Pw z-bc~+bZ+ZCqYM!f})}gL)#OpVt^KRzmTfXp6^{mzkK-`3maQ_ z@-5M5{m%Y=8p*Y56|eFN0cQF50Q!(TK0Nfe0K`C|bUiaO5QAJnRu&66qxkgcvgg}< zUxEQt^joZ7JN(K3xBdnb6DzT+mxo7JiK}H>67-RSx*W7y;-!L}>d=3*;DLe7PS}bU zhzE;JkI1xga460O6u`;91Ds>3po76}c|%Q2w>NeS>$EJ7rf-LT#ppu6WnpySI9=zN zVaq1^siGolZ-2jqd#2_cEL1l-=xc2?4OGpWZ2AGlRkZ^(UCHB^7?SwDzDIGRS7gu$ zS`mcF0(RqS2p>B;j{JJnSFc{F_#?H74Tj!d`}UiKn|o_DU#r+!>RAHuBdJAGq_~Iy z#SU4`q&#(Pf7LF&1?Z(CMY$?MCE+yv`qS~Fn z4bNieIT|jyJ`-yr36j7nEsl;7T)L!#JI*S>!xNY{w4!gjc72VaQm39E&Q%Jf0dTdw zjXt$F+#tF}7*zmIM*R(j+vr<-#{jEx|N8YS9ivzm z#Rn^UduF3#)&AcnLd4pDW?B6Sl_vIE4u=kU(F)M$9KZNeA!|TbHyrR)gJ=X%BwlW#l;u?k@bMheFEtB zwyQ-sm0JE#1OYkYmjInYPQK*sI1xcXLH66Xm+S=gm%O8TEa~VoK8+LHf?&sm2*>Cv zha%vDg1X7^och+7V@$4r(O&E~`T2)(b92MCDF+~~Rk<|PSW4coDZ1RbG)2Gb3^~=g$UMI?#{qjfDi)(8U z*f=<4mk`vE%%Ae}2|Of87g{ez!c?l>LjHKxgYj!^ti00JuI1{5{%6Mw1(-zTJFS-V zkh+mLM};qP$2Uj@;;|V%ahOkv8Drz(%BYPB2neJB1poq&>uc;L5P3Wi*#9g|60C>{ zcK*V_Vq$a&;}&%>kby&(zaL*-R^~5!e1zjxJUcskHs;HbwR2Cz&`s9AwvO%%z$;v6 z%YZq2(9G{PG3^EX>sE|1q!xVCM6&}bdXMwe%Ne}ZN{bmh=UypL?z@~9(TTd%oquXP zv+LFVWEZ_QT`%f-cD(mli5Zl<6=HZb)JG56c30D}qWhU0BddFU=-K4kJ3C(Zt%$bj zz6u??xA!wW?=Uj@Z#QEsbY2ceEl3;+u(b$qT=q#rQAp0Bm96dR%fjv@$fIJ48XC^|biHi9b#y3^`iCQz`%{RGM`bgbP-p!)v9Ih*FCv(kxpbKU=HZ9mVa39$$NQu zG1GWK3eXrH74=qidG}fUy+Y0MB6kxL z6FsS8-B0#IzlEkd+H#;u*BFEZBbS6K36z$$#{sTTy*gZ2i}S3kr6iqLw_HEk1q;$rrW@mI_^5x@3}O=BC6Ocvj))Yi)F}ic1hav> zCyCz%M~dW+Awo`SNyAU~+s0I_200#p;x(V(T9=_ht9s{ug#tDXNdO<-! z`=NcZ)Xdt#onKtpB_)68YF59_chZqQb#P$7sjRjc;Y=wM8;}c#5$F8oT9q9U&QkFF zIo?u@6a<$}RRWk87-?9`Y;0`QW8*dcAI5wcXxM_*A+4{{?x+ysHn>tii({Gc?rv&l%?HWq|q~bx#nM( zZ&mY@aMrK2AqZ>1%IMR!2bj0#q0(|xG9o5<3_3eK91WGk91s8t(lrMFq0{^pQ{6dt zhH^5u_9q-D>JFy8s7e|=m$T!iXUm&{?q?oR$Wu^Iuvn^Lz#bE}Z=Hiho55a&l}m|x zV9rC6Z1Uw7rlz(wWyL#l5T-?2I|!*xapkqt)Obst4(9OM+Nq*e_WPSVe*QjJCd(~V zhC_*H#OE``n=q4i@ z9xSd#`M2U0jE;_WFzUnh#el_%FYJauR)bOB-2B!btr(72=7;0rHpA@L@_wg>TfavP zyf|JI@6)DI7ihk$hZt?%cYoCSJ$3VQm6h(fW*`#bi~DTzGsj;maA z2BszmoQO76aamc}16asa3`Vdn{x&910J~?q{`eJ0#=#pc1N5BXde5C4fNYRg80;ch zd{4L9!;E6ji~Y`Q=nZY8KqH%o8B0q`n}}~SI?^(5-nkR>7X8lc+uH5JMG1~e{$$`; z`IKgU{Me<^O@{pA4kT~Pfx9B9_7b|u>fi_eU@7_SuZ?93MPZWGUH{PRRCfVzMQ`9P z)EGw#o|J2wr(i=ST}qRc%=h&54xk%p7B;axmdoA-YeLATmk|*u*aJ^1#~&AJcGe(* zRr9dYuLag{)&j$MFeKKA*eX7A}Mj-&o>02coI=0v**aE=4|GE`eu%{#L~s@jY(--3PhYubJI@L>dL-q~v?tD=WL1W(T} zYqAr6``SxOfDrKR&booy`l>fPMRGw(+fIZktr5syjG9J=m|I$w8&F>G!`84!)}U_Z z9cp>Eqc1W;!F!pe1j6ih8V@RT*3qj3AY>X=$c`H`D**UI#Xs*3FC=~;VqWyRG0>IQ3zfK0WHkazOE5gjAOo4*m&FG{ zQPI8^X9rFE9RL>KS^(d|!klISe2#0-E+QS{6@VnJPo7XAMiQAE97xjRx&7@$Wgrxx z<8*6nY4ImW+S}XHbP$OM5AVcT1`yc*y4AC@qcIIBFXuI<-@%6ntntG*=8G3E41K@^ zHPxAOb9496Z7Y4q%R~2N3^=+*m_RJLy^j+{sEtf_n;0Kgb}EHboj}j!QT`Ba^=O^S zvuDo^Uy|L)3D^bug-%{ug88gMhhu)48JH6X!qwm!(7l~~pfXPm37To7Po)l#cSsO) zEW+USW1Z+SRf$o$TWw9veJKBV+1ddWp$J6jz4uE5B)^a^>ynk6o}G;ZAW>k23e3H* zwC!9waQ5&|BCqB42P8zN1u9oZlTfCVOYd`^Y_^NDbBni+k6~5YIS@p|xhVJr_T*smg2ZemjKO!Q zET=awFOL(X{EYErE&;2t3RwmfcD+g+F_Thlc1Sx?O_o1>HED*R$`D8Y0;*0MP<3Ll zS&J2y#$VPguzTG=D62G*o+mU(N*=UM*hCbBV1AgiOA}KB#iN(u-6x-GYbAv3#`y%< z^q)S>Gd42vA0#K#-C4;mW^TARKapa4vl75-*`st-4d=!5^mOaHf;8|jTh6YomDWtG zU2;YZ*g-wxr}!? zYL=R?l~4L0h(jofM*RG6)|9J$cfdvc7<^Ns31yow8VsH)0oC!Y`A=>pxyk9Djw;$E zDmAdd%QK&yX7Q^8AR2q0`To7Xut802ZFE_sCqp1(3cy6He)SNAap(JOj!{cL&#y-dk!7<+K zA#=WYRiO)#mdQLMaD~{fr)!f47&$urar5*Poy;ip1=UDQ7spRkRXVQf%zS*i z_dZ@oh={yg-g|bf#8wHi4dWP20L4C*{XrN898nUcDj)bl-ZcLfpU|ZaB%QQ`(#+Co z2FO2mC?;S}cd?d5L`8*J)|l{G_<49rp%VGk6&pSfiVP_{W59sxmk zc}~>zzhg5+aj+oDZ0fF#dRyNNNzoL`q}RcQlZZ%cdU_*{=2fU;V1^U*{Q}R$Kt^`2 z+Se6=6`iWD+$6)ickfQ>XlmwU58RWJ^D?Du^BfWF($dq@D>*&&{#kvW64|gW4-3d_ z^e~AJ|M<@PA?twXV+815I>s`j3T)1uY=7S{*U*Fi zM$5t8-kF5n+BgmLjDdmiZoUX9Lbqy?2O|TXQ=IPQjdI_!V?XE8aAV5*B*9(1yW`fD^UzuTb_NyqG;n)0E|(PDdZ`SI1B z>lnjx9kIFoNYwJy@AQbKq?H5)2GXN18&NS({pO7Am{WfV#+8~ol>x~IG0CtMU%k3W zp8Cp5V@k)P0DQzuz!7akce0@2hoT}J@}cMO`e`yUP2$r8C^d*{ib6F%S}UR;BO@aq ze;t%TE&vJccu#NLgfg@mU=xLG)$cnmAb{S8ofZ~3J3GVqc)=Chp$E(%RzIr*j2*g! z-v0i+KFP#Ez@gX$1T^0!CgPudVJn38Mj2IDNVW;sqPlkleChw@rl{!9{Ik4!J z*0~L0jK}_DBqV4LGcpF3h1M;4QmWxHjj9o&NobL`_BJ$k5hx%m(p-@?SijC;ZZ@|Ow%$Na?9 z3!3Ie+-Lf8%FuOSWD8l;BQGye1d}Ylk&cC0?9WAvpcaqYo5+iMXrrZ}fn5-z7}nS* z;Yex-E6<=+d*I~kydC!-I}Y8(!y{pPgw9y)HcLZnEa}49nyu?^#RTGJ@93!UaUG-k z&vEHJn#AB0mv84K`2)RkaB$}U;RD8SH2bE)rk?we)TJ>%Js;{q4aqGFb3Y#C)Z#-|Kxq zu!EG9mE*iBMkNfuWI+WC(D7S)Ygl)9QX~hb&deoU?GQbrYU1BVJ2KdwbY+r7ci*`S|#-x+0pc zK}@}}x*CvYVI(duXKKpyhp|HTMl)Ec>7UlRR*esJ2RJro5F6f(p0TPN_Y#WQaqb~qP((0f$rNg)hoBO? zv^iA2qO4Fx%SiVv?7*TXBg6I{QqLbsQ5!m?t~XG5qUZ8Gj&%c!y{yU;fX>!vv2|L1 ztnQI{S7PqmN+2Ep%T!OClYZB8+qS4G(S?9-aXm0|Vuw7v4Zq zB`9QN4fzSE$Oe>5a=YkI4m>R*_xyds7FK=UNg0(;#xS~ie z4<3ByxMPc%{~oxZ)3es`muTC&hlYmY$aHd)5`S-i3Xv#`d;CN90bl=EH|X zfByK%$_C43tG?j0dckSLdhO**^DboADS{D@Oi0hH0;|2(rIP4PYg;{%P>A_Nh6iW-Q#ctI2&#$i5V&!ZCDYos>M4y>I zPEdfFoeU+gm5E@b<5sny=9;EL5==2;cjJQ-RPmD}{KV&Nv|;W1$82$YJ!dbas`MY- zB&?~H6pUZH(vMvLQE?)|M@6Mqs;J7x+uPqO9V*JWhX##JCFysF;^X7he1~>-c3jF9 zD9D>HXR98)4JX)pDGAB#5#`i{vGx{Tg37>uA0f6bdjU|wOBPZLB_+`iiYTs90$Hfl z)2AKS%YZ2gL}}DMzkuRiyd1sf99c|5Muzc;b|ujc2XqrK>!AV*Sn&F?PAj$I68R(z zHMNi>v{fmr<5wfPnT5-Jcs5|54t+yu20~JV)>;)?3JI}{nA&5veBy&K--@^pbG_w zGey+*Th+A;36MfX^&EXb>}+?iQ7(MbR1O7#0#LN*zYFlI4f{my4u{AL>?+Hbs(%e@ zWL4sq^~BT^U6S87D?W0k%I;tk%$h3Z^>&*uD>rvB7!C;3mD>8<cB&B%CXFHu|1nR$*Xpa8`0;5)wXVXJ^fc_Y7IlkEM^9EhpwC-vy_r1NYWHHoKDeS4rd{ z_MUvoN8MO;PXh9eorla#3!$Ur)At}%VE=q!7U`3%ihuXh5Cpllk#+(oKD9#-62;u! z2DeJ7yZ5!f16!FWAG3T&^4lacRP2>sD&EB#2NEaC;g3b5%+Q{%AFkyY$_mM!n z`F6dEl{Y8~+sDVJ9dh%2%mJ30H}$GC3~8x=_4JlQ7e_CKla+N@fRZqM{G$YdA?S!% zW}>h9dQOOYKNkDw@1K2rBvr<(I6cLRP}bsxoU|#}A9|}ZPt3w>-|7dpMgjUVs=@*3 zV)d}*nUgwzTl;r`{?K&n2bC`!hy2_-gh3|>sI1E-tw7Lr)Dda*yzD(~sPS(d4~mCP zf$QH33koVeBI}fxGeu=QI;c-<|E7)LanR@vQ7D@+$V?o^$(%f@r1u%P=Mq7?sH&Q7 zqpuiW`n8$9Bg)k10rX@hlkqLimmt|cr$1Jzd0rv*+Qn0fAIzEk`~B9w!(@1CrcH)-XEhT`nhdmZ=}zceN48Zi?8j#VRkBPql^Loks0 z)%*AFb^6)_gPM&>hkb#tAo1-S#o@aoykAjK@hDYU@X|_phglh@Q17*}XpiqT*=Q}6YuUFQVy0eeP$2M34h z%KbuPNKd;_G~0Z}`uzMm`;#ucXZ}6Zfl$73f`SJ%U-@DHCa&^LW@caGeDTNVJNyaJ zJlFzSMlM}xB=?$GJBjPy%}VR`F&Naj-T792_=lo%7C1i@(8VxeSjkhC|o}oLfa!HC9u~P!8Bb$FVZ= zLM$nNu3@1d#^?Txr}JE{B@d>dZYgu`-o3$g9v?!rCGW@{t!4jivKO*}FO0>0Y+$|( z3u{+RXaLg`$iENz7tp8!JfTcI#pxZQsM&?$hGVv>!a_T&T|tPX(SdCB^d_G4wZ^xm z_);Y3euu3LNsuk18vD7=eS39FC~DPqh>H@S$93qWsrw_s&>Uk*FC*Dz-+v01oq-`e z%;;IYf!`$c3B<5XbYB4GjC&#(f;zF)jiOsR82OcZZ2fLxN%MH`bk~wq1NH;#h_|V_ z`nBDs6?QAThpF?! z{f#MIMx>#X^fB!%Z(BRYMZ#NidZee+O+bZiLRHYokWL)rz8Eio^RnSI{>i~Gqi+O_ z8AZ@;D(dx#f^rIYy&*U<6!oSK4tzX@joVWy`U-VfH-ag{gcxx-{N;Sju`p~|Af{hm zO!+y2e$%Z!6!OD!qMXf*jj9#-s0Z0etnr-z>9s^Stsphg{6J&68<(7X@}mi@wF1AR`S_WVdo!Ogc7&_- z#HF%TpS*bzVBgc%Eu2xh>Oa4{jQ_ATG0-I_~?@Kp3b1#++uu(L%CkQBmAb^|=HHk~T2e)g0>g zhTSH1qePM7a*O52zHX`-VHP22iQmn0hg-8>-^pp!8#wIEZb1PmnpkrGNNC$sQ32wO z!{yv`hnG%m(P`Hv0S)n-w&SRi3rNmA@Xsi%H;{9>)VmosP$^4dfYCtY}wtFZT>;}t8V z#+;g(aTI?Z!^`j!WBbB6R1oNYSXVMBwY$%Me-riN#}BlOlO9d^8L&=IP}T_-+07>% z&Ad>tDbpi2$e8J*4A1m;}8bT@pcsWC}u!jZrZb#;rO+IyY&}}**ky!BuE}_=oi6$ zlv8A}EYe@nw*9lW=Yy7IV{1!Wwy&km9Lo{9d~$MPr^#wr0AXNJ6M~%w&XKBwlXHv< z00qcU;KFwxOQ8o`*>$^5>&gsHZ}Q=o0LLs7j;>O z{cSVwrO=@ws--o;2!9GZiCu=wu}1|4^&*UHY~L~8ZiKL+xc^Xi8i$i^Rn2e7?AxeC zW|(~9U7A{)^ae*qg|5-li@$n6oa`lS`UzDN#7nqZm6xYLLr-u2#;00O`RJPuLuUVy z<30Ls4-gFNaFQZ2jQ-hee$=VNa5|{Ub`1`?1OjEq28ghHp~n5E``46RTz39|sGp2M zAaKsSKO(`ltF;ePUBJJzfuV0E$F4P>+wwZxGMC3>M`?&*WKkJ)Y z|BP)sTX(3%4;wKpGhT_+a7t7@CfAgrB2J@hYPlf2le}icS~Qka-ETNP z9R{UvL9o9$KpE>^;ZoIuY?ZF4puqNHK><6QaAE-ZM!Ct?OV?{|P-YRU;;<)d@`R+w zG+p{VM|;=GPSo2Jo&-qibtMNr>WmOX;!ik?d1^lmF5RTihg({_-rL`J6ch42mTpXFppktJbRc3tPm9%RiZ- zffdY1mYJiKMGwbEx$oj@)R7iQ6wp6h^=ola?kEHcAg{(oKRuiRLus7iVg%vIOUMx4 zzrVqdr%uft+wmK4J-?V|frKe(Hze2E~mdBO_XQ zBdd+viAwGW!c}Azm(MW9jugz<9Q8bSE+2{x)X==}E@l+KkiETB$Ym-jcCoRrw9O^p zF&@xPvcAKt#!>_GGEVh$_Vsz@P~%#>z&|naH)Ele(2}LPtPXCi708H5K#~UD4-x23 z63~ac$ivOQfuo4HZ<-2&vE@m$kB*3__$|aKf6uNIZAU6m$!#XA@c0+=;%k;Smj!S` zzHp-W4OqVRBUXIYHtUKvuUd^c#CE7#+R;Q^J|feIKC5F`q6w&-b?iH0TyE9GW_RX% zjKe-kd+lm%R~Q*NIZnaxz|@q!O`%Vox(Hbg1105$k}4vs7V0JMn4Yjiv}DB+;oCRe zC`#1XhLj*Vn8cnM98|NmqXA#n=OYKliK{B@7)gdD7lV-EU09=fs<*FcS_;w;tZ^Du z*Vf8}-=mIfy94{Quz)k!kq;c!_D%za;4>&t`U6?kH`xCOp|-SebxQ9VMlFFh@Ym^4 zf)rk0C&L+!8-RrP-oj>`iNqUi=UxIaZ-_l-fA_uXCAI$ZkS!8rF%gUD(mevi_)M|} zcx0KC`&aP9{f};Rg(ZUGR+pAK;bnz&-^)PV0AQ8(4?7UFUztQ9(!a0=pfY7JF3DJc zy%3IIu)wrcZeDo*XjH!`2`B@CsOn(hGy>571qdlF4*)(AnQSVIcY^ajw!Z6Gb}b8j zi6HNHCJ`KcF`@xXcE!g44~wD6`^rMAt$#P`sNS_pwU_=DV}wP6VzHO@j%mCrFh!#L z;iNQABK46KWXqxU%o)Mk*ICw!kMN7gfA9HY1>sJ?2ilHeiM#G@8_jJL_jG`l-bp=g9HKEAcP zo29fCZA>{lGSc2DLWR*xfk+QN;-OhuAfKA7xaCG#V#YHT^mhQagoUeMk89V4R!^z`*v?<_;nDl#g{q@$zbgU;oa zB6)}rDCw|A;zN%3XpCG41qAIPr?7ygYGf4o1;FJU?+Q?H^2-BH;lQUjXw@OkLNX#9 zcJm*T4EKMNn0Q1YKLW|n%h}IS(QaluRJN&v-ezn1iq z`dI7`LEuV?MBZ=JWpn}ujsb|b7@K%NiK0;hs@nQhOH`+jT>EE8@mC+4(s2KIFfm=L znS;w7qMWk}3-_PArD;WUS@BUHTH^-%B#rIBB7`vC{!+tu|1#2tF*QFwf9OrlQ4=S| zTP0@9g-KwiEzgzG3CoYn%*=FZiQ-|U?;adr`c)WE0JHbzGVJ-uz=r2eRKyo#<;|JzIhZ)a1mGbQ3Vq)!GY0h}e#Sa{)A^!Sx1#MvO z;9#fh>9tmb5@)=kWKBQ-y81MMaXjn}hJ*;~wM)}%6HQU*@a89NB_I#RHi~t$ z&w#_GcKcdWZ#iuE(ofzNPVVGx>KHg!^v5j?en4Y55DC9l;`ZuWuK@=6pC3nX>c~NO z81yG#7OGQq*Ph;EJhXtLNeNXn3xl@H@M{M61D^kF)z!C;J`3E<5drkef$**W{?)~0 z2?96iyLze|NZWAmpd;|mmab`ZNLRaD}ogSoDzZC;j0OPClna~*K*xX^XqhBT5HgB3b^ces&4c)hw0kD zmD>3)e zb+$}@WeKzo*ory8dj)7ylX$48O#(1hA58Yo&)3iQw-xF1*ReEn&e*Lwyqt(tBxg+7$F@iRr%9EM7^J2!DhpT0QMe&_ESq2gTjG-;Dm#<%E z{{kE@dUZA&xCUaQ&=O#hXiAp@x~>v9zT-c8w$HNLHCutJ1-RBcY%?-dcq0q++m}FK z`TU^YFdDeHsUru0z5P5aXV;_IOxzm1%0vt!y{{$}doIOn^(rIQatHcI_GiJA?1b|u& zueoy#bcE5jwg=XC1vyxnG&K@{>Mu4hi7_<_@QxhLfBrLJeBXsU6E#3*Bzn5~xvX - Join us on Slack; We want to get to know you!
- Slack Status diff --git a/content/code-of-conduct.md b/content/code-of-conduct.md deleted file mode 100644 index 6f50be4..0000000 --- a/content/code-of-conduct.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: "Code of Conduct" -date: "2017-12-20T22:41:28-05:00" -weight: 0 ---- - -STL Tech is dedicated to providing a harassment-free experience for everyone. We -do not tolerate harassment of participants in any form. - -This code of conduct applies to all STL Tech spaces, including the STL Tech -Slack and Github Repositories, both online and off. Anyone who violates this -code of conduct may be sanctioned or expelled from these spaces at the -discretion of the the incident response team. - -**Please note that STL Tech spaces are not public spaces** and that interpretation of this Code of Conduct in matters of sanctioning or expelling participants in violation of same is at the sole discretion of the incident response team. - -Some STL Tech spaces may have additional rules in place, which will be made -clearly available to participants. Participants are responsible for knowing and -abiding by these rules. - -Harassment includes: - -- Offensive comments related to gender, gender identity and expression, sexual - orientation, disability, mental illness, neuro(a)typicality, physical - appearance, body size, age, race, or religion. Note that "offensive" includes - questioning the person's right to equal treatment. -- Unwelcome comments regarding a person’s lifestyle choices and practices, - including those related to food, health, parenting, drugs, and employment. -- [Concern trolling](http://geekfeminism.wikia.com/wiki/Concern_troll). -- Deliberate misgendering or use of ‘dead’ or rejected names. -- Gratuitous or off-topic sexual images or behavior in spaces where they’re not - appropriate. -- Gratuitous or off-topic discussions of violence or violent behavior in this - space. -- Physical contact and simulated physical contact (eg, textual descriptions like - `*hug*` or `*backrub*`) without consent or after a request to stop. -- Threats of violence towards any individual, group, or society at large. -- Incitement of violence towards any individual, including encouraging a person - to commit suicide or to engage in self-harm. -- Deliberate intimidation. -- Stalking or following. -- Harassing photography or recording, including logging online activity for - harassment purposes. -- Sustained disruption of discussion. -- Unwelcome sexual attention. -- Pattern of inappropriate social contact, such as requesting/assuming - inappropriate levels of intimacy with others -- Continued one-on-one communication after requests to cease. -- Deliberate “outing” of any aspect of a person’s identity without their consent - except as necessary to protect vulnerable people from intentional abuse. -- Publication of non-harassing private communication. -- Complaining of ‘reverse‘ -isms (‘reverse racism,’ ‘reverse sexism,’, ‘cisphobia’, etc), or otherwise attempting to legitimize the same as discrimination or oppression, will not be tolerated under any circumstances - -STL Tech prioritizes marginalized people’s safety over privileged people’s -comfort. the incident response team will not act on complaints regarding: - -- ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ -- Reasonable communication of boundaries, such as “leave me alone,” “go away,” - or “I’m not discussing this with you.” -- Communicating in a ‘tone’ you don’t find congenial -- Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or - assumptions - -## Reporting - -If you are being harassed by a member of STL Tech, notice that someone else is -being harassed, or have any other concerns, please contact the the incident -response team (contact information below). If the person who is harassing you is -on the team, they will recuse themselves from handling your incident. We will -respond as promptly as we can. - -This code of conduct applies to STL Tech spaces, but if you are being harassed -by a member of STL Tech outside our spaces, we still want to know about it. We -will take all good-faith reports of harassment by STL Tech members, especially -the leadership team, seriously. This includes harassment outside our spaces and -harassment that took place at any point in time. The abuse team reserves the -right to exclude people from STL Tech based on their past behavior, including -behavior outside STL Tech spaces and behavior towards people who are not in STL -Tech. - -In order to protect volunteers from abuse and burnout, we reserve the right to -reject any report we believe to have been made in bad faith. Reports intended to -silence legitimate criticism may be deleted without response. - -We will respect confidentiality requests for the purpose of protecting victims -of abuse. At our discretion, we may publicly name a person about whom we've -received harassment complaints, or privately warn third parties about them, if -we believe that doing so will increase the safety of STL Tech members or the -general public. We will not name harassment victims without their affirmative -consent. - -## Consequences - -Participants asked to stop any harassing behavior are expected to comply -immediately. - -If a participant engages in harassing behavior, the incident response team may -take any action they deem appropriate, up to and including expulsion from all -STL Tech spaces and identification of the participant as a harasser to other STL -Tech members or the general public. - -## Contacts - -the incident response team can be reached by directly messaging anyone on the -list below: - -- Becca Stevens (@beccastevens) -- Keith Brown (@hellmark) -- Craig Buchek (@craigbuchek) -- Steven Pritchard (@silug) - -## Source - -This anti-harassment policy is based on the -[example policy from the Geek Feminism wiki](http://geekfeminism.wikia.com/wiki/Community_anti-harassment), -created by the Geek Feminism community. diff --git a/content/member-handbook.md b/content/member-handbook.md deleted file mode 100644 index 316e1a4..0000000 --- a/content/member-handbook.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -title: "Member Handbook" -date: "2017-08-16T22:45:35-05:00" -weight: 0 ---- - -The goal of the St. Louis Tech Slack is to create a space for discussions that will help members grow personally and professionally, create new connections between those members, and showcase the best things about the tech community in St. Louis. - -This is the member handbook, a living guide to the ins and outs of the Slack. -If you have additions or changes, please [submit a PR on GitHub](https://github.com/stl-tech/stltech.org). - -## Channels - -We have a lot of channels on the STL Tech Slack! -Join whatever you like (and don't forget `/list-private` and `/join-private` for channels you need to be a member of to see conversations in.) -Here are the channels that likely won't change, and which everyone should know about: - -- **#announce**: Community-wide announcements, mostly about administration of the Slack and to announce new channels. - Low volume. (and… you can't leave! Mua ha ha ha ha!) -- **#everything**: The widest-ranging channel. - For everything not specifically covered by another channel. - If this gets too noisy, you can leave it. -- **#meta**: discussion about the Slack. - This is a good place to ask questions (is there a channel for `X`? How do we do `Y` here?) -- **#events**: event postings. - This is mostly RSS feeds from meetup.com with local tech events. - It's good for discovering new groups! - (note: If you have an event to announce, go ahead and do it here. We don't do event announcements in the announce channel since nobody can opt out of it.) -- **#jobs**: the job board. - Please restrict this to primarily job postings -- **#careers**: more general disucssion about careers (resumés, job hunting, et cetera.) -- **#welcome**: this is a space for new people to introduce themselves and the community to welcome them to our space! - -If you want to make a new channel, read the rest of this guide and then do it. -If you have any questions, please ask in #meta. -Please let us know about the new channel so we can announce it for you. - -## Slash Commands - -Some useful slash commands (entered by typing `/`, then the command name in the chat box.) - -- `/admin [message]`: send a message to the admin team. - This does not mean that you will go on record as having said something, but the moderation team will see who sent it. - We treat all reports as private by default. -- `/status [:emoji:] [message]`: set your status. - This is how people get emoji next to their names. -- `/giphy [text]`: search for reaction GIFs. - We have our Giphy integration set to only allow G-rated GIFs and to allow you to preview the result before posting, so it's fairly safe to use. -- `/list-private`: list private (no-preview-before-join) channels. - These are private for various reasons, ask in \#meta if you're curious. - -Some commands live on a Heroku dyno that may take a little bit to spin up, so you may have to retry. -Unfortunately, this includes `/admin`. -If you get persistent errors, please message an admin directly so we can go boop it after we help you. - -## Do These Things - -Here are a few things we especially like to see in the community. -The moderation team keeps these as standards for behavior which we compare members against. - -You can help! -If you see a discussion getting off track or flamey, please call out the behavior (note: the /behavior/ not the /person/.) -If you're uncomfortable doing that, please contact a member of the moderation team by using the `/admin` command. - -On the other side, if you see someone being especially great about these things, tell them! -They'll surely appreciate you noticing, and it makes everyone's day better. -And, again, if you don't feel comfortable doing this personally let an moderator know and we'll be happy to deliver the good news without mentioning the source. - -### Show Kindness and Respect - -While the Slack is used by quite a few usergroups to organize in-person events, the majority of communication among members is text-based. -This has the potential to lose a lot of tone and nuance that you'd get in a face-to-face discussion! When you're chatting, please be aware of that. -Go out of your way to be kind, and to make sure that the people you're talking to are not being made to feel uncomfortable. - -This can be really difficult! -Check out the #interpersonal channel for discussions and tips on how to manage these interactions. - -### Have Constructive Discussions - -We want you to be able to learn new things and grow by being a part of the STL Tech community. -Part of this is making sure that discussions stay on-track and constructive. -Channel titles are pretty loose labels for the discussions that take place inside them, but the discussions themselves should stay on topic. - -A tip: it's fine if you want to discuss controversial topics, as long as they're relevant and don't devolve into flamewars and bickering. -Try having these kinds of discussions in a Slack thread. -Other people can opt in to the discussion instead of it taking over a channel, and they tend to lead to better conversations about difficult topics. - -### Keep it Relevant - -This is the St. Louis Tech Slack. -Things that are most relevant to the group are about either life in St. Louis or the tech industry. -Sometimes topics are both at once, which is great! -Everyone here is connected to the local tech scene in some way, be it as a programmer, consultant, recruiter, or student. -This creates a huge range of topics that are relevant to the group, and some that aren't. Examples may help: - -- **Good topics**: questions and discussions about specific programming languages and techniques, organizing local usergroups, the way people in various social groups take part in the tech scene, and "soft skills". -- **Slightly tangential, but OK**: where to get lunch and other topics that are relevant to living in St. Louis, but not necessarily about technical topics. -- **Probably not**: current events and politics (especially partisan politics), dating advice, how to properly raise cattle… topics that are neither related to tech nor about living in St. Louis. - -That said, we're more concerned about making sure people are well supported here than we are in strictly enforcing topics. -So if you want to start a discussion or create a channel, please do! -If you're in doubt or have questions, ask in #meta or DM a moderator or admin directly. - -### Be Welcoming - -New members join frequently. -Make sure they feel welcome and supported when they show up. -If they're your coworkers or friends, please introduce them (if they're comfortable) in #welcome. -If you're new, feel free to introduce yourself! - -## Please Don't Do These Things - -We've found these things particularly counterproductive to achieving the goals of the community: - -- **Sexual humor and innuendo**: regardless of your personal feelings, these kinds of humor make other people feel uncomfortable. - Please keep your conversation about the equivalent of a PG rating. -- **Trolling and Flaming**: deliberately getting a rise out of someone does not make conversation better. -- **Personal attacks**: this is covered in the Code of Conduct (linked below) but briefly: name calling, outing, and deliberately insensitive remarks are not OK in this community. - -A good guideline: would what you're about to say be appropriate for a mixed-company professional conversation? -Would you say it in a user group or conference talk? -If the answer is "no", it's probably not suitable here either. - -We're also big fans of the [the Recurse Center's social rules](https://www.recurse.com/manual#sub-sec-social-rules). -Specifically: no feigning surprise, no well-actually's, no back-seat driving, and no subtle -isms. - -In addition to the above, please read [Code of Conduct](http://stl-tech.github.io/code-of-conduct/). -The behaviors listed there are used as bright lines for moderation and removal. - -Finally, the STL Tech community is not a place for hate speech or hate groups. -If you're a member of such a group (Nazis, the KKK, et cetera), please don't join. -If we find you, we will remove you. - -### Consequences - -Ultimately, the moderation team has to decide how to handle violations on a per-incident basis. -Things like intentional outing will be dealt with swiftly and severely, whereas a conversation getting a little heated is less of an issue. -We're humans too, not robots. -That said, here are some things we might do, in rough order of severity: - -- **private messages**: most moderation takes place in private messages. - These usually just reminders about having constructive conversations. - If they're more than that we will try to make it extremely clear. - It's helpful if you acknowledge so we know you've seen it, but we'll assume you have even if you don't. -- **de-escalating a heated conversation**: "please step back for a while, we can discuss this later after everyone has a chance to cool off." - If you see a message like this in a channel, that's your cue to back down so we don't have to go any further down this list. -- **channel kick**: asking one or more people to voluntarily leave a channel for a short time or doing the same via admin tools. - Usually used when someone refuses to step back from a heated conversation or for trolls. -- **ban**: asking someone to log off completely or doing the same via admin tools. - -## The Moderation Team - -The moderation team is here to help you and to guide conversation towards good places. -If you have any problems, use the `/admin` command and someone will respond soon. - -* Becca Stevens (@beccastevens) -* Keith Brown (@hellmark) -* Craig Buchek (@craigbuchek) -* Steven Pritchard (@silug) - -Moderators are chosen by the admins for being helpful in community spaces. diff --git a/content/slack.md b/content/slack.md deleted file mode 100644 index 819c10d..0000000 --- a/content/slack.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "Slack" -date: "2017-08-16T23:00:57-05:00" -weight: 0 ---- - -Most of the interaction in STL Tech happens on Slack. -We invite you to join us! - -You can ask any current STL Tech member for an invitation, or use our self-inviter tool located at [slack.stltech.org](http://slack.stltech.org). -See you soon! - -Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining. diff --git a/index.html b/index.html new file mode 100644 index 0000000..01ce908 --- /dev/null +++ b/index.html @@ -0,0 +1,382 @@ + + + + + StL Tech + + + + + + + + + + + + + + + + +
+ + + + + +
+ +
+
+ Back to Top ↑ +

Code of Conduct

+ +

STL Tech is dedicated to providing a harassment-free experience for everyone. We + do not tolerate harassment of participants in any form.

+

This code of conduct applies to all STL Tech spaces, including the STL Tech + Slack and Github Repositories, both online and off. Anyone who violates this + code of conduct may be sanctioned or expelled from these spaces at the + discretion of the the incident response team.

+

Please note that STL Tech spaces are not public spaces and that interpretation of + this Code of Conduct in matters of sanctioning or expelling participants in violation of same is at + the sole discretion of the incident response team.

+

Some STL Tech spaces may have additional rules in place, which will be made + clearly available to participants. Participants are responsible for knowing and + abiding by these rules.

+

Harassment includes:

+
    +
  • Offensive comments related to gender, gender identity and expression, sexual + orientation, disability, mental illness, neuro(a)typicality, physical + appearance, body size, age, race, or religion. Note that “offensive” includes + questioning the person’s right to equal treatment.
    • +
  • Unwelcome comments regarding a person’s lifestyle choices and practices, + including those related to food, health, parenting, drugs, and employment.
    • +
  • Concern trolling.
    • +
  • Deliberate misgendering or use of ‘dead’ or rejected names.
    • +
  • Gratuitous or off-topic sexual images or behavior in spaces where they’re not + appropriate.
    • +
  • Gratuitous or off-topic discussions of violence or violent behavior in this + space.
    • +
  • Physical contact and simulated physical contact (eg, textual descriptions like + *hug* or *backrub*) without consent or after a request to stop. +
    • +
  • Threats of violence towards any individual, group, or society at large.
    • +
  • Incitement of violence towards any individual, including encouraging a person + to commit suicide or to engage in self-harm.
    • +
  • Deliberate intimidation.
    • +
  • Stalking or following.
    • +
  • Harassing photography or recording, including logging online activity for + harassment purposes.
    • +
  • Sustained disruption of discussion.
    • +
  • Unwelcome sexual attention.
    • +
  • Pattern of inappropriate social contact, such as requesting/assuming + inappropriate levels of intimacy with others
    • +
  • Continued one-on-one communication after requests to cease.
    • +
  • Deliberate “outing” of any aspect of a person’s identity without their consent + except as necessary to protect vulnerable people from intentional abuse.
    • +
  • Publication of non-harassing private communication.
    • +
  • Complaining of ‘reverse‘ -isms (‘reverse racism,’ ‘reverse sexism,’, ‘cisphobia’, etc), or + otherwise attempting to legitimize the same as discrimination or oppression, will not be + tolerated under any circumstances
    • +
+

STL Tech prioritizes marginalized people’s safety over privileged people’s + comfort. the incident response team will not act on complaints regarding:

+
    +
  • ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
    • +
  • Reasonable communication of boundaries, such as “leave me alone,” “go away,” + or “I’m not discussing this with you.”
    • +
  • Communicating in a ‘tone’ you don’t find congenial
    • +
  • Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or + assumptions
    • +
+

Reporting

+

If you are being harassed by a member of STL Tech, notice that someone else is + being harassed, or have any other concerns, please contact the the incident + response team (contact information below). If the person who is harassing you is + on the team, they will recuse themselves from handling your incident. We will + respond as promptly as we can.

+

This code of conduct applies to STL Tech spaces, but if you are being harassed + by a member of STL Tech outside our spaces, we still want to know about it. We + will take all good-faith reports of harassment by STL Tech members, especially + the leadership team, seriously. This includes harassment outside our spaces and + harassment that took place at any point in time. The abuse team reserves the + right to exclude people from STL Tech based on their past behavior, including + behavior outside STL Tech spaces and behavior towards people who are not in STL + Tech.

+

In order to protect volunteers from abuse and burnout, we reserve the right to + reject any report we believe to have been made in bad faith. Reports intended to + silence legitimate criticism may be deleted without response.

+

We will respect confidentiality requests for the purpose of protecting victims + of abuse. At our discretion, we may publicly name a person about whom we’ve + received harassment complaints, or privately warn third parties about them, if + we believe that doing so will increase the safety of STL Tech members or the + general public. We will not name harassment victims without their affirmative + consent.

+

Consequences

+

Participants asked to stop any harassing behavior are expected to comply + immediately.

+

If a participant engages in harassing behavior, the incident response team may + take any action they deem appropriate, up to and including expulsion from all + STL Tech spaces and identification of the participant as a harasser to other STL + Tech members or the general public.

+

Contacts

+

the incident response team can be reached by directly messaging anyone on the + list below:

+
    +
  • Becca Stevens (@beccastevens)
    • +
  • Keith Brown (@hellmark)
    • +
  • Craig Buchek (@craigbuchek)
    • +
  • Steven Pritchard (@silug)
    • +
+

Source

+

This anti-harassment policy is based on the + example policy from the Geek + Feminism wiki, + created by the Geek Feminism community. +

+
+
+ + +
+
+ Back to Top ↑ +

Slack

+ +

Most of the interaction in STL Tech happens on Slack. + We invite you to join us!

+

You can ask any current STL Tech member for an invitation, or use the Community Inviter.

+

See you soon!

+

Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page + before joining.

+
+
+ +
+
+ Back to Top ↑ +

Member Handbook

+ +

The goal of the St. Louis Tech Slack is to create a space for discussions that will help members grow + personally and professionally, create new connections between those members, and showcase the best + things about the tech community in St. Louis.

+

This is the member handbook, a living guide to the ins and outs of the Slack. + If you have additions or changes, please submit a + PR on GitHub.

+

Channels

+

We have a lot of channels on the STL Tech Slack! + Join whatever you like (and don’t forget /list-private and + /join-private for channels you need to be a member of to see conversations in.) + Here are the channels that likely won’t change, and which everyone should know about: +

+
    +
  • #announce: Community-wide announcements, mostly about administration of the + Slack and to announce new channels. + Low volume. (and… you can’t leave! Mua ha ha ha ha!)
    • +
  • #everything: The widest-ranging channel. + For everything not specifically covered by another channel. + If this gets too noisy, you can leave it.
    • +
  • #meta: discussion about the Slack. + This is a good place to ask questions (is there a channel for X? How do we do + Y here?) +
    • +
  • #events: event postings. + This is mostly RSS feeds from meetup.com with local tech events. + It’s good for discovering new groups! + (note: If you have an event to announce, go ahead and do it here. We don’t do event + announcements in the announce channel since nobody can opt out of it.)
    • +
  • #jobs: the job board. + Please restrict this to primarily job postings
    • +
  • #careers: more general disucssion about careers (resumés, job hunting, et + cetera.)
    • +
  • #welcome: this is a space for new people to introduce themselves and the + community to welcome them to our space!
    • +
+

If you want to make a new channel, read the rest of this guide and then do it. + If you have any questions, please ask in #meta. + Please let us know about the new channel so we can announce it for you.

+

Slash Commands

+

Some useful slash commands (entered by typing /, then the command name in the chat box.) +

+
    +
  • /admin [message]: send a message to the admin team. + This does not mean that you will go on record as having said something, but the moderation team + will see who sent it. + We treat all reports as private by default.
    • +
  • /status [:emoji:] [message]: set your status. + This is how people get emoji next to their names.
    • +
  • /giphy [text]: search for reaction GIFs. + We have our Giphy integration set to only allow G-rated GIFs and to allow you to preview the + result before posting, so it’s fairly safe to use.
    • +
  • /list-private: list private (no-preview-before-join) channels. + These are private for various reasons, ask in #meta if you’re curious.
    • +
+

Some commands live on a Heroku dyno that may take a little bit to spin up, so you may have to retry. + Unfortunately, this includes /admin. + If you get persistent errors, please message an admin directly so we can go boop it after we help + you.

+

Do These Things

+

Here are a few things we especially like to see in the community. + The moderation team keeps these as standards for behavior which we compare members against.

+

You can help! + If you see a discussion getting off track or flamey, please call out the behavior (note: the + /behavior/ not the /person/.) + If you’re uncomfortable doing that, please contact a member of the moderation team by using + the /admin command.

+

On the other side, if you see someone being especially great about these things, tell them! + They’ll surely appreciate you noticing, and it makes everyone’s day better. + And, again, if you don’t feel comfortable doing this personally let an moderator know and + we’ll be happy to deliver the good news without mentioning the source.

+

Show Kindness and Respect

+

While the Slack is used by quite a few usergroups to organize in-person events, the majority of + communication among members is text-based. + This has the potential to lose a lot of tone and nuance that you’d get in a face-to-face + discussion! When you’re chatting, please be aware of that. + Go out of your way to be kind, and to make sure that the people you’re talking to are not + being made to feel uncomfortable.

+

This can be really difficult! + Check out the #interpersonal channel for discussions and tips on how to manage these interactions. +

+

Have Constructive Discussions

+

We want you to be able to learn new things and grow by being a part of the STL Tech community. + Part of this is making sure that discussions stay on-track and constructive. + Channel titles are pretty loose labels for the discussions that take place inside them, but the + discussions themselves should stay on topic.

+

A tip: it’s fine if you want to discuss controversial topics, as long as they’re relevant + and don’t devolve into flamewars and bickering. + Try having these kinds of discussions in a Slack thread. + Other people can opt in to the discussion instead of it taking over a channel, and they tend to lead + to better conversations about difficult topics.

+

Keep it Relevant

+

This is the St. Louis Tech Slack. + Things that are most relevant to the group are about either life in St. Louis or the tech industry. + Sometimes topics are both at once, which is great! + Everyone here is connected to the local tech scene in some way, be it as a programmer, consultant, + recruiter, or student. + This creates a huge range of topics that are relevant to the group, and some that aren’t. + Examples may help:

+
    +
  • Good topics: questions and discussions about specific programming languages and + techniques, organizing local usergroups, the way people in various social groups take part in + the tech scene, and “soft skills”.
    • +
  • Slightly tangential, but OK: where to get lunch and other topics that are + relevant to living in St. Louis, but not necessarily about technical topics.
    • +
  • Probably not: current events and politics (especially partisan politics), + dating advice, how to properly raise cattle… topics that are neither related to tech nor about + living in St. Louis.
    • +
+

That said, we’re more concerned about making sure people are well supported here than we are in + strictly enforcing topics. + So if you want to start a discussion or create a channel, please do! + If you’re in doubt or have questions, ask in #meta or DM a moderator or admin directly.

+

Be Welcoming

+

New members join frequently. + Make sure they feel welcome and supported when they show up. + If they’re your coworkers or friends, please introduce them (if they’re comfortable) in + #welcome. + If you’re new, feel free to introduce yourself!

+

Please Don’t Do These Things

+

We’ve found these things particularly counterproductive to achieving the goals of the + community:

+
    +
  • Sexual humor and innuendo: regardless of your personal feelings, these kinds of + humor make other people feel uncomfortable. + Please keep your conversation about the equivalent of a PG rating.
    • +
  • Trolling and Flaming: deliberately getting a rise out of someone does not make + conversation better.
    • +
  • Personal attacks: this is covered in the Code of Conduct (linked below) but + briefly: name calling, outing, and deliberately insensitive remarks are not OK in this + community.
    • +
+

A good guideline: would what you’re about to say be appropriate for a mixed-company + professional conversation? + Would you say it in a user group or conference talk? + If the answer is “no”, it’s probably not suitable here either.

+

We’re also big fans of the the + Recurse Center’s social rules. + Specifically: no feigning surprise, no well-actually’s, no back-seat driving, and no subtle + -isms.

+

In addition to the above, please read Code of + Conduct. + The behaviors listed there are used as bright lines for moderation and removal.

+

Finally, the STL Tech community is not a place for hate speech or hate groups. + If you’re a member of such a group (Nazis, the KKK, et cetera), please don’t join. + If we find you, we will remove you.

+

Consequences

+

Ultimately, the moderation team has to decide how to handle violations on a per-incident basis. + Things like intentional outing will be dealt with swiftly and severely, whereas a conversation + getting a little heated is less of an issue. + We’re humans too, not robots. + That said, here are some things we might do, in rough order of severity:

+
    +
  • private messages: most moderation takes place in private messages. + These usually just reminders about having constructive conversations. + If they’re more than that we will try to make it extremely clear. + It’s helpful if you acknowledge so we know you’ve seen it, but we’ll assume + you have even if you don’t.
    • +
  • de-escalating a heated conversation: “please step back for a while, we + can discuss this later after everyone has a chance to cool off.” + If you see a message like this in a channel, that’s your cue to back down so we + don’t have to go any further down this list.
    • +
  • channel kick: asking one or more people to voluntarily leave a channel for a + short time or doing the same via admin tools. + Usually used when someone refuses to step back from a heated conversation or for trolls.
    • +
  • ban: asking someone to log off completely or doing the same via admin tools. +
    • +
+

The Moderation Team

+

The moderation team is here to help you and to guide conversation towards good places. + If you have any problems, use the /admin command and someone will respond soon.

+
    +
  • Becca Stevens (@beccastevens)
    • +
  • Keith Brown (@hellmark)
    • +
  • Craig Buchek (@craigbuchek)
    • +
  • Steven Pritchard (@silug)
    • +
+

Moderators are chosen by the admins for being helpful in community spaces.

+
+
+ +
+ +
+

© 2021 StLTech.org

+
+ +
+ +
+ + + + + + + \ No newline at end of file diff --git a/netlify.toml b/netlify.toml index 6fe677b..e69de29 100644 --- a/netlify.toml +++ b/netlify.toml @@ -1,6 +0,0 @@ -[build] - publish = "public" - command = "git submodule init && git submodule update && hugo" - -[context.environment] - HUGO_VERSION = "0.26" diff --git a/themes/dimension b/themes/dimension deleted file mode 160000 index e648156..0000000 --- a/themes/dimension +++ /dev/null @@ -1 +0,0 @@ -Subproject commit e6481563275726656c28479744181c2fe686c4be From e359bf7e6ec77b0a3fd1e40904ce4b0ff65862be Mon Sep 17 00:00:00 2001 From: sehqlr Date: Fri, 3 Sep 2021 17:42:19 -0500 Subject: [PATCH 31/43] Switch globals to production only in netlify.toml --- netlify.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/netlify.toml b/netlify.toml index 84cbe8a..aa53bc9 100644 --- a/netlify.toml +++ b/netlify.toml @@ -1,6 +1,6 @@ -[build] +[context.production] publish = "public" command = "git submodule init && git submodule update && hugo" -[context.environment] +[context.production.environment] HUGO_VERSION = "0.85.0" From 857aed280beb7161605f9f68ad283bad035f7481 Mon Sep 17 00:00:00 2001 From: sehqlr Date: Fri, 3 Sep 2021 17:45:22 -0500 Subject: [PATCH 32/43] Readd netlify settings from master --- netlify.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/netlify.toml b/netlify.toml index e69de29..aa53bc9 100644 --- a/netlify.toml +++ b/netlify.toml @@ -0,0 +1,6 @@ +[context.production] + publish = "public" + command = "git submodule init && git submodule update && hugo" + +[context.production.environment] + HUGO_VERSION = "0.85.0" From aed4562829e2fae25760978c44270252754a019b Mon Sep 17 00:00:00 2001 From: sehqlr Date: Wed, 15 Sep 2021 11:09:18 -0500 Subject: [PATCH 33/43] Don't need to ignore anything currently --- .gitignore | 1 - 1 file changed, 1 deletion(-) delete mode 100644 .gitignore diff --git a/.gitignore b/.gitignore deleted file mode 100644 index a48cf0d..0000000 --- a/.gitignore +++ /dev/null @@ -1 +0,0 @@ -public From aabea2df45baeeebcf02fd268e9683b40c4c2ebb Mon Sep 17 00:00:00 2001 From: sehqlr Date: Wed, 15 Sep 2021 11:18:01 -0500 Subject: [PATCH 34/43] I forgot to delete this --- .envrc | 1 - 1 file changed, 1 deletion(-) delete mode 100644 .envrc diff --git a/.envrc b/.envrc deleted file mode 100644 index 051d09d..0000000 --- a/.envrc +++ /dev/null @@ -1 +0,0 @@ -eval "$(lorri direnv)" From 2a3d90e63553b07770200f98a502a873e5cf408d Mon Sep 17 00:00:00 2001 From: sehqlr Date: Wed, 15 Sep 2021 11:23:30 -0500 Subject: [PATCH 35/43] Removing copyright --- index.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/index.html b/index.html index 01ce908..2fa89a0 100644 --- a/index.html +++ b/index.html @@ -366,7 +366,6 @@

The Moderation Team

-

© 2021 StLTech.org

@@ -379,4 +378,4 @@

The Moderation Team

- \ No newline at end of file + From 243b4b429d6ee1d5627871859da0ce5eb01d9fa1 Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Wed, 10 Aug 2022 21:46:15 -0500 Subject: [PATCH 36/43] Remove ref to #interpersonal h/t bhicks --- index.html | 3 --- 1 file changed, 3 deletions(-) diff --git a/index.html b/index.html index 2fa89a0..2e40ddf 100644 --- a/index.html +++ b/index.html @@ -260,9 +260,6 @@

Show Kindness and Respect

discussion! When you’re chatting, please be aware of that. Go out of your way to be kind, and to make sure that the people you’re talking to are not being made to feel uncomfortable.

-

This can be really difficult! - Check out the #interpersonal channel for discussions and tips on how to manage these interactions. -

Have Constructive Discussions

We want you to be able to learn new things and grow by being a part of the STL Tech community. Part of this is making sure that discussions stay on-track and constructive. From 8fd3fa2b6739c8a738eb0425f062f7e05a10315f Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Wed, 10 Aug 2022 21:57:40 -0500 Subject: [PATCH 37/43] Replace inviter link --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 2e40ddf..87bd190 100644 --- a/index.html +++ b/index.html @@ -171,7 +171,7 @@

Slack

Most of the interaction in STL Tech happens on Slack. We invite you to join us!

You can ask any current STL Tech member for an invitation, or use the Community Inviter.

+ href="https://join.slack.com/t/stl-tech/shared_invite/zt-1e25idwp1-yVQaYhavmdqXK0iK~vxKBg">Community Inviter.

See you soon!

Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining.

From d518da9fb57378b654e5d297808ac702eae3e129 Mon Sep 17 00:00:00 2001 From: Sam Hatfield Date: Sat, 3 Sep 2022 17:40:17 -0500 Subject: [PATCH 38/43] Update index.html --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 87bd190..998d817 100644 --- a/index.html +++ b/index.html @@ -170,8 +170,8 @@

Slack

Most of the interaction in STL Tech happens on Slack. We invite you to join us!

-

You can ask any current STL Tech member for an invitation, or use the Community Inviter.

+

You can ask any current STL Tech member for an invitation, or use this invite link.

See you soon!

Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining.

From a20157d2e950f56ffc5494523926a0ff44908db1 Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Wed, 21 Sep 2022 23:07:50 -0500 Subject: [PATCH 39/43] Refreshing invite link --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 998d817..db22e4f 100644 --- a/index.html +++ b/index.html @@ -171,7 +171,7 @@

Slack

Most of the interaction in STL Tech happens on Slack. We invite you to join us!

You can ask any current STL Tech member for an invitation, or use this invite link.

+ href="https://join.slack.com/t/stl-tech/shared_invite/zt-1gj2886z7-vMMdL__vULISmRuR9FkGqg">invite link.

See you soon!

Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining.

From 49456cb9b682c9060e58fbbe869f845b002622be Mon Sep 17 00:00:00 2001 From: Marc Brooks Date: Fri, 29 Sep 2023 12:57:42 -0500 Subject: [PATCH 40/43] Fix code-of-conduct link Was pointing to an invalid (or perhaps non-public) wiki page. Now points back up in this document. --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index db22e4f..3d1b9c2 100644 --- a/index.html +++ b/index.html @@ -319,7 +319,7 @@

Please Don’t Do These Things

Recurse Center’s social rules. Specifically: no feigning surprise, no well-actually’s, no back-seat driving, and no subtle -isms.

-

In addition to the above, please read Code of +

In addition to the above, please read Code of Conduct. The behaviors listed there are used as bright lines for moderation and removal.

Finally, the STL Tech community is not a place for hate speech or hate groups. From 00fe7152dada06c19c181bdd27ddc92f7e194c38 Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Fri, 5 Jan 2024 10:08:50 -0600 Subject: [PATCH 41/43] Remove explicit IR/mod section --- index.html | 9 --------- 1 file changed, 9 deletions(-) diff --git a/index.html b/index.html index 3d1b9c2..9634b5e 100644 --- a/index.html +++ b/index.html @@ -144,15 +144,6 @@

Consequences

take any action they deem appropriate, up to and including expulsion from all STL Tech spaces and identification of the participant as a harasser to other STL Tech members or the general public.

-

Contacts

-

the incident response team can be reached by directly messaging anyone on the - list below:

-
    -
  • Becca Stevens (@beccastevens)
    • -
  • Keith Brown (@hellmark)
    • -
  • Craig Buchek (@craigbuchek)
    • -
  • Steven Pritchard (@silug)
    • -

Source

This anti-harassment policy is based on the example policy from the Geek From 4d8e1754f4862509253247e8549b22316cf207bd Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Fri, 5 Jan 2024 10:10:41 -0600 Subject: [PATCH 42/43] Remove explicit IR/mod section --- index.html | 6 ------ 1 file changed, 6 deletions(-) diff --git a/index.html b/index.html index 9634b5e..36409dc 100644 --- a/index.html +++ b/index.html @@ -341,12 +341,6 @@

Consequences

The Moderation Team

The moderation team is here to help you and to guide conversation towards good places. If you have any problems, use the /admin command and someone will respond soon.

-
    -
  • Becca Stevens (@beccastevens)
    • -
  • Keith Brown (@hellmark)
    • -
  • Craig Buchek (@craigbuchek)
    • -
  • Steven Pritchard (@silug)
    • -

Moderators are chosen by the admins for being helpful in community spaces.

From 0ce0ffec05c6af72be114598664dca65ab49169b Mon Sep 17 00:00:00 2001 From: Justin Honold Date: Thu, 27 Mar 2025 22:31:50 -0500 Subject: [PATCH 43/43] Update invite link --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 36409dc..04ed872 100644 --- a/index.html +++ b/index.html @@ -162,7 +162,7 @@

Slack

Most of the interaction in STL Tech happens on Slack. We invite you to join us!

You can ask any current STL Tech member for an invitation, or use this invite link.

+ href="https://join.slack.com/t/stl-tech/shared_invite/zt-32ongr3fo-DObek4T1BJuyiMIj7NAqpg">invite link.

See you soon!

Please familiarize yourself with the Code of Conduct and Member Handbook linked from the front page before joining.