---
tags: community, minutes
---

# PlasmaPy Community Meeting | Tuesday 2023 Jan 17 at 2 pm ET

### Video Conference Information
* [Zoom link](https://zoom.us/j/91633383503?pwd=QWNkdHpWeFhrYW1vQy91ODNTVG5Ndz09)
* [Element chat](https://app.element.io/#/room/#plasmapy:openastronomy.org)
* [GitHub Minutes Repository](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes)
* ["Community" Sub-directory](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes/_community)
* [Repository](https://github.com/PlasmaPy/plasmapy) ([pull requests](https://github.com/PlasmaPy/plasmapy/pulls), [issues](https://github.com/PlasmaPy/plasmapy/issues))
* [PlasmaPy Enhancement Proposals](https://github.com/PlasmaPy/PlasmaPy-PLEPs)
* [Calendar](https://calendar.google.com/calendar/embed?src=c_sqqq390s24jjfjp3q86pv41pi8%40group.calendar.google.com&ctz=America%2FNew_York)

## Agenda (please feel free to edit or add items)

[MPRL]: http://webhome.auburn.edu/~thomaed/mprl/mdpx-pages/mdpx-construction/construction-images-junejul/index.html
[ZEUS]: https://zeus.engin.umich.edu/laser/
[bridge]: http://ems-docs.element.io/books/element-cloud-documentation/page/discord-bridge
[SULI summer school]: https://suli.pppl.gov/2021/course/

1. Introductions
2. `v2023.1.0` release
3. [Issues](https://github.com/PlasmaPy/PlasmaPy/issues)
- ...
4. [Pull requests](https://github.com/PlasmaPy/PlasmaPy/pulls)
- [x] dependabot
5. [ ] Dominik: maybe we could add [numba-style issue labels (4 - Waiting on author/CI/reviewer)](https://github.com/numba/numba/labels)? Any suggestions? I wanted this for:
1. waiting on author: [#1548](https://github.com/PlasmaPy/PlasmaPy/pull/1548), [#1831](https://github.com/PlasmaPy/PlasmaPy/pull/1831)
7. waiting on weird CI issues: [buchsbaum](https://github.com/PlasmaPy/PlasmaPy/pull/1828)
8. possibly: could be picked up and finished: [sphinx whatsnew -> changelog](https://github.com/PlasmaPy/PlasmaPy/pull/1639)
7. Doing cool Python 3.9+ annotation/decorator stuff with `__class_getitem__` ([PEP 560](https://peps.python.org/pep-0560/))
1. Example: [`Quantity.__class_getitem__`](https://github.com/astropy/astropy/blob/b1e6ff80b708c30f6e235ac8f027a763f4297a79/astropy/units/quantity.py#L342)
2. `validate_quantities`: [issue #1414](https://github.com/PlasmaPy/PlasmaPy/issues/1414) & [PR #1661](https://github.com/PlasmaPy/PlasmaPy/pull/1661)
3. Do something similar with particle typing w.r.t. particle categories (vs. specifying categories in `particle_input`)?
8. [Remove stable branch (just like xarray did)?](https://github.com/pydata/xarray/issues/6206#issuecomment-1025241182)

## Attendees

* Nick
* Erik
* Dominik

## Action Items

***Person***
* ...

## Minutes

* Need to annouce releases
* [x] Move to Mastodon?
* now waiting for fosstodon application review; for now on personal email, will transfer to `team@plasmapy` later
* - [x] Delete `stable` branch?
* We have to manually update `stable` during releases
* But Read the Docs no longer requires there to be a `stable` branch
* It's smart enough to find the last (non-pre) release
- [x] We agreed that we can try out the new smart RTD functionality.
* Shouldn't be too hard to automate monthly releases
* https://github.com/marketplace/actions/send-email
* Nick releases jokes into public domain under CC0 license
* https://www.pola.rs/
* https://adventofcode.com/ in rust?
* issue labels: rename existing where possible
* `__class_getitem__`, sure, but first let's just play around with it and figure out how to use it wisely

# check_units

in comments, we had examples of three ways to annotate units on inputs:

@check_units
def f(x: u.m):
    pass

@check_units({"x": {"units": u.m}})
def f1(x):
    pass

@check_units
def f2(x: {"units": u.m}):      # drop this one because mypy
    pass

# instead we do this now so we can leverage mypy:
def f_canonical_new_awesome(x: Quantity[u.m]):
    pass