[Bioc-devel] Suggested edits to support site posting guide

well, Hadley usually walks people through the steps required to 1) file a
bug reproducibly or 2) learn how to do the thing in question organically,
and his universe is doing OK, so N=1 in favor of that approach.  Also a lot
of people helped me learning Perl (!) on Usenet (!!!) so yeah I'm old but
it seems like civility was once a little more common.  Bioc-devel and
support.bioconductor.com are healthy communities, I would hope that nobody
minds this being spelled out explicitly.

I love Prof Ripley and he's never been anything but nice to me, still,
r-help's reputation took a beating from his insistence on self-reliance.
Several times when I thought I understood a library or process, I'd write
up an example and discover that what I believed to be true was not, in
fact, true -- perhaps an example was cordoned off with \{dontrun} or some
such, perhaps an upstream package broke unwritten assumptions, whatever.
My point is that it can be beneficial for the answerer as for the asker,
and perhaps if one does not have time to provide a working example in an
answer, then it might be better to let another person with sufficient time
go ahead and address that question.

JMHO, since you asked "everyone else".

Best,


--t

On Mon, Apr 30, 2018 at 2:58 PM, Leonardo Collado Torres <lcollado at jhu.edu>
wrote:

Hi Mike, Lori and everyone else,

I recently saw this tweet
https://twitter.com/aprilwensel/status/989248246878035972 that links
to https://medium.com/compassionate-coding/its-time-
to-retire-rtfm-31acdfef654f#---0-162

First, I'm curious if you've read it and if you like it. Second, maybe
we could include some of it (or link to it) in the suggested changes
to the posting guide that Mike is working on.

Best,
Leo



On Fri, Apr 20, 2018 at 10:10 AM, Shepherd, Lori
<Lori.Shepherd at roswellpark.org> wrote:

May I also suggested when you are satisfied with user feedback and

alterations to create a pull request for the website repository

https://github.com/Bioconductor/bioconductor.org




Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263

Michael Love <michaelisaiahlove at gmail.com>

Sent: Thursday, April 12, 2018 11:23:35 AM
To: bioc-devel
Subject: [Bioc-devel] Suggested edits to support site posting guide

dear all,

I've edited the text from the posting guide
<http://www.bioconductor.org/help/support/posting-guide/> to update it a
bit.

For example, some of the text still referred to the mailing list
:
"Compose a new message with a new subject line".

Mostly, though, I wanted to emphasize posting all of their R code and
information about the experiment, which is often missing from support

site

posts. The self-contained example with data and code is rarely possible
because many Bioc users have large datasets that can't be shared.

Curious if this is useful or if others have suggestions. The following
link allows edits:

https://docs.google.com/document/d/1baiBUYB8E02KMbaojjoo-
tKV3Ctd9sA5lVCvwFIWquA/edit?usp=sharing

best,
Mike

        [[alternative HTML version deleted]]

information.  If you are not the intended recipient(s), or the employee or
agent responsible for the delivery of this message to the intended
recipient(s), you are hereby notified that any disclosure, copying,
distribution, or use of this email message is prohibited.  If you have
received this message in error, please notify the sender immediately by
e-mail and delete this email message from your computer. Thank you.

        [[alternative HTML version deleted]]

        [[alternative HTML version deleted]]