-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Potential Issue with Licensing #34
Comments
Hello @YusukeSano, Thanks for reaching out. So here's the existing LICENSE from the official microsoft/fluentui-emoji repository. Which clearly mentions the all the limitations and use-cases. I've also mentioned everything clearly in the readme file (at the bottom) about the original owner and how these things are being collected. I hope this clarifies everything. I know things is still vague and confusing. But my intention was to make those beautiful looking emojis accessible for everyone (personal use) to make their work standout. If you any more queries, please let me know. Regards, |
Thank you for your response. I understand that the existing LICENSE in the official microsoft/fluentui-emoji repository outlines the limitations and use-cases, and that you've provided additional information in the README file regarding the original owner and the collection process. However, it's important to note that the license specifically applies to non-animated emojis, and the files collected from Emojipedia are not covered under the MIT License.
While making these emojis accessible for personal use is a commendable goal, I believe it is not appropriate to publish them under the MIT License without explicit permission. |
@YusukeSano Thanks for the explanation and I'll do some research and probably reach out to them. |
There may be an issue with the licensing information in this repository.
In the official microsoft/fluentui-emoji repository, a Microsoft team member mentioned:
microsoft/fluentui-emoji#51 (comment)
Since these files may fall under the same restrictions, I recommend updating the licensing information to reflect this.
The text was updated successfully, but these errors were encountered: