What's in a name? Why call it an OSPO?

[claredillon]

Here are some thoughts from a conversation that has been brewing in a number of places recently...

What is the value in calling something an OSPO (above and beyond carrying out OSPO-like activities)?

Here are some initial thoughts - I'd really welcome other ideas...

Calling an entity an OSPO puts a flag/name on the org doing OSPO-like activities. This has the effect of:

• Allows better reach within the university - as there is a recognizable destination for people to reach out to when they have a question about open source
• Enables better-sustained OSS-enabling activities within the university
  • because otherwise OSS-enabling activities may be tied to an individual and stop when they leave or become re-deployed, and no-one notices...
  • because having an entity gives a focus for securing funding (not tied to individuals)
• Magnifying effect of engagement - e.g. I came to the OSPO hackathon, now I am engaging in their training program, or am linked to the researcher I was introduced to by them. You could characterise this as "systemized glue-work for OSS community within the org"
  Allows simplified language to be used when describing the value of the work to leadership (e.g. "because we have an OSPO we have achieved a,b,c" as opposed to "because we did this <program that the leadership don't really understand or care about" we have achieved a,b,c"
• Enabling external networking with other OSPOs
  • Easier to network with others doing the same thing and learn from them, share resources etc.
  • Easier for people from outside the org to find the right person to talk to about open source in the university.
  • Has led to invites to speak, collaborations etc.

[jyoung3131]

+1 to all of these ideas, @claredillon.

Based on our updated academic OSPO definition, we say that "An open source program office or OSPO is defined as an organizational construct supported by one or more individuals that acts as a convener, community steward, and center of competency for open source software."

In my mind, the "center of competency" is key for any OSPO, regardless of hosting institution. An OSPO might have several people each with different expertise areas (e.g., in ours we split licensing questions and open source AI between two people) but that centralizing point and "name recognition" is critical for the continued success of the organization.

[claredillon]

The most obvious point, some would say! :) Thanks Jeff