-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
episode-ideaProposed topics or demos for future eCHO livestreams.Proposed topics or demos for future eCHO livestreams.pendingDefault state for new requests. The maintainers have not yet accepted or scheduled this idea/guest.Default state for new requests. The maintainers have not yet accepted or scheduled this idea/guest.
Description
Basically what "patterns" should one use... Libbpf-bootstrap is Dual BSD/GPL I think and some helpers are GPL only. But what does this mean regarding including/publishing your own code as only GPL ... or only BSD/MIT/Apache?
I guess the scenarios (all totally valid) are - how to approach licensing and code structuring when you:
- Want your code/app to just spread, licensing as permissive as possible
- Want to commit to "free software" approach and license your app/code as GPL only too
- Want to build some proprietary enterprise app (even closed source), but still use eBPF infrastructure without violating any underlying licenses (and optionally good-faith too)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
episode-ideaProposed topics or demos for future eCHO livestreams.Proposed topics or demos for future eCHO livestreams.pendingDefault state for new requests. The maintainers have not yet accepted or scheduled this idea/guest.Default state for new requests. The maintainers have not yet accepted or scheduled this idea/guest.