Mailman 3 September 2019 - yt-dev

Switching from Nose to Pytest
by Coughlin, Jared W Dec. 20, 2019

Dec. 20, 2019

Hello! I've been working on a PR (https://github.com/yt-project/yt/pull/2286) that converts yt's testing framework from nose to pytest. I believe that it's mostly ready to go, so I was writing to see what everyone's thoughts on this change are, if there is any feedback on my implementation, and if anyone would be willing to help review it, since there are quite a few changes. Thanks, and have a good weekend! -Jared

5 10

weekly PR triage
by Matthew Turk Oct. 24, 2019

Oct. 24, 2019

Hi folks, We used to have a weekly PR triage meeting, but then, we stopped having one! I have re-created one, set up for 9:30AM Central time on Fridays for the next couple weeks. They worked really well while we did them. I've also left it be a bit long so that if there's any non-PR-triage work we can or should do, we can do that too. I know this isn't ideal for West Coast folks, but I'd be happy to set up another one as well. Looking forward to seeing you! The invitation is copied below, and there's a link to a URL that will add it to your calendar. I'll try (but will likely forget) to send out reminders. Best, Matt Matthew Turk is inviting you to a scheduled Zoom meeting. Topic: yt PR triage and co-working Time: Sep 20, 2019 09:30 AM Central Time (US and Canada) Every week on Fri, until Nov 1, 2019, 7 occurrence(s) Sep 20, 2019 09:30 AM Sep 27, 2019 09:30 AM Oct 4, 2019 09:30 AM Oct 11, 2019 09:30 AM Oct 18, 2019 09:30 AM Oct 25, 2019 09:30 AM Nov 1, 2019 09:30 AM Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://illinois.zoom.us/meeting/vpApcOqopjstT5gdYkIDGz6AmSlsYv7AGw/ics?ics… Join Zoom Meeting https://illinois.zoom.us/j/344730807 One tap mobile +19292056099,,344730807# US (New York) +16699006833,,344730807# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) +1 647 558 0588 Canada +49 30 3080 6188 Germany +49 30 5679 5800 Germany +49 69 7104 9922 Germany +82 2 6105 4111 South Korea +82 2 6022 2322 South Korea +44 203 051 2874 United Kingdom +44 203 481 5237 United Kingdom +44 203 966 3809 United Kingdom +44 131 460 1196 United Kingdom +81 524 564 439 Japan +81 3 4578 1488 Japan +61 8 7150 1149 Australia +61 2 8015 6011 Australia +52 554 161 4288 Mexico +52 229 910 0061 Mexico Meeting ID: 344 730 807 Find your local number: https://zoom.us/u/abzljuNmCN Join by SIP 344730807(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India) 213.19.144.110 (EMEA) 103.122.166.55 (Australia) 209.9.211.110 (Hong Kong) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan) Meeting ID: 344 730 807 Join by Skype for Business https://illinois.zoom.us/skype/344730807

3 4

Update on yt governance documents/structure
by Madicken Munk Oct. 23, 2019

Oct. 23, 2019

Hi yt-dev! As many of you know, the yt-project has been growing and evolving over the past several years (to new domains, to new datasets, to support new packages, etc.). To accompany that growth, we'd like to take the opportunity to update our governance structure. We've been working on updating our governance model for the yt project and I've submitted two companion PRs with drafts of this updated governance: https://github.com/yt-project/governance/pull/1 and https://github.com/yt-project/ytep/pull/7 Our existing governance structure is located at https://ytep.readthedocs.io/en/master/YTEPs/YTEP-1776.html The first PR is to a new governance repository, where our governance documentation will live separately from the YTEPs. This will allow us to maintain and minorly update our governance without having to update YTEP. The second PR is to the YTEP repository and generally outlines the core values and ideas we want our governance structure to reflect. Hopefully all of the things I've listed in the YTEP are reflected in the governance docs. As members of the community, I'd like to solicit feedback from all of you about these governance documents. Do these reflect our community values? Should we add anything? Do you feel everything is clear? Is this too much governance for our community right now? Is there something that's missing? Feel free to reply here or comment on the pull requests! Our governance will be better with your feedback. Madicken PS - I tried to build in a mentorship structure into our maintainer structure to help with onboarding new maintainers. I'd especially like to know if you all think this would be valuable to you or if it is adding unnecessary constraints to our community.

1 1

notes for team meeting 11
by Britton Smith Sept. 26, 2019

Sept. 26, 2019

Hi everyone, Team meeting 11 was on September 12, 2019. The notes from the meeting are now up here <https://github.com/yt-project/project-records/blob/master/meeting-notes/not…> . Britton

1 0

Appveyor github organization
by Nathan Sept. 20, 2019

Sept. 20, 2019

Hi all, It looks like when I originally set up appveyor for yt a few years ago I did it incorrectly under my own github account instead of under the yt-project organization. There are instructions for how to sign up for an organization account on appveyor here: https://www.appveyor.com/docs/team-setup/#setting-up-appveyor-account-for-g… Someone (not me, I'm not sure which e-mail to use) will need to follow those instructions to set up a yt-project account on appveyor using an e-mail address controlled by the project or a project maintainer. Once that is set up you'll be able to update the webhook on the yt-project org to point at the new test setup on the yt-project appveyor account. Sorry for setting this up in a bad way and sorry for any confusion this has caused, I honestly didn't realize until now that this was an issue. -Nathan

2 1

proposal: get rid of the install script
by Britton Smith Sept. 19, 2019

Sept. 19, 2019

Hi everyone, This might be a real hot take, but I'd like to propose getting rid of the install script. Below are a few reasons I think this is a good idea: - yt can be reliably installed straight from pip or conda. Even installing from source can be done reliably with "pip install -e ." assuming you have pip. This has all been true for quite some time. - The install script needs to be maintained. It's currently 718 lines long, still has options for installing mercurial, rockstar, etc. I will happily back down if anyone feels particularly attached to it, but I think the combination of the above two points makes it more trouble than it's worth. Comments encouraged! Britton

6 5

traitlets YTEP
by Matthew Turk Sept. 16, 2019

Sept. 16, 2019

Hi folks, I wrote up a reasonably short YTEP about why and how we could use the traitlets library in some particular places in yt: https://github.com/yt-project/ytep/pull/8 I look forward to comments and discussion! -Matt

1 0

yt project calendar
by Britton Smith Sept. 9, 2019

Sept. 9, 2019

Greetings! We have created google calendar to keep track of yt project-related events. We'll post team meetings, workshops, or other events when people from yt are getting together. If you'd like to view it or add to your own calendar click here <https://calendar.google.com/calendar?cid=ZjJsaGJhcXAzcGRkY2xmNjRvN3RkNDBkbj…> . Britton

1 0

yt Team Meeting 11: Thursday, 9/12 at 10am EDT
by Britton Smith Sept. 9, 2019

Sept. 9, 2019

Hi everyone, We'll have a yt team meeting this Thursday 9/12 at 3pm BST (10am EDT). I'll post a link to the hangout on slack when it begins. The steering committee members will be there, but all are welcome to participate. Thanks! Britton

1 0

code reformatting
by Matthew Turk Sept. 3, 2019

Sept. 3, 2019

Hi folks, In this weeks "PyCoders" newsletter, they note that "git blame" can now ignore revisions. https://twitter.com/llanga/status/1163767833706323970 https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-rev… I believe this might remove one of the biggest objections we've had to things like running a code formatter such as black. It's not obvious to me that there won't be additional issues introduced by doing this, but it could be a good starting place for consistent code formatting. -Matt

4 4