proglangdesign.net

The /r/ProgrammingLanguages Discord

Rules

These rules are guidelines for the moderation team just as much as they are for the members of this community. They are an elaboration of the rules for /r/ProgrammingLanguages.

1. Discussion should stay on topic

We are a community dedicated to the discussion of programming language design, so discussion should remain related to this topic. Use the appropriate Discord channel, and do not use the off-topic channels for unwanted promotional or NSFW material. Nobody’s going to mind if you go slightly off-topic in a channel, but don’t derail ongoing conversations, and at least move to the relevant channel if you find that the conversation has gone off-topic.

2. Be civil and respectful

While we encourage discussion, and yes, even disagreements, we require them to remain civil, respectful, and constructive. We don’t want you here if your behavior disrupts the community. Examples of disruptive behaviors include, but are not limited to: insults, threats, intimidation, discrimination, personal attacks, harassment, rudeness, doxing, excessive negativity, spamming, trolling, excessive melodrama, and sexualized attention. Use common sense. If someone tells you to stop, there’s a good chance you’re being disruptive. Don’t be a problem if you don’t want to be handled like one.

Additionally, the /r/ProgrammingLanguages server is not the place to debate politics, religion, or philosophy, and such debates often lead to bad blood all around. A number of our members are interested in goodwill discussion, however, so we do recommend joining our friends at The Philosophy Chat if you’re seeking productive discussion on the topic.

The Members List

You might have noticed that the members list isn’t divided into sections. All of us here are interested in programming language design and implementation, and we don’t want to force artificial distinctions between members of our community. However, there are a couple convenience roles to facilitate easier communication:

Channel Overview

Meta

The Meta category is dedicated to discussing the actual platforms that our community uses:

General Chat

PLT&D

This is the main section of our Discord, for discussing programming language theory and design. You’ll find channels devoted to every step of developing a programming language here, and a #general plt&d chat. Feel free to ask there if you don’t think any of the other channels will fit your topic better.

#beginners is intended to be the place to go for folks new to PLT&D. The moderators are going to be extra strict on moderation there - it’s supposed to be a welcoming place where someone without proglangs knowledge can ask how to get started and get help with their proglang journey, and being unwelcoming there is… unwelcome.

The IRC Bridge

We have two bridged Freenode IRC channels: #proglangdesign and ##programminglanguages. ##programminglanguages is an alternative channel with stricter moderation, controlled by our moderators, and is subject to the same rules as the Discord server.

Message edits and removals are not relayed to the IRC side. In addition, emoji and file uploads are not guaranteed to display properly on all IRC clients due to the more diverse nature of their deployment.

If you suspect that the bridge may not be working properly, please notify @jamestmartin#7117. The sooner you tell me, the sooner I can fix it.

Voice Channels

Go here to have an audio chat with other people! If you can’t talk, or want to share a link relevant to what you’re discussing, #voice-text is there as a supplemental text chat for the voice channels.

It’s also possible to share your screen in those channels, if you’d like to stream your development.

Project Channels

Members of our community may get a channel for their project in the Projects category.

How to get a project channel

Just go ahead and ping the mods (@Mods) in #meta. The only requirements are that you are a member of the project, and that it’s under active development.

When we create your channel, we will also create a role for members of your project. We will add you to both the @Language Developers role and the role for your language. You will have full permissions for your channel, including the ability to set the topic or pin messages.

Getting your project’s icon as an emoji

If you include your project’s square icon (preferably in PNG format, with a colored or transparent background), we will add your icon as an emoji.

Including your project on the website

If your project is reasonably mature and has a good landing page (e.g. a website or detailed README), I encourage you to go ahead and showcase your work on the website’s projects list!

You may simply open up a pull request to do this. The Discord moderators do not need to be involved.

The policy for inactive channels

  1. If no messages have been sent to a project’s channel for three months, it will be moved to the “Inactive Projects” category.
  2. If a project’s channel remains in the “Inactive Projects” category for three more months, the moderators will attempt to contact the owner of the channel.
  3. If the channel’s owner does not request for the channel’s life to be extended (e.g. for when the developer needs to be on hiatus for more than six months), the channel’s contents will be downloaded as a text file (not including e.g. file attachments), and that file will then be uploaded to #archive.

You may remove your project from the “Inactive Projects” category at any time by sending a message to the channel. If you are planning on going on a (temporary) hiatus, you may voluntarily put your channel into the “Inactive Projects” category using the !archive command. If you are planning on quitting your project permanently, please notify a moderator so that we may archive your channel. Finally, as you have full permissions over your channel, you may delete your channel (without backup!) at any time.

Thanks to Timon Passlick for the bot which automates the inactive projects list.

Git webhooks

You have permission in your channel to configure a webhook to recieve Git notifications in your channel (a feature which has built-in support from both GitHub and GitLab). Here’s a gist that describes how to do it.

There are some caveats, though: many users consider webhook notifications unnecessarily noisy and will mute your channel if you enable them (it is not possible to mute only the webhook). I would personally recommend restricting your webhook to only generate notifications for issues and pull requests.