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

--- tags: Hack Week --- # Hack week planning meeting | Thursday 2022 April 7 at 11 am ET [Zoom link](https://us06web.zoom.us/j/84285813626?pwd=eW96bHMxODdySE01TkY5dVlqMGhXZz09) 1. Our first messages to the community 2. Registration form 3. Lightning talks? 4. Website # Action items * Website group * Look into registration form * Nick * # Minutes People attending: Valentina Marascu, Reynaldo Rojas, Will DeShazer, David Schaffner, Nick Murphy, Erik Everson, Ramiz Qudsi, Pawel Kozlowski, Steve Vincena * Summarizing [last week's meeting](https://hackmd.io/JOmPyYwPS7CEw0kXplmEXA) * Version 0.1 of roles * Adding the registration form to the website managers' responsibilities? * Yes, sharing the responsibility with communications * We should have a session to go over how the website works — maybe at the end of this meeting? * Uses [Nikola](https://getnikola.com/) * Most of the pages are written in [Markdown](https://www.markdownguide.org/), like these minutes * Need to archive 2021 event from website and start 2022 event. A way to do that is built into the repo — yay for planning ahead! * In `conf.py`, commented out "Past Events" page * Last year was presentation-heavy, with not as much time for hacking. An idea for this year: have ∼1–2 presentations in the "morning", with the rest of the time hacking in the afternoon to build a hack Python package. Essentially, duplicate [`plasmapy.formulary`](https://docs.plasmapy.org/en/latest/formulary/index.html) and functions from [NRL formulary](https://www.nrl.navy.mil/Portals/38/PDF%20Files/NRL_Formulary_2019.pdf?ver=p9F4Uq9wAtB0MPBwKYL9lw==) * Audience would be people who are new to contributing to open source software * Over week, populate the hack week repository * Can add whatever else they wanted to work on * A disadvantage is that we won't be highlighting existing packages as much as last year * Often people coming into events like these will not have a project that they're working on already. Could come up with several development efforts that * Maybe have the above idea be the main event, and allow participants the freedom to have hack sessions focusing on different efforts * One of the big hurdles is that there was hesitancy for people so speak up. * Can sprinkle in new stuff too * Could start with speeds, lengths, frequencies, etc. * Collision rates could be an improvement for `plasmapy.formulary` (especially since collision rates are often clouded in mystery) * Zoom breakouts are great for getting interactions — David's happy to help organize this * We still need to figure out how to facilitate this smoothly * Would help to name breakout rooms appropriately * Can also label the difficulty level so people know where to join * OMFIT hackathon breakout sessions got focused on different modules, and whoever was most interested would lead the discussion. It's helpful that there are known facilitators. * Another possibility: unconference sessions * Could end up being second half of the session * Days 1 & 2 could focus on essentials of git, virtual envs, conda, `astropy.units`... * Would be helpful to have a session that introduces [Conda](https://docs.conda.io/en/latest/) * Rest of the hack week could focus on informal sessions * Can website coordinators work on registration form? * Can look at last year's reg form * Should create a google drive folder for hack week, with a subfolder for each year * Use PlasmaPy's account * What is the timeline for when we send things out? * After we get the website set up. * When do we want to refresh the website? * Perhaps within next two weeks? * When should there be the registration due date? * Last year, we didn't have a due date for registering...just a due date for proposing a lightning talk * Limit presentations on packages to ≲ 10 minutes? * Not sure if it would be beneficial to have somethign that short. Perhaps 15-20 minute range? * Perhaps focus on learning the fundamentals, like `git` and how to contribute to an open source project? Less of a focus on individual packages * Good breakout session: integration between PlasamPy and OMFIT * Last year we had a social hour * Maybe this year the social hour could be transformed into an unconference hour?