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

Update library to meet the requirements of Elastic UI's apache license #17

Open
1 of 6 tasks
mpRegalado opened this issue Jan 18, 2022 · 0 comments · Fixed by #21
Open
1 of 6 tasks

Update library to meet the requirements of Elastic UI's apache license #17

mpRegalado opened this issue Jan 18, 2022 · 0 comments · Fixed by #21

Comments

@mpRegalado
Copy link
Member

Description

In order to be able to use this project, we must make sure we are meeting the requirements set by the upstream repository in their licensing terms.

Elastic UI v29.3.2, the upstream repository base for this fork, uses an Apache v2 license (https://github.com/elastic/eui/blob/v29.3.2/LICENSE) for it's code and product, meaning it's possible to fork it as long as the conditions on the license are met.

Redistribution

Section 4 of the license specifies the conditions required in order to redistribute Derivative Works of the original, such as this repository.

Trademarks

According to the terms of the license, it does not grant permission to use any trade names, trademarks, service marks or product names of the licensor, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.

This project is currently in violation of this licensing term:

  • The Icon component contains assets that represent service marks of products by the Licensor. Including but not limited to logo_kibana.svg, logo_elastic.svg, logo_elasticsearch.svg, etc... All icons under src/components/icon/assets should be reviewed and removed accordingly
  • All components and scss classes follow the naming scheme eui----, this represents a violation on the product names section and should be removed or renamed before this fork is viable.
@Desvelao Desvelao linked a pull request Jan 28, 2022 that will close this issue
4 tasks
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 a pull request may close this issue.

1 participant