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

How Should We License Core? #26

Open
slaymaker1907 opened this issue Feb 21, 2017 · 4 comments
Open

How Should We License Core? #26

slaymaker1907 opened this issue Feb 21, 2017 · 4 comments
Assignees
Labels
Milestone

Comments

@slaymaker1907
Copy link
Contributor

I personally like MIT, but apparently TSC is licensed under Apache which could present issues for core. However, for interpreters, it seems like we can use whatever license we want since they do not use the TSC compiler.

@danielscottjames
Copy link
Member

I think we are only obligated to include the TSC license with our bundled version, and we can license sinap-core however we want.

@cj-dimaano
Copy link
Member

I believe Daniel is correct, but to highlight what I think is most important:

we are only obligated to include the TSC license with our bundled version

@Sheyne Sheyne modified the milestones: 1.0, Beta Mar 21, 2017
@Sheyne Sheyne closed this as completed Apr 4, 2017
@Sheyne Sheyne reopened this Apr 4, 2017
@Sheyne
Copy link
Member

Sheyne commented Apr 4, 2017

This is only relevant to sinap-typescript, but I don't want 4 issue trackers. Propose we move this to sinap-ide?

@danielscottjames
Copy link
Member

Do it

@Sheyne Sheyne modified the milestones: 2.0, 1.0 Apr 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants