On Mar 18, 3:33 pm, Edmond Kachale <edmond.kach...@baobabhealth.org> wrote: > Railers (if you allow me to you so), > > *1. Posting Right Questions* > ======================= > There are some questions that are not necessarily worthy posting on this > forum. For example, questions on how to create HTML elements like textboxes, > buttons, forms, e.t.c. in Ruby on Rails. These are HTML specific questions. > If one wants to create them using Rails helpers there are tutorials that are > dedicated to that. All in all, there are guides on how to do that on > rubyonrails.org (for example this > one:http://guides.rubyonrails.org/form_helpers.html). If one is not sure of > something in Ruby on Rails, they may search online first, before posting on > this forum. Things are happening very fast. It is very likely that most of > the "general questions" about RoR have been answered via blog posts or > various forums already. *We need to know the difference between a search > engine and a forum*. Only when there is no tutorial or blog post tackling a > particular question then we can go ahead posting it here. > > *2. Differentiating between Ruby and Ruby on Rails Questions* > ==================================================
I don't worry an awful lot about this, although I don't read the pure ruby forums that much (so in that sense I'm happy to get my dose of ruby related questions). On top of that, I'm not sure it is always clear to the person asking the question what is core ruby and what is a railsisms. To me it's a much more fuzzy line than the html & css type question. > > *3. Framing Questions and Email Titles/Subjects before Posting* > =================================================== > We need to take our time framing our questions before posting them on this > forum. Some of the questions do not make real sense at all. It becomes hard > for us to figure out what someone is looking for, and (I'm sorry to say > that) we tend to ignore them. Some of the subjects are too general like "I > need help" , "I have problems with my Rails application" or "Newbie > question". Sometimes it's even hard to work out what the question is, or it takes multiple back and forths to coax out the relevant piece of information. Treading the line between too much and too little information does require some skill. > > *4. Posting Jobs* > ============= > Let me take advantage to remind everyone that when we are posting about an > open job position or looking for a Rails developer, we are requested to > prefix email subject with [JOBS] tag. I cannot say why we need that, but > that is a request that is clearly spelled out on the forums page. There was a discussion a few years back about whether or not jobs posts should be allowed here. In the end, the compromise emerged that if they were easily identifiable (eg by having a tag in the subject) then those not interested can filter them out relatively easily. It's not stuck to very rigorously (not counting the countless job postings that have nothing to do with rails that never make it to the mailing list. Fred > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
