Repl Talk Rules and Guidelines [README]
h
mat1 (2756)

Rules

The Repl.it community is a place for users to share code, ask questions, and discuss coding-related subjects. We're committed to making it a fun and cool space for both aspiring and experienced programmers. To that end, we need to lay down some ground rules:


Quality posts

When sharing a post do your best to describe what you are sharing and why it's interesting. Spam, irrelevant, inappropriate, or posts that lack contexts will be deleted. Don't post homework assignments, we want to see your creativity!

Adding images, screenshots, stack traces, and of course, repls, typically make posts better.

Asking good questions

Attributes of a bad question:
  • Vague; doesn't fully describe the issue.
  • Does not include a link to a repl or does include their code using a codeblock.
  • Simply asks "how would I do this?" with no prior effort or investigation.
  • Not open to constructive criticism. If you're asking for help with code, you should expect some level of critique.
Attributes of a good question:
  • Links to a repl or codeblock with the faulty code (if applicable).
  • Be descriptive: explain what you've tried, what language you're using, and anything else that might be relevant.
  • Say what you want/expect the program to do.
  • It's unlikely that someone will fix your code for you, so don't ask for that. Instead, focus on learning.

Sharing interesting repls and apps

  • What the repl does: this should be at least 50 characters. For example saying "It's a pizza game" isn't very descriptive. Instead say "It's a game that simulates making pizza. The goal of the game is to sell 100 pizzas in a single day."
  • If it's not straightforward describe how to use/play your repl/game.
  • Images, screenshots, and gifs might make your post more exciting and interesting.

Writing good tutorials

  • Good tutorials are typically detailed and expect little prior knowledge from readers. Try to think from the point-of-view of the reader: What might be confusing or what questions they might have?
  • Images, screenshots, and gifs are proven to make posts more engaging.
  • Examples are important so that readers can follow along.
  • Be ready to provide support: Readers might ask questions or give you feedback. Engaging with your users is a great way to become a better writer.

Don't plagiarize

Don't pretend that you made something you didn't make. When people find out they'll lose respect for your work. Instead, if you forked someone's repl or based your code on an existing project then please give credit to the original author.

Learn more about plagiarism here.

Here is the section from the Repl.it ToS on plagiarism:

We respect the intellectual property rights of others. It is our policy to respond to any claim that User Content posted on the Service infringes on the copyright or other intellectual property rights ("Infringement") of any person or entity.

This means at the very least we'll take plagiarized posts and repls down and if this persists we will take action against the user.

Use the correct category

To make it easier to navigate Talk is made up of different "boards" for differnt categories. When posting, make sure to use the correct one:

Ask

This category is for asking questions. Typically coding questions, but feel free to use this for coding-related discussions. Check out @Mosrod's guide on asking good questions.

Be sure not to fall into the XY problem when asking questions. Don't ask how to get the last 3 letters of a filename, when you really want the file's extension.

Share

This category is for sharing projects and repls.

Learn

This category is for tutorials and guides. This is not for asking questions, though you can always leave questions in the comments if something is unclear.

Bugs

This is where bug reporting belongs and where the Repl.it team will see them.

Feedback

This is where feedback and suggestions belong and where the Repl.it team will see them.


How to be helpful

Be constructive

If you're going to give critisism, make it constructive. This means that you should tell people how to fix something rather than just telling them they're doing something wrong.

Do not spoon-feed

Don't flat out give someone the script for their question. If they are asking how to do something, suggest steps they could take to accomplish their goal. Focus on teaching.

Be patient

What's obvious to you might be new to someone who's new to programming. Never talk down. Remember yourself when you were just a newbie trying to learn and treat the asker how you would've liked to be treated.

Answer the question

If you want to contribute to a post in Ask, besure it's actually helpful. Do not say things like "Why are you using x? You should use y instead. Don't comment that you don't know the answer to an Ask question, you can just ignore it if that's the case.

Be friendly

Be kind to your fellow replers. Never insult people or their work. We have zero tolerance towards bullying.

Keep it SFW

Keep it clean, or SFW (safe for work). If you wouldn't show it to a 10 year old or your grandma, don't post it. This includes swearing, it is not allowed.

Zero tolerance for hate speech

Any abusive or threatening writing that expresses prejudice against a particular group, especially on the basis of race, religion, or sexual orientation will result in an immediate ban.

Other rules

Don't advertise

Don't make posts or comments advertising non-programming creations or sites.

Don't create more accounts for cycles

Do not make alternate accounts for voting on your own posts or comments.

Common sense

Common sense applies to all these rules. There is no "bending the rules," don't try and find an flaw in the wording and use it to your advantage. Basically, don't find loopholes and exploit them.

Other languages

For now, we're not supporting non-English languages. This is due to the fact that majority of our users speak only English, and it's hard to moderate posts in other languages.

Appealing

If you believe you were unfairly banned, submit an appeal at [email protected]

These rules are ever-evolving, and the last update to them was on 12/13/2019.

You are viewing a single comment. View All
Scoder12 (349)

Yay glad this finally came together! (I helped)

AllAwesome497 (247)

@Scoder12 yeah. Bummer i didn't have the time to work on it after i initially wrote it.

Scoder12 (349)

@AllAwesome497 ok sorry you're right I edited like 3 words

mat1 (2756)

@Scoder12 @AllAwesome497 yall can still edit the main repl and ill update the post

ChezCoder (58)

lol, flexers to flex to the community that they helped edited this post...