Publish out of tree drivers with GPL #7
Labels
No Label
Kind/Community
Kind/Documentation
Kind/Enhancement
Kind/Event
Kind/Feature
Kind/Security
Meeting
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: rocky-linux/board#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Will the RESF board support publishing Out of Tree (OOT) drivers if they include a GPL license?
SIG/Cloud has a request from a stakeholder at Google to incorporate Out of Tree drivers (IDPF, RDMA) into the SIG/Cloud offering. These drivers come with GNU license files (General Public License (GPL) Version 2 or BSD 2-Clause). The drivers are not currently available at a publicly accessible link.
Although the Linux kernel is provided to the public under GPLv2, I am inclined to say that the RESF board and legal counsel may want to take a look at it to double check as it's not publicly published yet.
If the code isn't public but the OOT driver code comes with the GPLv2 license, it might be ok (assuming the author(s) do publish it at some point), but I still believe that both (RESF+legal) should look into it and provide their comments on the matter.
Perhaps others on the project board here will have other thoughts (as some of us are both on the project and RESF board).
Thank you @label. I am attaching the files for reference.
Intel has begun publishing their IDPF drivers on Github. https://github.com/intel/ethernet-linux-idpf
More work will be required for them to unify and publish the RDMA driver sources.
While this is indicative of their commitment to publishing these drivers, we are still seeking to publish early OOT drivers through SIG/Cloud in advance of the specific versions being published in the respective public repo.
As long as the vendor allows publishing, and that the code is openly licensed, there shouldn't be a restriction on what SIG/Cloud wants to host. I don't think a longer investigation is needed now that the vendor themselves have started periodically syncing it to Github
Publishing approved in today's Rocky Linux Project Board meeting.