---
tags: community, minutes
---

# PlasmaPy Community Meeting | Tuesday 2021 November 23 at 18:00 UT

### Video Conference Information
* [Zoom link](https://zoom.us/j/91633383503?pwd=QWNkdHpWeFhrYW1vQy91ODNTVG5Ndz09)
* Instant messaging: [Matrix](https://app.element.io/#/room/#plasmapy:openastronomy.org) and [Gitter](https://gitter.im/PlasmaPy/Lobby)
* [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)
* [PlasmaPy on GitHub](https://github.com/PlasmaPy/plasmapy) ([pull requests](https://github.com/PlasmaPy/plasmapy/pulls), [issues](https://github.com/PlasmaPy/plasmapy/issues))
* [PlasmaPy Enhancement Proposals on GitHub](https://github.com/PlasmaPy/PlasmaPy-PLEPs)
* [PlasmaPy Google 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)

1. Introductions
2. 10-15 minutes for [roadmap](https://hackmd.io/@plasmapy/ry0mmnj6v)
3. solicit "Project Issues"
4. Retrospective on 0.7.0 release
* Any revisions to [release guide](https://docs.plasmapy.org/en/latest/development/release_guide.html)?
* scripts!
* leftover stuff:
* [conda](https://github.com/conda-forge/plasmapy-feedstock/pull/16)
* release notes
* 0.7 PR (can't merge without squash?)
6. Numba and new releases of Python
7.
8. Issues
1. ...
9. Pull requests in progress
1. [Adopt Contributor Covenant v2.1](https://github.com/PlasmaPy/PlasmaPy/pull/1324)
10. Pull requests **MERGED**
1. ...

## Attendees

* Erik
* Nick
* Dominik
* Elliot
* Rajagopalan

## Action Items

***Person***
* ...

## Minutes

* https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=417184&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d&l=1028
* 0.7.0 release
* Dominik started coding up a simple bash script to get closer to automating the whole thing. Will go through that and update the release guide as needed.
* Some things we can't automate, but helpful to automate what we can.
* Can we use a GitHub Action?
* Some parts need manual intervention: manually modifying files, etc.
* Not much to be gained from GitHub Actions
* A GitHub Action would enable a weekly dev release
* `setup.cfg` file has links that get put on PyPI. Didn't like `#` showing up in hyperlink for chat
* Can get around it by using `https://www.plasmapy.org/chat` redirect
* Might need to release `0.7.1` because it didn't exclude `docs/plasmapy_sphinx` (around line 105 of `setup.cfg`)
* Confusion about how files get included in distributions
* Maybe use a checklist?
* Perhaps create a checklist issue for each release.
* If it's editable by maintainers then anyone should be able to add/edit items.
* We could also make a template for this issue with the items that need to be done for every release
*