aboutsummaryrefslogtreecommitdiffstats
path: root/templates/main/about
diff options
context:
space:
mode:
Diffstat (limited to 'templates/main/about')
-rw-r--r--templates/main/about/channels.html268
-rw-r--r--templates/main/about/index.html40
-rw-r--r--templates/main/about/partners.html46
-rw-r--r--templates/main/about/privacy.html324
-rw-r--r--templates/main/about/rules.html124
5 files changed, 0 insertions, 802 deletions
diff --git a/templates/main/about/channels.html b/templates/main/about/channels.html
deleted file mode 100644
index ac3d95b5..00000000
--- a/templates/main/about/channels.html
+++ /dev/null
@@ -1,268 +0,0 @@
-{% extends "main/base.html" %}
-{% block title %}Channels{% endblock %}
-{% block og_title %}Channels{% endblock %}
-{% block og_description %}Channel listing and what's each channel is for{% endblock %}
-{% block content %}
- <div class="uk-section">
- <div class="uk-container uk-container-small">
- <article class="uk-article">
- <h1 class="uk-article-title hover-title" id="top">
- Channels
-
- <a href="#top" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Keeping things tidy
- </p>
-
- <p>
- Every channel on the server has a use, and we expect users to keep things relevant to the channel
- whenever possible. Below, we've outlined all of the channels a normal user has access to send
- messages to, and what they should be used for.
- </p>
-
- <h2>Discussion</h2>
-
- <p>
- Channels in this section are designated for discussion and chat, and shouldn't be used for help
- requests in most cases. All channels in this category are on-topic.
- </p>
-
- <table uk-table class="uk-table-striped uk-table uk-table-divider table-bordered">
- <thead>
- <tr>
- <th>Channel</th>
- <th>Info</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="fira-code">#python-discussion</td>
- <td>
- Discussion about the Python programming language and ecosystem
- </td>
- </tr>
- <tr>
- <td class="fira-code">#tools</td>
- <td>
- Discussion relating to Python tooling - IDEs, editors, package managers, documentation
- generators, and so on
- </td>
- </tr>
- <tr>
- <td class="fira-code">#meta</td>
- <td>
- Discussion and suggestions relating to the Discord server, site, bot, and other
- projects of ours
- </td>
- </tr>
- </tbody>
- </table>
-
- <h2>Off-Topic</h2>
-
- <p>
- Channels in this section are designated for off-topic <strong>discussion</strong>, and any topic
- may be talked about here once it follows our rules. Note that these channels are for discussion,
- and are not places for you to dump images or memes.
- </p>
-
- <p>
- These channels are renamed daily by the server bot. Suggest funny channel names
- <a href="https://gitlab.com/python-discord/meta/issues/8">on the dedicated GitLab meta issue</a>.
- </p>
-
- <h2>Python Help</h2>
-
- <p>
- Channels in this section are strictly on-topic, and designated for asking general Python-related
- questions. If you're a beginner or you need some help with your Python, this is probably where you
- want to be.
- </p>
-
- <p>
- Please try to pick a channel that isn't busy when asking your question. If you're not sure
- how best to ask a question, take a look at
- <a href="{{ url_for("main.info.help") }}">our guide on that subject</a>.
- </p>
-
- <h2>Topical Chat/Help</h2>
-
- <p>
- Channels in this section are strictly on-topic, and geared towards specific subjects. They can be
- used for either discussion or asking questions - if you need help with one of the specific things
- covered here, it's best to ask your question in the relevant channel rather than one of the general
- help channels.
- </p>
-
- <table uk-table class="uk-table-striped uk-table uk-table-divider table-bordered">
- <thead>
- <tr>
- <th>Channel</th>
- <th>Info</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="fira-code">#databases</td>
- <td>
- Discussion and questions relating to databases - both traditional and document-oriented -
- such as SQLite, Postgresql, RethinkDB, Cassandra, Redis and so on
- </td>
- </tr>
- <tr>
- <td class="fira-code">#data-science</td>
- <td>
- Discussion and questions relating to machine learning, natural language processing,
- statistics and graphing and so on
- </td>
- </tr>
- <tr>
- <td class="fira-code">#dev-ops</td>
- <td>
- Discussion and questions relating to devops - for example, deployment and configuration
- of services, virtual machines and containers, and the day-to-day running of your
- Python-powered services
- </td>
- </tr>
- <tr>
- <td class="fira-code">#discord-py</td>
- <td>
- Discussion and questions relating to the
- <a href="https://github.com/Rapptz/discord.py">discord.py</a> library for writing
- Discord bots in Python - This channel refers specifically to the
- <a href="https://discordpy.readthedocs.io/en/async/"><span class="fira-code">async</span> branch of discord.py</a>,
- which is currently the stable version but is heavily outdated
- </td>
- </tr>
- <tr>
- <td class="fira-code">#discord-py-rewrite</td>
- <td>
- Discussion and questions relating to the
- <a href="https://github.com/Rapptz/discord.py">discord.py</a> library for writing
- Discord bots in Python - This channel refers specifically to the
- <a href="https://discordpy.readthedocs.io/en/rewrite/"><span class="fira-code">rewrite</span> branch of discord.py</a>,
- which is the most up-to-date version but is considered to be in beta
- </td>
- </tr>
- <tr>
- <td class="fira-code">#security</td>
- <td>
- Discussion and questions relating to cybersecurity, especially in relation to Python
- and best practises
- </td>
- </tr>
- <tr>
- <td class="fira-code">#software-testing</td>
- <td>
- Discussion and questions relating to testing your Python applications
- </td>
- </tr>
- <tr>
- <td class="fira-code">#user-interface</td>
- <td>
- Discussion and questions relating to designing and building user interfaces
- in Python, and related libraries and tools - this includes graphical interfaces and
- console interfaces
- </td>
- </tr>
- <tr>
- <td class="fira-code">#web-development</td>
- <td>
- Discussion and questions relating to web development - including Python frameworks
- such as Flask and Django, as well as HTML and JavaScript where it relates to the Web
- </td>
- </tr>
- </tbody>
- </table>
-
- <h2>Events</h2>
-
- <p>
- Channels in this section are strictly on-topic, and designated for the discussion of Python-related
- events - for example, our <a href="{{ url_for("main.jams.index") }}">Code Jams</a>, as well as any
- other large, related events that many of our users are partaking in.
- </p>
- <p>
- If you're part of a related event and you don't see a channel for it here, feel free to ask for one!
- </p>
-
- <h2>Special</h2>
-
- <p>
- Channels in this section are designated for special uses, and don't really fit into the other
- categories.
- </p>
-
- <table uk-table class="uk-table-striped uk-table uk-table-divider table-bordered">
- <thead>
- <tr>
- <th>Channel</th>
- <th>Info</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="fira-code">#bot-commands</td>
- <td>
- A channel specifically for making use of the bots on the server without clogging up
- the other channels
- </td>
- </tr>
- <tr>
- <td class="fira-code">#checkpoint</td>
- <td>
- Invisible to most users after verifying themselves, this channel is where new
- users verify that they accept the rules and
- <a href="{{ url_for("main.about.privacy") }}">privacy policy</a>
- </td>
- </tr>
- <tr>
- <td class="fira-code">#challenges</td>
- <td>
- While currently not in use, this channel lists various programming challenges that
- one might like to attempt during their learning efforts - we'll be replacing this
- with something better later, so stay tuned!
- </td>
- </tr>
- <tr>
- <td class="fira-code">#reddit</td>
- <td>
- A listing channel with a live feed of posts from
- <a href="https://reddit.com/r/Python">r/Python</a>, our official subreddit.
- </td>
- </tr>
- <tr>
- <td class="fira-code">#show-your-projects</td>
- <td>
- A listing channel for users to show off their Python-oriented projects - please note
- that this is not a discussion channel, and we do not allow postings for communities
- or commercial projects - and if possible, we prefer that you post a link to your
- source code instead of a website
- </td>
- </tr>
- <tr>
- <td class="fira-code">#show-your-projects-discussion</td>
- <td>
- Strictly on-topic discussion relating to projects posted in
- <span class="fira-code">#show-your-projects</span> - we prefer that all discussion
- relating to personal projects goes here
- </td>
- </tr>
- </tbody>
- </table>
-
- <h2>Voice</h2>
-
- <p>
- This section contains all of our general voice channels, as well as a single text channel -
- <span class="fira-code">#voice-chat</span>. If you're in a voice channel but can't use a
- microphone, you should use this channel to reply to other users using text instead of any
- of the other channels.
- </p>
- </article>
- </div>
- </div>
-{% endblock %} \ No newline at end of file
diff --git a/templates/main/about/index.html b/templates/main/about/index.html
deleted file mode 100644
index 35fe6ae0..00000000
--- a/templates/main/about/index.html
+++ /dev/null
@@ -1,40 +0,0 @@
-{% extends "main/base.html" %}
-{% block title %}About{% endblock %}
-{% block og_title %}About{% endblock %}
-{% block og_description %}Partners links, and information about the server{% endblock %}
-{% block content %}
- <div class="uk-section">
- <div class="uk-container uk-container-small">
- <article class="uk-article">
- <h1 class="uk-article-title hover-title" id="top">
- About
-
- <a href="#top" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Learn about the server, find links to our partners, and more!
- </p>
- <p>
- <strong>Channels</strong>
- <a href="{{ url_for('main.about.channels') }}"><i class="fas fa-link"></i></a>
- <br />
- <span class="uk-text-meta">Server channel listings and information</span>
- </p>
- <p>
- <strong>Partners</strong>
- <a href="{{ url_for('main.about.partners') }}"><i class="fas fa-link"></i></a>
- <br />
- <span class="uk-text-meta">Links to our partnered servers</span>
- </p>
- <p>
- <strong>Rules</strong>
- <a href="{{ url_for('main.about.rules') }}"><i class="fas fa-link"></i></a>
- <br />
- <span class="uk-text-meta">Rules and infraction information for our community</span>
- </p>
- </article>
- </div>
- </div>
-{% endblock %}
diff --git a/templates/main/about/partners.html b/templates/main/about/partners.html
deleted file mode 100644
index 83803265..00000000
--- a/templates/main/about/partners.html
+++ /dev/null
@@ -1,46 +0,0 @@
-{% extends "main/base.html" %}
-{% block title %}Partners{% endblock %}
-{% block og_title %}Partners{% endblock %}
-{% block og_description %}List and Links to Partner servers{% endblock %}
-{% block content %}
- <div class="uk-section">
- <div class="uk-container uk-container-small">
- <article class="uk-article">
- <h1 class="uk-article-title hover-title" id="top">
- Partners
- <a href="#top" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <div class="uk-column-1-2@m uk-column-divider" id="partner-cards">
- {% if partners is none %}
- <div class="uk-alert-danger" uk-alert>
- <p>
- We were unable to load the <code>partners.json</code> file. If you see this, please
- notify us!
- </p>
- </div>
- {% else %}
- {% for partner_name, partner_data in partners.items() %}
- <div class="uk-card-default uk-card-hover uk-inline">
- <div class="uk-card-media-top">
- <a href="{{ partner_data['invite'] }}">
- <img src="{{ partner_data['banner'] }}" alt="{{ partner_name }}"/>
- </a>
- </div>
- <div class="uk-card-body">
- <p>{{ partner_data['description'] }}</p>
- </div>
- <div class="uk-card-footer">
- <a href="{{ partner_data['invite'] }}" class="uk-button uk-button-text">
- Join the server
- </a>
- </div>
- </div>
- {% endfor %}
- {% endif %}
- </div>
- </article>
- </div>
- </div>
-{% endblock %}
diff --git a/templates/main/about/privacy.html b/templates/main/about/privacy.html
deleted file mode 100644
index fa4e2aab..00000000
--- a/templates/main/about/privacy.html
+++ /dev/null
@@ -1,324 +0,0 @@
-{% extends "main/base.html" %}
-{% block title %}Privacy{% endblock %}
-{% block og_title %}Privacy{% endblock %}
-{% block og_description %}Our privacy policy, and compliance information{% endblock %}
-{% block content %}
- <div class="uk-section">
- <div class="uk-container uk-container-small">
- <article class="uk-article">
- <h1 class="uk-article-title hover-title" id="top">
- Privacy
-
- <a href="#top" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Stay safe out there
- </p>
-
- <p>
- We take every step to ensure that your data is used ethically and that includes making sure that
- you know exactly what data we collect, and what we do with it. That means that instead of a
- bunch of legalese, we've provided this information in an easy, human-readable form below.
- </p>
-
- <p>
- Please note that we are a completely non-profit community. We have no interest in selling your
- data, or shipping it off to third parties. Our community is entirely volunteer-run - it does
- not have any form of monetary income whatsoever - and we believe that this is how it should be.
- </p>
-
- <h3>Data collection</h3>
-
- <div class="uk-alert uk-alert-warning">
- <p>
- Please note that data <span class="uk-text-primary">marked with blurple text below</span> is not
- automatically removed. We need to hold onto this information in order to maintain infraction records
- and ensure the smooth running of our community.
- </p>
- <p>
- We do not store any data until you have verified yourself in <code>#checkpoint</code> on the server,
- and certified that you agree to our rules and privacy policy. If you are leaving the server and would
- like us to remove this data as well, please contact a member of staff directly.
- </p>
- </div>
-
- <table class="uk-table uk-table-divider uk-table-striped uk-table-small table-bordered" id="data-collection-table">
- <thead>
- <tr class="thick-bottom-border">
- <th class="uk-width-1-4">What we collect</th>
- <th class="uk-width-1-4">When it's collected</th>
- <th class="uk-width-1-4">What it's used for</th>
- <th class="uk-width-1-4">Who can access it</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="uk-text-primary">Discord user ID</td>
- <td class="uk-table-shrink"><strong>!accept</strong> run on Discord</td>
- <td>Statistics, data association (infractions, code jam applications, etc)</td>
- <td>Administrative staff</td>
- </tr>
- <tr>
- <td class="uk-text-primary">Discord username and discriminator</td>
- <td class="uk-table-shrink"><strong>!accept</strong> run on Discord</td>
- <td>Display purposes (alongside ID in staff areas, public profiles)</td>
- <td>Public (for code jam team listings and winner info) and staff areas</td>
- </tr>
- <tr>
- <td class="uk-text-primary">Discord avatar URLs</td>
- <td class="uk-table-shrink"><strong>!accept</strong> run on Discord</td>
- <td>Display purposes (alongside ID in staff areas, public profiles)</td>
- <td>Public (for code jam team listings and winner info) and staff areas</td>
- </tr>
- <tr>
- <td class="uk-text-primary">Assigned roles on Discord</td>
- <td class="uk-table-shrink"><strong>!accept</strong> run on Discord</td>
- <td>Access control for the site, infractions, role restoration after kicks</td>
- <td>Administrative staff</td>
- </tr>
- <tr class="thick-bottom-border">
- <td class="uk-text-primary">Messages sent on Discord</td>
- <td class="uk-table-shrink"><strong>!accept</strong> run on Discord</td>
- <td>
- Stored in memory by the bot for processing temporarily, may also end up in
- staff-only logging channels for the purposes of accountability and infraction
- management
- </td>
- <td>Administrative staff</td>
- </tr>
-
- <tr class="thick-bottom-border">
- <td>OAuth access and refresh token</td>
- <td class="uk-table-shrink">Discord login on site</td>
- <td>Used to find your Discord user ID when you log in</td>
- <td>Administrative staff</td>
- </tr>
-
- <tr>
- <td>GitLab username</td>
- <td class="uk-table-shrink">Code jam profile</td>
- <td>Used to identify you on GitLab as part of a code jam team</td>
- <td>Public, for code jam team listings</td>
- </tr>
- <tr class="thick-bottom-border">
- <td>Timezone</td>
- <td class="uk-table-shrink">Code jam profile</td>
- <td>A factor in code jam team match-ups</td>
- <td>Administrative staff</td>
- </tr>
-
- <tr class="thick-bottom-border">
- <td>System Information</td>
- <td class="uk-table-shrink">Code jam signup</td>
- <td>Used to verify that you have a working environment</td>
- <td>Administrative staff</td>
- </tr>
-
- <tr>
- <td>Email Address</td>
- <td class="uk-table-shrink">Issues emailed directly to GitLab</td>
- <td>Used to keep track of issue submissions</td>
- <td>GitLab staff - never stored in our database</td>
- </tr>
- </tbody>
- </table>
-
- <p>
- Note that we don't ordinarily collect your email address, and your email address will never be
- stored on our servers. The only time it will be shown is in the title of any issues you create on
- GitLab by directly emailing us on the <code>meta@</code> email address. These issues are confidential,
- not associated with a user account, do not require a GitLab account, and will only ever be seen by
- staff.
- </p>
-
- <h1 class="uk-article-title hover-title" id="consent">
- Collecting consent
-
- <a href="#consent" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
-
- <p>
- If you joined the community on or before the <strong>20th of May, 2018</strong>, you will have seen an announcement about our
- privacy policy on the Discord server. You will have had the opportunity to leave the server if
- you weren't happy with it. If you decided to stay, then we will consider you to have accepted
- our use of your data, as detailed on this page.
- </p>
- <p>
- If you joined the community after the <strong>20th of May, 2018</strong>, you will have been greeted with the
- <code>#checkpoint</code> channel. In this channel, you must run the <code>!accept</code>
- command to signify that you accept both our rules and this privacy policy. This will also have been
- detailed in a message in that channel.
- </p>
- <p>
- Please note that your acceptance of this privacy policy is retroactive, and you agree that any
- revisions to it will apply when they are published. We will attempt to keep everyone updated on
- changes to this policy via the usual announcement channels - if at any point you are not happy with
- a change to the privacy policy, please bring it up with a member of staff. If we're unable to
- solve your issue in a satisfactory way, you may remove your data as detailed below.
- </p>
-
- <h1 class="uk-article-title hover-title" id="removal">
- Data removal
-
- <a href="#removal" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
-
- <p>
- If you'd like to remove your data from our servers, there are two options available to you.
- </p>
-
- <div class="uk-grid uk-grid-match" uk-grid>
- <div class="uk-width-3-5@m">
- <div class="uk-card uk-card-default uk-card-small">
- <div class="uk-card-header">
- <h3 class="uk-card-title">Complete data removal</h3>
- </div>
-
- <div class="uk-card-body">
- <p>
- If you'd like to remove all of your personal data from our servers, all you need to do
- is leave the Discord server. As much of the data we collect is necessary for running
- our community, we are unable to offer you community membership with zero data collection.
- </p>
- <p>
- Please note that data <span class="uk-text-primary">marked with blurple text in the table above</span>
- is not automatically removed. We need to hold onto this information in order to maintain infraction records
- and ensure the smooth running of our community. If you are leaving the server and would like us to remove
- this data as well, please contact a member of staff directly.
- </p>
- <p>
- Once you've left the Discord server, your data is removed automatically. Please note that
- for the sake of data integrity and moderation purposes, we do not remove your Discord
- user ID from our database - but we do anonymize your data as far as possible.
- </p>
- <p>
- As with deleting your code jam profile directly, you will be issued an automatic ban
- from future code jams if you have applied for or are currently taking part in a
- code jam.
- </p>
- </div>
- </div>
- </div>
- <div class="uk-width-2-5@m">
- <div class="uk-card uk-card-default uk-card-small">
- <div class="uk-card-header">
- <h3 class="uk-card-title">Code jam profile removal</h3>
- </div>
-
- <div class="uk-card-body">
- <p>
- If you've provided us with a code jam profile in the past and would like to remove
- it, you may do so by heading to the
- <a href="{{ url_for("main.jams.profile") }}">"My Profile" page</a>,
- where you will find a button that will remove your profile.
- </p>
- <p>
- Please note that this is a nuclear option. If you have applied for or are currently
- taking part in a code jam, this will void your application and you will receive an
- automatic ban from future code jams until you've contacted us about it.
- </p>
- </div>
- </div>
- </div>
- </div>
-
- <h1 class="uk-article-title hover-title" id="gdpr">
- GDPR compliance
-
- <a href="#gdpr" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Keeping your data under your control
- </p>
-
- <p>
- Under the terms specified above, we do aim to comply with GDPR. While we do not currently have
- an automated way for users to export the data they've provided to us, we're happy to do this
- manually or answer any other GDPR- or privacy-related queries you may have. Feel free to contact
- our GDPR officer on Discord (<code>gdude#2002</code>), or any other member of the administrative
- staff.
- </p>
- <p>
- We believe that the best way to keep your personal data safe is to avoid collecting it at all.
- Discord itself is GDPR-compliant and they've already done the legwork required to ensure that
- your data may be collected - so we don't see the need to collect your personal information
- ourselves. Don't forget that by using Discord, you are stating that you are of legal age in
- your country to give consent to process your data!
- </p>
- <p>
- We are currently working on an automated way to get all of your data in both a human-readable
- and machine-readable format. Keep your eye on the usual announcements channels for more information
- on that, as it happens.
- </p>
-
- <h1 class="uk-article-title hover-title" id="changelog">
- Changelog
-
- <a href="#changelog" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Accountability, for the masses
- </p>
-
- <ul class="uk-list uk-list-divider">
- <li>
- <h4>July 27th, 2018</h4>
- <p>
- As we're replacing Rowboat (the bot we use for moderation), we need to hold onto some of
- your data - even after you've left the server. This is necessary to ensure the smooth
- running and security of our community.
- </p>
- </li>
- <li>
- <h4>July 3rd, 2018</h4>
- <p>
- While we don't collect your email addresses, they are visible on GitLab if you email an
- issue directly to our <code>meta@</code> email address, but only to staff.
- </p>
- </li>
- <li>
- <h4>June 7th, 2018</h4>
- <p>
- We no longer collect GitHub usernames - instead, we collect GitLab usernames. Additionally,
- we now collect user avatar URLs for display purposes.
- </p>
- </li>
- <li>
- <h4>June 5th, 2018</h4>
- <p>
- Rectified an omission in the old privacy policy, where the system information you provide
- as part of a code jam signup wasn't mentioned.
- </p>
- </li>
- <li>
- <h4>May 31st, 2018</h4>
- <p>
- We no longer collect your date of birth, and all collected dates of birth have been
- removed from our database. The reason for this is that Discord itself already complies with
- GDPR - and in order for you to sign up for a code jam, you must already have a Discord
- account.
- </p>
- </li>
- <li>
- <h4>May 20th, 2018</h4>
- <p>
- Completed the first version of our privacy policy. We also updated our OAuth scopes for
- Discord logins - we no longer collect your email, or get the access to join you to servers
- automatically. All collected emails have also been removed from the database.
- </p>
- </li>
- </ul>
- </article>
- </div>
- </div>
-{% endblock %}
diff --git a/templates/main/about/rules.html b/templates/main/about/rules.html
deleted file mode 100644
index b11f91d9..00000000
--- a/templates/main/about/rules.html
+++ /dev/null
@@ -1,124 +0,0 @@
-{% extends "main/base.html" %}
-{% block title %}Rules{% endblock %}
-{% block og_title %}Rules{% endblock %}
-{% block og_description %}The server rules, along with an explanation of what happens when they're broken{% endblock %}
-{% block content %}
- <div class="uk-section">
- <div class="uk-container uk-container-small">
- <article class="uk-article">
- <h1 class="uk-article-title hover-title" id="top">
- Rules
-
- <a href="#top" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Keeping our noses clean since 2017
- </p>
- <p>
- We have a small but strict set of rules on our server. Please read over them and take them on board -
- if you don't understand anything or need some clarification, feel free to ask any staff member!
- </p>
- <ol>
- <li>
- Be polite, and do not spam
- </li>
- <li>
- Follow the <a href="https://discordapp.com/guidelines">Discord community guidelines</a>
- </li>
- <li>
- Don't intentionally make other people uncomfortable - if someone asks you to stop discussing
- something, you should stop
- </li>
- <li>
- Be patient both with users asking questions, and the users answering them
- </li>
- <li>
- We will not help you with anything that might break a law or the terms of service of any other
- community, site, service, or otherwise - No piracy, brute-forcing, captcha circumvention,
- sneaker bots, or anything else of that nature
- </li>
- <li>
- Listen to and respect the staff members - we're here to help, but we're all human beings
- </li>
- <li>
- All discussion should be kept within the relevant channels for the subject - See the
- <a href="{{ url_for("main.about.channels") }}">channels page</a> for more information
- </li>
- <li>
- This is an English-speaking server, so please speak English to the best of your ability -
- <a href="https://translate.google.com">Google Translate</a> should be fine if you're not sure
- </li>
- <li>
- Keep all discussions safe for work - No gore, nudity, sexual soliciting, references to suicide,
- or anything else of that nature
- </li>
- <li>
- We do not allow advertisements for communities or commercial projects - Contact us directly if
- you want to discuss a partnership!
- </li>
- </ol>
-
- <h1 class="uk-article-title hover-title" id="nickname-policy">
- Nickname Policy
-
- <a href="#nickname-policy" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Keep It Simple, Stupid
- </p>
- <p>
- In order to keep things pleasant and workable for both users and staff members, we enforce the
- following requirements regarding your nickname.
- </p>
- <ol>
- <li>No blank or "invisible" names</li>
- <li>No slurs or other offensive sentiments</li>
- <li>No noisy unicode characters - for example, z̯̯͡a̧͎̺̻̝͕̠l̡͓̫̣g̹̲o̡̼̘ or byte order marks</li>
- <li>No nicknames designed to annoy other users</li>
- <li>Make sure the nickname is easy to mention using a keyboard that can only type ASCII characters</li>
- </ol>
- <p>
- Staff reserves the right to change the nickname of any user for any reason. Failure to comply with these
- requirements may result in you losing the right to change your nickname. We also reserve the right to
- discipline users with offensive usernames, regardless of the nickname they're using.
- </p>
-
- <h1 class="uk-article-title hover-title" id="infractions">
- Infractions
-
- <a href="#infractions" class="uk-text-primary" title="Permanent link to this header">
- <i class="fas fa-paragraph" data-fa-transform="shrink-8"></i>
- </a>
- </h1>
- <p class="uk-article-meta">
- Why you gotta be so rude?
- </p>
- <p>
- We have a generally no-nonsense policy when it comes to our rules. If you notice someone breaking
- them, feel free to mention or DM a staff member and we'll try to deal with it as soon as possible.
- </p>
- <p>
- The possible actions we take based on infractions can include the following:
- </p>
- <ul>
- <li>A public verbal or textual warning</li>
- <li>Forced nick changes, where appropriate</li>
- <li>A short temporary mute</li>
- <li>A long temporary mute</li>
- <li>A kick from the server</li>
- <li>A temporary ban from the server</li>
- <li>A permanent ban from the server</li>
- </ul>
- <p>
- While we do discuss more serious matters internally before handing out a punishment, simpler
- infractions are dealt with directly by individual staffers and the punishment they hand out is left
- to their own discretion.
- </p>
- </article>
- </div>
- </div>
-{% endblock %} \ No newline at end of file