pip pkg

[casperdcl]

Enables pip install

[casperdcl]

would prefer:

Suggested change

	name=pydcm2niix
	name=dcm2niix

but was getting errors:

The name 'dcm2niix' isn't allowed. See https://pypi.org/help/#project-name for more information.

[casperdcl]

@jstutters are you OK with this pull request? I notice you have a repository named pydcm2niix.

Interesting. Ideally this PR should use simply dcm2niix anyway. I can raise a request following https://www.python.org/dev/peps/pep-0541/#how-to-request-a-name-transfer (i.e. https://github.com/pypa/pypi-support/issues/new?labels=PEP+541&template=pep541-request.yml&title=PEP+541+Request%3A+dcm2niix) if you want @neurolabusc?

[neurolabusc]

@jstutters are you OK with this pull request? I notice you have a repository named pydcm2niix.

[jstutters]

Thanks for checking. No objection. If I do ever get any further with the work I had in mind for my project it would be better contributed as a follow-up to this PR anyway.

[casperdcl]

Thanks @jstutters.

@neurolabusc what about my suggestion of filing a request for dcm2niix though? Seems to me to be a better solution.

[neurolabusc]

@casperdcl I think it would be ideal if the pip could install the latest stable release of dcm2niix, and the package name dcm2niix sounds reasonable. I am not familiar with pip package management, and am unsure how to proceed. Do I have to request a change, or do you instigate this to have the name associated with this github repository?

[casperdcl]

@neurolabusc at least one of us needs an account with PyPI. I maintain a lot of PyPI packages so I can put in the request and do general maintenance legwork (making sure releases are in sync etc) if you're happy - let me know :)

If so, at any point in future I can also add maintainers to the PyPI package.

[neurolabusc]

@casperdcl thanks for volunteering to take on the role of dcm2niix pip install maintainer. Please proceed. Tell me if there is anything else I need to do. If at some future stage you feel you can no longer fill this role, please let the community know. My recent work with Debian maintainer @yarikoptic has allowed me to recognize how much implicit knowledge and skill is required to support packages.

[neurolabusc]

1. I am going to close this pull request. Please generate a new one when you are ready.
2. Please make all pull requests to the development branch. The master branch is the current stable release. Twice a year (spring, autumn) advanced users who have access to a lot of edge case clinical data that can not be shared are asked to validate the development branch, and once it is vetted it is released as the next stable release.