---
# System prepended metadata

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

---

---
tags: Hack Week
---

# Hack week planning meeting | Thursday 2022 June 2 at 11 am ET

## Agenda

1. We're **6 weeks** away
2. Hack Week repo
    * Cover change from the past week?
    * What else needs to be done?
    * **[Creating issues](https://github.com/PlasmaPy/hack-week/issues/new) for Hack Week projects!!!!**
    * resources directory...how should we utilize?
3. Documentation for the hack repo
    * https://docs.hack.plasmapy.org/en/latest/
    * we can choose a different CNAME if desired
    * need to link to documentation on the hack.plasmapy.org page
4. Hack Week Projects
5. [Schedule]
    * **How do we solidify the schedule?**
    * Review current schedule
    * When to post to website?
    * What are our next steps?
6. Status of advertisement/spreading the word (David)
    * how/when do we do follow up messaging?
7. Status of registration (Ramiz)
    * on website
    * responses so far
8. What material do we need to give participants before the event? (if time permits)
    * just start brainstorming what is needed
    * to go on the website and/or in the "resources" directory in the repo
10. Discord channel (if Time permits)
11. Review website (if Time permits)

[Google Drive]: https://drive.google.com/drive/folders/1LaxMGDt1fPhJP9D9XtefFB2sOoVtFUEy?usp=sharing
[Distribution List]: https://docs.google.com/document/d/1PN4_R3Rdv-h_BEDem9wknWZY5K4WwO8KJMq4bzuG3Ug/edit?usp=sharing
[schedule]: https://docs.google.com/spreadsheets/d/1OixK8fN8QOy0bKnXcZugayiuHzmQrMhAB0-etm9dIQk/edit?usp=sharing


## Action Items

* [Steve] compose and send out lightning talk email

## Minutes

* Review of changes to schedule from last week
* We should go in and make sure that we have a plan for the less-structured, getting started sessions
* Would be helpful to have `git` covered before IDEs

* Day 1:
    * Should cover basics of IDEs, but advanced concepts don't happen until day 2
    * Knowing the mechanics of an IDE requites the git commands, but that doesn't happen until Day 2

* Lightning talk criteria
    * Day 2-5 have a slot for (up to) 4 talks
    * pin the session before the social hours so we can break directly into the social hour
    * Limit all talks to 5 mins
    * No more than 2 slides
    * ...
    * reaching out to presenters
        * what day do you prefer?
        * tell them the criteria
        * confirm (lock-in) you will talk
    * announcement email
        * set end of registration to June 28, 2022
        * include criteria
        * if you're talk needs approval by your facility, please be aware of the timeline.


<!--- https://github.com/heliophysicsPy/summer-school --->