# PlasmaPy community meeting agenda and minutes - Tuesday 2020 October 20 at 18:00 UT

[](https://hackmd.io/tsHpdBtTQrWOGVDp9vRVUQ)

### Video Conference Information
* [Jitsi video conference link](https://meet.jit.si/plasmapy) with [call-in information](https://meet.jit.si/static/dialInInfo.html?room=plasmapy)
* Instant messaging: [Matrix](https://riot.im/app/#/room/#plasmapy:openastronomy.org) and [Gitter](https://gitter.im/PlasmaPy/Lobby)
* [PlasmaPy google directory](https://drive.google.com/drive/folders/0ByPG8nie6fTPMEIxTlZLZjdjYms?usp=sharing) ([minutes/agendas](https://drive.google.com/drive/folders/0ByPG8nie6fTPV1FQUEkzMTgtRTg?usp=sharing), [documents](https://drive.google.com/drive/folders/0ByPG8nie6fTPYzk2TEhTa1N6R0U?usp=sharing))
* [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?cid=bzVsb3ZkcW0zaWxsam00ZTlrMDd2cmw5bWdAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ)

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

1. Introductions
2. DPP open source mini-conference talks and posters!
3. Do we still want to release 0.5.0 before DPP?
4. Defining affiliated packages...adding to website
5.
6. Issues
1. ...
2.
3.
7. Pull requests in progress
1. [PR 908](https://github.com/PlasmaPy/PlasmaPy/pull/908): `plasmapy.analysis` & fit functions
2. [PR 922](https://github.com/PlasmaPy/PlasmaPy/pull/922): Test refactoring #3

## Minutes

* Probably not enough time before DPP to do a 0.5.0 release
* A release in ~2 months would have more substantive changes
* Create a page on website with mission statement related to gathering open source projects for the plasma community in general
* Two subgroups: affiliated packages and community packages?
* Community packages would not necessarily be interoperable with PlasmaPy
* Affiliated packages would be actively working towards interoperability
* Should look at [Astropy stuff](https://www.astropy.org/affiliated/index.html) which has affiliated, coordinated, and infrastructure packages
* Can expand it in the future
* Who should put this on the website? And when do we want it by?
* Can move source link out of website, and put in footer
* Should put together a PlasmaPy email address
* Can set this up through register.com: [e-mail], but requires a monthly fee
* Nick will look into this, but it may take longer due to bureaucratic stuff for reimbursement
* [Setting custom domain emails up through google?](https://workspace.google.com/solutions/new-business/)
* Erik will be meeting with Peter biweekly at 9 Pacific on Mondays
* Should add office hours to PlasmaPy google calendar
* In testing guide, about having multiple assert statements strung together in one test function vs. having a separate test for each assert statement, talk about how a deciding factor is that the former approach could be more appropriate if the outcomes of the subsequent tests would not be helpful in diagnosing problems (i.e. if it doesn't actually make sense to run the subsequent tests).