|
1 | 1 | # OceanHackWeek 2024 (OHW24) |
2 | 2 |
|
3 | | -**Passionate about data science in oceanography, love collaborative project work and interested in helping organize & host OceanHackWeek 2024? Please read on!** |
4 | | - |
5 | | -**We are recruiting Organizing Committee members, tutorial instructors, and project mentors for OceanHackWeek 2024!** |
6 | | - |
7 | | -We are currently recruiting three different roles: |
8 | | - |
9 | | -- **Organizing Committee members**, who oversee organizing all aspects of the workshop including planning the schedule, selecting tutorials, applicant review and selection, cyberinfrastructure decisions, and logistics. |
10 | | -- **Tutorial instructors**, who will deliver tutorials live during the workshop. |
11 | | -- **Project mentors**, who mentor the project team during the workshop. Mentors may bring initial project ideas for participants to brainstorm further toward setting up a project, or serve as mentors for project ideas proposed by participants themselves. |
12 | | - |
13 | | -**OceanHackWeek 2024 will be August 26th - 30th.** We will have two in-person events, held at Bigelow Laboratory for Ocean Sciences in Maine, US, and in Australia (location TBD). We are working on securing more funding to support project mentors and tutorial instructors to attend the in-person event, but currently we are unsure of the level of available funding. We ask you to consider your interest with this caveat in mind. |
14 | | - |
15 | | -## Further details for each role |
16 | | - |
17 | | -### Organizing Committee members |
18 | | - |
19 | | -- Key responsibilities |
20 | | - - Work collaboratively to plan and organize the workshop. The following is a non-exhaustive list of tasks typically carried out by the Organizing Committee: |
21 | | - - Develop the schedule, deciding on the balance of tutorials and project work |
22 | | - - Promote and advertise OHW |
23 | | - - Select participants |
24 | | - - Set up the cyberinfrastructure to support the event |
25 | | - - Recruit helpers (instructors, project mentors, general helpers) |
26 | | - - Distribute and promote post event surveys |
27 | | - - The Organizing Committee uses a distributed leadership model with task groups focused on: event coordination, participant application/selection, communication, tutorials, projects, cyberinfrastructure. Organizing Committee members are expected to participate in at least 1 and at most 3 task groups. |
28 | | - - Prepare for and conscientiously participate in Organizing Committee and task group meetings and activities. |
29 | | - - Support OHW's [mission & vision](../about/index). |
30 | | - - Exemplify OHW's [Code of Conduct](../about/code-of-conduct). |
31 | | -- Time commitment |
32 | | - - The Organizing Committee meets for approximately 6 months, starting in March. Initially, the Committee will meet every 2 weeks, until 2 months before the event, when they will switch to weekly meetings. The Committee will also hold a debrief meeting after the event and look at post event survey results. |
33 | | - - The Organizing Committee members do not need to attend the in-person event. |
34 | | - |
35 | | -### Tutorial instructors |
36 | | - |
37 | | -- Key responsibilities |
38 | | - - Develop an executable tutorial approximately 45 minutes to 1 hour in length |
39 | | - - Upload the tutorial materials to the OHW GitHub and work with the OHW Cyberinfrastructure task group to validate environment requirements |
40 | | - - Test the tutorial on the OHW JupyterHub to ensure participants can actively follow along. |
41 | | -- Time commitment |
42 | | - - Deliver the tutorial live during OHW (either virtually or in-person). |
43 | | - |
44 | | -### Project mentors |
45 | | - |
46 | | -- Key responsibilities |
47 | | - - Encourage and guide the project team to ensure participation by every team member: e.g., mitigate situations where extroverts dominate discussions, suggest ways to balance tasks so that everyone feels they have something to contribute |
48 | | - - Facilitate project team communication |
49 | | - - Monitor and guide the project team's use of GitHub issues and pull requests |
50 | | - - Guide the participants in preparing the final project presentation, especially if the team is stuck because the different strands of a project are not coming together semi cleanly. |
51 | | - - Provide technical advisory support and help connect participants to others in the OHW community (organizers, instructors, other participants, etc.) who may have relevant expertise. |
52 | | - - Provide scientific advisory support if the proposed project is in your broader scientific domains. |
53 | | -- Time commitment |
54 | | - - Attend weekly Organizing Committee meetings for the month before the event. |
55 | | - - Be present for the full workshop. |
56 | | - - Participate in a post workshop debrief. |
57 | | - |
58 | | - |
59 | | -:::{admonition} Apply to help with OceanHackWeek 2024! |
| 3 | +OceanHackWeek 2024 (OHW24) will be held on **August 26-30, 2024** as two in-person events, in East Boothbay, Maine, US and in Sydney, Australia. The US in-person event will take place at the [Bigelow Laboratory for Ocean Sciences](https://www.bigelow.org). |
| 4 | + |
| 5 | +```{image} ../assets/images/ohw_hacking/ohw19-hacking.JPG |
| 6 | +:alt: OHW19 in person, hacking |
| 7 | +:width: 230px |
| 8 | +:align: left |
| 9 | +``` |
| 10 | + |
| 11 | +The events will be all-day workshops (approximately 9am - 5pm). Join us for five days of hands-on tutorials, data exploration, software development, presentations, collaborative hack projects and community networking! |
| 12 | + |
| 13 | +See the [OHW23 program](https://oceanhackweek.org/ohw23/) (a hybrid event) to get a better sense of the usual activities and how they're organized. |
| 14 | + |
| 15 | +```{admonition} Applications will open soon! |
60 | 16 | :class: important |
61 | 17 |
|
62 | | -Please [apply here](https://share.hsforms.com/1wW5CSVglSJyqAyG_EV3vXwe5s09). We will start reviewing applications **on March 11th**. Please direct any questions to <a href="mailto:info@oceanhackweek.org" target="_blank">info@oceanhackweek.org</a>. |
63 | | -::: |
| 18 | +Please come back in early June for updates! |
| 19 | +``` |
| 20 | + |
| 21 | + |
| 22 | +## OHW24 Sponsors |
| 23 | + |
| 24 | +<div class="row"> |
| 25 | + <div class="col-4" style="margin-bottom: 1rem"> |
| 26 | + |
| 27 | +```{image} ../assets/images/eScience_square_logo.jpg |
| 28 | +:alt: UW eScience |
| 29 | +:width: 150px |
| 30 | +``` |
| 31 | + |
| 32 | + </div> |
| 33 | + <div class="col-4" style="margin-bottom: 1rem"> |
| 34 | + |
| 35 | +```{image} ../assets/images/BigelowLabs.png |
| 36 | +:alt: Bigelow Lab |
| 37 | +:width: 180px |
| 38 | +``` |
| 39 | + |
| 40 | + </div> |
| 41 | + <div class="col-4" style="margin-bottom: 1rem"> |
| 42 | + |
| 43 | +```{image} ../assets/images/apl_logo_blue.jpg |
| 44 | +:alt: UW APL |
| 45 | +:width: 180px |
| 46 | +``` |
| 47 | + |
| 48 | + </div> |
| 49 | +</div> |
| 50 | + |
| 51 | + <div class="col-4" style="margin-bottom: 1rem"> |
| 52 | + |
| 53 | +```{image} ../assets/images/ioos_logo.jpg |
| 54 | +:alt: IOOS |
| 55 | +:width: 180px |
| 56 | +``` |
| 57 | + |
| 58 | + </div> |
| 59 | + |
| 60 | +</div> |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +```{toctree} |
| 65 | +:maxdepth: 3 |
| 66 | +:caption: OceanHackWeek 2024 (OHW24) |
| 67 | +:hidden: |
| 68 | +
|
| 69 | +Organizers <organizers> |
| 70 | +<!-- Information for Applicants <applicants> --> |
| 71 | +``` |
0 commit comments