open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • Add a picture of yourself
  • Set your nickname to your full name
  • Post in the right channels
  • Keep things "safe for work"
  • Use @ mentions sparingly
  • Mute your microphone when you're not speaking

Was this helpful?

  1. Tools & Resources
  2. Discord

Discord etiquette

Help your fellow participants have the best experience they can while communicating at osoc

PreviousBasicsNextSetting your nickname & description

Last updated 4 years ago

Was this helpful?

Add a picture of yourself

During a remote edition, a picture does a lot! To help get to know and recognize each other, we suggest you .

If you're already using Discord to engage with other communities, but would rather not have your picture in them, you can make an account for osoc specifically.

Set your nickname to your full name

This makes you easier to recognize, and makes things a little more personal. specifically, so this information stays within the osoc server.

Post in the right channels

Most channels describe what they're for. Post everything related to your specific project in its channel.

Keep things "safe for work"

Use @ mentions sparingly

Most people have notifications for mentions on. If something isn't urgent or you're not replying to someone's message, use @ sparingly. Discord tends to be open during work, and unnecessary notifications will distract from working flow.

Mute your microphone when you're not speaking

When in a voice channel - mute your microphone when you're not actively talking. This helps reduce background noises from fans, busy streets, and excited family members or roommates :).

As mentioned in the , messages & content that contain violence, hate, racism, nudity, pornography, profanity, gore, or anything else considered unwelcome in a work environment, have no place in the osoc communication channels.

You can also , which makes sure your microphone is only activated when you press a key.

Code of Conduct
enable push to talk
add a picture of yourself
You can set different nicknames for different servers