#8685 closed defect (fixed)
Need to understand pedigree of OAuth.js
| Reported by: | Chris Mitchell | Owned by: | Chris Mitchell |
|---|---|---|---|
| Priority: | high | Milestone: | 1.3 |
| Component: | General | Version: | 1.3.0b1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
OAuth.js has a comment that it is based on code from Netflix. If this is not the committer's original work, do we have approval to use the 3rd party code, under what license and copyright, etc. If this is the committers work, can we state that in the comments so that there's no confusion on its origin.
Change History (3)
comment:1 Changed 13 years ago by
| Owner: | changed from Tom Trenka to Chris Mitchell |
|---|
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 Changed 13 years ago by
| Milestone: | tbd → 1.3 |
|---|
batch move of tickets marked 'tbd' fixed in the 1.3 timeframe
Note: See
TracTickets for help on using
tickets.
The OAuth code was written custom against the Netflix OAuth service, using the included link and the OAuth specification as a reference implementation, but developed from scratch.
I included the link so that others may take a look at the reference implementations I used to create the module.
Does that answer the question at all?