www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandro Boehme (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-217) Use of npm with the Artistic License 2.0
Date Tue, 03 Mar 2015 23:01:05 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345947#comment-14345947
] 

Sandro Boehme commented on LEGAL-217:
-------------------------------------

To be honest, it's a long time ago when I was developing in C so I can not really compare
it well.
No npm artifact is included. The Maven plugin downloads, installs and calls npm at build time.
But artifacts from npm will not be checked in and not be distributed.

The problem might be that the npm license is not so much about npm itself but more about the
packages it manages. At least from what I understand.
This is one of the first sentences of its Artistic License 2.0:
"This license establishes the terms under which a given free software Package may be copied,
modified, distributed, and/or redistributed."
A npm package is for example a css or a JavaScript library that I would like to include in
the web based admin tool for Apache Sling. The Sling Resource Editor.

When using this setup I would not check in the packages to SVN. Instead I declare the package
names in the build tool and at build time they are downloaded and included in the resulting
jar file.
This jar file might be later distributed with a standalone server the user starts or within
a war archive the user puts to the server that he starts. In any case it contains the npm
package and the part of the HTML page that links to that package. E.g. via <script src="path/to/package/from/jar"></script>.

> 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


Mime
View raw message