UCL / UCL/open-source

Popular UCL repos without a license.

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
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:

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.