You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/03/15 11:48:00 UTC

[jira] [Created] (LEGAL-447) Using Category-X (LGPL) in project's CI test suite?

Ash Berlin-Taylor created LEGAL-447:
---------------------------------------

             Summary: Using Category-X (LGPL) in project's CI test suite?
                 Key: LEGAL-447
                 URL: https://issues.apache.org/jira/browse/LEGAL-447
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Ash Berlin-Taylor


For Apache Airflow we want to have machine enforced code style on our CI builds on Travis (https://github.com/apache/airflow/pull/4892#issuecomment-473168239)

One of the plugins we want to use to test things is a Python module licensed under LGPL 3.0 https://github.com/PyCQA/flake8-import-order, and we wanted to confirm if this was allowable.

I have read [http://www.apache.org/legal/resolved.html#optional] and it's pertinent question of 
 "Will the majority of users want to use my product without adding the optional components?"

I think this is fine, as the majority of users of Airflow will not use this dependency, as it is not needed at runtime, nor will it be distributed in any of our artifacts. But we will install it on our CI image, and reject any change that doesn't pass it's style guide.

Is it okay to depend on a Category-X project only in the test suite? We are slightly more than just "using" the project, as we list it in the "required for developmen" section of our dependencies.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org