Adding process and template for license exceptions

.github/ISSUE_TEMPLATE/license-exception-request.yaml

@@ -0,0 +1,68 @@
+---
+name: Licensing Exception Request
+description: Submit an exception request
+title: "[License Exception Request] [Project] [License]"
+labels:
+  - licensing
+assignees: krook,amye
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Please note:
+
+        If it is Apache-2.0 for code or CC-BY-4.0 for documentation, no further exception request is required.
+
+
+        Does it meet the [Allowlist policy](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md)? If so, no further exception request is required.
+
+
+        For all other license exception requests, we need the following information.
+
+
+        ### License Exception Request:
+  - type: textarea
+    id: introduction
+    attributes:
+      label: Component details
+      description: What is the third party component (name, URL, and version if available)?
+    validations:
+      required: true
+  - type: input
+    id: name
+    attributes:
+      label: License name
+      description: What is the full name or title of the license?
+    validations:
+      required: true
+  - type: textarea
+    id: modifications
+    attributes:
+      label: Code modified?
+      description: Will the code be used in modified or unmodified form?
+    validations:
+      required: true
+  - type: textarea
+    id: license-exception
+    attributes:
+      label: Changes contributed?
+      description: If modified, will changes be contributed back to the upstream project?
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Any alternatives?
+      description:
+        Are there any alternative components available with equivalent
+        functionality under a more permissive license? If so, is it possible to
+        use that component instead?
+    validations:
+      required: true
+  - type: textarea
+    id: integration
+    attributes:
+      label: Integrates with other components?
+      description:
+        How does this component integrate with or interact with, if at all,
+        other components of the project?
+    validations:
+      required: true

allowed-third-party-license-policy.md

@@ -57,3 +57,19 @@ List.
 [Allowlist License Policy]: #cncf-allowlist-policy
 [Approved Licenses]: #approved-licenses-for-allowlist
 [CNCF Charter]: https://github.com/cncf/foundation/blob/master/charter.md
+
+### Process for applying for an exception
+
+This outlines the process for applying for an exception to the Intellectual Property policy referenced above.
+
+- A CNCF project maintainer can file a request for an exception using the issue template. 
+
+Exceptions should be filed by the project using the component - the exception applies to how the component is being used. 
+
+- A staff member will review and add to the [Licensing Exception Board](https://github.com/cncf/foundation/projects/1)
+- Staff will work with Legal to create an agenda for the Legal Committee to review and present a recommendation to the Governing Board. 
+- A vote is called according to the [CNCF Charter](https://github.com/cncf/foundation/blob/master/charter.md).
+- If the vote is approved and the resolution passes, Staff will post in the issue, linking to the PR where this has been approved.
+- If the vote is not approved, the issue will be closed. 
+
+