You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Jim Jagielski (JIRA)" <ji...@apache.org> on 2015/03/03 19:35:04 UTC
[jira] [Commented] (LEGAL-217) Use of npm with the Artistic License
2.0
[ https://issues.apache.org/jira/browse/LEGAL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345462#comment-14345462 ]
Jim Jagielski commented on LEGAL-217:
-------------------------------------
As I understand it, nothing about npm itself as included or distributed; you are simply using it as a build tool. This is similar to cases where, for example, a C-based project would include a Windows dsw file, even though Microsoft Developer Studio Workspace itself is not open source. As such, there is no issue.
> Use of npm with the Artistic License 2.0
> -----------------------------------------
>
> Key: LEGAL-217
> URL: https://issues.apache.org/jira/browse/LEGAL-217
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Sandro Boehme
>
> npm (Node.js package manager) uses the Artistic License 2.0 and I would like to use it in the build process of an Apache Sling component. Would that be according to the ASF policies?
> Please see SLING-4463 and it's parent issue SLING-4462 for details.
> Thanks in advance,
> Sandro
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org