---
# System prepended metadata

title: Hack week planning meeting | Thursday 2022 April 14 at 11 am ET
tags: [Hack Week]

---

---
tags: Hack Week
---

# Hack week planning meeting | Thursday 2022 April 14 at 11 am ET

# Agenda

1. Introductions
2. Registration form update
3. Website stuff
    * Photos for organizing committee needed
4. Meeting format
5. Brainstorm meeting topics

## Action Items

* [Erik] ping Ramiz about getting the registration form going
* [Erik] get first iteration of website merged

## Minutes

* **Need to work on wording to explain and advertise the meeting.**
    * clearly define the difference between Hack Week and a Hackathon
    * needs to be done on the web page and email
    * Hack School (?) ... immediately changes the meaning ... **The School of Hack**
* [Erik] begain reorganizing website for the 2022 event (see PR https://github.com/PlasmaPy/hack.plasmapy.org/pull/64)
* Morris will likely not be able to continure helping
* Registration Form
    * will repurpose last year's registration form
    * keep the lighning talk part but give more of an explanation of what it is
    * say a talk is 5 mins, but we budget for longer in our scheduling
* Meeting format?
    * keep the same format as last time
        * Morning: 8-10am PT
        * Break: 10-11 am PT
        * Late Morning: 11-1pm PT
    * This schedule prioritizes timezones of the meeting coordinators (i.e. North America and Europe)
* Having a motivation talk in the morning of the first day?
    * show case some amazing project currently happening
    * capture the minds of the people
* Brainstorm
    * thinking complexity of session escalates throuh the week
    * DAY 1-2
        * Terminals (on Mac, Linux, Windows)
        * git
        * GitHub (mechanics of github, forking, cloning)
        * local (git) & remote (GitHub) integration
        * virtual environments (why do you want to create?)
        * conda
        * jupyter notebooks (local, binder, google colab)
    * DAY 3 -> 
        * contributing to the hack pkg
        * focus on a formulary, but not limited to
        * should come to the session with specific hack topics
    * DAY 4 ->
        * do more complex topics...like hashing out langmuir, bdot functionality, or the like
* **Labeling days as a certain skill level**
    * earlier days should prepair the noob for attending the later days
    * should be advertised on day 1, in emails, on the web page, etc.
