├── .gitignore ├── documents ├── nats │ ├── README.md │ ├── Proposal to exit NATS from CNCF.pdf │ ├── NATS.io Maintainer Minutes - March 2025.pdf │ ├── Cease and Demand Letter from Synadia Counsel.pdf │ ├── Petition for cancellation NATS IO Reg No 6216925 final.pdf │ └── Petition for cancellation NATS stylized Reg No 6216924 final.pdf ├── 2021 CNCF Strategy.pdf ├── 2022 CNCF Strategy.pdf ├── 2023 CNCF Strategy.pdf ├── 2024 CNCF Strategy.pdf ├── project-newsletter │ ├── share_7138959161444758122.png │ ├── 2023 -01-24- ProjectNewsletter.md │ ├── 2023-04-26-ProjectNewsletter.md │ ├── 2023-06-23-ProjectNewsletter.md │ ├── 2023-11-23- Project Newsletter.md │ ├── 2023-09-20-ProjectNewsletter.md │ ├── 2023-07-20-ProjectNewsletter.md │ ├── 2023-05-24-ProjectNewsletter.md │ ├── 2023-02-22-ProjectNewsletter.md │ └── 2024-01-26- Project Newsletter.md ├── README.md └── creative_brief_template.md ├── cncf-membership-agreement.pdf ├── policies-guidance ├── media │ └── slack-backup │ │ ├── export.png │ │ ├── login.jpeg │ │ ├── channelid.jpg │ │ ├── channelid2.jpg │ │ ├── getcookie.jpeg │ │ ├── runwizard.jpeg │ │ ├── channelid3.jpeg │ │ ├── channelid4.jpeg │ │ ├── cookielogin.jpeg │ │ ├── exportdata1.jpeg │ │ ├── exportdata2.jpeg │ │ └── createcredential.jpeg ├── dco-guidelines.md ├── slack-guidelines.md ├── sandbox-pr-guidelines.md ├── website-guidelines.md ├── allowed-third-party-license-policy.md ├── agpl-recommendations.md ├── maintainers-election-policy.md ├── case-study-guidelines.md ├── online-programs-guidelines.md └── social-guidelines.md ├── agreements ├── Sample Contribution Agreement (2025).pdf ├── deprecated │ ├── CNCF Trademark and Account Assignment Agreement (2020 - reg trademarks).pdf │ └── CNCF Trademark and Account Assignment Agreement (2020 - no reg trademarks).pdf └── README.md ├── .github ├── workflows │ └── validate-csv.yml └── pull_request_template.md ├── license-exceptions ├── cncf-exceptions-2021-07-19.spdx ├── cncf-exceptions-2023-08-31.json ├── cncf-exceptions-2021-07-19.json ├── cncf-exceptions-2023-08-31.spdx ├── README.md ├── cncf-exceptions-2022-04-12.spdx ├── cncf-exceptions-2023-06-27.json └── cncf-exceptions-2023-06-27.spdx ├── do-insurance.md ├── README.md ├── KubeWeekly.md ├── travel_funding.md ├── code-of-conduct-languages ├── zh.md ├── ro.md ├── ja.md ├── ko.md ├── he.md ├── ar.md ├── fa.md ├── cs.md ├── bn.md ├── vi.md ├── hi.md ├── id.md ├── hu.md ├── uk.md └── tr.md ├── cncf-marketing-committee-chair.md ├── style-guide.md ├── journey-reports.md ├── cncfgroups.md ├── copyright-notices.md ├── legal-committee-charter.md └── license-notices.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store -------------------------------------------------------------------------------- /documents/nats/README.md: -------------------------------------------------------------------------------- 1 | # Documents related to NATS 2 | -------------------------------------------------------------------------------- /cncf-membership-agreement.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/cncf-membership-agreement.pdf -------------------------------------------------------------------------------- /documents/2021 CNCF Strategy.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/2021 CNCF Strategy.pdf -------------------------------------------------------------------------------- /documents/2022 CNCF Strategy.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/2022 CNCF Strategy.pdf -------------------------------------------------------------------------------- /documents/2023 CNCF Strategy.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/2023 CNCF Strategy.pdf -------------------------------------------------------------------------------- /documents/2024 CNCF Strategy.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/2024 CNCF Strategy.pdf -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/export.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/export.png -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/login.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/login.jpeg -------------------------------------------------------------------------------- /agreements/Sample Contribution Agreement (2025).pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/agreements/Sample Contribution Agreement (2025).pdf -------------------------------------------------------------------------------- /documents/nats/Proposal to exit NATS from CNCF.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/nats/Proposal to exit NATS from CNCF.pdf -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/channelid.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/channelid.jpg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/channelid2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/channelid2.jpg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/getcookie.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/getcookie.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/runwizard.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/runwizard.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/channelid3.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/channelid3.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/channelid4.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/channelid4.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/cookielogin.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/cookielogin.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/exportdata1.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/exportdata1.jpeg -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/exportdata2.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/exportdata2.jpeg -------------------------------------------------------------------------------- /documents/nats/NATS.io Maintainer Minutes - March 2025.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/nats/NATS.io Maintainer Minutes - March 2025.pdf -------------------------------------------------------------------------------- /documents/project-newsletter/share_7138959161444758122.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/project-newsletter/share_7138959161444758122.png -------------------------------------------------------------------------------- /policies-guidance/media/slack-backup/createcredential.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/policies-guidance/media/slack-backup/createcredential.jpeg -------------------------------------------------------------------------------- /documents/nats/Cease and Demand Letter from Synadia Counsel.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/nats/Cease and Demand Letter from Synadia Counsel.pdf -------------------------------------------------------------------------------- /documents/nats/Petition for cancellation NATS IO Reg No 6216925 final.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/nats/Petition for cancellation NATS IO Reg No 6216925 final.pdf -------------------------------------------------------------------------------- /documents/README.md: -------------------------------------------------------------------------------- 1 | # CNCF Project Support Documents 2 | 3 | ### Creative Brief 4 | For projects applying for assistance from design. 5 | 6 | 7 | [Creative Brief Template](creative_brief_template.rtf) 8 | -------------------------------------------------------------------------------- /documents/nats/Petition for cancellation NATS stylized Reg No 6216924 final.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/documents/nats/Petition for cancellation NATS stylized Reg No 6216924 final.pdf -------------------------------------------------------------------------------- /agreements/deprecated/CNCF Trademark and Account Assignment Agreement (2020 - reg trademarks).pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/agreements/deprecated/CNCF Trademark and Account Assignment Agreement (2020 - reg trademarks).pdf -------------------------------------------------------------------------------- /agreements/deprecated/CNCF Trademark and Account Assignment Agreement (2020 - no reg trademarks).pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cncf/foundation/HEAD/agreements/deprecated/CNCF Trademark and Account Assignment Agreement (2020 - no reg trademarks).pdf -------------------------------------------------------------------------------- /.github/workflows/validate-csv.yml: -------------------------------------------------------------------------------- 1 | name: CSV Formatting Validation 2 | 3 | on: 4 | pull_request: 5 | paths: 6 | - "project-maintainers.csv" 7 | 8 | jobs: 9 | validate-csv: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: actions/checkout@v4 13 | - name: Validate CSV 14 | uses: krook/csv-lint@main 15 | env: 16 | CSV_FILE: "project-maintainers.csv" 17 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | # Checklist for maintainer updates 2 | 3 | > [!NOTE] 4 | > **Delete this template if you're not changing the CSV file** 5 | 6 | - [ ] You've provided a link to documentation where the project has approved the maintainer changes. 7 | - [ ] The maintainer(s) also created or updated their [LFX Individual Dashboard profile](https://openprofile.dev/). 8 | - [ ] You've sent an email with the list of email address(es) to for invitations to Service Desk and mailing lists. You can just mark this complete if you are only removing people. 9 | - [ ] Optional: You've also sent a PR with affiliation updates to [cncf/gitdm](https://github.com/cncf/gitdm?tab=readme-ov-file#cncf-gitdm). 10 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2021-07-19.spdx: -------------------------------------------------------------------------------- 1 | SPDXVersion: SPDX-2.1 2 | DataLicense: CC0-1.0 3 | SPDXID: SPDXRef-DOCUMENT 4 | DocumentName: cncf-exceptions-2011-07-19 5 | DocumentNamespace: https://github.com/cncf/foundation/license-exceptions-2021-07-19 6 | Creator: Organization: CNCF 7 | Creator: Tool: cncf-exceptions-maker-0.1 8 | Created: 2023-05-26 9 | 10 | ##### Package: go-retryablehttp 11 | 12 | PackageName: go-retryablehttp 13 | SPDXID: SPDXRef-Package2 14 | PackageDownloadLocation: NOASSERTION 15 | FilesAnalyzed: false 16 | PackageLicenseConcluded: MPL-2.0 17 | PackageLicenseDeclared: NOASSERTION 18 | PackageCopyrightText: NOASSERTION 19 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2021-07-19 -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2023-08-31.json: -------------------------------------------------------------------------------- 1 | [ 2 | { 3 | "package": "github.com/docker/go-metrics", 4 | "license": "CC-BY-SA 4.0", 5 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31" 6 | }, 7 | { 8 | "package": "github.com/hashicorp/go-memdb", 9 | "license": "MPL-2.0 ", 10 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31" 11 | }, 12 | { 13 | "package": "github.com/shoenig/go-m1cpu", 14 | "license": "MPL-2.0 ", 15 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31" 16 | }, 17 | { 18 | "package": "hashicorp/packer-plugin-sdk", 19 | "license": "MPL-2.0 ", 20 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31" 21 | } 22 | ] -------------------------------------------------------------------------------- /agreements/README.md: -------------------------------------------------------------------------------- 1 | # CNCF Trademark and Account Assignment Agreements 2 | 3 | This folder contains the [deprecated trademark agreements](https://github.com/cncf/foundation/tree/main/agreements/deprecated) that CNCF projects used to transfer trademarks to the Linux Foundation. 4 | 5 | Projects will now complete a "[Contribution Agreement](https://github.com/cncf/foundation/tree/main/agreements/Sample%20Contribution%20Agreement%20(2025).pdf)" that is generated as a Google document for them. This will then be executed via Docusign by the contributors and the LF. 6 | 7 | The new process follows the [CNCF Governing Board's approval](https://www.cncf.io/wp-content/uploads/2024/10/2024-Oct-09-GB-Voting-Results.pdf) of a [resolution](https://docs.google.com/document/d/1jeSSq8LvpRaw_6GWNeGjVEV0n9WoCJ-x3oTiUyJWYSk/edit?tab=t.0#heading=h.3sfarlt0uip7) that establishes a [new Series LLC model for projects](https://docs.google.com/document/d/1ddxjFfABSiubJ9by9P3p9lszNSMetonJGFtV-NEb_Pc/edit?tab=t.0#heading=h.so0m36vqkre0). 8 | 9 | [Additional context](https://github.com/cncf/foundation/issues/910). 10 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2021-07-19.json: -------------------------------------------------------------------------------- 1 | { 2 | "SPDXID" : "SPDXRef-DOCUMENT", 3 | "spdxVersion" : "SPDX-2.1", 4 | "creationInfo" : { 5 | "created" : "2023-05-26T13:11:55Z", 6 | "creators" : [ "Organization: CNCF", "Tool: cncf-exceptions-maker-0.1" ] 7 | }, 8 | "name" : "cncf-exceptions-2011-07-19", 9 | "dataLicense" : "CC0-1.0", 10 | "documentNamespace" : "https://github.com/cncf/foundation/license-exceptions-2021-07-19", 11 | "packages" : [ { 12 | "SPDXID" : "SPDXRef-Package2", 13 | "comment" : "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2021-07-19", 14 | "copyrightText" : "NOASSERTION", 15 | "downloadLocation" : "NOASSERTION", 16 | "filesAnalyzed" : false, 17 | "licenseConcluded" : "MPL-2.0", 18 | "licenseDeclared" : "NOASSERTION", 19 | "name" : "go-retryablehttp" 20 | } ], 21 | "relationships" : [ { 22 | "spdxElementId" : "SPDXRef-DOCUMENT", 23 | "relationshipType" : "DESCRIBES", 24 | "relatedSpdxElement" : "SPDXRef-Package2", 25 | "comment" : "This describes relationship was added as a default relationship by the SPDX Tools Tag parser." 26 | } ] 27 | } -------------------------------------------------------------------------------- /do-insurance.md: -------------------------------------------------------------------------------- 1 | # Directors and Officers (D&O) Insurance 2 | 3 | The Linux Foundation maintains a comprehensive umbrella of insurance policies to protect its communities' interests. This insurance covers the projects themselves, any employees of the organization and extends to volunteers who are working with LF projects. For those contributors who work on LF projects on behalf of member companies, those companies' own insurance policies also provide coverage and would most likely be the primary source of protection for those contributors. 4 | 5 | More importantly than insurance coverage levels, the Linux Foundation works every day to reduce risks that would ever lead to needing insurance at all. LF's in-house legal team works with some of the foremost intellectual property / trademark / export control lawyers in the world to ensure that LF projects and communities are established and organized with specific frameworks and are operated in specific manners that protect the communities from legal exposure. In addition to regularly updated guidelines regarding best practices that projects should abide by (https://www.linuxfoundation.org/resources/publications/ and https://www.linuxfoundation.org/resources/open-source-guides/), the LF legal team is available to support its projects if more specific guidance if needed. 6 | -------------------------------------------------------------------------------- /policies-guidance/dco-guidelines.md: -------------------------------------------------------------------------------- 1 | # DCO Guidelines v1.0 2 | 3 | The DCO is a representation by someone stating they have the right to contribute the code they have proposed for acceptance into a project: https://developercertificate.org 4 | 5 | That representation is important for legal purposes and was the community-developed outcome after a $1 billion [lawsuit](https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_disputes) by SCO against IBM. The representation is designed to prevent issues but also keep the burden on contributors low. It has proven very adaptable to other projects, is built into git itself (and now also GitHub), and is in use by thousands of projects to avoid more burdensome requirements to contribute (such as a CLA). 6 | 7 | ## DCO and Real Names 8 | 9 | The DCO requires the use of a real name that can be used to identify someone in case there is an issue about a contribution they made. 10 | 11 | **A real name does not require a legal name, nor a birth name, nor any name that appears on an official ID (e.g. a passport). Your real name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution.** 12 | 13 | Your real name should not be an anonymous id or false name that misrepresents who you are. 14 | 15 | ## Reference Issue 16 | 17 | https://github.com/cncf/foundation/issues/383 18 | -------------------------------------------------------------------------------- /documents/creative_brief_template.md: -------------------------------------------------------------------------------- 1 | # Creative Brief - [PROJECT NAME] 2 | 3 | ## Purpose / Background 4 | 5 | ## Target Date 6 | 7 | ## Target Audience 8 | 9 | ## Primary Stakeholders 10 | 11 | * 12 | * 13 | * 14 | 15 | ## Perception (Is there any internal insight you can provide that may impact design) 16 | 17 | 18 | ## Magnetic Idea 19 | 20 | (What do you want to communicate with this brand) 21 | 22 | * 23 | 24 | ## Terminology Associated with this Brand Includes: 25 | 26 | (If possible, please use descriptive terms that can be used by the creative team to design visual elements) 27 | 28 | * 29 | * 30 | * 31 | 32 | ## Competition: (Please list any competitors and/or potential members whose branding we should be aware of) 33 | 34 | * 35 | * 36 | * 37 | 38 | ## Design Suggestions 39 | 40 | (Please list any design direction that can be leveraged to create the initial concepts. I.e. Preferred color palette(s), whether the logo should be text-only or if it should also include an icon or mascot, should it be horizontal or stacked (or both), is there any information that we need to be aware of that will influence the design.) 41 | 42 | ## Creative Considerations & Distribution 43 | 44 | The creative elements need to be flexible. The logo needs to be visible in single and multiple colors and scale so that it works at very small sizes. It will also be reproduced for printing, silkscreen, embroidery, and web. 45 | 46 | ## Primary Deliverables 47 | 48 | * Print-Ready Logo Artwork Files: SVG 49 | * Screen-Optimized Logo Artwork Files: PNG 50 | 51 | ## Additional Deliverables 52 | 53 | * Logo Usage Guidelines: PDF 54 | * PowerPoint Template: PPTX 55 | * Any Font Licenses and Files Needed 56 | -------------------------------------------------------------------------------- /policies-guidance/slack-guidelines.md: -------------------------------------------------------------------------------- 1 | # Cloud Native Computing Foundation Slack Guidelines v1.0 2 | 3 | The [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md) applies in all areas in addition to these rules: 4 | 5 | ## Channel Spamming 6 | 7 | Outside of the issue queues, this is our best communication medium for projects. Please keep your messages on topic for each channel, and please use the appropriate channel. Spamming channels with unsolicited or frequent messages is not allowed. 8 | 9 | ## Unwanted Solicitation through Private Messages 10 | 11 | Directly messaging users (unless the user has specifically requested the information) offering services, events, employment opportunities or freelance projects, is not allowed. We have a #jobs channel where employment opportunities can be posted on top of a online jobs board at [jobs.cncf.io](https://jobs.cncf.io) 12 | 13 | ### Unwanted Voice/Video Calling 14 | 15 | Abuse of the voice/video calling features to call users without their permission is not allowed. Accidents sometimes happen, let the user know it was a mistake. 16 | 17 | ## Reporting a Problem 18 | 19 | The CNCF Slack has an integrated tool for reporting issues. It may be accessed by clicking on "More actions", the "..." to the right of a message, and selecting Report message. 20 | 21 | Slack guidelines patterned after the [HubSpot Developer Slack Code of Conduct](https://designers.hubspot.com/slack/code-of-conduct) and the [Kubernetes Slack Guidelines](https://github.com/kubernetes/community/blob/master/communication/slack-guidelines.md) 22 | 23 | ## Consequences of Unacceptable Behavior 24 | 25 | Unacceptable behavior from any community member will not be tolerated. 26 | 27 | If a community member engages in unacceptable behavior, CNCF staff may take any action deemed appropriate, up to and including a warning or temporary 30 day ban, along with a permanent ban for repeated violation of these guidelines. 28 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2023-08-31.spdx: -------------------------------------------------------------------------------- 1 | SPDXVersion: SPDX-2.1 2 | DataLicense: CC0-1.0 3 | SPDXID: SPDXRef-DOCUMENT 4 | DocumentName: cncf-exceptions-2023-08-31 5 | DocumentNamespace: https://github.com/cncf/foundation/license-exceptions-2023-08-31 6 | Creator: Organization: CNCF 7 | Created: 2023-09-8T13:52:00Z 8 | 9 | ##### Package: docker/go-metrics 10 | 11 | PackageName: docker/go-metrics 12 | SPDXID: SPDXRef-Package2 13 | PackageDownloadLocation: NOASSERTION 14 | FilesAnalyzed: false 15 | PackageLicenseConcluded: CC-BY-SA 4.0 16 | PackageLicenseDeclared: NOASSERTION 17 | PackageCopyrightText: NOASSERTION 18 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31 19 | 20 | 21 | ##### Package: hashicorp/go-memdb 22 | 23 | PackageName: hashicorp/go-memdb 24 | SPDXID: SPDXRef-Package3 25 | PackageDownloadLocation: NOASSERTION 26 | FilesAnalyzed: false 27 | PackageLicenseConcluded: MPL-2.0 28 | PackageLicenseDeclared: NOASSERTION 29 | PackageCopyrightText: NOASSERTION 30 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31 31 | 32 | ##### Package: shoenig/go-m1cpu 33 | 34 | PackageName: shoenig/go-m1cpu 35 | SPDXID: SPDXRef-Package4 36 | PackageDownloadLocation: NOASSERTION 37 | FilesAnalyzed: false 38 | PackageLicenseConcluded: MPL-2.0 39 | PackageLicenseDeclared: NOASSERTION 40 | PackageCopyrightText: NOASSERTION 41 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31 42 | 43 | ##### Package: hashicorp/packer-plugin-sdk 44 | 45 | PackageName: hashicorp/packer-plugin-sdk 46 | SPDXID: SPDXRef-Package5 47 | PackageDownloadLocation: NOASSERTION 48 | FilesAnalyzed: false 49 | PackageLicenseConcluded: MPL-2.0 50 | PackageLicenseDeclared: NOASSERTION 51 | PackageCopyrightText: NOASSERTION 52 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-08-31 53 | -------------------------------------------------------------------------------- /license-exceptions/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## License exceptions 4 | 5 | The manifest files in this directory contain a list of license exceptions that have been approved by the CNCF Governing Board. The exceptions are provided in JSON and SPDX tag-value format for convenience. 6 | 7 | These manifests will be updated from time to time as new exceptions are approved. 8 | 9 | Please see the [CNCF charter] and the [Allowlist Policy] for more background information. 10 | 11 | ## Allowlisted components 12 | 13 | For convenience, the manifests also contain a list of certain other dependencies for which individual license exceptions were not required. This is either because (a) they were automatically approved as license exceptions under CNCF's [Allowlist Policy]; or (b) they are under Apache-2.0 and therefore aligned with the IP policy in the [CNCF charter]. 14 | 15 | Dependencies that are not currently listed in the manifests, but which satisfy (a) or (b) in the preceding paragraph, are automatically approved and do not need separate license exceptions. 16 | 17 | [Allowlist Policy]: https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md#cncf-allowlist-license-policy 18 | [CNCF charter]: https://github.com/cncf/foundation/blob/main/charter.md 19 | 20 | ## GPL exceptions for in-kernel eBPF programs 21 | 22 | By email vote concluded on August 31 2023, the Governing Board approved a blanket exception for in-kernel eBPF programs licensed under either of the following licenses, either on its own or dual licensed in combination with any license already on the CNCF Licensing Allowlist Approved Licenses list (e.g., MIT License): 23 | 24 | * GPL 2.0 25 | * GPL 2.0 or later 26 | 27 | This exception is not documented in the SPDX/JSON files because it applies only to in-kernel eBPF programs. Usage of GPL 2.0 (or later) for other code is not approved. There is more background explaining the rationale behind this exception in [this document](https://docs.google.com/document/d/10CY8V1w8aQ6CrJ_US_Gnz8cx2SoOtOBqpUKX4cWl_4w/edit#heading=h.oxrtx3xdj6dn). 28 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # ☁️♮🏛Cloud Native Computing Foundation Policy Repo 2 | 3 | This repo contains several documents related to the operation of the [Cloud Native Computing Foundation](https://cncf.io). 4 | 5 | ## Governance 6 | 7 | * The [charter](charter.md) under which CNCF operates 8 | * [Maintainer election policy](policies-guidance/maintainers-election-policy.md) for the maintainer-elected TOC member and the two maintainers on the governing board 9 | * The [membership](cncf-membership-agreement.pdf) agreement 10 | * The [Code of Conduct](code-of-conduct.md) which has been translated into multiple languages 11 | 12 | ## Project Guidance 13 | 14 | * [Copyright](copyright-notices.md) notice recommendations 15 | * [Website guidelines](policies-guidance/website-guidelines.md) for mentioning companies while maintaining neutrality 16 | * [Allowlist License Policy](policies-guidance/allowed-third-party-license-policy.md) for which licenses are acceptable in upstream dependencies without requiring an explicit vote of the governing board 17 | 18 | ## Community recommendations 19 | 20 | * [CNCF Blog Guidelines](policies-guidance/blog-guidelines.md) outlining who can submit, suggested topics, and how to submit. 21 | * A [style guide](style-guide.md) with recommendations for cloud native terminology 22 | * A [translation guide](translation.md) for the Chinese equivalent of cloud native phrases 23 | 24 | ## Other content 25 | 26 | A lot of project, SIG, and TOC-related content is in the TOC [repo](https://github.com/cncf/toc#cncf-technical-oversight-committee-toc). [cncf.io](https://cncf.io) has information on all programs offered publicly by CNCF. 27 | 28 | The list of maintainers for each CNCF project is held in the [project-maintainers.csv](project-maintainers.csv) file. An existing project maintainer can update this list by Pull Request, and they should also email cncf-maintainer-changes@cncf.io (or raise a service desk ticket) to request corresponding changes to the project's CNCF-run maintainer mailing list. 29 | 30 | ## How to request changes 31 | 32 | You are welcome to file non-technical [issues](https://github.com/cncf/foundation/issues/new) related to [CNCF](https://cncf.io) on this repo. 33 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023 -01-24- ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | ## Cloud Native Project Monthly (CNPM) Jan 2023 2 | #### January 24, 2023 3 | 4 | Welcome into a new year! 5 | This is our new Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 6 | 7 | In this edition for January 2023 - 8 | ### Ambassador Applications Open 9 | ### LFX Mentorships - March through May cycle open 10 | ### New: Request meetings with Projects team 11 | 12 | 13 | 14 | ### Ambassador Applications Open 15 | 16 | As we approach 2023, the prestigious CNA program has been refreshed and we are now accepting applications for spring 2023. Could you be the newest CNA? If you have a track record of significant and impactful contributions to the cloud native community, check out the responsibilities and requirements to apply. 17 | 18 | 19 | ### LFX Mentorships - March through May cycle open 20 | 21 | The LFX Mentorship 2023 Term 01 March - May is open now open for project ideas: 22 | 23 | https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2023/01-Mar-May 24 | 25 | Project submission and application timeline: 26 | 27 | - project proposal period: January 16 - 31 *we are here* 28 | - mentee applications open: February 1 - 14 (2 weeks) 29 | - application review/admission decisions/HR paperwork: February 15 - 28 30 | 31 | 32 | We're looking forward to seeing all the project ideas you're interested in working on! 33 | 34 | ### New: Request meetings with Projects team 35 | 36 | One of the benefits of a CNCF Project is being able to get time on the CNCF’s calendar to discuss issues, concerns, or ideas your project has. To better execute on this offering, we’ve set up a Calendly to enable scheduling time with us! 37 | 38 | Our door is always open, so feel free to schedule as needed! 39 | 40 | 41 | Note: When requesting, give us an idea of your discussion topics so we can ensure the right CNCF folks are in the room! 42 | 43 | Ideally we’d like to hear from each of you at least once a year, so we may start reaching out to check on the weather in your project. :) 44 | 45 | 46 | Questions? 47 | Drop a note back to projects@cncf.io, we’re happy to help! 48 | -------------------------------------------------------------------------------- /KubeWeekly.md: -------------------------------------------------------------------------------- 1 | # KubeWeekly Guidelines 2 | 3 | ## Overview 4 | 5 | KubeWeekly is a weekly e-mail newsletter covering Kubernetes, cloud-native, open source, and projects in the cloud-native ecosystem. 6 | 7 | It is targeted at a technical audience (developers, IT operators), and curated by a team of editors from the Kubernetes community. 8 | 9 | The newsletter is sent out every Friday. 10 | 11 | ## Contributing Guidelines 12 | 13 | To provide high-value content to the community, the editors review article submissions based on these guidelines. 14 | 15 | * We aim to highlight open source information, how-tos, and cloud native thought leadership 16 | * Content should be of interest to the community as a whole, not just the users of a single commercial platform. 17 | * Content does not have to be vendor-neutral, but a press release or commercial announcement that does not outline feature benefits or how to use the project / product is not appropriate. 18 | * No gated content, unless in the webinar section. 19 | * Articles should be published within the last month. Exceptions will be made for good content we missed. 20 | * Only CNCF Online Programs, CNCF hosted events, and CNCF supported events are promoted in KubeWeekly 21 | 22 | ## Editor requirements: 23 | 24 | Commitment: 1 year 25 | 26 | * 1-2 hours a week; scanning for content and reviewing submissions (async) 27 | * Wednesday afternoon for review time, add notes for articles not chosen 28 | * Kickoff call/1x quarter to touch base 29 | * Actively contributing to 1x project 30 | * Ability to have an unbiased/vendor-neutral perspective when choosing/approving articles 31 | 32 | 33 | **Types of Content** 34 | The types of content shared includes but is not limited to: 35 | * Articles 36 | * Blogs 37 | * Videos 38 | * Podcasts 39 | * GitHub repos 40 | 41 | ## Publication of events 42 | 43 | With tens of thousands of people in the Kubernetes community, the editors could never keep up with the events and publish them in KubeWeekly. 44 | 45 | The only events shared in KubeWeekly are the CNCF Online Programs, CNCF hosted events, and CNCF supported events. 46 | 47 | ## To submit content 48 | 49 | Interested in submitting an article? Submit your form [here](https://form.asana.com/?k=z6hNf3wVvlLxETIco730kw&d=9283783873717) 50 | -------------------------------------------------------------------------------- /policies-guidance/sandbox-pr-guidelines.md: -------------------------------------------------------------------------------- 1 | # Sandbox Project Public Relations FAQ 2 | ## Updated: March 1 3 | 4 | # Guidelines: 5 | Please avoid using the word donated. The correct term for companies who have projects accepted into the CNCF Sandbox is “contributed”. Do not use the term “donated.” 6 | Please always mention “Sandbox” when talking about where the project will be housed. For example: [Company] has contributed [project] to the CNCF Sandbox. 7 | Please wait until a project is officially accepted into the CNCF Sandbox to make any public announcements as submissions are not always accepted and not every project application is considered in any given meeting. 8 | 9 | # Can our company announce that an open source project has been accepted to the CNCF Sandbox? 10 | Yes, once the project is officially accepted into the CNCF Sandbox through the TOC vote, you are welcome to make your own announcement. However, CNCF as a policy does not provide any marketing or public relations support at this level. 11 | 12 | # Will someone from CNCF provide a quote for our press release or blog about a Sandbox project being contributed? 13 | Unfortunately, no, we do not provide any marketing or public relations support to Sandbox projects. However, you are welcome to reach out to a supporting CNCF TOC member if you like, however, they are under no obligation to provide a quote. 14 | 15 | # Can we speak to the media about a project being accepted into the CNCF Sandbox? 16 | Yes - however - please make sure that the journalists or influencers understand and report accurately that this project is entering the CNCF Sandbox. Instances where this is not reported accurately can result in CNCF requesting a correction from you or the outlet. 17 | 18 | # Will CNCF support our announcement on social media? 19 | We can retweet the announcement once from our @CloudNativeFdn handle, however in order to do so, the tweet will need to adhere to the following guidelines: 20 | The tweet cannot come from a company handle 21 | The tweet cannot tag any company handle or make reference to the company contributing the project 22 | 23 | You can email pr@cncf.io with a request to retweet. 24 | 25 | # If we have questions about what is acceptable to say in our announcement, who can we reach out to? 26 | The CNCF PR team is more than happy to review your announcement or answer any questions you may have. You can contact the team at pr@cncf.io. 27 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-04-26-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | Cloud Native Project Monthly (CNPM) April 2023 2 | April 26, 2023 3 | 4 | Welcome back from Kubecon! 5 | This is our Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 6 | 7 | In this edition for April 2023: 8 | ## KubeCon EU 2023 Retro Doc 9 | ## CNCF Project Summary Table 10 | ## LFC Courses - Free to all! 11 | ## Mentoring - LFX 12 | ## TechDocs Open Office Hours 13 | 14 | #### 15 | 16 | ## KubeCon EU 2023 Retro Doc 17 | Were you at KubeCon EU 2023? Do you have any feedback to make the event better OR want to gush at the Events team? 18 | 19 | Each KubeCon we’ve been collecting community feedback from a subset of folks, but we’d like to open it up to the entire maintainer community. 20 | 21 | Thanks in advance! 22 | 23 | ## CNCF Project Summary Table 24 | A lesser-known part of the CNCF Landscape is the Project Summary Table. Part of the Landscape are fields that allow projects to define both typical and business use cases. 25 | 26 | Please check and see if your project already has these Use Case fields populated and if not, fill them in with some useful information. If you need help or a launching off point, please check KubeEdge’s Use Cases or contact projects@cncf.io 27 | 28 | ## LFC Courses 29 | The Linux Foundation has worked with the CNCF and created several courses specific to Open Source and inclusive communication. 30 | These are free for anyone to take so please feel free to sign up if you haven’t. 31 | https://training.linuxfoundation.org/training/inclusive-speaker-orientation/ 32 | https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ 33 | https://training.linuxfoundation.org/training/inclusive-strategies-for-open-source-lfc103/ 34 | 35 | 36 | ## Mentoring - LFX Mentorship 37 | 38 | LFX Proposals are open for both Term 02 and 03. If you have proposals, please feel free to open a PR and submit! These are a great alternative to GSoC if your proposal wasn’t accepted. 39 | Term 02 - 2023 June - August 40 | Term 03 - 2023 September - November 41 | 42 | ## TechDocs Open Office Hours 43 | 44 | On the last Wednesday of each month, the TechDocs team hosts Open Office Hours for anyone to drop in with questions about technical documentation. Our next session will be on April 26, 2023, at 8:00 AM PDT. You can find details on how to join us on the public calendar. Hope to see you there! 45 | -------------------------------------------------------------------------------- /travel_funding.md: -------------------------------------------------------------------------------- 1 | # CNCF Scholarship / Travel Funding Process 2 | 3 | 1. Event team will determine the close date and notification deadline. 4 | 5 | - a. Deadline is based on schedule announcement, visa process time, speaker notifications, length of the review period. 6 | 7 | - b. Notifications made 6 - 8 weeks prior to event. 8 | 9 | 2. Launch Application with link, information and dates on event website 4 months prior to the application deadline (6 months prior to event). 10 | 11 | 3. Applicants complete Survey Monkey application 12 | 13 | 4. Project determines a review committee. 14 | 15 | 5. Event team provides committee with timeline for review process. 16 | 17 | - a. The requirement is not to review on a rolling basis but rather wait for all applications to be submitted and then reviewed comprehensively. 18 | 19 | - b. Need to allow enough time between submission and notifications to compile applications, review committee to make selections, etc. 20 | 21 | - c. Recommended review period for committee is 7-10 days depending on the number of applicants and review committee availability. 22 | 23 | - d. Once selections are made, 1 week is needed to process notifications internally. 24 | 25 | 6. Event team collates submission information in a spreadsheet (remove duplicates, check the formatting, provide scholarship history, etc.) to present to review committee. 26 | 27 | 7. Review committee reviews and scores applications and requests. 28 | 29 | - a. Review committee to consider: Impact, Outreach, and Equity. 30 | 31 | - b. Any applicants not selected for a Diversity Scholarship, who selected Kubernetes Contributor (volunteer, speaker, contributor) or a CNCF-organized Day Zero Co-Lo will then be sent to respective review committees for funding consideration. 32 | 33 | 8. Event team creates and sends notification letters with reimbursement instructions. 34 | 35 | 9. Event team to manage invoices and reimbursement 36 | 37 | - a. Expense reports and receipts must be submitted within 30 days of completion of travel. Reimbursement will be made within 30 business days after the final expense report has been submitted and approved. 38 | 39 | - b. It is the responsibility of the recipient to arrange, reserve, and pay for accommodations and/or flight directly. They will then be reimbursed for approved travel expenses not to exceed a maximum stipend amount. The stipend may only be used for coach airfare, hotel/accommodations (up to five nights), and ground transportation (to and from the airport). 40 | 41 | - c. Attendance is required in order to be reimbursed. 42 | -------------------------------------------------------------------------------- /code-of-conduct-languages/zh.md: -------------------------------------------------------------------------------- 1 | ## 社区行为准则 2 | 3 | 作为 CNCF 社区的贡献者、维护者和参与者，我们努力建设一个开放和受欢迎的社区，我们承诺尊重所有上报 Issue、发布功能需求、更新文档、提交 PR 或补丁、参加会议或活动以及其他社区和项目活动的贡献者和参与者。 4 | 5 | 我们致力于让参与 CNCF 社区的每个人都不受骚扰，无论其年龄、体型、种姓、残疾、族裔、经验水平、家庭状况、性别、性别认同和表达、婚姻状况、军人或退伍军人身份、国籍、个人外表、种族、宗教、性取向、社会经济地位、部落或任何其他多样性维度如何。 6 | 7 | ## 范围 8 | 9 | 本行为准则适用于： 10 | 11 | * 项目和社区空间， 12 | * 其他空间（在个别 CNCF 社区参与者的言论或行动针对或涉及 CNCF 项目、CNCF 社区或其他 CNCF 社区参与者的情况下）。 13 | 14 | ## CNCF 活动 15 | 16 | 由 Linux 基金会和专业活动人员举办的 CNCF 活动受 Linux 基金会[《活动行为准则》](https://events.linuxfoundation.org/code-of-conduct/)管辖，该行为准则可在活动页面获得。 该准则旨在与《CNCF 行为准则》结合使用。 17 | 18 | ## 我们的标准 19 | 20 | CNCF 社区是一个开放、包容和互相尊重的社区。我们社区的每个成员都有权让自己的身份受到尊重。 21 | 22 | 有助于营造积极环境的行为示例包括但不限于： 23 | 24 | * 对他人表现出同理心和善意 25 | * 尊重不同的意见、观点和经验 26 | * 提供并优雅地接受建设性反馈 27 | * 承担责任，向那些受我们错误影响的人道歉，并从经验中吸取教训 28 | * 关注点不只放在如何让我们自己受益，还要着眼于整个社区 29 | * 使用欢迎和包容性的语言 30 | 31 | 不可接受的行为示例包括但不限于： 32 | 33 | * 使用性语言或图像 34 | * 挑衅、侮辱或贬损的言语，以及个人或政治攻击 35 | * 任何形式的公开或私下骚扰 36 | * 未经明确许可，发布他人的私人信息，比如实际地址或电子邮件地址 37 | * 暴力，威胁暴力，或鼓励他人参与暴力行为 38 | * 未经同意跟踪或跟随他人 39 | * 不受欢迎的身体接触 40 | * 不受欢迎的与性有关的或调情性质的关注或示爱 41 | * 其他在专业环境中被合理认为不适当的行为 42 | 43 | 同样禁止以下行为： 44 | 45 | * 故意提供与行为准则调查有关的虚假或误导性信息，或以其他方式故意干预调查。 46 | * 因为某人作为证人报告了事件或提供了有关事件的信息而对其进行报复。 47 | 48 | 项目维护者有权且有责任删除、编辑或拒绝与本行为准则不一致的评论、提交、代码、Wiki 编辑、问题和其他贡献。采用本行为准则即表明，项目维护者承诺公平且一致地将这些准则应用于管理 CNCF 项目的各个方面。不遵守或不执行行为准则的项目维护者可能被临时或永久地从项目团队中移除。 49 | 50 | ## 报告 51 | 52 | 对于在 Kubernetes 社区中发生的事件，请通过 [conduct@kubernetes.io](mailto:conduct@kubernetes.io) 联系 [Kubernetes 行为准则委员会](https://git.k8s.io/community/committee-code-of-conduct)。预计您可以在三个工作日内收到答复。 53 | 54 | 对于其他项目，或与项目无关或影响多个 CNCF 项目的事件，请通过 [conduct@cncf.io](mailto:conduct@cncf.io) 与 [CNCF 行为准则委员会](https://www.cncf.io/conduct/committee/)联系。或者，您可以联系 [CNCF 行为准则委员会](https://www.cncf.io/conduct/committee/)的任何个人成员提交您的报告。有关如何提交报告（包括如何匿名提交报告）的更详细说明，请参阅我们的[事件解决程序](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md)。预计您可以在三个工作日内收到答复。 55 | 56 | 关于由 Linux 基金会组织的发生在 CNCF 活动中的事件，请联系 [eventconduct@cncf.io](mailto:eventconduct@cncf.io)。 57 | 58 | ## 执行 59 | 60 | 在对报告的事件进行审查和调查后，具有管辖权的 CoC 响应团队将根据本行为准则及其相关文件决定采取何种适当行动。 61 | 62 | 有关哪些行为准则事件由项目领导处理，哪些事件由 CNCF 行为准则委员会处理，以及哪些事件由 Linux基金会（包括其事件团队）处理的信息，请参阅我们的[管辖权政策](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md)。 63 | 64 | ## 修正 65 | 66 | 与 CNCF 章程一致，对本行为准则的任何实质性修改必须得到技术监督委员会的批准。 67 | 68 | ## 致谢 69 | 70 | 本行为准则改编自《贡献者公约》 ([http://contributor-covenant.org](http://contributor-covenant.org/))，该文件的 2.0 版本载于 [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) 71 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2022-04-12.spdx: -------------------------------------------------------------------------------- 1 | SPDXVersion: SPDX-2.1 2 | DataLicense: CC0-1.0 3 | SPDXID: SPDXRef-DOCUMENT 4 | DocumentName: cncf-exceptions-2022-04-12 5 | DocumentNamespace: https://github.com/cncf/foundation/license-exceptions-2022-04-12 6 | Creator: Organization: CNCF 7 | Creator: Tool: cncf-exceptions-maker-0.1 8 | Created: 2023-05-26 9 | 10 | ##### Package: webpki-roots 11 | 12 | PackageName: webpki-roots 13 | SPDXID: SPDXRef-Package2 14 | PackageDownloadLocation: NOASSERTION 15 | FilesAnalyzed: false 16 | PackageLicenseConcluded: MPL-2.0 17 | PackageLicenseDeclared: NOASSERTION 18 | PackageCopyrightText: NOASSERTION 19 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 20 | 21 | ##### Package: go-version 22 | 23 | PackageName: go-version 24 | SPDXID: SPDXRef-Package3 25 | PackageDownloadLocation: NOASSERTION 26 | FilesAnalyzed: false 27 | PackageLicenseConcluded: MPL-2.0 28 | PackageLicenseDeclared: NOASSERTION 29 | PackageCopyrightText: NOASSERTION 30 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 31 | 32 | ##### Package: raft 33 | 34 | PackageName: raft 35 | SPDXID: SPDXRef-Package4 36 | PackageDownloadLocation: NOASSERTION 37 | FilesAnalyzed: false 38 | PackageLicenseConcluded: MPL-2.0 39 | PackageLicenseDeclared: NOASSERTION 40 | PackageCopyrightText: NOASSERTION 41 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 42 | 43 | ##### Package: raft-boltdb 44 | 45 | PackageName: raft-boltdb 46 | SPDXID: SPDXRef-Package5 47 | PackageDownloadLocation: NOASSERTION 48 | FilesAnalyzed: false 49 | PackageLicenseConcluded: MPL-2.0 50 | PackageLicenseDeclared: NOASSERTION 51 | PackageCopyrightText: NOASSERTION 52 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 53 | 54 | 55 | ##### Package: tslib 56 | 57 | PackageName: tslib 58 | SPDXID: SPDXRef-Package6 59 | PackageDownloadLocation: NOASSERTION 60 | FilesAnalyzed: false 61 | PackageLicenseConcluded: 0BSD 62 | PackageLicenseDeclared: NOASSERTION 63 | PackageCopyrightText: NOASSERTION 64 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 65 | 66 | ##### Package: paho.mqtt.golang 67 | 68 | PackageName: paho.mqtt.golang 69 | SPDXID: SPDXRef-Package7 70 | PackageDownloadLocation: NOASSERTION 71 | FilesAnalyzed: false 72 | PackageLicenseConcluded: EPL-2.0 73 | PackageLicenseDeclared: NOASSERTION 74 | PackageCopyrightText: NOASSERTION 75 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2022-04-12 76 | -------------------------------------------------------------------------------- /cncf-marketing-committee-chair.md: -------------------------------------------------------------------------------- 1 | # CNCF Marketing Committee Chair # 2 | 3 | *Role, as defined in the [CNCF Charter](https://github.com/cncf/foundation/blob/main/charter.md#10-marketing-committee)* 4 | 5 | ## Overview ## 6 | 7 | The CNCF Marketing Committee (MC) Chair is a crucial partner to the CNCF marketing team, providing a unique member perspective and enabling other member marketers. 8 | The MC Chair is a member of CNCF and has a strong understanding of the CNCF member programs and can serve as a mentor to other members within the MC, as well as lead the monthly calls. 9 | The ideal MC Chair has a strong marketing background, is collaborative, and has strong public speaking skills. 10 | 11 | ## Responsibilities ## 12 | 13 | * Lead and moderate monthly MC meetings with the support of CNCF staff 14 | * Encourage networking and collaboration across the MC 15 | * Meet with new MC members and guide them on how to utilize CNCF resources successfully via office hours 16 | * Have a good understanding of all CNCF member marketing benefits and be able to discuss them with existing members 17 | * Provide guidance and assistance to Subcommittees and other initiatives that emerge from the MC (as needed) 18 | 19 | ## Requirements ## 20 | To be nominated for MC Chair you must have the following: 21 | * Be a member company of CNCF for at least 1 year 22 | * Have attended at least 75% of MC meetings in the past year 23 | 24 | ## Time commitment ## 25 | 26 | Minimum 3 hours a month 27 | * 1 hour MC meeting 28 | * 2 hours of meeting preparation and follow up 29 | 30 | ## Term ## 31 | 32 | * The Marketing Committee Chair shall serve a 1 year term. 33 | 34 | ## Voting requirements ## 35 | * Votes may only be cast from members 36 | * 1 vote per member company will count 37 | * Employees of The Linux Foundation are disqualified from voting to allow for community voice 38 | 39 | ## Benefits ## 40 | 41 | * Build your thought leadership in the cloud native community 42 | * Network with other marketing contacts across CNCF members 43 | * Boost your knowledge of open source and the CNCF community 44 | * CNCF Swag Basket 45 | * Free registration to attend either KubeCon + CloudNativeCon North America or Europe 46 | 47 | ## Past MC Chairs ## 48 | 49 | * 2025: Rohit Ghumare 50 | * 2024: Carla Gaggini 51 | * 2023: Lori Lorusso 52 | * 2022: Carla Gaggini 53 | * 2021: Lexi Nadolski + Kaitlyn Barnard 54 | 55 | ## Marketing Committee Chair Election Timeline ## 56 | 57 | * Call for nominations: November 15 58 | * End of call for nominations: November 26 59 | * Presentation to MC committee: December 4 60 | * Voting occurs: December 4-11 61 | * The election will end on December 11 62 | * New MC chair makes their debut in January 2025 63 | 64 | Contact [CNCF Marketing](marketingteam@cncf.io) with questions. 65 | -------------------------------------------------------------------------------- /code-of-conduct-languages/ro.md: -------------------------------------------------------------------------------- 1 | ## Cod de conduită al comunității CNCF v1.0 2 | 3 | ### Cod de conduită al colaboratorului 4 | 5 | În calitate de colaboratori și de întreținători ai acestui proiect și în interesul promovării 6 | unei comunități deschise și primitoare, ne angajăm să respectăm toate persoanele care contribuie 7 | prin raportarea problemelor, postarea cererilor de funcții, actualizarea documentației, 8 | trimiterea de pull request-uri sau patch-uri și alte activități. 9 | 10 | Ne-am angajat să facem participarea la acest proiect o experiență fără hărțuire pentru 11 | toată lumea, indiferent de nivelul de experiență, sex, identitate și expresie de gen, 12 | orientare sexuală, dizabilitate, aspect personal, mărimea corpului, rasă, etnie, vârstă, 13 | religie sau naționalitate. 14 | 15 | Exemple de comportament neacetabil ale unui participant: 16 | 17 | * Folosirea unui limbaj sau imagini de natură sexuală 18 | * Atacuri personale 19 | * Trolling sau insulte/comentarii derogatorii 20 | * Hărțuire publică sau privată 21 | * Publicarea de informație privata a altor persoane, cum ar fi adresa fizica sau electronică, fară permisiune 22 | * Alte comportamente neetice sau neprofesionale 23 | 24 | Mentenanții de proiect au dreptul și responsabilitatea să steargă, editeze 25 | sau să respingă comentarii, commit-uri, cod, editări de wiki, issues, si alte contribuții 26 | care nu sunt aliniate cu acest Cod de Conduită. Prin adoptarea acestui Cod de Conduită, 27 | mentenanții de proiect se dedică să aplice, corect si consistent, aceste principii la toate 28 | aspectele gestionării acestui proiect. Mentenanții de proiect care nu urmăresc sau impun 29 | Codul de Conduită pot fi eliminați definitiv din echipa de proiect. 30 | 31 | Acest cod de conduită se aplică atât în spațiile proiectului, cât și în spațiile publice 32 | atunci când o persoană reprezintă proiectul sau comunitatea sa. 33 | 34 | Instanțele de comportament abuziv, hărțuitor sau altfel inacceptabil în Kubernetes pot fi raportate contactând [Comitetul pentru Codul de Conduită Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) via . Pentru alte proiecte, vă rugăm să contactați un întreținător de proiect CNCF sau pe mediatorul nostru, Mishi Choudhary . 35 | Acest Cod de Conduită este adaptat din Pactul de Contribuitori (http://contributor-covenant.org), vesiunea 1.2.0, disponibila la 36 | http://contributor-covenant.org/version/1/2/0/ 37 | 38 | ### Cod de Conduită al evenimentelor CNCF 39 | Evenimentele CNCF sunt guvernate de [Codul de Conduită](https://events.linuxfoundation.org/code-of-conduct/) al Fundației Linux disponibil pe pagina evenimentului. Acesta este conceput pentru a fi compatibil cu politica de mai sus și include, de asemenea, mai multe detalii privind reacția la incidente. 40 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2023-06-27.json: -------------------------------------------------------------------------------- 1 | [ 2 | { 3 | "package": "github.com/hashicorp/go-plugin", 4 | "license": "MPL-2.0 ", 5 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 6 | }, 7 | { 8 | "package": "github.com/hashicorp/go-immutable-radix", 9 | "license": "MPL-2.0 ", 10 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 11 | }, 12 | { 13 | "package": "github.com/hashicorp/raft", 14 | "license": "MPL-2.0 ", 15 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 16 | }, 17 | { 18 | "package": "github.com/hashicorp/go-rootcerts", 19 | "license": "MPL-2.0 ", 20 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 21 | }, 22 | { 23 | "package": "github.com/hashicorp/go-sockaddr", 24 | "license": "MPL-2.0 ", 25 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 26 | }, 27 | { 28 | "package": "github.com/hashicorp/vault", 29 | "license": "MPL-2.0 ", 30 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 31 | }, 32 | { 33 | "package": "github.com/hashicorp/consul/api", 34 | "license": "MPL-2.0 ", 35 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 36 | }, 37 | { 38 | "package": "github.com/hashicorp/serf", 39 | "license": "MPL-2.0 ", 40 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 41 | }, 42 | { 43 | "package": "github.com/hashicorp/serf", 44 | "license": "MPL-2.0 ", 45 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 46 | }, 47 | { 48 | "package": "github.com/hashicorp/go-hclog", 49 | "license": "MPL-2.0 ", 50 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 51 | }, 52 | { 53 | "package": "github.com/hashicorp/go-secure-stdlib", 54 | "license": "MPL-2.0 ", 55 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 56 | }, 57 | { 58 | "package": "github.com/hashicorp/go-uuid", 59 | "license": "MPL-2.0 ", 60 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 61 | }, 62 | { 63 | "package": "github.com/hashicorp/go-version", 64 | "license": "MPL-2.0 ", 65 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 66 | }, 67 | { 68 | "package": "github.com/veraison/go-cose", 69 | "license": "MPL-2.0 ", 70 | "comment": "not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27" 71 | } 72 | ] 73 | -------------------------------------------------------------------------------- /code-of-conduct-languages/ja.md: -------------------------------------------------------------------------------- 1 | ## コミュニティの行動規範 2 | 3 | CNCFコミュニティのコントリビューター、メンテナ、および参加者は、オープンかつ快適なコミュニティを促進するために、問題の報告、機能要求の投稿、ドキュメントの更新、プルリクエストまたはパッチの送信、カンファレンスやイベントへの参加、または他のコミュニティ、プロジェクト活動を通して参加または貢献するすべての人々を尊重することを誓います。 4 | 5 | 私たちは、年齢、身体の大きさ、カースト、障害、民族性、経験レベル、家族構成、性別、性自認と性表現、配偶者の有無、軍人または退役軍人の地位、国籍、容姿、人種、宗教、性的指向、社会経済的地位、部族、またはその他あらゆる多様性の側面に関係なく、CNCFコミュニティへの参加を、全員にとってハラスメントがない経験にすることを約束します。 6 | 7 | ## 適用範囲 8 | 9 | 本行動規範の適用範囲： 10 | 11 | 12 | 13 | * プロジェクトやコミュニティのスペース内 14 | * CNCFコミュニティ参加者の言葉や行動が、CNCFプロジェクト、CNCFコミュニティ、または他のCNCFコミュニティ参加者に向けられる、またはそれらに関連する場合の他のスペース内 15 | 16 | ## CNCFイベント 17 | 18 | Linux Foundationのプロフェッショナルなイベントスタッフによって制作されるCNCFイベントに関しては、イベントページにあるLinux Foundationの[イベント行動規範](https://events.linuxfoundation.org/code-of-conduct/)に準拠します。これは、CNCF行動規範と併用されることを目的としています。 19 | 20 | ## 規範 21 | 22 | CNCFコミュニティはオープンであり、包括的であり、敬意をもって接されます。コミュニティのすべてのメンバーは、自分自身のアイデンティティが尊重される権利を持っています。 23 | 24 | 良い環境を構築するための参加者の行動の例は以下のようなものが含まれますが、これらに限定されるものではありません。 25 | 26 | 27 | 28 | * 他人への共感と思いやりを表す 29 | * 異なる意見、視点、経験を尊重する 30 | * 建設的なフィードバックを心がけ、それを快く受け入れる 31 | * ミスに対して責任感を持ち、その影響を受けた人々に謝罪し、その経験から学ぶこと 32 | * 個人だけではなく、コミュニティ全体として何が最善策かを重視する 33 | * 快適で包括的な言葉の使用 34 | 35 | 一方で、以下のような行動は受け入れられませんが、これらに限定されるものではありません。 36 | 37 | 38 | 39 | * 性的な言語や描写の使用 40 | * 煽りや侮辱的、軽蔑的なコメント、および個人または政治的な攻撃 41 | * あらゆる形態の公開または非公開のハラスメント 42 | * 明示的な許可なしに他人の個人情報(住所やメールアドレス)を公開すること 43 | * 暴力、脅迫、またはこれらの行為を助長する行為 44 | * ストーカー行為やその人の意思に反した追跡行為をすること 45 | * 望ましくない身体的な接触 46 | * 歓迎されない性的または恋愛的な注目や誘い 47 | * その他、プロフェッショナルな場において不適切とみなされうる行為 48 | 49 | また、次のような行動も禁止されています。 50 | 51 | 52 | 53 | * 行動規範の調査に関連して故意に誤った情報や誤解を招く情報を提供する、あるいは調査を故意に妨害する。 54 | * インシデントを報告したり、証人としてインシデントに関する情報を提供したりした人へ対する報復行為。 55 | 56 | プロジェクトのメンテナは、この行動規範に準拠していないコメント、コミット、コード、Wikiの編集、問題、他のコントリビューションを削除、編集、または却下する権利および責任を持っています。プロジェクトのメンテナは、本行動規範を採用することで、公正かつ一貫した方法で、これらの原則をCNCFプロジェクトの管理におけるすべての要素に適用することに注力します。本行動規範を遵守または施行しないプロジェクトのメンテナは、一時的あるいは永久的にプロジェクトのチームから抹消される可能性があります。 57 | 58 | ## 報告 59 | 60 | Kubernetesコミュニティにて問題が発生した場合には、[conduct@kubernetes.io](mailto:conduct@kubernetes.io)から[Kubernetes Code of Conduct Committee](https://git.k8s.io/community/committee-code-of-conduct)(行動規範委員会)までご連絡ください。通常3営業日以内に返信致します。 61 | 62 | その他のプロジェクトや複数のプロジェクトに影響を与えるインシデントにつきましては、[CNCFの行動規範委員会](https://www.cncf.io/conduct/committee/)(email: [conduct@cncf.io](mailto:conduct@cncf.io))までご連絡ください。あるいは、[CNCFの行動規範委員会](https://www.cncf.io/conduct/committee/)の個別のメンバーに報告することもできます。報告の手順や匿名での報告方法など、より詳細な情報は、[インシデント解決手順](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md)をご覧ください。通常3営業日以内に返信致します。 63 | 64 | Linux Foundationが制作するCNCFイベントでのインシデントについては、[eventconduct@cncf.io](mailto:eventconduct@cncf.io)にご連絡ください。 65 | 66 | ## 施行 67 | 68 | 報告されたインシデントのレビューと調査の後、管轄するCoCの対応チームは、この行動規範と関連するドキュメントに基づいて、適切な行動を決定します。 69 | 70 | プロジェクトリーダーシップが取り扱う行動規範のインシデント、CNCF行動規範委員会が取り扱うインシデント、およびLinux Foundation(そのイベントチームを含む)が取り扱うインシデントに関する情報には、私たちの[管轄ポリシー](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md)を参照してください。 71 | 72 | ## 改正 73 | 74 | CNCFの憲章と一貫して、この行動規範に対する実質的な変更は、Technical Oversight Committeeの承認が必要です。 75 | 76 | ## 謝辞 77 | 78 | 本行動規範は、コントリビューター行動規範([http://contributor-covenant.org](http://contributor-covenant.org/))に基づいています。バージョン 2.0はこちらから参照可能です。[http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) -------------------------------------------------------------------------------- /policies-guidance/website-guidelines.md: -------------------------------------------------------------------------------- 1 | August 13, 2017 2 | 3 | Updated: July 9, 2025 4 | 5 | CNCF encourages each project to manage its own website, but after consulting with the projects, 6 | we are publishing a set of guidelines around dealing with potential commercial conflicts. 7 | 8 | Many CNCF projects began life within a single company (called the “origin company” below) and 9 | then transitioned to be community-managed before or after being accepted into the CNCF. This 10 | document provides some guidelines on how the project’s website should evolve. 11 | 12 | Note that many end users are interested in commercial support for CNCF projects, and project 13 | websites are welcome to list and link to companies providing support. However, the key principle 14 | is that the origin company should not be favored over any other companies offering the same 15 | services. 16 | 17 | The guidelines: 18 | 19 | 1. CNCF projects are strongly encouraged to host the source of their websites in an open 20 | source repository (and under the same organization) so that requests to change can be done via 21 | pull requests and the discussions are archived in a transparent manner. 22 | 23 | 2. It is OK to say that, e.g., “Prometheus was originally created by Soundcloud” or “Kubernetes 24 | builds upon 15 years of experience of running production workloads at Google,” but the origin 25 | company should not otherwise be referred to on the project homepage. 26 | 27 | 3. There should be no links or forms for capturing enterprise support leads. Instead, it is fine 28 | to have an enterprise support, commercial partners or similar page. Companies must be listed on 29 | that page in alphabetical order, or the order can be changed randomly on each page load. It’s OK 30 | to have different categories of support offered. Simple vetting by the project is needed to ensure 31 | that all companies listed really can provide the support promised. Projects are welcome to outsource 32 | this vetting to CNCF staff if it becomes a burden. 33 | 34 | 4. Links to companies offering support are expected to go a page that at least mentions support of 35 | the project. This can either be the company homepage or a project-specific landing page. 36 | 37 | 5. If there is a copyright notice at the bottom of the page, copyright should be to the project authors 38 | or to CNCF, not the origin company. For details, see [Copyright notices](https://github.com/cncf/foundation/blob/main/copyright-notices.md). 39 | 40 | 6. CNCF requests that graduated and incubating projects include the sentence “We are a Cloud Native 41 | Computing Foundation project.” and the CNCF logo near the bottom of their project homepage. 42 | Sandbox-level projects should include the sentence “We are a Cloud Native Computing Foundation 43 | sandbox project.” and the CNCF logo. We also appreciate a link to KubeCon + CloudNativeCon as the 44 | events approach. 45 | 46 | 7. Website footers must include trademark guidelines and a copyright notice (where XYZ is the project's name). 47 | 48 | ```text 49 | Copyright XYZ a Series of LF Projects, LLC 50 | For website terms of use, trademark policy and other project policies please see lfprojects.org/policies/. 51 | ``` 52 | 53 | 8. If the project does not have a website, this copyright notice must be added in the README or similar location. 54 | 55 | ```text 56 | Copyright Contributors to XYZ, established as XYZ a Series of LF Projects, LLC. 57 | ``` 58 | 59 | Questions? Email us at . 60 | -------------------------------------------------------------------------------- /code-of-conduct-languages/ko.md: -------------------------------------------------------------------------------- 1 | ## 커뮤니티 행동 강령 2 | 3 | CNCF 커뮤니티의 기여자(contributor), 메인테이너(maintainer), 참여자로서 개방적이고 친근한 분위기의 커뮤니티 조성을 위하여, 저희는 이슈 보고, 기능 요청, 문서 업데이트, 풀 리퀘스트(pull request) 또는 패치(patch) 제출, 컨퍼런스 또는 이벤트 참석, 기타 커뮤니티 또는 프로젝트 활동 참여를 통해 커뮤니티에 참여하거나 기여하는 모든 분을 존중할 것을 서약합니다. 4 | 5 | 저희는 나이, 신체 크기, 계급, 장애, 민족, 경력 수준, 가족 구성원, 성별, 성 정체성 및 표현(gender identity and expression), 결혼 여부, 군필 또는 퇴역 여부, 국적, 외모, 인종, 종교, 성적 지향, 사회경제적 지위, 부족 또는 기타 다양성의 차원에 관계없이 모두가 괴롭힘 없는 환경에서 CNCF 커뮤니티에 참여할 수 있도록 최선을 다하고 있습니다. 6 | 7 | ## 범위 8 | 9 | 본 행동 강령이 적용됩니다: 10 | * 프로젝트 및 커뮤니티 공간 내부에서, 11 | * 다른 공간에서 개별 CNCF 커뮤니티 참여자의 말이나 행동이 CNCF 프로젝트, CNCF 커뮤니티, 또는 다른 CNCF 커뮤니티 참여자를 대상으로 하거나 이에 관한 것일 경우. 12 | 13 | ## CNCF 이벤트 14 | 15 | 리눅스 재단이 전문 이벤트 스태프와 함께 진행하는 CNCF 이벤트는 리눅스 재단의 [이벤트 행동 강령](https://events.linuxfoundation.org/code-of-conduct/)을 따르며, 해당 내용은 이벤트 페이지에서 확인할 수 있습니다. 이는 CNCF 행동 강령과 함께 사용하도록 설계되었습니다. 16 | 17 | ## 우리의 기준 18 | 19 | CNCF 커뮤니티는 개방적이고 포용적이며 서로를 존중합니다. 커뮤니티의 모든 구성원은 자신의 정체성을 존중받을 권리가 있습니다. 20 | 21 | 참여자에게 권장되는 행동의 예시는 다음과 같지만 이에 국한되지 않습니다: 22 | * 다른 사람에 대한 공감과 친절함을 보여주기 23 | * 서로 다른 의견, 관점, 경험을 존중하기 24 | * 건설적인 피드백을 제공하고 정중하게 수용하기 25 | * 우리의 실수로 인해 영향을 받은 사람들에게 책임이 있음을 인정하고 사과하며, 경험을 통해 교훈 얻기 26 | * 개인뿐만 아니라 전체 커뮤니티를 위해 무엇이 최선인지에 초점 맞추기 27 | * 따뜻하고 포용적인 언어 사용하기 28 | 29 | 참여자에게 금지하는 행동의 예시는 다음과 같지만 이에 국한되지 않습니다: 30 | * 성적인 언어 또는 이미지 사용 31 | * 트롤링, 모욕적이거나 경멸적인 댓글, 개인적 또는 정치적인 공격을 하는 행위 32 | * 모든 형태의 공개적이거나 사적인 괴롭힘 33 | * 타인의 명시적 허가 없이 주소 또는 전자 주소와 같은 타인의 개인 정보를 공개하는 행위 34 | * 폭력, 폭력 위협 또는 타인에게 폭력적인 행동을 하도록 부추기는 행위 35 | * 상대방의 동의 없이 스토킹 또는 미행하는 행위 36 | * 원치 않는 신체적 접촉 37 | * 원치 않는 성적 또는 연애적 관심이나 접근 38 | * 기타 전문적인 환경에서 합리적으로 부적절한 것으로 간주될 수 있는 행위 39 | 40 | 다음과 같은 행위도 금지됩니다: 41 | * 행동 강령 조사와 관련하여 고의로 허위 또는 오해의 소지가 있는 정보를 제공하거나 조사를 의도적으로 조작하는 행위. 42 | * 사건을 신고하거나 목격자로서 사건에 대한 정보를 제공했다는 이유로 보복하는 행위. 43 | 44 | 프로젝트 메인테이너(maintainer)는 본 행동 강령에 부합하지 않는 코멘트, 커밋(commit), 코드, 위키(wiki) 수정, 이슈 및 그 밖의 기여에 대해서 삭제, 수정, 거부할 권한과 책임이 있습니다. 본 행동 강령을 채택함으로써, 프로젝트 메인테이너는 CNCF 프로젝트를 관리하는 모든 상황에 이러한 원칙을 공정하고 일관적으로 적용할 것을 약속해야 합니다. 행동 강령을 따르지 않거나 이행하지 않는 프로젝트 메인테이너는 프로젝트 팀에서 일시적 또는 영구적으로 제명될 수 있습니다. 45 | 46 | ## 보고하기 47 | 48 | 쿠버네티스 커뮤니티에서 발생하는 사건에 대해서는 이메일[conduct@kubernetes.io](mailto:conduct@kubernetes.io)를 통해 [쿠버네티스 행동 강령 위원회](https://git.k8s.io/community/committee-code-of-conduct)에 신고할 수 있습니다. 영업일 기준 3일 이내에 답변을 받으실 수 있습니다. 49 | 50 | 기타 프로젝트 또는 프로젝트와 무관하거나 여러 CNCF 프로젝트에 영향을 미치는 사건에 대해서는 이메일 [conduct@cncf.io](mailto:conduct@cncf.io)를 통해 [CNCF 행동 강령 위원회](https://www.cncf.io/conduct/committee/)에 신고할 수 있습니다. 대안으로, [CNCF 행동 강령 위원회](https://www.cncf.io/conduct/committee/)의 개별 위원에게 연락하여 신고서를 제출할 수도 있습니다. 익명으로 신고하는 방법을 포함하여 신고를 제출하는 방법에 대한 자세한 지침을 알고 싶으시다면 [사건 해결 절차](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md)를 참조하세요. 영업일 기준 3일 이내에 답변을 받으실 수 있습니다. 51 | 52 | 리눅스 재단에서 주최하는 CNCF 행사에서 발생한 사건에 대해서는 이메일 [eventconduct@cncf.io](mailto:eventconduct@cncf.io)로 신고하시기 바랍니다. 53 | 54 | ## 시행 55 | 56 | 신고된 사건을 검토하고 조사하면, 관할권을 가진 CoC 대응팀이 본 행동 강령 및 관련 문서를 바탕으로 적절한 조치를 결정합니다. 57 | 58 | 프로젝트 리더십이 처리하는 행동 강령 사건, CNCF 행동 강령 위원회가 처리하는 사건, 리눅스 재단(이벤트 팀 포함)이 처리하는 사건에 대한 자세한 내용은 [관할권 정책](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md)을 참조하세요. 59 | 60 | ## 개정 61 | 62 | CNCF 헌장에 따라 본 행동 강령의 실질적인 변경은 기술감독위원회의 승인을 받아야 합니다. 63 | 64 | ## 승인 65 | 66 | 본 행동 강령은 기여자 서약([http://contributor-covenant.org](http://contributor-covenant.org/))의 버전 2.0을 적용하였으며, 해당 내용은 이 페이지 [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/)에서 확인할 수 있습니다. 67 | -------------------------------------------------------------------------------- /style-guide.md: -------------------------------------------------------------------------------- 1 | # CNCF Style Guide # 2 | 3 | ## 1. Cloud native and open source ## 4 | 5 | Online and in print media, the phrases "cloud native" and "open source" are written both with and without the hyphen. 6 | [Merriam-Webster](https://www.merriam-webster.com/dictionary/open-source) lists the phrase as "open-source," and the 7 | [Chicago Manual of Style](https://www.chicagomanualofstyle.org/book/ed18/part2/ch07/toc.html) recommends a hyphen in 8 | noun + adjective compounds used as an adjective in front of a noun. 9 | 10 | However, the [Open Source Initiative](https://opensource.org/), established in 1998, does not use a hyphen in 11 | "open source." Likewise, the Cloud Native Computing Foundation does not use a hyphen in "cloud native" in its name. 12 | And the [IEEE Computer Society Style Guide](https://ieeecs-media.computer.org/assets/pdf/2016CSStyleGuide.pdf), 13 | which is maintained by the 72-year-old Computer Society, lists "open source" as the preferred usage. 14 | 15 | We believe that the cloud native aspect of a "cloud native technology" is so integral to its meaning that the entire 16 | phrase serves as a noun. The same can be said for an "open source project." Following this logic, "cloud native" and 17 | "open source" are not compound adjectives that need to be hyphenated, per the Chicago Manual of Style. 18 | 19 | Thus, going forward, for all CNCF publications online and in print, we are establishing "open source" and "cloud native" 20 | as the proper style. 21 | 22 | The words should be lowercase, except in organization names like the Cloud Native Computing Foundation and Open Source 23 | Initiative. Normal capitalization rules apply at the beginning of a sentence and in titles. 24 | 25 | The CNCF Cloud Native [Definition](https://github.com/cncf/toc/blob/main/DEFINITION.md) is available in multiple languages. 26 | 27 | ## 2. Kubernetes ## 28 | 29 | *Etymology:* [κυβερνήτης](https://en.wiktionary.org/wiki/%CE%BA%CF%85%CE%B2%CE%B5%CF%81%CE%BD%CE%AE%CF%84%CE%B7%CF%82), 30 | Greek for helmsman or pilot. Also the root word for cybernetics and governor (which has an important meaning in control 31 | theory). 32 | 33 | *Abbreviation:* K8s (sometimes k8s), a [numeronym](https://en.wikipedia.org/wiki/Numeronym) formed by replacing the 34 | middle of the word ("ubernete") with the number of letters it contains (8). K8s is preferred, as Kubernetes is a proper noun. 35 | 36 | *Unacceptable abbreviations:* K8, which leaves off the "s," and K8S, which gets the capitalization wrong. 37 | 38 | *Pronunciation:* koo-bur-NET-ees. Source: its co-creator [Joe Beda](https://twitter.com/jbeda/status/773368060728057856). 39 | 40 | *Additional notes:* 41 | 42 | 1. Contrary to the pronunciation of Kubernetes, [KubeCon](http://kubecon.io) is pronounced KYOOB-kon. 43 | 2. The canonical pronunciation of kubectl was [established in v1.9](https://github.com/kubernetes/kubernetes/blame/80c75ef19ea37880329a5dfa8fb578d5a8c4263e/CHANGELOG-1.9.md#L550) as "cube-control". 44 | 45 | ## 3. Other CNCF Projects ## 46 | 47 | Different CNCF-hosted projects have preferred capitalization (e.g., containerd, gRPC, KEDA). Please see 48 | [https://www.cncf.io/projects/](https://www.cncf.io/projects/). 49 | 50 | ## 4. Logos ## 51 | 52 | Logos for all CNCF-hosted [projects](https://www.cncf.io/projects/) and programs are available at 53 | [https://github.com/cncf/artwork/](https://github.com/cncf/artwork/). We prepare artwork in 2 formats 54 | (PNG & SVG), 3 layouts -- horizontal (also known as landscape format), stacked (which is closer to square), 55 | and icon (which does not include the name and is square), and 3 versions (color/black/white). So, that's at 56 | least 18 versions of most logos. 57 | 58 | You can find stickers for all projects and t-shirts and hoodies for each CNCF graduated and incubating project 59 | at the CNCF [store](https://store.cncf.io/). 60 | -------------------------------------------------------------------------------- /policies-guidance/allowed-third-party-license-policy.md: -------------------------------------------------------------------------------- 1 | CNCF's IP policy is set forth in the [CNCF charter], section 11. 2 | 3 | CNCF project dependencies that are licensed under Apache-2.0 do not require 4 | further license review or approval, since they are under the same license as 5 | the CNCF project itself. 6 | 7 | The IP policy in the [CNCF charter] allows the CNCF Governing Board to review 8 | and approve other non-Apache-2.0 licenses on an exception basis. 9 | 10 | To streamline this process, licenses for some components are allowed as per 11 | the CNCF Allowlist License Policy (adopted by the CNCF Governing Board on 2018-05-01). 12 | 13 | Components that are not under Apache-2.0, and that do not satisfy the Allowlist License Policy, remain subject to review and exception approval by the Governing Board. 14 | 15 | ## CNCF Allowlist License Policy 16 | 17 | A third-party component under a non-Apache 2.0 license is deemed automatically 18 | approved by the Governing Board for inclusion in a CNCF codebase as an 19 | exception to the CNCF Intellectual Property Policy, if **all** of the following 20 | apply: 21 | 22 | 1. It is fully licensable under the approved licenses set forth below under 23 | [Approved Licenses] (including combinations with Apache-2.0); AND 24 | 25 | 2. It is either (A) stored unmodified in a designated third-party folder, or (B) 26 | not stored in the CNCF project repository and instead retrieved at installation 27 | or build time from the upstream third party repository or package repository; AND 28 | 29 | 3. It has indications of substantial use outside CNCF by satisfying one of the 30 | following: 31 | 32 | 1. the component is part of the applicable programming language’s standard 33 | library; or 34 | 35 | 2. the component was created on Github at least 12 months ago and has at 36 | least 10 stars or 10 forks. 37 | 38 | ### Approved Licenses for Allowlist 39 | 40 | To be approved as “allowlisted,” a third-party component must be fully 41 | licenseable under one or more of the following licenses, and must meet the 42 | other allowlist criteria set forth in the [Allowlist License Policy] above. 43 | 44 | License IDs refer to the [SPDX License List](https://spdx.org/licenses), except 45 | where a URL is specified below for licenses that are not on the SPDX License 46 | List. 47 | 48 | - 0BSD 49 | - BSD-2-Clause 50 | - BSD-2-Clause-FreeBSD 51 | - BSD-3-Clause 52 | - MIT 53 | - MIT-0 54 | - ISC 55 | - OpenSSL 56 | - OpenSSL-standalone 57 | - PSF-2.0 58 | - Python-2.0 59 | - Python-2.0.1 60 | - PostgreSQL 61 | - SSLeay-standalone 62 | - UPL-1.0 63 | - X11 64 | - Zlib 65 | - [Google patent license for Golang](https://golang.org/PATENTS) 66 | 67 | [Allowlist License Policy]: #cncf-allowlist-license-policy 68 | [Approved Licenses]: #approved-licenses-for-allowlist 69 | [CNCF Charter]: https://github.com/cncf/foundation/blob/main/charter.md 70 | 71 | ### Process for applying for an exception 72 | 73 | This outlines the process for applying for an exception to the Intellectual Property policy referenced above. 74 | 75 | - A CNCF project maintainer can [file a request for an exception using the issue template](https://github.com/cncf/foundation/issues/new?template=license-exception-request.yaml). 76 | 77 | Exceptions should be filed by the project using the component - the exception applies to how the component is being used. 78 | 79 | - A staff member will review and add to the [Licensing Exception Board](https://github.com/orgs/cncf/projects/44) 80 | - Staff will work with Legal to create an agenda for the Legal Committee to review and present a recommendation to the Governing Board. 81 | - A vote is called according to the [CNCF Charter](https://github.com/cncf/foundation/blob/main/charter.md). 82 | - If the vote is approved and the resolution passes, Staff will post in the issue, linking to the PR where this has been approved. 83 | - If the vote is not approved, the issue will be closed. 84 | -------------------------------------------------------------------------------- /journey-reports.md: -------------------------------------------------------------------------------- 1 | # Project Journey Report 2 | 3 | ## Overview 4 | 5 | A Project Journey Report is an in-depth analysis created by the CNCF to objectively evaluate the current state of a project and assess the impact CNCF has had on its development and growth through the graduation stage. The report provides a comprehensive overview, including a detailed history of the project, its evolution over time, and a current snapshot of its status. Key metrics such as project velocity, community diversity, and levels of participation will also be included. Projects must be graduated to request a Project Journey Report. 6 | 7 | [Review other Project Journey Reports](https://www.cncf.io/reports?_sft_lf-report-type=project-journey) 8 | 9 | ## What you can expect once you submit your PJR request 10 | 11 | 1. Submit your request and wait for confirmation 12 | 2. CNCF will create a workback plan to share with the maintainers and determine publish date - current turnaround is 6 weeks 13 | 3. Identify correct maintainers (2 to 3) that will review the report 14 | 4. CNCF will set up interview/questionnaire with maintainers as well as end-user contacts for quotes and begin collecting data for the report 15 | 5. Maintainers receive first draft of the report and provide feedback in accordance with the workback plan 16 | 6. Once the report copy is finalized, CNCF will develop the creative draft of the report and initiate the blog drafting with the social team 17 | 7. Report will be published to the CNCF website & blog posting date will be set and shared with the maintainers - CNCF will send over all of the live links 18 | 19 | [Submit your request for a Project Journey Report] - Currently Closed 20 | 21 | *Suggested amount of time between reports is 2 years* 22 | 23 | ### End User Journey Report Submission Process ### 24 | 25 | End User Journey Reports are managed, written and produced by CNCF, in close collaboration with End User Members. 26 | Participants will need to: 27 | **1. Proposal** 28 | 29 | * To participate in an End User Journey Report, submit a [proposal] - Currently Closed 30 | * Complete initial proposal which covers: 31 | * How long have you been using CNCF projects? 32 | * Which projects do you use? 33 | * Has your organization contributed to a project/donated a project? 34 | * Do employees of your organization take an active role in CNCF -- for example, chairing committees, or speaking at KubeCon + CloudNativeCon? 35 | 36 | **2. Review** 37 | 38 | * The CNCF team reviews proposal within 20 working days 39 | * If the proposal meets the criteria, the marketing team reaches out to set up an interview 40 | * If the proposal doesn’t meet the criteria, the CNCF team will provide feedback and the end user is invited to resubmit 41 | 42 | **3. Creation** 43 | 44 | * Nominate 1-2 employees to take part in an hour-long interview 45 | * CNCF writes end user journey report 46 | 47 | **4. Editing** 48 | 49 | * Take part in a follow-up interviews to fact-check and clarify information 50 | * Approve written content 51 | * Approve final designed content 52 | 53 | **5. Publishing** 54 | 55 | * CNCF prepares the end user journey report for publication 56 | * Generally end user journey reports are published within 30 days but the timeframe can vary. The case study team will communicate potential publication dates and/or changes to those dates 57 | * Case study is published to [cncf.io/reports](https://www.cncf.io/reports?_sft_lf-report-type=end-user-journey) 58 | * Promotion cycle begins 59 | 60 | **Sample End User Journey Report: [Adobe](https://www.cncf.io/reports/adobe-end-user-journey-report/)** 61 | 62 | ### Promotion ### 63 | 64 | End User Journey Reports are published on [cncf.io](https://www.cncf.io/) and marketed through social media, blog promotion, and the CNCF newsletter. Participating End Users may be asked to join media interviews or speaking opportunities with CNCF leaders. End users are encouraged to leverage CNCF’s numerous marketing channels to amplify their End User Journey Report. We ask that you share the report on your platforms as well. 65 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-06-23-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | Cloud Native Project Monthly (CNPM) June 2023 2 | June 23, 2023 3 | 4 | This is our Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 5 | 6 | In this edition for June 2023: 7 | ## Upcoming Maintainers' Circle 8 | ## Devstats Affliation 9 | ## TOC Meeting with AdaLogics 10 | ## Boost Your Project with Documentation Advice! 11 | ## Mentoring 12 | ## CNCF Project Summary Table 13 | ## gRPC 14 | 15 | #### 16 | 17 | ## Upcoming Maintainers' Circle 18 | Join us on Wednesday, June 28th at 10 am PT, a new Maintainer's Circle special session with Paris Pittman on defining and managing the roles in your Project. 19 | More details here: https://github.com/cncf/tag-contributor-strategy/tree/main/maintainers-circle#community-management 20 | 21 | ## Devstats Affliation 22 | Ever wondered where Devstats affiliations come from? 23 | 24 | They’re in here: https://github.com/cncf/gitdm and openprofile.dev 25 | These may be useful to you! If you haven’t updated these recently, these affiliations are what Devstats looks for. 26 | 27 | ## TOC Meeting with AdaLogics 28 | If you’re curious about the goals + processes for security audits, the Technical Oversight Meeting for 6/20 might be useful for you! This is a recorded meeting with Adalogics and some project maintainers. 29 | Recording: https://youtu.be/v2v8TuY9Ijc 30 | Presentation: CNCF TOC Meeting 6/20/2023 (https://docs.google.com/presentation/d/16XmBqV7f9t9yIETbDdzJt_Qa0VHSWRFCVXWvfs0Hwec/edit#slide=id.g25ca91f87f_0_0) 31 | 32 | ## Boost Your Project with Documentation Advice! 33 | There’s a new Sheriff in town - maintaining repo access permissions on the CNCF org 34 | When you want to grant access to your project repos to maintainers and collaborators, please submit a pull request to update the config.yaml file in the cncf/people repo. 35 | Sheriff is being used to centralize repo access control for the CNCF org on GitHub. 36 | Sheriff runs once per hour, is launched from a Github Action on cncf/people, and it will undo any changes to repo permissions that are made via a repo's settings.yml file. 37 | Using Sheriff makes it easy for us to review who has access to all community repos in the CNCF org. Sheriff also allows us to structure our teams to reflect team roles and Sheriff teams are cross platform. 38 | 39 | ## Mentoring 40 | Don't miss the next CNCF Tech Docs open office session on June 28, 2023, at 8:00 AM PDT. We're here to answer your questions and guide you in enhancing your project's documentation. 41 | Let's make your project shine even brighter! No RSVP needed. 42 | Just join us on Zoom (https://zoom.us/j/98293716536?pwd=SElSK2FVMkxCbzJidTB1dXJ1TTNsUT09#success) (password: 77777) and check out the agenda doc (https://docs.google.com/document/d/1roexHTLCrErYjNT2NEoRsVnn_YNbQzZ1gyXNK8hXR4Q/edit#heading=h.581dl5s9us63) for topics. We look forward to seeing you there! 43 | 44 | ## Mentoring 45 | LFX Term 02 - 2023 June - August (https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2023/02-Jun-Aug) has kicked off, thanks to all the mentors who are participating (55 of you!). 46 | It’s early yet, but Term 03 - 2023 September - November (https://www.google.com/url?q=https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2023/03-Sep-Nov&sa=D&source=docs&ust=1692652539211219&usg=AOvVaw0NIcxPWGHkMnl_zeVeFPcS) 47 | is open for project proposals—but we're excited to see what you're interested in working on! 48 | 49 | ## CNCF Project Summary Table 50 | A lesser-known part of the CNCF Landscape is the Project Summary Table (https://landscape.cncf.io/summary). Part of the Landscape are fields that allow projects to define both typical and business use cases (https://github.com/cncf/landscape/blob/master/landscape.yml#L188-L231). 51 | 52 | ## gRPC 53 | Don’t miss your chance to join key customers, project leads, and contributors at the upcoming gRCP Conf 2023. Submit your CFP today (https://events.linuxfoundation.org/archive/2020/kubecon-cloudnativecon-north-america/program/cfp/#submit-your-talk)! The CFP closes on Sunday, July 2. 54 | 55 | 56 | Want to contribute to July's newsletter? 57 | Drop a note to projects@cncf.io. 58 | -------------------------------------------------------------------------------- /cncfgroups.md: -------------------------------------------------------------------------------- 1 | ### What are CNCF groups? 2 | 3 | CNCF groups are public long lived groups that do not fall under a specific CNCF project, CNCF [governance](https://github.com/cncf/toc), or a [local CNCF chapter](https://community.cncf.io/). These groups can cut across technologies, geographies, and businesses to address matters that affect CNCF members. They are important forums for working on the issues, beyond technological, transforming the cloud native community. They can have multiple purposes which may include: 4 | 5 | 1. Discussion and sharing issues 6 | 2. Providing feedback 7 | 3. Producing content and assets 8 | 9 | ### List of CNCF groups 10 | 11 | 1. [Telecom User Group](https://github.com/cncf/telecom-user-group) 12 | 2. [Research User Group](https://github.com/cncf/research-user-group) 13 | 3. [Financial Services User Group](https://github.com/cncf/financial-user-group) 14 | 4. [Business Value SubCommittee](https://github.com/cncf/business-value) [charter](https://docs.google.com/document/d/1lMEwmdLHPi7FUh1WVt-kDrk1UKZlV3BykXjlm_iL4Ro/edit?ts=5f74c3e0#heading=h.7ugaugyyy9bv) 15 | 5. Service Mesh User Group [charter](https://docs.google.com/document/d/1jiQnPPXaPS0YG4_l3565lx555v4kqWoxifJXu3-i9Gw/edit) 16 | 6. Cartografos [charter](https://docs.google.com/document/d/1nL_x_APhKKAAxQMIBspXjXaz_sEqMgTm1lWjUxd6HYw/edit?ts=5ffcd705#heading=h.75bkqqx2sglh) 17 | 7. Marketing Committee [charter](https://github.com/cncf/foundation/blob/main/charter.md#10-marketing-committee) 18 | 19 | ### Forming a CNCF Group 20 | 21 | First determine if the group is already covered under a specific CNCF project, CNCF [governance](https://github.com/cncf/toc), or a [local CNCG chapter](https://community.cncf.io/). Next, find a CNCF sponsor. Please reach out to [info@cncf.io](mailto:info@cncf.io) if you want to form a CNCF group, but don’t know who on staff to speak with. Once you have a CNCF sponsor, it is important to find 1-2 other co-chairs to help share the load with you. Reach out to people at [Member companies](https://www.cncf.io/about/members/) in similar areas or look for people that have previously spoken about it at [KubeCon](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/). Your CNCF sponsor may also know other people interested in the group. 22 | 23 | Once you have co-chairs, a charter should be drafted. At a minimum, it should include: 24 | 25 | 1. Name of group 26 | 2. Initial Authors: 27 | 3. Reviewed and contributed to by: 28 | 4. Introduction 29 | 5. Mission 30 | 6. Areas considered in scope 31 | 7. Areas considered out of scope 32 | 8. Roadmap and initial efforts 33 | 9. Operations 34 | 1. Chairs 35 | 2. CNCF sponsor 36 | 3. Communications 37 | 4. Meeting schedule 38 | 39 | Once finalized, make a pull request in this repo with a link to the charter. 40 | 41 | ### Meetings and Organization 42 | 43 | New groups will be hosted on [Cloud Native Community Groups (CNCG)](https://community.cncf.io/). Once your charter has been organized, contact [meetups@cncf.io](mailto:meetups@cncf.io) to set up your chapter. You should also reference the official [Bevy documentation on how to create a chapter](https://help.bevy.com/hc/en-us/articles/1500001546381-Create-a-chapter) for more technical details. CNCG allows organizers to easily manage their communities, including setting up and running meetings, emailing members, and following up with surveys. More information and resources on how run a group can be found [here](https://help.bevylabs.com/). 44 | 45 | If needed a Slack channel, mailing list, and/or Github repo can also be set up to organize discussions. Please work with your CNCF Sponsor to get this set up as needed. 46 | 47 | ### Platform Support 48 | 49 | If you have any technical difficulties with the platform itself, please reach out to the [Bevy platform support](https://help.bevylabs.com/) directly. 50 | 51 | ### Marketing support 52 | 53 | As these groups are under the auspices of the CNCF, they are able to use the multitude of CNCF media channels including [blog](https://github.com/cncf/foundation/blob/main/policies-guidance/blog-guidelines.md), [social media](https://github.com/cncf/foundation/blob/main/policies-guidance/social-guidelines.md), and [online programs](https://github.com/cncf/foundation/blob/main/policies-guidance/online-programs-guidelines.md). Please refer to the individual guidelines for more information. 54 | -------------------------------------------------------------------------------- /code-of-conduct-languages/he.md: -------------------------------------------------------------------------------- 1 | ## קוד ההתנהגות הקהילתי 2 | 3 | כמשתתפים, שותפים ותורמים בקהילת CNCF, ובמטרה לטפח קהילה פתוחה ומקבלת, אנו מתחייבים לכבד את כל האנשים שמשתתפים או תורמים באמצעות דיווח על בעיות, פרסום בקשות לתכונות חדשות, עדכון תיעוד, שליחת בקשות משיכה או תיקונים, השתתפות בכנסים או אירועים, או מעורבות בפעילויות קהילתיות או פרויקטיות אחרות. 4 | 5 | אנו מחויבים להפוך את ההשתתפות בקהילת CNCF לחוויה חופשית מהטרדה עבור כולם, ללא קשר לגיל, גודל גוף, מעמד, מוגבלות, מוצא אתני, רמת ניסיון, מצב משפחתי, מגדר, זהות מגדרית וביטוי מגדרי, מצב נישואין, צבאי או וותק, לאום, מראה אישי, גזע, דת, נטייה מינית, מצב סוציו-אקונומי, שבט, או כל ממד אחר של גיוון. 6 | 7 | ## היקף 8 | 9 | קוד ההתנהגות זה חל: 10 | * בתוך פרויקטים ומרחבים קהילתיים, 11 | * במרחבים אחרים כאשר דבריו או פעולותיו של משתתף קהילת CNCF בודדים מכוונים או נוגעים לפרויקט CNCF, קהילת CNCF או משתתף קהילת CNCF אחר בהקשר של פעילות CNCF. 12 | 13 | ### אירועי CNCF 14 | 15 | אירועי CNCF המופקים על ידי קרן לינוקס עם צוות אירועים מקצועי מנוהלים על ידי קרן לינוקס [קוד ההתנהגות של אירועים](https://events.linuxfoundation.org/code-of-conduct/) הזמין בדף האירוע. זה נועד לשמש בשילוב עם קוד ההתנהגות של CNCF. 16 | 17 | ## הסטנדרטים שלנו 18 | 19 | קהילת CNCF פתוחה, מכילה ומכבדת. לכל חבר בקהילה שלנו יש זכות לכבד את זהותו. 20 | 21 | דוגמאות להתנהגות התורמת לסביבה חיובית כוללות בין היתר: 22 | 23 | * הפגנת אמפתיה ואדיבות כלפי אנשים אחרים 24 | * לכבד דעות שונות, נקודות מבט וחוויות שונות 25 | * לתת ולקבל משוב בונה בצורה חיננית 26 | * לקבל אחריות ולהתנצל בפני מי שנפגע מהטעויות שלנו, וללמוד מהחוויה 27 | * התמקדות במה שהכי טוב לא רק עבורנו כיחידים, אלא עבור הקהילה כולה 28 | * שימוש בשפה מסבירת פנים ומכילה 29 | 30 | דוגמאות להתנהגות בלתי מקובלת כוללות בין היתר: 31 | 32 | * השימוש בשפה או בדימויים מיניים 33 | * הערות מטרילות, מעליבות או גנאי, והתקפות אישיות או פוליטיות 34 | * הטרדה ציבורית או פרטית בכל צורה שהיא 35 | * פרסום מידע פרטי של אחרים, כגון כתובת פיזית או כתובת אימייל, ללא רשותם המפורשת 36 | * אלימות, איומים באלימות או עידוד אחרים לעסוק בהתנהגות אלימה 37 | * הטרה או מעקב אחר מישהו ללא הסכמתו 38 | * מגע פיזי לא רצוי 39 | * תשומת לב או התקדמות מינית או רומנטית לא רצויה 40 | * התנהגות אחרת שיכולה להיחשב כבלתי הולמת בסביבה מקצועית 41 | 42 | גם ההתנהגויות הבאות אסורות: 43 | * מתן מידע שקרי או מטעה ביודעין בקשר לחקירת קוד התנהגות או התעסקות מכוונת אחרת בחקירה. 44 | * נקמה נגד אדם משום שדיווח על תקרית או מסר מידע על תקרית כעד. 45 | 46 | למתחזקי פרויקטים יש את הזכות והאחריות להסיר, לערוך או לדחות הערות, התחייבויות, קוד, עריכות של ויקי, בעיות ותרומות אחרות שאינן מותאמת לקוד התנהגות זה. 47 | על ידי אימוץ קוד התנהגות זה, מתחזקי הפרויקט מתחייבים ליישם באופן הוגן ועקבי את העקרונות הללו בכל היבט 48 | של ניהול פרויקט CNCF. 49 | מתחזקי פרויקטים שאינם פועלים לפי או אוכפים את קוד ההתנהגות עשויים להיות מוסרים באופן זמני או לצמיתות מצוות הפרויקט. 50 | 51 | ## דיווח 52 | 53 | למקרים המתרחשים בקהילת Kubernetes, צור קשר עם [ועדת קוד ההתנהגות של Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) דרך . ניתן לצפות לתגובה תוך שלושה ימי עסקים. 54 | 55 | עבור פרויקטים אחרים, או עבור תקריות שהן אגנוסטיות לפרויקט או להשפיע על פרויקטים מרובים של CNCF, אנא צור קשר עם [ועדת קוד ההתנהגות של CNCF](https://www.cncf.io/conduct/committee/) דרך . לחלופין, תוכל ליצור קשר עם כל אחד מהחברים הפרטיים של [ועדת קוד ההתנהגות של CNCF](https://www.cncf.io/conduct/committee/) כדי להגיש את הדוח שלך. להנחיות מפורטות יותר כיצד להגיש דוח, לרבות כיצד להגיש דוח באופן אנונימי, עיין ב[נהלי פתרון תקריות](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). ניתן לצפות לתגובה תוך שלושה ימי עסקים. 56 | 57 | לתקריות המתרחשות באירוע CNCF המופק על ידי קרן Linux, אנא צור קשר עם . 58 | 59 | ## אכיפה 60 | 61 | לאחר סקירה וחקירה של תקרית מדווחת, צוות התגובה לקוד ההתנהגות האחראי יקבע את הפעולה הנדרשת בהתאם לקוד ההתנהגות ולתיעוד הנלווה לו. 62 | 63 | למידע נוסף על אילו תקריות קוד התנהגות מטופלות על ידי הנהגת הפרויקט, אילו תקריות מטופלות על ידי ועדת קוד ההתנהגות של CNCF, ואילו תקריות מטופלות על ידי קרן הלינוקס (כולל צוות האירועים שלה), עיינו ב[מדיניות הסמכות השיפוטית שלנו](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). 64 | 65 | ## שינויים 66 | 67 | בהתאם לאמנת CNCF, כל שינוי מהותי בקוד התנהגות זה חייב להיות מאושר על ידי ועדת הפיקוח הטכני. 68 | 69 | ## הכרת תודה 70 | 71 | קוד התנהגות זה הותאם בהתאם לאמנת התורמים (http://contributor-covenant.org), גרסה 2.0 הזמינה בכתובת: [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) -------------------------------------------------------------------------------- /copyright-notices.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Ownership of Copyrights in CNCF Project Contributions 4 | 5 | When source code, documentation and other content is contributed to a CNCF 6 | project, the copyrights in those contributions remain owned by the original 7 | copyright holders. 8 | 9 | The copyrights are not _assigned_ to CNCF. Instead, they are _licensed_ for 10 | distribution as part of the project. Whether a project uses the DCO or a CLA, 11 | the original copyright holders retain their copyrights. 12 | 13 | ## Copyright Notices 14 | 15 | CNCF does not require or recommend that every contributor include their 16 | copyright notice in contributed files. [See below for more details on why 17 | not.](#why-not-list-every-copyright-holder) 18 | 19 | Instead, CNCF recommends using a more general statement in a form similar to the 20 | following (where XYZ is the project's name): 21 | 22 | - **Copyright The XYZ Authors.** 23 | - **Copyright The XYZ Contributors.** 24 | - **Copyright Contributors to the XYZ project.** 25 | - **Copyright Contributors to XYZ a Series of LF Projects, LLC.** 26 | 27 | > [!NOTE] 28 | > Use the fourth format if the project has been converted to the [Series LLC model](https://github.com/cncf/foundation/issues/910). 29 | 30 | These statements are intended to communicate the following: 31 | 32 | - the work is copyrighted; 33 | - the contributors of the code licensed it, but retain ownership of their copyrights; and 34 | - it was licensed for distribution as part of the named project. 35 | 36 | By using a common format, the project avoids having to deal with names of 37 | copyright holders, years or ranges of years, and variations on the (c) symbol. 38 | This aims to minimize the burden on developers and maintainers as well as 39 | redistributors of the code. 40 | 41 | ## What if I want my copyright notice included? 42 | 43 | Please note that it is _not wrong_, and it is acceptable, if a contributor 44 | wishes to keep their own copyright notices on their contributions. The above is 45 | a recommended format for ease of use, but is not mandated by CNCF. 46 | 47 | If you are contributing on behalf of your employer, you may wish to discuss with 48 | your legal department about whether they will require you to include a copyright 49 | notice identifying them as the copyright holder in contributions. 50 | 51 | ## What about Third Party Code? 52 | 53 | If a file only contains code that originates from a third party source who 54 | didn't contribute it themselves, then you would _not_ want to add the notices 55 | above. (In a similar vein, you wouldn't add a notice identifying you as the 56 | copyright holder either, if you didn't own it.) Just preserve the existing 57 | copyright and license notices as they are. 58 | 59 | If, however, you add copyrightable content to a pre-existing file from another 60 | project, then at that point you could _add_ a copyright notice similar to the 61 | one above. 62 | 63 | ## Don't Change Someone Else's Notice without their Permission 64 | 65 | You _should not_ change or remove someone else's copyright notice unless they 66 | have expressly permitted you to do so. This includes third parties' notices in 67 | pre-existing code. 68 | 69 | For additional details regarding attribution notices for third party code used 70 | in CNCF projects, see the [CNCF attribution recommendations] document. 71 | 72 | ## Why not list every copyright holder? 73 | 74 | There are several reasons why CNCF doesn't require or recommend trying to list 75 | every copyright holder for contributions to every file: 76 | 77 | - Copyright notices are not mandatory in order for the contributor to retain 78 | ownership of their copyright. 79 | - Copyright notices are rarely kept up to date as a file evolves, resulting in 80 | inaccurate statements. 81 | - Trying to keep notices up to date, or to correct notices that have become 82 | inaccurate, increases the burden on developers without tangible benefit. 83 | - Developers and maintainers often do not want to have to worry about e.g. 84 | whether a minor contribution (such as a typo fix) means that a new copyright 85 | notice should be added. 86 | - Adding many different copyright notices may increase the burden on downstream 87 | distributors, if their license compliance processes involve reproducing 88 | notices. 89 | - The specific individual or legal entity that owns the copyright might not be 90 | known to the contributor; it could be you, your employer, or some other entity. 91 | 92 | [CNCF attribution recommendations]: https://github.com/cncf/foundation/blob/main/policies-guidance/recommendations-for-attribution.md 93 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-11-23- Project Newsletter.md: -------------------------------------------------------------------------------- 1 | 2 | Cloud Native Project Monthly (CNPM) November 2023 3 | November 24, 2023 4 | 5 | In this Edition: 6 | ## Maintainers Survey 2023 H2 7 | ## Community Retro Doc for KubeCon + CloudNativeCon NA 8 | ## Project Opportunities Feedback at KubeCon + CloudNativeCon NA 9 | ## Announcing....... Lightning Round - Security Slam! 10 | ## GitHub Actions: Now with Apple Silicon 11 | ## Upcoming CFP Deadlines 12 | 13 | 14 | #### 15 | 16 | ## 📈Maintainers Survey 2023 H2 17 | A friendly nudge: we're still eagerly awaiting your valuable input! Our survey is open for a limited time, and we'd love to hear from you. Your insights play a crucial role in shaping our path forward. Take a moment to share your thoughts and help us create an even better experience for you. 18 | 19 | [Submit Now](https://www.surveymonkey.com/r/CNCF-Maintainers-Survey-H2-2023) 20 | 21 | ## 🎉 Community Retro Doc for KubeCon + CloudNativeCon NA 22 | Were you at KubeCon+ CloudNativeCon NA 2023? Do you have any feedback to make the event better OR do you want to gush at the Events team? 23 | For each KubeCon + CloudNativeCon, we’ve been collecting community feedback from a subset of folks, but we’d like to open it up to the entire maintainer community. 24 | 25 | [Provide Feedback](https://docs.google.com/document/d/1Bqhwq6-MI18aK6UHdgZiHlIxV232f16G4xWLpRI8TpQ/edit#heading=h.qlbiyi5b6o1m) 26 | 27 | ## 🚨Project Opportunities Feedback at KubeCon + CloudNativeCon NA 28 | Your input matters! We want to ensure our project opportunities at KubeCon + CloudNativeCon fit your needs. Participate in our Project Opportunities Survey and have your say in shaping future initiatives! We welcome you to share your insights and thoughts on potential project offerings for future events. 29 | 30 | [Take the Survey Now](https://community.cncf.io/events/details/cncf-cloud-native-security-slam-presents-2023-security-slam-lightning-round/) 31 | 32 | ## ⚡ Announcing... Lightning Round - Security Slam! 33 | Following the impact of the 2023 Cloud Native Security Slam, the Kubernetes maintainers have scheduled a one-day special event to allow new Kubernetes contributors an easy path to helping commit critical security improvements to Kubernetes. 34 | Whether you are joining for one day or would like to become a recurring contributor, this is a perfect opportunity to learn more about what goes on behind the scenes to make Kubernetes the global digital superpower it has become. 35 | 36 | [View Details](https://community.cncf.io/events/details/cncf-cloud-native-security-slam-presents-2023-security-slam-lightning-round/) 37 | 38 | ## 🍎 GitHub Actions: Now with Apple Silicon! 39 | In case you missed it, exciting news broke this fall regarding projects under the CNCF GitHub Enterprise License. Now, you should have access to the latest GitHub Action Runner type. Check out GitHub's fantastic blog announcement for detailed instructions on setup and more information. 40 | 41 | In the upcoming months, native Linux ARM GitHub Action runners will be available. Keep an eye out for further updates! 42 | 43 | [Read the Blog Post Now](https://github.blog/2023-10-02-introducing-the-new-apple-silicon-powered-m1-macos-larger-runner-for-github-actions/) 44 | 45 | 46 | ## ✍️Upcoming CFP Deadlines: 47 | Here are the upcoming deadlines for CFPs: 48 | - [KubeCon + CloudNativeCon EU](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--#submit-your-talk) - November 26 49 | - [Co-located Events @ KubeCon + CloudNativeCon EU](https://sessionize.com/kccnc-eu-co-located-24?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--) - December 3 50 | - [KCD São Paulo 2024](https://kcd.smapply.io/prog/sp-brazil-cfp/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--)- December 3 51 | - [Dapr Day](https://sessionize.com/Dapr-Day-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--) - January 3 52 | - [KCD Mexico 2024](https://sessionize.com/ccoss-kcdgdl-2024/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--) - January 9 53 | - [KCD Costa Rica 2024](https://sessionize.com/kubernetes-community-day-costa-rica-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--) - January 31 54 | - [KCD Romania 2024](https://sessionize.com/kcd-romania-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--UONy4FTThR5RIO9XmatavbW5dvEym02z9q2lycI-qXJDDC3d-knOY2tTDnP4LTN7yqf--) - January 31 55 | 56 | 57 | Want to contribute to December's newsletter? 58 | [Contribute Today!](projects@cncf.io) 59 | -------------------------------------------------------------------------------- /policies-guidance/agpl-recommendations.md: -------------------------------------------------------------------------------- 1 | # Third Party Dependencies that have been Relicensed to AGPL 2 | 3 | ## Background 4 | 5 | CNCF's IP policy is set forth in the [CNCF charter], section 11. 6 | 7 | Under the IP policy, CNCF projects use Apache-2.0 for their code. The CNCF 8 | Governing Board reviews and approves other non-Apache-2.0 licenses, for 9 | code in the repos or dependencies of CNCF projects, on an exception basis. 10 | 11 | The CNCF Governing Board has previously adopted an [Allowlist License Policy] 12 | that permits most permissively-licensed components to be automatically 13 | approved as exceptions, when used in an unmodified manner. 14 | 15 | However, components under other licenses -- particularly under copyleft-style 16 | licenses -- remain subject to approval by the CNCF Governing Board. This is 17 | not because such licenses are inherently problematic, but rather because 18 | they may add obligations that would not be expected by, or acceptable to, 19 | users of CNCF's projects under Apache-2.0. 20 | 21 | ## Recent changes to dependencies' licenses 22 | 23 | Recently (in early 2021), CNCF projects have discovered that some existing 24 | dependencies they use have been relicensed by their licensors from 25 | Apache-2.0 to the GNU Affero General Public License v3.0, [AGPL-3.0]. 26 | 27 | The AGPL-3.0 license is a free and open source software license. However, 28 | it is a strong copyleft license, which means that when used or distributed 29 | in certain ways, it imposes copyleft obligations that go beyond the more 30 | permissive requirements of Apache-2.0. 31 | 32 | In addition, portions of AGPL-3.0's copyleft obligations apply to contexts 33 | where the AGPL-3.0 software is interacted with through a computer network. 34 | In the context of cloud-native software, this means that copyleft 35 | obligations may come into play under AGPL-3.0 where they would not for 36 | other GPL licenses, where distribution is the primary relevant trigger. 37 | 38 | This can present a problem for CNCF projects, where the license of the 39 | component they depend on was previously aligned with the CNCF project's 40 | own license, but is no longer aligned. 41 | 42 | ## Recommendations 43 | 44 | There are a few approaches that CNCF projects should consider taking, for 45 | dependencies that fall into this category. 46 | 47 | ### Switch to an alternative component 48 | 49 | The project will likely want to evaluate alternative components with 50 | similar functionality, and switch to one that is Apache-2.0 or that has 51 | a permissive license under the [Allowlist License Policy]. 52 | 53 | ### Freeze the component at the version prior to the license change 54 | 55 | As a short-term solution, the project might consider freezing the version 56 | of the component so that it is fixed at the last release prior to the 57 | license change. 58 | 59 | This is unlikely to be tenable as a long-term solution, particularly as 60 | the prior release is presumably unlikely to continue receiving maintenance 61 | updates, security fixes, etc. 62 | 63 | ### Seek an exception from the Governing Board 64 | 65 | If the project requires the now-AGPL-3.0 component as a mandatory 66 | dependency, it can request that the Governing Board grant an exception 67 | to the license policy. 68 | 69 | Please be aware that this is **highly** unlikely to be granted, and that 70 | the Governing Board has (at the time of this writing) not previously 71 | granted any exceptions for components that are under AGPL-3.0. 72 | 73 | If you do seek an exception, you will want to provide information about 74 | the specific component(s) and how they are being used. In particular, 75 | provide details about the boundaries and interactions between the project 76 | code and the third-party component, and whether the component 77 | is mandatory or optional for use with the project. 78 | 79 | The Governing Board may refuse to grant exceptions at its discretion; 80 | however, some of the considerations that the Governing Board might take 81 | into account are as follows: 82 | * if AGPL-3.0 code would be included directly in the source code repo, 83 | this is extremely unlikely to be approved as an exception. 84 | * if use of an AGPL-3.0 component is mandatory to use the CNCF project, 85 | it is highly unlikely to be approved as an exception. 86 | * if the component is an _optional_ run-time dependency, and is not 87 | enabled or incorporated by default, it may be more acceptable as an 88 | exception. 89 | * additionally, if the optional AGPL-3.0 component's licensor has made 90 | available interface tools (such as client libraries) that are under 91 | Apache-2.0 or a similar permissive license, that may also make it more 92 | acceptable as an exception. 93 | 94 | [CNCF Charter]: https://github.com/cncf/foundation/blob/main/charter.md 95 | [Allowlist License Policy]: https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md 96 | [AGPL-3.0]: https://www.gnu.org/licenses/agpl-3.0.en.html 97 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-09-20-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | Cloud Native Project Monthly (CNPM) September 2023 2 | September 20, 2023 3 | 4 | In this Edition: 5 | ## Updates from the Blog 6 | ## Security Slam 7 | ## Project Marketing Feedback Session 8 | ## Exciting News: New Project Event Guidelines! 9 | ## CNCF Annual Survey 10 | ## Upcoming CFP Deadlines 11 | 12 | 13 | #### 14 | 15 | ## 📝Updates from the Blog 16 | Guest writer Riaan Kleinhans shares a story of a journey that starts with a memorable road trip and leads to valuable insights for the open source community. 17 | "Navigating Success: The Power of Roadmaps in Open Source Projects." [Link](https://www.cncf.io/blog/2023/09/14/navigating-success-the-power-of-roadmaps-in-open-source-projects/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--bymN3kW8AUE2ueJ3jU-U2d6HDZKJT1zrnR37Hyz1NyatHC4jXNcYL95fa4ffPL3swNB87) 18 | 19 | Congratulations to all the mentees who have completed the second term of the 2023 CNCF LFX mentoring program, and thank you to all the maintainers and mentors who participated! 20 | “36 CNCF term 2 LFX mentees have successfully completed the program.” [Link](https://www.cncf.io/blog/2023/09/12/36-cncf-term-2-lfx-mentees-have-successfully-completed-the-program/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--bymN3kW8AUE2ueJ3jU-U2d6HDZKJT1zrnR37Hyz1NyatHC4jXNcYL95fa4ffPL3swNB87) 21 | Term 3 is underway, and we are planning our next intake early next year [Link](https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2024/01-Mar-May?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--bymN3kW8AUE2ueJ3jU-U2d6HDZKJT1zrnR37Hyz1NyatHC4jXNcYL95fa4ffPL3swNB87). 22 | 23 | 24 | ## 🔐Security Slam 25 | Join the Security Slam, a 30-day challenge to boost your software supply chain security. Gain access to the Security Slam Library, filled with informative articles and videos. 26 | Exciting success metrics and awards await at the kickoff webinar. 27 | Don't forget, it all leads to a hybrid award ceremony where your achievements will shine. Enhance security, connect with the CNCF community, and be part of this unmissable event! 28 | 29 | Learn More Now: [Link](https://community.cncf.io/cloud-native-security-slam/) 30 | 31 | ## 📆 Project Marketing Feedback Session 32 | Join us on September 26th at 8pm PST for the APAC session or on September 27th at 8 am PST for our NA/EMEA session. 33 | During these sessions, we'll discuss why this feedback is crucial, what aspects work well in our projects, and where we can improve to serve your needs better. 34 | Additionally, we'd love to hear your thoughts on the marketing support that would be most beneficial to you. 35 | Your input will shape the future of our projects, and we can't wait to hear from you. To secure your spot, please register using the following links: 36 | 37 | APAC Session Registration: [Link](https://zoom.us/webinar/register/WN_R0-UJq50Q8Cns4LL2P3LHw?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--bymN3kW8AUE2ueJ3jU-U2d6HDZKJT1zrnR37Hyz1NyatHC4jXNcYL95fa4ffPL3swNB87#/) 38 | NA/EMEA Session Registration: [Link](https://zoom.us/webinar/register/WN__QYzfF4EQiCqNMgdCrvjAA?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--bymN3kW8AUE2ueJ3jU-U2d6HDZKJT1zrnR37Hyz1NyatHC4jXNcYL95fa4ffPL3swNB87#/) 39 | 40 | ## 🌟 Exciting News: New Project Event Guidelines! 41 | Big news! We've just rolled out updated Project Event Guidelines designed to supercharge your community engagement efforts. 42 | Check out the updated guidelines on our website and find quick answers in the FAQ section. 43 | 44 | Learn More Now: [Link](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/cncf-hosted-co-located-events-overview/#submit-a-cncf-project-or-co-located-event-proposal) 45 | 46 | Proposals due for KubeCon Europe 2024 or Open Source Summit North America 2024 - October 2 47 | Notifications for KubeCon Europe or Open Source Summit North America 2024 - Week of October 16 48 | 49 | We're here to support CNCF's growth journey. Reach out to [Link](cncfcolocatedevents@linuxfoundation.org) if you have questions. 50 | 51 | ## 📊 CNCF Annual Survey 52 | In 2022, our Annual Survey with LF Research revealed a rising trend among Web Assembly and the cloud native ecosystem. What will 2023 bring for cloud native adoption and trends? 53 | 54 | Join #TeamCloudNative by sharing your expertise and cloud native journey in the 11th CNCF Annual Survey – tell us how you’re leveraging the cloud native ecosystem and help us to better serve you! 55 | 56 | As a thank you, we’re offering 25% off any CNCF certification for anyone who completes the survey. 57 | 58 | Take the Survey: [Link](https://www.research.net/r/S5BY23R) 59 | 60 | ## ✍️Upcoming CFP Deadlines: 61 | Here are the upcoming deadlines for CFPs: 62 | GitOpsCon EU [Link](https://events.linuxfoundation.org/gitopscon-europe/program/cfp/)- October 4 63 | KubeCon + CloudNativeCon EU 2024 [Link](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/) - November 26 64 | 65 | 66 | Want to contribute to October's newsletter? 67 | Drop a note to [Link](projects@cncf.io). 68 | -------------------------------------------------------------------------------- /policies-guidance/maintainers-election-policy.md: -------------------------------------------------------------------------------- 1 | ## Maintainers Election Policy 2 | 3 | Maintainers of graduated and incubating CNCF-hosted projects elect 2 members of the Governing Board (GB) (see CNCF Charter [section](https://github.com/cncf/foundation/blob/main/charter.md#5-governing-board) 5(c)(ii)(b)) and one member of the Technical Oversight Committee (TOC) (see CNCF Charter [section](https://github.com/cncf/foundation/blob/main/charter.md#6-technical-oversight-committee-toc) 6(b)(iii)). This document specifies the nomination and voting process. 4 | 5 | ## Maintainer Nomination 6 | 7 | To nominate themselves for an open position, a graduated or incubating maintainer needs to send an email to the private list prior to the announced deadline with a maximum 1-page nomination pitch which includes the nominee's name, contact information, and a supporting statement identifying the nominee's experience in CNCF domains and interest in the position. The nominee needs to cc (i.e., copy) 2 other maintainers from 2 different graduated or incubating CNCF projects who each need to group reply endorsing the nomination. The 2 endorsers also need to be employed by different companies than the nominee and each other (i.e., the nominee and endorsers must each work for a different group of Related Companies as defined in the CNCF Charter section 14). It is the nominee’s responsibility to ensure that their nomination and both endorsements are sent prior to the deadline. 8 | 9 | ## Maintainer Voting 10 | 11 | The CNCF GB has defined the following system of “Maintainer Voting”: 12 | 13 | The eligible voters for a maintainer chosen seat are the maintainers of graduated and incubating projects on the date that the election is opened. 14 | 15 | This means that projects in process to move to incubation are not eligible if they have not been announced on the date that the election is opened. 16 | 17 | These project maintainer lists will be determined by the public lists at maintainers.cncf.io. 18 | 19 | Each eligible project maintainer will receive one vote. In order to participate in the election process, maintainers will need to add themselves to the list of active voters. This will occur at the same time as the nomination process and last at least two weeks. 20 | 21 | Votes will occur using Condorcet-IRV. 22 | 23 | ## Developer Representation on the CNCF GB 24 | 25 | The Cloud Native Computing Foundation (CNCF) is a community made up of contributors, vendor companies, end user organizations, academic institutions, and nonprofits. The funding and marketing functions of CNCF are overseen by its Governing Board (GB) while technology decisions are under the purview of the Technical Oversight Committee (TOC). The GB consists of company representatives (17 platinum seats, 3 gold seats, and 3 silver seats) plus the chairperson of the Technical Oversight Committee (TOC) and 2 developer seats. 26 | 27 | One of these developer seats is filled by the Kubernetes Steering Committee. The other seat is elected by the maintainers of the non-Kubernetes, graduated and incubating projects. 28 | 29 | The developer seats are be held for 2 years with an election each year to replace one of the seats. 30 | 31 | ## GB Developer Seat Eligibility 32 | 33 | Current and emeritus members of the Kubernetes Steering Committee are eligible to hold the Kubernetes seat. The Kubernetes Steering Committee will determine its own method for selecting the representative, though CNCF is happy to organize an election for it if requested. Maintainer voting is not used for selecting this seat. 34 | 35 | For the other GB developer seat, the pool of eligible nominees and voters are individuals who are maintainers of at least one graduated or incubating, non-Kubernetes project at the time when nominations are called. The CNCF maintains a [list](https://github.com/cncf/foundation/blob/main/project-maintainers.csv) of project maintainers. The election will be held using the process described in the “Maintainers Election Policy” above, limited to the graduated or incubating non-Kubernetes project maintainers. 36 | 37 | Maintainers who already hold a Governing Board seat are eligible to vote but not to run. The 2 developer seats and the TOC chair are collectively known as Technical Community Representatives and are required to be from different companies (i.e., each must work for a different group of Related Companies as defined in the CNCF Charter section 14). If more than one Technical Community Representative would be from the same group of Related Companies, either at the time of election or from a later job change, they will jointly decide who should step down, or if there is no agreement, random lots shall be drawn. 38 | 39 | If a GB developer seat holder resigns or is forced to leave their seat, the seat will be re-appointed by the original method and for the remainder of the previous term. 40 | 41 | ## TOC Developer Seat Eligibility 42 | 43 | Maintainers of graduated or incubating projects who do not currently hold a TOC seat are eligible to self-nominate for the developer TOC seat. All graduated and incubating maintainers are eligible to vote. 44 | -------------------------------------------------------------------------------- /code-of-conduct-languages/ar.md: -------------------------------------------------------------------------------- 1 |
2 | 3 | ## مدونة قواعد سلوك المجتمع 4 | 5 | بصفتنا مساهمين ومشرفين ومشاركين في مجتمع CNCF، وبهدف تعزيز مجتمع مفتوح يرحب بالجميع، نتعهد باحترام كل الأفراد المشاركين أو المساهمين من خلال الإبلاغ عن المشكلات، أو تقديم طلبات ميزات، أو تحديث الوثائق، أو إرسال طلبات السحب أو الإصلاحات، أو حضور المؤتمرات أو الفعاليات، أو الاشتراك في أنشطة المشروع أو المجتمع الأخرى. 6 | 7 | 8 | نلتزم بجعل المشاركة في مجتمع CNCF تجربة خالية من المضايقات للجميع، بغض النظر عن السن، أو حجم الجسم، أو الانتماء، أو الإعاقة، أو العرقية، أو مستوى الخبرة، أو الحالة العائلية، أو التعبير والهوية الجندرية، أو الموقف من التجنيد، أو حالة الانضمام إلى الجيش أو التقاعد منه، أو الجنسية، أو المظهر الشخصي، أو العرق، أو الديانة، أو التوجه الجنسي، أو الحالة الاجتماعية الاقتصادية، أو العشيرة، أو أي بعد آخر من أبعاد التنوع. 9 | 10 | ## النطاق 11 | 12 | تنطبق مدونة قواعد سلوك المجتمع هذه: 13 | 14 | * داخل مساحات المجتمع والمشروع، 15 | * وفي المساحات الأخرى حيث تكون أفعال أو كلمات مشارك مجتمع CNCF موجهة إلى أو حول مشروع CNCF، أو مجتمع CNCF، أو مشارك آخر في مجتمع CNCF. 16 | 17 | ## فعاليات CNCF 18 | 19 | تتم حوكمة في فعاليات CNCF برعاية Linux Foundation مع طاقم العمل الاحترافي للفعاليات بواسطة مدونة قواعد سلوك الفعاليات من Linux Foundation المتوفرة على صفحة الفعاليات. تم تصميم هذا لاستخدامه مع مدونة قواعد سلوك CNCF. 20 | 21 | ## معاييرنا 22 | 23 | مجتمع CNCF مفتوح ويتسم بالتنوع والاحترام. يتمتع كل عضو في مجتمعنا بالحق في احترام هويته. 24 | 25 | تتضمن الأمثلة على السلوك الذي يعزز بيئة إيجابية على سبيل المثال لا الحصر: 26 | 27 | * إظهار التعاطف والرأفة تجاه الآخرين 28 | * احترام الآراء ووحهات النظر والتجارب المختلفة 29 | * تقديم ملاحظات بناءة وقبولها باحترام 30 | * تحمّل المسؤولبة والاعتذار لمن تأثروا بأخطائنا والتعلم من التجارب 31 | * التركيز على الأفضل ليس للأفراد فقط ولكن للمجتمع ككل 32 | * استخدام لغة ترحيبية وتشجع على الاحتواء 33 | 34 | تتضمن الأمثلة على السلوك غير المقبول على سبيل المثال لا الحصر: 35 | 36 | * استخدام صور أو لغة جنسية 37 | * التعليقات المهينة أو بغرض التصيد، والهجوم بدوافع شخصية أو سياسية 38 | * المضايقات العامة أو الخاصة بأي شكل 39 | * نشر المعلومات الخاصة للأفراد الآخرين مثل عناوين البريد الفعلية أو الإلكترونية بدون إذن صريح 40 | * استخدام العنف أو التهديد بالعنف أو تشجيع الآخرين على تنفيذ سلوكيات عنيفة 41 | * الترصد أو ملاحقة شخص بدون موافقته 42 | * التلامس الجسدي غير المرحب به 43 | * الاهتمام أو المحاولات الرومانسية أو الجنسية غير المرحب بها 44 | * السلوكيات الأخرى التي يمكن اعتبارها منطقيًا غير ملائمة في مكان احترافي 45 | 46 | كما أن السلوكيات التالية محظورة هي الأخرى: 47 | 48 | * تقديم معلومات خاطئة أو مضللة فيما يتعلق بتحقيق تابع لمدونة قواعد السلوك أو التلاعب عن قصد بشكل آخر في تحقيق. 49 | * الانتقام من شخص لأنه أبلغ عن حادث أو قدم معلومات حول حادث كشاهد. 50 | 51 | يتمتع المشرفون على المشروع بحق ومسؤولية إزالة أو تحرير أو رفض التعليقات أو الالتزامات أو التعليمات البرمجية أو تحريرات الموسوعة wiki أو الإصدارات أو التعاونات الأخرى التي لا تلتزم بمدونة قواعد السلوك هذه. باتباع مدونة قواعد السلوك هذه، يلتزم المشرفون على المشروع بتطبيق هذه المبادئ بشكل عادل ومتسق على جميع أوجه إدارة مشروع CNCF. قد تتم إزالة المشرفين على المشروع الذين لا يتبعون مدونة قواعد السلوك بشكل مؤقت أو دائم من فريق المشروع. 52 | 53 | ## الإبلاغ 54 | 55 | بالنسبة إلى الحوادث التي تقع في مجتمع Kubernetes، يمكن التواصل مع لجنة مدونة قواعد سلوك Kubernetes على conduct@kubernetes.io. يمكنك توقع رد خلال ثلاثة أيام عمل. 56 | 57 | بالنسبة إلى المشروعات الأخرى، أو للحوادث غير المرتبطة بمشروع أو تؤثر على عدة مشروعات CNCF، يرجى التواصل مع لجنة مدونة قواعد سلوك CNCF على conduct@cncf.io. أو يمكنك التواصل مع أي من الأفراد أعضاء لجنة مدونة قواعد سلوك CNCF لإرسال بلاغك. لمزيد من المعلومات التفصيلية حول إرسال بلاغ، بما في ذلك كيفية إرسال بلاغ مجهول الهوية، يرجى الاطلاع على إجراءات حل الحوادث. يمكنك توقع رد خلال ثلاثة أيام عمل. 58 | 59 | بالنسبة للحوادث التي حدثت في فعالية CNCF برعاية Linux Foundation، يرجى التواصل على eventconduct@cncf.io. 60 | 61 | ## التنفيذ 62 | 63 | عند مراجعة بلاغ بحادثة والتحقيق به، سيحدد فريق مدونة قواعد السلوك صاحب جهة الاختصاص الإجراء المناسب تبعًا لمدونة قواعد السلوك هذه والوثائق المتعلقة بها. 64 | 65 | لمعرفة المعلومات حول حوادث قواعد مدونة السلوك التي يتعامل معها قادة المشروعات، وحوادث مدونة قواعد السلوك التي تتعامل معها لجنة مدونة قواعد سلوك CNCF، وحوادث مدونة قواعد السلوك التي تتعامل معها Linux Foundation (بما في ذلك فريق الفعاليات)، اطلع على سياسة الاختصاص. 66 | 67 | ## التعديلات 68 | 69 | بما يتفق مع ميثاق CNCF، يجب اعتماد أي تغييرات مهمة على مدونة قواعد السلوك هذه بواسطة لجنة الإشراف التقني. 70 | 71 | ## الإقرارات 72 | 73 | تم اقتباس مدونة قواعد السلوك هذه من Contributor Covenant (http://contributor-covenant.org)، الإصدار 2.0 متوفر على http://contributor-covenant.org/version/2/0/code_of_conduct/ 74 | 75 |
76 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-07-20-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | Cloud Native Project Monthly (CNPM) July 2023 2 | July 20, 2023 3 | 4 | In this Edition 5 | 6 | In this edition for July 2023: 7 | ## Mentoring 8 | ## Etcd Usage Survey 9 | ## GitHub Merge Queues 10 | ## Artifact Hub Expands Artifact Support 11 | ## Boost Your Project with Documentation Advice! 12 | ## Services for CNCF Projects 13 | ## Upcoming Event Info 14 | 15 | 16 | #### 17 | 18 | ## Mentoring 19 | The LFX Mentorship 2023 Term 03, September - November is open for project ideas: 20 | https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2023/03-Sep-Nov 21 | 22 | Project submission and application timeline: 23 | Project proposals due: July 27, 2023 24 | Mentee applications open: Aug 2 - 15, 2023 25 | Application review/admission decisions/HR paperwork: Aug 16 - 29, 2023 26 | 27 | Did you know that previous proposals can be used? If your Google Summer of Code proposal was declined and you didn't participate in LFX Term 2, this is a great way to reuse the content and submit. 28 | 29 | All project levels welcome! Sandbox, Incubating, and Graduated projects can all participate. 30 | 31 | We're looking forward to seeing all the project ideas you're interested in working on! 32 | 33 | ## Etcd Usage Survey 34 | The etcd project wants to hear from you! Please take the Usage Survey (https://www.surveymonkey.com/r/etcdusage23). 35 | Data compiled from the survey will help guide the project’s strategic direction and prioritize work, particularly around support for uses outside of Kubernetes. 36 | 37 | ## GitHub Merge Queues 38 | GitHub Merge Queues are now generally available (https://github.blog/2023-07-12-github-merge-queue-is-generally-available/). 39 | The merge queue workflow allows busy teams to land changes into the main branch more efficiently. 40 | It does this by creating an independent branch of each approved change which is then added to a queue. 41 | As an item is added to the queue it is branched along with the upstream changes that are ahead of that merge in the queue, allowing for continuous merging while enforcing all the status checks. 42 | Watch the video for more (https://www.youtube.com/watch?v=XEZMgohmtts). 43 | 44 | ## Artifact Hub Expands Artifact Support 45 | Artifacthub.io is an indexer of cloud native deployment artifacts. It doesn’t host these artifacts, but allows projects to index their artifacts so that it’s more discoverable by users. 46 | This is handy if you publish your artifacts in multiple registries, or have a collection that you’d like to recommend to your users. 47 | Each entry also includes a social integration card so that you can embed the information in your README or website. 48 | 49 | Over the past year Artifact Hub has gained support for more than just container images. 50 | You can also register Helm charts and plugins, Falco configurations, Open Policy Agent (OPA) and Gatekeeper policies, OLM operators, Tinkerbell actions, kubectl plugins, Tekton tasks and pipelines, KEDA scalers, CoreDNS plugins, Keptn integrations, container images, Kubewarden policies, Kyverno policies, Knative client, Backstage plugins, Argo templates and KubeArmor policies. 51 | 52 | ## Boost Your Project with Documentation Advice! 53 | Don't miss the next CNCF Tech Docs open office session on Wednesday July 26, 2023, at 8:00 AM PDT. 54 | We're here to answer your questions and guide you in enhancing your project's documentation. 55 | No RSVP needed. Learn how we can work together to make your project shine by joining the Zoom 9https://zoom.us/j/98293716536?pwd=SElSK2FVMkxCbzJidTB1dXJ1TTNsUT09#success) (password: 77777) and check out the agenda doc (https://docs.google.com/document/d/1roexHTLCrErYjNT2NEoRsVnn_YNbQzZ1gyXNK8hXR4Q/edit#heading=h.mp4al549hr04) for topics. We look forward to seeing you there! 56 | 57 | ## Services for CNCF Projects 58 | Curious about how CNCF supports projects? Ask no further! Check out the link at: https://www.cncf.io/services-for-projects/ 59 | For any service requests, or ideas for additional support we can provide, please swing by https://servicedesk.cncf.io and let us know. 60 | 61 | ## Upcoming Event Info 62 | KubeCon + CloudNativeCon NA 2023 - Project Opportunities 63 | November 6-9 - Chicago, IL 64 | Calling all Maintainers from graduated, incubating, and sandbox projects, along with CNCF TAGs and SIGs chairs! We are thrilled to invite you to participate in project opportunities at KubeCon + CloudNativeCon North America 2023. 65 | This is a fantastic opportunity to showcase your projects and actively contribute to the vibrant Cloud Native community. 66 | Learn More [(https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/program/project-opportunities/)] 67 | 68 | Space is limited 69 | Requests will be based on hierarchy, and we may only be able to accept some requests. 70 | Deadlines 71 | Project Updates on Keynotes Stage Video: Thursday, August 10 72 | Submission for Project Opportunities Interest Form: Friday, August 18 73 | 74 | Notifications 75 | Project Meeting + In-Person Kiosk: Wednesday, August 23 76 | Maintainer Track: Monday, August 28 77 | Questions? Please don’t hesitate to reach out to kmatienzo@linuxfoundation.org 78 | 79 | Upcoming CFP Deadlines: 80 | IstioCon - July 23 81 | KCD Austria - July 30 82 | CNCF-hosted Co-located events @ KubeCon NA - August 6 83 | KCD El Salvador - August 11 84 | KCD Sri Lanka - August 28 85 | KCD Texas - August 30 86 | KCD Denmark - September 14 87 | 88 | 89 | Want to contribute to August's newsletter? 90 | Drop a note to projects@cncf.io. 91 | -------------------------------------------------------------------------------- /policies-guidance/case-study-guidelines.md: -------------------------------------------------------------------------------- 1 | # CNCF End User Stories Guidelines # 2 | 3 | ## Overview ## 4 | 5 | You’ve got great case studies. We want our ecosystem (and beyond) to hear about the impact CNCF projects and cloud native technologies are having on your business. They are also a valuable resource for organizations considering adopting cloud native technologies and helping showcase participating CNCF organizations as leaders in their field. 6 | 7 | **There are a number of ways you can participate in the case study program. Please see further information and eligibility criteria below** 8 | 9 | [Written case study](https://marketingform.cncf.io) 10 | * Open to any end user (CNCF member or non-member companies that use, but don’t sell cloud native technologies) organization working with a * CNCF incubating or graduated project 11 | * CNCF members can provide a case study centered on your customer use case with details about how you helped with the implementation 12 | * All case studies must demonstrate at least one tangible business impact of CNCF incubating or graduated projects 13 | 14 | [Online Programs](https://github.com/cncf/foundation/blob/main/policies-guidance/online-programs-guidelines.md) – CNCF Member organizations can also submit a case study webinar. 15 | 16 | 17 | ## Ensure maximum engagement. Review the guidelines below to optimize your case study. ## 18 | 19 | ### Tips for Getting Started & Engagement ### 20 | 21 | * Simple and concise is the way to go 22 | * Less is more – 750 words or less is optimal, but no more than 1,000 23 | * Bullets 24 | * break up long paragraphs of text 25 | * help highlight key points, successes, and metrics 26 | * Section headers 27 | * Clear, results-oriented headline, section headers (instead of stating Challenge, Solution, Results): 28 | * Add interest 29 | * Provide context for the section (i.e. takeaways) 30 | * Help with SEO 31 | * Tip: ChatGPT is great for help 32 | * Visuals and architecture diagrams (when applicable) add interest and help tell your story 33 | * Ensure they are hi-res 34 | * Feature individual voices 35 | * Please use the active voice in CNCF case studies. More information on active vs passive voices can be [found here](https://www.grammarly.com/blog/active-vs-passive-voice/) 36 | * Conversational and honest: avoid jargon-heavy corporate speak 37 | * All CNCF publications use "open source" and "cloud native" as the proper style 38 | * User-centric: highlight the real-world experience of engineers or decision-makers 39 | * Outcome-driven: focus on measurable impacts and lessons learned 40 | * Mention contributions, bug reports, or participation in working groups or KubeCon and other relevant meetups, KCDs, events, and talks. 41 | * Each CNCF project has a different style for capitalization. Make sure you use the correct one by 42 | * Referencing the [graduated and incubating project listing](https://www.cncf.io/projects/%5d) 43 | * Tell the full journey. It’s OK to include challenges or roadblocks—this adds authenticity and relatability 44 | * Invite readers to reach out, explore a GitHub repo, or learn more about the project 45 | 46 | 47 | 48 | ### Be Sure to Provide ### 49 | 50 | * Company Name & Logo & Logos of referenced projects 51 | * PNG OR SVG 52 | * [Logos for all CNCF-hosted projects and programs](https://github.com/cncf/artwork/) 53 | * Challenges 54 | * Example: Fragmented Legacy Systems, Data Silos, Lack of Interoperability, Dynamic Evolving Requirements 55 | * Industry 56 | * Location 57 | * Cloud type(s) 58 | * Product Type 59 | * CNCF Projects Used 60 | * Bullet point list of Metrics for “By the numbers” infographic 61 | 62 | 63 | ### What to Include ### 64 | 65 | * Note: All case studies must demonstrate at least one tangible business impact of CNCF incubating or graduated projects 66 | * Title & Summary 67 | * Use a clear, results-oriented headline 68 | * Example–“How [Company] Reduced Deployment Time by 70% with [CNCF Project]” 69 | * Include a 2–3 sentence executive summary with key outcomes 70 | * Company Overview - briefly introduce the company: size, industry, mission, and digital strategy focus 71 | * Challenges 72 | * Describe specific technical or business problems and measurable goals 73 | * Solution–detail the solution with an emphasis on: 74 | * Why CNCF/cloud native tools were chosen 75 | * Architecture diagrams, if applicable 76 | * Phases of adoption (e.g., pilot → scale) 77 | * Results 78 | * Quantifiable improvements (time saved, costs reduced, performance gains) 79 | * Developer productivity and team morale 80 | * Before/after comparisons or metrics 81 | * Key lessons learned and future plans (if applicable) 82 | * Future Plans 83 | * Upcoming initiatives or deeper integration with CNCF technologies 84 | * Potential for community contributions or open sourcing 85 | * At least one quote must be included 86 | * From someone who worked on or with the project - engineers, SREs, or product leads help humanize the story 87 | 88 | 89 | ### How to Submit ### 90 | 91 | * Fill out the [submission form](https://form.asana.com/?k=Ufi_ZE31X3EAKMTiplIEcA&d=9283783873717) 92 | * The CNCF team reviews proposals and provides any feedback within 20 working days 93 | * Finalized case studies will be added to the [CNCF case study page](https://www.cncf.io/case-studies/) on CNCF.io and considered for promotion across CNCF marketing outlets such as the CNCF newsletter, social, and slack channels 94 | * NOTE: Refer to the tips, what to provide, and what to include above for a streamlined process 95 | -------------------------------------------------------------------------------- /code-of-conduct-languages/fa.md: -------------------------------------------------------------------------------- 1 |
2 | 3 | ## منشور اخلاقی انجمن 4 | 5 | به‌عنوان پدیدآورنده، مسئول نگهداری و شرکت‌کننده در جامعه CNCF، و به‌منظور ایجاد یک جامعه باز و پذیرا، متعهد می‌شویم که به همه افرادی که از طریق گزارش‌دهی مشکلات، پست درخواست‌های ویژگی، به‌روزرسانی اسناد، ارسال پچ‌ها یا درخواست‌های دریافت تغییرات، شرکت در کنفرانس‌ها یا رویدادها، یا شرکت در سایر فعالیت‌های اجتماعی یا پروژه‌ای مشارکت یا همکاری می‌کنند، احترام بگذاریم. 6 | 7 | متعهد هستیم که صرف نظر از سن، اندازه بدن، طبقه، ناتوانی، قومیت، سطح تجربه، وضعیت خانوادگی، جنسیت، هویت و بیان جنسیت، وضعیت تأهل، وضعیت خدمت نظامی یا جانبازی، ملیت، ظاهر شخصی، نژاد، مذهب، گرایش جنسی، وضعیت اجتماعی-اقتصادی، قبیله یا هر بعد دیگری از تنوع، مشارکت در جامعه CNCF را به تجربه‌ای بدون آزار و اذیت برای همه تبدیل کنیم. 8 | 9 | ### حوزه 10 | 11 | این منشور اخلاقی برای موارد زیر اعمال می‌شود: 12 | * در پروژه و فضاهای انجمن، 13 | * در فضاهای دیگر زمانی که سخنان یا اقدامات یک شرکت‌کننده در جامعه CNCF به یک پروژه CNCF، انجمن CNCF یا یکی دیگر از شرکت‌کنندگان در جامعه CNCF مربوط شود یا درباره آن باشد. 14 | 15 | ### رویدادهای CNCF 16 | 17 | رویدادهای CNCF که توسط بنیاد لینوکس و با کارکنان رویدادهای حرفه‌ای تولید می‌شوند، تحت کنترل منشور اخلاقی رویدادهای بنیاد لینوکس هستند که در صفحه رویداد در دسترس قرار دارد. این سند به‌نحوی طراحی شده است که در کنار «منشور اخلاقی CNCF» استفاده شود. 18 | 19 | ### استانداردهای ما 20 | 21 | جامعه CNCF باز، همه‌پذیر و احترام‌گذار است. همه اعضای جامعه ما از این حق برخوردار هستند که به هویتشان احترام گذاشته شود. 22 | 23 | مثال رفتارهایی که در ایجاد محیط مثبت نقش دارند شامل موارد زیر است اما محدود به آن‌ها نیست: 24 | * نشان دادن همدلی و مهربانی نسبت به افراد دیگر 25 | * احترام گذاشتن به نظرات، دیدگاه‌ها و تجربیات متفاوت 26 | * ارائه و پذیرش مؤدبانه بازخوردهای سازنده 27 | * پذیرش مسئولیت و پوزش طلبیدن از افراد متأثر از اشتباهات شما و یادگیری از تجربیات 28 | * تمرکز بر آنچه که نه تنها برای ما به‌عنوان افراد حقیقی، بلکه برای کل انجمن بهترین است 29 | * استفاده از زبان خوشایند و مرسوم 30 | 31 | مثال رفتارهای غیرقابل قبول شامل موارد زیر است اما محدود به آن‌ها نیست: 32 | * استفاده از تصویرسازی یا زبان جنسی 33 | * مزاحمت اینترنتی، نظرات توهین‌آمیز یا تحقیرآمیز و حملات شخصی یا سیاسی 34 | * هر شکلی از آراز و اذیت عمومی یا خصوصی 35 | * انتشار اطلاعات شخصی دیگران، برای مثال آدرس ایمیل یا نشانی پستی، بدون مجوز صریح آن‌ها 36 | * خشونت، خشونت تهدیدآمیز یا تشویق دیگران به مشارکت در رفتارهای خشونت‌آمیز 37 | * پاییدن یا دنبال کردن فردی بدون رضایت او 38 | * تماس فیزیکی ناخواسته 39 | * توجه یا تلاش برای رابطه جنسی یا عاشقانه ناخواسته 40 | * رفتارهای دیگری که ممکن است به‌طور منطقی در محیط حرفه‌ای نامناسب به‌نظر برسند 41 | 42 | رفتارهای زیر نیز ممنوع هستند: 43 | * ارائه آگاهانه اطلاعات نادرست یا گمراه‌کننده در ارتباط با تحقیقات «منشور اخلاقی» یا به هر نحو دیگری، دستکاری عمدی در تحقیقات. 44 | * انتقام‌جویی از شخصی به‌دلیل گزارش حادثه یا ارائه اطلاعات درباره یک حادثه به‌عنوان شاهد. 45 | 46 | حق و مسئولیت حذف، ویرایش یا رد نظرات، تعهدات، کدهای ویکی، نسخه‌ها، مسائل و سایر مشارکت‌هایی که با این «منشور اخلاقی» مطابقت ندارند، برعهده مسئولان نگهداری پروژه است. با پذیرفتن این «منشور اخلاقی»، مسئولان نگهداری پروژه خود را متعهد می‌کنند که به‌طور منصفانه و مداوم این اصول را در تمامی حنبه‌های مدیریت یک پروژه CNCF به‌کار بگیرند. مسئولان نگهداری پروژه که از «منشور اخلاقی» پیروی نمی‌کنند یا آن‌ها را اجرا نمی‌کنند، ممکن است به‌طور موقت یا دائم از تیم پروژه حذف شوند. 47 | 48 | ### گزارش‌دهی 49 | 50 | برای حوادثی که در انجمن Kubernetes رخ می‌دهد، با کمیته منشور اخلاقی Kubernetes از طریق conduct@kubernetes.io تماس بگیرید. می‌توانید ظرف سه روز کاری منتظر پاسخ باشید. 51 | 52 | برای پروژه‌های دیگر یا حوادثی که ضد پروژه هستند یا بر چند پروژه CNCF تأثیر می‌گذارند، لطفاً با کمیته منشور اخلاقی CNCF از طریق conduct@cncf.io تماس بگیرید. یا، می‌توانید با اعضای حقیقی کمیته منشور اخلاقی CNCF تماس بگیرید تا گزارشتان را ارسال کنید. برای دستورالعمل‌های دقیق‌تر درباره نحوه ارسال گزارش، از جمله نحوه ارسال ناشناس گزارش، لطفاً به رویه‌های حل‌وفصل حادثه ما بروید. می‌توانید ظرف سه روز کاری منتظر پاسخ باشید. 53 | 54 | برای حوادثی که در رویداد CNCF تولیدشده توسط بنیاد لینوکس رخ می‌دهند، لطفاً با eventconduct@cncf.io تماس بگیرید. 55 | 56 | ### اجرا 57 | 58 | پس از مرور و بررسی یک حادثه گزارش‌شده، تیم امداد CoC که صلاحیت قضایی دارد، تعیین خواهد کرد که چه اقدامی بر اساس این «منشور اخلاقی» و اسناد مربوطه مناسب هستند. 59 | 60 | برای اطلاع از اینکه کدام حوادث «منشور اخلاقی» توسط رهبر پروژه مدیریت می‌شوند، کدام حوادث توسط «کمیته منشور اخلاقی CNCF» مدیریت می‌شوند، و کدام رویدادها توسط بنیاد لینوکس (از جمله تیم رویدادهای آن) مدیریت می‌شوند، به خط‌مشی صلاحیت قضایی بروید. 61 | 62 | ### اصلاحیه‌ها 63 | 64 | مطابق با اساسنامه CNCF، هرگونه تغییر اساسی در این «منشور اخلاقی» باید توسط کمیته نظارت فنی تایید شود. 65 | 66 | ### تقدیر و تشکر 67 | 68 | این «منشور اخلاقی» از «پیمان پدیدآورندگان» (http://contributor-covenant.org) اقتباس شده است که نسخه ۲.۰ در http://contributor-covenant.org/version/2/0/code_of_conduct/ در دسترس است 69 | 70 |
71 | -------------------------------------------------------------------------------- /legal-committee-charter.md: -------------------------------------------------------------------------------- 1 | # CNCF Legal Committee Charter 2 | 3 | (a) The responsibilities of the Legal Committee include making recommendations to the Governing Board in response to questions submitted to the Legal Committee by the Governing Board. For clarity, the Legal Committee does not represent CNCF and does not have an attorney-client relationship with CNCF. 4 | 5 | (b) Participation on the Legal Committee is optional. The voting members of the Legal Committee will consist of attorney representatives from Platinum, Gold, and Silver Members who have appointed or elected seats on the Governing Board. Governing Board members appointed by such Platinum, Gold, and Silver Member companies who wish to participate on the Legal Committee may do so together with any attorney representative of their company. Additionally, the Governing Board may designate one or more Governing Board members to attend Legal Committee meetings as non-voting liaison observers. 6 | 7 | (c) In the event that the attorney representative appointed by an eligible Member company is unable to attend a Legal Committee meeting, the Member company may send an alternate attorney representative to that meeting which alternate representative may participate in voting. 8 | 9 | (d) Decisions will be made based on consensus whenever practicable. If, however, any decision requires a vote to move forward, attorney representatives of the Member companies participating in the Legal Committee will vote on a one vote per Member company basis. Actions and recommendations of the Legal Committee may be approved by the absence of sustained objection or an affirmative vote of a simple majority. Abstentions will be excluded from the denominator for purposes of determining whether a majority has voted affirmatively; in other words, an action will be approved when the number of “FOR” votes exceeds the number of “AGAINST” votes. 10 | 11 | (e) Except where a different quorum requirement is set forth in this charter, quorum for any vote shall require attendance or participation by at least fifty percent (50%) of active voting members of the Legal Committee. For purposes of calculating quorum for any meeting or vote, a committee member shall be deemed “active” if they or an alternate designated by their company have attended any meeting or participated in any vote (including the then-current meeting or vote) during the prior six (6) months. Any member who is not active shall be excluded from the denominator for purposes of calculating quorum. “Abstain” votes shall be counted as attendance or participation for purposes of determining quorum and determining whether a member is active or inactive. 12 | 13 | (f) Legal Committee members shall be provided with notice of the date and time and proposed agenda of a regular meeting at least fourteen (14) calendar days in advance of the meeting. If a vote will be held at the meeting, the matter to be voted upon must be included in the agenda for the meeting. In the event the Governing Board determines it is necessary to call an emergency meeting of the Legal Committee, at least five (5) calendar days notice of the date and time and proposed agenda for the meeting shall be provided, and Legal Committee members will be given the option to vote either at the emergency meeting or by email or electronic ballot. 14 | 15 | (g) Subject to the other requirements in this charter, voting may be conducted (i) during a meeting that complies with the notice requirements of paragraph (f) of this charter; (ii) by email, (iii) by written or electronic ballot; or (iv) a combination of the foregoing. Votes cast at a duly called meeting, even if attendance at the meeting is less than a quorum, may be combined with votes cast by email or electronic ballot before or after the meeting. 16 | 17 | (h) Voting on license exceptions to the “IP Policy” section of the CNCF Charter may take place with or without a meeting. If such voting takes place entirely by email or electronic ballot without a meeting, the deadline for voting shall be not less than fourteen (14) calendar days after the vote is first solicited. If the votes on the matter (excluding abstentions) are unanimous and no legal committee member requests a meeting or objects to voting without a meeting, affirmative votes (excluding abstentions) from at least three (3) committee members shall constitute quorum; otherwise, the standard quorum requirements of paragraph (e) shall apply to a vote conducted without a meeting in accordance with this paragraph (h). 18 | 19 | (i) For all matters other than license exceptions to the “IP Policy” section of the CNCF Charter, a meeting that complies with the notice requirements of paragraph (f) of this charter shall be held to discuss the matter. 20 | 21 | (j) If a vote is conducted at a meeting that meets the notice requirements of paragraph (f) of this charter but a quorum of at least fifty percent (50%) of active voting members is not present at the meeting, additional votes may be solicited after the meeting, and the deadline for submitting additional votes by email or electronic ballot shall be not less than seven (7) calendar days after the meeting in the case of a non-emergency meeting, and not less than four (4) calendar days after the meeting in the case of an emergency meeting. For any vote on license exceptions to the “IP Policy” section of the CNCF Charter conducted in accordance with the procedures set forth in this paragraph (j), quorum shall be reduced so that attendance at the meeting or participation in the vote by at least three (3) members of the Legal Committee (including abstentions) shall constitute quorum. 22 | 23 | **Approval and Revision History** 24 | 25 | Approved by the CNCF Governing Board on March 30, 2023 26 | 27 | Amended by the CNCF Governing Board on July 16, 2024 28 | -------------------------------------------------------------------------------- /code-of-conduct-languages/cs.md: -------------------------------------------------------------------------------- 1 | 2 | ## Kodex chování komunity 3 | 4 | Jako přispěvatelé, správci a účastníci komunity CNCF se v zájmu podpory otevřené a laskavé komunity zavazujeme respektovat všechny lidi, kteří se účastní nebo přispívají hlášením problémů, odesíláním žádostí o funkce, aktualizací dokumentace, odesíláním návrhů na sloučení sady změn nebo záplat, účastí na konferencích nebo akcích nebo zapojením do jiných aktivit komunity nebo projektu. 5 | 6 | Jsme zavázáni k tomu, aby účast všech lidí v komunitě CNCF probíhala bez jakéhokoli druhu obtěžování, bez ohledu na věk, velikost, kastu, hendikep, etnickou příslušnost, úroveň zkušeností, rodinný stav, pohlaví, genderovou identitu nebo vyjádření, manželský stav, vojenský status nebo status veterána, národnost, vzhled, rasu, náboženství, sexuální orientaci, socioekonomický status, kmenovou příslušnost nebo jakýkoli jiný rozměr diverzity. 7 | 8 | ## Rozsah 9 | 10 | Tento kodex chování platí: 11 | 12 | * v prostorech rozsahu projektu a komunity, 13 | * v dalších prostorech, kdy jsou slova nebo činy jednotlivého účastníka komunity CNCF cíleny na projekt CNCF, komunitu CNCF nebo jiného účastníka komunity CNCF nebo se jich týkají. 14 | 15 | ## Akce CNCF 16 | 17 | Akce CNCF, které produkuje Linux Foundation s profesionály najatými na akce, řídí [Kodex chování na akcích](https://events.linuxfoundation.org/code-of-conduct/) Linux Foundation dostupný na stránce akce. Je navržen tak, aby se používal ve spojení s Kodexem chování CNCF. 18 | 19 | ## Naše normy 20 | 21 | Komunita CNCF je otevřená, inkluzivní a zdvořilá. Každý člen komunity má právo, aby byla respektována jeho identita. 22 | 23 | Mezi příklady chování, které přispívá k pozitivnímu prostředí, patří mimo jiné: 24 | 25 | * Projevování empatie a laskavosti vůči ostatním lidem 26 | * Respekt k jiným názorům, úhlům pohledu a zkušenostem 27 | * Poskytování a kultivované přijímání konstruktivní zpětné vazby 28 | * Přijímání odpovědnosti a omluva těm, na které mají vliv naše chyby, a poučení se z této zkušenosti 29 | * Soustředění se na to, co je nejlepší nejen pro nás jako jednotlivce, ale pro celou komunitu 30 | * Používání laskavého a inkluzivního jazyka 31 | 32 | Mezi příklady nepřijatelného chování patří mimo jiné: 33 | 34 | * Používání sexualizovaného jazyka nebo obrázků 35 | * Trolling, urážlivé nebo hanlivé komentáře a osobní nebo politické útoky 36 | * Veřejné nebo soukromé obtěžování v jakékoli formě 37 | * Zveřejňování osobních informací jiných lidí, jako je fyzická nebo e-mailová adresa, pokud vám to vysloveně nepovolí 38 | * Násilí, vyhrožování násilím nebo podněcování ostatních k tomu, aby se zapojili do násilného chování 39 | * Stalking nebo sledování někoho bez jeho souhlasu 40 | * Nevítaný fyzický kontakt 41 | * Nevítaný sexuální nebo romantický zájem nebo návrhy 42 | * Jiné chování, které by mohlo být oprávněně pokládáno za nevhodné v profesionálním prostředí 43 | 44 | Navíc je zakázáno i toto chování: 45 | 46 | * Poskytování vědomě nesprávných nebo zavádějících informací ve spojení s vyšetřováním souvisejícím s Kodexem chování nebo jiné úmyslné zasahování do vyšetřování. 47 | * Protiopatření proti osobě, která nahlásila incident nebo poskytla informace o incidentu jako svědek. 48 | 49 | Správci projektu mají právo a odpovědnost odstranit, upravit nebo odmítnout komentáře, závazky, kód, úpravy na wikipedii, problémy a další příspěvky, které nejsou v souladu s tímto Kodexem chování. Přijetím tohoto Kodexu chování se správci projektu zavazují, že budou spravedlivě a konzistentně aplikovat tyto principy na každý aspekt správy projektu CNCF. Správci projektu, kteří se neřídí Kodexem chování nebo jeho dodržování neprosazují, mohou být dočasně nebo trvale vyloučeni z projektového týmu. 50 | 51 | ## Hlášení událostí 52 | 53 | Pro incidenty v komunitě Kubernetes kontaktujte [Výbor pro Kodex chování Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) na adrese [conduct@kubernetes.io](mailto:conduct@kubernetes.io). Odpověď můžete očekávat do tří pracovních dnů. 54 | 55 | Pro jiné projekty nebo pro incidenty, které jsou vůči projektu agnostické nebo mají vliv na více projektů CNCF, prosím kontaktujte [Výbor pro Kodex chování CNCF](https://www.cncf.io/conduct/committee/) prostřednictvím [conduct@cncf.io](mailto:conduct@cncf.io). Případně můžete kontaktovat kohokoliv z jednotlivých členů [Výboru pro Kodex chování CNCF](https://www.cncf.io/conduct/committee/) a odeslat svou zprávu. Podrobnější pokyny k tomu, jak odeslat zprávu, včetně toho, jak ji odeslat anonymně, viz naše [Postupy řešení incidentů](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). Odpověď můžete očekávat do tří pracovních dnů. 56 | 57 | V případě incidentů, ke kterým dojde na akci CNCF produkované prostřednictvím Linux Foundation, prosím kontaktujte [eventconduct@cncf.io](mailto:conduct@cncf.io). 58 | 59 | ## Prosazování 60 | 61 | Po posouzení a vyšetřování nahlášeného incidentu tým odezvy Kodexu chování v příslušné jurisdikci určí, jaká je odpovídající akce, na základě tohoto Kodexu chování a jeho související dokumentace. 62 | 63 | Pro informace o tom, které incidenty související s Kodexem chování řeší vedení projektu, které incidenty řeší Výbor pro Kodex chování CNCF a které incidenty řeší Linux Foundation (včetně jejích týmů pro akce), viz naše [Zásady jurisdikce](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). 64 | 65 | ## Dodatky 66 | 67 | Abychom byli v souladu s Chartou CNCF, jakékoli podstatné změny tohoto Kodexu chování musí schválit Výbor pro technický dohled. 68 | 69 | ## Poděkování 70 | 71 | Tento Kodex chování je adaptací ze smlouvy o přispěvatelích ([http://contributor-covenant.org](http://contributor-covenant.org/)), verze 2.0 dostupné na [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) 72 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-05-24-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | Cloud Native Project Monthly (CNPM) May 2023 2 | May 24, 2023 3 | 4 | This is our Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 5 | 6 | 7 | In this edition for May 2023: 8 | ## Grafana Labs 9 | ## Maintainers' Survey 10 | ## Maintainers' Circle 11 | ## Sheriff + Your Access on the CNCF GitHub 12 | ## ServiceDesk: Your Portal to Project Support 13 | ## Devstats Profile 14 | ## TechDocs 15 | ## Mentoring 16 | 17 | #### 18 | 19 | ## Grafana Labs 20 | Grafana Labs is happy to offer sponsored [Grafana Cloud Pro](https://grafana.com/products/cloud/) 21 | for all Linux Foundation and CNCF projects. For all Incubating and Graduated projects who need it, we are also happy to discuss increased sponsorship levels. 22 | 23 | Grafana Cloud Pro offers a self-service way to store metrics, logs, and traces - and more. With ready-made integrations for many popular tools and use cases, OnCall and Incidents for incident management, k6 for load testing and API contract validation, 24 | Pyroscope for profiles, and Faro for real end user monitoring, projects can get full-stack observability in one holistic package. For more information, drop an email to community@grafana.com! 25 | 26 | ## Maintainers' Survey 27 | We've opened the CNCF maintainers survey for the first half of 2023, now available here: 28 | http://maintainers-survey.cncf.io/ 29 | 30 | We've also changed the questions on the survey to highlight some of the areas that we'd like your feedback on. We'll be publishing the survey data, minus any personally identifying information, at the end of this survey round. 31 | 32 | We'll be closing this survey at the end of May, deadline is May 31st. 33 | 34 | ## Maintianers' Circle 35 | In this session, join Nate W., co-chair of the CNCF mentoring working group, as he shares the power and impact of these programs in shaping open-source projects. 36 | Then hear Lee, a seasoned CNCF mentor, share his insights, experiences, and highlights from his mentorship journey within the CNCF. 37 | Whether you’re a seasoned maintainer, a new contributor, or just interested in open source, this session promises to help you understand how mentoring can help your project grow contributors. 38 | Don’t miss this opportunity to learn, connect, and grow with your peers. 39 | 40 | May 30th, 2023 @ 9:00am PDT / 4:00pm GMT 41 | Maintainers Circle CNCF mentoring 42 | 43 | ## Sherriff + Your Access on the CNCF GitHub 44 | There’s a new Sheriff in town - maintaining repo access permissions on the CNCF org 45 | When you want to grant access to your project repos to maintainers and collaborators, please submit a pull request to update the config.yaml file in the cncf/people repo. 46 | Sheriff is being used to centralize repo access control for the CNCF org on GitHub. 47 | Sheriff runs once per hour, is launched from a Github Action on cncf/people, and it will undo any changes to repo permissions that are made via a repo's settings.yml file. 48 | Using Sheriff makes it easy for us to review who has access to all community repos in the CNCF org. Sheriff also allows us to structure our teams to reflect team roles and Sheriff teams are cross platform. 49 | 50 | ## ServiceDesk: Your Portal to Project Support 51 | A project can have a lot of different requests for, or questions of, the CNCF. To try and consolidate these, we want to remind everyone that https://servicedesk.cncf.io/ exists for any and all project needs. 52 | By asking questions or raising concerns through Service Desk, it means if someone on the team is out, someone else can pick up an urgent request. 53 | As an added bonus, there’s now email support for interacting with ServiceDesk tickets (similar to using email with GitHub). Yes! Servicedesk will now pick up your emails! 54 | You can update an open ticket by replying to the email notification you receive from the Service Desk. Your reply will be added to the ticket as a comment and will be easily picked up by the team. 55 | 56 | In other Service Desk news, we have added a bot that will move a request to a Pending state if a request has been in Waiting for Customer state for 90 days or more if you want to keep the request open, update the ticket and let us know. 57 | 58 | ## Devstats Profile 59 | Ever wondered where Devstats affiliations come from? 60 | They’re in here: https://github.com/cncf/gitdm 61 | If you haven’t updated it in awhile, it might be good to take a look at. 62 | 63 | ## TechDocs 64 | On the last Wednesday of each month, the TechDocs team hosts Open Office Hours for anyone to drop in with questions about technical documentation or how our team can help your project. 65 | Our next session will be on May 31, 2023, at 8:00 AM PDT. You can find details on how to join us on the public calendar (https://tockify.com/cncf.public.events/detail/433/1685545200000?startms=1682899200000). 66 | Hope to see you there! 67 | 68 | ## Mentoring 69 | The CNCF has had 14 projects selected for the Google Summer of Code 2023 program! Thanks to all the participating projects and mentors. Congratulations to Flux and WasmEdge, who have been selected as participants in Google's Season of Docs program. 70 | 71 | LFX Mentoring 72 | Term 01 has just been completed; thanks to everyone who participated. We had over 75 mentors across 28 CNCF projects working with 60 mentees. 73 | Term 02 - 2023 June - August (https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2023/02-Jun-Aug) is now in the mentee selection phase. 74 | Term 03 - 2023 September - November (https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2023/03-Sep-Nov) is open for project proposals -- We're excited to see what you're interested in working on! 75 | 76 | Want to contribute to June's newsletter? 77 | Drop a note to projects@cncf.io. 78 | -------------------------------------------------------------------------------- /documents/project-newsletter/2023-02-22-ProjectNewsletter.md: -------------------------------------------------------------------------------- 1 | # Cloud Native Project Monthly (CNPM) Feb 2023 2 | # February 22, 2023 3 | 4 | Welcome into a new year! 5 | This is our new Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 6 | 7 | Happy February! (We made it!) 8 | This is our new Projects update, this will go out once a month letting CNCF maintainers know of upcoming deadlines, outreach or other useful things going on in the wider community of CNCF. 9 | 10 | In this edition for February 2023 - 11 | ## Mentorship 12 | ## TechDocs 13 | ## Kubernetes Registry Deprecation: k8s.gcr.io => registry.k8s.io 14 | ## Does your project need mainframe resources? 15 | ## Elekto? GitVote? Project voting tools! 16 | ## CNCF GitHub Org Housekeeping 17 | ## Project-meetings.cncf.io now open 18 | ## KubeCon Hotels 19 | 20 | ---- 21 | 22 | ## Mentorship 23 | 24 | Google Season of Docs 25 | The CNCF is applying to participate in Google Season of Docs as an org this year, and we’ve made a call for proposals. If your project needs documentation help, this is a great opportunity to bring a writer on board! 26 | 27 | Google Summer of Code 28 | Interest has been high for project participation in GSoC, we’ve had a lot of proposals, thanks everyone! We should know if the CNCF has been accepted as an organization by Feb 22. We’ll make any announcements and updates on the cncf/mentoring discussion board. 29 | 30 | LFX Mentorship 31 | Applications for Term 01 have just closed, and projects are now making their mentee selections. 32 | 33 | We’ve also published the timelines for the next two terms of the LFX Mentorship program. If you have proposals, please feel free to open a PR and submit! These are a great alternative to GSoC if your proposal wasn’t accepted. 34 | Term 02 - 2023 June - August 35 | Term 03 - 2023 September - November 36 | 37 | ## TechDocs 38 | 39 | Open office hours 40 | On the last Wednesday of each month, the TechDocs team hosts Open Office Hours for anyone to drop in with questions about technical documentation. Our next session will be March 29, 2023 at 8:00AM PDT. You can find details on how to join us on the public calendar. Hope to see you there! 41 | 42 | ## Kubernetes Registry Deprecation: k8s.gcr.io => registry.k8s.io 43 | 44 | In an effort to reduce reliance on Google and reduce cloud spend, the Kubernetes Project is [migrating all references of k8s.gcr.io to registry.k8s.io](https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/). The old URL, which is referenced across the Cloud Native ecosystem, will be [frozen beginning in April](https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/). 45 | 46 | Please check this [GH Issue](https://github.com/kubernetes/k8s.io/issues/4780) to see if your project may be affected. 47 | 48 | ## Does your project need a mainframe? 49 | 50 | The Open Mainframe Project (a sibling foundation to the CNCF) recently reached out to the CNCF to see if any projects have a need for mainframe resources for CI testing or building. If your project has any interest in these resources, please reach out to jeefy@linuxfoundation.org 51 | 52 | #### Elekto? GitVote? Project voting tools! 53 | 54 | The Cloud Native Way is often distributed, and (much like etcd) some form of quorum must be established. In support of this, we have some tools your project might be able to use! 55 | 56 | Does your project run elections for things like a steering committee or TOC? If so, check out https://elekto.dev/ – a Cloud Native way to run elections inspired by the long-running CIVS project. 57 | 58 | Ever want to have structured voting within a GitHub Issue? How about a PR Check that prevents merging without a 2/3rds majority vote? You can do all of that with GitVote. 59 | 60 | Both of these projects are open source and built with love by fellow Cloud Native Community members, so please take a look and feel free to file issues or add feature requests! 61 | 62 | #### CNCF GitHub Org Housekeeping 63 | 64 | Recently, the CNCF GItHub Org has begun using Sheriff, an OSS project created by the folks over at ElectronJS, to manage people-related resources (GitHub and Slack to start). What does this mean? 65 | For better or worse, Yet Another YAML File. (YAY…F) – Adding folks to GitHub Teams and repo access is managed through a new file in the cncf/people repository 66 | You can now programmatically create Slack User Groups via changes to said file 67 | Soon, you will be able to automatically receive access to various resources (Service Desk, Equinix, etc.) and mailing lists as we build plugins for Sheriff. 68 | A lot more self service, and a lot less ServiceDesk tickets for Maintainer updates 69 | 70 | Short term, this might cause some headaches as we all get used to this pattern. That said, this is a huge win in terms of sustainability and optimization of processes for us all. 71 | 72 | For any questions or additional ideas for automation, reach out to jeefy@linuxfoundation.org or file an issue in cncf/sheriff 73 | 74 | ## Project-meetings.cncf.io now open 75 | 76 | One of the benefits of a CNCF Project is being able to get time on the CNCF’s calendar to discuss issues, concerns, or ideas your project has. To better execute on this offering, we’ve set up a Calendly to enable scheduling time with us! 77 | 78 | Our door is always open, so feel free to schedule as needed! 79 | https://project-meetings.cncf.io 80 | Note: When requesting, give us an idea of your discussion topics so we can ensure the right CNCF folks are in the room! 81 | 82 | Ideally we’d like to hear from each of you at least once a year, so we may start reaching out to check on the weather in your project. :) 83 | 84 | ## KubeCon Hotels 85 | 86 | We encourage you to book your hotel for KubeCon + CloudNativeCon Amsterdam quickly - a few hotels listed still have availability. The room blocks end March 30, 2023. 87 | 88 | -------------------------------------------------------------------------------- /code-of-conduct-languages/bn.md: -------------------------------------------------------------------------------- 1 | ## CNCF কমিউনিটি কোড অফ কন্ডাক্ট (CNCF Community Code of Conduct) v1.3 2 | 3 | ### কমিউনিটি কোড অফ কন্ডাক্ট (Contributor Code of Conduct) 4 | 5 | CNCF কমিউনিটির অবদানকারী, রক্ষণাবেক্ষণকারী এবং অংশগ্রহণকারী হিসাবে, এবং একটি উন্মুক্ত এবং একটি উন্মুক্ত 6 | এবং স্বাগতম জানানো কমিউনিটিতে গড়ে তোলার স্বার্থে, যে সমস্ত লোক অংশগ্রহণ করে বা অবদান রেখে সমস্যাগুলি রিপোর্ট করা, 7 | ফিচারগুলো অনুরোধ পোস্ট করা, ডকুমেন্টেশন আপডেট করা, পুল অনুরোধ বা প্যাচ জমা দেওয়া, কনফারেন্স বা ইভেন্টে যোগদান করা, 8 | বা অন্যান্য কমিউনিটি বা প্রকল্পের কার্যকলাপে জড়িত থাকার মাধ্যমে তাদের সকলকে আমরা সম্মান করার অঙ্গীকার করি। 9 | 10 | আমরা বয়স, শরীরের আকার, বর্ণ, অক্ষমতা, জাতিগততা, অভিজ্ঞতার স্তর, পারিবারিক অবস্থা, লিঙ্গ, লিঙ্গ পরিচয় এবং অভিব্যক্তি, বৈবাহিক অবস্থা, সামরিক বা প্রবীণ অবস্থা, জাতীয়তা, ব্যক্তিগত চেহারা, জাতি, ধর্ম, যৌন দৃষ্টিভঙ্গি, আর্থ-সামাজিক অবস্থা, উপজাতি বা বৈচিত্র্যের অন্য কোনও মাত্রা নির্বিশেষে প্রত্যেকের জন্য CNCF কমিউনিটিয়ের অংশগ্রহণকে একটি হয়রানি-মুক্ত অভিজ্ঞতা তৈরি করতে প্রতিশ্রুতিবদ্ধ। 11 | 12 | ## সুযোগ (Scope) 13 | 14 | এই আচরণবিধি প্রযোজ্য: 15 | 16 | * প্রকল্প এবং কমিউনিটির স্থানগুলির মধ্যে, 17 | * অন্যান্য স্থানগুলিতে যখন কোনও পৃথক CNCF কমিউনিটির অংশগ্রহণকারীর কথা বা ক্রিয়াগুলি কোনও CNCF প্রকল্প, CNCF কমিউনিটি বা অন্য কোনও CNCF কমিউনিটির অংশগ্রহণকারীর দিকে পরিচালিত হয় 18 | 19 | ### CNCF ইভেন্টস (CNCF Events) 20 | 21 | পেশাদার ইভেন্ট কর্মীদের সাথে লিনাক্স ফাউন্ডেশন দ্বারা উত্পাদিত CNCF ইভেন্টগুলি ইভেন্ট পৃষ্ঠায় উপলব্ধ লিনাক্স ফাউন্ডেশন [ইভেন্টস কোড অফ কন্ডাক্ট] () দ্বারা পরিচালিত হয়। এটি CNCF আচরণবিধির সাথে একত্রে ব্যবহার করার জন্য ডিজাইন করা হয়েছে। 22 | 23 | ## আমাদের মান (Our Standards) 24 | 25 | CNCF কমিউনিটি উন্মুক্ত, অন্তর্ভুক্তিমূলক এবং শ্রদ্ধাশীল। আমাদের কমিউনিটির প্রতিটি সদস্যের তাদের পরিচয়কে সম্মান করার অধিকার রয়েছে। 26 | 27 | ইতিবাচক পরিবেশে অবদান রাখে এমন আচরণের উদাহরণগুলির মধ্যে রয়েছে তবে সীমাবদ্ধ নয়: 28 | 29 | * অন্যান্য মানুষের প্রতি সহানুভূতি এবং দয়া প্রদর্শন করা 30 | * ভিন্ন মতামত, দৃষ্টিভঙ্গি এবং অভিজ্ঞতার প্রতি শ্রদ্ধাশীল হওয়া 31 | * গঠনমূলক প্রতিক্রিয়া দেওয়া এবং সদয়ভাবে গ্রহণ করা 32 | * দায় স্বীকার করা এবং আমাদের ভুলের দ্বারা ক্ষতিগ্রস্থদের কাছে ক্ষমা চাওয়া, 33 | এবং অভিজ্ঞতা থেকে শিখা 34 | * যা কেবল ব্যক্তি হিসাবে আমাদের জন্য নয়, সামগ্রিক কমিউনিটির জন্য সর্বোত্তম সেদিকে 35 | মনোনিবেশ করা 36 | * স্বাগত এবং অন্তর্ভুক্তিমূলক ভাষা ব্যবহার করা 37 | 38 | অগ্রহণযোগ্য আচরণের উদাহরণগুলির মধ্যে রয়েছে তবে সীমাবদ্ধ নয়: 39 | 40 | * যৌন ভাষা বা চিত্রাবলীর ব্যবহার 41 | * ট্রলিং, অপমানজনক বা অবমাননাকর মন্তব্য এবং ব্যক্তিগত বা রাজনৈতিক আক্রমণ 42 | * যে কোনও রূপে পাবলিক বা প্রাইভেট হয়রানি 43 | * অন্যদের ব্যক্তিগত তথ্য প্রকাশ, যেমন তাদের স্পষ্ট অনুমতি ছাড়া 44 | প্রকৃত বা ইমেল ঠিকানা প্রকাশ করা 45 | * সহিংসতা, সহিংসতার হুমকি দেওয়া বা অন্যকে হিংসাত্মক আচরণে জড়িত হতে উত্সাহিত করা 46 | * কারও সম্মতি ছাড়াই অনুসরণ করা বা অনুসরণ করা 47 | * অবাঞ্ছিত শারীরিক যোগাযোগ 48 | * অবাঞ্ছিত যৌন বা রোমান্টিক মনোযোগ বা অগ্রগতি 49 | * অন্যান্য আচরণ যা পেশাদার পরিবেশে যুক্তিসঙ্গতভাবে অনুপযুক্ত বলে 50 | বিবেচিত হতে পারে 51 | 52 | নিম্নলিখিত আচরণগুলিও নিষিদ্ধ: 53 | 54 | * আচরণবিধির তদন্তের সাথে সম্পর্কিত জেনেশুনে মিথ্যা বা বিভ্রান্তিকর তথ্য সরবরাহ করা বা অন্যথায় ইচ্ছাকৃতভাবে তদন্তে হস্তক্ষেপ করা। 55 | * কোনও ব্যক্তির বিরুদ্ধে প্রতিশোধ নেওয়া কারণ তারা কোনও ঘটনা রিপোর্ট করেছে বা সাক্ষী হিসাবে কোনও ঘটনা সম্পর্কে তথ্য সরবরাহ করেছে। 56 | 57 | প্রকল্প রক্ষণাবেক্ষণকারীদের কমেন্ট, কমিট, কোড, উইকি এডিট, ইস্যু এবং অন্যান্য অবদান যা এই আচরণবিধির সাথে সামঞ্জস্যপূর্ণ নয় তা অপসারণ, এডিট বা প্রত্যাখ্যান করার অধিকার এবং দায়িত্ব রয়েছে। 58 | এই আচরণবিধি গ্রহণ করে, প্রকল্প রক্ষণাবেক্ষণকারীরা একটি CNCF প্রকল্প পরিচালনার প্রতিটি ক্ষেত্রে এই নীতিগুলি ন্যায্য এবং ধারাবাহিকভাবে প্রয়োগ 59 | করার জন্য প্রতিশ্রুতিবদ্ধ। 60 | প্রকল্প রক্ষণাবেক্ষণকারীরা যারা আচরণবিধি অনুসরণ বা প্রয়োগ করে না তাদের প্রকল্প দল থেকে অস্থায়ীভাবে বা স্থায়ীভাবে অপসারণ করা যেতে পারে। 61 | 62 | ## প্রতিবেদন (Reporting) 63 | 64 | কুবারনেটিস কমিউনিটির মধ্যে ঘটে যাওয়া ঘটনাগুলির জন্য, মাধ্যমে [কুবারনেটিস কোড অফ কন্ডাক্ট কমিটি](https://git.k8s.io/community/committee-code-of-conduct) এর সাথে যোগাযোগ করুন। আপনি তিন কার্যদিবসের মধ্যে একটি প্রতিক্রিয়া আশা করতে পারেন। 65 | 66 | অন্যান্য প্রকল্পের জন্য, বা প্রকল্প-অজ্ঞেয়বাদী বা একাধিক CNCF প্রকল্পকে প্রভাবিত করে এমন ঘটনাগুলির জন্য, দয়া করে এর মাধ্যমে [CNCF কোড অফ কন্ডাক্ট কমিটি](https://www.cncf.io/conduct/committee/) এর সাথে যোগাযোগ করুন। বিকল্পভাবে, আপনি আপনার প্রতিবেদন জমা দেওয়ার জন্য [CNCF কোড অফ কন্ডাক্ট কমিটি](https://www.cncf.io/conduct/committee/) এর যে কোনও স্বতন্ত্র সদস্যের সাথে যোগাযোগ করতে পারেন। বেনামে কীভাবে রিপোর্ট জমা দিতে হয়, সেই সহ কীভাবে রিপোর্ট জমা দিতে হয়, সেই বিষয়ে আরও বিস্তারিত নির্দেশাবলীর জন্য অনুগ্রহ করে আমাদের [ইনসিডেন্ট রেজোলিউশন প্রসিডিউরস](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md) দেখুন। আপনি তিন কার্যদিবসের মধ্যে একটি প্রতিক্রিয়া আশা করতে পারেন। 67 | 68 | লিনাক্স ফাউন্ডেশন দ্বারা উত্পাদিত CNCF ইভেন্টে ঘটে যাওয়া ঘটনাগুলির জন্য, দয়া করে সাথে যোগাযোগ করুন। 69 | 70 | ## প্রয়োগ (Enforcement) 71 | 72 | একটি রিপোর্ট করা ঘটনার পর্যালোচনা ও তদন্তের পরে, সিওসি প্রতিক্রিয়া দল যার এখতিয়ার রয়েছে তারা এই আচরণবিধি এবং এর সম্পর্কিত ডকুমেন্টেশনের ভিত্তিতে কোন পদক্ষেপটি উপযুক্ত তা নির্ধারণ করবে। 73 | 74 | কোন আচরণবিধির ঘটনাগুলি প্রকল্প নেতৃত্ব দ্বারা পরিচালিত হয়, কোন ঘটনাগুলি CNCF কোড অফ কন্ডাক্ট কমিটি দ্বারা পরিচালিত হয় এবং কোন ঘটনাগুলি লিনাক্স ফাউন্ডেশন (এর ইভেন্ট টিম সহ) দ্বারা পরিচালিত হয় সে সম্পর্কে তথ্যের জন্য আমাদের [এখতিয়ার নীতি](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md) দেখুন। 75 | 76 | ## সংশোধনী (Amendments) 77 | 78 | CNCF সনদের সাথে সামঞ্জস্যপূর্ণ, এই আচরণবিধিতে যে কোনও উল্লেখযোগ্য পরিবর্তন অবশ্যই প্রযুক্তিগত তদারকি কমিটি দ্বারা অনুমোদিত হতে হবে। 79 | 80 | ## স্বীকারোক্তি (Acknowledgements) 81 | 82 | এই আচরণবিধিটি অবদানকারী চুক্তি থেকে অভিযোজিত 83 | (http://contributor-covenant.org), সংস্করণ 2.0 এখানে উপলব্ধ 84 | http://contributor-covenant.org/version/2/0/code_of_conduct/ 85 | -------------------------------------------------------------------------------- /policies-guidance/online-programs-guidelines.md: -------------------------------------------------------------------------------- 1 | # CNCF Online Programs Guidelines v1.0 # 2 | 3 | ## Overview ## 4 | 5 | Formerly known as the CNCF webinar program, CNCF online programs are offered to the community to provide education about open source cloud native technologies. Online programs include on-demand, livestream, and live webinars that are offered by members, CNCF incubating and graduated projects, and CNCF Ambassadors. 6 | 7 | Please note: We are unable to share leads due to the Linux Foundation privacy policy. Additionally, when booking dates for your online programs we cannot publish events concurrent weeks in a row. Please allow for at least two weeks in between bookings to ensure the maximum benefit is achieved for each of your events. 8 | 9 | ## Publishing schedule ## 10 | 11 | Live webinars and Livestreams are hosted on Tuesdays or Wednesdays at 10am PT once per month. 12 | 13 | On-demand webinars premiere on Thursdays. 14 | 15 | ## Who can participate in CNCF Online Programs ## 16 | 17 | Members 18 | * Platinum members are eligible for 3 activities per quarter including live webinar, on-demand webinar, and a livestream. 19 | * Gold members are eligible for 3 activities per quarter including on-demand webinar or livestream (Only 1 can be livestream, you get to choose.) 20 | * Silver members are eligible for 2 activities per quarter including on-demand webinars and livestreams. (Only 1 can be livestream, you get to choose.) 21 | * End user supporter members cannot hold a webinar. 22 | * CNCF Member webinars will have “member webinar” in the YouTube description. 23 | * All livestreams and webinars (live or on-demand) make it to a YouTube playlist on the [CNCF YouTube channel](https://www.youtube.com/@cncf). 24 | 25 | Projects 26 | * Graduated and incubating projects can participate in our online programs via livestream. These livestreams can demonstrate release features and details or provide a project update. 27 | * Sandbox projects cannot host a livestream. 28 | * CNCF project webinars will have "Project webinar" in the YouTube description. 29 | 30 | Ambassadors 31 | * CNCF Ambassadors can hold a webinar via livestream as it fits their schedule. 32 | * CNCF Ambassador webinars will have "Ambassador webinar" in the YouTube description. 33 | 34 | ## Online programs type definitions ## 35 | 36 | * Live webinars 37 | * Only offered to Platinum members with 1 slot/month 38 | * Day of webinar - 15 minute soundcheck 39 | * Premiere date - Tuesdays or Wednesdays at 10am PT 40 | * On-demand webinars 41 | * Members submit their own pre-recorded content and it will be assigned a publish date based on the editorial calendar. Content cannot be from previous KubeCon + CloudNativeCons. 42 | * Premiere date - Thursdays 43 | * Livestream option 44 | * Streaming from Restream and will broadcast to YouTubeLive and LinkedIn Live - recordings uploaded to CNCF YouTube channel under Online Programs playlist 45 | * Content must be live coding/demo/panel discussions - no presentations with slides, no product pitches 46 | * We will require a high level outline to be provided including any demos you will present one week prior to the event 47 | * CNCF Ambassador will join the stream as co-host 48 | * Premiere date - Tuesdays and Wednesdays (2 per week) 49 | 50 | 51 | ## Online Programs content guidelines ## 52 | * Webinar topics should be comparable to what would be accepted in a KubeCon + CloudNativeCon talk. 53 | * Webinars and Youtube playlist submissions are great for overviews, 101s, best practices, or other content that you want to present in a specific structure 54 | * Livestreams are best for interactive content like experimenting with new features or building something from scratch with mistakes along the way 55 | * Any platforms, tools, or technologies you are describing must be open source. 56 | * Online programs are not limited to English language only. If you would like to submit an online program to be presented in another language, please submit all information in the booking tool in the language it will be presented in (does not need to be translated to English). The title of the program is the only item that needs to be in dual languages. Both translations will appear on our sites. 57 | * Not allowed: 58 | * Sales or marketing pitches 59 | * Unlicensed or potentially closed-source technologies 60 | * Webinars should not be promotional. 61 | * It is NOT okay to mislead or misrepresent features of CNCF projects. 62 | * All Online Programs are subject to [the CNCF Code of Conduct](https://www.cncf.io/conduct/). 63 | 64 | Members can add a CTA (Call to Action) at the end of their webinar or livestream on where to get more information. 65 | Examples: 66 | * Share contact info of speaker - twitter, slack, email 67 | * Links to company websites 68 | * Links to projects websites or Github 69 | * Can advertise if they are hiring and who to contact if interested 70 | 71 | Note: This is not a link to a CNCF website or form on the CNCF website. 72 | 73 | ## Submit to participate in online programs + deadlines ## 74 | 75 | If you are a CNCF member and eligible to participate in our online programs, [please submit your request here](http://marketingform.cncf.io/). We are always accepting submissions and will get in touch with you once your submission is received and to discuss next steps for scheduling. Please note the following will also be due upon submission: 76 | * Live webinar slides 77 | * On-demand webinar slides and recording 78 | * Livestreams: High level outline of talk including live demos 79 | * Notes for all submissions: 80 | * Your event will *not* be published and promoted on cncf.io until you have submitted your title and abstract 81 | * Character limit for titles is 81 82 | * Character limit for abstract is 10,000 83 | * Please submit your title, abstract, speaker bios, speaker titles and speaker headshots upon submission 84 | 85 | ### If we do not receive all neccessary documents and assets upon submission, your online program is subject to postponement 86 | -------------------------------------------------------------------------------- /policies-guidance/social-guidelines.md: -------------------------------------------------------------------------------- 1 | # CNCF Social Media Guidelines 2 | 3 | This document covers the social media guidelines for the use of the CNCF Twitter channel and the CNCF project Twitter channels. 4 | 5 | CNCF manages multiple project handles. These guidelines apply to all CNCF project channels, regardless of who manages. 6 | 7 | ## CNCF Project Twitter handles 8 | ### Objectives 9 | The objectives of project social media: 10 | * Share project news, roadmap updates, news releases 11 | * Report on performance and security updates 12 | * Educate on project updates 13 | * Share information on how-tos, demos, etc that are valuable to the community 14 | * Build awareness for the project 15 | * Drive engagement and participate in the project 16 | 17 | 18 | ### Strategy and Guidelines 19 | * Keep messages positive and uplifting, consistent with the values and principles of CNCF 20 | * Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means. 21 | * Share content across social media channels that benefit the ecosystem as a whole 22 | * Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused 23 | * Engage with the community through retweets and sharing of community content. 24 | * Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, cloud native-specific Meetups, etc. 25 | * CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website. 26 | * Social posts from member company handles and/or vendor channels cannot be shared. 27 | * RTs are limited to news outlet handles, project handles + personal handles. 28 | * Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing. 29 | * Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole. 30 | 31 | 32 | ### Images & Videos 33 | Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.” 34 | 35 | 36 | ## @cloudnativefdn Twitter handle 37 | ### Objectives 38 | The objectives of CNCF social media: 39 | * Advance topics and conversations that are relevant to and beneficial for the cloud native community 40 | * Continue building positive affinity for CNCF projects among key influencers and throughout cloud native community 41 | * Drive engagement and participation in CNCF projects 42 | 43 | ### Themes and Topics 44 | Informational, engaging, and ecosystem-focused content: 45 | * CNCF projects 46 | * CNCF end user community 47 | * Contributor / SIG blog posts 48 | * Cloud native ecosystem 49 | * CNCF event information and deadlines (i.e. CFP) 50 | * Technical topics such as containers, microservices, serverless, and DevOps 51 | * Industry vertical topics such as AI, Serverless, Edge, and IoT 52 | * Informational: Tutorials, editorials, news stories. Items that help connect the dots for our community 53 | * Thought leadership: insights, perspectives, learnings, and experiences 54 | 55 | ### Strategy 56 | * Keep messages positive and uplifting, consistent with the [values and principles of CNCF](https://github.com/cncf/foundation/blob/main/charter.md) 57 | * Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means. 58 | * Share content across social media channels that benefit the ecosystem as a whole 59 | * Maintain a balance of posting on CNCF activities/news and ecosystem-focused content 60 | * Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused 61 | * Engage with the community through retweets and sharing of community content. 62 | 63 | ### General Guidelines 64 | For all CNCF social activity, we remain a neutral foundation. Examples of the type of content: 65 | * Owned content is CNCF news, blogs, case studies, survey data, etc. 66 | * Project content is anything sourced from [CNCF’s currently hosted projects](https://www.cncf.io/projects/), including project news, roadmap updates, new releases, performance/security updates, blogs, conferences slides/videos, etc. 67 | * Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, cloud native-specific Meetups, etc. 68 | * CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website. 69 | * Social posts from member company handles and/or vendor channels cannot be shared. 70 | * RTs are limited to news outlet handles, @linuxfoundation, @kubecon_, project handles + personal handles. 71 | * Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing. 72 | * Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole. 73 | 74 | ### Images & Videos 75 | Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.” 76 | 77 | ### Hashtags 78 | CNCF uses hashtags in our posts: 79 | * To measure the success of campaigns (for example, #KubeCon); 80 | * To expand our reach beyond our current followers and tap into larger, trending topics on Twitter (for example, #cloudnative) 81 | * To organize or categorize shares (for example, #Kubernetes). 82 | 83 | ### To request content to be shared 84 | Share your tweet on the [#socialmedia](https://app.slack.com/client/T08PSQ7BQ/C12MRQ97A) channel on the CNCF Slack channel or email social@cncf.io. 85 | 86 | -------------------------------------------------------------------------------- /code-of-conduct-languages/vi.md: -------------------------------------------------------------------------------- 1 | ## Quy Tắc Ứng Xử Cộng Đồng 2 | 3 | Là những người đóng góp, duy trì và tham gia cộng đồng CNCF và để thúc đẩy một cộng đồng cởi mở và thân thiện, chúng tôi cam kết tôn trọng tất cả những người có đóng góp hoặc tham gia bằng cách gửi báo cáo những vấn đề, đăng yêu cầu tính năng, cập nhật tài liệu, gửi các yêu cầu kéo (pull request) hoặc bản vá, tham dự các hội thảo hoặc sự kiện hoặc tham gia vào các hoạt động khác của cộng đồng hoặc dự án. 4 | 5 | Chúng tôi cam kết tất cả những người tham gia vào cộng đồng CNCF sẽ không bị quấy rối, bất kể tuổi tác, kích thước cơ thể, địa vị xã hội, tình trạng khuyết tật, sắc tộc, mức độ kinh nghiệm, tình trạng gia đình, giới tính, bản dạng và biểu hiện giới tính, tình trạng hôn nhân, tư cách quân nhân hoặc cựu chiến binh, quốc tịch, ngoại hình cá nhân, chủng tộc, tôn giáo, khuynh hướng tình dục, tình trạng kinh tế xã hội, bộ lạc hoặc bất kỳ đặc điểm đa dạng nào khác. 6 | 7 | ## Phạm Vi 8 | 9 | Quy tắc ứng xử này được áp dụng: 10 | * trong các không gian dự án và cộng đồng, 11 | * trong các không gian khác khi một người tham gia cộng đồng CNCF có lời nói hoặc hành động hướng tới hoặc về một dự án CNCF, cộng đồng CNCF hoặc một người tham gia cộng đồng CNCF khác. 12 | 13 | ## Các Sự Kiện CNCF 14 | 15 | Các sự kiện CNCF do Linux Foundation tổ chức với đội ngũ nhân viên sự kiện chuyên nghiệp được kiểm soát bởi [Quy Tắc Ứng Xử của Sự Kiện](https://events.linuxfoundation.org/code-of-conduct/) của Linux Foundation có sẵn trên trang web của sự kiện. Quy tắc này được thiết kế để sử dụng cùng với Quy Tắc Ứng Xử CNCF. 16 | 17 | ## Tiêu Chuẩn của Chúng Tôi 18 | 19 | Cộng Đồng CNCF là một cộng đồng cởi mở, hòa nhập và tôn trọng. Mọi thành viên trong cộng đồng chúng tôi đều có quyền nhận được sự tôn trọng đối với bản dạng của mình. 20 | 21 | Ví dụ về hành vi góp phần tạo nên môi trường tích cực bao gồm nhưng không giới hạn ở: 22 | * Thể hiện sự đồng cảm và lòng tốt đối với người khác 23 | * Tôn trọng những ý kiến, quan điểm và kinh nghiệm khác biệt 24 | * Đưa ra và chấp nhận những phản hồi mang tính xây dựng một cách lịch thiệp 25 | * Nhận trách nhiệm và xin lỗi những người bị ảnh hưởng bởi lỗi lầm của chính chúng ta và rút kinh nghiệm 26 | * Tập trung vào những gì tốt nhất không chỉ cho cá nhân chúng ta mà còn cho cả cộng đồng 27 | * Sử dụng ngôn ngữ có tính chào đón và hòa nhập 28 | 29 | Ví dụ về hành vi không được chấp nhận bao gồm nhưng không giới hạn ở: 30 | * Việc sử dụng ngôn ngữ hoặc hình ảnh gợi dục 31 | * Những bình luận có tính khiêu khích, xúc phạm hoặc sỉ nhục, cũng như tấn công về mặt cá nhân hoặc chính trị 32 | * Quấy rối tại nơi công cộng hoặc riêng tư dưới mọi hình thức 33 | * Công khai thông tin cá nhân của người khác, chẳng hạn như địa chỉ chỗ ở hoặc địa chỉ email của họ mà không có sự cho phép rõ ràng của họ 34 | * Bạo lực, đe dọa bạo lực hoặc khuyến khích người khác thực hiện hành vi bạo lực 35 | * Rình rập hoặc theo dõi ai đó mà không có sự đồng ý của họ 36 | * Tiếp xúc cơ thể không được chào đón 37 | * Sự chú ý hoặc hành vi tán tỉnh với ý đồ gợi dục hoặc lãng mạn không được chào đón 38 | * Hành vi khác có thể được coi là không phù hợp trong môi trường chuyên nghiệp 39 | 40 | Các hành vi sau đây cũng bị cấm: 41 | * Cung cấp thông tin cố ý sai lệch hoặc gây hiểu lầm liên quan đến cuộc điều tra về Quy Tắc Ứng Xử hoặc cố ý làm thay đổi cuộc điều tra. 42 | * Trả thù một người vì họ đã báo cáo sự cố hoặc là nhân chứng cung cấp thông tin về sự cố. 43 | 44 | Những người duy trì dự án có quyền và trách nhiệm xóa, chỉnh sửa hoặc từ chối các bình luận, commit, dòng mã, chỉnh sửa wiki, vấn đề và các đóng góp khác không phù hợp với Quy Tắc Ứng Xử này. Bằng việc áp dụng Quy Tắc Ứng Xử này, những người duy trì dự án cam kết áp dụng một cách công bằng và nhất quán những nguyên tắc này trong mọi vấn đề quản lý dự án CNCF. Những người duy trì dự án không tuân theo hoặc thực thi Quy Tắc Ứng Xử có thể bị xóa tên tạm thời hoặc vĩnh viễn khỏi nhóm dự án. 45 | 46 | ## Báo Cáo 47 | 48 | Đối với các sự cố xảy ra trong cộng đồng Kubernetes, hãy gửi email cho [Ủy Ban Quy Tắc Ứng Xử Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) tại địa chỉ [conduct@kubernetes.io](mailto:conduct@kubernetes.io). Quý vị có thể nhận được phản hồi trong vòng ba ngày làm việc. 49 | 50 | Đối với các dự án khác hoặc các sự cố không liên quan đến dự án hoặc ảnh hưởng đến nhiều dự án CNCF, vui lòng gửi email cho [Ủy Ban Quy Tắc Ứng Xử CNCF](https://www.cncf.io/conduct/committee/) tại địa chỉ [conduct@cncf.io](mailto:conduct@cncf.io). Ngoài ra, quý vị có thể liên hệ với bất kỳ thành viên cá nhân nào của [Ủy Ban Quy Tắc Ứng Xử CNCF](https://www.cncf.io/conduct/committee/) để gửi báo cáo của quý vị. Để biết chi tiết hơn về cách thức gửi báo cáo, bao gồm cách gửi báo cáo ẩn danh, vui lòng xem [Quy Trình Giải Quyết Sự Cố](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). Quý vị có thể nhận được phản hồi trong vòng ba ngày làm việc. 51 | 52 | Đối với các sự cố xảy ra tại sự kiện CNCF do Linux Foundation tổ chức, vui lòng liên hệ [eventconduct@cncf.io](mailto:eventconduct@cncf.io). 53 | 54 | ## Thực Thi 55 | 56 | Sau khi xem xét và điều tra sự cố được báo cáo, nhóm ứng phó CoC có thẩm quyền sẽ xác định hành động nào là phù hợp dựa trên Quy Tắc Ứng Xử này và tài liệu liên quan. 57 | 58 | Để biết thông tin về sự cố nào về Quy Tắc Ứng Xử do nhóm lãnh đạo dự án xử lý, sự cố nào do Ủy Ban Quy Tắc Ứng Xử CNCF xử lý cũng như các sự cố do Linux Foundation xử lý (bao gồm cả nhóm sự kiện của tổ chức này), hãy xem [Chính Sách về Thẩm Quyền](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). 59 | 60 | ## Sửa Đổi 61 | 62 | Theo quy định trong Điều Lệ CNCF, mọi thay đổi quan trọng đối với Quy Tắc Ứng Xử này đều phải được Ủy Ban Giám Sát Kỹ Thuật phê duyệt. 63 | 64 | ## Xác Nhận 65 | 66 | Quy tắc ứng xử này được điều chỉnh từ Quy ước người đóng góp ([http://contributor-covenant.org](http://contributor-covenant.org/)), bản 2.0 có sẵn tại [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) -------------------------------------------------------------------------------- /code-of-conduct-languages/hi.md: -------------------------------------------------------------------------------- 1 | ## सामुदायिक आचार संहिता 2 | 3 | CNCF समुदाय में योगदानकर्ताओं (Contributors), अनुरक्षकों(Maintainers) और प्रतिभागियों (Participants) के रूप में, और एक खुले और स्वागत करने वाले समुदाय को बढ़ावा देने के हित में, हम उन सभी लोगों का सम्मान करने की प्रतिज्ञा करते हैं जो मुद्दों की रिपोर्टिंग (issues) करने, सुविधा अनुरोध पोस्ट करने, दस्तावेज़ीकरण (documentation) अद्यतन करने, पुल अनुरोध या पैच सबमिट करने, सम्मेलनों या कार्यक्रमों में भाग लेने, या अन्य समुदाय या परियोजना गतिविधियों में शामिल होने के माध्यम से भाग लेते हैं या योगदान करते हैं। 4 | 5 | हम उम्र, शरीर के आकार, जाति, विकलांगता, जातीयता, अनुभव के स्तर, पारिवारिक स्थिति, लिंग, लैंगिक पहचान और अभिव्यक्ति, वैवाहिक स्थिति, सैन्य या वेटरन स्थिति, राष्ट्रीयता, व्यक्तिगत उपस्थिति, नस्ल, धर्म, यौन अभिविन्यास, सामाजिक आर्थिक स्थिति, जनजाति, या विविधता के किसी भी आयाम की परवाह किए बिना CNCF समुदाय में भागीदारी को हर किसी के लिए उत्पीड़न-मुक्त अनुभव बनाने के लिए प्रतिबद्ध हैं। 6 | 7 | ## दायरा 8 | 9 | यह आचार संहिता लागू होती है: 10 | * परियोजना और सामुदायिक स्थानों के भीतर, 11 | * अन्य स्थानों पर जब CNCF समुदाय के किसी व्यक्तिगत प्रतिभागी के शब्द या कार्य CNCF परियोजना, CNCF समुदाय, या CNCF समुदाय के किसी अन्य प्रतिभागी पर निर्देशित होते हैं या उसके बारे में होंं। 12 | 13 | ## CNCF इवेंट्स 14 | 15 | पेशेवर इवेंट स्टाफ के साथ लिनक्स फाउंडेशन द्वारा तैयार किए जाने वाले CNCF इवेंट Linux Foundation द्वारा नियंत्रित होते हैं [इवेंट आचार संहिता](https://events.linuxfoundation.org/code-of-conduct/) इवेंट पेज पर उपलब्ध है। इसे CNCF आचार संहिता के संयोजन में उपयोग करने के लिए डिज़ाइन किया गया है। 16 | 17 | ## हमारे मानक 18 | 19 | CNCF समुदाय खुला, समावेशी और सम्मानजनक है। हमारे समुदाय के प्रत्येक सदस्य को अपनी पहचान का सम्मान पाने का अधिकार है। 20 | 21 | सकारात्मक वातावरण में योगदान करने वाले व्यवहार के उदाहरण निम्नलिखित हैं, लेकिन यहीं तक सीमित नहीं हैं: 22 | * अन्य लोगों के प्रति सहानुभूति और दयालुता प्रदर्शित करना 23 | * भिन्न-भिन्न विचारों, दृष्टिकोणों और अनुभवों का सम्मान करना 24 | * रचनात्मक फीडबैक देना और शालीनता से स्वीकार करना 25 | * जिम्मेदारी स्वीकार करना और अपनी गलतियों से प्रभावित हुए लोगों से माफी मांगना, और ऐसे अनुभव से सीखना 26 | * सिर्फ हमारे लिए व्यक्तिगत रूप से नहीं, बल्कि पूरे समुदाय के हित के लिए क्या बेहतर है उस पर ध्यान केंद्रित करना 27 | * स्वागतपूर्ण और समावेशी भाषा का उपयोग करना 28 | 29 | अस्वीकार्य व्यवहार के उदाहरण निम्नलिखित हैं, लेकिन यहीं तक सीमित नहीं हैं: 30 | * कामुक भाषा या छवियों का उपयोगा 31 | * ट्रोलिंग, अपमानजनक या निन्दात्मक टिप्पणियाँ, और व्यक्तिगत या राजनीतिक हमले 32 | * किसी भी रूप में सार्वजनिक या निजी उत्पीड़न 33 | * दूसरों की स्पष्ट अनुमति के बिना उनकी निजी जानकारी, जैसे भौतिक या ईमेल पता, प्रकाशित करना 34 | * हिंसा, हिंसा की धमकी देना, या दूसरों को हिंसक व्यवहार में शामिल होने के लिए प्रोत्साहित करना 35 | * बिना सहमति के किसी का पीछा करना या फॉलो करना। 36 | * अवांछित शारीरिक संपर्क 37 | * सेक्शुअल या रोमांटिक अवांछित ध्यान या इशारे 38 | * अन्य आचरण जिसे एक प्रोफेशनल वातावरण में उचित रूप से अनुचित माना जा सकता है 39 | 40 | निम्नलिखित व्यवहार भी निषिद्ध हैं: 41 | * आचार संहिता की जांच के संबंध में जानबूझकर गलत या भ्रामक जानकारी प्रदान करना या किसी जांच में जानबूझकर छेड़छाड़ करना। 42 | * किसी व्यक्ति के खिलाफ प्रतिशोध लेना क्योंकि उन्होंने किसी घटना की रिपोर्ट की थी या गवाह के रूप में किसी घटना के बारे में जानकारी प्रदान की थी। 43 | 44 | परियोजना अनुरक्षकों के पास इस आचार संहिता के अनुरूप नहीं होने वाली टिप्पणियों, प्रतिबद्धताओं, कोड, विकी संपादनों, मुद्दों और अन्य योगदानों को हटाने, संपादित करने या अस्वीकार करने का अधिकार और जिम्मेदारी है। इस आचार संहिता को अपनाकर, परियोजना अनुरक्षक CNCF परियोजना के प्रबंधन के हर पहलू पर इन सिद्धांतों को निष्पक्ष रूप से और लगातार लागू करने के लिए प्रतिबद्ध हैं। जो प्रोजेक्ट अनुरक्षक आचार संहिता का पालन नहीं करते या लागू नहीं करते, उन्हें प्रोजेक्ट टीम से अस्थायी या स्थायी रूप से हटाया जा सकता है। 45 | 46 | ## रिपोर्टिंग 47 | 48 | कुबेरनेट्स समुदाय में होने वाली घटनाओं के लिए, [conduct@kubernetes.io](mailto:conduct@kubernetes.io) [कुबेरनेट्स आचार संहिता समिति](https://git.k8s.io/community/committee-code-of-conduct) से संपर्क करें। आप तीन व्यावसायिक दिनों के भीतर जवाब प्राप्त करने की उम्मीद कर सकते हैं। 49 | 50 | अन्य परियोजनाओं के लिए, या ऐसी घटनाओं के लिए जो परियोजना-अज्ञेयवादी हैं या कई CNCF परियोजनाओं को प्रभावित करती हैं, कृपया [conduct@cncf.io](mailto:conduct@cncf.io) पर [CNCF आचार संहिता समिति](https://www.cncf.io/conduct/committee/) से संपर्क करें। वैकल्पिक रूप से, आप अपनी रिपोर्ट सबमिट करने के लिए [CNCF आचार संहिता समिति](https://www.cncf.io/conduct/committee/) के किसी भी व्यक्तिगत सदस्य से संपर्क कर सकते हैं। रिपोर्ट सबमिट करने के तरीके के बारे में अधिक विस्तृत निर्देशों के लिए, जिसमें गुमनाम रूप से रिपोर्ट सबमिट करने का तरीका भी शामिल है, कृपया हमार [घटना समाधान प्रक्रियाएँ](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md) देखें। आप तीन व्यावसायिक दिनों के भीतर जवाब प्राप्त करने की उम्मीद कर सकते हैं। 51 | 52 | Linux Foundation द्वारा निर्मित CNCF इवेंट में होने वाली घटनाओं के लिए, कृपया [eventconduct@cncf.io](mailto:conduct@cncf.io) पर संपर्क करें। 53 | 54 | ## प्रवर्तन 55 | 56 | किसी रिपोर्ट की गई घटना की समीक्षा और जांच करने पर, CoC प्रतिक्रिया टीम, जिसके पास अधिकार क्षेत्र है, यह निर्धारित करेगी कि इस आचार संहिता और इसके संबंधित दस्तावेज के आधार पर कौन सी कार्रवाई उचित है। 57 | 58 | इस बारे में जानकारी के लिए कि कौन सी आचार संहिता की घटनाओं को परियोजना नेतृत्व द्वारा नियंत्रित किया जाता है, किन घटनाओं को CNCF आचार संहिता समिति द्वारा नियंत्रित किया जाता है, और कौन सी घटनाओं को Linux Foundation (इसकी Event Team सहित) द्वारा नियंत्रित किया जाता है, हमारा [क्षेत्राधिकार नीति](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md) देखें। 59 | 60 | ## संशोधन 61 | 62 | CNCF चार्टर के अनुरूप, इस आचार संहिता में किसी भी महत्वपूर्ण बदलाव को Technical Oversight Committee द्वारा अनुमोदित किया जाना चाहिए। 63 | 64 | ## आभार 65 | 66 | यह आचार संहिता योगदानकर्ता अनुबंध ([http://contributor-covenant.org](http://contributor-covenant.org/)) संस्करण 2.0 से अनुकूलित है जो [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/)पर उपलब्ध है। -------------------------------------------------------------------------------- /code-of-conduct-languages/id.md: -------------------------------------------------------------------------------- 1 | # Kode Etik Komunitas 2 | 3 | Sebagai kontributor, pengelola, dan peserta dalam komunitas CNCF, dan untuk membina komunitas yang terbuka dan ramah, kami berjanji akan menghormati semua orang yang berpartisipasi atau berkontribusi dengan melaporkan masalah, memposting permintaan fitur, memperbarui dokumentasi, mengirim permintaan penarikan atau perbaikan, menghadiri konferensi atau acara, atau terlibat dalam aktivitas komunitas atau proyek lainnya. 4 | 5 | Kami berkomitmen untuk memberikan pengalaman bebas pelecehan bagi semua orang yang berpartisipasi dalam komunitas CNCF, tanpa memandang usia, ukuran tubuh, kasta, disabilitas, etnis, tingkat pengalaman, status keluarga, gender, identitas dan ekspresi gender, status perkawinan, status militer atau veteran, kewarganegaraan, penampilan pribadi, ras, agama, orientasi seksual, status sosial ekonomi, suku, atau dimensi keberagaman lainnya. 6 | 7 | ## Ruang Lingkup 8 | 9 | Kode etik ini berlaku: 10 | * dalam ruang lingkup proyek dan komunitas, 11 | * dalam ruang lingkup lain ketika ucapan atau tindakan seorang peserta komunitas CNCF ditujukan untuk atau terkait dengan proyek CNCF, komunitas CNCF, atau peserta komunitas CNCF lainnya. 12 | 13 | ### Acara CNCF 14 | 15 | Acara CNCF yang diselenggarakan oleh Linux Foundation bersama staf acara profesional diatur dalam [Kode Etik Acara](https://events.linuxfoundation.org/code-of-conduct/) Linux Foundation yang tersedia di halaman acara. Kode Etik Acara ini dirancang untuk digunakan bersama dengan Kode Etik CNCF. 16 | 17 | ## Standar Kami 18 | 19 | Komunitas CNCF bersifat terbuka, inklusif, dan saling menghormati. Setiap anggota dalam komunitas kami berhak untuk dihormati identitasnya. 20 | 21 | Contoh perilaku yang berkontribusi menciptakan lingkungan positif mencakup, tetapi tidak terbatas pada: 22 | * Menunjukkan empati dan kebaikan kepada orang lain 23 | * Menghargai pendapat, sudut pandang, dan pengalaman yang berbeda 24 | * Memberi dan menerima masukan yang membangun dengan lapang dada 25 | * Bertanggung jawab dan meminta maaf kepada mereka yang terkena dampak dari kesalahan kita, serta belajar dari pengalaman 26 | * Berfokus pada apa yang terbaik, tidak hanya bagi kita secara pribadi, tetapi juga bagi komunitas secara keseluruhan 27 | * Menggunakan bahasa yang inklusif dan ramah 28 | 29 | Contoh perilaku yang tidak dapat diterima mencakup, tetapi tidak terbatas pada: 30 | * Penggunaan bahasa atau gambaran yang berkonotasi seksual 31 | * Komentar yang mengejek, menghina, atau merendahkan, dan serangan pribadi atau politik 32 | * Pelecehan publik atau pribadi dalam bentuk apa pun 33 | * Pemublikasian informasi pribadi orang lain, seperti alamat fisik atau email, tanpa izin tersurat dari pemiliknya 34 | * Kekerasan, ancaman kekerasan, atau dorongan kepada orang lain untuk melakukan tindakan kekerasan 35 | * Perbuatan menguntit atau mengikuti seseorang tanpa persetujuan orang tersebut 36 | * Sentuhan fisik yang tidak diinginkan 37 | * Perhatian atau rayuan seksual atau romantis yang tidak diinginkan 38 | * Perilaku lain yang secara wajar dapat dianggap tidak patut di lingkungan profesional 39 | 40 | Berikut adalah perilaku yang juga dilarang: 41 | * Memberikan informasi palsu atau menyesatkan secara disengaja terkait penyelidikan Kode Etik atau dengan sengaja mengganggu penyelidikan. 42 | * Melakukan tindakan balasan terhadap seseorang karena telah melaporkan suatu kejadian atau memberikan informasi tentang suatu kejadian sebagai saksi. 43 | 44 | Pengelola proyek berhak dan bertanggung jawab untuk menghapus, mengedit, atau menolak komentar, komitmen, kode, pengeditan wiki, masalah, dan kontribusi lainnya yang tidak sejalan dengan Kode Etik ini. Dengan menerapkan Kode Etik ini, pengelola proyek berkomitmen untuk menerapkan prinsip-prinsip ini secara adil dan konsisten di setiap aspek pengelolaan proyek CNCF. Pengelola proyek yang tidak mengikuti atau menegakkan Kode Etik dapat dikeluarkan dari tim proyek untuk sementara waktu atau secara permanen. 45 | 46 | ## Pelaporan 47 | 48 | Untuk insiden yang terjadi di komunitas Kubernetes, hubungi [Komite Kode Etik Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) melalui [conduct@kubernetes.io](mailto:conduct@kubernetes.io). Tanggapan biasanya akan diberikan dalam waktu tiga hari kerja. 49 | 50 | Untuk proyek lain, atau untuk insiden yang tidak terkait proyek atau yang berdampak pada beberapa proyek CNCF, hubungi [Komite Kode Etik CNCF](https://www.cncf.io/conduct/committee/) melalui [conduct@cncf.io](mailto:conduct@cncf.io). Anda juga dapat menghubungi salah satu anggota [Komite Kode Etik CNCF](https://www.cncf.io/conduct/committee/) secara pribadi untuk mengirimkan laporan Anda. Untuk petunjuk lebih terperinci tentang cara mengirimkan laporan, termasuk cara mengirimkan laporan secara anonim, lihat [Prosedur Penyelesaian Insiden](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). Tanggapan biasanya akan diberikan dalam waktu tiga hari kerja. 51 | 52 | Untuk insiden yang terjadi di acara CNCF yang diselenggarakan oleh Linux Foundation, hubungi [eventconduct@cncf.io](mailto:eventconduct@cncf.io). 53 | 54 | ## Pelaksanaan 55 | 56 | Setelah meninjau dan menyelidiki insiden yang dilaporkan, tim respons CoC yang memiliki yurisdiksi akan menentukan tindakan yang tepat berdasarkan Kode Etik ini dan dokumentasi terkait. 57 | 58 | Untuk informasi mengenai insiden Kode Etik yang ditangani oleh pimpinan proyek, insiden yang ditangani oleh Komite Kode Etik CNCF, dan insiden yang ditangani oleh Linux Foundation (termasuk tim acaranya), lihat [Kebijakan Yurisdiksi](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md) kami. 59 | 60 | ## Amendemen 61 | 62 | Sesuai dengan Piagam CNCF, persetujuan dari Komite Pengawasan Teknis diperlukan untuk setiap perubahan substantif terhadap Kode Etik ini. 63 | 64 | ## Pernyataan 65 | 66 | Kode Etik ini diadaptasi dari Perjanjian Kontributor ([http://contributor-covenant.org](http://contributor-covenant.org/)) versi 2.0 yang tersedia di [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) 67 | -------------------------------------------------------------------------------- /code-of-conduct-languages/hu.md: -------------------------------------------------------------------------------- 1 | ## Közösségi Magatartási Kódex 2 | 3 | Mint a CNCF közösség közreműködői, fenntartói és résztvevői, vállaljuk, hogy egy nyitott és befogadó közösség kialakítása érdekében, tiszteletben tartunk minden olyan személyt, aki részt vesz vagy hozzájárul a közösséghez, problémák jelentésével, funkciók kérésével, dokumentáció frissítésével, pull requestek vagy javítások benyújtásával, konferenciákon vagy eseményeken való részvétellel, vagy egyéb közösségi vagy projekt tevékenységel. 4 | 5 | Elkötelezettek vagyunk amellett, hogy a CNCF közösségben való részvétel zaklatásmentes élmény legyen mindenki számára, függetlenül kortól, testmérettől, kaszttól, fogyatékosságtól, etnikai hovatartozástól, tapasztalati szinttől, családi állapottól, nemtől, nemi identitástól és kifejeződéstől, családi állapottól, katonai vagy veterán státusztól, nemzetiségtől, megjelenéstől, fajtól, vallástól, szexuális irányultságtól, társadalmi-gazdasági státusztól, törzsi hovatartozástól, vagy a sokszínűség bármely más dimenziójától. 6 | 7 | ## Hatáskör 8 | 9 | Ez a magatartási kódex érvényes: 10 | 11 | * projekt és közösségi terekben, 12 | * más terekben, ahol egy CNCF közösségi résztvevő szavai vagy cselekedetei egy CNCF projektre, a CNCF közösségre, vagy egy másik CNCF közösségi résztvevőre irányulnak vagy róluk szólnak. 13 | 14 | ## CNCF Események 15 | 16 | A Linux Foundation által professzionális eseményszervezőkkel megvalósított CNCF eseményekre a Linux Foundation [Események Magatartási Kódexe](https://events.linuxfoundation.org/code-of-conduct/) vonatkozik, amely az esemény oldalán elérhető. Utóbbi a CNCF Magatartási Kódexszel együtt használandó. 17 | 18 | ## Alapelveink 19 | 20 | A CNCF közösség nyitott, befogadó és tiszteletteljes. Közösségünk minden tagjának joga van ahhoz, hogy identitását tiszteletben tartsák. 21 | 22 | A pozitív környezethez hozzájáruló viselkedés példái többek között: 23 | 24 | * Empátiával és kedvességel viszonyulni másokhoz 25 | * Tiszteletteljes hozzáállás az eltérő véleményekkel, nézőpontokkal és 26 | tapasztalatokkal szemben 27 | * Konstruktív visszajelzés adása és elfogadása 28 | * Felelősség vállalása és bocsánatkérés azoktól, akiket hibáink 29 | érintettek,valamint a megfelelő tanulság levonása az esetből 30 | * Koncentrálás arra, ami nem csak egyénileg, hanem az egész közösség 31 | számára a legjobb 32 | * Befogadó és inkluzív nyelvhasználat 33 | 34 | Elfogadhatatlan viselkedés példái többek között: 35 | 36 | * Szexualizált nyelvezet vagy képek használata 37 | * Trollkodás, sértő vagy lekicsinylő megjegyzések, valamint személyes 38 | vagy politikai támadások 39 | * Bármilyen formájú nyilvános vagy privát zaklatás 40 | * Mások magáninformációinak közzététele, például fizikai vagy e-mail cím, 41 | kifejezett engedélyük nélkül 42 | * Erőszak, megfélemlítés, vagy mások erőszakos viselkedésre való biztatása 43 | * Mások követése vagy megfigyelése beleegyezésük nélkül 44 | * Nem kívánt fizikai érintkezés 45 | * Nem kívánt szexuális vagy romantikus figyelem vagy közeledés 46 | * Egyéb magatartás, amely ésszerűen nem megfelelőnek tekinthető szakmai környezetben 47 | 48 | Az alábbi viselkedések szintén nem megengedettek: 49 | 50 | * Tudatosan hamis vagy félrevezető információk szolgáltatása egy fegyelmi vizsgálattal kapcsolatban, vagy egyéb módon szándékos beavatkozás egy vizsgálatba. 51 | * Megtorlás egy személy ellen, mert jelentett egy incidenst vagy tanúként információt szolgáltatott egy incidensről. 52 | 53 | A projekt fenntartóinak joga és felelőssége eltávolítani, szerkeszteni vagy elutasítani olyan hozzászólásokat, commit-okat, kódokat, wiki szerkesztéseket, problémákat és egyéb hozzájárulásokat, amelyek nincsenek összhangban ezzel a Magatartási Kódex-szel. 54 | A Magatartási Kódex elfogadásával a projekt fenntartói kötelezettséget vállalnak arra, hogy ezeket az elveket tisztességesen és következetesen alkalmazzák egy CNCF projekt kezelésének minden aspektusában. 55 | Azon projekt fenntartók, akik nem követik vagy nem érvényesítik a Magatartási Kódexet, ideiglenesen vagy véglegesen eltávolíthatók a projekt csapatából. 56 | 57 | ## Jelentés 58 | 59 | A Kubernetes közösségben történő incidensek esetén vegye fel a kapcsolatot a [Kubernetes Magatartási Kódex Bizottságával](https://git.k8s.io/community/committee-code-of-conduct) a címen. Három munkanapon belül választ várhat. 60 | 61 | Más projektek esetében, vagy olyan incidensek esetén, amelyek projekt-függetlenek vagy több CNCF projektet érintenek, kérjük, vegye fel a kapcsolatot a [CNCF Magatartási Kódex Bizottságával](https://www.cncf.io/conduct/committee/) a címen. Alternatívaként kapcsolatba léphet a [CNCF Magatartási Kódex Bizottság](https://www.cncf.io/conduct/committee/) bármely tagjával a jelentése benyújtásához. A jelentés benyújtásának részletesebb útmutatójáért, beleértve azt is, hogyan nyújthat be névtelen jelentést, kérjük, tekintse meg az [Incidens Megoldási Eljárásainkat](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). Három munkanapon belül választ várhat. 62 | 63 | A Linux Foundation által szervezett CNCF eseményen történő incidensek esetén kérjük, vegye fel a kapcsolatot az címen. 64 | 65 | ## Végrehajtás 66 | 67 | A bejelentett incidens áttekintése és kivizsgálása után az illetékes válaszadó csapat meghatározza, hogy milyen intézkedés megfelelő a Magatartási Kódex és a kapcsolódó dokumentáció alapján. 68 | 69 | Hogy mely Magatartási Kódex incidenseket kezelik a projekt vezetői, mely incidenseket kezeli a CNCF Magatartási Kódex Bizottság, és mely incidenseket kezeli a Linux Foundation (beleértve annak eseménycsapatát is), lásd a [Joghatósági Szabályzatunkat](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). 70 | 71 | ## Kiegészítés 72 | 73 | A CNCF Alapszabályzatával összhangban jelen Magatartási Kódex bármely lényegi változtatását a Műszaki Felügyeleti Bizottságnak kell jóváhagynia. 74 | 75 | ## Köszönetnyilvánítás 76 | 77 | Ez a Magatartási Kódex a Contributor Covenant 2.0-ás verziójának adaptációja, amely elérhető a címen. 78 | -------------------------------------------------------------------------------- /license-exceptions/cncf-exceptions-2023-06-27.spdx: -------------------------------------------------------------------------------- 1 | SPDXVersion: SPDX-2.1 2 | DataLicense: CC0-1.0 3 | SPDXID: SPDXRef-DOCUMENT 4 | DocumentName: cncf-exceptions-2023-06-27 5 | DocumentNamespace: https://github.com/cncf/foundation/license-exceptions-2023-06-27 6 | Creator: Organization: CNCF 7 | Created: 2023-06-27T14:38:55Z 8 | 9 | ##### Package: hashicorp/go-plugin 10 | 11 | PackageName: hashicorp/go-plugin 12 | SPDXID: SPDXRef-Package2 13 | PackageDownloadLocation: NOASSERTION 14 | FilesAnalyzed: false 15 | PackageLicenseConcluded: MPL-2.0 16 | PackageLicenseDeclared: NOASSERTION 17 | PackageCopyrightText: NOASSERTION 18 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 19 | 20 | 21 | ##### Package: hashicorp/go-immutable-radix 22 | 23 | PackageName: hashicorp/go-immutable-radix 24 | SPDXID: SPDXRef-Package3 25 | PackageDownloadLocation: NOASSERTION 26 | FilesAnalyzed: false 27 | PackageLicenseConcluded: MPL-2.0 28 | PackageLicenseDeclared: NOASSERTION 29 | PackageCopyrightText: NOASSERTION 30 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 31 | 32 | ##### Package: hashicorp/raft 33 | 34 | PackageName: hashicorp/raft 35 | SPDXID: SPDXRef-Package4 36 | PackageDownloadLocation: NOASSERTION 37 | FilesAnalyzed: false 38 | PackageLicenseConcluded: MPL-2.0 39 | PackageLicenseDeclared: NOASSERTION 40 | PackageCopyrightText: NOASSERTION 41 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 42 | 43 | ##### Package: hashicorp/go-rootcerts 44 | 45 | PackageName: hashicorp/go-rootcerts 46 | SPDXID: SPDXRef-Package5 47 | PackageDownloadLocation: NOASSERTION 48 | FilesAnalyzed: false 49 | PackageLicenseConcluded: MPL-2.0 50 | PackageLicenseDeclared: NOASSERTION 51 | PackageCopyrightText: NOASSERTION 52 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 53 | 54 | ##### Package: hashicorp/go-sockaddr 55 | 56 | PackageName: hashicorp/go-sockaddr 57 | SPDXID: SPDXRef-Package6 58 | PackageDownloadLocation: NOASSERTION 59 | FilesAnalyzed: false 60 | PackageLicenseConcluded: MPL-2.0 61 | PackageLicenseDeclared: NOASSERTION 62 | PackageCopyrightText: NOASSERTION 63 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 64 | 65 | ##### Package: hashicorp/vault 66 | 67 | PackageName: hashicorp/vault/api 68 | SPDXID: SPDXRef-Package7 69 | PackageDownloadLocation: NOASSERTION 70 | FilesAnalyzed: false 71 | PackageLicenseConcluded: MPL-2.0 72 | PackageLicenseDeclared: NOASSERTION 73 | PackageCopyrightText: NOASSERTION 74 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 75 | 76 | ##### Package: hashicorp/consul/api 77 | 78 | PackageName: hashicorp/consul/api 79 | SPDXID: SPDXRef-Package8 80 | PackageDownloadLocation: NOASSERTION 81 | FilesAnalyzed: false 82 | PackageLicenseConcluded: MPL-2.0 83 | PackageLicenseDeclared: NOASSERTION 84 | PackageCopyrightText: NOASSERTION 85 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 86 | 87 | ##### Package: hashicorp/serf 88 | 89 | PackageName: hashicorp/serf 90 | SPDXID: SPDXRef-Package9 91 | PackageDownloadLocation: NOASSERTION 92 | FilesAnalyzed: false 93 | PackageLicenseConcluded: MPL-2.0 94 | PackageLicenseDeclared: NOASSERTION 95 | PackageCopyrightText: NOASSERTION 96 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 97 | 98 | ##### Package: hashicorp/go-hclog 99 | 100 | PackageName: hashicorp/go-hclog 101 | SPDXID: SPDXRef-Package10 102 | PackageDownloadLocation: NOASSERTION 103 | FilesAnalyzed: false 104 | PackageLicenseConcluded: MPL-2.0 105 | PackageLicenseDeclared: NOASSERTION 106 | PackageCopyrightText: NOASSERTION 107 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 108 | 109 | ##### Package: hashicorp/go-secure-stdlib 110 | 111 | PackageName: hashicorp/go-secure-stdlib 112 | SPDXID: SPDXRef-Package11 113 | PackageDownloadLocation: NOASSERTION 114 | FilesAnalyzed: false 115 | PackageLicenseConcluded: MPL-2.0 116 | PackageLicenseDeclared: NOASSERTION 117 | PackageCopyrightText: NOASSERTION 118 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 119 | 120 | ##### Package: hashicorp/go-uuid 121 | 122 | PackageName: hashicorp/go-uuid 123 | SPDXID: SPDXRef-Package12 124 | PackageDownloadLocation: NOASSERTION 125 | FilesAnalyzed: false 126 | PackageLicenseConcluded: MPL-2.0 127 | PackageLicenseDeclared: NOASSERTION 128 | PackageCopyrightText: NOASSERTION 129 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 130 | 131 | ##### Package: hashicorp/go-version 132 | 133 | PackageName: hashicorp/go-version 134 | SPDXID: SPDXRef-Package13 135 | PackageDownloadLocation: NOASSERTION 136 | FilesAnalyzed: false 137 | PackageLicenseConcluded: MPL-2.0 138 | PackageLicenseDeclared: NOASSERTION 139 | PackageCopyrightText: NOASSERTION 140 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 141 | 142 | 143 | ##### Package: hashicorp/yamux 144 | 145 | PackageName: hashicorp/yamux 146 | SPDXID: SPDXRef-Package14 147 | PackageDownloadLocation: NOASSERTION 148 | FilesAnalyzed: false 149 | PackageLicenseConcluded: MPL-2.0 150 | PackageLicenseDeclared: NOASSERTION 151 | PackageCopyrightText: NOASSERTION 152 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 153 | 154 | 155 | ##### Package: veraison/go-cose 156 | 157 | PackageName: veraison/go-cose 158 | SPDXID: SPDXRef-Package15 159 | PackageDownloadLocation: NOASSERTION 160 | FilesAnalyzed: false 161 | PackageLicenseConcluded: MPL-2.0 162 | PackageLicenseDeclared: NOASSERTION 163 | PackageCopyrightText: NOASSERTION 164 | PackageComment: not auto-allowlist because: Non-allowlist license(s); approved by GB exception 2023-06-27 -------------------------------------------------------------------------------- /code-of-conduct-languages/uk.md: -------------------------------------------------------------------------------- 1 | ## Кодекс поведінки Спільноти 2 | 3 | Як контриб'ютори, координатори (мейнтейнери) та учасники Спільноти CNCF, а також в інтересах сприяння відкритості привітності спільноти, ми зобов'язуємось поважати всіх осіб, які беруть активну участь у житті спільноти або роблять значний вклад в її діяльність шляхом подання звітів про проблеми, запитів на нові функції, оновлення документації, подання запитів на внесення змін чи виправлень, відвідин конференцій або подій, або участі в інших заходах спільноти або проєкту. 4 | 5 | Ми беремо на себе зобов'язання зробити участь у Спільноті CNCF вільним від переслідування досвідом для всіх, незалежно від віку, розміру тіла, касти, інвалідності, етнічного походження, рівня досвіду, сімейного стану, статі, гендерної ідентичності та поглядів, сімейного стану, статусу військовослужбовця або ветерана, національності, зовнішності, раси, релігії, сексуальної орієнтації, соціально-економічного статусу, племінної приналежності чи будь-якого іншого виміру різноманіття. 6 | 7 | ## Сфера застосування 8 | 9 | Цей Кодекс поведінки застосовується: 10 | * у межах проєктів та проєктних спільнот, 11 | * в інших просторах, коли слова або дії окремого учасника Спільноти CNCF спрямовані або стосуються проекту CNCF, Спільноти CNCF або іншого учасника Спільноти CNCF. 12 | 13 | ## Події CNCF 14 | 15 | Події CNCF, які проводяться Linux Foundation із залученням професійних співробітників, регулюються [Кодексом поведінки на подіях](https://events.linuxfoundation.org/code-of-conduct/) Linux Foundation, доступним на сторінці події. Він розроблений таким чином, щоб відповідати вимогам з Кодексом поведінки CNCF. 16 | 17 | ## Наші стандарти 18 | 19 | Спільнота CNCF є відкритою, інклюзивною та ставиться з повагою до своїх членів. Кожен учасник нашої спільноти має право на повагу до своєї ідентичності. 20 | 21 | Приклади поведінки, яка сприяє створенню позитивного середовища, включають, але не обмежуються наступними: 22 | * Демонстрація емпатії та доброти до інших людей 23 | * Повага до різних думок, точок зору та досвіду 24 | * Конструктивний зворотній зв'язок, який дають і приймають ввічливо 25 | * Прийняття відповідальності та принесення вибачень тими, хто постраждав від наших помилок, і навчання на власному досвіді 26 | * Зосередження на тому, що є найкращим не лише для нас як особистостей, але й для спільноти в цілому 27 | * Використання привітної та інклюзивної мови 28 | 29 | Приклади неприйнятної поведінки включають, але не обмежуються наступними: 30 | * Використання сексуалізованої мови або образів 31 | * Тролінг, образливі або принизливі коментарі, а також особисті або політичні докори 32 | * Громадське або особисте переслідування в будь-якій формі 33 | * Публікація особистої інформації інших осіб, наприклад, фізичної адреси або адреси електронної пошти, без явного дозволу 34 | * Насильство, погроза насильством або заохочення інших до насильницької поведінки 35 | * Переслідування або стеження за людиною без її згоди 36 | * Небажаний фізичний контакт 37 | * Небажана сексуальна чи романтична увага або залицяння 38 | * Інша поведінка, яка може обґрунтовано вважатися неприйнятною в професійному середовищі 39 | 40 | Наступна поведінка також заборонена: 41 | * Надання завідомо неправдивої або оманливої інформації у зв'язку з розслідуванням в межах Кодексу поведінки або інше умисне перешкоджання розслідуванню. 42 | * Переслідування особи за те, що вона повідомила про інцидент або надала інформацію про інцидент як свідок. 43 | 44 | Мейнтейнери проєкту має право та несуть відповідальність за видалення, редагування або відхилення коментарів, транзакцій, кодів, редагувань вікі-сторінок, проблем та інших змін, які не узгоджені з цим Кодексом поведінки Приймаючи цей Кодекс поведінки, службовий персонал проєкту зобов'язуються справедливо та послідовно застосовувати ці принципи до кожного аспекту управління проєктами які належать до CNCF. Учасники проєкту, які не дотримуються положень Кодексу поведінки та не виконують їх, можуть бути тимчасово або назавжди вилучені з команди проєкту. 45 | 46 | ## Звітування 47 | 48 | Щодо інцидентів, які трапляються у спільноті Kubernetes, звертайтеся до [Комітету з питань Кодексу поведінки Kubernetes](https://git.k8s.io/community/committee-code-of-conduct) за адресою [conduct@kubernetes.io](mailto:conduct@kubernetes.io). Відповідь зазвичай надається протягом трьох днів. 49 | 50 | Щодо інших проєктів або інцидентів, які стосуються конкретного проєкту або впливають на кілька проєктів CNCF, звертайтеся до [Комітету з питань Кодексу поведінки CNCF](https://www.cncf.io/conduct/committee/) за адресою [conduct@cncf.io](mailto:conduct@cncf.io). Крім того, для звітування ви можете зв'язатися з будь-яким членом [Комітету з питань Кодексу поведінки CNCF](https://www.cncf.io/conduct/committee/). Більш детальні інструкції щодо звітування, в тому числі анонімно, див. у документі [«Процедури вирішення інцидентів»](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). Відповідь зазвичай надається протягом трьох днів. 51 | 52 | Щодо інцидентів, які сталися в межах подій CNCF, організованих Linux Foundation, звертайтеся за адресою [eventconduct@cncf.io](mailto:eventconduct@cncf.io). 53 | 54 | ## Забезпечення виконання 55 | 56 | Після розгляду та розслідування інциденту, про який було повідомлено у звіті, група реагування щодо Кодексу поведінки, яка має відповідну юрисдикцію, визначить, які дії є доречними на основі цього Кодексу поведінки та пов'язаної з ним документації. 57 | 58 | Для отримання інформації про те, які порушення Кодексу поведінки розглядаються керівництвом проєкту, які - Комітетом з питань Кодексу поведінки CNCF, а які - Linux Foundation (включно з його командою з питань подій), див. нашу [Політику юрисдикції](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). 59 | 60 | ## Внесення змін 61 | 62 | Відповідно до статуту CNCF, будь-які суттєві зміни до цього Кодексу поведінки мають бути затверджені Комітетом з технічного нагляду (CNCF TOC). 63 | 64 | ## Подяки 65 | 66 | Цей Кодекс поведінки адаптовано згідно з Кодексом поведінки учасника ([http://contributor-covenant.org](http://contributor-covenant.org/)), версія 2.0, доступним за адресою [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) -------------------------------------------------------------------------------- /license-notices.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## License Notices in CNCF Files 4 | 5 | Where reasonably possible, each source code and documentation file that is contributed to a CNCF project should contain a copyright notice and license notice. 6 | 7 | There are several reasons to include notices on a file-by-file basis, rather than just in a single LICENSE file in the repo root directory. In particular, including notices on a file-by-file basis enables better code reuse, by helping to ensure that the relevant information travels along with the file when it is reused in other projects. 8 | 9 | There is no one mandatory way in which license notices need to be provided. Following are some options for ways to provide notices in various use cases. 10 | 11 | For additional details regarding attribution notices for third party code used 12 | in CNCF projects, see the [CNCF attribution recommendations] document. 13 | 14 | ### Original content for CNCF projects 15 | 16 | Under the [CNCF charter], section 11, source code is to be made available under the Apache License, version 2.0 (Apache-2.0) and documentation is to be made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0). 17 | 18 | These notices can be included using either the standard language from the license steward, and/or using an [SPDX short-form identifier](https://spdx.dev/ids). For example, for source code: 19 | 20 | ``` 21 | # Licensed under the Apache License, Version 2.0 (the "License"); 22 | # you may not use this file except in compliance with the License. 23 | # You may obtain a copy of the License at 24 | # 25 | # http://www.apache.org/licenses/LICENSE-2.0 26 | # 27 | # Unless required by applicable law or agreed to in writing, software 28 | # distributed under the License is distributed on an "AS IS" BASIS, 29 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 30 | # See the License for the specific language governing permissions and 31 | # limitations under the License. 32 | ``` 33 | 34 | and/or: 35 | 36 | ``` 37 | # SPDX-License-Identifier: Apache-2.0 38 | ``` 39 | 40 | For documentation: 41 | 42 | ``` 43 | 44 | ``` 45 | 46 | and/or: 47 | 48 | ``` 49 | 50 | ``` 51 | 52 | Often, a file will include a copyright notice just before or after the license notice. See CNCF's [recommendations for copyright notices](./copyright-notices.md) for more details. 53 | 54 | ### Reusing a file from another project 55 | 56 | When reusing a file from another project, you will typically want to: 57 | 1. retain any existing copyright notices in the file; 58 | 2. retain any existing license notices in the file; and 59 | 3. if there is no license notice in the file, add one. 60 | 61 | Parts 1 and 2 are straightforward: Don't delete existing notices. 62 | 63 | For part 3, if the file does not contain a notice stating the license it was used under, you will likely want to add one. This can be done with an [SPDX short-form identifier](https://spdx.dev/ids), using the applicable license ID from the [SPDX license list](https://spdx.org/licenses). 64 | 65 | For example, if the file is provided under the MIT license, you could add to the file: 66 | 67 | ``` 68 | # SPDX-License-Identifier: MIT 69 | ``` 70 | 71 | Also see below for details about including the actual text of these additional licenses in the repo. 72 | 73 | ### Reusing content from part of a file from another project 74 | 75 | Sometimes, a contribution may include a portion of code (sometimes called a "snippet") taken from another project, but without copying the entire file. For example, this might include copying a single function from another project, and adding it to a file that you otherwise wrote. 76 | 77 | When reusing a _portion of a file_ from another project, you will typically want to: 78 | 1. include any existing copyright notices from the original file that applied to that portion; 79 | 2. include any existing license notices from the original file that applied to that portion; and 80 | 3. if there was no license notice from the original file, add one. 81 | 82 | For each of these, it is typically helpful to include context explaining which part of the new file is covered by the applicable notices. For example: 83 | 84 | ``` 85 | # The foo() function was copied from Project XYZ, and is 86 | # provided here subject to the following: 87 | # [copyright notice] 88 | # [license notice] 89 | ``` 90 | 91 | Additionally, if the copied content is under a different license from your own code, then you will likely want to update any SPDX short-form identifier to communicate that both licenses apply to the file. This is typically done using the `AND` operator in an [SPDX license expression](https://spdx.dev/ids). For example: 92 | * if a file contains code written for CNCF which is under Apache-2.0, 93 | * and it also contains a function copied from a third-party project licensed under MIT, 94 | * then the identifier for the file would say: `SPDX-License-Identifier: Apache-2.0 AND MIT` 95 | 96 | Also see below for details about including the actual text of these additional licenses in the repo. 97 | 98 | ## Including the text of additional licenses 99 | 100 | Note that where other licenses are used, you will also want to include the corresponding license text itself somewhere in the repo. The LICENSE file will contain the project's main license text (e.g., Apache-2.0), but many other licenses require that the license text itself be reproduced in addition to a short notice or identifier. 101 | 102 | This could be done in the file itself, or in a root-level file such as THIRD-PARTY.txt. We do not recommend using a file called NOTICE for this purpose, as that filename has a specific meaning under the [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0.txt). 103 | 104 | The [REUSE Software Initiative](https://reuse.software/spec/) also contains recommendations for placing license texts within a `/LICENSES/` directory. 105 | 106 | [CNCF Charter]: https://github.com/cncf/foundation/blob/main/charter.md 107 | [CNCF attribution recommendations]: https://github.com/cncf/foundation/blob/main/policies-guidance/recommendations-for-attribution.md 108 | -------------------------------------------------------------------------------- /code-of-conduct-languages/tr.md: -------------------------------------------------------------------------------- 1 | ## Topluluk Davranış Kuralları 2 | 3 | CNCF topluluğuna katkı yapan ve topluluğun devamını sağlayan kişiler ve topluluğun katılımcıları olarak, açık ve samimi bir topluluğun gelişimini teşvik etme amacıyla; sorunları raporlayarak, özellik talepleri yayımlayarak, belgeleri güncelleyerek, çekme talepleri veya yamalar göndererek, konferanslara veya etkinliklere katılarak ya da diğer topluluk veya proje faaliyetlerinde bulunarak katılım sağlayan ya da katkıda bulunan herkese saygı duyacağımızı taahhüt ediyoruz. 4 | 5 | CNCF topluluğuna katılımı yaş, vücut ölçüsü, sosyal sınıf, engellilik durumu, etnik köken, deneyim seviyesi, aile durumu, cinsiyet, cinsiyet kimliği ve ifadesi, medeni durum, askerlik veya gazilik durumu, milliyet, kişisel görünüm, ırk, din, cinsel yönelim, sosyoekonomik durum, kabile mensubiyeti ya da çeşitlilik bağlamında herhangi bir başka boyuttan bağımsız olarak herkes için tacizden arındırılmış bir deneyim haline getirmeye kararlıyız. 6 | 7 | ## Kapsam 8 | 9 | Bu davranış kuralları şu alanlarda geçerlidir: 10 | * proje ve topluluk alanları dahilinde, 11 | * bireysel bir CNCF topluluğu katılımcısının söz veya eylemlerinin bir CNCF projesine, CNCF topluluğuna ya da bir başka CNCF topluluğu katılımcısına yönelik veya bunlar hakkında olduğu diğer alanlarda. 12 | 13 | ## CNCF Etkinlikleri 14 | 15 | Profesyonel etkinlik personeli ile Linux Vakfı tarafından düzenlenen CNCF etkinlikleri, etkinlik sayfasında mevcut olan Linux Vakfı [Etkinlik Davranış Kuralları](https://events.linuxfoundation.org/code-of-conduct/)'na tabidir. Bu, CNCF Davranış Kuralları ile bağlantılı olarak kullanılmak üzere tasarlanmıştır. 16 | 17 | ## Standartlarımız 18 | 19 | CNCF Topluluğu açık, kapsayıcı ve saygıya dayalı bir topluluktur. Topluluğumuzun her bir üyesi, kimliğine saygı gösterilme hakkına sahiptir. 20 | 21 | Ortamın olumlu bir havaya sahip olmasına katkıda bulunan davranış örnekleri, bunlarla sınırlı olmamak üzere aşağıdakileri içerir: 22 | * Diğer insanlara empati ve nezaketle yaklaşmak 23 | * Farklı görüşlere, bakış açılarına ve deneyimlere saygılı olmak 24 | * Yapıcı geri bildirimde bulunmak ve yapıcı geri bildirimi nezaketle kabul etmek 25 | * Sorumluluğu kabul etmek, hatalarımızdan etkilenenlerden özür dilemek ve deneyimlerden ders çıkarmak 26 | * Sadece bireyler olarak bizim için değil, tüm toplum için en iyisinin ne olduğuna odaklanmak 27 | * Samimi ve kapsayıcı bir dil kullanmak 28 | 29 | Kabul edilemez davranış örnekleri, bunlarla sınırlı olmamak üzere aşağıdakileri içerir: 30 | * Cinselleştirilmiş dil veya imge kullanımı 31 | * Trolleme, hakaret niteliğinde veya aşağılayıcı yorumlar ve kişisel ya da siyasi saldırılar 32 | * Herhangi bir biçimde herkese açık veya gizli şekilde tacizde bulunmak 33 | * Başkalarının fiziksel veya e-posta adresi gibi özel bilgilerini açık izinleri olmadan yayımlamak 34 | * Şiddet uygulamak, şiddetle tehdit etmek ya da başkalarını şiddet içerikli davranışta bulunmaya teşvik etmek 35 | * Sanal takip veya onayı olmadan birini takip etmek 36 | * İstenmeyen fiziksel temas 37 | * İstenmeyen cinsel ya da romantik ilgi veya yakınlaşma çabası 38 | * Profesyonel bir ortamda mantıken uygunsuz kabul edilebilecek diğer davranışlar 39 | 40 | Ayrıca aşağıdaki davranışlar da yasaktır: 41 | * Davranış Kuralları ile ilgili bir soruşturmayla bağlantılı olarak bilerek hatalı ya da yanlış yönlendirici bilgi vermek veya soruşturmayı farklı biçimlerde kasti olarak etkilemeye çalışmak. 42 | * Tanık olarak bir olayı rapor ettiği ya da olay hakkında bilgi verdiği için bir kişiye karşı misillemede bulunmak. 43 | 44 | Proje sorumluları, bu Davranış Kuralları ile uyumlu olmayan yorumları, girişleri, kodları, wiki düzenlemelerini, sorunları ve diğer katkıları kaldırma, düzenleme ya da reddetme hakkına ve sorumluluğuna sahiptir. Proje sorumluları, bu Davranış Kurallarını kabul ettiklerinde bir CNCF projesi yönetmenin her aşamasında söz konusu ilkeleri adil ve tutarlı bir biçimde uygulama taahhüdünde bulunmuş olur. Davranış Kurallarını uygulamayan ya da yürürlüğe koymayan proje sorumluları, proje ekibinden geçici veya kalıcı olarak çıkarılabilir. 45 | 46 | ## Raporlama 47 | 48 | Kubernetes topluluğunda meydana gelen olaylar için [conduct@kubernetes.io](mailto:conduct@kubernetes.io) adresi üzerinden [Kubernetes Davranış Kuralları Komitesi](https://git.k8s.io/community/committee-code-of-conduct) ile iletişime geçin. Normal şartlarda üç iş günü içinde yanıt alırsınız. 49 | 50 | Diğer projeler veya projeden bağımsız olan ya da birden fazla CNCF projesini etkileyen olaylar için lütfen [conduct@cncf.io](mailto:conduct@cncf.io) adresi üzerinden [CNCF Davranış Kuralları Komitesi](https://www.cncf.io/conduct/committee/) ile iletişime geçin. Alternatif olarak, raporunuzu göndermek için [CNCF Davranış Kuralları Komitesi](https://www.cncf.io/conduct/committee/) üyelerinin herhangi biri ile iletişime geçebilirsiniz. Bir raporun nasıl gönderileceğine ilişkin daha ayrıntılı talimatlar için lütfen [Olay Çözümleme Prosedürlerimize](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md) bakın. Normal şartlarda üç iş günü içinde yanıt alırsınız. 51 | 52 | Linux Vakfı tarafından düzenlenen bir CNCF etkinliğinde meydana gelen olaylar için lütfen [eventconduct@cncf.io](mailto:eventconduct@cncf.io) ile iletişime geçin. 53 | 54 | ## Uygulama 55 | 56 | Rapor edilen bir olayın incelenip soruşturulmasının ardından yargı yetkisine sahip olan CoC müdahale ekibi, bu Davranış Kuralları ve ilgili belgeleri esas alarak hangi eylemin uygun olduğuna karar verecektir. 57 | 58 | Hangi Davranış Kuralları olaylarının proje liderliği tarafından, hangi olayların CNCF Davranış Kuralları Komitesi tarafından ve hangi olayların Linux Vakfı (vakfın etkinlikler ekibi dahil) tarafından ele alındığı hakkında bilgi için [Yargı Yetkisi Politikamıza](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md) bakın. 59 | 60 | ## Değişiklikler 61 | 62 | CNCF Sözleşmesi ile tutarlı olacak şekilde bu Davranış Kuralları'nda yapılacak tüm önemli değişiklikler, Teknik Denetim Komitesi tarafından onaylanmalıdır. 63 | 64 | ## Teşekkür 65 | 66 | Bu Davranış Kuralları, [http://contributor-covenant.org/version/2/0/code_of_conduct/](http://contributor-covenant.org/version/2/0/code_of_conduct/) adresinde bulunan Katılımcı Sözleşmesi'nin ([http://contributor-covenant.org](http://contributor-covenant.org/)) 2.0 numaralı sürümünden uyarlanmıştır. -------------------------------------------------------------------------------- /documents/project-newsletter/2024-01-26- Project Newsletter.md: -------------------------------------------------------------------------------- 1 | 2 | Cloud Native Project Monthly (CNPM) January 2024 3 | 4 | January 26, 2024 5 | 6 | In this Edition: 7 | ## KubeCon + CloudNativeCon Schedule 8 | ## Project Video Update at KubeCon + CloudNativeCon EU 9 | ## Mentorship Opportunities 10 | ## TechDocs Open Office Hours 11 | ## Upcoming CFP Deadlines 12 | 13 | 14 | #### 15 | 16 | ## 🏨KubeCon + CloudNativeCon EU Hotels Now Available 17 | The schedule is LIVE for [KubeCon + CloudNativeCon Europe 2024](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/)! 🎁 [If you’re not yet registered to join us in Paris](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/), France from 19-22 March, get a move on. 🏃 18 | 19 | This epic event has everything you need: talks from experts, news, and tech from the best vendors, a hackathon, more than a dozen co-located events, parties, swag, and all the networking you can handle with the best in the industry! [Join us](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/). 20 | 21 | [View Schedule](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/schedule/) 22 | 23 | ## 📽️ Project Video Update at KubeCon + CloudNativeCon EU 24 | For KubeCon + CloudNativeCon EU, we will limit the project updates on the keynote stage exclusively to Graduated projects + Kubernetes SIGs. 25 | 26 | Incubating projects will still be able to provide updates at KubeCon + CloudNativeCon EU on our new Lightning Talk stage with the option to provide live or pre-recorded updates. 27 | 28 | All updates provided at KubeCon + CloudNativeCon EU will be showcased throughout the event on monitors displayed in our Project Pavilion. 29 | 30 | Please submit your video and slide deck by Friday, January 25, in order to be considered. 31 | 32 | [Review Guidelines](https://docs.google.com/forms/d/e/1FAIpQLSf_dCUIsbnCPohBqBtc22G6thTYyvf25kw8MbYb4WUipdC4_A/viewform?_hsenc=p2ANqtz-98E0spAnDIhKO1W2CZIiN-NM1ZaEkFwdDVS8M-4xz_-Pcr8KNd1-3KOAo7RoEW3BliThF0) 33 | 34 | ## 🗣️Mentoring 35 | LFX Mentorship 36 | The LFX Mentorship 2024 Term 01: March - May is open now open for project ideas: 37 | [https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2024/01-Mar-May](https://github.com/cncf/mentoring/tree/main/programs/lfx-mentorship/2024/01-Mar-May) 38 | 39 | Project submission and application timeline: 40 | 41 | - Project proposal period: January 8 - 24. If you miss this deadline by a day or so, please contact [nwaddington@linuxfoundation.org](nwaddington@linuxfoundation.org) 42 | - Mentee applications open: January 29 - February 13 (2 weeks) 43 | - Application review/admission decisions/HR paperwork: February 14 - February 27 44 | - We look forward to seeing all the project ideas you're interested in working on! 45 | 46 | Google Summer of Code 20 47 | This is Google Summer of Code’s 20th Year 🎉 CNCF has been participating in the Google Summer of Code for a few years, and now we are excited to apply and join the 2024 program cycle with them! 48 | 49 | All CNCF projects are eligible to apply to participate in the Google Summer of Code. Please start thinking about project ideas and submit them via pull request: 50 | [https://github.com/cncf/mentoring/blob/main/programs/summerofcode/2024.md#ideas](https://github.com/cncf/mentoring/blob/main/programs/summerofcode/2024.md#ideas) 51 | 52 | This year, GSoC is looking to have more AI/ML projects in particular, so please share any open source AI/ML projects that you’re thinking of doing. 53 | 54 | The deadline to [submit project ideas](https://github.com/cncf/mentoring/blob/main/programs/summerofcode/2024.md) is March 11, 2024. 55 | 56 | [Google Summer of Code 2024 Timeline](https://developers.google.com/open-source/gsoc/timeline?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-_rKmaXoYjQIRMIB5ww_TJEgv5XSEo8lK4abcyojedtSpe9MhS-trDJuBvCFoaX2n-K8wZq) 57 | 58 | 59 | ## 📋TechDocs: TechDocsCon CFP 60 | On the last Wednesday of each month, the TechDocs team hosts Open Office Hours for anyone to drop in with questions about technical documentation. Our next session will be on Jan 31, 2024, at 8:00 AM PST. You can find details on how to join us on the [public calendar](https://tockify.com/cncf.public.events/detail/643/1706716800000?startms=1706659200000&utm_source=hs_email&utm_medium=email). Hope to see you there! 61 | 62 | 63 | ## ✍️Upcoming CFP Deadlines: 64 | Here are the upcoming deadlines for CFPs: 65 | - [KCD Costa Rica](https://sessionize.com/kubernetes-community-day-costa-rica-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - January 31 66 | - [KCD Romania](https://sessionize.com/kcd-romania-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - January 31 67 | - [KCD Istanbul](https://sessionize.com/kubernetes-community-days-istanbul/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - January 31 68 | - [KCD Texas](https://sessionize.com/kcd-texas?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - February 4 69 | - [GitOpsCon](https://sessionize.com/GitOpsCon-North-America-2024/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - February 4 70 | - [KCD New York](https://sessionize.com/kcd-newyork-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - February 11 71 | - [KCD Munich](https://sessionize.com/kcd-munich-2024-cfp?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - March 31 72 | - [CloudNativeSecurityCon](https://events.linuxfoundation.org/cloudnativesecuritycon-north-america/program/cfp/?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - March 31 73 | - [KCD Italy](https://sessionize.com/kcd-italy-2024?utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-9_TuQzHGK_-Ldi2EzFOBySc36uQ3vVcRX63QsId5ooLD7xTvXMqFCT8UmVrtOX77lZY0gq) - April 4 74 | 75 | 76 | Want to contribute to February's newsletter? 77 | [Contribute Today!](projects@cncf.io) 78 | 79 | 80 | --------------------------------------------------------------------------------