Popular UCL repos without a license.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 4
Description
From browsing the open-source-dashboard, a few @UCL repositories are missing a license.
In order of the most starred they are:
- ucl-beamer
- research-computing-with-cpp
- Open_Docking_Lab_Handbook
- COMP0249_24-25
- STIR-GATE-Connection (actually Apatche 2.0 but not recognised)
- ADMUR
- ucl-letter
- tus-rec-challenge_code
- FASt-MAL-MOFF
- ECON-CLUSTER
- siman
- COMP0130_22-23_Topic_03
- network
We should contact the owners and ask them to choose a license (or in some cases they've already chosen one but not made it disciverable by GitHub. In cases where a student contributed a lot of code, they should be asked and added to the review as well.
Definition of done
- Contacted the owners of the above.
- They've either added a license or have chosen not to, in which case "No License" is the correct state.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked open-source dashboard and the listed UCL repositories, prioritising the unchecked entries. Contact each repository owner and ask them to add or choose a license, involving major student contributors where relevant. Done means every owner has been contacted and each repository has either a discoverable license or an explicit “No License” state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100