From 7f9fe6355ae9fcea6e0dff7b59da8eedd61727c3 Mon Sep 17 00:00:00 2001 From: Mia Diewald Date: Wed, 5 Nov 2025 12:36:48 -0500 Subject: [PATCH 1/2] Student Ambassadors CURIOSS Pattern --- Student-Ambassadors.md | 55 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 Student-Ambassadors.md diff --git a/Student-Ambassadors.md b/Student-Ambassadors.md new file mode 100644 index 0000000..345318d --- /dev/null +++ b/Student-Ambassadors.md @@ -0,0 +1,55 @@ + +# GW OSPO Student Ambassador Program + +# Pattern Summary + +A paid student ambassador program that empowers undergraduate and graduate students to promote open source engagement, events, and projects across the university. + + # Problem + +Many universities, including George Washington University, are developing Open Source Program Offices (OSPOs) to foster a culture of collaboration and innovation; however, they struggle to connect directly with students. Students comprise an essential part of the academic community. Still, engagement can be challenging for academic offices due to the consistent presence, peer-to-peer outreach, and relevant campus projects that it entails. As it stands now, faculty and staff may have limited time for outreach, and communication directly from an academic institution can feel distant, inaccessible, or otherwise miss the mark when it comes to connecting students. Without active engagement, awareness of open source opportunities remains low, and participation in OSPO initiatives is limited. The challenge is to build consistent, authentic connections with students while advancing the OSPO’s technical and community goals. + + # Pattern Category + +* Awareness +* Community Building +* Education & Skills +* Open Source Development +* Open Source Discovery +* Promoting Best Practices + +# Context + +This pattern applies to university OSPOs seeking to strengthen their connections with students and build a culture of open-source participation on campus. It is particularly effective at institutions where OSPOs are newly established or lack full-time staff dedicated to outreach. The approach works best when there is administrative support for paid student positions and when project goals align with both educational and open-source values. + +# Forces + +* OSPO staff often have limited abilities to maintain regular contact with students. +* Students respond more positively to peer-led initiatives than to top-down institutional messaging. +* Effective outreach requires both technical expertise and social engagement skills. +* Consistent student involvement must be balanced with academic workloads and turnover. +* Funding and measurable outcomes are necessary to justify continued university support. + +# Solution + +Create a Student Ambassador program within the OSPO consisting of a small team of paid students; two graduate students working 20 hours per week and two undergraduates working 10 hours per week. A combination of both graduate and undergraduate ambassadors enables broader coverage across academic levels, strengthens continuity over semesters, and meets OSPO workload requirements. These ambassadors serve as liaisons between the OSPO and the student body in the following ways: + +* Hosting and tabling at campus events to raise open source awareness +* Organizing community-building activities such as movie nights or coding sessions +* Creating and managing OSPO social media accounts to share updates and opportunities +* Leading or contributing to open source technical projects that advance university OSPO goals +* Gathering student feedback and communicating emerging needs to OSPO leadership + +# Resulting Context: + +Implementing this pattern creates a visible, student-led initiative for the OSPO on campus. The ambassadors increase awareness and participation in open-source initiatives while also delivering tangible technical outcomes. At GW, early results have demonstrated increased event attendance, successful launches of social media channels, and ongoing student-led technical projects aimed at promoting open-source use across departments. Challenges lie in maintaining consistent engagement as students graduate and ensuring sustained funding for paid positions; however, the benefits of authentic outreach and student leadership outweigh these concerns. + +# Known Instances + +* **The George Washington University OSPO:** Two graduate and two undergraduate student ambassadors work part-time alongside OSPO staff to promote open source awareness, organize events, and contribute to open source infrastructure at GW. +* **University of Vermont, Open Research Community Accelerator (ORCA):** Run by the University of Vermont’s OSPO (VERSO), [ORCA](https://verso.w3.uvm.edu/orca/) connects undergraduate students with faculty, graduate researchers, and local partners to create open-source tools that extend the reach and impact of academic research. Students work in small “Pods” of 4–5 members, gaining real-world experience in open-source development while translating research outputs into accessible, community-focused applications. The program strengthens open research practices and cultivates workforce-ready skills in open source. + + +# Contributors & Acknowledgements + +Mia Diewald (George Washington University OSPO) [https://orcid.org/0009-0005-8123-1832](https://orcid.org/0009-0005-8123-1832) From 5cd505483f82e9154fef8b420b801e2cc6c3c45d Mon Sep 17 00:00:00 2001 From: Ciara Flanagan <101422261+CiaraFlanagan@users.noreply.github.com> Date: Mon, 10 Nov 2025 21:30:19 +0000 Subject: [PATCH 2/2] Update Student-Ambassadors.md Updated format for consistency with other patterns. --- Student-Ambassadors.md | 73 +++++++++++++++++++++++++++--------------- 1 file changed, 48 insertions(+), 25 deletions(-) diff --git a/Student-Ambassadors.md b/Student-Ambassadors.md index 345318d..7679486 100644 --- a/Student-Ambassadors.md +++ b/Student-Ambassadors.md @@ -1,55 +1,78 @@ -# GW OSPO Student Ambassador Program +# OSPO Student Ambassador Program # Pattern Summary -A paid student ambassador program that empowers undergraduate and graduate students to promote open source engagement, events, and projects across the university. +Create a paid Student Ambassador program that empowers undergraduate and graduate students to promote open source engagement, events and projects across the university. - # Problem + # Problem / Challenge +An academic OSPO wants to build consistent, authentic connections with the student body while advancing the OSPO’s technical and community goals. -Many universities, including George Washington University, are developing Open Source Program Offices (OSPOs) to foster a culture of collaboration and innovation; however, they struggle to connect directly with students. Students comprise an essential part of the academic community. Still, engagement can be challenging for academic offices due to the consistent presence, peer-to-peer outreach, and relevant campus projects that it entails. As it stands now, faculty and staff may have limited time for outreach, and communication directly from an academic institution can feel distant, inaccessible, or otherwise miss the mark when it comes to connecting students. Without active engagement, awareness of open source opportunities remains low, and participation in OSPO initiatives is limited. The challenge is to build consistent, authentic connections with students while advancing the OSPO’s technical and community goals. +Academic OSPO staff have competing priorities and do not have the necessary time for outreach initiatives that connect directly with students. - # Pattern Category +Without proactive outreach, awareness of open source opportunities remains low and student participation in OSPO initiatives will be limited. + +# Pattern Category * Awareness * Community Building * Education & Skills -* Open Source Development -* Open Source Discovery -* Promoting Best Practices # Context -This pattern applies to university OSPOs seeking to strengthen their connections with students and build a culture of open-source participation on campus. It is particularly effective at institutions where OSPOs are newly established or lack full-time staff dedicated to outreach. The approach works best when there is administrative support for paid student positions and when project goals align with both educational and open-source values. +A research university creating large volumes of research outputs across every discipline. + +The academic OSPO may lack full-time staff dedicated to outreach. # Forces -* OSPO staff often have limited abilities to maintain regular contact with students. -* Students respond more positively to peer-led initiatives than to top-down institutional messaging. -* Effective outreach requires both technical expertise and social engagement skills. -* Consistent student involvement must be balanced with academic workloads and turnover. -* Funding and measurable outcomes are necessary to justify continued university support. +* OSPO staff are time-poor and lack the capacity to maintain regular contact with students. +* There is administrative support for paid student positions. +* Prospective Student Ambassadors will have technical expertise and social engagement skills. +* Student involvement must be balanced with academic workloads and turnover. # Solution -Create a Student Ambassador program within the OSPO consisting of a small team of paid students; two graduate students working 20 hours per week and two undergraduates working 10 hours per week. A combination of both graduate and undergraduate ambassadors enables broader coverage across academic levels, strengthens continuity over semesters, and meets OSPO workload requirements. These ambassadors serve as liaisons between the OSPO and the student body in the following ways: +Create a Student Ambassador program within the OSPO consisting of a small team of paid undergraduate and graduate students (working approximately 10 - 20 hours a week). + +The ambassadors serve as liaisons between the OSPO and the student body through designated acitivities. + +Activities to consider may include: +* Creating and managing OSPO social media accounts to share updates and opportunities. +* Hosting and [tabling at campus events](https://github.com/CURIOSSorg/curioss-patterns/blob/main/event-tabling.md) to promote the OSPO and open source awareness. +* Organizing community-building activities such as movie nights or coding sessions. +* Leading or contributing to open source technical projects that advance university OSPO goals. +* Gathering student feedback and communicating emerging needs to OSPO leadership. + +# Resulting Context -* Hosting and tabling at campus events to raise open source awareness -* Organizing community-building activities such as movie nights or coding sessions -* Creating and managing OSPO social media accounts to share updates and opportunities -* Leading or contributing to open source technical projects that advance university OSPO goals -* Gathering student feedback and communicating emerging needs to OSPO leadership +Student Ambassador Programs create visible, authentic, student-led initiatives for the OSPO based on peer-to-peer engagement rather than top-down institutional messaging. -# Resulting Context: +Ambassadors increase awareness and participation in open-source initiatives whilst also delivering tangible technical outcomes. -Implementing this pattern creates a visible, student-led initiative for the OSPO on campus. The ambassadors increase awareness and participation in open-source initiatives while also delivering tangible technical outcomes. At GW, early results have demonstrated increased event attendance, successful launches of social media channels, and ongoing student-led technical projects aimed at promoting open-source use across departments. Challenges lie in maintaining consistent engagement as students graduate and ensuring sustained funding for paid positions; however, the benefits of authentic outreach and student leadership outweigh these concerns. +The program presents opportunities for students to develop important soft skills in communications, facilitation, team work and leadership. + +A combination of graduate and undergraduate ambassadors creates a sustainable pipeline of Student Ambassadors and maintains consistency as students graduate. It also enables broader coverage across academic levels, strengthens continuity over semesters and meets OSPO workload requirements. + +In order to sustain funding for paid positions, measurable program outputs and outcomes should be developed to justify continued university support. The program should also align with both educational and open source values. + +## Additional Learning from the GW Open Source Program Office +Two graduates (working 20 hours per week) and two undergraduate students (working 10 hours per week) work alongside OSPO staff to promote open source awareness, organize events and contribute to open source infrastructure at GW. + +Early results have demonstrated increased event attendance, successful launches of social media channels and ongoing student-led technical projects aimed at promoting open-source use across departments. # Known Instances +* [GW OSPO](https://ospo.gwu.edu/), George Washington University + +# References +[GeorgeHacks Makerspace 2025](https://ospo.gwu.edu/georgehacks-makerspace-2025) article on the GW OSPO Student Ambassadors' table at a Makerspace event. -* **The George Washington University OSPO:** Two graduate and two undergraduate student ambassadors work part-time alongside OSPO staff to promote open source awareness, organize events, and contribute to open source infrastructure at GW. -* **University of Vermont, Open Research Community Accelerator (ORCA):** Run by the University of Vermont’s OSPO (VERSO), [ORCA](https://verso.w3.uvm.edu/orca/) connects undergraduate students with faculty, graduate researchers, and local partners to create open-source tools that extend the reach and impact of academic research. Students work in small “Pods” of 4–5 members, gaining real-world experience in open-source development while translating research outputs into accessible, community-focused applications. The program strengthens open research practices and cultivates workforce-ready skills in open source. +## Related Patterns +* [Event Tabling](https://github.com/CURIOSSorg/curioss-patterns/blob/main/event-tabling.md) +* [Open Research Community Accelerator (ORCA)](https://github.com/CURIOSSorg/curioss-patterns/blob/main/open-research-community-accelerator.md) # Contributors & Acknowledgements -Mia Diewald (George Washington University OSPO) [https://orcid.org/0009-0005-8123-1832](https://orcid.org/0009-0005-8123-1832) +Mia Diewald, George Washington University, https://orcid.org/0009-0005-8123-1832 +Ciara Flanagan, https://orcid.org/0009-0005-3153-7673