Update Roles and Mentor and Helper Guide

_quarto.yml

@@ -39,8 +39,8 @@ website:
           - text: Guides
           - href: about/projects-overview.qmd
             text: Projects Overview
-          - href: about/mentor-guide.qmd
-            text: Project Mentor Guide
+          - href: about/helper-guide.qmd
+            text: Project Mentor and Helper Guide
           - href: about/instructor-guide.qmd
             text: Tutorial Instructor Guide
           - href: about/facilitator-guide.qmd

about/mentor-guide.qmd → about/helper-guide.qmd

@@ -1,13 +1,17 @@
 ---
-title: "Project Mentor Guide"
+title: "Project Mentor and Helper Guide"
 ---
 
+Everyone is expected to actively participate during the hackathon to support project teams. We are assigning Mentor and Helper roles for project ideation & work time so that everyone – planning team and participants – know what to expect and who to ask when help is needed.
+
+The [Roles](roles.qmd) page has an overview of the Mentor and Helper roles, and this guide is to give you more ideas to help you effectively support teams in their projects.
+
 This guide is adapted from [Ocean Hackweek](https://oceanhackweek.org/resources/organizing/project-mentor-guide.html). 
 
-- A project mentor can also propose a project idea and lead it. But the priority should be on enabling leadership and collaborative work by participants themselves. The project mentor shouldn't be the center of attention.
+- Project Mentors will be very active in the project ideation, pitching, and organization phase, and can even propose project ideas. Once projects get underway the priority for both Mentors and Helpers should be on enabling leadership and collaborative work by participants themselves. The project mentor shouldn't be the center of attention.
 - Monitor participation by *everyone*, to mitigate situations where extroverts dominate discussions or introverts don't feel comfortable to participate. Suggest ways to rebalance participation so that everyone feels they have something to contribute.
 - Provide scientific advisory support. Serve as a resource. Ideally the project will be in your broader scientific domains, but it's not really necessary.
 - Provide technical advisory support. Serve as a resource for Python, R, git/GitHub, sources of relevant data, analytical or data processing methods, etc. Help the team arrive at solutions to specific challenges.
 - When you can't help directly, help them seek help elsewhere in the ESA EarthCODE community. Link to other helpers or participants who may have relevant expertise.
-- Maintain regular communication with project team via a Slack channel, in person (as appropriate) and GitHub issues and PR discussions.
+- Maintain regular communication with project team via a Slack channel, in person, and through GitHub issues and PR discussions.
 - Be a resource for the preparation of project presentations. Make suggestions if the team is stuck because the different strands of a project are not coming together semi cleanly.

about/roles.qmd

@@ -3,15 +3,15 @@ title: "Hackathon Roles"
 ---
 
 There are many roles required to envision, organize, and execute a successful hackathon. This page defines roles for the planning team and helpers.
-While we define discrete roles here, everyone is expected to actively participate to support project teams. You might embed in a team. More likely you will be needed to move between teams as needed. Take 15 minutes to sit alongside them and listen. The idea is for you to get a sense of how they are doing. Are they struggling? Ask a powerful question to help them see what they need. Bring in someone who might be able to help, like a Technical Helper or Project Consultant.  
+While we define discrete roles here, everyone is expected to actively participate to support project teams. You might embed in a team. More likely you will be needed to move between teams as needed. Take 15 minutes to sit alongside them and listen. The idea is for you to get a sense of how they are doing. Are they struggling? Ask a powerful question to help them see what they need. Bring in someone who might be able to help, like another Helper or Project Mentor.  
 
 The roles described here are lightly modified from those outlined in the [eScience Hackweek Guide](https://guidebook.hackweek.io/intro.html).
 
 
-## Project Consultant 
+## Project Mentor 
 
-The Project Consultant has a big-picture view of the possible scope of projects for the hackathon community, and helps participants get clear on project ideas and objectives. 
-See the [Project Guide](projects-overview.qmd) for more information on projects, and the [Helper Guide](mentor-guide.qmd), as project consultants will also help teams with projects. This role will primarily be Cluster Leads as well as the organizing team.
+The Project Mentor has a big-picture view of the possible scope of projects for the hackathon community, and helps participants get clear on project ideas and objectives. Domain expertise is key during project initiation, and Mentors will use their expertise to help guide teams to shape ideas into well-defined and realistic project designs.
+See the [Project Guide](projects-overview.qmd) for more information on projects, and the [Helper Guide](helper-guide.qmd), as project mentors will also help teams with projects throughout the hackathon.
 
 ### Goals
 
@@ -25,6 +25,7 @@ See the [Project Guide](projects-overview.qmd) for more information on projects,
 - Suggest project ideas.
 - Assemble and make sense of project ideas.
 - Guide the formation of project teams on the first day of the hackathon.
+- Assist individuals and teams in preparing project pitches.
 - Facilitate small group collaborations during the hackathon.
 - Assist teams in setting goals and sharing results.
 - Provide guidance to teams who wish to remain connected after the hackathon.
@@ -33,7 +34,7 @@ See the [Project Guide](projects-overview.qmd) for more information on projects,
 
 ## Project Helpers
 
-Helpers have knowledge of data or domain science tools and methods that they wish to share with their peers, or they may have facilitation skills to help keep project teams well-scoped, organized, and inclusive. See the [Helper Guide](mentor-guide.qmd) for more details. They can include ESA staff, community members and hackathon participants. 
+Helpers have knowledge of data or domain science tools and methods that they wish to share with their peers, or they may have facilitation skills to help keep project teams well-scoped, organized, and inclusive. See the [Helper Guide](helper-guide.qmd) for more details. They can include ESA staff, community members and hackathon participants. 
 
 ### Goals
 
@@ -53,7 +54,7 @@ Helpers have knowledge of data or domain science tools and methods that they wis
 
 ## Community Leads
 
-The Community Leads guide the activities of community members engaged in hackathon organization and execution. This role has been shared by the organizing team, with Openscapes as primary lead.  
+The Community Leads guide the activities of community members engaged in hackathon organization and execution. This role is shared by the organizing team, with Openscapes as primary lead.  
 
 ### Goals