---
# System prepended metadata

title: 'PlasmaPy community meeting agenda and minutes - Tuesday 2020 December 22 at 18:00 UT'
tags: [community, ' minutes']

---

---
tags: community, minutes
---

# PlasmaPy community meeting agenda and minutes - Tuesday 2020 December 22 at 18:00 UT

[![hackmd-github-sync-badge](https://hackmd.io/kX-urpoKTeCg7RsVkW30XA/badge)](https://hackmd.io/kX-urpoKTeCg7RsVkW30XA)

### 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://app.element.io/#/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. roadmap chat
3. `plasmapy-meeting-notes` renamed to `plasmapy-project`
4. GitHub Discussions vs Discourse??
5. Established GitHub "Project Issues" and associated GitHub Labels https://github.com/PlasmaPy/PlasmaPy/issues/964
6. ...
7. Issues
    1. ...
    2. ...
8. Pull requests in progress 
    1. [PR 942](https://github.com/PlasmaPy/PlasmaPy/pull/942) Update documentation for particles and utils subpackages (**MERGED**)
    2. [PR 962](https://github.com/PlasmaPy/PlasmaPy/pull/962) Updating names for Coulomb Logarithm
    3. [PR 932](https://github.com/PlasmaPy/PlasmaPy/pull/932) Dispersion
    4. [PR 963](https://github.com/PlasmaPy/PlasmaPy/pull/963) Grids #2
    
## Attendees

* Dominik
* Nick
* Erik
* Ehab
* Tiger

## Action Items

***Dominik***
- [x] link back to discourse from github discussion pages
    - do we want to do that?
- [x] do the big migration of meeting notes repo etc etc, with separate meeting directories
    * this has been done and this is a little test change to see how badly I broke the links
- [ ] update Discourse links to GitHub Discussions (website, RTD, and repo links, README!)

***Erik***
- [ ] need to start summarizing the roadmap from past meetings, this will facilitate future discussions
- [x] form core Review team of Erik, Nick, and Dominik
- [ ] Review [PR 932](https://github.com/PlasmaPy/PlasmaPy/pull/932) Dispersion

***Nick***
- [x] After Erik creates Reviewer Team, assign team to PR 942 as a test run for the process
- [ ] Create an issue on adding a Jupyter notebook on Coulomb logarithm super magical fun stuff
- [ ] Review [PR 962](https://github.com/PlasmaPy/PlasmaPy/pull/962) give 👍 or 👎 on naming scheme
- [ ] ~~Think about creating an issue for which default Coulomb logarithm to use~~

## Minutes

* **MEETINGS WILL RETURN ON JAN. 5TH 2021**
* Need to review development guide on whether instructions for pre-commit usage are there
    * Need to get Erik to read them!
* Going with GitHub discussions for now
    * GitHub discussion have the benefit of visibility, better interop with issues/PR...but will likely have slow development and less features than Discourse
    * update discussion forum links
    * post on discourse that we'll be trying github discussions out
* https://github.com/isaacs/github/issues/305
* sphinx:
    * single ticks `` ` ``: default to `py:mod:` in sphinx (which is utilized by intersphinx referencing)  e.g. `` `numpy.nan` `` maps to `` py:mod:`numpy.nan` ``
    * double ticks ` `` `: code blobs, ``a = np.isnan(b)``
    * math blocks: ``:math:`a = nan(b)` ``
    * PlasmaPy's usage of the above goes like
        * single ticks when trying to link/reference code objects/members (this creates links to said objects documentation)
        * double ticks when writing inline code that does not reference a documented code object
        * math syntax when talking about math objects 
