Skip to content

Latest commit

 

History

History
81 lines (41 loc) · 2.78 KB

Notices.md

File metadata and controls

81 lines (41 loc) · 2.78 KB
Raw

Notices

Code of Conduct

The Code of Conduct is available in the repository in CODE_OF_CONDUCT.md.

Contact for Code of Conduct issues or inquires: hello@fission.codes

License Acceptance

Per Community Specification License 1.0 Section 2.1.3.3, Licensees may indicate their acceptance of the Community Specification License by issuing a pull request to the Specification’s repository’s Notice.md file, including the Licensee’s name, authorized individuals' names, and repository system identifier (e.g. GitHub ID), and specification version.

A Licensee may consent to accepting the current Community Specification License version or any future version of the Community Specification License by indicating "or later" after their specification version.

Licensee’s name: Philipp Krüger

Authorized individual and system identifier: matheus23

Specification version: 0.2.0-alpha or later

Licensee’s name: Brooklyn Zelenka

Authorized individual and system identifier: expede

Specification version: 0.2.0-alpha or later

Licensee’s name: Daniel Holmgren

Authorized individual and system identifier: dholms

Specification version: 0.2.0-alpha or later

Licensee’s name: Brendan O'Brien

Authorized individual and system identifier: b5

Specification version: 0.2.0-alpha or later

Withdrawals

Name of party withdrawing:

Date of withdrawal:

Exclusions

This section includes any Exclusion Notices made against a Draft Deliverable or Approved Deliverable as set forth in the Community Specification Development License. Each Exclusion Notice must include the following information:

  • Name of party making the Exclusion Notice:

  • Name of patent owner:

  • Specification:

  • Version number:

For issued patents and published patent applications:

(i)	patent number(s) or title and application number(s), as the case may be:

(ii)	identification of the specific part(s) of the Specification whose implementation makes the excluded claim a Necessary Claim.

For unpublished patent applications must provide either:

(i) the text of the filed application; or

(ii) identification of the specific part(s) of the Specification whose implementation makes the excluded claim a Necessary Claim.