Update private-distributors-list.md #50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
size/XS
|
/auto-cc @philips |
|
@swamymsft could you please add the application to the commit message as done with the canonical: 49b5e06#diff-49e086cea35a7ca0f86fae6ba77880c9 |
done, does it look good now? |
|
Yes, but can you squash everything down? |
<!-- Please answer the following questions and provide supporting evidence for meeting the membership criteria. --> Actively monitored security email alias for our project: security@loodse.com 1. Be an actively maintained and CNCF certified distribution of Kubernetes components. Yes, we have Kubermatic and KubeOne https://github.com/kubermatic/kubeone 2. Have a user base not limited to your own organization. KubeOne is open source and kubermatic is used by several enterprises e.g. https://metakube.syseleven.de 3. Have a publicly verifiable track record up to present day of fixing security issues. We are working on upstream patches for https://github.com/kubernetes/dashboard Additional we have an security newsletter where we announce all upstream patches https://www.loodse.com/newsletter/ 4. Not be a downstream or rebuild of another distribution. This does not apply, Kubermatic and KubeOne are unique. 5. Be a participant and active contributor in the community. We have several member who are working on upstream project e.g. https://github.com/nikhita https://github.com/maciaszczykm https://github.com/floreks https://github.com/alvaroaleman 6. Accept the Embargo Policy. We accept it 7. Be willing to contribute back. We are definitely willing to help! 8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution. Brandon Philips
I squashed the commits. |
|
/lgtm /approve |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjcullen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
tallclair
added a commit
to tallclair/k8s.io
that referenced
this pull request
Nov 15, 2019
Instantiate changes in kubernetes/committee-security-response#50 for kubernetes/committee-security-response#48. /cc @swamymsft @scheeles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding Loodse to the private distribution list based on the application