rename with lower case

docs/roles/collaboration-architect.md

@@ -0,0 +1,21 @@
+![Collaboration Architect](../images/collaboration-architect.svg) 
+
+## Collaboration Architect
+The Collaboration Architect is experienced in developing community-building strategies that amplify inclusion, co-mentoring, and collaboration. They identify the barriers that inhibit engagement and contribution, and they develop structured interactions that enhance the participant’s learning experience.
+
+### Goals
+- Reduce the degree of overwhelm and social anxiety that emerges when learning and practicing new skills with new people in a compressed timeframe.
+- Foster inclusive and generative teamwork.
+- Encourage and support early career participants to step out of their comfort zone to take on leading a project team.
+
+### Specific Activities
+*Pre-hackweek*
+- Facilitate collaborative discussions about the portfolio of tutorials and their content.
+- Train/coach Project Coordinator and Helpers.
+
+*Hackweek*
+- Facilitate participant interaction.
+- Facilitate participants moving through the project formation phases i.e., ideation, pitching, co-shaping/scoping, and selection.
+
+*Post Hackweek*
+- Gather feedback, insights, and ideas from the organizing team, participant focus group, and survey responses and identify areas for improvement.

docs/roles/community-lead.md

@@ -0,0 +1,20 @@
+![Community Lead](../images/community-lead.svg)
+## Community Lead
+The Community Lead guides the activities of community members engaged in hackweek organization and execution. This is typically the person who contacted eScience requesting a hackweek.
+
+Depending on the structure of the event, this role may be filled by a member of the eScience Institute core team, or by a community member looking to lead their own hackweek. In either case, the scope of the goals and activities below remains the same.
+
+### Goals
+- Matching the technical and scientific needs of the community to the design of the hackweek.
+- Ensuring everyone involved is sufficiently resourced to carry out the work.
+- Strategizing on how best to implement practices of open-source science within this community.
+- Building supportive partnerships and communities of practice before, during, and after the hackweek.
+
+### Specific Activities
+- Acquire funding to support hackweek activities.
+- Work with the community to define the overarching goals of the hackweek.
+- Build a diverse, inclusive, and equitable hackweek organizing team; recruit broadly for organizers and participants.
+- Help organize and attend event planning meetings.
+- Review tutorial content, evaluating meeting hackweek goals, learning objectives, and community relevance.
+- Attend the hackweek and be available to assist with project and tutorial work.
+- Facilitate and/or lead longer-term community efforts to build on collaborations fostered around the hackweek.

docs/roles/escience-institute-roles.md

@@ -0,0 +1,53 @@
+![eScience Roles](../images/escience-roles.svg)
+## eScience Institute Roles
+The roles outlined below are unique to the eScience Institute and perform specific tasks related to the hackweek events hosted by the University of Washington. For organizers looking to host their own hackweek events, these roles have been included below to provide insight into some of the support roles a group may wish to consider if running their own event.
+
+--------
+
+## Program Manager
+The Program Manager is experienced in organizational management and event planning. They act as main logistical point of contact for participants and organizers of the hackweek.
+
+### Goals
+- Ensuring organizers and participants have access to the resources they need to design and host the hackweek.
+- Advertizing hackweek opportunities to community members, with a focus on underrepresented groups.
+- Creating hackweek learning spaces that align with our mission and values.
+
+### Specific Activities
+- Connect with prospective hackweek clients to communicate details of our program.
+- Oversee recruitment and selection process for each hackweek.
+- Organize the event planning and logistics.
+- Assist with program evaluation.
+
+--------
+
+## Budget Manager
+The Budget Manager has experience with university funding policies and the specific requirements of organizations who support our hackweeks.
+
+### Goals
+- Assisting team members to develop realistic cost estimates for hackweek activities and expenses.
+- Ensuring team activities and expenditures align with the requirements of funding agencies.
+
+### Specific Activities
+- Notify hackweek organizers of potential funding sources.
+- Facilitate budgeting conversations.
+- Create a budget and scope of work.
+- Allocate funds to cover hackweek activities and expenses.
+
+--------
+
+## Education Consultant
+The Education Consultant has experience with designing curriculum and creating positive learning spaces for data science education.
+
+### Goals
+- Helping all participants feel able to intellectually engage in the educational and project spaces at hackweeks.
+- Helping tutorial leads build content that is effective for participants across a wide range of backgrounds and experience levels.
+
+### Specific Activities
+- Offer a series of tutorials to hackweek organizers for best practices in data science pedagogy.
+- Facilitate peer feedback sessions for hackweek tutorial leads as they develop content.
+- Offer tutorials during the hackweek to teach participants about strategies for teamwork and collaboration.
+- Provide content editing with a pedagogical lens for tutorial leads as they develop written content.
+
+--------
+
+

