Hey Nathan, Thanks for everything to that you have done for yt and for the broader PyData community! I hope I'll still get to see you around! Be Well Anthony On Thu, Feb 28, 2019, 15:27 Nathan Goldbaum wrote:

Hi all,

I'd like to publicly announce that I will be leaving my current position at NCSA at the beginning of May and starting a 12-week batch at the recurse center in NYC this summer. If you're curious about the recurse center, take a look at their website for details (https://recurse.com). While I will still be around and able to participate in the community at a lower level, I will need to step down from my current role as primary maintainer of yt when I leave NCSA so I can focus on new projects and opportunities.

Matt has volunteered to take up some of the slack on code review but I'm hoping that everyone else can also chip in. We also have two postdocs here at NCSA (Madicken Munk and Jared Coughlin) who have both expressed interest in stepping up their contributions to yt and helping out with day-to-day support and maintenance. I also hope we can have a conversation about updating yt's governance documents and adding rotating members to the steering committee at the development workshop next week.

I would like to continue maintaining unyt as part of the yt project going forward as I expect that will take substantially less time than maintaining yt as a whole. If people are nervous about yt depending on unyt when I'm not employed to work on yt development that is fair and I'm happy to talk about the relationship between unyt and yt in light of all of this.

My plan for the next few weeks is to help get yt-4.0 in a state where we can do a release. That means merging the yt-4.0 branch into master, helping out with testing and documentation, and triaging and fixing remaining issues. I don't know if we'll be able to do a yt 4.0 final release by May but hopefully we'll at least have a much more solid base to work from.

I'm going to try my best to make this transition as smooth as possible. If you're aware of places where I could take action now to lead off headaches down the road it would be great to get reminders about those places.

It's been an amazing experience to have so much of my professional life and achievements influenced by yt and the yt community over the past 8 years or so. I'm looking forward to seeing all the cool new things you all will build in the next few years.

With a heavy heart,

Nathan _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org

-- Asst. Prof. Anthony Scopatz Nuclear Engineering Program Mechanical Engineering Dept. University of South Carolina scopatz@cec.sc.edu Cell: (512) 827-8239 Book a meeting with me at https://scopatz.youcanbook.me/ Open up an issue: https://github.com/scopatz/me/issues Check my calendar https://www.google.com/calendar/embed?src=scopatz%40gmail.com

Hi Nathan, I don't think there's any way I can convey what a genuine honor it has been to work with you on this project for so many years. I have learned so much from you, and I am deeply appreciative of all you have done -- not just with yt, but so much more broadly. Thank you. -Matt On Thu, Feb 28, 2019 at 2:27 PM Nathan Goldbaum wrote:

Hi all,

I'd like to publicly announce that I will be leaving my current position at NCSA at the beginning of May and starting a 12-week batch at the recurse center in NYC this summer. If you're curious about the recurse center, take a look at their website for details (https://recurse.com). While I will still be around and able to participate in the community at a lower level, I will need to step down from my current role as primary maintainer of yt when I leave NCSA so I can focus on new projects and opportunities.

Matt has volunteered to take up some of the slack on code review but I'm hoping that everyone else can also chip in. We also have two postdocs here at NCSA (Madicken Munk and Jared Coughlin) who have both expressed interest in stepping up their contributions to yt and helping out with day-to-day support and maintenance. I also hope we can have a conversation about updating yt's governance documents and adding rotating members to the steering committee at the development workshop next week.

I would like to continue maintaining unyt as part of the yt project going forward as I expect that will take substantially less time than maintaining yt as a whole. If people are nervous about yt depending on unyt when I'm not employed to work on yt development that is fair and I'm happy to talk about the relationship between unyt and yt in light of all of this.

My plan for the next few weeks is to help get yt-4.0 in a state where we can do a release. That means merging the yt-4.0 branch into master, helping out with testing and documentation, and triaging and fixing remaining issues. I don't know if we'll be able to do a yt 4.0 final release by May but hopefully we'll at least have a much more solid base to work from.

I'm going to try my best to make this transition as smooth as possible. If you're aware of places where I could take action now to lead off headaches down the road it would be great to get reminders about those places.

It's been an amazing experience to have so much of my professional life and achievements influenced by yt and the yt community over the past 8 years or so. I'm looking forward to seeing all the cool new things you all will build in the next few years.

With a heavy heart,

Nathan _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org