RE: [R] draft of posting guide

2003-12-26 Thread Thomas Lumley
Rather than a separate beginners' mailing list or a posting guide, perhaps what we need is a separate mailing list for discussing posting style? -thomas __ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-help

RE: [R] draft of posting guide

2003-12-24 Thread Andrew C. Ward
With respect to 'tone' and 'friendliness', perhaps all that is meant or needed is that people be polite and respectful. There is never any need for being rude, either from the asker of questions or from the answerer. I shake my head as often at rude answers as I do at ill-considered questions.

RE: [R] draft of posting guide

2003-12-23 Thread Pascal . Niklaus
Having followed the discussion about this posting guide, I'd like to add a few comments. While I think that the *content* is fully appropriate, I am not sure whether the *form* is the appropriate, for the following reason: - The folks posting questions like I've installed R two minutes ago,

RE: [R] draft of posting guide

2003-12-23 Thread Tony Plate
I do share Eryk Wolski's and Pascal Nicklaus' concerns that my revision of the posting guide is somewhat unfriendly and negative. My problem here was to keep it to a reasonable length, which meant eliminating sentences whose function was mainly to be positive and friendly. Pascal put it

Re: [R] draft of posting guide. Sorry.

2003-12-23 Thread Patrick Connolly
On Tue, 23-Dec-2003 at 05:31AM +0100, Eryk Wolski wrote: [] | I cooled down now and therefore give me a chance to explain why | that user guide scares me. A few comments: | As I said, the guide had given me the feeling that someone wants to | censor me. You mean you reacted in a way

Re: [R] draft of posting guide

2003-12-23 Thread Patrick Burns
I think the idea of answering simple questions if it hasn't been answered after 4 * runif(1) hours is a brilliant idea (well done Tony -- I'm jealous). However, a slight tweak would be even better. It should be number of years you've used S times runif(1) hours. This encourages more people to

Re: [R] draft of posting guide

2003-12-22 Thread Rolf Turner
This is in response to Gabor Grothendieck's commentary on Tony Plate's draft guidelines for question-askers, which was posted a couple of days ago. I disagree, from mildly to vehemently with just about everything in Grothendieck's posting. E.g. the ``tone'' of the draft should not be

Re: [R] draft of posting guide

2003-12-22 Thread Spencer Graves
I don't study carefully every piece of available documentation for everything (anything?) I do. A major challenge is how to provide a guide that will get used and will in the process improve the quality of questions and answers. Best Wishes, spencer graves Rolf Turner wrote:

Re: [R] draft of posting guide

2003-12-22 Thread Peter Flom
How about some sort of happy medium? e.g., in the posting guide include something like 'The people who wrote R, and the people who answers questions on R-help, are volunteers. R software is the product of thousands of hours of time by many highly trained and highly intelligent people. Please

Re: [R] draft of posting guide

2003-12-22 Thread Wolski
Hi! The guide are in my opinion much to long. If someone posts a question to the mailing list its because he likes to get a answer (fast?). The Introduction proposed by Peter Flom and the Homework before posting section will do it in my opinion. The part: Homework before posting a question.

Re: [R] draft of posting guide

2003-12-22 Thread Frank E Harrell Jr
On Mon, 22 Dec 2003 20:32:15 +0100 Wolski [EMAIL PROTECTED] wrote: Hi! The guide are in my opinion much to long. If someone posts a question to the mailing list its because he likes to get a answer (fast?). The Introduction proposed by Peter Flom and the Homework before posting section

RE: [R] draft of posting guide

2003-12-22 Thread Mulholland, Tom
I think there will always be disagreement when commenting about the appropriateness of social behaviour. So I think we will do well to understand the purpose of any proposed posting guide. It is not clear to me where the list is going with regards to this topic. If the aim is to produce a

Re: [R] draft of posting guide. Sorry.

2003-12-22 Thread Eryk Wolski
Hi! Sorry. Please take my last mail to the account that it was monday and I had two hard birthday party's during the weekend. Probably all this caused the problem to express that the style of the mailing list guide shocked me. I asked this morning such a stupid(if you know the answer) question.

Re: [R] draft of posting guide. Sorry.

2003-12-22 Thread A.J. Rossini
A few comments... Eryk Wolski [EMAIL PROTECTED] writes: As I said, the guide had given me the feeling that someone wants to censor me. Especially the first section of the Posting Guide: How to ask good questions that prompt useful answers does this. The guide starts with talking mainly

Re: Re: [R] draft of posting guide. Sorry.

2003-12-22 Thread Tim Churches
A.J. Rossini [EMAIL PROTECTED] wrote: However, the amount (and quality) of (freely-available, at least for the cost of download, which might not be free) documentation for R is simply incredible. The closest that I've seen, for freely available languages, is Python, for actual quality of

Re: [R] draft of posting guide

2003-12-20 Thread Peter Dalgaard
Tony Plate [EMAIL PROTECTED] writes: h3Common posting mistakes/h3 Doing any of the following may result in you getting a response that you may find rude or insulting. (However, such a response may be justified in the eyes of some because you have wasted people's time or unjustly insulted

RE: [R] draft of posting guide

2003-12-20 Thread Gabor Grothendieck
proposals and discussions on this on their lists with little counterpart on R's. Date: Fri, 19 Dec 2003 22:55:53 -0700 From: Tony Plate [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [R] draft of posting guide Here is a first draft of a guide for posters to r-help and r-devel

[R] draft of posting guide

2003-12-19 Thread Tony Plate
Here is a first draft of a guide for posters to r-help and r-devel. Suggestions on how to improve any aspect of it are most welcome. Suggestions on ways to make it more concise are especially welcome. Comments on which parts you like or don't like are welcome. Rather than clutter up R-help