Skip to content

Commit cddb51a

Browse files
authored
Merge pull request #67 from emiliom/openappl
config.yml updates + Application Info page
2 parents c2221ed + 5494fbd commit cddb51a

3 files changed

Lines changed: 23 additions & 35 deletions

File tree

_InstructionSiteUpdates.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ The OceanHackweek web site is a Jekyll site that uses the [Jekyll Spectral theme
66

77
Relevant, editable content is organized in the following directories and files:
88

9-
- [_config.yml](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/master/_config.yml): core Jekyll site configuration, including some banner/header/footer text and urls
10-
- [jekyll-spectral-theme/_includes](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/master/jekyll-spectral-theme/_includes) directory: front page content, broken up into sections, one markdown file per section.
11-
- The layout templates for sections and section order are controlled by [jekyll-spectral-theme/_layouts/default.html](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/master/jekyll-spectral-theme/_layouts/default.html)
12-
- Each section specifies a template for its layout, where the templates available are found in [jekyll-spectral-theme/_layouts](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/master/jekyll-spectral-theme/_layouts)
13-
- Section two ("Information for Applicants") is a special beast. While [jekyll-spectral-theme/_includes/section-02.html](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/master/jekyll-spectral-theme/_includes/section-two.html) orchestrates it, the directives there point to content to be grabbed from tags `title` and `description` in [_pages/01-applicants.md](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/master/_pages/01-applicants.md)
14-
- [_pages](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/master/_pages): content for extra pages, including all the pages accessible via the drop-down menu on the upper right of the page.
15-
- The destination page file name (what a user sees) is *not* the source markdown file name on the repository; instead, the destination file name is found in the `permalink` tag within the markdown file. For example, for [_pages/01-applicants.md](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/master/_pages/01-applicants.md), the destination file name is [applicant-info.html](https://oceanhackweek.github.io/applicant-info.html)
9+
- [_config.yml](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/source/_config.yml): core Jekyll site configuration, including some banner/header/footer text and urls
10+
- [jekyll-spectral-theme/_includes](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/source/jekyll-spectral-theme/_includes) directory: front page content, broken up into sections, one markdown file per section.
11+
- The layout templates for sections and section order are controlled by [jekyll-spectral-theme/_layouts/default.html](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/source/jekyll-spectral-theme/_layouts/default.html)
12+
- Each section specifies a template for its layout, where the templates available are found in [jekyll-spectral-theme/_layouts](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/source/jekyll-spectral-theme/_layouts)
13+
- Section two ("Information for Applicants") is a special beast. While [jekyll-spectral-theme/_includes/section-02.html](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/source/jekyll-spectral-theme/_includes/section-two.html) orchestrates it, the directives there point to content to be grabbed from tags `title` and `description` in [_pages/01-applicants.md](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/source/_pages/01-applicants.md)
14+
- [_pages](https://github.com/oceanhackweek/oceanhackweek.github.io/tree/source/_pages): content for extra pages, including all the pages accessible via the drop-down menu on the upper right of the page.
15+
- The destination page file name (what a user sees) is *not* the source markdown file name on the repository; instead, the destination file name is found in the `permalink` tag within the markdown file. For example, for [_pages/01-applicants.md](https://github.com/oceanhackweek/oceanhackweek.github.io/blob/source/_pages/01-applicants.md), the destination file name is [applicant-info.html](https://oceanhackweek.github.io/applicant-info.html)
1616

1717
Note that apparently any Markdown file dropped at the root level of the repository, or in the `_pages` directory (or possibly anywhere else?), will be automatically added to the Menu drop down; except ones with names starting with the `_` character.
1818

_config.yml

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,8 @@
22
title: Oceanhackweek 2020
33
email: oceanhackweek@uw.edu
44
description: Data Science + Oceanography<br>
5-
COVID-19 has impacted OceanHackweek 2020 plans.<br>
6-
There will be no in-person event in 2020.<br>
7-
A virtual event around August is being discussed.<br><br>
8-
<b>Please check back in early May.</b>
5+
A hands-on, interactive virtual workshop<br>
6+
August 10-14, 2020.
97

108
baseurl: "" # the subpath of your site, e.g. /blog
119
url: "" # the base hostname & protocol for your site
@@ -23,8 +21,6 @@ slack_url: https://oceanhackweek.slack.com
2321
email_url: oceanhkw@uw.edu
2422
500px_url:
2523
facebook_url:
26-
gitlab_url:
27-
googleplus_url:
2824
instagram_url:
2925
linkedin_url:
3026
pinterest_url:

_pages/01-applicants.md

Lines changed: 14 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,25 @@
11
---
22
layout: applicant
33
title: Information for Applicants
4-
description: <b>Due to COVID-19, there will be no in-person event in 2020.
5-
A virtual event around August is being discussed.
6-
Applications will open soon.
7-
Please check back in early May.</b><br><br>
4+
description: <b>Due to COVID-19, OceanHackWeek (OHW) 2020 will take place as a virtual, online event.
5+
<a href="applicant-info.html">Applications</a> close on July 13, 2020.
86

97
In OceanHackWeek we will explore the intersection of data science
108
and oceanography through tutorials and hands-on “hacking” projects.
119
To best benefit from the program, participants are expected to have some experience with Python programming and data analysis.
1210
permalink: applicant-info.html
1311
image: ohw18-hacking2.JPG
14-
1512
---
1613

17-
**Due to COVID-19, there will be no in-person event in 2020. A virtual event around August is
18-
being discussed. Applications will open soon. Please check back in early May.**
14+
OceanHackWeek 2020 is a small, hands-on, interactive virtual workshop focused on data science and oceanography that will be held during **August 10-14, 2020**. Join us for five days of tutorials, data exploration, software development and community networking!
15+
16+
**To apply, please [fill out this form](https://form.jotform.com/201774238098159) by July 13, 2020.**
17+
Accepted applicants will be notified no later than July 22, 2020.
18+
We expect to accommodate approximately 50 participants.
1919

20-
In Oceanhackweek we will explore the intersection of data science and oceanography through tutorials and hands-on “hacking” projects. In tutorials, we will learn data science tools, cloud computing, visualization, and a suite of software assets to interact with data sets of complex temporal-spatial structures or high volume. In project sessions, we will immediately put these skills to use by implementing research, computation, or visualization ideas in a group setting. To best benefit from the program, participant are expected to have some experience with Python programming and data analysis.
20+
**Formal daily activities will take place over a period of up to 3 hours per day, tentatively 10am-1pm US PDT / 1-4pm US EDT / 17:00-20:00 UTC.** Formal daily activities includes tutorials and project check-in with the entire group, but excludes actual project time.
21+
22+
For additional questions, please email <a href="mailto:oceanhkw@uw.edu" target="_blank">oceanhkw@uw.edu</a>.
2123

2224
---
2325

@@ -32,52 +34,42 @@ To stay up to date on the current impact of the coronavirus emergency and govern
3234
see the US Federal web site <a href="https://www.coronavirus.gov">https://www.coronavirus.gov</a>
3335
and your state and local positions.
3436

35-
3637
**Q: I am an undergrad / first year grad / faculty / etc. Is this program right for me?**
3738

3839
We welcome participants from all career stages. We strongly encourage applications from graduate students, postdocs and early career researchers. There are different ways to contribute to the event: by pitching a project, by your knowledge of data sets, by your computational skills, by your project management skills. We want you to grow/learn during the event! We expect all participants to be engaged in the team projects and focus during the week. If in doubt, simply apply and explain your motivation for participation.
3940

40-
4141
**Q: I am proficient in Matlab / R / other languages but have not used Python. It has been on my list to learn. How can I make my application be stronger?**
4242

4343
We want to build an inclusive Oceanography community regardless of people’s language of choice and programming level. Since the event is only one week long, the tutorials will be presented in one language (Python), and participants will benefit the most if they have basic familiarity with this language. We expect that you have gone through the [Software Carpentry Python tutorial](http://swcarpentry.github.io/python-novice-gapminder) to get familiar with the syntax in advance of the program. The more experience you can obtain before the beginning of the program, the easier it will be to follow the tutorials and contribute to the projects.
4444

45-
4645
**Q: I do not have any programming experience. Is the program a good opportunity to get started?**
4746

4847
We believe that Oceanhackweek participants will benefit the most with some prior programming experience, and might not find the hackweek the best place to learn programming. If you do not have any programming experience we encourage you to start with some local or online training. Check if your institution runs a [Software Carpentry workshop](https://software-carpentry.org/workshops/), or try learning by going through the [Python Novice Lesson](http://swcarpentry.github.io/python-novice-gapminder).
4948

5049
Once you have gone through some training you will have a better understanding of whether Oceanhackweek is right for you. We expect that you have basic operational knowledge of Python in advance of the program.
5150

52-
5351
**Q: Do I have to be a stellar Python programmer to be accepted?**
5452

55-
No, we aim to bring in motivated participants with a range of programming skills levels, but we do require basic familiarity with Python (see above) so that you will be able to learn and have fun in the tutorials and hack project time!
56-
53+
No, we aim to bring in motivated participants with a range of programming skills levels, but we do expect basic familiarity with Python (see above) so that you will be able to learn and have fun in the tutorials and hack project time!
5754

5855
**Q: I already know a lot of what you plan to cover, should I apply / will I be bored?**
5956

6057
Oceanhackweek is not only a place to learn new skills but also a place to share expertise and build a community together. If you are already an expert but are interested in sharing and helping others, we welcome you to pitch project ideas, contribute to hacking, and assist other participants during the tutorials by being a teaching assistant! Please mention this in the application. Send us an email if you have any questions!
6158

62-
6359
**Q: I have strong computational skills but have not worked in oceanography?**
6460

6561
To ensure that participants will be interested in the oceanography problems they are solving and can give back to the field later on, we require that participants have had at least some familiarity or prior experience with oceanography data.
6662

67-
6863
**Q: I work in an ocean engineering/robotics/consulting company. Can I apply?**
6964

70-
Make sure to explain your motivation for participation in the application form! We expect participants from the private sector to pay for their own expenses. We will hold a career panel discussion, so please mention if you are interested in participating.
71-
65+
Make sure to explain your motivation for participation in the application form! We may hold a career panel discussion, so please mention if you are interested in participating.
7266

7367
**Q: I work in a non-US institution / organization / company. Can I apply?**
7468

75-
Yes, we welcome applications from abroad. However please note that we are constrained by the amount of funding we could provide for people who travel internationally.
76-
69+
Yes, we welcome applications from abroad.
7770

78-
**Q: I was a participant in Oceanhackweek last year. Can I apply to again?**
71+
**Q: I was a participant in a previous Oceanhackweek. Can I apply again?**
7972

8073
Yes, we welcome applications from previous participants, but priority will be given to new applicants. If you are interested in being a TA (teaching assistant) during the hackweek, please mention that in the application.
8174

82-
8375
---

0 commit comments

Comments
 (0)