kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5400 from nikhita/licensing-move 

Remove licensing subproject, move doc to vendor.md
This commit is contained in:
Kubernetes Prow Robot 2021-01-13 05:20:36 -08:00 committed by GitHub
parent f2550643ea c0e8b136e5
commit dfecebceaa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
contributors/devel/sig-architecture/vendor.md
View File

@ -164,10 +164,14 @@ Additionally:
- If this is all good, approve, but don't LGTM, unless you also do code review - If this is all good, approve, but don't LGTM, unless you also do code review
or unless it is trivial (e.g. moving from k/k/pkg/utils -> k/utils). or unless it is trivial (e.g. moving from k/k/pkg/utils -> k/utils).
Licenses for dependencies are specified by the CNCF [Allowlist Policy].
All new dependency licenses should be reviewed by @kubernetes/dep-approvers to ensure that they All new dependency licenses should be reviewed by @kubernetes/dep-approvers to ensure that they
are compatible with the Kubernetes project license. It is also important to note are compatible with the Kubernetes project license. It is also important to note
and flag if a license has changed when updating a dependency, so that these can and flag if a license has changed when updating a dependency, so that these can
also be reviewed. also be reviewed.
For reference, whitelisted licenses as per the CNCF Whitelist Policy are In case of questions or concerns regarding the allowlist policy, please create
mentioned [here](https://git.k8s.io/sig-release/licensing/README.md#licenses-for-dependencies). an issue or send an email to the [SIG Architecture] mailing list.
[Allowlist Policy]: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md
[SIG Architecture]: https://groups.google.com/forum/#!forum/kubernetes-sig-architecture

4
sig-release/README.md
View File

@ -51,10 +51,6 @@ subprojects, and resolve cross-subproject technical issues and decisions.
## Subprojects ## Subprojects
The following [subprojects][subproject-definition] are owned by sig-release: The following [subprojects][subproject-definition] are owned by sig-release:
### Licensing
The Licensing subproject is responsible for analyzing/reporting/remediating licensing concerns within the Kubernetes project orgs.
- **Owners:**
- https://raw.githubusercontent.com/kubernetes/sig-release/master/licensing/OWNERS
### Release Engineering ### Release Engineering
The Release Engineering subproject is responsible for the [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering) and [tools](https://github.com/kubernetes/release) used to create/maintain Kubernetes release artifacts. The Release Engineering subproject is responsible for the [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering) and [tools](https://github.com/kubernetes/release) used to create/maintain Kubernetes release artifacts.
- **Owners:** - **Owners:**

5
sigs.yaml
View File

@ -1792,11 +1792,6 @@ sigs:
- name: sig-release-admins - name: sig-release-admins
description: Admins for SIG Release repositories description: Admins for SIG Release repositories
subprojects: subprojects:
- name: Licensing
description: |
The Licensing subproject is responsible for analyzing/reporting/remediating licensing concerns within the Kubernetes project orgs.
owners:
- https://raw.githubusercontent.com/kubernetes/sig-release/master/licensing/OWNERS
- name: Release Engineering - name: Release Engineering
description: | description: |
The Release Engineering subproject is responsible for the [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering) and [tools](https://github.com/kubernetes/release) used to create/maintain Kubernetes release artifacts. The Release Engineering subproject is responsible for the [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering) and [tools](https://github.com/kubernetes/release) used to create/maintain Kubernetes release artifacts.