What is the policy for including third-party licensed dependencies in Swift repositories?

Development Embedded
, ,
1

Hi!

I was able to fix an issue I had with the pico-blink-sdk example on certain boards and SDK versions (RP2040 / RP2350 on RISC-V cores on the new Pico 2.0.0 SDK), but the current fix requires a file licensed BSD-3-Clause from Raspberry Pi.

I was wondering: what is the policy on third-party licensed code? Should I try to find another way of doing this without the licensed code, or could I include this file in my PR, creating a NOTICE file accordingly?

I was also thinking to make a PR to update the embedded docs included in the main Swift repo, but if I take the “include the licensed code“ path, that might become the only licensed-code dependency of the Swift Language itself, which is quite undesirable. I guess I could circumvent this by linking the docs to the swift-embedded-examples repo.

2

I think I'll try to find an alternative, but either way, I was curious to find out if there are any guidelines regarding this sort of stuff.