Skip to content

Instantly share code, notes, and snippets.

@radar
Last active May 13, 2023 04:42
  • Star 22 You must be signed in to star a gist
  • Fork 4 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save radar/996779 to your computer and use it in GitHub Desktop.

Welcome to #rubyonrails

Please behave in a polite, considerate and inclusive manner in the channel at all times. People volunteer their time in the channel to help people like you with your Rails problems and some respect (in both directions) will go an extremely long way.

These rules are in place so that you can get the quickest and best support from #rubyonrails.

Rule #0: Show rather than tell. Explaining your problem with code, stacktraces or errors is always preferred to explaining it with just text. Show us what's happening, rather than telling us.

  1. Do your research before hand. Your question may be answerable with a quick Google search or by simply experimenting. If you're using a method in Rails, look it up in the API Docs or in the Official Guides.
  2. If you've tried Googling, explain what terms you've tried to use so people can better help you.
  3. Clearly explain what is happening and create a Gist (http://gist.github.com), (with neat formatting, so that people can read it easily) or Hastebin (http://hastebin.com) of the code that is causing the problem you are encountering, as well as any useful output like stacktraces.
    1. If you're using an older version of Ruby or Rails, please tell us.
    2. A "Full Trace" as opposed to the default "Application Trace" is preferred.
    3. NO FAKE CODE. If you're under an NDA, we cannot help you with your problem. Go hire a consultant.
  4. Do not use any service that is not Pastie or Gist to post code. Pastebin, for example has a tiny font and it has ads on it which cause the page to load slowly. Other paste services generally look like crap.
  5. Saying that something "doesn't work" is completely useless to the people who are trying to help you. Please show all available information you have that indicates to you that something doesn't work. This means all the code you can think of being relevant, as well as any logs.
  6. Remember that using English is preferable, as the majority of people in the channel speak it. Asking in other languages may give you a response, but English is best.
  7. Anything more than 2 lines goes in a Gist (http://gist.github.com) or a Pastie (http://pastie.org). Spamming the channel with walls of text is not welcome.
  8. Treat people in a considerate manner, as they are volunteering their time to help you. If you're helping, do so in a kind and considerate manner; you were a newbie once too. If you're being annoying or rude you may be muted by one of the channel ops.
  9. Do not use excessive punctuation. This includes question marks (?), exclamation marks (!) and ellipsis (...).
  10. Do not beg / plead with people to help you. This includes asking questions like "Any ideas?" after posting your original question.
  11. Do not repeat your question every 5 minutes expecting somebody to answer it. If you do not get a reply after the first time perhaps posting your question on StackOverflow (http://stackoverflow.com) would help you. Linking to the question in the channel after you've posted it is OK.
  12. Do not PM members of the channel without first asking if that is OK.
  13. If you're going to tell someone to "Just google it" or "RTFM", tell them what terms to use on Google exactly, or link them to the place in the documentation.
  14. We're not all guys here - while you probably don't meant to be exclusive, not everybody feels that way. Maybe consider using "folks", "y'all" or "everyone" instead?

What happens when you break the rules

  1. An op will ask you to follow the rules, and link you to the specific rule.
  2. If you fail to follow the rules, you will be asked again to follow the rules.
  3. If you still fail to follow the rules, the op will give you another warning.
  4. After that warning, failure to follow the rules will result in a mute of 15 minutes.
  5. After that warning, failure to follow the rules will result in a mute of 1 hour.
  6. After that warning, failure to follow the rules will result in a mute of 1 day.
  7. After that warning, failure to follow the rules will result in a mute of 1 week.
@Spaceghost
Copy link

Good gist @radar,
well done.

@bsodmike
Copy link

bsodmike commented Feb 7, 2012

Do not use Pastie either. Got into a potentially embarrassing discussion about strippers when I mentioned 'pastie' to a colleague, in earshot of the entire IT floor.

@shahidbscs
Copy link

great

@appwebtech
Copy link

Great, brilliant!

@vovs03
Copy link

vovs03 commented Jan 4, 2017

Ok. thanks. It's really human's rules for all.

@mixflame
Copy link

its a good rules 👍

@c3aus3scu
Copy link

Perfect !

@Querens
Copy link

Querens commented Oct 29, 2020

I've been banned immediately after sending like 10 messages in a row. No warnings or anything like in "What happens when you break the rules" from 1 to 3

@tpo
Copy link

tpo commented Mar 22, 2021

@Querens

I've been banned immediately after sending like 10 messages in a row. No warnings or anything like in "What happens when you break the rules" from 1 to 3

That might be due to you breaking Freenode's rules and not those of the #RubyOnRails channel. Various IRC hosting serices dislike "flooding" and they might have taken your 10 messages in a row for flooding. So it might have been Freenode, that has banned you...

@dannypage
Copy link

dannypage commented Jun 14, 2021

Freenode seems like it is in the process of a very contentious ownership change that is resulting in many channels being banned, and it seems like the Rails channel itself generally pretty quiet. Is there any thought to moving to Libera.Chat or another service?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment