Skip to content

New license request: new ADI BSD variant, with proprietary terms #4300

@pombredanne

Description

@pombredanne

License Name
The full name of the license, preferably as provided by the original authors.

TBD, possibly ADI BSD 2 or ADI BSD proprietary?

License Homepage URL
The primary and/or most reliable URL that contains the text of this license and/or information about it. This is ideally a web page dedicated to the license, but it may also be a source file that contains the license text.

Reference URLs
Optionally provide URLs that contain references to the license.

See in the wild at:

License Notes
Optionally describe any aspects of the license that deserve special attention.

There is an extra clause
https://github.com/aboutcode-org/scancode-toolkit/blob/develop/src/licensedcode/data/licenses/adi-bsd.LICENSE does not have:

Use of the software either in source or binary form, must be run
on or directly connected to an Analog Devices Inc. component.

Also the current adi-bsd license URL is dead and is now only seen at
https://web.archive.org/web/20150923121048/https://docs.blackfin.uclinux.org/doku.php?id=adi_bsd

See also https://ez.analog.com/dsp/software-and-development-tools/linux-blackfin/f/q-a/108907/end-of-life-for-blackfin-linux where black has been "EOL'ed".

There is a nascent problem: the older existing adi-bsd license is seldom seen, while the new one is much more common and also seen in SPDX license expression in ADI code.

Therefore I suggest doing something like:

  1. deprecate the existing adi-bsd and create a new adibsd-blackfin for it
  2. create a new adibsd with the extra clause

Also create a bunch of rules for the various notices like:

Metadata

Metadata

Labels

complexnew-licenseA new scancode license can be added for this

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions