<div dir="ltr">Hi all,<div><br></div><div>My initial personal point of view was to use one mailing list both for users and developers. That is <a href="mailto:neuroimaging@python.org" target="_blank">neuroimaging@python.org</a> (previously nipy-devel...)</div><div>Then I saw that this list was not attracting enough questions. This is probably because we didn't promote this list enough. And maybe that </div><div>should have been the first thing to do. Which we clearly didn't do.</div><div><br></div><div>Then I thought okay the <a href="mailto:neuroimaging@python.org" target="_blank">neuroimaging@python.org</a> list is for developers and expert users and <a href="http://neurostars.org" target="_blank">neurostars.org</a><br></div><div>is for users who don't want to touch development and need feedback. </div><div><br></div><div><br></div><div>But I have to say that there are some features in neurostars which can be dangerous. One of them is that people who answer questions get</div><div>different status and reputation points. For example, the status of the person answering often says "trusted". This is misleading information.</div><div><br></div><div>I think we need to be smarter here. There are no experts. We are research projects. We want a community which does not promote <br></div><div>expertise but promotes understanding and good scientific practice. The focus of neurostars should be exactly that.</div><div><br></div><div>I see that neurostars is still in a beta and I am wondering if we can change some of its settings.</div><div><br></div><div>It is true that neurostars has attracted very quickly a relatively large audience. So, I am not sure if we should stop using it or not. But I will</div><div>suggest something different. </div><div><br></div><div>Can we continue using Neurostars with some different setup so that it promotes more understanding/discussion rather than expertise?</div><div><br></div><div>To be more clear. Here is a summary of the important problems that StackOverflow has which also Neurostars can potentially have:</div><div><br></div><div>This is from <a href="http://michael.richter.name/blogs/awhy-i-no-longer-contribute-to-stackoverflow" target="_blank">http://michael.richter.name/blogs/awhy-i-no-longer-contribute-to-stackoverflow</a> which was posted previously in this thread. Thanx for </div><div>posting this.<br></div><div><br></div><div><p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;color:rgb(0,0,0);font-family:'Lucida Grande','Segoe UI','Droid Sans',sans-serif;font-size:12.8000001907349px;line-height:19.2000007629395px;text-align:justify">The problems with StackOverflow are summarized in this list:</p><ol style="margin:15px 0px 15px 2em;padding:0px;border:0px;vertical-align:baseline;color:rgb(0,0,0);font-family:'Lucida Grande','Segoe UI','Droid Sans',sans-serif;font-size:12.8000001907349px;line-height:19.2000007629395px;text-align:justify"><li style="margin:0px 0px 0.25em;padding:0px;border:0px;vertical-align:baseline;line-height:1.5em">Poor pedagogy</li><li style="margin:0px 0px 0.25em;padding:0px;border:0px;vertical-align:baseline;line-height:1.5em">Poor reward system</li><li style="margin:0px 0px 0.25em;padding:0px;border:0px;vertical-align:baseline;line-height:1.5em">Poor community</li></ol></div><div>If we can change/block some of the functionality of neurostars maybe we can avoid those issues and build a strong community.</div><div>If not then maybe we should consider using the current mailing list.</div><div><br></div><div>I would like also to remind that we made <a href="http://nipy.org" target="_blank">nipy.org</a> to reach a much higher level of community participation. So, please don't take</div><div>this lightly. If we can improve neurostars to reach that goal we shall do it. If that is not possible with this technology then maybe </div><div>just continue using what we currently have. I mean the list. </div><div><br></div><div>So who are the stars in Neurostars? If the stars are the experts (us). Not very interesting. If the stars is everyone who helps in improving</div><div>understanding and learning without looking for credits and points then this is much more interesting. Is there a way to promote this </div><div>direction more?</div><div><br></div><div><div>Also about something else. Because neurostars has become quite popular I think it will be difficult to do what Matthew says. Forward traffic in the mailing list.</div><div>I am afraid we are past that point. Or we will have to do that in coordination for a long time. So, maybe improve what we have is the way to go.</div></div><div><br></div><div>Sorry for the long e-mail. Let me know what you think. I hope this was helpful in some way.</div><div><br></div><div>Best regards,</div><div>Eleftherios</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 2:05 PM, Michael Hanke <span dir="ltr"><<a href="mailto:michael.hanke@gmail.com" target="_blank">michael.hanke@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey,<div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Aug 25, 2015 at 7:53 PM, Matthew Brett <span dir="ltr"><<a href="mailto:matthew.brett@gmail.com" target="_blank">matthew.brett@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For the communities - it's surely reasonable to refer questions to the<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
chosen forum of the project - for example, I think I'm right in saying<br>
there's no controversy that nipype wants user questions to neurostars.<br>
I guess it's more complex to direct people who have more general<br>
neuroimaging questions.</blockquote><div><br></div></span><div>Not just that. For nipype, imagine a user sees that the package install fails. _I_ don't want</div><div>them to go to neurostars -- even if nipype wants that. I want that bug, because it is fairly clear that _I_ should deal with</div><div>it. I can do that better and quicker, if there is a single forum (or even better a bug tracker) for all these bugs</div><div>-- regardless of the actual software in question. For everything else, I prefer a pass-through of some</div><div>kind that neither burdens me, nor the user.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Michael</div><div><br></div><div>-- </div></font></span></div><span class="HOEnZb"><font color="#888888"><div><div dir="ltr"><div>Michael Hanke</div><div><a href="http://mih.voxindeserto.de" target="_blank">http://mih.voxindeserto.de</a></div><div><div><br></div></div></div></div>
</font></span></div></div></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br></div>