react-component / react-component/util

PureRenderMixin BSD+Patent license issues

Open
#560 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
670
Forks
205
Avg merge
11d 17h
Merged PRs (30d)
4

Description

Hi,

We are using the package rc-util through various nested dependencies, and it becomes difficult for us (and also for other users who have problems with the PATENTS agreement) because of the BSD+Patent license from the library PureRenderMixin:
https://github.com/react-component/util/blob/master/src/PureRenderMixin.js

It would be great if you can upgrade the library to re-release one with MIT license:
https://github.com/facebook/react/blob/v15.7.0/old_major_packages/15/react/lib/ReactComponentWithPureRenderMixin.js

Old news links from 2017 regarding the relicensing:
https://engineering.fb.com/2017/09/22/web/relicensing-react-jest-flow-and-immutable-js/
https://legacy.reactjs.org/blog/2017/09/25/react-v15.6.2.html

Best,
Haifeng

Contributor guide

No contributing guide indexed for this repository

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 by reviewing src/PureRenderMixin.js and comparing it with the MIT-licensed React implementation linked in the issue. Confirm the package and release metadata that govern this utility, then verify that the released version no longer carries the BSD+Patent licensing concern.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.