Uniswap / Uniswap/interface

LICENSE Clarity

Open
#7,650 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.5k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

This repository doesn't seem to have a LICENSE file at the moment. From commit https://github.com/Uniswap/interface/commit/fc7ecc7e3bea1c7b459d0d0bad0840f0b82388ef and before, the LICENSE file was the GPLv3. But commits after that to the main branch have that LICENSE file removed from the repo, effectively asserting that the repository is now a proprietry, "look, but don't touch" codebase.

This puts the legal status of the current code base into question as Github currently lists 187 contributors to this repository who contributed to this repository under the terms of the GPLv3.

I understand Uniswap Labs may have some interests in making this codebase prorprietary again, but unless all 187 contributors:

  1. Were employees of Uniswap Labs at the time of their contribution,
  2. Or had signed contribution agreements or copyright assignements allowing Uniswap Labs to arbitrarily relicense their contributions,
  3. Or their contributions have been removed or replaced -

Uniswap Labs is now infringing on the copyrights of these contributors by removing the GPLv3 LICENSE file.

I believe some clarification is required on this matter. For posterity sake - I've forked this repo as of the last commit clearly listed under the GPLv3 here - https://github.com/yokem55/uni-interface-gplv3

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

Review the repository history around commit fc7ecc7e3bea1c7b459d0d0bad0840f0b82388ef and compare the GPLv3 LICENSE file with the current main branch. Determine what license clarification is required for the repository and its contributors; done means the licensing status and any relevant contributor-rights explanation are documented.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.