Universities

University involvement in open source varies widely. For instance, a university could have: a fully structured Open Source Program Offices (OSPOs); a lab or department dedicated to open source; unstructured work done by university staff; investment in open source from libraries or researchers; use of open source edtech internally; taught courses on open source with students; and so on. Because of this, providing a list of universities active in the open source space is hard, and is best thought of as broken down by categories or by usage.

OSPOs

The following universities have an office which has the standing of an Open Source Program Office:

• Carnegie Mellon University

• George Washington University

• Georgia Institute of Technology

• Johns Hopkins University

• Lero - Technically a Research Center for a collection of universities

• Penn State

• Rochester Institute of Technology

• Saint Louis University

• SnT, University of Luxembourg

• Stanford University

• Syracuse University

• Trinity College Dublin

• University of California Berkeley

• University of California Davis

• University of California Los Angeles

• University of California San Diego

• University of California Santa Barbara

• University of California Santa Cruz

• University of Texas Austin

• University of Vermont

• University of Wisconsin-Madison

Labs

There’s a host of universities which don’t have open source program offices, but which do have labs which do a considerable amount of open source work.

• Oregon State University

• University of Nebraska Bridge Lab – This lab includes Matt Germonprez, who works closely with CHAOSS.

• UMass Amherst Open Source Computer Lab

• University at Albany OSI Lab

Universities without OSPOs

There are also universities that develop open source software, but don’t have policies publicly set for staff or researchers.

• Rey Juan Carlos University

• University of Cambridge – IT services has some code available.