You need a place on the public web where people can find your OSPO. There are two patterns we’ve seen in the network:
Path A: page(s) on ucospo.net. The network site has space for every campus, and adding your page is a single PR. Examples in the network: UCSB.
Path B: page(s) on a campus URL. Examples in the network: UCSD, UCSC.
What every page needs (regardless of path)¶
A short intro: one to three sentences on what a campus OSPO is and how yours serves the campus community. Don’t overthink this; it’ll evolve as you go along. (“We support open-source contributors and maintainers at [Campus] across [departments/disciplines/units].” is enough to start.)
How to reach you:
Identify at least one person (probably you!) who people on your campus can reach out to with questions about your OSPO and the Network
Make it easy for people from your campus to get in touch—however that usually happens (email, your campus’s Slack, office hours). You can also link to the public UC OSPO Network Slack.
News/events: upcoming meetups, workshops, talks. Even one upcoming event is enough; the section signals “we’re alive.” Link also to the network events page.
Get involved: spell out concrete next steps for visitors—joining the public UC OSPO Network Slack, subscribing to your campus mailing list, attending the next meetup. Even one of these is enough to start.
Templates and resources¶
For Path A (page on ucospo.net): the repo is at https://
github .com /UC -OSPO -Network /ucospo .net. Look at existing campus directories for inspiration—clone one as a starting template, edit, open a PR. If you’d like help getting the first PR open, open an issue on the repo, or DM Laura (community manager) directly! For Path B (standalone site): start the conversation with whoever handles web infrastructure for your unit (campus IT, your library, etc.). The network can share what’s worked elsewhere—Laura (community manager) is happy to chat through CMS/framework choices before you commit, and we’ve seen a few different setups across the network. Link to ucospo.net from your page, and open an issue (ping Laura on Slack if you need help!) so we can link back to you. Cross-linking is how the network shows up as a network rather than a list of isolated OSPOs.