Skip to content

Commit c6627cf

Browse files
committed
guidelines
1 parent 58feb48 commit c6627cf

File tree

1 file changed

+17
-28
lines changed

1 file changed

+17
-28
lines changed

src/pages/community-guidelines-slack.js

Lines changed: 17 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ const ResourcesPage = () => {
4343
SDV Slack Community Guidelines
4444
</h1>
4545
<p className="text-xl">
46-
Last Update: <i>September 2023</i>
46+
Last Update: <i>October 12, 2023</i>
4747
</p>
4848
</div>
4949
</div>
@@ -86,7 +86,22 @@ const ResourcesPage = () => {
8686
<div className="sm:pl-8 md:pl-16 xl:pl-20">
8787
<div className="text-lg my-10 post">
8888
<p className="text-3xl lg:text-4xl font-bold text-sdv-dark">
89-
1. Keep the workspace organized
89+
1. Discuss and participate openly
90+
</p>
91+
<p>
92+
We created our Slack Community as an open place to discuss the SDV. Anyone can join our community by creating a profile. Whether it's through asking questions, having detailed discussions or reacting to existing conversations, you are welcome to engage with the community in any way you feel comfortable. Feel free to answer questions by replying in a thread, especially if you've run into the same problems in the past or have workarounds.
93+
</p>
94+
<p>
95+
The guidance below allows us to keep the community safe:
96+
</p>
97+
<ul>
98+
<li>We encourage SDV Slack members to create profiles that accurately represent who they are, including their name, profile image and email. Please do not deliberately change your identity in order to mislead the community, for example by providing a temporary email or a fake name or profile photo. Impersonating others could also result in your expulsion.</li>
99+
<li>We encourage everyone to communicate in public channels instead of through private Direct Messages (DMs). When you keep discussions in the public space, everyone in the community can benefit from the solutions that you find, and others can also join in. This also applies to communicating with SDV team members — we try to respond to questions on a first-come, first-serve basis, and generally get to everything within a few business days. <strong>You will <i>not</i> receive a faster response by directly messaging individual members of the SDV team.</strong></li>
100+
</ul>
101+
</div>
102+
<div className="text-lg my-10 post">
103+
<p className="text-3xl lg:text-4xl font-bold text-sdv-dark">
104+
2. Keep the workspace organized
90105
</p>
91106
<p>
92107
Before starting a discussion, check to see if there is already
@@ -147,32 +162,6 @@ const ResourcesPage = () => {
147162
to add external Slack Apps to the SDV space.)
148163
</p>
149164
</div>
150-
<div className="text-lg my-10 post">
151-
<p className="text-3xl lg:text-4xl font-bold text-sdv-dark">
152-
2. Discuss and participate openly
153-
</p>
154-
<p>
155-
Whether it's through asking questions, having detailed
156-
discussions or reacting to existing conversations, you are
157-
welcome to engage with the community in any way you feel
158-
comfortable. Feel free to answer questions by replying in a
159-
thread, especially if you've run into the same problems in the
160-
past or have workarounds.
161-
</p>
162-
<p>
163-
We encourage everyone to communicate in public channels instead
164-
of through private Direct Messages (DMs). When you keep
165-
discussions in the public space, everyone in the community can
166-
benefit from the solutions that you find, and others can also
167-
join in. This also applies to communicating with SDV team
168-
members — we try to respond to questions on a first-come,
169-
first-serve basis, and generally get to everything within a few
170-
business days. <strong className="font-bold">
171-
You will <i className="italic">not</i> receive a faster response by
172-
directly messaging individual members of the SDV team.
173-
</strong>
174-
</p>
175-
</div>
176165
<div className="text-lg my-10 post">
177166
<p className="text-3xl lg:text-4xl font-bold text-sdv-dark">
178167
3. Continue with involved discussions on GitHub

0 commit comments

Comments
 (0)