yt-dev March 2020

yt-dev@python.org

4 participants
6 discussions

by Madicken Munk

Hi yt dev! It has been some time since we last did a release of yt. `master` has a lot of features that are not in any of our releases on pypi and conda forge. We're also prepping for the yt-4.0 release soon. I propose that we try to get yt 3.6 out the door soon so we can use our developer time on yt-4.0. We should leave some time so that people can get issues resolved and minor features added before we publish the release. Is April 08 a long enough time out for everybody? If not, what would be better? That's just under two weeks out, but the release would happen on a Wednesday so we have a couple of days to put out fires if things go horribly wrong (and we're not working over a weekend). What do you think? Is this too aggressive? Too slow? I've added a label to the yt repo called `yt-3.6`. Please use this label (or comment if you don't have access to the labels) in your open PRs or in your PRs that you submit before we do the release if you want them to be included in yt-3.6. For the next while we'll prioritize review of the 3.6 related PRs. The CI platforms are still not reliably running on master. I'll do my best to get them working ASAP so we know that the features we're adding aren't introducing obvious breaking changes. -Madicken TL;DR: - I am proposing we release the yt 3.6 on April 08. Do you all agree on this timeline? - If you want to have a feature in yt 3.6 or resolve an issue before this release, please label using the yt-3.6 label or comment in your PRs that this is a yt 3.6 feature. We will give review priority to those PRs before the release.

6 months

Edinburgh yt workshop cancelled

by Britton Smith

Hi everyone, I think this message will not come as a surprise to anyone. In light of the COVID-19 pandemic, we have decided to cancel the yt user/developer workshop at the University of Edinburgh this summer. There is not yet a specific plan for a workshop at a later date, but we will make a go at having one in summer 2021. In the meantime, we will also look into the possibility of hosting an online yt workshop sometime this summer. Stay safe and stay connected. Britton

6 months

Announcing the 2020 John Hunter Excellence in Plotting Contest

by Madicken Munk

Dear all, In memory of John Hunter, we are pleased to announce the John Hunter Excellence in Plotting Contest for 2020. This open competition aims to highlight the importance of data visualization to scientific progress and showcase the capabilities of open source software. Participants are invited to submit scientific plots to be judged by a panel. The winning entries will be announced and displayed at SciPy 2020 or announced in the John Hunter Excellence in Plotting Contest website and youtube channel. John Hunter’s family are graciously sponsoring cash prizes for the winners in the following amounts: - 1st prize: $1000 - 2nd prize: $750 - 3rd prize: $500 - Entries must be submitted by June 1st to the form at https://forms.gle/SrexmkDwiAmDc7ej7 - Winners will be announced at Scipy 2020 in Austin, TX or publicly on the John Hunter Excellence in Plotting Contest website and youtube channel - Participants do not need to attend the Scipy conference. - Entries may take the definition of “visualization” rather broadly. Entries may be, for example, a traditional printed plot, an interactive visualization for the web, a dashboard, or an animation. - Source code for the plot must be provided, in the form of Python code and/or a Jupyter notebook, along with a rendering of the plot in a widely used format. The rendering may be, for example, PDF for print, standalone HTML and Javascript for an interactive plot, or MPEG-4 for a video. If the original data can not be shared for reasons of size or licensing, "fake" data may be substituted, along with an image of the plot using real data. - Each entry must include a 300-500 word abstract describing the plot and its importance for a general scientific audience. - Entries will be judged on their clarity, innovation and aesthetics, but most importantly for their effectiveness in communicating a real-world problem. Entrants are encouraged to submit plots that were used during the course of research or work, rather than merely being hypothetical. - SciPy and the John Hunter Excellence in Plotting Contest organizers reserves the right to display any and all entries, whether prize-winning or not, at the conference, use in any materials or on its website, with attribution to the original author(s). - Past entries can be found at https://jhepc.github.io/ - Questions regarding the contest can be sent to jhepc.organizers(a)gmail.com John Hunter Excellence in Plotting Contest Co-Chairs Madicken Munk Nelle Varoquaux

6 months, 1 week

yt triage meetings - spring 2020

by Madicken Munk

Hi yt community, I'd like to start scheduling yt triage meetings for the next few months. If you're interested in yt development, in discussing your recently submitted PR, or you've encountered a bug but you're not sure quite how to start fixing it, then we'd love for you to attend the triage meetings! To be more inclusive to developers a breadth of timezones, we'll alternate triage meeting times every other week. I'll choose one early morning time and afternoon time (based on US central time), which together should cover more developers' availability. If you're interested in attending at all, please respond to the polls I'm sending out! Meetings will be on Fridays. Report your general Friday availability, not just the availability for March 06. Morning meeting poll: http://whenisgood.net/7cbrt49 Afternoon meeting poll: http://whenisgood.net/t3hci7j There are two different polls -- if you know for sure you won't be attending one of the meetings (if you're in Europe and don't like or plan on attending a meeting in the evening, for example), please do not respond to the poll for that time at all and only respond to the one where you plan to attend. Make sure to update the time zone of the poll to be where you're located! These triage meetings will build off of the ones we had in the fall, but I'd like to expand their scope a bit. The first purpose of the meetings will be to do day-to-day yt maintenance work (triage issues, review PRs, respond to issues, etc.), then if we have time the rest of the time can be spent either coworking or talking about where to direct our developer resources over the coming week (which bugs we should focus on fixing, what features need improvement, etc.). We have the yt-4.0 release and yt 3.6 releases on the horizon, so supporting the project moving towards these releases will keep things going! I will pick times for yt triage meetings based on whoever has filled out the poll by Wednesday, March 11th. Our first triage meeting will be on Friday, March 13th (👻)! I'm looking forward to triaging, PRing, and community-ing with you all! -Madicken

6 months, 2 weeks

Yt User/Developer Workshop: call for funding requests

by Britton Smith

Greetings, The yt User/Developer Workshop to be held at the University of Edinburgh (June 29-July 3) is now accepting applications for financial support. If you would like to request support, please visit the workshop webpage <https://higgs.ph.ed.ac.uk/workshops/yt-user-and-developer-workshop/> and follow the instructions under "Requesting Financial Support." The deadline to request support is Friday March 27, 2020. After that time, the workshop will be open for registration. As the situation with the COVID-19 virus continues to evolve, it's difficult to say for certain what will happen between now and the workshop. For the moment, we will continue under the assumption that the workshop will happen as scheduled. If needs be, we will extend deadlines to allow for as much flexibility as possible. I look forward to seeing you in Edinburgh this summer! https://higgs.ph.ed.ac.uk/workshops/yt-user-and-developer-workshop/ Britton

6 months, 2 weeks

Spam on the list

by Matthew Turk

Hi folks! I've just updated the list settings in light of some recent spam. Messages will be held for moderation. This is not great, but it will help us to keep out obvious spam. When someone posts for the first time, we'll either mark them as "whitelisted" so that all subsequent messages do *not* get moderated and just go right through. So, those of you who have been on the list for a while will see your next message get held, but I'll keep on top of that to make sure you're then whitelisted. Sorry for the inconvenience. -Matt

6 months, 3 weeks

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

yt-dev March 2020