Book - Simplify adding a team member

An observed challenge over the years was to add many team members to the
website at once without creating the dreaded merge conflict. This breaks
up the monolithic `team.yaml` file and has each team member fill out
their own. This hopefully makes it easier and has the nice side-effect
of reusable files across hackweeks and years.

.gitignore

@@ -12,6 +12,8 @@
 # cookiecutter webpage things
 cookiecutter.json
 /book/_build/html/assets
+## Temporary files created by build scripts
+/team/team.yaml
 
 # Byte-compiled / optimized / DLL files
 __pycache__/

cookiecutter.yaml

@@ -28,7 +28,7 @@ about:
 applicant_info: UW Hackweek 2022 will take place in October 2022 (virtual or in-person
   TBD). Applications have not yet opened, but should be anticipated in September 2022.
 team:
-  !include book/team.yaml
+  !include team/team.yaml
 schedule:
   !include book/schedule.yaml
 sponsors:

scripts/build_resources.sh

@@ -14,6 +14,7 @@ if [ -f "$YAML_FILE" ]; then
    python yaml2json.py "$YAML_FILE" "$JSON_FILE"
 fi
 
+./build_team_yaml.sh
 
 if [ -d "../book/_build/html/assets" ]; then
    rm -rf ../book/_build/html/assets

scripts/build_team_yaml.sh

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+#
+# Create one team yaml file to include with the cookiecutter.yaml
+#
+# This script is meant to be called only within the 'script' directory
+
+# Go to the team directory (silently)
+pushd ../team/ > /dev/null
+
+# Merge all individual files, excluding template and header files
+find . -type f -name '*.yaml' \
+  ! -name team.yaml ! -name team_people.yaml \
+  ! -name template.yaml ! -name header.yaml | \
+  sort | xargs -I '{}' cat '{}' > team_people.yaml
+
+# Indent to proper yaml
+sed -i 's/^/  /' team_people.yaml
+
+# Create the final team file
+cat header.yaml team_people.yaml > team.yaml
+
+# Remove temporary files
+rm team_people.yaml
+
+# Go back where we came from
+popd > /dev/null
+
+echo "Team.yaml created"
+

team/README.md

@@ -0,0 +1,17 @@
+# The team folder
+
+All members of the organizing team should add themselves to the webpage and
+this folder contains a file for each person describing themselves.
+
+## Adding a new member
+Follow these steps to add yourself:
+* Use the provided 'template.yaml' file and copy the file.
+* Rename the file to your name
+   ```
+    mv template.yaml FirstName_LastName.yaml
+   ```
+* Open the file in your favorite editor and fill out the details, 
+replacing the placeholder text.
+* Commit the file and open a pull request
+* Don't forget to add a reviewer to the pull request so they get notified.
+

team/anthony-arendt.yaml

@@ -0,0 +1,24 @@
+- title: Anthony Arendt
+  avatar: https://avatars.githubusercontent.com/u/4993098?v=4?s=100
+  role: Senior Data Science Fellow
+  organizations:
+    - name: eScience Institute
+    - name: Applied Physics Laboratory
+  bio: Anthony is leading the eScience Institute's Hackweek-as-a-Service program.
+    He is an advocate for open, inclusive and collaborative science.
+    He has experience teaching GIS and has been the lead organizer for multiple earth-science themed hackweeks.
+    His background is in cryospheric science and remote sensing.
+  expertise:
+    - open science
+    - community building
+    - GIS
+    - SQL
+    - glaciers
+    - Python
+  social:
+    - icon: github
+      icon_pack: fab
+      link: https://github.com/aaarendt
+  user_groups:
+    - Lead Hackweek Organizer
+

team/charley-haley.yaml

@@ -0,0 +1,17 @@
+- title: Charley Haley
+  avatar: https://avatars.githubusercontent.com/u/70242677?v=4
+  role: Social Strategist and Collaboration Architect
+  organizations:
+    - name: Collaboration Architect at eScience Institute
+    - name: WayForagers
+      url: https://WayForagers.org
+  bio: I am passionate about all things that are in service to building collaborations, especially interdisciplinary ones.
+    I love building frameworks that make it easier for science groups (research, applied, data, stakeholders) to understand
+    each other and how they might fit together to address the larger, more complex science challenges that are impossible to
+    touch without a community of collaborators representing all angles & all perspectives.
+  expertise:
+    - Participatory Design and facilitation
+    - Structuring productive meetings & discussions
+    - Community development
+  user_groups:
+    - Lead Community Building

team/don-setiawan.yaml

@@ -0,0 +1,25 @@
+- title: Don Setiawan
+  avatar: https://avatars.githubusercontent.com/u/17802172?v=4
+  role: Research Software Engineer
+  organizations:
+    - name: School of Oceanography
+      url: https://www.ocean.washington.edu/home/Don_Setiawan
+    - name: University of Washington
+  bio: I am a Research Software Engineer at the University of Washington with a
+    strong focus in designing, developing, and maintaining scientific data analysis
+    systems. I am a contributor to various open source software. I learning new
+    technologies and apply them in my work.
+  expertise:
+    - Geospatial Information Systems (GIS)
+    - Data Engineering / Data Science
+    - Software Engineering
+    - Web Development
+    - DevOps/GitOps
+    - Oceanography
+    - Python
+  social:
+    - icon: github
+      icon_pack: fab
+      link: https://github.com/lsetiawan
+  user_groups:
+    - Technology Specialist

team/header.yaml

@@ -0,0 +1,5 @@
+description:
+  The people on this page have helped organize the hackweek.
+  You'll find a few specializations listed per person if you're wondering who to reach out to during the event!
+
+people:

team/jessica-scheick.yaml

@@ -0,0 +1,29 @@
+- title: Jessica Scheick
+  avatar: https://avatars.githubusercontent.com/u/11756442?v=4
+  role: Research Assistant Professor
+  organizations:
+    - name: University of New Hampshire
+    - name: eScience
+  bio: Jessica is a glaciologist, remote sensing specialist, open science advocate and educator,
+    collaborative developer, open-source software contributor and maintainer, and community manager.
+    She enjoys weaving her many roles together to work with others to build software that makes it easier
+    for everyone to access and manipulate data, and she's especially fond of detecting icebergs.
+  expertise:
+    - open science
+    - collaborative development
+    - Python
+    - git
+    - GitHub
+    - glaciers
+    - ICESat-2/icepyx
+  social:
+    - icon: github
+      icon_pack: fab
+      link: https://github.com/jessicas11
+    - icon: github
+      icon_pack: fab
+      link: https://github.com/icesat2py
+  user_groups:
+    - Lead Hackweek Organizer
+    - Tutorial Lead
+    - Project Team Lead

team/joachim-meyer.yaml

@@ -0,0 +1,22 @@
+- title: Joachim Meyer
+  avatar: https://avatars.githubusercontent.com/u/178649?v=4
+  role: Senior Research Scholar
+  organizations:
+    - name: Boise State University
+  bio: >
+    Joe is a research scientist at Boise State University with a focus
+    on physical based snow modeling development and operational application.
+    He has a background in software development and would love to see more
+    software development best practices, open source software, and open science
+    principles being adapted throughout the research community.
+  expertise:
+    - Software Development
+    - Python
+    - git, GDAL, anything in the Terminal really ...
+    - Modeling
+  social:
+    - icon: github
+      icon_pack: fab
+      link: https://github.com/jomey
+  user_groups:
+    - Technology Specialist