├── .vale.ini ├── shoutouter ├── tce.yaml ├── testdata │ ├── missing_teams.yaml │ └── good_example.yaml ├── go.mod ├── example.yaml ├── types_test.go ├── README.md ├── main.go ├── types.go └── LICENSE ├── .github └── dependabot.yml ├── README.md ├── styles └── inclusivity │ └── inclusive-terminology.yml ├── HEALTHCHECK-SHEET.md ├── INCLUSIVE_TERMINOLOGY.md ├── CODE_OF_CONDUCT.md ├── GUIDELINES.md ├── HEALTHCHECKS.md ├── SECURITY.md └── LICENSE.txt /.vale.ini: -------------------------------------------------------------------------------- 1 | StylesPath = styles 2 | 3 | [*.md] 4 | BasedOnStyles = inclusivity -------------------------------------------------------------------------------- /shoutouter/tce.yaml: -------------------------------------------------------------------------------- 1 | org: "vmware-tanzu" 2 | teams: 3 | - "tce-owners" 4 | - "tce-releng" 5 | -------------------------------------------------------------------------------- /shoutouter/testdata/missing_teams.yaml: -------------------------------------------------------------------------------- 1 | name: "test case" 2 | org: "org" 3 | token: "token" 4 | -------------------------------------------------------------------------------- /shoutouter/testdata/good_example.yaml: -------------------------------------------------------------------------------- 1 | name: "test case" 2 | org: "org" 3 | token: "token" 4 | teams: 5 | - "team" 6 | -------------------------------------------------------------------------------- /shoutouter/go.mod: -------------------------------------------------------------------------------- 1 | module github.com/nrb/velero-contributor-shoutouter 2 | 3 | go 1.14 4 | 5 | require ( 6 | github.com/google/go-github/v32 v32.1.0 7 | github.com/sirupsen/logrus v1.9.3 8 | github.com/stretchr/testify v1.8.4 9 | golang.org/x/oauth2 v0.12.0 10 | gopkg.in/yaml.v2 v2.4.0 11 | ) 12 | -------------------------------------------------------------------------------- /shoutouter/example.yaml: -------------------------------------------------------------------------------- 1 | --- 2 | name: velero 3 | org: vmware-tanzu 4 | repos: 5 | - velero 6 | - velero-plugin-for-aws 7 | - velero-plugin-for-gcp 8 | - velero-plugin-for-microsoft-azure 9 | - helm-charts 10 | devs: 11 | - ashish-amarnath 12 | - carlisia 13 | - jonasrosland 14 | - michmike 15 | - nrb 16 | - zubron 17 | - dsu-igeek 18 | teams: 19 | - velero-authors 20 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | # To get started with Dependabot version updates, you'll need to specify which 2 | # package ecosystems to update and where the package manifests are located. 3 | # Please see the documentation for all configuration options: 4 | # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates 5 | 6 | version: 2 7 | updates: 8 | - package-ecosystem: "gomod" # See documentation for possible values 9 | directory: "/shoutouter" # Location of package manifests 10 | schedule: 11 | interval: "weekly" 12 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Tanzu Community Engagement 2 | 3 | The purpose of this repository is to publish the Tanzu Community Engagement 4 | guidelines, community health measurements, and goals. 5 | 6 | ## Using the information in this repo 7 | 8 | We use these documents during the planning phase of open sourcing a new 9 | project, and during our community engagement health checks. 10 | 11 | We hope these documents can be useful for the wider open source community, 12 | as you start out new projects or want to improve already existing ones. 13 | 14 | The flow of information goes: 15 | 16 | 1. [GUIDELINES](GUIDELINES.md), used for planning and implementation of 17 | documentation, processes, and communication platforms for our open source 18 | projects. 19 | 20 | 1. [HEALTHCHECKS](HEALTHCHECKS.md), used twice yearly to see what community 21 | engagement improvements should be made in the near future. 22 | 23 | ## Further reading 24 | 25 | Within this repository we also keep the following: 26 | 27 | - [Inclusive terminology](INCLUSIVE_TERMINOLOGY.md) details and a [Vale](https://docs.errata.ai/vale/about) implementation 28 | - [Security policy template](SECURITY.md), to be modified and added to each project 29 | - [A "shoutouter" program](shoutouter/README.md) to generate reports on contributions from non-VMware community members 30 | 31 | ## Code of Conduct 32 | 33 | We use the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). 34 | 35 | ## License 36 | 37 | This project is licensed under the CC-BY-SA 4.0 License - see the [LICENSE.txt](LICENSE.txt) file for details. 38 | -------------------------------------------------------------------------------- /shoutouter/types_test.go: -------------------------------------------------------------------------------- 1 | // Copyright 2021 VMware Shoutouter contributors. All Rights Reserved. 2 | // SPDX-License-Identifier: Apache-2.0 3 | 4 | package main 5 | 6 | import ( 7 | "testing" 8 | 9 | "github.com/stretchr/testify/assert" 10 | ) 11 | 12 | func TestValidateOrg(t *testing.T) { 13 | // Missing org name should return an error 14 | c := ProjectConfig{ 15 | Token: "asdf", 16 | TeamNames: []string{"team"}, 17 | } 18 | assert.Error(t, c.Validate()) 19 | 20 | // Adding an org name will make the error go away 21 | c.OrgName = "org" 22 | assert.NoError(t, c.Validate()) 23 | } 24 | 25 | func TestValidateTeam(t *testing.T) { 26 | // Missing team names should return an error 27 | c := ProjectConfig{ 28 | Token: "asdf", 29 | OrgName: "org", 30 | } 31 | assert.Error(t, c.Validate()) 32 | 33 | // Adding a team name will make the error go away 34 | c.TeamNames = []string{"team"} 35 | assert.NoError(t, c.Validate()) 36 | } 37 | 38 | func TestValidateToken(t *testing.T) { 39 | // Missing token should return an error 40 | c := ProjectConfig{ 41 | OrgName: "org", 42 | TeamNames: []string{"team"}, 43 | } 44 | assert.Error(t, c.Validate()) 45 | 46 | // Adding a token will make the error go away 47 | c.Token = "asdf" 48 | assert.NoError(t, c.Validate()) 49 | } 50 | 51 | func TestNewConfigFromFileSucceeds(t *testing.T) { 52 | c, err := NewConfigFromFile("testdata/good_example.yaml") 53 | assert.Nil(t, err) 54 | assert.NoError(t, c.Validate()) 55 | } 56 | 57 | func TestNewConfigFromFileMissingTeams(t *testing.T) { 58 | c, err := NewConfigFromFile("testdata/missing_teams.yaml") 59 | assert.NoError(t, err) 60 | assert.Equal(t, NoTeamError, c.Validate()) 61 | } 62 | -------------------------------------------------------------------------------- /shoutouter/README.md: -------------------------------------------------------------------------------- 1 | # Contributor Shoutouter 2 | 3 | This is a small program that will look at Pull Requests on the various Velero GitHub repositories, and assemble their titles into Markdown for acknowledgement in the weekly community meeting. 4 | 5 | To use it, run: 6 | 7 | ```shell 8 | 9 | go run . --config my_file.yaml --token 10 | ``` 11 | 12 | Optionally, you can specify a number of days to find PRs within. To filter by PRs in the last month: 13 | 14 | ```shell 15 | go run . --config my_file.yaml --token --days 30 16 | ``` 17 | 18 | On macOS, you can also copy them directly to your clipboard. 19 | 20 | ```shell 21 | ./velero-shoutouts | pbcopy 22 | ``` 23 | 24 | If you do not include a GitHub API token, the program will provide you with a link to generate one with the right permissions. 25 | 26 | ## Making a config file 27 | 28 | You can make a config file with YAML that specifies the following values: 29 | 30 | 31 | ```yaml 32 | --- 33 | # Name of the shoutouts you're doing 34 | name: velero 35 | # GitHub organization to look in. All teams and repos must be within this org 36 | org: vmware-tanzu 37 | # List of repos to check 38 | repos: 39 | - velero 40 | - velero-plugin-for-aws 41 | - velero-plugin-for-gcp 42 | - velero-plugin-for-microsoft-azure 43 | - helm-charts 44 | # Core devs, if they are not in a team. This is useful if you want to include alumni or non-VMware maintainers. (optional) 45 | devs: 46 | - ashish-amarnath 47 | - carlisia 48 | - jonasrosland 49 | - michmike 50 | - nrb 51 | - zubron 52 | - dsu-igeek 53 | # GitHub teams to filter by. 54 | teams: 55 | - velero-authors 56 | 57 | ``` 58 | 59 | 60 | -------------------------------------------------------------------------------- /styles/inclusivity/inclusive-terminology.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # In our continued efforts to build inclusive communities and software, we recommend the following words be avoided in all projects. 3 | extends: substitution 4 | message: 'Use inclusive terminology. Consider "%s" instead of "%s".' 5 | link: https://github.com/vmware-tanzu/community-engagement/blob/main/INCLUSIVE_TERMINOLOGY.md 6 | level: warning 7 | ignorecase: true 8 | swap: 9 | abort(?:ed|ing|s)?: stop (v), cancel (v), halt prematurely (v), end prematurely (v), stop prematurely (v) 10 | black hat: unethical (adj) 11 | blacklist: denylist (n), block (v), banned list (n), deny (v), ban (v) 12 | blackout: restrict (v), restriction (n), outage (n), failed (adj) 13 | cakewalk: easy (v) 14 | disable: deactivate (v), when paired with “enable”, consider also changing “enable” to “activate” 15 | evict(?:ion|s)?: removal (n), remove (v), eject (v) 16 | female: (when not referring to anything other than a persona) jack (n), socket (n) 17 | kill: stop (v), halt (v) 18 | grandfathered: legacy (adj) 19 | handicap: obstacle (n), restrict (v), impede (v) 20 | (?:he|she): (when not referring to anything other than a specific person) - they 21 | male: (when not referring to anything other than a persona) plug (n) 22 | master: primary (n), main (n), leader (n), controller (n), control plane (n, in the context of Kubernetes) 23 | masterplan: overall (adj), unifying (adj) 24 | rule of thumb: rule (n, if a fixed rule), guideline (n, if recommended or common practice but not mandated) 25 | sanity (?:test|check|s)?: confidence test (n), confidence check (n) 26 | segregat(?:e|ion|s)?: separate (v), separation (v) 27 | slave: secondary (n), doer (n), replica (n), control plane node (n, in the context of Kubernetes) 28 | suffer: Alternate usage depends on what's being described; alternatives can include - decrease (v), lessen (v), shrink (v), increase (v), grow (v) 29 | war room: operations room (n), ops room (noun) 30 | white hat: ethical (adj) 31 | whitelist: allowlist (n), approved list (n), approve (v) 32 | -------------------------------------------------------------------------------- /shoutouter/main.go: -------------------------------------------------------------------------------- 1 | // Copyright 2021 VMware Shoutouter contributors. All Rights Reserved. 2 | // SPDX-License-Identifier: Apache-2.0 3 | 4 | package main 5 | 6 | import ( 7 | "flag" 8 | "fmt" 9 | "time" 10 | 11 | log "github.com/sirupsen/logrus" 12 | 13 | "github.com/google/go-github/v32/github" 14 | ) 15 | 16 | type args struct { 17 | debug bool 18 | config, token, team, org string 19 | days int 20 | } 21 | 22 | var a *args 23 | 24 | func main() { 25 | 26 | c, err := makeConfig() 27 | if err != nil { 28 | log.Fatal(err) 29 | } 30 | 31 | if err := c.Validate(); err != nil { 32 | log.Fatal(err) 33 | } 34 | 35 | p := NewProject(c) 36 | 37 | err = p.GetDevs() 38 | if err != nil { 39 | log.Fatal(err) 40 | } 41 | 42 | for _, d := range p.Devs { 43 | if d != nil { 44 | log.Debug("Login: %s\n", d.GetLogin()) 45 | } 46 | } 47 | 48 | err = p.GetReposFromTeam() 49 | if err != nil { 50 | log.Fatal(err) 51 | } 52 | 53 | log.Debug("---- REPOS ----") 54 | for _, r := range p.Repos { 55 | log.Debug("%s\n", *r.Name) 56 | } 57 | 58 | log.Debug("---- PRs ----") 59 | err = p.GetPullRequests() 60 | if err != nil { 61 | log.Fatal(err) 62 | } 63 | log.Debug("PRs Found: %d\n", len(p.PullRequests)) 64 | 65 | i := 0 66 | emptyTime := time.Time{} 67 | for _, pr := range p.PullRequests { 68 | 69 | if pr.GetMergedAt() != emptyTime { 70 | // Skip PRs older than specified dates 71 | // this works for now, but should probably be put in a function or method. 72 | if a.days > -1 { 73 | age := time.Since(pr.GetMergedAt()) 74 | if int(age.Hours()/24) > a.days { 75 | continue 76 | } 77 | } 78 | 79 | if fromMember(pr, p) { 80 | continue 81 | } 82 | i++ 83 | printShoutout(pr) 84 | } 85 | } 86 | 87 | fmt.Printf("PRs merged from non-core memembers: %d\n", i) 88 | } 89 | 90 | func init() { 91 | a = &args{} 92 | flag.StringVar(&a.config, "config", "", "--config file.yaml") 93 | flag.StringVar(&a.token, "token", "", "--token ${GITHUB_API_TOKEN}") 94 | flag.StringVar(&a.org, "org", "", "--org ${GITHUB_ORG_NAME}") 95 | flag.StringVar(&a.team, "team", "", "--team ${GITHUB_TEAM_NAME}") 96 | flag.BoolVar(&a.debug, "debug", false, "--debug for detailed logging") 97 | flag.IntVar(&a.days, "days", -1, "--days for a window to check PRs (-1 for all (default), 30 for a month)") 98 | 99 | flag.Parse() 100 | 101 | if a.debug { 102 | log.SetLevel(log.DebugLevel) 103 | } 104 | } 105 | 106 | func makeConfig() (*ProjectConfig, error) { 107 | var err error 108 | c := &ProjectConfig{} 109 | 110 | if a != nil && a.config != "" { 111 | c, err = NewConfigFromFile(a.config) 112 | } 113 | if err != nil { 114 | return nil, err 115 | } 116 | 117 | if a != nil && a.org != "" { 118 | c.OrgName = a.org 119 | } 120 | 121 | if a.team != "" { 122 | c.TeamNames = append(c.TeamNames, a.team) 123 | } 124 | 125 | if a.token != "" { 126 | c.Token = a.token 127 | } 128 | 129 | return c, nil 130 | } 131 | 132 | // Formats the shoutouts in a consistent format. 133 | func printShoutout(pr *github.PullRequest) { 134 | fmt.Printf("- [@%s](%s): [%s](%s)\n", *pr.User.Login, *pr.User.HTMLURL, *pr.Title, *pr.HTMLURL) 135 | } 136 | 137 | // fromMember determines if a PR was written by a core team member 138 | func fromMember(pr *github.PullRequest, p *Project) bool { 139 | for _, m := range p.Devs { 140 | if pr.GetUser().GetLogin() == m.GetLogin() { 141 | return true 142 | } 143 | } 144 | return false 145 | } 146 | -------------------------------------------------------------------------------- /HEALTHCHECK-SHEET.md: -------------------------------------------------------------------------------- 1 | # Open Source Project Health Checks example sheet 2 | 3 | You can use the table below to measure your own open source project community engagement health. 4 | 5 | Please see [HEALTHCHECKS](HEALTHCHECKS.md) for more information on all the measurements below. 6 | 7 | 8 | | Category | Measurement | Status | Advice | Notes | 9 | | ---------------------------- | ----------------------------------------------------------------------------------------- | ------ | ------ | ----- | 10 | | Project Maturity | Following the "Getting Started" guidelines | | | | 11 | | Project Maturity | Following CII Best Practices | | | | 12 | | Project Maturity | Regular release cadence | | | | 13 | | Project Maturity | Roadmap quality | | | | 14 | | Project Viability | Documentation thoroughness | | | | 15 | | Project Viability | Low elephant factor (if applicable) | | | | 16 | | Growth of Community | Role definitions | | | | 17 | | Growth of Community | Path to maintainership | | | | 18 | | Growth of Community | Continually onboarding new contributors | | | | 19 | | Growth of Community | Distribution of work | | | | 20 | | Growth of Community | Decision distribution - central vs distributed | | | | 21 | | Growth of Community | Communication channels are in place and used effectively | | | | 22 | | Diversity of Community | Number of contributors | | | | 23 | | Diversity of Community | Contributing organizations - monthly | | | | 24 | | Diversity of Community | Non-code contributions | | | | 25 | | Diversity of Community | Contributor breadth | | | | 26 | | Attentiveness of Maintainers | Recognition of contributors | | | | 27 | | Attentiveness of Maintainers | Retrospectives | | | | 28 | | Attentiveness of Maintainers | Release note completeness | | | | 29 | | Attentiveness of Maintainers | Transparency | | | | 30 | | User Community Engagement | User training material (visible, being updated) | | | | 31 | | User Community Engagement | Communications channel for user questions are used actively by both users and maintainers | | | | 32 | | User Community Engagement | Obvious process for user bug reports and feature requests | | | | 33 | | User Community Engagement | Meetings for user engagement, bof, best practices | | | | -------------------------------------------------------------------------------- /INCLUSIVE_TERMINOLOGY.md: -------------------------------------------------------------------------------- 1 | 2 | # Inclusive Terminology 3 | 4 | In our continued efforts to build inclusive communities and software, we recommend the following words be avoided in all projects. 5 | 6 | This list should be considered a living artifact, if you have suggestions on words we should consider adding, pleases open an issue. This list is built upon VMware’s own internal inclusive terminology as well as that of the [Inclusive Naming Initiative](https://inclusivenaming.org/). 7 | 8 | | Word | Recommendations | 9 | | --------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------: | 10 | | abort | stop (v), cancel (v), halt prematurely (v), end prematurely (v), stop prematurely (v) | 11 | | black hat | unethical (adj) | 12 | | blacklist | denylist (n), block (v), banned list (n), deny (v), ban (v) | 13 | | blackout/brownout | restrict (v), restriction (n), outage (n), failed (adj) | 14 | | cakewalk | easy (v) | 15 | | disable | deactivate (v), when paired with “enable”, consider also changing “enable” to “activate” | 16 | | eviction (n), evict (v) | removal (n), remove (v), eject (v) | 17 | | female (when not referring to anything other than a persona) | jack (n), socket (n) | 18 | | kill | stop (v), halt (v) | 19 | | grandfathered | legacy (adj) | 20 | | handicap | obstacle (n), restrict (v), impede (v) | 21 | | he, she (when not referring to anything other than a specific person) | they | 22 | | male (when not referring to anything other than a persona) | plug (n) | 23 | | master | primary (n), main (n), leader (n), controller (n), control plane (n, in the context of Kubernetes) | 24 | | masterplan | overall (adj), unifying (adj) | 25 | | rule of thumb | rule (n, if a fixed rule), guideline (n, if recommended or common practice but not mandated) | 26 | | sanity test | sanity check (n), confidence test (n), confidence check (n) | 27 | | segregate/segregation | separate (v), separation (v) | 28 | | slave | secondary (n), doer (n), replica (n), control plane node (n, in the context of Kubernetes) | 29 | | suffer | Alternate usage depends on what's being described; alternatives can include: decrease (v), lessen (v), shrink (v), increase (v), grow (v) | 30 | | war room | operations room (n), ops room (noun) | 31 | | white hat | ethical (adj) | 32 | | whitelist | allowlist (n), approved list (n), approve (v) | 33 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in the 6 | Tanzu Community Engagement project and our community a harassment-free experience 7 | for everyone, regardless of age, body size, visible or invisible disability, 8 | ethnicity, sex characteristics, gender identity and expression, level of 9 | experience, education, socio-economic status, nationality, personal appearance, 10 | race, religion, or sexual identity and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the overall 26 | community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or advances of 31 | any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email address, 35 | without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | oss-coc@vmware.com. All complaints will be reviewed and investigated promptly 64 | and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series of 86 | actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or permanent 93 | ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within the 113 | community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /shoutouter/types.go: -------------------------------------------------------------------------------- 1 | // Copyright 2021 VMware Shoutouter contributors. All Rights Reserved. 2 | // SPDX-License-Identifier: Apache-2.0 3 | 4 | package main 5 | 6 | import ( 7 | "context" 8 | "fmt" 9 | "os" 10 | 11 | log "github.com/sirupsen/logrus" 12 | 13 | "github.com/google/go-github/v32/github" 14 | "golang.org/x/oauth2" 15 | "gopkg.in/yaml.v2" 16 | ) 17 | 18 | // ProjectConfig is a representation of an umbrella project to thank contributors on. 19 | // A project can span one or more repostories within one GitHub organization. 20 | // Values within a Project are strings used to query the GitHub API. 21 | type ProjectConfig struct { 22 | // Name of the project to find contributors. 23 | Name string `yaml:"name,omitempty"` 24 | // Name of the GitHub organization which the repositories are in. 25 | OrgName string `yaml:"org"` 26 | // List of Repositories that should be considered within the project. 27 | RepoNames []string `yaml:"repos,omitempty"` 28 | // List of core developer accounts names that will be excluded. Will be merged with teams. 29 | DevNames []string `yaml:"devs,omitempty"` 30 | // GitHub Teams to extract members from that will be exluded. Members will be merged with developers. 31 | TeamNames []string `yaml:"teams"` 32 | // Token is a GitHub Token that is able to read the GitHub repositories. 33 | Token string `yaml:"token"` 34 | } 35 | 36 | func NewConfigFromFile(path string) (*ProjectConfig, error) { 37 | log.Debugf("Opening file %s\n", path) 38 | bytes, err := os.ReadFile(path) 39 | if err != nil { 40 | return nil, err 41 | } 42 | 43 | var config ProjectConfig 44 | log.Debug("Parsing config from bytes") 45 | err = yaml.Unmarshal(bytes, &config) 46 | if err != nil { 47 | return nil, err 48 | } 49 | 50 | return &config, nil 51 | } 52 | 53 | var NoOrgError = fmt.Errorf("Please populate an organization") 54 | var NoTeamError = fmt.Errorf("Please specify one or more teams") 55 | var NoTokenError = fmt.Errorf("Please provide a Github API Token. You can make one with the proper permissions via this link: https://github.com/settings/tokens/new?description=shoutouts&scopes=read:org") 56 | 57 | // validateConfig makes sure the minimum fields are populated in order to query GitHub. 58 | func (c *ProjectConfig) Validate() error { 59 | if c.OrgName == "" { 60 | return NoOrgError 61 | } 62 | 63 | if len(c.TeamNames) == 0 { 64 | return NoTeamError 65 | } 66 | 67 | if c.Token == "" { 68 | return NoTokenError 69 | } 70 | 71 | return nil 72 | } 73 | 74 | type Project struct { 75 | Config *ProjectConfig 76 | // PullRequests are the merged pull requests for the project. 77 | PullRequests []*github.PullRequest 78 | // Devs are GitHub Users that will be excluded from consideration. 79 | Devs []*github.User 80 | // Teams are GitHub Teams that will be inspected for Users to exclude from consideration. 81 | Teams []*github.Team 82 | // Repos is a list of GitHub Repositories associated with the team(s) 83 | Repos []*github.Repository 84 | // Client is a GitHub client used to query the REST API 85 | client *github.Client 86 | } 87 | 88 | func NewProject(c *ProjectConfig) *Project { 89 | ctx := context.Background() 90 | ts := oauth2.StaticTokenSource( 91 | &oauth2.Token{AccessToken: c.Token}, 92 | ) 93 | tc := oauth2.NewClient(ctx, ts) 94 | 95 | return &Project{ 96 | Config: c, 97 | client: github.NewClient(tc), 98 | } 99 | } 100 | 101 | // GetPullRequests will get all pull requests across all of a project's repositories. 102 | func (p *Project) GetPullRequests() error { 103 | 104 | if len(p.Repos) == 0 { 105 | if err := p.GetReposFromTeam(); err != nil { 106 | return err 107 | } 108 | } 109 | opts := &github.PullRequestListOptions{State: "closed", 110 | ListOptions: github.ListOptions{ 111 | PerPage: 100, 112 | }, 113 | } 114 | for _, r := range p.Repos { 115 | for { 116 | prs, response, err := p.client.PullRequests.List(context.Background(), p.Config.OrgName, r.GetName(), opts) 117 | if err != nil { 118 | return err 119 | } 120 | log.Debugf("Found these closed PRs: %v", prs) 121 | p.PullRequests = append(p.PullRequests, prs...) 122 | if response.NextPage == 0 { 123 | break 124 | } 125 | opts.Page = response.NextPage 126 | } 127 | } 128 | return nil 129 | } 130 | 131 | // GetDevs will get all GitHub Users based on the configuration, as well Users from the specified Teams. 132 | func (p *Project) GetDevs() error { 133 | // devsSeen holds a list of devs we've already seen based on a team, so we don't get duplicates. 134 | var devsSeen []string 135 | 136 | // Get all the team members first 137 | teamOpts := &github.TeamListTeamMembersOptions{ 138 | ListOptions: github.ListOptions{PerPage: 100}, 139 | } 140 | for _, t := range p.Config.TeamNames { 141 | log.Debugf("Trying to get members for team %s\n", t) 142 | devs, response, err := p.client.Teams.ListTeamMembersBySlug(context.Background(), p.Config.OrgName, t, teamOpts) 143 | 144 | log.Debugf("Response: %v\n", response) 145 | if err != nil { 146 | return err 147 | } 148 | for _, d := range devs { 149 | log.Debugf("Found user: %v\n", d) 150 | p.Devs = append(p.Devs, d) 151 | devsSeen = append(devsSeen, *d.Login) 152 | } 153 | } 154 | 155 | // Get all devs, if they're not already in the list. 156 | for _, n := range p.Config.DevNames { 157 | // Skip over any devs we've already seen. 158 | for _, ds := range devsSeen { 159 | if ds == n { 160 | log.Debugf("Skipping user %s, already present", n) 161 | continue 162 | } 163 | } 164 | 165 | log.Debugf("Trying to get user %s", n) 166 | dev, response, err := p.client.Users.Get(context.Background(), n) 167 | log.Debugf("Response: %v\n", response) 168 | if err != nil { 169 | return err 170 | } 171 | p.Devs = append(p.Devs, dev) 172 | } 173 | 174 | return nil 175 | } 176 | 177 | // GetReposFromTeam will retrieve the repositories that all the teams are responsible for. 178 | func (p *Project) GetReposFromTeam() error { 179 | opts := &github.ListOptions{} 180 | for _, t := range p.Config.TeamNames { 181 | log.Debugf("Trying to get repos for team %s\n", t) 182 | repos, response, err := p.client.Teams.ListTeamReposBySlug(context.Background(), p.Config.OrgName, t, opts) 183 | log.Debugf("Response: %v\n", response) 184 | 185 | if err != nil { 186 | return err 187 | } 188 | p.Repos = append(p.Repos, repos...) 189 | } 190 | return nil 191 | } 192 | -------------------------------------------------------------------------------- /GUIDELINES.md: -------------------------------------------------------------------------------- 1 | # Guidelines: Getting started with Community Engagement for Open Source projects 2 | 3 | > **Required within the VMware Tanzu GitHub Organization** 4 | 5 | The below document complements VMware's Open Source Guidelines and provides a checklist of what is needed by each open source project to be set up for healthy community engagement. 6 | 7 | ## 1. Share Knowledge 8 | 9 | 1. The project README should be simple, focused, and mostly bullet item listed with steps to get up and running quickly. The README or landing page should include a project statement (what is does, why it’s important, and how it works), a list of features, screenshots (if a graphical UI exists), contribution guidelines, code of conduct, and links to relevant outside sources. ([EXAMPLE](https://gist.github.com/jonasrosland/8bf2e270887aa8514a19fd55335e9915)). 10 | 11 | 1. Add Code of Conduct that you receive from OSPO. 12 | 13 | 1. Have a clear “Getting started” guide, for both [users](https://velero.io/docs/v1.6/basic-install/) and [contributors](https://velero.io/docs/v1.6/start-contributing/). 14 | 15 | 1. Design and architecture documents should be made available to help users and contributors understand the underpinnings of the project ([EXAMPLE](https://github.com/vmware-tanzu/antrea/blob/main/docs/design/architecture.md)). 16 | 17 | 1. Make sure the main documentation page for the project is: 18 | 19 | 1. Up to date. 20 | 21 | 1. Works properly in all browsers and mobile devices. 22 | 23 | 1. Is easy to contribute to - using tools such as Hugo to publish documentation and similar content has worked really well. 24 | 25 | 1. Shared communication should be easy to find, for example [blogs](https://octant.dev/blog/), [recorded meetings](https://www.youtube.com/playlist?list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM), [meeting notes](https://hackmd.io/Jq6F5zqZR7S80CeDWUklkA?view), and [presentations](https://velero.io/resources/). 26 | 27 | 1. Have an initial blog post that states the vision, why the project was created versus contributing to an existing project, and gives a commitment to the community ([EXAMPLE](https://tanzu.vmware.com/content/blog/seeing-is-believing-octant-reveals-the-objects-running-in-kubernetes-clusters)). 28 | 29 | ## 2. Collaborate 30 | 31 | 1. Development solely done in public and upstream. 32 | 33 | 1. Use public tools for issue tracking and planning such as GitHub Projects and Zenhub Boards. 34 | 35 | 1. Ensure that each open source project has a Slack presence - make sure you are where your contributors are. 36 | 37 | 1. In the repositories, there needs to be an MAINTAINERS file that lists all maintainers of the project, and potential stakeholders ([EXAMPLE](https://github.com/goharbor/community/blob/master/MAINTAINERS.md)). 38 | 39 | 1. Document who owns key roles in each project, and include that in MAINTAINERS ([EXAMPLE 1](https://github.com/vmware-tanzu/velero/blob/main/MAINTAINERS.md) and [EXAMPLE 2](https://github.com/goharbor/community/blob/master/MAINTAINERS.md)), or have them listed on the project landing page ([EXAMPLE](https://carvel.dev/)). 40 | 41 | 1. Create sample issue templates to ensure predictable triaging of bugs, features and support issues ([EXAMPLE 1](https://github.com/vmware-tanzu/sonobuoy/blob/master/.github/ISSUE_TEMPLATE/bug_report.md) and [EXAMPLE 2](https://github.com/vmware-tanzu/velero/blob/master/.github/ISSUE_TEMPLATE/feature-enhancement-request.md)). 42 | 43 | 1. Be a good open source citizen - “wear your agenda on your sleeve”. If you are clear about that then folks will be able to predict what you are looking for, and it is much easier to get to a "win-win" solution. 44 | 45 | 1. As the project grows, include a GOVERNANCE directive with leadership defined, community engagement, maintainers, expected maturity or growth patterns, and commitment or non-commitment to open governance, and architecture decisions. 46 | 47 | 1. Have a clearly defined path for a contributor to become a reviewer, and ultimately a maintainer ([EXAMPLE](https://github.com/vmware-tanzu/antrea/blob/main/GOVERNANCE.md#maintainers)). 48 | 49 | 1. Have a common style guide to use for documentation ([EXAMPLE](https://github.com/vmware-tanzu/velero/blob/main/site/content/docs/v1.5/style-guide.md)). 50 | 51 | 1. Have comprehensive end-to-end and unit testing using public CI/CD systems such as CircleCI or GitHub Actions. 52 | 53 | 1. Use inclusive terminology throughout your project and docs. For example, the default branch in Github should be `main` instead of `master`. Refer to the inclusive terminology list for more examples. 54 | 55 | ## 3. Build and Increase our credibility 56 | 57 | 1. Deliver on features that are set in the roadmap - stay focused. 58 | 59 | 1. Contribute to related open source projects, tying yourself and your project to another part of the open source ecosystem - don’t work in a bubble. 60 | 61 | 1. Be public and be seen, by writing blog posts, speaking at events, hosting open community calls, engaging with the community on Slack, being a part of podcasts, or hosting IRL Community Meetings. 62 | 63 | ## 4. Engage with users and contributors 64 | 65 | 1. When getting users who want to publicly state that they are using your project, utilize an ADOPTERS file ([EXAMPLE](https://github.com/vmware-tanzu/velero/blob/main/ADOPTERS.md)). 66 | 67 | 1. Be engaged and open in your project Slack channel, keep project discussions as much as possible in there and not in the internal VMware Slack. 68 | 69 | 1. Don’t immediately jump on fixing the small and easy things - create and use the “good first issue” and “help wanted” tags to give new contributors an easy way into the project. 70 | 71 | 1. Hold regular community meetings through Zoom, explaining finished work, what’s currently on deck, and roadmap items that should be discussed with the community - we’ve had success with running these weekly instead of monthly. 72 | 73 | 1. Be cognizant of time zones, not everyone is online when you are - make sure the work you do supports an asynchronous community. 74 | 75 | 1. Establish a Twitter profile ([EXAMPLE](https://twitter.com/projectvelero)) or Twitter outlet for each open source project - this could be a separate account, or amplified messaging through @vmwopensource and others. 76 | 77 | 1. Submit CFPs and be active at relevant conferences, events, and meetups - there is more we can do than just be speakers, for example lead live community meetings, workshops, and code jams at these events. 78 | 79 | ## 5. Evolve perception of VMware 80 | 81 | 1. Ensure a complementary presence in existing communities such as Kubernetes Special Interest Groups (SIGs) and Working Groups (WG). 82 | 83 | 1. Ensure that blogs, CFPs and tweets are community first, not VMware first. 84 | -------------------------------------------------------------------------------- /HEALTHCHECKS.md: -------------------------------------------------------------------------------- 1 | # Open Source Project Health Checks 2 | 3 | This page describes the VMware Tanzu Community Engagement team’s open source project health check process. Building on the team’s commitment to developing thriving communities, we’ve created this process to work with project teams to understand what a healthy project looks like, give feedback on how to improve health, and track project health over time. 4 | 5 | Our approach is to focus on measuring and reporting metrics for open source projects we are heavily invested in. We want to steer clear of vanity metrics, and focus on actionable items that project teams can use to improve the project’s overall health and public image. Metrics include tracking things like documentation quality, maintainer attentiveness, and community involvement in the project. 6 | 7 | ## Goals of the health checks: 8 | 9 | - Provide guidelines for project teams around what makes a healthy open source community experience 10 | - Highlight areas where improvements can be made 11 | - Spark discussions, collaboration, and new ideas to make a better community experience for everyone 12 | - Continuous evaluation of projects as they develop within the ecosystem, allowing teams the opportunity to hear about new guidelines and adjust on-going processes 13 | - Catch and make corrections for slow-downs or lapses as the projects progress 14 | 15 | ## Non-goals of health checks: 16 | 17 | - Providing “we’re done” metrics - open source community engagements are never “done” 18 | - Implement a pass/fail rating system for projects 19 | - Create single “cookie-cutter” path for every project 20 | 21 | ## Health check metrics 22 | 23 | Open source projects with assigned community managers will be assessed with "Shoot for the Stars" measurements: 24 | 25 | - Project Maturity 26 | - Following the guidelines outlined in our [Guidelines](GUIDELINES.md) 27 | - Following CII best practices 28 | - The [CII Best Practices Badge Program](https://bestpractices.coreinfrastructure.org/en) provides maturity self-certification: passing, silver, and gold. 29 | - Release velocity 30 | - Time between releases. Regular releases are a reliability indicator. 31 | - Roadmap 32 | - Existence and quality of roadmap. 33 | 34 | - Project Viability 35 | - Documentation 36 | - What is the thoroughness, and accessibility of documentation according to a set of criteria? 37 | - Low elephant factor - when applicable 38 | - Related to the [bus/lottery](https://en.wikipedia.org/wiki/Bus_factor) factor, but measured at a corporation level. How viable would the project be if the largest organization pulled out its contributors? We use this measurement for multi-vendor projects such as CNCF project. 39 | 40 | - Growth of Community 41 | - Role definitions 42 | - Existence and quality of role definitions 43 | - Path to Maintainership 44 | - Published path to maintainership. How can someone go from user, to contributor, to maintainer. 45 | - Continually onboarding new contributors 46 | - How many casual/regular contributors are we onboarding/retaining? 47 | - Distribution of Work 48 | - How much of a project’s recent activity was distributed between community members (all maintainer driven, split, all community driven)? 49 | - Decision distribution 50 | - Central vs. distributed decision making. Shows scalability of community. 51 | - Communication channels are in place and used effectively 52 | - Slack, distribution lists, GitHub issues & PRs, community meetings, public meeting notes, recorded videos 53 | 54 | - Diversity of Community 55 | - Number of contributors 56 | - Having a stable number of contributors over time. 57 | - Contributing organizations 58 | - Having a stable number of organizations contributing over time. 59 | - Non-code contributions 60 | - Track contributions like running tests in test environments, writing blog posts, producing videos, and giving talks. 61 | - Contributor breadth 62 | - Ratio of non-core committers (regular and casual committers). 63 | 64 | - Attentiveness of Maintainers 65 | - Recognition of contributors 66 | - Shout-outs, recognition, and mentions in pull-requests or change logs. 67 | - Retrospectives 68 | - Existence of a retrospective meeting after a release. Collect lessons learned, improve processes, recognize contributors. 69 | - Release Note Completeness 70 | - Functionality changes and bug fixes should be represented in release notes. Good for users, and shows diligence of the community. 71 | - Transparency 72 | - Decisions are made public and communicated where appropriate. Discussion is occurring openly as much as possible. 73 | 74 | - User Community Engagement 75 | - User documentation (visible and being updated) 76 | - Communications channel for user questions are used actively by both users and maintainers 77 | - Obvious process for bug reports and feature requests 78 | - Meetings for user engagement, office hours, best practices 79 | 80 | ## Health check measurement scale 81 | 82 | In general each metric should be reported using the following guidelines: 83 | 84 | - Working well (Green) 85 | - The team and community are progressing or engaging at a good level. There is no immediate need to make improvements. 86 | 87 | - Some pieces are missing (Yellow) 88 | - There is still some work to be done to implement guidelines or recommended practices. This should be addressed when there is time. 89 | 90 | - Needs attention (Red) 91 | - Large pieces of process, content, or community interaction are missing. The project team should take steps to improve as soon as possible. 92 | 93 | ## How to perform a health check 94 | 95 | The Community Engagement team performs health checks every 6 months on projects with dedicated community managers. 96 | 97 | We have an [example sheet](HEALTHCHECK-SHEET.md) available that you can use to track your project's measurements. 98 | 99 | 1. Review each metric and update the Status field according to the current state of the project. 100 | 1. Research the current state of the project by 101 | 1. Reviewing the previous Advice and Comments to see if progress has been made 102 | 1. Talking to the project engineering leads 103 | 1. Any metric graded below **Working Well** should have **Advice or Notes** filled in with your reasoning. 104 | 1. Once you have reviewed each metric, schedule a meeting with the engineering leads of the project to go over your findings. 105 | 1. Create a presentation of your findings 106 | 1. This presentation should capture the key takeaways and potential action items from your evaluation of the project and discussions with project lead(s). 107 | 1. Schedule time to present to the entire open source project team. This presentation is meant to share your findings of the current project health, and also be an open discussion with the project team. The team should agree on any action items and how to take the next steps to improve the health for the next review. 108 | 1. Continously review action items until the next review cycle 109 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Release Process 2 | 3 | 4 | 5 | The community has adopted this security disclosure and response policy to ensure we responsibly handle critical issues. 6 | 7 | 8 | ## Supported Versions 9 | 10 | 11 | 12 | 13 | ## Reporting a Vulnerability - Private Disclosure Process 14 | 15 | Security is of the highest importance and all security vulnerabilities or suspected security vulnerabilities should be reported to privately, to minimize attacks against current users of before they are fixed. Vulnerabilities will be investigated and patched on the next patch (or minor) release as soon as possible. This information could be kept entirely internal to the project. 16 | 17 | If you know of a publicly disclosed security vulnerability for , please **IMMEDIATELY** contact the VMware Security Team (security@vmware.com). The use of encrypted email is encouraged. The public PGP key can be found at https://kb.vmware.com/kb/1055. 18 | 19 | 20 | 21 | **IMPORTANT: Do not file public issues on GitHub for security vulnerabilities** 22 | 23 | To report a vulnerability or a security-related issue, please contact the VMware email address with the details of the vulnerability. The email will be fielded by the VMware Security Team and then shared with the maintainers who have committer and release permissions. Emails will be addressed within 3 business days, including a detailed plan to investigate the issue and any potential workarounds to perform in the meantime. Do not report non-security-impacting bugs through this channel. Use [GitHub issues]() instead. 24 | 25 | 26 | ## Proposed Email Content 27 | 28 | Provide a descriptive subject line and in the body of the email include the following information: 29 | 30 | 31 | 32 | * Basic identity information, such as your name and your affiliation or company. 33 | * Detailed steps to reproduce the vulnerability (POC scripts, screenshots, and logs are all helpful to us). 34 | * Description of the effects of the vulnerability on and the related hardware and software configurations, so that the VMware Security Team can reproduce it. 35 | * How the vulnerability affects usage and an estimation of the attack surface, if there is one. 36 | * List other projects or dependencies that were used in conjunction with to produce the vulnerability. 37 | 38 | 39 | 40 | 41 | ## When to report a vulnerability 42 | 43 | 44 | 45 | * When you think has a potential security vulnerability. 46 | * When you suspect a potential vulnerability but you are unsure that it impacts . 47 | * When you know of or suspect a potential vulnerability on another project that is used by . 48 | 49 | 50 | 51 | 52 | ## Patch, Release, and Disclosure 53 | 54 | The VMware Security Team will respond to vulnerability reports as follows: 55 | 56 | 57 | 58 | 59 | 60 | 1. The Security Team will investigate the vulnerability and determine its effects and criticality. 61 | 2. If the issue is not deemed to be a vulnerability, the Security Team will follow up with a detailed reason for rejection. 62 | 3. The Security Team will initiate a conversation with the reporter within 3 business days. 63 | 4. If a vulnerability is acknowledged and the timeline for a fix is determined, the Security Team will work on a plan to communicate with the appropriate community, including identifying mitigating steps that affected users can take to protect themselves until the fix is rolled out. 64 | 5. The Security Team will also create a [CVSS](https://www.first.org/cvss/specification-document) using the [CVSS Calculator](https://www.first.org/cvss/calculator/3.0). The Security Team makes the final call on the calculated CVSS; it is better to move quickly than making the CVSS perfect. Issues may also be reported to [Mitre](https://cve.mitre.org/) using this [scoring calculator](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator). The CVE will initially be set to private. 65 | 6. The Security Team will work on fixing the vulnerability and perform internal testing before preparing to roll out the fix. 66 | 7. The Security Team will provide early disclosure of the vulnerability by emailing the [ Distributors]() mailing list. Distributors can initially plan for the vulnerability patch ahead of the fix, and later can test the fix and provide feedback to the team. See the section **Early Disclosure to Distributors List** for details about how to join this mailing list. 67 | 8. A public disclosure date is negotiated by the VMware SecurityTeam, the bug submitter, and the distributors list. We prefer to fully disclose the bug as soon as possible once a user mitigation or patch is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for distributor coordination. The timeframe for disclosure is from immediate (especially if it’s already publicly known) to a few weeks. For a critical vulnerability with a straightforward mitigation, we expect the report date for the public disclosure date to be on the order of 14 business days. The VMware Security Team holds the final say when setting a public disclosure date. 68 | 9. Once the fix is confirmed, the Security Team will patch the vulnerability in the next patch or minor release, and backport a patch release into all earlier supported releases. Upon release of the patched version of , we will follow the **Public Disclosure Process**. 69 | 70 | 71 | ## Public Disclosure Process 72 | 73 | The Security Team publishes a [public advisory]() to the community via GitHub. In most cases, additional communication via Slack, Twitter, mailing lists, blog and other channels will assist in educating users and rolling out the patched release to affected users. 74 | 75 | The Security Team will also publish any mitigating steps users can take until the fix can be applied to their instances. distributors will handle creating and publishing their own security advisories. 76 | 77 | 78 | 79 | 80 | ## Mailing lists 81 | 82 | 83 | 84 | * Use security@vmware.com to report security concerns to the VMware Security Team, who uses the list to privately discuss security issues and fixes prior to disclosure. 85 | * Join the [ Distributors]() mailing list for early private information and vulnerability disclosure. Early disclosure may include mitigating steps and additional information on security patch releases. See below for information on how distributors or vendors can apply to join this list. 86 | 87 | 88 | ## Early Disclosure to Distributors List 89 | 90 | The private list is intended to be used primarily to provide actionable information to multiple distributor projects at once. This list is not intended to inform individuals about security issues. 91 | 92 | 93 | ## Membership Criteria 94 | 95 | To be eligible to join the [ Distributors]() mailing list, you should: 96 | 97 | 98 | 99 | 1. Be an active distributor of . 100 | 2. Have a user base that is not limited to your own organization. 101 | 3. Have a publicly verifiable track record up to the present day of fixing security issues. 102 | 4. Not be a downstream or rebuild of another distributor. 103 | 5. Be a participant and active contributor in the community. 104 | 6. Accept the Embargo Policy that is outlined below. 105 | 7. Have someone who is already on the list vouch for the person requesting membership on behalf of your distribution. 106 | 107 | **The terms and conditions of the Embargo Policy apply to all members of this mailing list. A request for membership represents your acceptance to the terms and conditions of the Embargo Policy.** 108 | 109 | 110 | ## Embargo Policy 111 | 112 | The information that members receive on the Distributors mailing list must not be made public, shared, or even hinted at anywhere beyond those who need to know within your specific team, unless you receive explicit approval to do so from the VMware Security Team. This remains true until the public disclosure date/time agreed upon by the list. Members of the list and others cannot use the information for any reason other than to get the issue fixed for your respective distribution's users. 113 | 114 | Before you share any information from the list with members of your team who are required to fix the issue, these team members must agree to the same terms, and only be provided with information on a need-to-know basis. 115 | 116 | In the unfortunate event that you share information beyond what is permitted by this policy, you must urgently inform the VMware Security Team (security@vmware.com) of exactly what information was leaked and to whom. If you continue to leak information and break the policy outlined here, you will be permanently removed from the list. 117 | 118 | 119 | 120 | 121 | ## Requesting to Join 122 | 123 | Send new membership requests to . In the body of your request please specify how you qualify for membership and fulfill each criterion listed in the Membership Criteria section above. 124 | 125 | 126 | ## Confidentiality, integrity and availability 127 | 128 | We consider vulnerabilities leading to the compromise of data confidentiality, elevation of privilege, or integrity to be our highest priority concerns. Availability, in particular in areas relating to DoS and resource exhaustion, is also a serious security concern. The VMware Security Team takes all vulnerabilities, potential vulnerabilities, and suspected vulnerabilities seriously and will investigate them in an urgent and expeditious manner. 129 | 130 | Note that we do not currently consider the default settings for to be secure-by-default. It is necessary for operators to explicitly configure settings, role based access control, and other resource related features in to provide a hardened environment. We will not act on any security disclosure that relates to a lack of safe defaults. Over time, we will work towards improved safe-by-default configuration, taking into account backwards compatibility. 131 | -------------------------------------------------------------------------------- /shoutouter/LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | -------------------------------------------------------------------------------- /LICENSE.txt: -------------------------------------------------------------------------------- 1 | community-engagement 2 | 3 | Copyright 2020 VMware, Inc. 4 | 5 | The CC-BY-SA-4.0 license (the "License") set forth below applies to all parts of the tanzu-community-engagement project. You may not use this file except in compliance with the License. 6 | 7 | 8 | Creative Commons Attribution Share Alike 4.0 International License 9 | 10 | Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible. 11 | 12 | Using Creative Commons Public Licenses 13 | 14 | Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses. 15 | 16 | Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors : wiki.creativecommons.org/Considerations_for_licensors 17 | 18 | Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor's permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. 19 | 20 | Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public : wiki.creativecommons.org/Considerations_for_licensees 21 | 22 | 23 | Creative Commons Attribution-ShareAlike 4.0 International Public License 24 | 25 | By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. 26 | 27 | Section 1 – Definitions. 28 | 29 | Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. 30 | Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. 31 | BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License. 32 | Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. 33 | Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. 34 | Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. 35 | License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike. 36 | Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License. 37 | Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. 38 | Licensor means the individual(s) or entity(ies) granting rights under this Public License. 39 | Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. 40 | Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. 41 | You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. 42 | 43 | Section 2 – Scope. 44 | 45 | License grant. 46 | Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: 47 | reproduce and Share the Licensed Material, in whole or in part; and 48 | produce, reproduce, and Share Adapted Material. 49 | Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. 50 | Term. The term of this Public License is specified in Section 6(a). 51 | Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material. 52 | Downstream recipients. 53 | Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. 54 | Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply. 55 | No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. 56 | No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). 57 | 58 | Other rights. 59 | Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. 60 | Patent and trademark rights are not licensed under this Public License. 61 | To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties. 62 | 63 | Section 3 – License Conditions. 64 | 65 | Your exercise of the Licensed Rights is expressly made subject to the following conditions. 66 | 67 | Attribution. 68 | 69 | If You Share the Licensed Material (including in modified form), You must: 70 | retain the following if it is supplied by the Licensor with the Licensed Material: 71 | identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); 72 | a copyright notice; 73 | a notice that refers to this Public License; 74 | a notice that refers to the disclaimer of warranties; 75 | a URI or hyperlink to the Licensed Material to the extent reasonably practicable; 76 | indicate if You modified the Licensed Material and retain an indication of any previous modifications; and 77 | indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. 78 | You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. 79 | If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. 80 | ShareAlike. 81 | 82 | In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply. 83 | The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License. 84 | You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material. 85 | You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply. 86 | 87 | Section 4 – Sui Generis Database Rights. 88 | 89 | Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: 90 | 91 | for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database; 92 | if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and 93 | You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. 94 | 95 | For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. 96 | 97 | Section 5 – Disclaimer of Warranties and Limitation of Liability. 98 | 99 | Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You. 100 | To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You. 101 | 102 | The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. 103 | 104 | Section 6 – Term and Termination. 105 | 106 | This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. 107 | 108 | Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: 109 | automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or 110 | upon express reinstatement by the Licensor. 111 | For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. 112 | For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. 113 | Sections 1, 5, 6, 7, and 8 survive termination of this Public License. 114 | 115 | Section 7 – Other Terms and Conditions. 116 | 117 | The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. 118 | Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. 119 | 120 | Section 8 – Interpretation. 121 | 122 | For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. 123 | To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. 124 | No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. 125 | Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. 126 | 127 | 128 | 129 | 130 | 131 | --------------------------------------------------------------------------------