Closed BarkleyBG closed 4 years ago
mitchellhenke 8:44 AM I think future hack nights should make more time for open time for hacking. Had a couple people mention it to me and I agree. One had to leave by 8 and was disappointed they didn’t get much time to work on stuff with everything else beforehand
Draft Schedule, please let me know your thoughts.
6:00 to 6:15 - Arrival, Registration, Food Service 6:15 to 6:25 - Welcome from Code for Milwaukee 6:25 to 6:45 - Presentation (Save Questions for Q&A) 6:45 to 6:50 - Presentation Q&A 6:50 to 7:00 - Breakout Group Introductions
7:00 to 9:00 - Open Collaboration and Hacking 9:00 to 9:10 - Updates from the Groups, Next Steps Discussion, Announcements 9:30 - Hard Stop, Doors Closed and Locked
I think we should be more aggressive and aim to start hacking by ~6:30-6:40
Is it possible to have doors open at 5:45, shorten welcome, and perhaps introduce existing working groups on a presentation slide? The person leading the group can wave so anyone interested people can find them to discuss further. Any new working groups would still verbally introduce themselves.
My thoughts on starting before 6 would involve people who are further out (like Kohl's and NM in Franklin) and need to get through rush hour traffic to make it over to the event.
On Fri, Sep 20, 2019 at 9:12 AM Mitchell Henke notifications@github.com wrote:
I think we should be more aggressive and aim to start hacking by ~6:30-6:40
Is it possible to have doors open at 5:45, shorten welcome, and perhaps introduce existing working groups on a presentation slide? The person leading the group can wave so anyone interested can find them to discuss further. Any new working groups would still verbally introduce themselves.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/codeformilwaukee/hack-night-planning/issues/66?email_source=notifications&email_token=ABARPYF4KE7XYJ7RXSPQ4CLQKTK3XA5CNFSM4IYRWQOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7G2JHI#issuecomment-533570717, or mute the thread https://github.com/notifications/unsubscribe-auth/ABARPYEJMSLDT5HFR7WXIBTQKTK3XANCNFSM4IYRWQOA .
To @mitchellhenke's suggestion about existing groups. I think that can work alright, if we can get ppl to view videos and the github issues page for a project independently. --> Please help to think about how we can make that something people do (this is hard)
I also mentioned having orientation recorded, this will free up time for ppl to network at the beginning if they already watched a recording (before coming to their first hack night), free up most of the time of whichever core team member (Erin or Brian) would do the orientation, and give ppl the ability to review anything they found confusing (then they could also independently ask questions). This requires us to think about if orientation is well-developed enough for this, or if there is anything that ppl think needs to be added, changed or experimented with about it.
To @mitchellhenke's suggestion about existing groups. I think that can work alright, if we can get ppl to view videos and the github issues page for a project independently. --> Please help to think about how we can make that something people do (this is hard)
I also mentioned having orientation recorded, this will free up time for ppl to network at the beginning if they already watched a recording (before coming to their first hack night), free up most of the time of whichever core team member (Erin or Brian) would do the orientation, and give ppl the ability to review anything they found confusing (then they could also independently ask questions). This requires us to think about if orientation is well-developed enough for this, or if there is anything that ppl think needs to be added, changed or experimented with about it.
Having the orientation recorded would be a great idea. It would mean we would only have to reserve one room and can have all core team members focused at the same time. People can also complete a quiz on orientation when they are done and formally register to be a CfM member.
I'm not sure if I've thought about a videotaped orientation. I would certainly like some help in plotting out a short script for that if we go in that direction
@BarkleyBG @Aycrazy @mitchellhenke @romkedehaan @Dannycap @erinmagennis
I feel we need to call this to a vote. Please react with a thumbs-up or thumbs-down emoji (using the +:) button above).
I move that we should:
I think we should plan out what this new precanned orientation would look like, and then vote if we want to go with the new precanned version
Can we do have a working group around it?
On Mon, Sep 23, 2019 at 9:38 AM Brian G. Barkley notifications@github.com wrote:
I think we should plan out what this new precanned orientation would look like, and then cote if we want to go with the new precanned version
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/codeformilwaukee/hack-night-planning/issues/66?email_source=notifications&email_token=AAL3MU3RWGQZU7DO452QXP3QLDIFNA5CNFSM4IYRWQOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7LCPAQ#issuecomment-534128514, or mute the thread https://github.com/notifications/unsubscribe-auth/AAL3MUZEAO57SESPOQ5LJ6TQLDIFNANCNFSM4IYRWQOA .
Let's start to compile our thoughts in this document. We should consider what we want in these two items, and how we can do them. https://docs.google.com/document/d/157EWI1xyPzwiNwpnuXeBCx3dzknp13Uwvh9--2JTZoo/edit#heading=h.8evjuh8ec5yx
We will plan to discuss this in Wednesday’s phone call.
How to earn your membership badge --> whatever physical form it takes
Draft to be posted for Meetup until we finalize:
6:00 to 6:15 - Arrival, Registration, Food Service 6:15 to 6:20 - Welcome from Code for Milwaukee 6:20 to 6:40 - Presentation (Save Questions for Q&A) 6:40 to 6:45 - Presentation Q&A 6:47 to 6:57 - Breakout Group Introductions New members need to attend Orientation in a separate space before starting to contribute to CfM. Speaker will have a breakout group for discussing their presentation, ideas, detailed questions, etc. New breakout groups MUST be registered at https://forms.gle/6ZKzKj2HKG5bMq8j6 in order to receive introductory time. 7:00 to 9:00 - Open Collaboration and Hacking 9:00 to 9:10 - Updates from the Groups, Next Steps Discussion, Announcements 9:30 - Hard Stop, Doors Closed and Locked
Updating:
6:00 to 6:15 - Arrival, Registration, Food Service 6:15 to 6:20 - Welcome from Code for Milwaukee 6:20 to 6:40 - Presentation (Save Questions for Q&A) 6:40 to 6:45 - Presentation Q&A 6:45 to 7:00 - Breakout Group Introductions New members need to attend Orientation in a separate space before starting to contribute to CfM. Speaker will have a breakout group for discussing their presentation, ideas, detailed questions, etc. New breakout groups MUST be registered at https://forms.gle/6ZKzKj2HKG5bMq8j6 in order to receive introductory time. 7:00 to 9:00 - Open Collaboration and Hacking 9:00 to 9:10 - Updates from the Groups, Next Steps Discussion, Announcements 9:30 - Hard Stop, Doors Closed and Locked
I think we've nailed this
Let's be sure to invite the host/sponsor to give a 5 min talk
High-level goals
Suggestions: