Skip to content

Licensing and reference to public domain material #17545

@pabigot

Description

@pabigot

PR #17468 exposes what may be a gap in the licensing infrastructure: the code is Apache-2.0 as required, but because I'm documenting that it's derived from another source that includes the words "public domain" the licensing check fails.

Moving those words to a separate comment outside the standard header didn't fix it.

Rather than continue to try to game the system by inserting hard spaces or splitting the sentence across comments, I'd like some insight from those who deal with Zephyr licensing:

Is the way I've used and referenced the public domain description of the implemented algorithm acceptable?

If it is, what's the process of getting the license block removed so people will start to review this PR rather than dismiss it because it's got a big red X next to it in the list?

If it's not, how should I provide credit to the author of the original material, who has placed it in the public domain? See also: #17468 (comment)

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions