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.

Sign up for GitHub

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

Jump to bottom

Clear License Explanation #8950

Open
zacheryph opened this issue Mar 16, 2024 · 0 comments
Open

Clear License Explanation #8950

zacheryph opened this issue Mar 16, 2024 · 0 comments
Assignees
@geospatialem
Labels
1 - assigned Issues that are assigned to a sprint and a team member. docs Issues relating to documentation updates only. estimate - 3 A day or two of work, likely requires updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Milestone
2025-03-25 - 3.1....

Comments

@zacheryph
Copy link

Description

Hi. My question is; Can I use Calcite in a project unrelated to Arcgis? For the scope of the Calcite Design System, how does the MLA license terms compare to open source licenses?

I am not a lawyer, and trying to understand the actual licensing terms for the Calcite Design System isn't exactly easy. The LICENSE file simply says to follow the MLA. The MLA makes mention of Development use, deployment license, and Content (vs Customer Content) which Calcite could fall... kind of under any of? all of? none of them? Now, the MLA does not distinctly say anything (that I can find) about Offerings, Development use, Content or any such only being usable within the Arcgis platform, or "Value Added Applications". I just don't want to spend time looking at Calcite as a possible solution if its not. A simple "cliffs notes" of the MLA (at least in the case of Calcite for my concerns anyway) would be nice to have?

Which Component

LICENSE

Resources

No response
@zacheryph zacheryph added 0 - new New issues that need assignment. docs Issues relating to documentation updates only. needs triage Planning workflow - pending design/dev review. labels Mar 16, 2024
@geospatialem geospatialem added spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. and removed needs triage Planning workflow - pending design/dev review. labels Sep 20, 2024
@geospatialem geospatialem self-assigned this Sep 20, 2024
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Sep 20, 2024
@geospatialem geospatialem added 2 - in development Issues that are actively being worked on. 1 - assigned Issues that are assigned to a sprint and a team member. and removed 1 - assigned Issues that are assigned to a sprint and a team member. 2 - in development Issues that are actively being worked on. labels Nov 7, 2024
@geospatialem geospatialem added p - high Issue should be addressed in the current milestone, impacts component or core functionality estimate - 3 A day or two of work, likely requires updates to tests. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@geospatialem geospatialem

Labels
1 - assigned Issues that are assigned to a sprint and a team member. docs Issues relating to documentation updates only. estimate - 3 A day or two of work, likely requires updates to tests. p - high Issue should be addressed in the current milestone, impacts component or core functionality spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Projects
None yet
Milestone
2025-03-25 - 3.1.0 Mar Release
Development

No branches or pull requests
2 participants
@zacheryph @geospatialem