add links to intro and mention concept of a muscular ospo

Author: kungfuchicken

docs/about/playbook.md

@@ -8,7 +8,7 @@ custom_edit_url: null
 
 ## Introduction
 
-This playbook describes an approach for operating an Open Source Program Office (OSPO) at a university, with a focus on actively building and maintaining research and community software tools. The OSPO serves as a hub for fostering open-source software development, collaboration, and knowledge-sharing within the university community and beyond.
+This playbook describes an approach for operating an [Open Source Program Office (OSPO)](https://github.com/todogroup/ospodefinition.org) at a university, with a focus on actively building and maintaining research and community software tools. The OSPO serves as a hub for fostering open-source software development, collaboration, and knowledge-sharing within the university community and beyond. This OSPO also coordinates and contributes work on open source software projects, what some people call a ["muscular OSPO"](https://mospo.io/).
 
 The primary goals of the OSPO are:
 
@@ -291,17 +291,9 @@ This project was successful based on the following success metrics (as described
 MeltShiny allows computational chemists to perform the analysis of the aminoacid melting temperatures without the need for programming knowledge. It's a web browser based user interface that interacts with the [MeltR](https://github.com/JPSieg/MeltR) library. The application is deployed [here](https://oss-slu.shinyapps.io/MeltShiny/) and can be accessed by anyone with a web browser.
 
 This project was successful based on the following success metrics (as described in this playbook):
-
 - The client is intersted in continuing to work with us (after two years of collaboration). There are a few fixes that remain to be done to get this application to the state when it can be actively used by clients. (success metric from the [Project Selection, Deliveray, and Support](#1-project-selection-delivery-and-support) section)
 - All students working on this rpoject recieved top grades. (success metric from the [Software Development with Enrolled Students](#2-software-deveopment-with-enrolled-students) section)
 - We secured $25K in internal funding to continue development of this application. (success metric from the [Faculty Outreach](#5-faculty-outreach) section)
 
 ### Failed Project - Santiago
-
-A request was submitted by a neuroscience lab for a desktop application for 3D imaging macroscopy data. An existing open source MatLab library was identified in the original request, but the lab did not have anyone with software development skills. The project was accepted on its scientific merits and with the expectation that the MatLab library coud be used as an engine for a desktop app. Early on risks were identified regarding a hard dependency on the upstream library with a sole developer, limited MatLab experience amongst available developers, and engineering challenges using MatLab as a procesing engine for a desktop based app. Ultimately the team faced significant challenges creating a performant application that could handle the volume of data in the 3D point clouds that MatLab was generating, and various team members expressed concern that the upstream library did not seem be getting maintenance updates.
-
-There are several lessons learned from this project:
-
-- The project selection rubric must weigh risk factors and either de-prioritize or find alternative approaches to projects with excessive risks.
-- When considering open source libraries or dependencies, prioritize those with active development communities, frequent updates, and robust documentation, or find ways to engage with single-developer dependencies to begin building communities around their projects.
-- Identify alternative means for supporting research software needs, including helping researchers with training or referrals to developers with more experience in a required tech stack.
+