Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [iot-pmc] EPL-2.0 NOTICE File?
Wayne,

I'm going to remove the notice.html file in the branch I'm doing the license change in.

Later, after master has had the change merged in, I'll notify EMO and try to get a NOTICE file based on the output of that script.

On Mon, Nov 27, 2017 at 6:47 AM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Kevin.

That file is the SUA. The SUA was never really a good fit for projects that aren't building Eclipse Platform Plug-ins and Features. We recently spent time to generalize the legal documentation requirements. You'll see the results in the handbook. We only rolled them out a short time  ago, and haven't really done enough yet to tell projects about them.

The short answer is that you can replace the notice.html file with a NOTICE file that looks something along the lines of what is generated here:


Note that this is an experimental script. FWIW, I took a quick look at your source code and your headers are fine and don't need to be changed (they're different than what is suggested in the script). Also, the way that you have the licenses laid out seems fine to me, but you may consider replacing the three license files in the root with the one that's described in the guide.

Note that the script will generate something different when you switch to the EPL-2.0. You can make that happen by sending a note to EMO asking us to update our database. There's more here: https://www.eclipse.org/org/documents/epl-2.0/faq.php#h.tci84nlsqpgw

HTH,

Wayne


On Sun, Nov 26, 2017 at 10:15 AM, Kevin Herron <kevinherron@xxxxxxxxx> wrote:
Oliver,

More specifically, I'm asking about replacing this file: https://github.com/eclipse/milo/blob/master/notice.html

On Sun, Nov 26, 2017 at 7:14 AM, Oliver Kopp <kopp.dev@xxxxxxxxx> wrote:
Dear Kevin,

Did you check with https://www.eclipse.org/projects/handbook/#legaldoc-notice? Are you sure, you are asking about NOTICE and not LICENSE?

Cheers,

Oliver


Am 25.11.2017 23:47 schrieb "Kevin Herron" <kevinherron@xxxxxxxxx>:
I'm not sure what I'm supposed to do with my existing notice file when switching to EPL-2.0.

One interpretation says it should just be replaced wholesale with the same contents as the EPL-2.0 license. If this is the case... do we really still need a notice file in the repo?

Another would be to replace *occurrences* of "EPLv1" and similar text inside the notice with "EPLv2".

Anybody know what the correct approach is?

_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc



_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc



_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc


Back to the top