[iot-pmc] LICENSE file for dual-licensed project

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[iot-pmc] LICENSE file for dual-licensed project

From: Kevin Herron <kevinherron@xxxxxxxxx>
Date: Wed, 11 Oct 2017 09:10:43 -0700
Delivered-to: iot-pmc@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/iot-pmc>
List-help: <mailto:iot-pmc-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/iot-pmc>, <mailto:iot-pmc-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/iot-pmc>, <mailto:iot-pmc-request@eclipse.org?subject=unsubscribe>

Quick question for anyone who might know:

Eclipse Milo is dual licensed under both EPL and EDL. I mention both in the comment header and include both licenses in HTML format in the base of the repo.

A question has arisen as to whether I should also have the "standard" LICENSE file in the base as well, and if so, what should it contain? Currently it's there and has just the text of the EPL in it.

Does anybody know what the correct approach is?

Follow-Ups:
- Re: [iot-pmc] LICENSE file for dual-licensed project
  - From: Wayne Beaton

Prev by Date: [iot-pmc] [CQ 14493] lmdbjava Version: 0.0.5
Next by Date: [iot-pmc] [CQ 14494] MongoDB Java Driver Version: 3.5.0
Previous by thread: [iot-pmc] [CQ 14493] lmdbjava Version: 0.0.5
Next by thread: Re: [iot-pmc] LICENSE file for dual-licensed project
Index(es):
- Date
- Thread

Breadcrumbs