Improve the first page and add our general advice from the ARC internal documentation. #80
Conversation
Clarify and strengthen the homepage. Add the first guide which is almost exactly Sarah's guide from our internal documentation.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
This PR strengthens the homepage messaging to be more assertive about UCL's open-source commitment and adds a comprehensive guide on UCL's position regarding open-source software licensing, adapted from ARC's internal documentation.
Key changes:
- Revised homepage to emphasize UCL's history with open source and core values around openness
- Added new guide "UCL and open-source software" with licensing advice, copyright guidance, and legal resources
- Reorganized guides index to feature the new licensing guide prominently
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
| index.md | Updated homepage content to emphasize UCL's open-source values and highlight the new licensing guide |
| guides/ucl-and-oss.md | New comprehensive guide covering UCL's IP policy, ARC's recommendations on licensing, copyright holder conventions, and legal resources |
| guides/index.md | Updated to link to the new UCL licensing guide and removed placeholder for research software licensing |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
guides/ucl-and-oss.md
Outdated
| The [Centre for Advanced Research computing](https://ucl.ac.uk/arc) recommends that people always add a licence and copyright to any software that is produced and shared with a third party. | ||
| However ARC does not offer legal advice. | ||
|
|
||
| ### Which licence ? |
There was a problem hiding this comment.
[nitpick] Inconsistent terminology: The heading says "Which licence ?" but the text uses "license" (e.g., line 46 "Many licenses"). Consider using consistent spelling throughout the document. British English uses "licence" (noun) and "license" (verb), while American English uses "license" for both.
guides/ucl-and-oss.md
Outdated
| link: /guides/ucl-and-oss | ||
| # TODO: the breadcrumb above is not working as expected: ask DPS |
There was a problem hiding this comment.
I don't know why, but more than one breadcrumb deep breaks. (Not just here but also on other pages, like the OSPO section.)
@dpshelio any ideas?
There was a problem hiding this comment.
Does it need the .html extension?
There was a problem hiding this comment.
Seems to have no effect.
Co-authored-by: Copilot <[email protected]>
samcunliffe
added
enhancement
github-project-automation
bot
moved this to Backlog
in OSPO Business Case (and peripheral items)
samcunliffe
moved this from Backlog
to In review
in OSPO Business Case (and peripheral items)
Co-authored-by: Mosè Giordano <[email protected]>
Co-authored-by: Mosè Giordano <[email protected]>
jonc125
left a comment
jonc125
left a comment
There was a problem hiding this comment.
Looks good, only minor suggestions.
guides/ucl-and-oss.md
Outdated
| link: /guides/ucl-and-oss | ||
| # TODO: the breadcrumb above is not working as expected: ask DPS |
There was a problem hiding this comment.
Does it need the .html extension?
Co-authored-by: Jonathan Cooper <[email protected]>
Co-authored-by: Jonathan Cooper <[email protected]>
As discussed in the November meeting (and spectacularly well-captured by me in #61 😁).
I've attempted to clarify and strengthen the homepage. Less "we don't know what UCL does" and more 💪 strong statements. I also added a first general guide, which is almost exactly @skeating's page from our internal documentation. I'd appreciate a lot of eyes on that.
Obviously, @skeating, in addition to anything else, you need to be OK with your words being put in public under CC-BY-4.0.