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

2018-05-01 Thread Hervé Pagès 

Thanks Leo for the link to April Wensel's blog.

I wonder if she is 100% serious with her rant about the Grandma
thing but I found it pretty funny!

H.


On 04/30/2018 01:16 PM, Michael Love wrote:

hi Leo,

We currently have "Rudeness and ad hominem comments are not
acceptable" in the section on replying. This is nice and simple.

I think most of the people reading the guide will be first time
question-askers, but I'm glad we have the above bulletpoint so we can
say someone was breaking the site guidelines if they were rude.

I don't think we need to link to the anti-RTFM piece, because I don't
think I've ever seen that phrase used on Bioc support (or if I saw it,
it was a while ago and I forgot about it). If you want to incorporate
any of the positive suggestions from there to the section on replying
go for it.

Anyone should feel free to keep editing the Gdoc. I'll wait a week or
so and then do a PR to the site.

best,
Mike


On Mon, Apr 30, 2018 at 3:30 PM, Tim Triche, Jr. <tim.tri...@gmail.com> wrote:

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 <lcoll...@jhu.edu>
wrote:


Hi Mike, Lori and everyone else,

I recently saw this tweet
https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_aprilwensel_status_989248246878035972=DwICAg=eRAMFD45gAfqt84VtBcfhQ=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA=S5D7QD263pcF-j96zEV-sY0v_ulBJ_ZpI9JMXcbAEOI=-p8hKcFjc_9ArMb2xpIHzDt9ZrOm5Ojtf4XrEmnC5tw=
 that links
to 
https://urldefense.proofpoint.com/v2/url?u=https-3A__medium.com_compassionate-2Dcoding_its-2Dtime-2D=DwICAg=eRAMFD45gAfqt84VtBcfhQ=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA=S5D7QD263pcF-j96zEV-sY0v_ulBJ_ZpI9JMXcbAEOI=tqcYe_NWBZlekYGeTonoXkxgnYpjk14j_DFWw0yVcRk=
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.sheph...@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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Bioconductor_bioconductor.org=DwICAg=eRAMFD45gAfqt84VtBcfhQ=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA=S5D7QD263pcF-j96zEV-sY0v_ulBJ_ZpI9JMXcbAEOI=lDZRqONtpk4hTnHzIpBY0FHTUu2Y8-fCZ9-kechwRKI=




Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263


From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of

Michael Love <michaelisaiahl...@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
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bioconductor.org_help_support_posting-2Dguide_=DwICAg=eRAMFD45gAfqt84VtBcfhQ=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA=S5D7QD263pcF-j96zEV-sY0v_ulBJ_ZpI9JMXcbAEOI=4NMQpCXfazPlsIzz4y0aJDeOyaHgH83K6rGiirye0Ps=>
 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 foll

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

2018-04-30 Thread Michael Love 
hi Leo,

We currently have "Rudeness and ad hominem comments are not
acceptable" in the section on replying. This is nice and simple.

I think most of the people reading the guide will be first time
question-askers, but I'm glad we have the above bulletpoint so we can
say someone was breaking the site guidelines if they were rude.

I don't think we need to link to the anti-RTFM piece, because I don't
think I've ever seen that phrase used on Bioc support (or if I saw it,
it was a while ago and I forgot about it). If you want to incorporate
any of the positive suggestions from there to the section on replying
go for it.

Anyone should feel free to keep editing the Gdoc. I'll wait a week or
so and then do a PR to the site.

best,
Mike


On Mon, Apr 30, 2018 at 3:30 PM, Tim Triche, Jr. <tim.tri...@gmail.com> wrote:
> 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 <lcoll...@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.sheph...@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
>> >
>> > 
>> > From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of
>> Michael Love <michaelisaiahl...@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/e

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

2018-04-30 Thread Tim Triche, Jr. 
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 <lcoll...@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.sheph...@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
> >
> > ________
> > From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of
> Michael Love <michaelisaiahl...@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]]
> >
> > ___
> > Bioc-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/bioc-devel
> >
> >
> > This email message may contain legally privileged and/or confidential
> 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]]
> >
> > ___
> > Bioc-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
> ___
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>

[[alternative HTML version deleted]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

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

2018-04-30 Thread Leonardo Collado Torres 
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.sheph...@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
>
> 
> From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of Michael Love 
> <michaelisaiahl...@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]]
>
> ___
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
>
> This email message may contain legally privileged and/or confidential 
> 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]]
>
> ___
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

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

2018-04-20 Thread Shepherd, Lori 
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


From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of Michael Love 
<michaelisaiahl...@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]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


This email message may contain legally privileged and/or confidential 
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]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

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

2018-04-12 Thread Leonardo Collado Torres 
Hi Mike,

I just added a few comments to your google doc. Thanks for doing this!

Best,
Leo

On Thu, Apr 12, 2018 at 11:23 AM, Michael Love
 wrote:
>
>
> dear all,
>
> I've edited the text from the 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]]
>
> ___
> Bioc-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

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

2018-04-12 Thread Michael Love 
dear all,

I've edited the text from the 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]]

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel