2019 should be fine.
Remove the Oracle copyright from the final versions of specs.
(Do not remove Oracle copyright from source code.)
Tom Jenkinson wrote on 8/1/19 11:43 PM:
Do we want the copyright to just be 2019 for Eclipse or
should it be 2018-2019?
+1
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter:
@kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>,
Kevin Sutter <sutter@xxxxxxxxxx>
Date:
08/01/2019
05:26 PM
Subject:
[EXTERNAL]
Re: [jakartaee-spec-project-leads] Copyrights of final
specifications
And I just realized that there
actually
isn't any copyright statement in the boilerplate
specification template!
Argh!
I think we should add the copyright statement to the
license-efsl.adoc
file:
---
a/src/main/asciidoc/license-efsl.adoc
+++ b/src/main/asciidoc/license-efsl.adoc
@@ -14,6 +14,8 @@ endif::[]
Release: {revdate}
....
+Copyright (c) 2019 Eclipse Foundation.
+
=== Eclipse Foundation Specification License
By using and/or copying this document, or the Eclipse
Foundation
Look good?
Bill Shannon wrote on 8/1/19 3:05
PM:
I'm assuming we want:
Copyright (c) 2019 Eclipse Foundation.
Kevin Sutter wrote on 8/1/19 3:02
PM:
Bill,
What dates should we use for the Copyright statements?
Leave the
original dates or just use 2019? And, how should we
attribute the
Eclipse Foundation? Maybe these are questions for Mike or
Wayne...
For example, the Platform spec has this:
Copyright (c) 2017, 2019 Oracle and/or its affiliates. All
rights reserved.
I'll take a guess it would become this:
Copyright (c) 2019 Eclipse Foundation. All rights reserved.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter:
@kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Bill
Shannon <bill.shannon@xxxxxxxxxx>
To: JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date: 08/01/2019
03:56 PM
Subject: [EXTERNAL]
[jakartaee-spec-project-leads] Copyrights of final
specifications
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
I was wrong.
I've been telling many of you that the specifications,
including the javadocs,
should be copyright of Oracle since they're derived from
source code that
is
copyright of Oracle. That would be the standard Oracle
copyright
approach.
Apparently the Eclipse Foundation Specification License
requires that,
even though the Eclipse Foundation hasn't directly
contributed to the
content of the specifications, the final versions of the
specifications
(which includes the specification documents and the
javadocs), must be
copyright "Eclipse Foundation". We're assigning the
Eclipse
Foundation
copyright to our contributions for these specifications.
Sorry, but this means updating all our submissions to
reflect this copyright
requirement.
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
