To get around the legal issue that they won't do this for an open source project, just create a shell corporation.
That shell corp then writes a closed-source plugin wrapper in another project entirely.
Put widevine in that wrapper. Then your open source project just has to include that plugin.
To get around the legal issue that they won't do this for an open source project, just create a shell corporation.
That shell corp then writes a closed-source plugin wrapper in another project entirely.
Put widevine in that wrapper. Then your open source project just has to include that plugin.