[Neuroimaging] Nibabel future plans and roadmaps (Was Re: Chris Markiewicz taking over as lead maintainer for nibabel)

[Christopher Markiewicz]

Hi Eleftherios,

As far as I'm concerned, any formats that people want to submit are fair game. The only new image format currently in the pipeline is Philips XML/REC (#683). And I expect that in a couple months we'll see some more activity on the spatial transform data model/file formats (#656), as the BIDS transforms meeting is happening in March.

Personally, I would like to make some progress on some API improvements for serializing images and getting zooms in consistent units across image types.

On this topic, I think it would be good to establish some roadmaps and timelines. Much of the last couple years has been bug fixes, and some deprecations are due to be effected. A predictable release schedule should make planning easier. With the Python 2 sunset in 11 months, I think we should have an explicit plan as a community of how nibabel should be oriented to it.

I don't know if people want to hash these things out here or on GitHub, but I'm happy to do a developer hangout if some real-time responses are desired. If you're interested in participating in this planning, please let me know.

Chris

________________________________
From: Neuroimaging <neuroimaging-bounces+markiewicz=stanford.edu at python.org> on behalf of Eleftherios Garyfallidis <elef at indiana.edu>
Sent: Friday, February 1, 2019 10:11 AM
To: Neuroimaging analysis in Python
Subject: Re: [Neuroimaging] Chris Markiewicz taking over as lead maintainer for nibabel

Congrats Chris,

It would be nice to know what are the next plans for nibabel. Which formats are going to be supported or not etc.

Best,
Eleftherios

On Thu, Jan 31, 2019 at 9:43 PM Christopher Markiewicz <markiewicz at stanford.edu<mailto:markiewicz at stanford.edu>> wrote:

Thanks, Matthew, for your many years of guidance and support of nibabel and its contributors. I credit my engagement with nibabel in particular with teaching me how to write and maintain open source software, and I can only say thank you. It really is the bedrock of the community, and I hope to keep it in worthy shape.

Chris


________________________________
From: Neuroimaging <neuroimaging-bounces+markiewicz=stanford.edu at python.org<mailto:stanford.edu at python.org>> on behalf of Matthew Brett <matthew.brett at gmail.com<mailto:matthew.brett at gmail.com>>
Sent: Thursday, January 31, 2019 12:55 PM
To: neuroimaging
Subject: [Neuroimaging] Chris Markiewicz taking over as lead maintainer for nibabel

Hi,

Just so y'all know, Chris has kindly agreed to take over the role of
lead maintainer for nibabel.

Well, I should say, he had kindly agreed to take on the title, because
the observant among you will know he has effectively been doing that
job for some time.

We nibabelers don't have any real governance docs, but, as my last act
as lead maintainer, I'm going propose the following:

* the lead maintainer has veto power over commits to nibabel
* they should use it only very rarely, when all possible compromises
have been explored.

If anyone disagrees with this little formalization, please do say.

Thanks very much, as ever, to Chris, and good luck with the task, that
you are already doing...

Cheers,

Matthew
_______________________________________________
Neuroimaging mailing list
Neuroimaging at python.org<mailto:Neuroimaging at python.org>
https://mail.python.org/mailman/listinfo/neuroimaging
_______________________________________________
Neuroimaging mailing list
Neuroimaging at python.org<mailto:Neuroimaging at python.org>
https://mail.python.org/mailman/listinfo/neuroimaging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20190201/64d1302f/attachment.html>