Closed Bug 1185704 Opened 6 years ago Closed 6 years ago

Get Licensing signoff on using newer React.js versions after 0.12.0 due to changed license


( :: Licensing, task)

Not set


(Not tracked)



(Reporter: standard8, Assigned: gerv)



In bug 1033784 we got approval for using react.js version 0.10.0 with a Apache license, and landed it in bug 1033841.

When react released 0.12.0, Facebook changed the license it was released with to BSD (from apache):

Unfortunately, in landing the upgrade in bug 1096399 we totally missed spotting the license change and getting re-approval. This landed for Fx37.

Therefore we're post-requesting approval. I suspect we may need an about:license update as well. NI to gerv to take a look at this.
Flags: needinfo?(gerv)
If possible, I'd like to have this finished this week. We have been blocked on this for other work.
Yes, this license is fine. If we ship React in Firefox / Fennec, we need to add the React BSD license (not the patent stuff) to about:license in the normal way.

Flags: needinfo?(gerv)
Great, thanks gerv! Mark do you know how to add a license to about:license?
Flags: needinfo?(standard8)
(In reply to James Long (:jlongster) from comment #3)
> Great, thanks gerv! Mark do you know how to add a license to about:license?

James: it's very straightforward, and just involves making a change to toolkit/content/license.html.  See the patch in bug 1176280 if you want to have a run at it.
Flags: needinfo?(standard8)
(That patch is an example where I'm a different license).
Depends on: 1190440
I've just filed bug 1190440 for the license addition. Marking this as fixed as we have approval per comment 2.
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.