Vermont Research Open Source Program Office
ORCA (Open Research Community Accelerator) student internship program connects University of Vermont students with faculty, graduate researchers, and community partners to build open source tools with real-world impact.
About ORCA
The Open Research Community Accelerator (ORCA) is a student initiative housed within UVM's Vermont Research Open Source Program Office (VERSO). We bridge the gap between academic research and real-world impact through open projects with social significance.
Student teams — called Pods — partner with faculty, graduate students, and community organizations to translate research findings into publicly accessible, open source tools. Members gain hands-on experience with industry-standard engineering practices while creating products that matter.
How It Works
ORCA teams operate like real open source engineering teams — with structured sprints, transparent collaboration, and a focus on shipping software that solves real problems.
You join a team of 4–5 students — including a Team Lead, members, and optional Business or Community Leads — to tackle a specific research challenge alongside a faculty sponsor.
Using Agile-inspired two-week sprints, you plan tasks collaboratively, hold brief stand-ups, and iterate openly. Every decision is transparent to the whole team and sponsor.
At the end of each sprint, teams record demonstrations of completed work for sponsors. Rather than traditional grades, you're evaluated on stakeholder feedback and personal growth goals you set yourself.
Everything you build is publicly released under open source licenses. Your work lives on GitHub, cited in research, and used by communities — long after the semester ends.
Projects
Open source tools created by ORCA Pods — each addressing a real challenge identified by researchers, community partners, or state agencies.
A statewide zoning visualization covering all 237 Vermont towns — making complex zoning regulations accessible to planners, advocates, and the public to identify barriers to affordable housing and climate resilience.
A comprehensive town-level dataset of Vermont wastewater resources, supporting housing development and economic sustainability by identifying infrastructure gaps aligned with the Vermont Climate Action Plan.
An AI-powered tool for exploring and classifying silences and conversational gaps using Random Forests, CNNs, Whisper transcriptions, and BERT models — in partnership with the Vermont Conversation Lab.
An open source tool for Interpretive Structural Modeling that creates flow diagrams helping groups solve collective problems — applied in research on thriving in open source communities.
An open source toolkit helping students and researchers get started with open source software development — covering licensing, version control, community governance, and documentation.
A static web map for emergency water and wastewater resources across Vermont, New Hampshire, and New York — supporting mutual aid coordination during infrastructure crises.
An exploratory data visualization combining zoning, wastewater, and flood-risk datasets to help policymakers, planners, and community members understand the factors shaping Vermont's livability and sustainable growth.
A community-driven continuation of NASA's Transform-to-Open-Science curriculum, rewritten and expanded by VERSO. Five modules equip researchers, students, and citizen scientists with open science knowledge and data management skills.
A story-driven, collaborative open source game where players don't just explore a world — they co-create it. Players recover knowledge, craft stories, and design characters and quests drawn from their own lives and communities.
A modern, secure system replacing VRWA's legacy Access database — automating course registration syncing, operator portal access for training records and certificates, and administrative tools for attendance tracking and regulatory compliance.
A civic technology project providing real-time alerts and notifications for Burlington, Vermont — connecting residents with timely local information to support community awareness and safety.
How We Work
Exceeding sponsor expectations generates referrals, trust, and lasting program growth. Good enough isn't the goal.
Validating ideas with teammates before diving in prevents misunderstanding and saves time. Share rough drafts, not polished products.
Changes happen transparently. Everyone on the team and every stakeholder knows what's changing and why — no surprises.
Collaborative problem-solving elevates everyone. Approach challenges with questions, not conclusions.
Teaching others to solve problems builds a more resilient team and a more impactful program than going it alone.
Life in a Pod
ORCA isn't a class with readings and exams. It's a real internship — with real deadlines, real stakeholders, and real software shipped publicly. Here's what a typical semester looks like from the inside.
You'll join a Pod of 4–5 students — a tight team with a mix of skills — working on a specific project for a faculty member, community organization, or state agency. Pods operate like small, self-directed startup teams: you make decisions together, divide up work based on strengths, and hold each other accountable. Unlike a traditional class project, the people using your output are real, and they're counting on you.
Multiple Pods run simultaneously across ORCA each semester, each on different projects. Teams share a co-working space, cross-pollinate ideas, and support each other — so you're never siloed, even if your Sprint work is focused.
ORCA uses an Agile-inspired sprint model. Every two weeks your team plans a sprint: you look at the backlog, talk through priorities with your sponsor, and each member commits to a concrete set of tasks. Brief daily or weekly stand-ups keep everyone aligned and surface blockers early. At the end of each sprint you record a short demo showing what you actually shipped — not slides, not a status update, but working software or data.
This rhythm teaches you to scope work realistically, communicate progress continuously, and ship incrementally rather than in one big push at the end of the semester.
Your project sponsor — a researcher, planner, nonprofit, or state agency — isn't a passive client. They attend Sprint Reviews, give direct feedback on your demos, and help you understand the real-world constraints your tool has to work within. You'll practice translating technical choices into plain language, managing expectations, and presenting work to people who care deeply about the outcome without caring much about the code.
This stakeholder dynamic is one of the most valuable parts of the experience. Learning to build software with someone, not just for them, is a skill most engineers don't develop until years into their careers.
ORCA projects are built for people — not for benchmarks or portfolios. That means you start by understanding who will use the tool and what problem they're actually trying to solve, then prototype quickly, test with real users, and iterate. UX Design Specialists lead wire-framing and usability testing; developers build to those specs; data specialists shape what the interface shows and why. Everyone participates in understanding the user.
The goal isn't perfection on the first try — it's learning what works, fast, so you can make it better. You'll ship things you're proud of and things you'd do differently. Both are part of the training.
Plan, build, demo, reflect — then repeat. The sprint cycle keeps work tangible and momentum high.
Short check-ins surface blockers before they become problems. Everyone knows what everyone else is working on.
Stakeholders attend Sprint Reviews and give direct feedback — building your ability to communicate work to non-technical audiences.
Issues, pull requests, code review, and project boards — the same tools used in professional open source development.
UX-first thinking means you design before you build, test before you ship, and validate assumptions early.
You set your own growth goals at the semester's start and assess your progress at the end — with stakeholder feedback as a guide.
Internship Roles
ORCA offers five distinct internship positions. All roles require current UVM student status and a willingness to apply technology to real research and community problems.
Guides a small intern team while contributing directly to open source development. Coordinates with project sponsors on goals and progress, researches relevant technologies, and provides technical mentorship throughout the semester.
Writes clean, well-documented code and contributes new features within an Agile team. Works through Git and pull requests, maintains documentation, participates in sprint planning and reviews, and debugs and optimizes shared codebases.
Creates and analyzes location-based datasets for research and community projects. Works with ArcGIS, QGIS, and Python geospatial libraries to build maps, generate metadata, and document workflows for partners and the public.
Analyzes large datasets, identifies trends, and builds visualizations and interactive dashboards that make findings accessible to stakeholders. Documents methodologies, supports cross-functional problem-solving, and ensures data quality throughout the project lifecycle.
Leads user research, gathers requirements through stakeholder meetings, and designs wireframes, prototypes, and mockups from low to high fidelity. Conducts usability testing, creates design systems and style guides, and ensures accessibility standards are met throughout the build.
Current Pods
Each Pod is named after a Vermont ski mountain. Five teams are currently running in parallel, each focused on a distinct problem domain.
ORCA Skills
Every ORCA Skills task, from getting started to leading a Pod, each with its own link. You can take them on whenever your work calls for them: choose what fits you now to see your tasks in order.
When you finish a task, send it with the reflection form, a UVM Qualtrics survey. Sign in with your NetID, choose the task from the list, and answer three questions:
Some tasks ask for one more thing, such as your ORCiD or a pull request link; the form asks for it when you choose that task. Admin tasks only need "done". Only ORCA staff see your answers. Never put ID documents, bank details or passwords in the form.
Admin steps to finish before your first day.
ORCA's projects, issues and onboarding all live on GitHub, in the VERSO-UVM organization. You need to be a member to work on them.
Send "done" for ADM-01 with the reflection form. Admin tasks need no reflection.
UVM can't pay you until your I-9 is on record. Doing it early avoids delays and keeps UVM in line with federal rules.
Send "done" for ADM-02 with the reflection form. Never put your ID, documents or other personal details in the form.
PeopleSoft is where you get paid and where you enter your hours.
Send "done" for ADM-03 with the reflection form. Never put bank or account details in the form.
You are paid for the hours you enter. Missed entries mean late pay.
Returning students: just confirm your time entry still works.
Once your reminder is set, send "done" for ADM-04 with the reflection form.
Policies, AI use, open science and goals.
As in any job, you need to know the policies and expectations of your role. The wiki holds the details, and we expect you to follow them. Ask if anything is unclear.
Returning students: read both again, since they change between semesters.
Send your reflection with the reflection form, and add your initials and the date to affirm that you have reviewed both.
ORCA expects you to use AI tools to build, and to stay the person who owns every decision. The goal is not writing lots of prompts. It is judging what comes back: knowing how a solution must change to fit the project, debugging code that fails in ways you didn't write, and seeing why some output shouldn't ship even when it runs.
Some of you would rather build your core coding skills without AI, and that has a place too. Talk with your Pod lead about where on your project you can do that.
Use UVM's tools for project work.
Know what you commit.
Know when not to use it.
Where it helps most: boilerplate and test data, repetitive tests (which you still review), and getting unstuck on a problem, as long as you understand the answer.
Send your reflection with the reflection form. Under "What I learned", name one kind of work on your project where you would not use AI, and why. Add your initials and the date to affirm that you will follow these rules.
An ORCiD (Open Researcher and Contributor ID) tracks your contributions to academic work. It connects your work without depending on your name, which can change over time. We use ORCiDs to credit your work where it fits.
Send your reflection with the reflection form, and include your ORCiD.
Transform to Open Science (TOPS) was part of NASA's Open-Source Science Initiative, a long-term commitment to a scientific culture ready for 21st-century challenges. ORCA used its Open Science 101 course for onboarding until it was taken down in 2025.
This is where open source matters. The course was released under an open Creative Commons license, and we had forked it. So we gave it new life: we took the original materials, extended them, and repurposed them for ORCA.
Send your reflection with the reflection form, and paste your answers to the 5 activities into it.
Everything ORCA builds is released as open source, so you need to know what a license allows and requires. This short course covers the essentials of open source software licensing for research and education.
Send your reflection with the reflection form.
Designing a team project means thinking about the skills it needs and how to get them, along with its timeline, budget, risks, expectations and project management. The Turing Way's case studies cover small, mid-size and large projects, both short and long term.
Send your reflection with the reflection form.
The Open Resource Library is ORCA's community resource for understanding open source software and open practices. As a community project, it needs your input, and improving it is a low-stakes way to make your first pull request.
Send your reflection with the reflection form, with a link to your pull request. The task is done once the pull request is accepted.
Skip any course you already know.
ORCA uses Git and GitHub for project management, data storage and code. These are GitHub's own training courses.
You may already know this. Skip any course you can already do.
Complete the First day on GitHub courses:
Send your reflection with the reflection form, and say which courses you skipped because you already knew them.
These courses take your GitHub skills further: reviewing, resolving conflicts and working with releases, which you will do on every project.
You may already know this. Skip any course you can already do.
Complete the First week on GitHub courses:
Send your reflection with the reflection form, and say which courses you skipped because you already knew them.
As a verified student, GitHub gives you more for free: free use of GitHub Codespaces (up to 180 core hours a month on your personal account), GitHub Copilot, and offers on industry tools in the Student Developer Pack. See GitHub Education for students.
Approval isn't instant, so apply in your first week. If you are already verified, skip this task.
About Copilot: GitHub Copilot is not on UVM's approved AI tools list. Use it only with public code and public data (see CORE-03).
The full steps are in GitHub's guide, Apply to GitHub Education as a student.
Once you are approved, send "done" for GIT-03 with the reflection form. Your proof of enrollment goes only to GitHub. Never put it in the form.
For students leading a Pod.
Leading a Pod is about trust, safety and how teams work, as much as code. These readings and talks are the shared grounding for every ORCA lead. Returning students do this only the first time they lead.
Each week, read or listen to that week's pieces.
Week 1
Week 2
Week 3
Week 4
By 3pm each Friday, send a paragraph about that week's pieces with the reflection form: what you found insightful, and what you disagreed with. Choose LEAD-01 and the week.
ORCA Pods work in sprints. Running the first few planning meetings and reviews early, even with little to show, gets your team used to the rhythm.
Week 2 (sprint 1)
Week 3 (sprint 2)
Week 4 (sprint 2)
Send your reflection with the reflection form after the week 4 demo review.
These six activities, spread over the project lifecycle, help you settle into leading a team.
Send your reflection with the reflection form once you have done the first four.
Join ORCA
ORCA accepts UVM undergraduate students each semester. Members can participate for course credit, as paid student employees, or as volunteers. No specific major is required — we welcome engineers, designers, communicators, and researchers.
Recruitment typically opens at the start of each semester. Check the VERSO website or reach out through the program office to learn about current openings.
Learn about ORCA's mission, current projects, and how to apply.
verso.w3.uvm.edu/orca →Read about our policies, onboarding process, and what to expect.
View on GitHub Wiki →Browse all VERSO-UVM open source projects and contribute.
github.com/VERSO-UVM →