Merge branch 'cncf:main' into keda-graduation-proposal

.github/ISSUE_TEMPLATE/archived.md

@@ -0,0 +1,20 @@
+---
+name: Archiving checklist
+about: archiving
+title: "[ARCHIVE] project"
+labels: archive
+assignees: caniszczyk, amye, idvoretskyi, jeefy
+---
+- [ ] TOC vote to archive passed
+- [ ] Move logo to archived on CNCF.io	
+- [ ] Remove from landscape		
+- [ ] Archive maintainers mailing list	
+- [ ] Remove ML from maintainers@ mailing group
+- [ ] Remove/Archive on maintainers.cncf.io
+- [ ] Remove logo from all slide decks	
+- [ ] Remove logo from event sites	
+- [ ] Move logo to archived in artwork	
+- [ ] Archive DevStats (or archive?)	
+- [ ] Notify Speakers team to remove from CFPs	
+- [ ] Remove from service desk or archive	
+- [ ] Remove from CNCF store

CONTRIBUTING.md

@@ -2,28 +2,27 @@
 
 ## Contributing Projects to CNCF
 
-If you're interested in contributing a project to CNCF, please open up an issue here for discussion: https://github.com/cncf/toc/issues
+If you're interested in contributing a project to CNCF, please see the full project proposal process is located [here](https://github.com/cncf/toc/blob/main/process/project_proposals.md).
 
