From 9f4998b1007de3d810f7f29af3ce9da02f22c790 Mon Sep 17 00:00:00 2001 From: Brandt Keller Date: Wed, 19 Jun 2024 16:58:04 +0000 Subject: [PATCH] chore(governance): fixing ci issues Signed-off-by: Brandt Keller --- ci/spelling-config.json | 5 ++--- governance/presentations.md | 2 ++ governance/process.md | 4 ++-- website/README.md | 2 +- 4 files changed, 7 insertions(+), 6 deletions(-) diff --git a/ci/spelling-config.json b/ci/spelling-config.json index 766761cfa..b8243b39a 100644 --- a/ci/spelling-config.json +++ b/ci/spelling-config.json @@ -23,8 +23,8 @@ "CMMC", "CNCF", "CNSMAP", - "CNSWP's", "CNSWP", + "CNSWP's", "codecov", "CODEOWNERS", "Configu", @@ -97,6 +97,7 @@ "OWASP", "Oxley", "Packagist", + "pagefind", "pcre", "PEAR", "pearweb", @@ -125,7 +126,6 @@ "sscsp", "SSCSP", "SSDF", - "SSDF", "stdlib", "superseded", "supplychain", @@ -140,7 +140,6 @@ "triaging", "trojanized", "TTPS", - "TTPS", "Twintag", "unencrypted", "unpatched", diff --git a/governance/presentations.md b/governance/presentations.md index d586a506b..648b27575 100644 --- a/governance/presentations.md +++ b/governance/presentations.md @@ -13,11 +13,13 @@ following guidelines. - Presentations should abide by the CNCF code of conduct Examples of topics that are within scope: + - Open source project presentations - Security use-cases and case studies - Open source community efforts - whitepapers, communities, standards, etc. Examples of topics that do NOT meet the guidelines: + - Vendor pitches and marketing heavy presentations - Topics unrelated to security - Topics that are help desk questions, that have a definitive, known searchable answer diff --git a/governance/process.md b/governance/process.md index 392f3eb64..bbbe6ba51 100644 --- a/governance/process.md +++ b/governance/process.md @@ -57,7 +57,7 @@ informative note. ### Raising an Issue Anyone is welcome to raise an issue either as a suggestion or as a proposal. -These will follow the process described in [proposals and suggestions](#suggestions-proposals--presentations). +These will follow the process described in Suggestions, proposals, & presentations. ## Suggestions, proposals, & presentations @@ -148,7 +148,7 @@ line with the [mission and charter](charter.md). interested in working on the project is able to attend, then add the issue to the meeting agenda: include a link and the name of the person who will present the proposal in the "Planned Meeting" area of the - [meeting notes][https://github.com/cncf/tag-security#meeting-times]. + [meeting notes](https://github.com/cncf/tag-security#meeting-times). Then at the meeting: * The presenter should screen share the github issue (or ask the meeting diff --git a/website/README.md b/website/README.md index adc74f45b..4a6e13c4e 100644 --- a/website/README.md +++ b/website/README.md @@ -14,7 +14,7 @@ Configuration is set in [config.toml](./config.toml). To set up a local dev environment make sure you have [Hugo Extended](https://gohugo.io/installation/linux/#editions), [npm](https://www.npmjs.com/), and [rsync](https://github.com/RsyncProject/rsync) installed, then run the following: -``` +```bash git clone git@github.com:cncf/tag-security.git cd tag-security/website/ make deps