---
# System prepended metadata

title: 'PlasmaPy "Project" Meeting | Wednesday 2022 Feburary 09 at 12:00 PT / 15:00 ET'
tags: [project management, ' minutes']

---

---
tags: project management, minutes
---

# PlasmaPy "Project" Meeting | Wednesday 2022 Feburary 09 at 12:00 PT / 15:00 ET

### Video Conference Information
* [Zoom](https://www.plasmapy.org/zoom)
* Instant messaging: [Matrix](https://element.im/app/#/room/#plasmapy:openastronomy.org) and [Gitter](https://gitter.im/PlasmaPy/Lobby)
* [GitHub Minutes Repository](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes)
    * ["Project" Sub-directory](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes/_project)
* [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 of [roadmap](https://hackmd.io/@plasmapy/ry0mmnj6v)
3. solicit "Project Issues"
4. Hack Week Roles
5. Gio and YouTube (Erik (!) get off your rear!)
6. ...
7. ...
8. Issues
    1. ...
    2. ...
9. Pull requests in progress 
    1. ...

## Attendees

* Erik
* Nick
* Steve
* David
* Ben

## Action Items

***David***
* will summarize roles to be presented to outside sources
* initial contact for filling roles

## Minutes

* 2022 Hack Week Roles
    * These are the postions that should be filled by members of the organizing committee
    * The Positions:
        * Project Manager (glue person): 
            * The one that keeps everyone on Task.
            * Should probably be a PlasmaPy person.
        * Meeting Scheduler
            * Scheduling of Planning Meetings
            * Schedule hack sessions
            * Global structure of event
        * Presenter Scheduler
            * The one that reaches out to presenters
            * Fills the talk and hack sessions with presenters
            * manages lightning talks
        * Communications Director
            * emailing participants
            * newsletters
            * announcements
            * posting on engage forum
            * reminding people of upcomming planning meetings
        * Social Media Coordinator
            * posting to social media sources
            * could be absorbed into Communications Dirctor
        * Recorder (for meeting)
            * record meeting minutes
            * setup surveys
            * organize post-meeting review
        * Video Manager
            * ensures presentations are recorded during the HackWeek
            * performs basic video editing and uploads videos to PlasmaPy's YouTube channel
        * Unconference coordinator (live event manager?)
            * Only occurs during the event
            * ensures the live event flows
            * listens to the participants needs
        * GitHub & Website Manager
            * manages Hack Week website
            * manages GitHub repo associated with the event
            * also likely to be a PlasmaPy person
    * Who and How should we reach out to fill the roles?
        * email PlasmaPy mailing list
        * email last Hack Week organizer list
        * email last Hack WEek participants list
        * email Computational Seminar
        * contacts through MagNET
        * post on engage
        * individual emalils
        * post on social media (facebook and twitter)
        * plasma grad student discord
        * post on BaPSF slack
        * Plasma Pride discord server
        * Reach out to Saskia (or Liz Merrit) to further expand to (WiPP+) women in plasma physics +

* Brainstorm of responsibilities
        * Project Mangager (CEO/Chair): glue person to keep all other organizers on task, likely a PlasmaPy person

* Open questions & topics
    * What if there is limited community participation?
        * Responsibility/contingency structures
    * Hardest part was getting people to spend time collectively coding
        * Last time was more watching than doing
    * How do we make people feel free to be able to talk?
    * Should have 
    * Live stream of coding
    * Maybe have a person to coordinate community-driven sessions
    * Is there unconference software?