-The full project proposal process is located [here](https://github.com/cncf/toc/blob/main/process/project_proposals.md).
+## Contributing to Technical Advisory Groups and Working Groups
 
-## TOC Contributors
-
-There has been a call from CNCF’s Technical Oversight Committee (TOC) for additional contributors and expertise to help evaluate potential projects and contribute to [CNCF TAGs](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md) and [working groups](https://github.com/cncf/toc#working-groups). With the metaphor of the TOC as an open source project and the TOC [members](https://github.com/cncf/toc#members) as the maintainers, we are making a call for new **TOC Contributors**.
+There has been a call from CNCF’s Technical Oversight Committee (TOC) for contributions to [CNCF TAGs](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md) and [working groups](https://github.com/cncf/toc#working-groups).
 
 Possible ways to contribute:
 
+* Technical content and leadership
 * Tech due diligence for projects
+* White papers
 * Time spent helping projects
-* Liaison with GB
-* CNCF TAGs & working groups (various tasks)
-* Technical content for website
 
-If you are interested in engaging in this way, we would encourage you to issue a pull request to [TOC Contributors](https://github.com/cncf/toc/blob/main/CONTRIBUTORS.md) that you desire to become a TOC Contributor. Although there is not an actual limit of having one Contributor per company, we would encourage CNCF member companies to designate an official TOC Contributor who is tasked with consulting internal experts and expressing a semi-official view on a given project. We will list current TOC Contributors on a page similar to https://www.cncf.io/people/ambassadors/.
+## Getting involved in the TOC itself
 
-This is not only about individual contribution.  It is also about rallying help from your employer, e.g., if you work for a CNCF Member company. Given the [breadth](https://landscape.cncf.io/) of projects represented by cloud native, it is impossible for anyone to be an expert in all technologies that we’re evaluating. We’re particularly interested in Contributors that can act as a focal point for tapping relevant expertise from their organizations and colleagues in order to engage with CNCF discussions in a timely manner.
+We use the [cncf/toc](https://github.com/cncf/toc/) github repository to track ongoing work and discussions. Please see our [README.md](https://github.com/cncf/toc#readme) for all the communication channels. We welcome the community to join us in our public meetings as well.
 
-The TOC already has the pattern of encouraging non-members to make non-binding votes, so no change in the TOC charter is necessary to allow Contributors.
+This is not only about individual contribution.  It is also about rallying help from your employer, e.g., if you work for a CNCF Member company. Given the [breadth](https://landscape.cncf.io/) of projects represented by cloud native, it is impossible for anyone to be an expert in all technologies that we’re evaluating. We’re particularly interested in Contributors that can act as a focal point for tapping relevant expertise from their organizations and colleagues in order to engage with CNCF discussions in a timely manner.
 
 TOC [meetings](https://github.com/cncf/toc#meeting-time) are only two hours a month, which are mainly taken up with project presentations. While Contributors are welcome to share their views during the meeting, the biggest opportunity is to comment on the TOC [mailing list](https://github.com/cncf/toc#mailing-list), on pull requests representing project applications and in voting.
 
-And, just as the biggest contributors to open source projects often become maintainers, becoming an active TOC Contributor is one of the best paths to distinguish oneself ahead of TOC [elections](https://github.com/cncf/toc/blob/main/process/election-schedule.md).
+The TOC welcomes non-binding votes from members of the CNCF community to express their viewpoints.
+
+And, just as the biggest contributors to open source projects often become maintainers, becoming active in TOC and TAG business is one of the best paths to distinguish oneself ahead of TOC [elections](https://github.com/cncf/toc/blob/main/process/election-schedule.md).

DEFINITION.md

@@ -3,7 +3,7 @@
 *Approved by TOC: 2018-06-11*
 
 [العربية](#العربية) (Arabic) | [中文版本](#中文版本) (Chinese) |  [עברית](#עברית) (Hebrew) | [日本語版](#日本語版) (Japanese) | [한국어](#한국어) (Korean) | [Deutsch](#deutsch) (German) | [Español](#español) (Spanish)  
-[Français](#français) (French) | [Polski](#polski) (Polish) | [Português Brasileiro](#português-brasileiro) (Portuguese-BR) | [Português de Portugal](#português-de-portugal) (Portuguese-PT) | [Русский](#русский) (Russian) | [Bahasa Indonesia](#bahasa-indonesia) (Indonesian) | [Türkçe](#türkçe) (Turkish) | [Български](#български) (Bulgarian) | [ไทย](#ไทย) (Thai) | [Magyar](#magyar) (Hungarian) | [Hindi](#हिन्दी) (Indian)
+[Français](#français) (French) | [Polski](#polski) (Polish) | [Português Brasileiro](#português-brasileiro) (Portuguese-BR) | [Português de Portugal](#português-de-portugal) (Portuguese-PT) | [Русский](#русский) (Russian) | [Bahasa Indonesia](#bahasa-indonesia) (Indonesian) | [Türkçe](#türkçe) (Turkish) | [Български](#български) (Bulgarian) | [ไทย](#ไทย) (Thai) | [Magyar](#magyar) (Hungarian) | [Hindi](#हिन्दी) (Indian) | [Nederlands](#nederlands) (Dutch)
 
 Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic
 environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable
@@ -186,3 +186,13 @@ A **Cloud Native Computing Foundation** nyílt forráskódú és szolgáltató-s
 ये तकनीक ढीले युग्मित सिस्टम को सक्षम करती हैं जो लचीला, प्रबंधनीय और अवलोकन योग्य हैं। मजबूत स्वचालन के साथ, वे इंजीनियरों को न्यूनतम परिश्रम के साथ बार-बार और अनुमानित रूप से उच्च-प्रभाव वाले परिवर्तन करने की अनुमति देते हैं।
 
 क्लाउड नेटिव कंप्यूटिंग फाउंडेशन खुले स्रोत, विक्रेता-तटस्थ परियोजनाओं के एक पारिस्थितिकी तंत्र को बढ़ावा देने और बनाए रखने के द्वारा इस प्रतिमान को अपनाने का प्रयास करता है। हम इन नवाचारों को सभी के लिए सुलभ बनाने के लिए अत्याधुनिक पैटर्न का लोकतंत्रीकरण करते हैं।
+
+## Nederlands:
+
+Cloud native technologieën stellen organisaties in staat om schaalbare applicaties te bouwen en te draaien in moderne, dynamische
+omgevingen zoals publieke, private en hybride cloud. Containers, service meshes, microservices, immutable infrastructuur en declaratieve APIs illusteren deze aanpak.
+
+Deze technieken maken los-gekoppelde systemen mogelijk, die veerkrachtig, beheersbaar en observeerbaar zijn. Gecombineerd met robuuste automatisering stellen ze software ontwikkelaars in staat om met grote regelmaat veranderingen met hoge impact aan te brengen, op een voorspelbare wijze en met minimale inspanning.
+
+De Cloud Native Computing Foundation stelt zich als doel om de adoptie van dit paradigma te stimuleren door een eco-systeem van open source en vendor-neutrale projecten aan te moedigen en te faciliteren.
+Wij democratiseren state-of-the art software ontwikkel patterns, om deze innovaties voor iedereen toegankelijk te maken.

FAQ.md

@@ -7,8 +7,7 @@ A FAQ geared towards CNCF TOC and project issues.
 The TOC is a body elected by a variety of constituents. There is a public election schedule:
 https://github.com/cncf/toc/blob/main/process/election-schedule.md
 
-The best way to get involved is to start attending TOC meetings and become an official TOC Contributor:
-https://github.com/cncf/toc/blob/main/CONTRIBUTORS.md
+The best way to get involved is to start attending TOC meetings and especially by participating in TAG(s)/WG(s).
 
 If you have specific focus areas, CNCF TAG meetings are good opportunity to dive in:
 https://github.com/cncf/toc/tree/main/tags
@@ -95,6 +94,8 @@ The main member benefit is to support the cloud native ecosystem and to be publi
 
 ## Do I have to use my real name when contributing via DCO/CLA?
 
-Yes, no pseudonyms or anonymous contributions. The CNCF follows the same tried and true policy in the Linux Kernel and other LF projects. They have proven strong enough to defend the Linux kernel against legal attacks to date
+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.
 
-* https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst#developers-certificate-of-origin-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.
+
+See the full guidelines here: https://github.com/cncf/foundation/blob/main/dco-guidelines.md