This seems like a great idea to me.  There's one thing that I'm really curious about: can we use grant money to contribute to the yt project through this mechanism?  Essentially my entire research group now depends on yt for analysis and visualization of our simulations, and I know that's now true for a lot of people.  I really want to directly support core infrastructure development, and would be happy to write line-items into all of my grants (in the way that one would ask for grant money for a laptop for a grad student, HPC buy-in, or an outreach assessment consultant) to provide some recurring funding to the yt project.  This would both directly help the project by contributing to salaries, workshops, etc., and indirectly help by communicating to federal agencies that this is an important and widely valued endeavor.  But, I have no idea if people have used grant money in this way, or if it is even allowable under NSF/NASA/DOE regulations.  Matt, do you have any sense of this? 


On Thu, Jan 28, 2016 at 11:26 AM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi everyone,

The NumFOCUS organization is a 501(c)3 dedicated to both open source scientific software and computational science education ( numfocus.org ).  I have recently been named to their board of directors.

NumFOCUS supports many projects familiar to us here, including NumPy, Matplotlib, Jupyter, Astropy, and Sympy, as well as rOpenSci, Data Carpentry, Software Carpentry and Julia.

After talking this over with Britton, I would like to propose that we join NumFOCUS through a comprehensive Fiscal Sponsorship Agreement.  This process is outlined here:


Organizations such as NumPy and rOpenSci have detailed their reasons for participating in this program here:


Primarily, I think that this would help with our ability to exist independently of a single investigator; grants for programs such as workshops, project infrastructure, and so on can be managed by NumFOCUS (which has low overhead) and can be affiliated with the project.

I think this is something that warrants discussion, and perhaps should be talked over in person during a team meeting, but I believe that this would be a strong step forward for us as a project and a community.


yt-dev mailing list