I do not agree with a separate beginner's list. But I do stand with moving
to stackoverflow, mainly because of the easier google search than current
mailing list. It could make it more accessible.


On Mon, Nov 25, 2013 at 4:07 AM, John Sorkin <JSorkin@grecc.umaryland.edu>wrote:

> Mailing list vs. stack overflow, I have no opinion, but
> beginners list NO! I was a beginner at one time and the
> mailing list worked just fine. I see no reason to divide our
> efforts across two lists (be they mailing lists or stack overflow).
> John
>
>
> John David Sorkin M.D., Ph.D.
> Professor of Medicine
> Chief, Biostatistics and Informatics
> University of Maryland School of Medicine Division of Gerontology and
> Geriatric Medicine
> Baltimore VA Medical Center
> 10 North Greene Street
> GRECC (BT/18/GR)
> Baltimore, MD 21201-1524
> (Phone) 410-605-7119
> (Fax) 410-605-7913 (Please call phone number above prior to faxing)
> >>> memilanuk <memilanuk@gmail.com> 11/24/2013 7:30 PM >>>
> On 11/24/2013 12:04 PM, Rich Shepard wrote:
> > On Sun, 24 Nov 2013, Yihui Xie wrote:
> >
> >> Mailing lists are good for a smaller group of people, and especially
> >> good when more focused on discussions on development (including bug
> >> reports). The better place for questions is a web forum.
> >
> >    I disagree. Mail lists push messages to subscribers while web fora
> > require
> > one to use a browser, log in, then pull messages. Not nearly as
> convenient.
> >
> > Rich
> >
>
> With the StackOverflow model, you can either view the list of posts
> related to a specific tag via RSS, or subscribe for email notification
> of new updates on that topic.
>
> Add in the added bonus of the ability to moderate and/or cull spam and
> redundant questions, etc. and the targeted focus of a SO-type forum
> increases dramatically IMHO.
>
> ______________________________________________
> R-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>
>
> Confidentiality Statement:
> This email message, including any attachments, is for ...{{dropped:18}}

