Skip to content

Remove section on proprietary code inclusion in copyleft - #147

Open
copernicat wants to merge 1 commit into
lfc194_update_2026from
copernicat-patch-3
Open

copernicat wants to merge 1 commit into
lfc194_update_2026from
copernicat-patch-3

Conversation

@copernicat

Copy link
Copy Markdown
Contributor

If we want to include something about this, I think it means 'modifying copyleft open source code' instead. Snippet code scanners would not flag original code inserted in an open source code file.

If we want to include something about this, I think it means 'modifying copyleft open source code' instead. Snippet code scanners would not flag original code inserted in an open source code file.

@myagi2019 myagi2019 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed the heading to "Unplanned Inclusion of proprietary code/modifications of copyleft open source". I feel like this completes the set of things that could happen with copyleft.
I think this could be caught by a "scanner" - just not necessarily today's snippet scanners nor directly indicated as such. For example, a tool should flag that component X version Y is not 100% the same as the stock/library/previously analysed component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants