Skip to content

Commit 24d3c11

Browse files
authored
Merge branch 'main' into feature-add-sec-assessment-facilitator-role-details
Signed-off-by: Andrés Vega <av@messier42.com>
2 parents 153e5ae + 8af95f1 commit 24d3c11

File tree

190 files changed

+18529
-1255
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

190 files changed

+18529
-1255
lines changed

.github/ISSUE_TEMPLATE/joint-review.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Security Provider: yes/no (e.g. Is the primary function of the project to suppor
2424
- [ ] Lead security reviewer
2525
- [ ] 1 or more additional reviewer(s)
2626
- [ ] Every reviewer has read [security reviewer guidelines](https://github.com/cncf/tag-security/blob/main/assessments/guide/security-reviewer.md) and stated declaration of conflict
27-
- [ ] Sign off by 2 chairs on reviewer conflicts
27+
- [ ] Sign off by facilitator on reviewer conflicts
2828
- [ ] Create slack channel (e.g. #sec-assess-projectname)
2929
- [ ] Project lead provides draft document - see [outline](https://github.com/cncf/tag-security/blob/main/assessments/guide/joint-review.md)
3030
- [ ] "Naive question phase" Lead Security Reviewer asks clarifying questions

.github/ISSUE_TEMPLATE/proposal.md

+28-5
Original file line numberDiff line numberDiff line change
@@ -9,21 +9,44 @@ assignees: ''
99

1010
Description: what's your idea?
1111

12-
Impact: Describe the customer impact of the problem. Who will this help? How will it help them?
12+
Impact: Describe the customer impact of the problem. Who will this help? How
13+
will it help them?
1314

14-
Scope: How much effort will this take? ok to provide a range of options if or "not yet determined" for initial proposals. Feel free to include proposed tasks below or link a Google doc
15+
Scope: How much effort will this take? ok to provide a range of options if or
16+
"not yet determined" for initial proposals. Feel free to include proposed tasks
17+
below or link a Google doc
18+
19+
Intent to lead:
20+
21+
* [ ] **I volunteer to be a project lead on this proposal if the community is
22+
interested in pursing this work.** This statement of intent does not preclude
23+
others from co-leading or becoming lead in my stead.
24+
25+
Proposal to Project:
26+
27+
* [ ] Added to the planned meeting template for _mm dd_
28+
* [ ] Raised in a Security TAG meeting to determine interest - _mm dd_
29+
* [ ] Collaborators comment on issue for determine interest and nominate project
30+
lead
31+
* [ ] Scope determined via meeting _mm dd_ and/or shared document *add link*
32+
with call for participation in #tag-security slack channel thread *add link*
33+
and mailing list email *add link*
34+
* [ ] Scope presented to Security TAG leadership and Sponsor is assigned
1535

1636
TO DO
37+
1738
- [ ] Security TAG Leadership Representative:
1839
- [ ] Project leader(s):
40+
- [ ] Issue is assigned to project leaders and Security TAG Leadership
41+
Representative
1942
- [ ] Project Members:
20-
- [ ] _Fill in addition TODO items here so the project team and community can see progress!_
21-
- [ ] Scope
43+
- [ ] _Fill in addition TODO items here so the project team and community can
44+
see progress!_
45+
- [ ] Scope
2246
- [ ] Deliverable(s)
2347
- [ ] Project Schedule
2448
- [ ] Slack Channel (as needed)
2549
- [ ] Meeting Time & Day:
2650
- [ ] Meeting Notes (link)
2751
- [ ] Meeting Details (zoom or hangouts link)
2852
- [ ] Retrospective
29-
+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: Unconference talk proposal
3+
about: You have a proposal for the in-person KubeCon Security Hub Unconference. Unconference sessions can be more casual group conversations about a topic. Submitters must be attending KubeCon in-person.
4+
title: "[Unconference] some descriptive title"
5+
labels: "unconference, triage-required"
6+
assignees: ''
7+
8+
---
9+
10+
Description: What's your topic?
11+
Benefits to Ecosystem: Why is this talk or discussion important to cloud native security?
12+
Additional info:
13+
- Reference to supporting material
14+
- Feel free to delete this section if you don't have more info
15+
- Let us know if you have any availability limitations for us to consider

.github/auto_request_review.yml

+5
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ reviewers:
2525
- mlieberman85
2626
- ragashreeshekar
2727
- sublimino
28+
- eddie-knight
2829
supply-chain-security-reviewers:
2930
- mnm678
3031
- mlieberman85
@@ -40,6 +41,8 @@ reviewers:
4041
- ashutosh-narkar
4142
controls-reviewers:
4243
- JonZeolla
44+
assessments-reviewers:
45+
- eddie-knight
4346

4447
files:
4548
# Keys are glob expressions.
@@ -54,6 +57,8 @@ files:
5457
- supply-chain-security-reviewers #group
5558
'cloud-native-controls/**':
5659
- controls-reviewers #group
60+
'assessments/**':
61+
- assessments-reviewers #group
5762

5863
options:
5964
ignore_draft: true #draft PRs are ignored

.github/settings.yml

+2-76
Original file line numberDiff line numberDiff line change
@@ -11,79 +11,5 @@ repository:
1111
homepage: https://cncf.io/projects
1212

1313
# Collaborators: give specific users access to this repository.
14-
# Note: changing this file will update the users visible in Github UI
15-
# see /governance/roles.md for details on write access policy
16-
# note that the permissions below may provide wider access than needed for
17-
# a specific role, and we trust these individuals to act according to their
18-
# role. If there are questions, please contact one of the chairs.
19-
collaborators:
20-
# Chairs
21-
- username: achetal01
22-
permission: admin
23-
24-
- username: lumjjb
25-
permission: admin
26-
27-
- username: sublimino
28-
permission: admin
29-
30-
# Chairs Emeriti
31-
- username: ultrasaurus
32-
permission: push
33-
34-
- username: pragashj
35-
permission: push
36-
37-
- username: dshaw
38-
permission: push
39-
40-
- username: TheFoxAtWork
41-
permission: push
42-
43-
# Technical Leads
44-
- username: ashutosh-narkar
45-
permission: push
46-
47-
- username: anvega
48-
permission: push
49-
50-
- username: JustinCappos
51-
permission: push
52-
53-
- username: PushkarJ
54-
permission: push
55-
56-
- username: mnm678
57-
permission: push
58-
59-
- username: mlieberman85
60-
permission: push
61-
62-
- username: ragashreeshekar
63-
permission: push
64-
65-
# Contributing Reviewers
66-
# Submit Reviews to PRs based on this grouping: https://github.com/cncf/tag-security/blob/main/.github/auto_request_review.yml
67-
- username: lirantal
68-
permission: read
69-
70-
# Leading the policy project #987
71-
- username: jkjell
72-
permission: push
73-
74-
# Security Assessment Facilitator
75-
# merge PRs in /assesssments according to guidelines
76-
# triage related issues
77-
# JustinCappos
78-
79-
# Security Reviewers
80-
# issues may be assigned, edited by assignee
81-
# merge PRs for assigned issue according to guidelines
82-
# JustinCappos, ultrasaurus, lumjjb
83-
- username: JustinCormack
84-
permission: push
85-
86-
87-
# Meeting Facilitators
88-
# ultrasaurus, dshaw, pragashj, lumjjb, justincormack, izgeri, JustinCappos, magnologan, TheFoxAtWork, anvega, achetal01, ashutosh-narkar,
89-
# chasemp, pushkarj, jonzeolla
14+
# Note that the permissions are controlled using CLOWarden in the https://github.com/cncf/people/blob/main/config.yaml file
15+
# Please create a PR in the https://github.com/cncf/people/ repo to change user access

.gitignore

+5
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,8 @@
22
node_modules
33
modified
44
*.DS_Store*
5+
6+
# Hugo file replication
7+
website/root/*
8+
!website/root/.gitkeep
9+
website/static/design/

0 commit comments

Comments
 (0)