discussion: WDYT about moving workflows out of nipype

[satra]

1. moving all workflows out of nipype
2. creating a github organization for workflows with repos corresponding to specific workflows/apps (since each workflow can have their own dependencies, and pin their own version of nipype).
3. creating templates for allowing X-ificiation for workflows where X = BIDS, NIDM, CWL, Boutiques, etc.,.
4. generate docker/singularity apps

we are slowly running into versioning considerations as people start building more extensively and maintaining workflows is hard and perhaps should be distributed to the community that takes care of them (e.g., niworkflows).

[chrisgorgo]

+1 We could try to model http://nf-co.re/

[effigies]

Pinning independent nipypes seems potentially problematic, if one wants to mix uses.

But I'm very much pro-splitting out workflows. Correctness of a workflow is very different from that of the core or even the interfaces.

[effigies]

I wonder if splitting out interface sets would be good. We talked about individual interfaces a while back, similar to how Node has individual functions packaged. But maybe packages like nipype-interfaces-fsl, nipype-interfaces-spm, etc. would be a more sensible unit.

But workflows are probably easier to separate at this point, so getting that experience behind us would be a good pre-condition to thinking more seriously about interfaces.

[oesteban]

+1

[satra]

@effigies - you mean a new npm :)

[satra]

new org created: https://github.com/niflows

@yarikoptic @tyarkoni @adelavega - in case you were wondering.