Skip to content

Commit

Permalink
Update SLACK.md
Browse files Browse the repository at this point in the history
  • Loading branch information
carlosefr authored Sep 18, 2019
1 parent 636e923 commit 862064d
Showing 1 changed file with 43 additions and 37 deletions.
80 changes: 43 additions & 37 deletions SLACK.md
Original file line number Diff line number Diff line change
@@ -1,101 +1,107 @@
![Header](https://raw.githubusercontent.com/PixelsCamp/pixels_camp_2016/master/img/pxc_slack.png)

# Using Slack
# Pixels Camp Slack

Pixels Camp's organization provides a Slack instance as a communication channel to help the community to take best from the event. This guide provides a policy and some guidelines on how to use Slack in this context.
The Pixels Camp organization provides a Slack instance to help the community take the best from the event. This guide provides a policy and some guidelines on how to use Slack in this context.

### GENERAL

**What is Slack?**

Slack provides a rich text communication platform where its members and teams can exchange messages and files, public or privately, and interact with other services and applications. More about it [here][1]
Slack provides a rich communication platform where its members can exchange messages and files. It's both a way for the Pixels Camp community to interact with each other, as well with the organization. It's most active during the weeks around Pixels Camp, but it's available throughout the year.

**Who can use Pixel Camp's Slack**
More about Slack [here][1]

We've decided to open our Slack to anyone willing to talk about hard-core tech with the Pixels Camp community. If you fit this profile, then by all means, join us.
**Who can join?**

**Do I really need to use this?**
It's open to anyone willing to talk about hard-core tech with the Pixels Camp community. If you fit this profile, then by all means, join us.

No.
**How can I join?**

Slack is just another way for the organization and its partners to connect with the Pixels Camp community and support it, announce important messages, and foster discussion and creativity during the event. Hopefully, it will help and turn out to be a great instrument.
When you're accepted as an [attendee][5], you'll automatically get an invite via email if you haven't joined already. To join before being accepted, you can ask anyone already there to send you an invite.

It is also a big social experiment, and we're not completely sure it will work. Who knows what can happen when you put one thousand highly skilled engineers and hackers in a room interacting in real time, right?
**Do I really need to join?**

**I don't want to miss a beat, what are my other options?**
You don't _need_ to join. Slack is just another way to connect with the Pixels Camp community and foster discussion and creativity.

We use email for every critical message. We use a few social networks too. [Facebook][4] works nicely for general messages and announcements. We use [Instagram][3] because, er, it's cool and everyone loves great photos. Finally, we use [Twitter][2], our favorite, which is useful for real-time communication, announcements, and important messages. You should follow our [Twitter account][2] anyhow.
Having said this, it has proven to be useful for the past few Pixels Camp editions. People use it to ask questions, help each other (eg. challenges happening before and during the event), and generally have a good time. It's also one of the primary means of communication for quick updates during the event.

**The message notifications are taking my focus away and draining my battery**
**What are my other options?**

We use email for critical messages. We use a few social networks too. [Facebook][4] works nicely for general messages and announcements. We use [Instagram][3] because, er, it's cool and everyone loves great photos.

We use [Twitter][2] as well and, along with email and Slack, it's one of our primary means of communication. You should follow our [account][2] if you can.

**Slack notifications are bugging me and draining my battery!**

We have good news for you. Slack has marvelous controls over notification settings, per channel, if you need to. Here's something you can start by doing: turning off notifications in the #general channel unless there's a mention of yourself.

![Screenshot](https://github.com/PixelsCamp/pixels_camp_2016/blob/master/img/slacksettings.png?raw=true)

You can do this to other channels as well, and you can turn off all notifications except direct mentions of yourself if you wish (some members of the organization would say this is the sanest option).

### CODE OF CONDUCT

**Use English**
**Use english**

Whenever possible, especially in **#general**, use English.
Whenever possible, especially in `#general`, use **english**. Remember, although Pixels Camp happens in Portugal, it has participants from all over.

**No shouting, please**
**No shouting**

Hundreds of people in a chatroom can be quite noisy. Mostly, we want it to be useful. This means we have to be extra careful with anything that potentially triggers a notification, or ultimately, your precious attention. For caution, **@channel**, **@here** and **@everyone** are disabled to the public. When using the crowded default **#general** channel, please speak only when you have something to say.
Hundreds of people in a channel can be quite noisy and we want it to be useful, not annoying. This means we have to be extra careful with anything that potentially triggers a notification, or ultimately, tries to capture your precious attention. As a precaution, `@channel`, `@here` and `@everyone` mentions are disabled in the larger channels.

**Jibber-jabber, can I?**

We understand. You get all excited with bots, memes, giphy images and tasteless jokes about programming languages you don't use or understand. We want you to express yourself in creative ways, even if no one is listening, so there's the #random channel for that. Go for it.
We understand. You get all excited with bots, memes, giphy images, and random jokes about programming languages you don't use or understand. We want you to express yourself in creative ways, even if no one is listening, so there's the `#random` channel for that. Go for it. Or... you can create your own public or private channel and invite your pals to join you. That might work too.

Optionally, you can create your own public or private channel and invite your pals to join you. That might work too.
On `#general` the moderators will generally try to keep things clean and **will** delete messages they find inappropriate or noisy.

**Announcements**

The organization provides you an official public **#announcements** channel. Subscribe to it when you log in. We'll use this channel to broadcast important messages before and during Pixels Camp.
The organization provides you an official `#announcements` channel. We'll use this channel to broadcast information before and during Pixels Camp. Sometimes sponsors will too. It's a fairly low traffic channel, don't worry.

**Use the same nickname**
**Nickname**

The whole point of this is to promote interaction and networking between the participants of Pixels Camp, which means we should aim for some level of knowledge and transparency about everyone on Slack. We won't ask to expose your email; you probably wouldn't like that, but we're going to ask you to use the **same nickname you've used when you registered** for Pixels Camp (which is the same as your Github account).
The whole point of this is to promote interaction and networking between the participants of Pixels Camp, which means we should aim for some level of knowledge and transparency about everyone on Slack. We won't ask you to expose your email; you probably wouldn't like that, but we're going to ask you to use the **same nickname you've used when you registered for Pixels Camp** (ie. the same as your GitHub account).

We can't enforce this technically, but we're expecting you to comply.

**Use a real photo**

Read above on the nickname arguments. Use a real photo of yourself.
Read above on the nickname arguments. Consider using a real photo of yourself.

### COMMON CHANNELS

Here's a list of common channels you should be aware of:

#### #announcements

General announcements about Pixels Camp. Everyone should subscribe this. Low traffic.
General announcements about Pixels Camp. Everyone should subscribe it. Low traffic.

#### #marketplace
### #hackathon

A place where geeks can advertize and sell their stuff to others.
Questions and general discussion about the 48h hackathon.

#### #badges
### #quizshow

Every badge redeemed will echo in here. High traffic.
Support group for the quizmaster's "victims". Most active before Pixels Camp, with participants seeking hints and helping eachother get through the quiz qualifiers.

#### #jobs
See also the `#codeinthedark` and `#security-ctf` channels.

The one and **only** place you can post occasional job offers. Opt in. Remember: Pixels Camp is **not** a recruitment event and recruitment activities are not permitted to sponsors or participants.

#### #hardware
#### #badges

Hardware heads hang out here.
Every badge redeemed will echo in here. High traffic during the event. If you're competing for badges, this is where you can follow your rivals.

### INVITES
#### #jobs

**How do I get in?**
The one and **only** place you can post occasional job offers. Opt-in. Remember: Pixels Camp is **not** a recruitment event and recruitment activities by sponsors or participants are **not permitted**.

To get in, please fill up [this form][5]. Note that invites will be sent sequentially and as possible. Slack has strict [limitations][6] on the number of invites you can send per period of time.
#### #hardware

Hardware geeks hang out here.

[1]: https://slack.com/is
[2]: https://twitter.com/pixelscamp
[3]: https://www.instagram.com/pixelscamp/
[4]: https://www.facebook.com/pxlscmp/
[5]: https://brpx.typeform.com/to/W3IeHK
[6]: https://get.slack.help/hc/en-us/articles/201330256-Inviting-new-members-to-your-Slack-team#invitation-limits
[5]: https://pixels.camp/apply

0 comments on commit 862064d

Please sign in to comment.