docs/roles/project-consultant.md

@@ -0,0 +1,17 @@
+![Project Consultant](../images/project-consultant.svg)
+## Project Consultant
+The Project Consultant has a big-picture view of the possible scope of projects for the hackweek community, and helps participants get clear on project ideas and objectives.
+
+### Goals
+- Communicating the purpose and approach of small group collaborations.
+- Shaping community ideas into well-defined and realistic project designs.
+- Creating a welcoming space for participants to engage in project ideation and completion.
+
+### Specific Activities
+- Post information on Slack to participants about the structure and purpose of hackweek projects.
+- Encourage participants to pitch project ideas before the hackweek.
+- Assemble and make sense of project ideas.
+- Guide the formation of project teams on the first day of the hackweek.
+- Facilitate small group collaborations during the hackweek.
+- Assist teams in setting goals and sharing results.
+- Provide guidance to teams who wish to remain connected after the hackweek.

docs/roles/project-lead.md

@@ -0,0 +1,15 @@
+![Project Lead](../images/project-lead.svg)
+## Project Lead
+Project Leads have an interest in guiding small teams in their progress toward hackweek project goals. Usually the project lead is the person who pitches a project idea.
+
+### Goals
+- Supporting all team members in getting something valuable out of their time during hackweek project work.
+- Fostering collaboration within a small team.
+- Laying the foundation for long-term project development after the hackweek is complete.
+
+### Specific Activities
+- Pitch an idea for a project.
+- Gather a team and help each person get clear on their individual goals during the project work.
+- Facilitate relationship-building and development of collaborative structures among the team.
+- Help everyone design project work that is within the scope of the hackweek.
+- Lead daily standup team check-ins.

docs/roles/technical-roles.md

@@ -0,0 +1,35 @@
+![Technical Lead](../images/technical-helper.svg)
+## Technical Lead
+The Technology Lead is experienced with the computational platforms that support hackweek collaboration and learning.
+
+### Goals
+- Empowering hackweek organizers to follow best practices in creating open source learning materials.
+- Ensuring shared hackweek tools are accessible to everyone.
+- Guiding workflow development to be reproducible and deployable on multiple infrastructures.
+
+### Specific Activities
+- Set up a shared computational environment, either on premises or via a contract with an independent provider.
+- Deploy the hackweek website.
+- Teach hackweek organizers how to use GitHub and JupyterHub for planning and design of the hackweek.
+- Assist tutorial leads in uploading their notebooks and sample datasets.
+- Help participants gain access to shared resources.
+- Archive hackweek outcomes using digital object identifiers.
+- Conduct research on emerging technology solutions.
+- Provide consultation on computational needs that evolve after a hackweek.
+
+--------
+
+## Technical Helper
+Technical Helpers have knowledge of data or domain science tools and methods that they wish to share with their peers. Helpers can include eScience staff, community members and hackweek participants.
+
+### Goals
+- Helping hackweek participants move past stuck points and complete learning objectives.
+- Including all participants in the learning process.
+- Empowering learners to connect with external educational resources.
+
+### Specific Activities
+- Answer questions from participants during the teaching of tutorials.
+- Help participants access resources needed to address specific problems.
+- Host office hours to offer guidance on specific data science or domain topics.
+- Participate in project teams and assist with technical questions.
+- Offer feedback to tutorial developers based on participant experiences with the materials.

docs/roles/tutorial-lead.md

@@ -0,0 +1,16 @@
+![Tutorial Lead](../images/tutorial-lead.svg)
+
+## Tutorial Lead
+Tutorial Leads use their knowledge of data science tools and methods to create online learning materials and teach tutorials during the hackweek.
+
+### Goals
+- Fostering the learning and development of community members on topics of interest at the hackweek.
+- Supporting the design of a shared open source curriculum.
+
+## Specific Activities
+- Define learning outcomes that are tailored to community needs.
+- Build new skills in data science pedagogy.
+- Offer feedback to peers on tutorial design.
+- Create interactive tutorials in Jupyter Notebooks.
+- Use GitHub to share tutorial content in an open source environment.
+- Teach or assist with teaching tutorials during the hackweek.