[Neuroimaging] When to use neurostars, and when not to

[Michael Hanke]

Hi,

please allow me to hijack some of this thread and ask for feedback on how
to guide users to find help. For the upcoming relaunch of neuro.debian.net
we have drafted this (example for nibabel):

http://neurodebian.ovgu.de/pkgs/python-nibabel.html

If you click the "help" button you can see how we envision this guidance.

Here is a more featureful example:

http://neurodebian.ovgu.de/pkgs/fsl-core.html

You can see that neurostars will be recommended for most cases. I'd be glad
to get your feedback and any suggestions for improvements.

Thanks,

Michael



On Tue, Aug 25, 2015 at 7:03 PM, vanessa sochat <vsochat at stanford.edu>
wrote:

> Awesome thanks Satra!
>
> On Tue, Aug 25, 2015 at 9:46 AM, Satrajit Ghosh <satra at mit.edu> wrote:
>
>> hi folks,
>>
>> issue posted here: https://github.com/ialbert/biostar-central/issues/389
>>
>> neurostars is based off biostars (shares the same codebase, with a
>> different config). biostars is a complete opensource django project that
>> anyone can contribute to. we do have plans for federation that will come
>> online in the next year or two.
>>
>> cheers,
>>
>> satra
>>
>> On Tue, Aug 25, 2015 at 12:37 PM, vanessa sochat <vsochat at stanford.edu>
>> wrote:
>>
>>> The ideal for questions / issues related to packages is github. However
>>> neurostars would have a much larger group. I'm not familiar with how
>>> neurostars is set up (django?) but why not have (akin to slack) an app
>>> integration for particular github repos and neurostars? Aka, when someone
>>> posts to the repo in some fashion, it is also shared on neurostars, and
>>> possibly directs to the repo.
>>>
>>> On Tue, Aug 25, 2015 at 9:29 AM, John Pellman <pellman.john at gmail.com>
>>> wrote:
>>>
>>>> While I understand an aversion to reputation-based systems (this
>>>> article
>>>> <http://michael.richter.name/blogs/awhy-i-no-longer-contribute-to-stackoverflow>
>>>> comes to mind) I would note that it is quite a bit more difficult to keep
>>>> track of questions when they are divided between two discussion fora (more
>>>> if you count the AFNI, FSL, and SPM mailing lists), and I can't help but
>>>> wonder if some amount of consolidation while preserving individual
>>>> interests would be beneficial to the neuroimaging community.
>>>>
>>>> 2015-08-25 11:42 GMT-04:00 Bertrand Thirion <bertrand.thirion at inria.fr>
>>>> :
>>>>
>>>>>
>>>>>
>>>>> ----- Mail original -----
>>>>> > De: "Matthew Brett" <matthew.brett at gmail.com>
>>>>> > À: "neuroimaging" <neuroimaging at python.org>
>>>>> > Envoyé: Mardi 25 Août 2015 17:40:39
>>>>> > Objet: [Neuroimaging] When to use neurostars, and when not to
>>>>> >
>>>>> > Hi,
>>>>> >
>>>>> > This just came up from a discussion on a nipy pull request:
>>>>> >
>>>>> > https://github.com/nipy/nipy/pull/340
>>>>> >
>>>>> > I thought it was worth clarifying what my position is.  I don't use
>>>>> > neurostars, so if you want advice on using or developing nibabel,
>>>>> then
>>>>> > this mailing list is the right place to go. rather than neurostars.
>>>>> >
>>>>> > This is probably also true for the nipy project - in that I can help
>>>>> > on this list but you probably won't get my attention on neurostars.
>>>>> > The other two main authors of nipy are Alexis and Bertrand - maybe
>>>>> > they hang out more on neurostars?  Can y'all clarify?
>>>>> >
>>>>>
>>>>> Hi Matthew,
>>>>>
>>>>> No, I don't look at Neurostars in general.
>>>>> Best,
>>>>>
>>>>> Bertrand
>>>>>
>>>>> > I'm actually not sure what the policy is for dipy - Eleftherios - did
>>>>> > you decide on this?
>>>>> >
>>>>> > To explain a bit further, I much prefer unified user- and developer-
>>>>> > discussions and therefore mailing lists, because I think it's
>>>>> > important to keep a fluid boundary between users and developers.   I
>>>>> > also have an instinctive aversion to reputation-based systems,
>>>>> >
>>>>> > Cheers,
>>>>> >
>>>>> > Matthew
>>>>> > _______________________________________________
>>>>> > Neuroimaging mailing list
>>>>> > Neuroimaging at python.org
>>>>> > https://mail.python.org/mailman/listinfo/neuroimaging
>>>>> >
>>>>> _______________________________________________
>>>>> Neuroimaging mailing list
>>>>> Neuroimaging at python.org
>>>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Neuroimaging mailing list
>>>> Neuroimaging at python.org
>>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>>
>>>>
>>>
>>>
>>> --
>>> Vanessa Villamia Sochat
>>> Stanford University
>>> (603) 321-0676
>>>
>>> _______________________________________________
>>> Neuroimaging mailing list
>>> Neuroimaging at python.org
>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>
>>>
>>
>> _______________________________________________
>> Neuroimaging mailing list
>> Neuroimaging at python.org
>> https://mail.python.org/mailman/listinfo/neuroimaging
>>
>>
>
>
> --
> Vanessa Villamia Sochat
> Stanford University
> (603) 321-0676
>
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
>


-- 
Michael Hanke
http://mih.voxindeserto.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150825/24b98c95/attachment.html>