Draft of stronger cautionary language for forks of Tidepool's code#347
Open
Draft of stronger cautionary language for forks of Tidepool's code#347
Conversation
toddkazakov
approved these changes
Feb 24, 2026
darinkrauss
approved these changes
Feb 26, 2026
Contributor
darinkrauss
left a comment
There was a problem hiding this comment.
Only one comment for your review.
| > | ||
| > Tidepool reserves the right to take appropriate action, including but not limited to legal action, to enforce its Terms of Use and protect its trademarks, users' safety, and reputation. | ||
| > | ||
| > If you have questions about what is or is not permitted, please contact us **before** distributing your derived work. |
Contributor
There was a problem hiding this comment.
Contact us how? Do we want a specific email address? Perhaps something other than support?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is in response to few recent cases where careless 3rd party developers ended up co-mingling their fork with Tidepool's products.