|
2 | 2 | title: Get Involved |
3 | 3 | --- |
4 | 4 |
|
5 | | -Joining the UC OSPO Network is less like filling out an application and more like joining a community—because that's what it is. We encourage you to spend some time getting to know the people, the work, and the rhythm of the network before taking on a more formal role. |
| 5 | +Whether you're new to open source or have been doing it for years, you're welcome here. The UC OSPO Network is open to everyone across the UC system—you don't need to be at a campus with an OSPO to participate. |
6 | 6 |
|
7 | | -## Step 1: Join Our Slack |
| 7 | +## First steps (for everyone) |
8 | 8 |
|
9 | | -The best way to start is to [join our Slack workspace](https://join.slack.com/t/uc-ospo-network/shared_invite/zt-3ecp5b20z-ECL~4DkCUslB0t3mbH9xUg). This is where the community has day-to-day conversations, shares resources, asks questions, and coordinates events. It's low-pressure and a great way to get a feel for what the network is about. |
| 9 | +No matter how you're joining the community—as an individual or as a new institution—start here. |
10 | 10 |
|
11 | | -## Step 2: Attend Community Meetings |
| 11 | +### Join our Slack |
12 | 12 |
|
13 | | -Once you're in Slack, we'd love to see you at some of our events and meetings: |
| 13 | +[Join our Slack workspace](https://join.slack.com/t/uc-ospo-network/shared_invite/zt-3ecp5b20z-ECL~4DkCUslB0t3mbH9xUg). This is where the community has day-to-day conversations, shares resources, asks questions, and coordinates events. |
14 | 14 |
|
15 | | -- **All-Campus Meetups**: Virtual gatherings open to anyone across the UC system, held roughly three times a year (summer, fall, spring). These feature speakers from the open source community and are a great introduction to the network. |
16 | | -- **Coworking & Office Hours**: Twice-weekly drop-in sessions ([see the events calendar](../events/index.md)) where you can ask questions, get advice, or just work alongside other community members. |
17 | | -- **Campus Meetups**: Some campuses hold their own local events. Check the [events calendar](../events/index.md) or ask in Slack about what's happening near you. |
| 15 | +### Attend events |
| 16 | + |
| 17 | +- **All-Campus Virtual Meetups**: First Thursday of every month at 10am. Each campus takes turns hosting. |
| 18 | +- **Coworking & Office Hours**: Tuesdays at 10am, Thursdays at 1pm ([see the events calendar](../events/index.md)). |
| 19 | +- **Campus Meetups**: Some campuses hold their own local events. Check the [events calendar](../events/index.md) or ask in Slack. |
18 | 20 |
|
19 | 21 | There's no minimum attendance requirement. Come to what interests you, when you can. |
20 | 22 |
|
21 | | -## Step 3: Start a Conversation |
| 23 | +If your campus has an OSPO or a presence in the network, connect with your local contact: |
| 24 | + |
| 25 | +- **Berkeley**—[Jarrod Millman](mailto:millman@berkeley.edu) · [join mailing list](mailto:ospo+subscribe@lists.berkeley.edu) |
| 26 | +- **Davis**—[davis-ospo@ucdavis.edu](mailto:davis-ospo@ucdavis.edu) · [join mailing list](https://lists.ucdavis.edu/sympa/info/opensource-announce) |
| 27 | +- **Los Angeles**—[Tim Dennis](mailto:tdennis@library.ucla.edu) · [join mailing list](https://groups.google.com/g/ucla-ospo) |
| 28 | +- **San Diego**—[David Minor](mailto:dminor@ucsd.edu) |
| 29 | +- **Santa Barbara**—[Amber Budden](mailto:ospo@library.ucsb.edu) · [join mailing list](https://lp.constantcontactpages.com/sl/hlmtgmY/ucsbospo) |
| 30 | +- **Santa Cruz**—[Stephanie Lieggi](mailto:ospo-info-group@ucsc.edu) · [join mailing list](https://groups.google.com/u/0/a/ucsc.edu/g/ucsc-open-source-news-group/about) |
| 31 | + |
| 32 | +If you don't see your campus listed, you're still welcome! Join the Slack workspace and the [network newsletter](https://mailchi.mp/ucdavis/uc-ospo-network), and/or [reach out to Laura](mailto:lalangdon@ucdavis.edu) and she'll point you in the right direction. |
| 33 | + |
| 34 | +--- |
| 35 | + |
| 36 | +## Get involved as an institution |
| 37 | + |
| 38 | +The UC OSPO Network is open to all UC-affiliated institutions—campuses, labs (such as Lawrence Berkeley National Lab), the California Digital Library (CDL), and other UC entities. Some of our member institutions have formal Open Source Program Offices; others have individuals or teams who champion open source work in various roles. Both are welcome. |
| 39 | + |
| 40 | +Joining the network is less like filling out an application and more like joining a community—because that's what it is. We encourage you to spend some time getting to know the people, the work, and the rhythm of the network before taking on a more formal role. |
| 41 | + |
| 42 | +:::{div} |
| 43 | +:class: mermaid-centered |
22 | 44 |
|
23 | | -When you're ready to explore a closer connection to the network, get in touch with the network team: |
| 45 | +```{mermaid} |
| 46 | +flowchart TD |
| 47 | + A["Interested in joining?"] --> B["Join our Slack workspace"] |
| 48 | + B --> C["Attend community events\nand meetings"] |
| 49 | + C --> D["Connect with the network team"] |
| 50 | + D --> E["Identify a lead contact\nat your institution"] |
| 51 | + E --> F["Welcome aboard! 🎉"] |
| 52 | +
|
| 53 | + style A fill:#fef3c7,color:#000,stroke:#fef3c7 |
| 54 | + style F fill:#fef3c7,color:#000,stroke:#fef3c7 |
| 55 | +``` |
| 56 | + |
| 57 | +::: |
| 58 | + |
| 59 | +### Start a conversation |
| 60 | + |
| 61 | +When you're ready to explore a closer connection to the network, get in touch: |
24 | 62 |
|
25 | 63 | - **Laura Langdon**, Community Manager: [lalangdon@ucdavis.edu](mailto:lalangdon@ucdavis.edu) |
26 | 64 | - **Stephanie Lieggi**, Network Chair: [slieggi@ucsc.edu](mailto:slieggi@ucsc.edu) |
27 | 65 |
|
28 | 66 | We'll talk with you about what open source work looks like at your institution, what you're hoping to get out of the network, and how we can support you. |
29 | 67 |
|
30 | | -## Step 4: Identify a Lead Contact |
| 68 | +### Identify a lead contact |
31 | 69 |
|
32 | 70 | As the relationship develops, we'll ask your institution to identify a lead contact—someone who can serve as the primary point of connection between your institution and the network. This person doesn't need to run an OSPO (not every member institution has one). They just need to be engaged with open source work and willing to participate in network activities. |
33 | 71 |
|
34 | | -## Step 5: Join the Network |
| 72 | +### Join the network |
35 | 73 |
|
36 | 74 | From there, you'll be welcomed into the network's regular activities, including working groups and leadership discussions. The specifics of how new members are integrated into network governance are still evolving, and we're committed to making the process transparent and collaborative. |
37 | | - |
38 | | -## Already at a Network Campus? |
39 | | - |
40 | | -If your campus already has an OSPO or a presence in the network, you don't need to go through this process. Connect directly with your local campus contact: |
41 | | - |
42 | | -- **Berkeley**—[Jarrod Millman](mailto:millman@berkeley.edu) |
43 | | -- **Davis**—[davis-ospo@ucdavis.edu](mailto:davis-ospo@ucdavis.edu) |
44 | | -- **Los Angeles**—[Tim Dennis](mailto:tdennis@library.ucla.edu) |
45 | | -- **San Diego**—[David Minor](mailto:dminor@ucsd.edu) |
46 | | -- **Santa Barbara**—[Amber Budden](mailto:ospo@library.ucsb.edu) |
47 | | -- **Santa Cruz**—[Stephanie Lieggi](mailto:ospo-info-group@ucsc.edu) |
48 | | - |
49 | | -Or [reach out to Laura](mailto:lalangdon@ucdavis.edu) and she'll point you in the right direction. |
|
0 commit comments