This repository was archived by the owner on Feb 13, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.qmd
More file actions
35 lines (24 loc) · 2.6 KB
/
Copy pathindex.qmd
File metadata and controls
35 lines (24 loc) · 2.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
---
title: "UC OSPO Survey Home"
toc: true
toc-title: "On this page"
---
Welcome to the homepage for the 2025 [UC OSPO Network](https://ucospo.net) Open Source Survey!
# Background
The University of California (UC) OSPO Network is working to develop infrastructure for open source education, discovery, and sustainability at UC. To develop our strategic priorities and assess the state of UC open source, we conducted a survey in April 2025 of 294 UC-affiliated open source contributors. This website contains a summary of our findings, links to the paper and data, and updates on this and related projects.
# Key results
This is where we'll put an infographic. For now, I am using a random image.
{width=75% fig-align="center" fig-alt="A person walking through a snowy forest."}
## Advice for OSPOs
* The most common challenges that emerged from our study were time and funding. As such, OSPOs should consider either directly funding open source development, or coming up with creative ways to "give back" time or money. Examples might include facilitating co-working groups, promoting AI tools for documentation, or providing support for external grant acquisition.
* We encountered high demand for affordable, accessible, feature-rich computing environments. This suggests an opportunity for academic OSPOs to help secure the technical infrastructure needed for open source development.
* Because the needs of students, faculty, and IT staff diverge significantly, OSPOs may consider partnering with other university teams and departments to extend their reach.
* OSPOs may encounter a tension between institutional priorities (e.g., cost savings, licensing compliance) and developer priorities (e.g., funding, maintenance). OSPOs can and should find a balance by building an open source culture, in which open source activities are not merely monitored or regulated, but also supported, celebrated, and rewarded.
# Links to project materials
[Lessons learned](https://github.com/UC-OSPO-Network/ospo-survey-analysis/blob/main/lessons_learned.md){target=_blank}: a retrospective on the survey instrument. \
Preprint: TBD \
Paper: TBD \
Data (Dryad): [https://doi.org/10.5061/dryad.2280gb662](https://doi.org/10.5061/dryad.2280gb662){target=_blank} \
Archived code (Zenodo): [https://doi.org/10.5281/zenodo.17783102](https://doi.org/10.5061/dryad.2280gb662){target=_blank} \
Living code (GitHub): [https://github.com/UC-OSPO-Network/ospo-survey-analysis](https://doi.org/10.5061/dryad.2280gb662){target=_blank} \
The survey instrument is available in the paper, the GitHub repo, and the Dryad dataset.