Skip to content

Commit 4443715

Browse files
authored
Merge pull request #320 from emiliom/ohw24
Initial OHW24 updates in anticipation of opening of applications
2 parents b84cc25 + a06bd9f commit 4443715

6 files changed

Lines changed: 218 additions & 67 deletions

File tree

_ext/team.yaml

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ team:
3232
- OHW21 Organizer
3333
- OHW22 Organizer - Florianopolis
3434
- OHW23 Organizer
35+
- OHW24 Organizer
3536

3637
- name: Chelle Gentemann
3738
title: Senior Scientist
@@ -68,6 +69,7 @@ team:
6869
- OHW21 Organizer
6970
- OHW22 Organizer - Global
7071
- OHW23 Organizer
72+
- OHW24 Organizer - USA
7173

7274
- name: Charley Haley
7375
title: Organizational & Social Strategist
@@ -90,6 +92,7 @@ team:
9092
- OHW21 Organizer - Maine
9193
- OHW22 Organizer - Maine
9294
- OHW23 Organizer
95+
- OHW24 Organizer - USA
9396

9497
- name: Jane Koh
9598
title: Program Specialist
@@ -119,6 +122,7 @@ team:
119122
- OHW21 Organizer
120123
- OHW22 Organizer - Seattle
121124
- OHW23 Organizer
125+
- OHW24 Organizer - USA
122126

123127
- name: Paige Martin
124128
title: User Training Team Leader
@@ -132,6 +136,7 @@ team:
132136
- Website
133137
- OHW21 Organizer - Australia
134138
- OHW22 Organizer - Global
139+
- OHW24 Organizer - Australia
135140

136141
- name: Emilio Mayorga
137142
title: Senior Oceanographer
@@ -168,6 +173,7 @@ team:
168173
- OHW21 Organizer - Maine
169174
- OHW22 Organizer - Maine
170175
- OHW23 Organizer
176+
- OHW24 Organizer - USA
171177

172178
- name: Thomas Moore
173179
title: Ocean Data Analyst
@@ -178,6 +184,7 @@ team:
178184
- Steering Committee
179185
- OHW21 Organizer - Australia
180186
- OHW22 Organizer
187+
- OHW24 Organizer - Australia
181188

182189
- name: Nick Record
183190
title: Senior Research Scientist
@@ -201,6 +208,7 @@ team:
201208
- OHW21 Organizer
202209
- OHW22 Organizer - Seattle
203210
- OHW23 Organizer
211+
- OHW24 Organizer - USA
204212

205213
- name: Nick Mortimer
206214
title: Senior Engineer
@@ -214,6 +222,7 @@ team:
214222
- OHW21 Organizer - Australia
215223
- OHW22 Organizer - Australia
216224
- OHW23 Organizer
225+
- OHW24 Organizer - Australia
217226

218227
- name: Sophie Clayton
219228
title: Assistant Professor of Oceanography
@@ -270,6 +279,7 @@ team:
270279
- OHW21 Participant
271280
- OHW22 Organizer - Espanol
272281
- OHW23 Organizer
282+
- OHW24 Organizer - Australia
273283

274284
- name: Ángel Segura
275285
title: Adjunct Professor
@@ -318,6 +328,7 @@ team:
318328
# email:
319329
roles:
320330
- OHW23 Organizer
331+
- OHW24 Organizer - USA
321332

322333
- name: Ben Tupper
323334
title: Senior Research Associate
@@ -345,3 +356,4 @@ team:
345356
- Steering Committee
346357
- OHW22 Participant
347358
- OHW23 Participant
359+
- OHW24 Organizer - Australia
234 KB
Loading

index.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,17 @@ description: OceanHackWeek home
66

77
# OceanHackWeek (OHW)
88

9-
:::{admonition} Volunteer to help with OceanHackWeek 2024!
9+
:::{admonition} OceanHackWeek 2024 will be on August 26 - 30!
1010
:class: important
11+
OceanHackWeek 2024 will be an in-person event with two in-person gatherings in Maine, US and Sydney, Australia. Visit the [OHW24 event web site](ohw24/index) for more information,
12+
including updates about when applications will open!
1113

