Skip to content

Conversation

@dpshelio
Copy link
Member

@dpshelio dpshelio commented Dec 15, 2025

Draft completed. Now to get reviews.

The rendered version can be seen visiting the file itself

@dpshelio dpshelio added the business case Develop and improve the business case label Dec 16, 2025
Copy link
Member

@mxochicale mxochicale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi David and all, great start!
I have added a few comments. Happy to read it again.
Thanks, Miguel


> context for your project, explaining the problem that it's meant to solve and how it aligns with the organisation's vision and strategic plan
UCL has a long history of open-source software development for research and open-source educational materials.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

long sounds vague, can we add the 1997 year or the number of years from the first open-source software projects?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, I disagree. The introduction is necessarily a summary. The study will be mentioned several times later with details, and probably we'll add it as an appendix.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although might also be worth considering that UCL OSS will go back way before 1997 I imagine, it's just harder to discover details now! In the 1950s all academic source code was basically OSS...

- Design based on surveys run by other universities
- Users ([University of Wisconsin Madison results][uw-survey]), contributors ([University of California results][uc-survey])
- Publish a guidance on how to release open source outcomes within UCL
- Including license, development models, community engagement, and commercial opportunities
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think commercial opportunities or Commercial Open Source Software (COSS) is a topic for itself. We have seen the need on selection of licensing for software, for instance dual-licencing is something I have been advocating to maintain community using open-source and academic licences and close source licences to protected ideas that could provide economical value.
In this blog, Matthieu Lavergne is talking about Commercial Open Source Software (COSS) and addressed this questions How challenging is the financing journey for COSS startups? Do COSS companies deliver superior exits?

@samcunliffe
Copy link
Member

samcunliffe commented Dec 18, 2025

I think this should be reviewed and merged to main. And I think it's ready (arbeit with some polishing).

Other sections will be drafted on other pull requests open against this branch to make reviews more manageable.

I disagree with this way of working.

Copy link
Member

@jonc125 jonc125 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Various thoughts from me on an initial read-through, and some proof reading.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's not obvious in this diagram, although perhaps it is in the text (it could come under advocacy for instance) is promoting the use of OSS within universities, both on the 'business' side as well as for research & teaching. The emphasis here seems to be more on OSS development. (Of course, if you're using it, hopefully you're also contributing back!)


# UCL's Open Source Programme Office

*Executive Summary*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this have a proper heading style? I'm guessing it'll be written at the end?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, styling will be done at the end.


> context for your project, explaining the problem that it's meant to solve and how it aligns with the organisation's vision and strategic plan
UCL has a long history of open-source software development for research and open-source educational materials.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although might also be worth considering that UCL OSS will go back way before 1997 I imagine, it's just harder to discover details now! In the 1950s all academic source code was basically OSS...

- community
- Ease collaboration with different institutions for similar tasks (from research software to infrastructure)
- policy
- Include Open Source solutions and technical sovereignty into UCL procurement,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the 'sovereignty' term when applied to an institution rather than a country. We don't have a king of UCL ;)

Is this commonly used in non-OSPO contexts too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's a common term used a lot. I've added a footnote to add an explanation.



*mission statement*
> You’ll need to define your project vision, goals and objectives.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to reflect the viewpoint of people like Will Greenly here, not just the research perspective.

Co-authored-by: Jonathan Cooper <[email protected]>
@dpshelio dpshelio marked this pull request as ready for review January 19, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

business case Develop and improve the business case

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants