Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize SDK licenses on MIT #56

Closed
9 tasks done
Tracked by #64
chadwhitacre opened this issue Oct 19, 2022 · 3 comments
Closed
9 tasks done
Tracked by #64

Standardize SDK licenses on MIT #56

chadwhitacre opened this issue Oct 19, 2022 · 3 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Oct 19, 2022

Our docs say MIT is our standard license for SDKs. Let's make that real. This is coming up now because a new SDK took a cue from sentry-javascript and ended up with the wrong license.

Here are the SDKs on https://open.sentry.io/structure/ that aren't MIT:

┆Issue is synchronized with this Jira Epic by Unito

@chadwhitacre
Copy link
Member Author

Going with [initial pub] for copyright year since that is status quo, in future we should try to get to [initial pub]-[current release] but that requires automation in many projects so out of scope here.

@Lms24
Copy link
Member

Lms24 commented Oct 19, 2022

Just saw the PR in the JS repo
@chadwhitacre I suppose we should also change this in the (coming-soon) unplugin? Just asking b/c it's technically not an SDK but rather something like a utility for sourcemaps upload

@chadwhitacre
Copy link
Member Author

@Lms24 Seems reasonable, yes. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants