Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Add a "Front Matter Requirements" section to the operations guide #54

Open
waynebeaton opened this issue Jun 17, 2021 · 0 comments
Open

Comments

@waynebeaton
Copy link
Contributor

Specification documents need to have certain elements in their front matter.

Specifically, specification documents must include:

  • The Eclipse Foundation Specification License; and
  • A statement regarding the specification's patent license.

Should anything else be included?

The statement regarding the patent license should be of the form:

This specification uses the {Implementation|Compatabile} Patent License as defined in the Eclipse Foundation's Intellectual Property Policy.

(with a link to the IP Policy)

@mmilinkov do you believe that "This specification uses..." is enough here?

Aside: (and this gets a little meta) including the Eclipse Foundation Specification License (EFSL) in the specification document does not mean the source of the specification document itself is under that license. From the perspective of the source file, the inclusion of the EFSL is just content; the document itself is under the project license. It is only the "binary" format of that document, following ratification as a component of a Final Specification that is licensed EFSL. For example, source documents in AsciiDoc format, whether or not they include the text of the EFSL, are distributed under the terms of the project license; HTML/PDF content generated from that AsciiDoc source (following ratification) are distributed under the terms of the EFSL.

@mmilinkov should we include a statement in the front matter that indicates that the EFSL and patent license only apply to documents marked as "FINAL"?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant