Translate in French the Platforms Glossary

.github/ISSUE_TEMPLATE/localization.yml

@@ -0,0 +1,39 @@
+---
+name: Website localization
+description: The introduction, or extension, of a website localization
+title: "[Website Localization] <Language name> (<Short language code>)"
+labels: [website, localization]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Welcome, we are excited to support localizations of the website to languages around the world!
+
+        _Note: While each localization is unique, we encourage you to familiarlize yourself with [past localization PRs](https://github.com/cncf/tag-app-delivery/issues?q=label%3Alocalization+) and the [Kubernetes SIG-Docs localization documentation](https://kubernetes.io/docs/contribute/localization) for general guidelines and lessons learned._
+  - type: dropdown
+    attributes:
+      label: New language
+      description: Is this a completely new localization or extension/improvement of an existing one?
+      options:
+        - First localization (default)
+        - Extending an existing localization to new pages
+        - Updating an existing localization
+      default: 0
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Language code to be used
+      description: Please reference the [SIG-Docs instructions for finding your code](https://kubernetes.io/docs/contribute/localization/#find-your-two-letter-language-code)
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        If this is a new localization, please complete the following items:
+        - [ ] Enable i18n by update website/config.toml and website/i18n/<short-language-code>.toml
+
+        All localizations require the following items:
+        - [ ] Translate some key pages (e.g. content/_short-language-code_/_index.md)
+        - [ ] Local testing
+        - [ ] Reviews by additional native speakers

.github/labeler.yml

@@ -0,0 +1,55 @@
+governance:
+  - changed-files:
+      - any-glob-to-any-file:
+          - governance/**
+
+wg-appdev:
+  - changed-files:
+      - any-glob-to-any-file:
+          - app-development-wg/**
+
+wg-gitops:
+  - changed-files:
+      - any-glob-to-any-file:
+          - gitops-wg/**
+
+wg-infra-lifecycle:
+  - changed-files:
+      - any-glob-to-any-file:
+          - infra-lifecycle-wg/**
+
+wg-platforms:
+  - changed-files:
+      - any-glob-to-any-file:
+          - platforms-wg/**
+
+website:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/**
+
+# Language-specific labels
+language/en:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/content/en/**
+
+language/es:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/content/es/**
+
+language/ja:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/content/ja/**
+
+language/ko:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/content/ko/**
+
+language/zh:
+  - changed-files:
+      - any-glob-to-any-file:
+          - website/content/zh/**

.github/workflows/labeler.yml

@@ -0,0 +1,12 @@
+name: labeler
+
+on: pull_request_target
+
+jobs:
+  triage:
+    permissions:
+      contents: read
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/labeler@v5

.github/workflows/notice-i18n-tasks.yml

@@ -18,7 +18,7 @@ jobs:
       uses: actions/checkout@v4
       with:
         fetch-depth: 1
-    
+
     - name: Checkout
       uses: actions/checkout@v4
       with:
@@ -29,10 +29,18 @@ jobs:
     - name: Check diffs
       id: check-diffs
       run: |
-        updated_files="$(.github/workflows/deep-diff.sh website/content/en ${{ github.sha }} ${{ github.event.pull_request.head.sha }})"
-        echo "${updated_files}" # for debugging
+        git remote add --fetch upstream "https://github.com/${{ github.repository }}.git"
+        ancestor="$(git show-branch --merge-base upstream/${{ github.event.pull_request.base.ref }} ${{ github.event.pull_request.head.sha }})"
+
+        echo "==== ancestor ===="
+        echo "${ancestor}"
+
+        updated_files="$(.github/workflows/deep-diff.sh website/content/en ${ancestor} ${{ github.event.pull_request.head.sha }})"
         echo "count=$(echo $updated_files | grep -v '^$' | wc -l)" >> $GITHUB_OUTPUT
 
+        echo "==== updated files ===="
+        echo "${updated_files}"
+
     - name: Send notice on the issue
       if: steps.check-diffs.outputs.count > 0
       uses: thollander/actions-comment-pull-request@v2

CODEOWNERS

@@ -10,13 +10,13 @@
 #
 # Unless a later match takes precedence, these owners will be requested for
 # review when someone opens a pull request.
-*   @thschue @joshgav @lianmakesthings @kgamanji @angellk @linsun @AloisReitbauer @roberthstrand
+*   @thschue @lianmakesthings @kgamanji @linsun @AloisReitbauer @roberthstrand
 
 # Platforms WG
-/platforms-*/ @thschue @joshgav @lianmakesthings @kgamanji  @angellk @abangser @roberthstrand @krumware @linsun @AloisReitbauer
+/platforms-*/ @thschue @lianmakesthings @kgamanji @abangser @roberthstrand @krumware @linsun @AloisReitbauer @techmaharaj
 
 # Artifacts WG
-/artifacts-*/ @thschue @joshgav @lianmakesthings @kgamanji @angellk @sabre1041 @rchincha @linsun @AloisReitbauer @roberthstrand
+/artifacts-*/ @thschue @lianmakesthings @kgamanji @sabre1041 @rchincha @linsun @AloisReitbauer @roberthstrand
 
 # App Development WG
-/app-development-*/ @thschue @joshgav @lianmakesthings @kgamanji @angellk @linsun @AloisReitbauer @roberthstrand @salaboy @danieloh30 @ThomasVitale
+/app-development-*/ @thschue @lianmakesthings @kgamanji @linsun @AloisReitbauer @roberthstrand @salaboy @danieloh30 @ThomasVitale

README.md

@@ -16,26 +16,23 @@ Full charter here: <https://github.com/cncf/toc/blob/main/tags/tag-charters/app-
 
 ## Meetings
 
-Every two weeks on Wednesday at 16:00 UTC ([convert to your local
-time](https://dateful.com/convert/utc?t=16)).
+Every two weeks on Wednesday at 11:00 ET ([convert to your local
+time](https://dateful.com/convert/eastern-time-et?t=11)).
 
 Meetings are listed on the [main CNCF calendar](https://www.cncf.io/calendar/)
 as well as the [CNCF Community Calendar](https://community.cncf.io/tag-app-delivery/).
 
 * Agenda and Notes: <https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit#>
-* Zoom Meeting: <https://zoom.us/j/7276783015>
-    * Passcode: 77777
+* Zoom Meeting: <https://zoom-lfx.platform.linuxfoundation.org/meeting/98590236563?password=b0335b64-4162-4499-bb61-ff2c7dec2724>
 * Recordings of previous meetings:
     * <https://www.youtube.com/playlist?list=PLjNzvzqUSpxJ0JfD6vrdF5bsuBaJQ2BRT>
     * Prior to April 2021: <https://www.youtube.com/playlist?list=PLj6h78yzYM2OHd1Ht3jiZuucWzvouAAci>
 
 ## Leads
 
 - Lian Li (@lianmakesthings) (Co-Chair, Term: 2024/04/16 - 2026/04/15)
-- Josh Gavant (@joshgav) (Co-Chair, Term: 2023/08/30 - 2025/08/29)
 - Thomas Schuetz (@thschue) (Co-Chair, Term: 2023/08/30 - 2025/08/29)
-- Karena Angell (@angellk) (TL)
-- Roberth Strand (@roberthstrand) (TL)
+- Roberth Strand (@roberthstrand) (Co-Chair, Term: 2024/08/05 - 2026/08/04)
 
 ## TOC Liaisons
 - Katie Gamanji (@kgamanji)
@@ -46,6 +43,8 @@ as well as the [CNCF Community Calendar](https://community.cncf.io/tag-app-deliv
 - Jennifer Strejevitch (@Jenninha)
 - Hongchao Deng (@hongchaodeng)
 - Alex Jones (@AlexsJones)
+- Josh Gavant (@joshgav)
+- Karena Angell (@angellk)
 
 ## Working Groups
 
@@ -59,3 +58,4 @@ The TAG has created the following working groups to investigate and discuss the
 | [Operator](https://github.com/cncf/tag-app-delivery/tree/main/operator-wg)     |                                                                        | Inactive                                                             |
 | [Artifacts](artifacts-wg/README.md)                                            | [artifacts-wg/README.md#chairs](./artifacts-wg/README.md#chairs)       | [artifacts-wg/README.md#meetings](./artifacts-wg/README.md#meetings) |
 | [App Development](app-development-wg/README.md)                                | [app-development-wg/README.md#chairs](./app-development-wg/README.md#chairs) | [app-development-wg/README.md#meetings](./app-development-wg/README.md#meetings) |
+| [Infrastructure Lifecycle](infra-lifecycle-wg/README.md)                       | [infra-lifecycle-wg/README.md#chairs](./infra-lifecycle-wg/README.md#chairs) | [infra-lifecycle-wg/README.md#meetings](./infra-lifecycle-wg/README.md#meetings) |

artifacts-wg/charter/charter.md

@@ -39,6 +39,6 @@ The working group intends to carry out (but is not limited to) the following:
 * Demonstrate via prototypes the use of published schemas to facilitate query and analysis of bundles and content.
 
 [1]: https://artifacthub.io/docs/topics/repositories/
-[2]: https://github.com/cncf/toc/blob/main/tags/tag-charters/app-delivery.mdp-delivery.md#areas-considered-in-scope
+[2]: https://github.com/cncf/toc/blob/main/tags/tag-charters/app-delivery.md#areas-considered-in-scope
 [3]: https://artifacthub.io/docs/topics/repositories/
 [4]: https://knative.dev/docs/concepts/duck-typing/ 

infra-lifecycle-wg/README.md

@@ -0,0 +1,19 @@
+# Infrastructure Lifecycle WG
+
+The [charter](./charter/charter.md) describes the goals and activites of this group.
+
+To contribute please join our Slack channel and/or biweekly meetings.
+
+#wg-infrastructure-lifecycle Slack channel: <https://cloud-native.slack.com/archives/C06USDTN683>. Get an invite at <https://slack.cncf.io/>
+
+## Chairs
+
+- Bruno Schaatsbergen (@bschaatsbergen)
+- Jochen Zehnder (@elft3r)
+- Ryan Nowak (@rynowak)
+
+## Meetings
+
+* Meeting schedule: Bi-weekly on Friday at [17:00 GMT+1](https://dateful.com/convert/utc?t=16)
+    * [Zoom](https://zoom-lfx.platform.linuxfoundation.org/meeting/96148400770?password=767d45df-c7cf-4400-9239-e789115cc85e&invite=true)
+* Agendas and notes: <https://docs.google.com/document/d/1KvNAY8hYZ_PXzyLC3BSnzWBl8w8glpLYuqDIa-Z6Stk/edit>

infra-lifecycle-wg/charter/charter.md

@@ -0,0 +1,72 @@
+# Infrastructure Lifecycle Working Group Charter
+
+## Problem Statement
+
+As the cloud native approach matures, the workloads we run have increasingly complex infrastructure needs. While we all strive to control costs, enforce best practices, and ensure secure configurations, the reality is often fragmented. Today's workloads reside in complex hybrid environments spanning on-premises physical infrastructure, public/private cloud, and Edge/IoT. This heterogeneity creates a significant burden for infrastructure engineers, particularly when it comes to maintaining workloads in production ("Day 10 and beyond"). The complexity for those managing infrastructure is growing rapidly across multiple dimensions.
+
+Despite the complexity and sophistication required, not enough has been done to meet the challenges. We're seeing significant investment in new open source infrastructure projects both in and out of CNCF but effective tooling for cloud native infrastructure lifecycle management remains elusive. The Platform Engineering movement emphasises treating infrastructure as a product, but there's no standardised approach for managing its lifecycle.
+
+While savvy users are embracing cloud native practices, infrastructure requirements are inherently diverse. However, there's an opportunity to champion technology-agnostic best practices. Infrastructure lifecycle management deserves the same level of attention and planning we dedicate to established areas of cloud native development. This ensures security, resilience, manageability, sustainability, and observability. This working group aims to bridge this critical gap by clarifying what a standardised approach for managing the infrastructure lifecycle looks like and develop best practices.
+
+## Deliverable
+
+Develop a framework for managing the lifecycle of infrastructure in public, private, or hybrid cloud environments based on cloud-native principles. This framework will guide end-users in managing infrastructure to ensure it is secure, resilient, manageable, sustainable, and observable.
+
+* **Start by**, collaborating with relevant Technical Advisory Groups (TAGs), Working Groups (WGs), vendors and end-users to integrate domain-specific expertise.
+* **Next**, develop practical examples and reference architectures to guide end-users in applying the Infrastructure Lifecycle framework effectively across varied infrastructure environments.
+* **Finally**, publish real-world case studies and collect feedback from end-users on their experiences with applying the Infrastructure Lifecycle framework.
+
+The key categories for the framework are:
+* Infrastructure as Code
+  * Development processes
+  * Design and abstractions
+* Control planes
+* State management
+* Disaster recovery
+* Automation
+* Testing
+* Observability
+
+## Long-term vision
+After delivering the framework, we will assess its effectiveness and decide whether a longer-term Working Group or TAG is needed. This approach ensures the framework remains relevant and adaptable to evolving infrastructure management needs.
+
+## Out of Scope
+
+* This working group is not intended to endorse or promote any specific infrastructure management tools or technologies.
+* This working group won’t develop a new type of standard to infrastructure lifecycle management.
+* This working group won’t create a new CNCF open source project.
+
+## Examples of known patterns aimed to manage lifecycle of infrastructure
+
+### Infrastructure as Code Tools
+
+There are various tools enabling practitioners to define and manage the lifecycle of infrastructure through code, enabling consistent and scalable deployments of their cloud infrastructure. Tools like Terraform, CloudFormation, Pulumi and Crossplane allow practitioners to describe their infrastructure in a declarative manner, ensuring reliability in managing the lifecycle of cloud infrastructure.
+
+### Infrastructure Tool Orchestration
+
+The growing need for GitOps-style deployments drives demand for orchestrating declarative cloud infrastructure using Infrastructure as Code Tools. These orchestrators manage cloud resources either using native APIs or IaC tools. They offer flexibility across cloud providers and tooling preferences. Tools like TACoS, Crossplane, and AWS Controller for Kubernetes (ACK) exemplify this powerful approach, simplifying cloud infrastructure management.
+
+## Examples of known tools aimed to manage the lifecycle of infrastructure:
+
+Without any claim to comprehensiveness:
+
+* Ansible
+* AWS CloudFormation & AWS CDK
+* Bicep
+* Crossplane
+* Metal³
+* OpenTofu
+* Pulumi
+* Radius
+* Terraform
+* Tinkerbell
+
+## Alignment with TAG App Delivery Charter
+
+The Infrastructure Lifecycle working group tackles the underlying infrastructure abstractions that serve as essential building blocks for platform products, an area addressed by the Platform Working Group. Application delivery is often coupled with infrastructure, think of databases, message queues and runtime environments.
+
+Originally, the Platform Working Group focused on clarifying the coordination between application development and infrastructure delivery. While this remains important, the group's focus has evolved to consider platforms as complete products. This broader perspective necessitates a renewed emphasis on the underlying infrastructure abstractions that provide the essential building blocks for these platform offerings, such as disaster recovery, infrastructure lifecycle state management, testability and more. The Infrastructure Lifecycle Working Group will address such topics in this charter.
+
+## Alignment with TAG Runtime Charter
+
+We partner with the Runtime TAG to ensure that cloud native runtime environments provide the fundamental workload execution abstractions and mechanisms needed to integrate with infrastructure lifecycle management tools. This collaboration focuses on guaranteeing that both runtime and infrastructure layers work cohesively to deliver applications effectively.