-
Notifications
You must be signed in to change notification settings - Fork 7
Business case #81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Business case #81
Conversation
Co-authored-by: David Perez-Suarez <[email protected]>
mxochicale
left a comment
There was a problem hiding this 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
ospo/business-case.md
Outdated
|
|
||
| > 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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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...
ospo/business-case.md
Outdated
| - 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 |
There was a problem hiding this comment.
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?
|
I think this should be reviewed and merged to
I disagree with this way of working. |
Co-authored-by: Sam Cunliffe <[email protected]>
Co-authored-by: Sam Cunliffe <[email protected]>
jonc125
left a comment
There was a problem hiding this 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.
There was a problem hiding this comment.
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* |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
ospo/business-case.md
Outdated
|
|
||
| > 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. |
There was a problem hiding this comment.
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...
ospo/business-case.md
Outdated
| - 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, |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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]>
Draft completed. Now to get reviews.
The rendered version can be seen visiting the file itself