# UC OSPO Education Program
Tim Dennis, Todd Grappone, Emily Lovell, Nick Ulle, David Minor, Reid Otsuji
---
#### Today's Agenda
```graphviz
digraph {
Agenda [label="Today's Agenda", shape=box, style=filled, fillcolor=lightblue]
Persona [label="Learner Personas Update", shape=ellipse]
Patterns [label="Emerging Patterns", shape=ellipse]
Curriculum [label="Curriculum Overview", shape=ellipse]
Discussion [label="Open Discussion", shape=ellipse]
NextSteps [label="Next Steps", shape=ellipse]
Agenda -> Persona
Agenda -> Patterns
Agenda -> Curriculum
Agenda -> Discussion
Agenda -> NextSteps
}
```
---
```graphviz
digraph {
Process [label="UC OSPO Education Program Process", shape=box, style=filled, fillcolor=lightblue]
Goals [label="1: Define Goals\nand Objectives", shape=ellipse]
Gap [label="2: Conduct Gap\nAnalysis", shape=ellipse]
Design [label="3: Curriculum\nDesign Framework", shape=ellipse]
Develop [label="4: Develop\nNew Content", shape=ellipse]
Implement [label="5: Implementation\nand Continuous Improvement", shape=ellipse]
Process -> Goals
Goals -> Gap
Gap -> Design
Design -> Develop
Develop -> Implement
}
```
---
# Progress Updates
---
**Using Learner Personas to Identify Lesson Gaps**
- **Analyze** learner personas to determine lesson needs.
- **Map** those needs to existing lessons and resources.
- **Identify** gaps and prioritize new lesson development.
---
## What are Learner Personas
**Personas are fictional profiles representing typical learners to guide curriculum design.**
---
## Examples:
#### Emma Calder: Research Software Engineer
- **Background**: Research Software Engineer (RSE) working with environmental data for the Urban Ecology Lab.
- **What They Know**: Proficient in Python and GIS tools, with experience in creating interactive data visualizations.
- **Goals**: Learn sustainable software development practices, improve workflow reproducibility, and prepare for collaborative projects.
- **Special Needs**: Mentorship on advanced version control and modular code development.
---
#### Dr. Adrian Wallace: Grant-Seeking Faculty
- **Background**: Faculty member in computational biology, leading a lab focused on data-intensive research.
- **What They Know**: Familiar with R and Python but limited understanding of OSS licensing and community practices.
- **Goals**: Ensure research outputs meet grant compliance, navigate licensing complexities, and adopt reproducible research practices.
- **Special Needs**: Resources on licensing for open-source tools and real-world examples of OSS-enabled grant success.
---
#### Alex Rivera: Data Archivist
- **Background**: Archivist managing institutional datasets and UCLA's Dataverse platform.
- **What They Know**: Expertise in metadata standards and data curation, with initial exposure to OSS community tools.
- **Goals**: Advocate for institutional data-sharing needs, enhance workflows with OSS practices, and represent the organization in OSS governance discussions.
- **Special Needs**: Hands-on training in OSS workflows and strategies for integrating OSS governance into institutional processes.
---
#### Alex Carter: Administrative Staff
- **Background**: Administrative staff supporting OSS initiatives with limited technical skills.
- **Goals**: Learn to support OSS initiatives and organize contributions effectively.
- **Special Needs**: Training on GitHub, project management, and institutional policies.
---
#### Taylor Kim: IT Security and Compliance Officer
- **Background**: Oversees compliance for applications handling sensitive data (e.g., P3, P4).
- **Goals**: Vet OSS tools for security risks and establish trust in OSS tools.
- **Special Needs**: Training on evaluating OSS security and risk management.
#### Chris Patel: Software Developer and OSS Contributor
- **Background**: Developer using OSS libraries for tools and contributing to external projects.
- **Goals**: Streamline OSS approval processes and share OSS code effectively.
- **Special Needs**: Clear institutional guidelines and streamlined contribution workflows.
---
## Emerging Needs for the Curriculum
### 1. Need for Open Source Literacy
- **Audience**: Faculty, students, staff.
- **Topics**: OSS principles, tools like Git, GitHub, and community norms.
---
### 2. Licensing and Compliance Challenges
- **Audience**: Faculty, students, tech transfer staff.
- **Topics**: Understanding OSS licenses and aligning them with institutional needs.
---
### 3. Security and Institutional Policy
- **Audience**: IT officers, compliance staff.
- **Topics**: Vetting tools, institutional policies, trust models.
---
### 4. Supporting Research and Grant Workflows
- **Audience**: Faculty and researchers.
- **Topics**: Reproducibility, sustainable tools, OSS for grants.
---
### 5. Building Communities and Entry Points
- **Audience**: Students and contributors.
- **Topics**: Beginner-friendly pathways, mentorship, OSS contributions.
---
#### Curriculum Overview
```graphviz
digraph {
Curriculum [label="Curriculum Overview", shape=box, style=filled, fillcolor=lightblue]
Foundations [label="Open Source Foundations", shape=ellipse]
Licensing [label="Licensing and Compliance", shape=ellipse]
Security [label="Security and Risk\nManagement", shape=ellipse]
Research [label="Research and Open\nScholarship", shape=ellipse]
Contribution [label="Contribution and\nCommunity Building", shape=ellipse]
Curriculum -> Foundations
Curriculum -> Licensing
Curriculum -> Security
Curriculum -> Research
Curriculum -> Contribution
}
```
---
## Curriculum Tracks and Modules
### Open Source Foundations
- **Audience**: Beginners (students, grant-seeking faculty, staff new to OSS).
- **Example Modules**:
- [Getting Started with OSS](https://opensource.guide/)
- [How to Contribute](https://coderefinery.github.io/social-coding/)
---
### Licensing and Compliance
- **Audience**: Faculty, students, licensing specialists, tech transfer staff.
- **Example Modules**:
- [Demystifying OSS Licenses](https://choosealicense.com/)
- [Licensing for Research](https://intersect-training.org/software-licensing/)
---
### Security and Risk Management
- **Audience**: IT officers, compliance staff, administrators.
- **Example Modules**:
- TBD
- TBD
---
### Research and Open Scholarship
- **Audience**: Faculty, researchers, grant seekers.
- **Example Modules**:
- [Reproducible Research](https://book.the-turing-way.org/reproducible-research/reproducible-research.html)
- [FAIR Software](https://carpentries-incubator.github.io/fair-research-software/)
---
### Contribution and Community Building
- **Audience**: Students, developers, multidisciplinary contributors.
- **Example Modules**:
- [How to Contribute](https://opensource.guide/how-to-contribute/)
- Open-Sourcing Your Projects (TBD)
---
# Open Discussion
### Questions for the Group
1. Do the emerging patterns align with your observations?
2. Are there any personas or curriculum tracks we should refine?
3. How should we prioritize lesson development?
---
# Next Steps
- Finalize learner personas and curriculum patterns.
- Review and refine inventory of lessons.
- Identify gaps.
- Recruiting authors to draft new modules to fill gaps.
- Use and refine lessons.
---
### Thank you! :tada:
Resources:
- [UC OSPO Education Repository](https://github.com/UC-OSPO-Network/education)
- [UC OSPO Project](https://github.com/orgs/UC-OSPO-Network/projects/1/views/7)
- [Learner Personas & Curriculum Needs](https://docs.google.com/document/d/1wdWaiM_tLO3rHRnmS3PPFcPwYCoXjoLldwG0oP7CGpE/edit?tab=t.0)
- [Slides](https://hackmd.io/@timdennis/HJZHDVv4Jx#/20)
---
{"title":"OSPO Education","description":"View the slide with \"Slide Mode\".","slideOptions":"{\"theme\":\"solarized\",\"transition\":\"fade\"}","contributors":"[{\"id\":\"1421b929-3417-4b58-b481-d440da17fe5d\",\"add\":9246,\"del\":1687},{\"id\":\"9bfdc0ff-3a1b-4d07-804a-5b5919c419c9\",\"add\":2,\"del\":0},{\"id\":null,\"add\":79,\"del\":0}]"}