| Time |
Item |
Goal |
Method |
Structured Invitation |
Facilitator |
| 8:00 - 8:30 (5 min) |
Set Up |
Prepare the physical space, test technology |
|
|
Everyone |
| 8:30 - 8:35 (5 min) |
Introduction |
Welcome everyone to the meeting, introduce the organizing committee |
|
|
Freidrich |
Express gratitude to:
- participants for joining us, taking a full week out of their busy schedules
funding agencies who support all of this happening
- the organizing team for dedication to our mission and hard work to develop content
Before we get started, some initial logistics
- we officially cannot bring any food or drink into this room
- Coffee breaks each day at 10 am and 3 pm
- Lunch
- Bathrooms: just outside to the right
- After hours: building locks at 7 pm
- Tutorials are being recorded
- Happy hour this evening
|
| 8:35 - 8:45 (10 min) |
Icebreaker |
Begin to connect with one another and get a sense of what brought people here. |
Small group sharing |
“What do you hope to get from and give to this learning community in the coming week?” |
Anthony |
| 8:45 - 8:50 (5 min) |
What is a hackweek? |
Talk about the hackweek model, history of the hackweek, success of the education model |
Presentation |
|
Rob |
You might be wondering, what is a hackweek? Some brief history:
- Hackweeks were designed 5 years ago at eScience
- The idea was to blend teaching with open project time
- Review our overall mission common across all hackweeks
- We can realize our mission only when we create the conditions for a positive learning environment
- As an organizing committee, it is our responsibility to create and sustain this environment so that each of you can do whatever learning you need to do this week
- Next we will discuss our shared principles and code of conduct that are the foundation of creating this learning community
|
| 8:50 - 8:55 (5 min) |
Norms of Behavior: explained |
Set the parameters of our learning community and develop a set of shared principles about how we intend to show up this week. |
Presentation |
Distribute norms of behavior handout. Instructors alternate reading through each one. |
Shay |
| 8:55 - 9:15 (10 min) |
Norms of Behavior: integration |
Invite participants to actively engage with the norms of behavior |
Partner share |
4 minutes: turn to your partner: “which of these norms most resonates for you?”
4 minutes: turn to a different partner: “Which of these norms is most challenging to you?”
|
Shay and Anthony |
| 9:15 - 9:20 (5 min) |
reminder about peer-learning |
|
Presentation |
|
Joe |
- As we transition into our first tutorial, let’s return to one of the core missions of our hackweek: peer learning
- One very unique component of hackweeks is that we intentionally maximize diversity in who we accept to the program. That includes disciplinary diversity. Folks in this room come from a wide variety of fields, each with their own technological tools and vocabularies.
- Therefore,everyone approaches these tutorials with their own particular combination of disciplinary and data science knowledge. Material could be overwhelmingly new, or in some cases you may have already mastered it in your own training. Most people will reside somewhere in the middle of that spectrum.
- We therefore encourage you to help each other along in your learning journey. If you already have some material mastered, this could be an opportunity for you to teach others in the room who may not have encountered this material yet.
|
| 9:20 - 10:30 |
Tutorial |
Missing Maps |
Tutorial |
|
Chase |
| 10:30 - 11:00 |
Coffee Break (30 min) |
| 11:00 - 12:00 |
Tutorial |
Git and GitHub |
Tutorial |
|
Ben |
| 12:00 - 1:00 |
Lunch (60 min) |