Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

license: Add preamble to non-eBPF C/include files #2

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Conversation

christos68k
Copy link
Member

@christos68k christos68k commented Apr 15, 2024

To clarify for readers: The eBPF C code in this repository is GPL licensed (and not affected by this PR). We have additional non-eBPF code however, and that is licensed under Apache2.

@athre0z
Copy link
Member

athre0z commented Apr 15, 2024

This preamble is in conflict with the README that states that the BPF code is licensed under GPL:

https://github.com/elastic/otel-profiling-agent/blob/527745e865b14dee5402de3830e4f80230719e41/README.md?plain=1#L502-L503

The license export here is also still set to GPL:

https://github.com/elastic/otel-profiling-agent/blob/527745e865b14dee5402de3830e4f80230719e41/support/ebpf/interpreter_dispatcher.ebpf.c#L188

We should update these two in the same wash.

Copy link
Member

@athre0z athre0z left a comment

Choose a reason for hiding this comment

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

Ah, sorry: I incorrectly associated "C files" with our BPF C files. Never mind previous comment, LGTM!

The eBPF code in this repository is licensed under GPL.
@christos68k christos68k changed the title license: Add preamble to C/include files license: Add preamble to non-eBPF C/include files Apr 15, 2024
@christos68k christos68k merged commit c36ea72 into main Apr 15, 2024
3 checks passed
@christos68k christos68k deleted the ck/preamble branch April 15, 2024 20:13
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