[Neuroimaging] Discourse category for DICOM discussions

Matthew Brett matthew.brett at gmail.com
Sat Jul 10 12:56:01 EDT 2021


On Sat, Jul 10, 2021 at 5:41 PM Satrajit Ghosh <satra at mit.edu> wrote:
> hi matthew,
> i don't have a good answer to that other than it seems to have worked out ok across the various python and other software tools discussed on neurostars. perhaps the folks here could decide or we go with trying out neurostars and seeing if we really run into those issues.
> the other option for more specificity is to turn on discussions on the github repo itself. that keeps it close to the code. here is an example of trying to balance code, proximity, outreach, and community: https://github.com/dandi/helpdesk/issues/new/choose

Ah - I think that doesn't match our problem here - because we're
thinking about how to coordinate development across at least three
different projects, and therefore, repositories.

On reflection, I'd prefer to stick with the nipy.discourse.group DICOM
category, to have one place devoted to those discussions.   If it
looks like the discussions are getting more general than developing
DICOM conversion and APIs across the Python packages, then we can move
to Neurostars.

I don't see any need for this to compete with Neurostars - this is a
very specific developer discussion forum (to which, of course, anyone
is welcome), rather than the more general focus of Neurostars.

So - as you were - please do join us over at:




More information about the Neuroimaging mailing list