Skip to content

Conversation

@rzr
Copy link
Contributor

@rzr rzr commented Mar 11, 2025

This intiial draft for establishing OSS guidelines is voluntary short to allow each topics to be discussed (and approved) in separate PRs.

This intiial draft for establishing OSS guidelines is voluntary short
to allow each topics to be discussed (and approved) in separate PRs.

Signed-off-by: Philippe Coval <[email protected]>
Copy link

@anhilton anhilton left a comment

Choose a reason for hiding this comment

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

seems like a lot of this is just pointing at vague "internal OSS policy" so I am kind of wondering where are those kept, and if we already have those documents what is the specific purpose of this document?

@rzr
Copy link
Contributor Author

rzr commented Mar 26, 2025

seems like a lot of this is just pointing at vague "internal OSS policy" so I am kind of wondering where are those kept, and if we already have those documents what is the specific purpose of this document?

Thank you for feedback, yes this should be in sync with the one in place. Ideally this will be versioned (in git) I should probably involve legal team to confirm the move to github.

cc: @silabs-Tabi

@rzr
Copy link
Contributor Author

rzr commented Oct 7, 2025

Once this base is merged, I can share more details on how to deal with OSS compliance using reuse tool.

I have managed to produce a SDPX sbom to distribute along software (and comply OSS duties), If any interest i can share detail of the journey of opening z-wave (from the legal aspect at least)

#3

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