12-
OceanHackWeek 2024 will be August 26 - 30! We are recruiting Organizing Committee members, tutorial instructors, and project mentors for the event. [**Go to the OceanHackWeek 2024 page to learn more and apply.**](ohw24/index)
13-
14-
<!--
15-
```{button-link} ohw23/
14+
```{button-link} ohw24/
1615
:color: primary
1716
:expand:
18-
:tooltip: OHW23
19-
Go to OceanHackWeek 2023
17+
:tooltip: OHW24
18+
Go to OceanHackWeek 2024
2019
```
21-
-->
2220
:::
2321

2422

ohw24/applicants.md

Lines changed: 127 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,127 @@
1+
---
2+
layout: applicant
3+
# title: Information for Applicants
4+
description: OceanHackWeek (OHW) 2024
5+
permalink: applicant-info.html
6+
---
7+
8+
# Information for OHW24 Applicants
9+
10+
OceanHackWeek 2024 (OHW24) is a hands-on, interactive in-person workshop focused on data science in oceanography and fisheries that will be held on **August 26-30, 2024**. Join us for five days of tutorials, data exploration, software development and community networking!
11+
12+
```{admonition} Applications for OceanHackWeek 2024 will open soon!
13+
:class: important
14+
15+
Please come back in early June for updates. **We plan to open applications
16+
very soon.**
17+
```
18+
19+
**See the [main OHW24 page](index) for information about each of the two in-person OHW24 events, in the US and in Australia.**
20+
21+
Please see the FAQs below for answers to common questions.
22+
For additional questions, please post in our [discussions on Github](https://github.com/orgs/oceanhackweek/discussions/categories/q-a) or email
23+
<a href="mailto:info@oceanhackweek.org" target="_blank">info@oceanhackweek.org</a>.
24+
25+
---
26+
27+
## FAQs
28+
29+
### Q: I am an undergrad / first year grad / faculty / etc. Is this program right for me?
30+
31+
We welcome participants from all career stages and encourage applications from graduate students,
32+
postdocs and early career researchers. Advanced undergrad students with background in oceanography
33+
and data science are also welcome.
34+
35+
Before applying consider what you can bring to the event:
36+
by pitching a project,
37+
by your knowledge of data sets,
38+
by your programming/computational skills,
39+
by your project management skills.
40+
41+
We want you to grow/learn during the event!
42+
If in doubt,
43+
simply apply and explain your motivation for participation.
44+
45+
We expect all participants to be engaged in the team projects and focus during the week.
46+
47+
### Q: I am proficient in Matlab / other languages but have not used Python or R. Python or R has been on my list to learn. How can I make my application be stronger?
48+
49+
We plan to accept participants with diverse skill levels and backgrounds in programming.
50+
51+
However, to best benefit from and contribute to the program, participants are expected to have some experience with Python and/or R programming.
52+
53+
Applicants with an extensive programming background in other languages (e.g. Matlab) are welcome to apply,
54+
if they are willing to get up-to-date on the expected basic skills before the program.
55+
56+
Participants should familiarize themselves with the materials included in [Python novice gapminder](https://swcarpentry.github.io/python-novice-gapminder/) and [Python novice inflammation](https://swcarpentry.github.io/python-novice-inflammation/) for a Python focus, or [R novice gapminder](http://swcarpentry.github.io/r-novice-gapminder/) for an R focus. These are a good reflection of the level we expect participants to be at coming into the workshop.
57+
58+
We also encourage participants to explore more advanced topics before the hackweek. For Python, we suggest looking at one of these resources: [Pythia Foundations](https://foundations.projectpythia.org/landing-page.html), [An Introduction to Earth and Environmental Data Science](https://earth-env-data-science.github.io/intro), and [Data Carpentry - Python for Atmosphere and Ocean Scientists](https://carpentries-lab.github.io/python-aos-lesson/)
59+
60+
### Q: I don't know the first thing about version revision/control systems. Can I still apply?
61+
62+
During the hackweek we will use Git and GitHub but you are not expected to be an expert on it. In previous years we have offered refresher in the week prior to the actual OHW event. The organizing committee is deciding whether we can offer this in OHW24. You are welcome to check back here for this info, but we want to emphasize that nothing is better than trying it yourself first -- we recommend the [Software Carpentry lessons](https://swcarpentry.github.io/git-novice/) for learning git basic.
63+
64+
Note that we will require you to create a [GitHub account](https://github.com/) before completing the application.
65+
66+
### Q: I do not have any programming experience. Is the program a good opportunity to get started?
67+
68+
We believe that OceanHackWeek participants will benefit the most with some prior programming experience,
69+
and might not find the hackweek the best place to learn programming.
70+
71+
If you do not have any programming experience we encourage you to start with some local or online training.
72+
Check if your institution runs a [Software Carpentry workshop](https://software-carpentry.org/workshops/).
73+
74+
Once you have gone through some training you will have a better understanding of whether OceanHackWeek is right for you.
75+
We expect that you have basic operational knowledge of Python or R in advance of the program.
76+
77+
### Q: Do I have to be a stellar Python or R programmer to be accepted?
78+
79+
No. We aim to bring in motivated participants with a diverse range of programming skill levels.
80+
81+
### Q: I already know a lot of what you plan to cover, should I apply / will I be bored?
82+
83+
OceanHackWeek is not only a place to learn new skills but also a place to share expertise and build a community together.
84+
If you are already an expert but are interested in sharing and helping others,
85+
we welcome you to pitch project ideas,
86+
contribute to hacking,
87+
and assist other participants during the tutorials by being a teaching assistant!
88+
89+
*Please mention this in the application. Send us an email if you have any questions!*
90+
91+
### Q: I have strong computational skills but have not worked in oceanography?
92+
93+
To ensure that participants will be interested in the oceanography problems they are solving and can give back to the field later on,
94+
we require that participants have had at least some familiarity or prior experience with oceanography data.
95+
96+
### Q: I work in an ocean engineering / robotics / consulting company. Can I apply?
97+
98+
<!-- We expect participants from the private sector to pay for their own expenses. -->
99+
Yes, we welcome applications from the private sector.
100+
Make sure to explain your motivation for participation in the application form!
101+
We may hold a career panel discussion,
102+
so please mention if you are interested in participating.
103+
104+
### Q: I work in a non-US institution / organization / company. Can I apply?
105+
106+
Yes, we welcome applications from abroad for both the in-person and virtual events.
107+
108+
### Q: I was a participant in previous OceanHackWeek. Can I apply again?
109+
110+
Yes, we welcome applications from previous participants,
111+
but priority will be given to new applicants.
112+
If you are interested in assisting as a project or tutorial helper during the hackweek,
113+
please mention that in the application.
114+
115+
### Q: Am I supposed to participate in all tutorials and presentations?
116+
117+
Yes. While we understand that not all topics may be 100% relevant to you we want to maximize engagement. Note that we post the lessons and videos online later, so if you are interested in only a portion of the OceanHackWeek consider that an option rather than taking someone's spot.
118+
119+
### Q: My application was not accepted, what now?
120+
121+
Sadly resources are limited and we cannot accommodate all the applicants we would like.
122+
123+
It is important to note that a rejected application does not mean a bad one! The reasons are:
124+
125+
- The organizer tries to accommodate a good balance from novices to experts. That means a candidate may be rejected one year and accepted in another due to the different pool of applicants. Rule of thumb? Always apply again next year if possible! Also, if you believe you can contribute to the OHW as a helper instead of a student, please get in touch! We are always in need of helpers.
126+
- Another important factor that goes into the selection of candidates is the motivation paragraph in your application. Boilerplate answers or short answers like: "I want to participate" or "It is important to me" may get lower ranking than those who read the past year materials and wrote a paragraph on how the OHW can really make a difference to them. In short: be informed, be honest, be you!
127+
- Also, please refer to the FAQ question: "I am proficient in Matlab / other languages but have not used Python or R. It has been on my list to learn. How can I make my application be stronger?"

ohw24/index.md

Lines changed: 61 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,65 @@
11
# OceanHackWeek 2024 (OHW24)
22

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/ohw21-Bigelow-outing.jpg
6+
:alt: OHW21 in person, taking a break
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!
6016
:class: important
6117
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! See the [Information for Applicants](applicants) page.
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/BigelowLabs.png
28+
:alt: Bigelow Lab
29+
:width: 180px
30+
```
31+
32+
</div>
33+
<div class="col-4" style="margin-bottom: 1rem">
34+
35+
```{image} ../assets/images/apl_logo_blue.jpg
36+
:alt: UW APL
37+
:width: 180px
38+
```
39+
40+
</div>
41+
</div>
42+
43+
44+
<div>
45+
<div class="col-4" style="margin-bottom: 1rem">
46+
47+
```{image} ../assets/images/ioos_logo.jpg
48+
:alt: IOOS
49+
:width: 180px
50+
```
51+
52+
</div>
53+
54+
</div>
55+
56+
57+
58+
```{toctree}
59+
:maxdepth: 3
60+
:caption: OceanHackWeek 2024 (OHW24)
61+
:hidden:
62+
63+
Organizers <organizers>
64+
Information for Applicants <applicants>
65+
```

ohw24/organizers.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
layout: page
3+
description: Team of OceanHackWeek 2024 organizers
4+
---
5+
6+
# OceanHackWeek 2024 Organizers
7+
8+
```{ohw-team}
9+
:roles: "OHW24 Organizer*"
10+
:badges:
11+
:hide_role_badges: "OHW18 O*,OHW19 O*,OHW20 O*,OHW21 O*,OHW22 O*,OHW23 O*,*Participant*,Steering *,Tutorials,Infrastructure,Applicant Selection,Projects,Financial Planning,Website"
12+
```

0 commit comments

Comments
 (0)