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

Use Flow & prettier #309

Merged
merged 4 commits into from
Sep 1, 2017
Merged

Use Flow & prettier #309

merged 4 commits into from
Sep 1, 2017

Conversation

rtfeldman
Copy link
Owner

No description provided.

@dustinfarris
Copy link
Contributor

Flow's license is BSD+Patents. Does that now extend to elm-css, and, by further extension, to my project? Just curious.

@rtfeldman
Copy link
Owner Author

rtfeldman commented Sep 1, 2017

I found a discussion on this, and the interpretation that seemed most likely to be accurate to me is "that wouldn't make sense." That said, "wouldn't make sense" from anyone but a lawyer isn't worth much in my book.

This comment is making me wonder if I should just move it to TypeScript so I don't have to worry about this ever again. 😛

@rtfeldman
Copy link
Owner Author

Although since TypeScript actually emits the code that gets published, it's actually more likely that TypeScript would carry an Apache2 License along with it. (That's far less burdensome than BSD+FBPatents, of course, but my preference is that elm-css's BSD-3-Clause license is all there is to it.)

@rtfeldman
Copy link
Owner Author

Thinking about it more, it would be hard to believe this would be a problem. After all, gcc is licensed under the GPL; it type-checks and emits code, and people have been using it to compile and emit non-GPL code for decades.

I can't find anything in Flow's LICENSE or PATENTS file that would lead me to believe differently, so my default thinking is that it's fine until I hear otherwise from a lawyer. 😄

@rtfeldman rtfeldman merged commit 34ef173 into master Sep 1, 2017
@rtfeldman rtfeldman deleted the flow-prettier branch September 1, 2017 22:51
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