Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project pages: updates for geosmart #22

Merged
merged 12 commits into from
Sep 12, 2023
3 changes: 1 addition & 2 deletions book/_toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,11 @@ parts:
- file: tutorials/example/tutorial-notebook
- caption: Projects
chapters:
- file: projects/list_of_projects
- file: projects/index
sections:
- file: projects/project_roles
- file: projects/project_roadmap
- file: projects/project_initialization
- file: projects/list_of_projects
- caption: Reference
chapters:
- file: reference/glossary
Expand Down
Binary file added book/img/new-repo.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed book/img/project-purpose.png
Binary file not shown.
Binary file removed book/img/project-roles.png
Binary file not shown.
Binary file added book/img/project-template.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed book/img/project-work.png
Binary file not shown.
Binary file added book/img/projects-montage.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
79 changes: 0 additions & 79 deletions book/projects/example_workflow.md

This file was deleted.

25 changes: 12 additions & 13 deletions book/projects/index.md
Original file line number Diff line number Diff line change
@@ -1,29 +1,28 @@
# Projects

During hackweeks we invite participants to collaborate in small group project teams (usually 5-7 people). Projects provide unique opportunities for networking, advancing research and learning new things:

```{image} ../img/project-purpose.png
:alt: diagram of the purpose of hackwek project work
:class: bg-primary mb-1
:width: 600px
:align: center
```
During hackweeks we invite participants to collaborate in small group project teams (usually 5-7 people). Projects provide unique opportunities for networking, advancing research and learning new things.

We encourage you to be creative in how you design your project work! Here are some ways people have used project time in the past:


* *focus on learning*: dive deeper into tutorial content and gain more hands on experience with new tools
* *focus on community building*: hackweeks bring people together for the first time and projects are used to build social fabric and foster open science
* *focus on research*: people often work to advance a research challenge using tools shared during the event. This often includes ongoing graduate and postgraduate investigations.
* *focus on creating new tools*: hackweeks often expose general community software needs. Projects can be the catalyst for new community libraries.

```{image} ../img/project-work.png
```{image} ../img/projects-montage.png
:alt: picture of people interacting during hackweek project work
:class: bg-primary mb-1
:width: 500px
:width: 700px
:align: center
```

## Projects from Past Events
## GeoSMART Hackweek Projects

The 2023 GeoSmart Hackweek will focus primarily on project work, with an emphasis on applications in Hydrology and Cyrosphere science. Project ideas will be shared in advance. Our goal is to have all participants connected to a project prior to the hackweek.
aaarendt marked this conversation as resolved.
Show resolved Hide resolved

Specific outcomes of the project work that would support objectives of the GeoSMART program include:

Visit our [gallery of past hackweeks](https://uwhackweek.github.io/hackweeks-as-a-service/gallery/index.html) to browse our catalog of amazing projects from previous events!
* further development of [Machine Learning use cases](https://geo-smart.github.io/usecases) that can be used by others to support learning and research progress
* expansion and refinement of existing [Machine Learning class curriculum](https://geo-smart.github.io/curriculum) so that more educational institutes can offer coursework in this area
* development of tutorials that can be used for training at subsequent GeoSMART hackweek events
* laying the foundation for a community of practice around Machine Learning in the geosciences
2 changes: 1 addition & 1 deletion book/projects/list_of_projects.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ Here is where we will be listing the projects during the {{dates}} {{ hackweek }

| Project Name (with link to GitHub repo) | slack channel | final presentation |
|:--------|:--------|:-----|
| [Snow Temperature Changes](https://github.com/snowex-hackweek/hot-pow) | [#Hot-Pow](https://snowexhackweek2021.slack.com/archives/C027RBZ9JH3) | [Video](https://youtu.be/lV3to0c_KtA) |
| | | |
18 changes: 12 additions & 6 deletions book/projects/project_initialization.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,16 +16,22 @@ Before getting started, you'll need a name for your project. A team exploring sn
We have created a GitHub template that is pre-populated with directories and a README layout the we find works well with most teams.

We encourage all teams to create a new GitHub repository within the {{hackweek}} Organization, even if it is just to point to an already-existing repository or package your team is contributing to for their project.
1. Go to: {{ '[https://github.com/`{hw}`](https://github.com/{hw})'.format(hw=hackweek) }}
1. Click the green “New” button on right side of page
1. Select the "{{hackweek}}/sample_project_repository" template
1. Use short project name
1. We recommend choosing "Public" (so other participants can follow progress). You can also select Private for now and make Public before final presentation.
* Go to: [https://github.com/geo-smart](https://github.com/geo-smart)
* Click the green “New” button on right side of page:

![new-repo-screenshot](../img/new-repo.png)

* Select the "{{hackweek}}/sample_project_repository" template:

![template-screenshot](../img/project-template.png)

* Name your repository using a short name.
* We recommend choosing "Public" (so other participants can follow progress). You can also select Private for now and make Public before final presentation.

## Create a new GitHub team within the {{hackweek}} Organization
GitHub teams provide a convenient way for you to set permissions on your project repository for groups of people, rather than having to do this for each individual on your team.

1. Go to: {{ '[https://github.com/orgs/`{hw}`](https://github.com/orgs/{hw})'.format(hw=hackweek + "/teams") }} (or click the "Teams" tab near the top of the GitHub Organization page)
1. Go to: [https://github.com/geo-smart](https://github.com/geo-smart) (or click the "Teams" tab near the top of the GitHub Organization page)
1. Click green “New team” button
1. Use your short project name for "Team name"
1. Set the team to visibility "Visible"
Expand Down
21 changes: 4 additions & 17 deletions book/projects/project_roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,25 +13,12 @@ Each project will progress through these stages:

### Weeks Before the Event

Ideally the project work begins in advance of the hackweek. As soon as you are accepted to the event we will invite you to Slack where you can begin sharing project ideas:
We will form project teams in the month prior to the hackweek. As soon as you are accepted to the event we will invite you to Slack where you can begin exploring project ideas. Organizers will be available to answer questions and to help participants get connected with a project that fits their learning objectives.

{fa}`check,text-success mr-1` Have an idea for a project? Pitch it on the hackweek Slack group #project-ideas channel

{fa}`check,text-success mr-1` If you don't yet have an idea brewing, take time to browse other ideas on Slack. Start up a conversation in a Slack thread if something catches your eye.

{fa}`check,text-success mr-1` Feel free to consult with one of the organizers if you have questions about project purpose, scope, roles and datasets.

{fa}`check,text-success mr-1` You may already have a critical mass forming. This is great! Go ahead and begin defining [project roles](project_roles) so that you can arrive at the hackweek ready to get started.

### Day 1 of the Event

We facilitate a project team formation session at the end of the first day of the event.

{fa}`check,text-success mr-1` People with project ideas will make a 1-minute pitch to the group

{fa}`check,text-success mr-1` People looking for a project are invited into small groups to learn more about existing ideas

{fa}`check,text-success mr-1` UW eScience helpers and facilitators are available to help teams get clear on size and scope of the effort
We facilitate a project team formation session on the first day of the hackweek. During this time we will finalize project goals and objectives. Hackweek organizers and facilitators will help each team set reasonable goals and develop a roadmap for task completion.
aaarendt marked this conversation as resolved.
Show resolved Hide resolved

## **Teamwork**

Expand All @@ -40,11 +27,11 @@ We facilitate a project team formation session at the end of the first day of th
* How do you work best? What level of group interaction works for you?
* What skills and background are you most excited to share with the team?
* When are you available to meet?
* set up team computing infrastructure on Slack and GitHub ([Project Initiallization](project_initialization))
* set up team computing infrastructure on Slack and GitHub ([Project Initialization](project_initialization))
* project work begins and teams have regular check-ins to chart progress
* project outputs are recorded in a GitHub repository

## **Presentations**
## **Share-Out**

* each team has 15 minutes to share what was learned, what challenges arose, what might be worth trying next
* individual contributions to the group effort are recognized and celebrated
Expand Down
40 changes: 0 additions & 40 deletions book/projects/project_roles.md

This file was deleted.

Loading