Skip to content

Commit 3066c3a

Browse files
ivanreeseivanreese
committed
Rough draft of the member handbook
1 parent 1a0d643 commit 3066c3a

File tree

2 files changed

+81
-59
lines changed

2 files changed

+81
-59
lines changed

‎community.md

+2-59
Original file line numberDiff line numberDiff line change
@@ -2,69 +2,12 @@
22
title: Community
33
---
44

5-
65
# Community
76

87
We share and discuss ideas, prototypes, weekly demo videos, and inspirational links, with a friendly tone and an inclusive [code of conduct](https://github.com/futureofcoding/code-of-conduct). We also organize meetups and events in cities around the world and online. The discussions are deep and wonderful, with an eye to half-forgotten history and a head filled with dreams of what could someday be.
98

9+
Before joining the community, please familiarize yourself with the [member handbook](/member-handbook).
10+
1011
You can join the [Future of Coding Slack community right here](https://join.slack.com/t/futureofcoding/shared_invite/zt-8vhwkhg2-rKZkVYJRKTwLbumJWVNaSw). If this link doesn't work on your mobile device, try it on a computer. Our community is open to any topic related to furthering the evolution of computing. We also have a [Matrix bridge](#matrix-bridge).
1112

1213
You can explore the archives of our Slack using this [History Search](http://history.futureofcoding.org) tool (h/t to [Mariano Guerra](https://marianoguerra.github.io)).
13-
14-
<br>
15-
16-
## Channels
17-
18-
### #introductions
19-
Please post here when you first join. Tell us about your background, how you got into these topics, and why you joined the Slack. Feel free to share past project URLs and tag other members you know. Please, no links to startups, unless you also provide something deeply technical, philosophical, or otherwise interesting for us to talk about.
20-
21-
### #general
22-
Share interesting links you've found and want to spark a discussion over. Ask questions, or `/poll` the crowd.
23-
24-
### #two-minute-week
25-
Once each week, post a 2-minute (max) video explaining your most recent progress on your project. [Learn More](/two-minute-week)
26-
27-
### #feedback
28-
Share your own projects, blog posts, or detailed concepts. We'll give them constructive feedback.
29-
30-
### #meta
31-
Discuss ways to better collaborate, improve this Slack, or resolve community issues.
32-
33-
### #1-on-1s
34-
Every 4 weeks, @donut will randomly pair everyone in this channel for 1-on-1 conversations. It's a good way to get to know others in the Slack.
35-
36-
### #jobs
37-
Post if you are hiring or looking for work. Work related to the future of coding is preferred but all paid opportunities are allowed. Don't post more than once every couple of months about yourself or your company.
38-
39-
### #random
40-
Have something cool to share that doesn't quite feel on-topic? Our random channel is a great place to enthuse about interesting things that are only distantly related, or perhaps not related at all, to the future of coding.
41-
42-
<br>
43-
44-
There are a handful of other channels, focussed on meetups and subject-specific discussion. When you first arrive, be sure to check them out and join the ones that fit your interests.
45-
46-
Note that we likely aren't going to add any new subject-specific channels, as they tend to all become ghost towns. But if you have an idea for a fun kind of activity we could do together in a new channel — something like #two-minute-week — propose it in #meta!
47-
48-
<br>
49-
50-
## Threading
51-
This slack discusses nuanced topics, so we have a strong preference for organizing conversations by thread. If you want to respond to someone, please respond in the thread of that message, and not with another top-level message.
52-
53-
- On desktop, hover over the message and in the little floating toolbar that appears, click "Start a thread" or "Reply to thread".
54-
- On mobile, simply tap the message to open the thread view.
55-
56-
When you have something to share, try to post it as a single message (rather than posting several messages in quick succession) so that it's easier to start a thread of replies. You can create newlines with `shift-enter`. It's helpful to draft longer messages in your text editor of choice, and then paste them into Slack when you're ready to post.
57-
58-
<br>
59-
60-
## Matrix Bridge
61-
Our 4 most popular channels are bridged to Matrix rooms. They should be accessible in any Matrix client using the following aliases:
62-
63-
* [#_slack_futureofcoding_general:matrix.org](https://matrix.to/#/#_slack_futureofcoding_general:matrix.org)
64-
* [#_slack_futureofcoding_feedback:matrix.org](https://matrix.to/#/#_slack_futureofcoding_feedback:matrix.org)
65-
* [#_slack_futureofcoding_introductions:matrix.org](https://matrix.to/#/#_slack_futureofcoding_introductions:matrix.org)
66-
* [#_slack_futureofcoding_random:matrix.org](https://matrix.to/#/#_slack_futureofcoding_random:matrix.org)
67-
68-
You can also search for "Future of Coding" in a Matrix client to find them. Thanks to [J. Ryan Stinnett](https://twitter.com/jryans) for facilitating these, and for suggesting the following etiquette:
69-
70-
When responding to someone, be sure to use your Matrix client's "reply" feature, rather than (say) block-quoting manually in Markdown or something. Exact steps will differ per client. For Riot Web, you hover on the message to reply to, an action bar appears on the top right of the message, and you can pick "reply" (the curved arrow icon) from there and type your reply. For Riot iOS and Android, you long press on the message to reply to, and then you can choose "reply" from the menu and type your reply.

‎member-handbook.md

+79
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: Member Handbook
3+
---
4+
5+
6+
# Member Handbook
7+
8+
This handbook is your guide to the cultural norms of our community.
9+
10+
You'll learn our preferred ways to structure discussions, what channels we have and how we use them, a few points of etiquette, and some extra options for power users.
11+
12+
Note: This guide is currently a work-in-progress under active development (as of August 17th, 2020). Watch for nails!
13+
14+
15+
## How We Slack
16+
17+
We treat Slack like a message board, not like a chat. Here's how that works.
18+
19+
When you want to start a discussion, act as though you're creating a forum post or blog post. Prepare what you want to say in its entirety, including any links, and then submit it all in a single message. In other words, please don't send multiple messages in succession. You can create newlines with `shift-enter`, but it's helpful to draft longer messages in your text editor of choice, and then paste them into Slack when you're ready to post.
20+
21+
When you want to respond to someone's post, always use threaded replies. On desktop, hover over the message and in the popover menu at the top right of the message choose "Reply to thread"; on mobile, simply tap any message to open the thread view.
22+
23+
Please try to keep thread replies on-topic with respect to the original post. If you want to fork a discussion off in a new direction — say, if you feel a tangent coming on — by all means start a new top-level post that includes a link back to whatever message sparked your digression.
24+
25+
26+
## Channels
27+
28+
Each of our channels has a specific purpose. Below, you'll find the descriptions of how we use each channel. When you're in the Slack, you can check the *pinned messages* in a channel to see the channel's description.
29+
30+
### #introduce-yourself
31+
When you first join the community, please drop a post here. You can tell us about your background, what your interests are, how you got into computer futurism, how you found the Slack, interesting hobbies — anything that'll help us know where you're coming from. Feel free to share past project URLs, and tag other members you know.
32+
33+
Please, no links to startups, unless you also provide something deeply technical, philosophical, or otherwise interesting for us to talk about.
34+
35+
### #thinking-together
36+
This is the primary channel for discussion. If you have big thoughts or questions about the future of computing, post them here.
37+
38+
While you can add reference links to your posts, please take any discussions that center around external links to the next channel...
39+
40+
### #linking-together
41+
If you have an interesting link (or podcast, or book, or any other kind of external resource), this is the channel to discuss it.
42+
43+
Please keep this channel focused on links that are relevant to the future of computing, or reflections on the arc of history. For links about the present, they're better off in #present-company.
44+
45+
### #present-company
46+
Have something cool to share that doesn't quite feel on-topic? Our random channel is a great place to enthuse about interesting things that are only distantly related, or perhaps not related at all, to the future of coding.
47+
48+
### #share-your-work
49+
Share your own projects, blog posts, or detailed concepts. We'll give them constructive feedback.
50+
51+
### #two-minute-week
52+
Once each week, post a 2-minute (max) video explaining your most recent progress on your project. [Learn More](/two-minute-week)
53+
54+
### #random-encounters
55+
Every 4 weeks, @donut will randomly pair everyone in this channel for 1-on-1 conversations. It's a good way to get to know others in the Slack.
56+
57+
### #administrivia
58+
Discuss ways to better collaborate, improve this Slack, or resolve community issues.
59+
60+
### #announcements
61+
Post if you are hiring or looking for work. Work related to the future of coding is preferred but all paid opportunities are allowed. Don't post more than once every couple of months about yourself or your company.
62+
63+
<br>
64+
65+
There are a handful of other channels, focussed on meetups and subject-specific discussion. When you first arrive, be sure to check them out and join the ones that fit your interests.
66+
67+
<br>
68+
69+
## Matrix Bridge
70+
Our 4 most popular channels are bridged to Matrix rooms. They should be accessible in any Matrix client using the following aliases:
71+
72+
* [#_slack_futureofcoding_general:matrix.org](https://matrix.to/#/#_slack_futureofcoding_general:matrix.org)
73+
* [#_slack_futureofcoding_feedback:matrix.org](https://matrix.to/#/#_slack_futureofcoding_feedback:matrix.org)
74+
* [#_slack_futureofcoding_introductions:matrix.org](https://matrix.to/#/#_slack_futureofcoding_introductions:matrix.org)
75+
* [#_slack_futureofcoding_random:matrix.org](https://matrix.to/#/#_slack_futureofcoding_random:matrix.org)
76+
77+
You can also search for "Future of Coding" in a Matrix client to find them. Thanks to [J. Ryan Stinnett](https://twitter.com/jryans) for facilitating these, and for suggesting the following etiquette:
78+
79+
When responding to someone, be sure to use your Matrix client's "reply" feature, rather than (say) block-quoting manually in Markdown or something. Exact steps will differ per client. For Riot Web, you hover on the message to reply to, an action bar appears on the top right of the message, and you can pick "reply" (the curved arrow icon) from there and type your reply. For Riot iOS and Android, you long press on the message to reply to, and then you can choose "reply" from the menu and type your reply.

0 commit comments

Comments
 (0)