---
# System prepended metadata

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

---

---
tags: Hack Week
---

# Hack week planning meeting | Thursday 2022 May 5 at 11 am ET

## Agenda

1. Check-in
2. Status update on registration form (Ramiz)
3. Google Drive
    * [Link to Drive](https://drive.google.com/drive/folders/1LaxMGDt1fPhJP9D9XtefFB2sOoVtFUEy?usp=sharing)
4. Review [Distribution List] (David)
4. [Schedule]
    * Review current schedule
    * Outline a theme for each day
    * start gathering content for each day
    * Who should lead sessions? How should sessions be lead?
6. Review website
7. Discord channel
8. Lightning :lightning: talks :zap: :zap: :zap:
9. Hack Week repo (if time)
    * How should we set up the hack week repo before the event starts
    * What materials should we make available before the event begins?

[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

* ...

## Minutes

* Registration form
    * some edits made from last time
    * it needs a review and then can be posted to the website
* Distribution list
    * website is live, so David will begin sending out announcements
    * if the registration form can be ready today or tomorrow, then we'll have it included in the announcement
* Schedule
    * Troubleshooting hours...one before and after each day
    * A helpdesk channel on discord so a troubleshooting breakout session can be launched as needed.
    * Someone in the helpdesk would need what's happening in the main session.
    * Might not have the people power to manage a breakout help desk...this is way the before and after helpdesk ours might be more feasibly (maybe include the help desk during the social hour)
    * People are that the fundamental topics of Day 1 and 2 are needed
    * [Day 3]: The formulary day
        * spend the day in breakout sessions focused on develping code specifically for lenght, speed, frequency, etc. parameters
        * people tend to like this idea
    * [Day 4]: similar to day 3 but have more advanced topics (bdots, CMA diagrams, etc.)
    * [Day 5]: hopefully utilize participant suggested topics, but have our own as backup
* lightening talks
    * request pre-recorded talks
    * we can then apply a hard time cutoff
* How to handle share screen during the Hack Week?
    * Likely don't want a blanket allow
    * allow share on a per case basis...this could be clunky
* Who will be leading topics?
    * Are we doing all internally?
    * Should we ping people from outside the committee to help?
    * let's think about this for next week