Merge branch 'main' into opentelemetry-contribution2024-devbranch2

.cspell/fr-mots.txt

@@ -46,4 +46,168 @@ universelle
 utilisé
 visuel
 votre
-vous
+vous
+l'état
+système
+incluent
+rendre
+signifie
+émettre
+metriques
+produites
+doivent
+transmises
+Pourquoi
+l'essor
+commerciales
+besoin
+répond
+suivant
+principes
+clés
+propriétaire
+générez
+dépendance
+fournisseur
+n'avez
+d'apprendre
+seul
+combinés
+offrent
+équipes
+organisations
+flexibilité
+dont
+informatique
+Extensibilité
+conçu
+extensible
+Quelques
+façon
+étendu
+Ajouter
+receveur
+Collecteur
+afin
+prendre
+venant
+personnalisée
+bibliothèques
+personnalisées
+Créer
+collecteur
+adaptée
+utilisation
+spécifique
+nouvel
+exportateur
+personnalisé
+prend
+propagateur
+contexte
+plupart
+utilisateurs
+n'aient
+d'étendre
+presque
+tous
+niveaux
+Histoire
+trouve
+antérieurs
+créés
+résoudre
+même
+problème
+norme
+décrivant
+manière
+transmettre
+Aucun
+n'étant
+indépendante
+fusionné
+leurs
+offrant
+utilisez
+actuellement
+pouvez
+découvrir
+migrer
+ensuite
+commencer
+Lancez
+directement
+composants
+standardisé
+définissant
+sémantiques
+décrire
+langage
+implémentent
+spécifications
+écosystème
+instrumentent
+automatique
+génèrent
+requérir
+reçoit
+modifie
+autre
+Opérateur
+ressources
+Faas
+variété
+intègrent
+fournir
+défaut
+pris
+fournisseurs
+fournissent
+contribuent
+n’aient
+d’étendre
+conçus
+créer
+gérer
+telles
+outil
+compris
+ainsi
+commerciaux
+d'autres
+génération
+collecte
+gestion
+objectifs
+principaux
+pouvoir
+aisément
+systèmes
+quelque
+soit
+leur
+environnement
+d'exécution
+stockage
+visualisation
+sont
+intentionnellement
+laissés
+d'autres
+comprendre
+sortantes
+logiciel
+d’aujourd’hui
+souhaitez
+jetez
+oeil
+valeurs
+principaux
+suivants
+spécification
+communautaires
+brève
+êtes
+standardisée
+autres

.github/component-label-map.yml

@@ -22,6 +22,10 @@ lang:es:
   - changed-files:
       - any-glob-to-any-file:
           - content/es/**
+lang:fr:
+  - changed-files:
+      - any-glob-to-any-file:
+          - content/fr/**
 sig:cpp:
   - changed-files:
       - any-glob-to-any-file:

.github/component-owners.yml

@@ -80,3 +80,6 @@ components:
   content/es:
     - open-telemetry/docs-maintainers
     - open-telemetry/docs-es-approvers
+  content/fr:
+    - open-telemetry/docs-maintainers
+    - open-telemetry/docs-fr-approvers

content/en/blog/2024/gc-candidates.md

@@ -0,0 +1,36 @@
+---
+title:
+  Announcing the 2024 OpenTelemetry Governance Committee Election Candidates
+linkTitle: 2024 GC Candidates
+date: 2024-10-15
+author: OpenTelemetry Governance Committee
+cSpell:ignore: Baeyens Danielson Marylia
+---
+
+The OpenTelemetry election committee is excited to announce the final list of
+candidates for the upcoming 2024 OpenTelemetry Governance Committee Election!
+
+If you are an
+[eligible voter](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-election.md#voter-eligibility),
+you’ll have the opportunity to continue shaping the future of OpenTelemetry by
+casting your vote between 21 October 2024 00:00 UTC and 23 October 2024 23:59
+UTC. You'll be selecting your preferred candidates to fill the four available
+seats in this year's election.
+
+You can find the candidates' pictures, profile link, and descriptions on the
+[candidates page](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-candidates.md).
+Here are their names:
+
+- Adriana Villela
+- Alolita Sharma
+- Daniel Dyla
+- Jamie Danielson
+- Marylia Gutierrez
+- Morgan McLean
+- Pablo Baeyens Fernández
+- Trask Stalnaker
+
+You can check your eligibility by reviewing
+[this GitHub issue](https://github.com/open-telemetry/community/issues/2329). If
+you are not listed there but believe you have the right to vote, kindly
+[fill out this registration form](https://forms.gle/LBvyRpNwZvqcJxUbA).

content/en/docs/contributing/localization.md

@@ -204,22 +204,50 @@ For more details about the script, run `npm run check:i18n -- -h`.
 
 ## New localizations
 
-(Section To Be Completed soon with information about how to propose a new
-localization.)
+To start a new localization for the OpenTelemetry website,
+[raise an issue](https://github.com/open-telemetry/opentelemetry.io/issues/) to
+share your interest to contribute. Tag all other individuals that are willing to
+write and review translations in the language you want to add. You need at least
+two potential contributors, three would be ideal. Include the following task
+list in your issue as well:
 
-<!--
+```markdown
+- [ ] List at least 2 contributors for the new language: `<@gitHubHandle1>`,
+  `<@gitHubHandle2>`, ...
+- [ ] Localize index page to `<your language>`
+- [ ] Create an issue label for `lang:<shortcode>`
+- [ ] Create org-level group for `<shortcode>` approvers
+- [ ] Update components owners for `content/<shortcode>`
+```
+
+For the `<shortcode>` use the
+[ISO 639-1 code](https://en.wikipedia.org/wiki/ISO_639-1) for the language you
+want to add.
 
-cSpell:ignore: CODEOWNERSHIP Comms
+After you created that issue and have the required amount of contributors,
+maintainers will ask you to provide a pull request with a translation of the
+[index page](https://github.com/open-telemetry/opentelemetry.io/blob/main/content/en/_index.md).
+Make sure that maintainers are allowed to edit your PR, since they will add
+additional changes to your PR that are required to get your localization project
+started.
 
-* Our website supports multiple languages already, so the translated content should live under main/content/<two_letter_code>
-* Our point of reference is how kubernetes is doing their localization, see https://github.com/kubernetes/website
-* We need at least 2 ppl owning that content, so that changes can be approved (CODEOWNERSHIP will help with that)
-* We can start with the translation been hidden until we reach a point where enough material is translated to go live (with maybe some blog post & announcements around it)
-* (Please anticipate that this is guidance on not a fixed set of rules)
+With your first PR merged maintainers will take care of setting up the issue
+label, the org-level group and the component owners.
 
-As stated above this project requires a set of individuals that are happy to take on ownership for their language and work with SIG Comms on implementing this. So any discussion on this page "how to do it" needs to be preceded by a "I volunteer to co-own `<language>`"
+{{% alert title="Important" color="warning" %}}
 
--->
+You don't have to be an existing contributor to the OpenTelemetry project, to
+start a new localization. However you will not be added as a member of the
+[OpenTelemetry GitHub organization](https://github.com/open-telemetry/) or as a
+member of the approvers group for your localization. You will need to satisfy
+the requirements for becoming an established member and approver as outlined in
+the
+[membership guidelines](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md).
+
+When starting the localization project, maintainers will treat your reviews as
+if you are an approver already.
+
+{{% /alert %}}
 
 [main]: https://github.com/open-telemetry/opentelemetry.io/commits/main/
 [multilingual framework]: https://gohugo.io/content-management/multilingual/

content/en/docs/kubernetes/operator/automatic.md

@@ -428,9 +428,16 @@ spec:
           instrumentation>
 ```
 
+See the
+[Python agent configuration docs](/docs/zero-code/python/configuration/#disabling-specific-instrumentations)
+for more details.
+
 #### Learn more {#python-learn-more}
 
-[See the Python agent Configuration docs for more details.](/docs/zero-code/python/configuration/#disabling-specific-instrumentations)
+For Python-specific quirks, see
+[Python OpenTelemetry Operator docs](/docs/zero-code/python/operator/#python-specific-topics)
+and the
+[Python agent configuration docs](/docs/zero-code/python/configuration/).
 
 ### Go
 

content/en/docs/languages/java/_index.md

@@ -9,7 +9,7 @@ cascade:
     instrumentation: 2.8.0
     otel: 1.43.0
     contrib: 1.38.0
-    semconv: 1.27.0
+    semconv: 1.28.0
 weight: 18
 ---
 

content/en/docs/languages/js/instrumentation.md

@@ -1508,7 +1508,7 @@ Now that you have [meters](/docs/concepts/signals/metrics/#meter) initialized.
 you can create
 [metric instruments](/docs/concepts/signals/metrics/#metric-instruments).
 
-### Create counters
+### Using counters
 
 Counters can be used to measure a non-negative, increasing value.
 

content/en/docs/zero-code/python/operator.md

@@ -3,11 +3,26 @@ title: Using the OpenTelemetry Operator to Inject Auto-Instrumentation
 linkTitle: Operator
 aliases: [/docs/languages/python/automatic/operator]
 weight: 30
-cSpell:ignore: distro mkdir uninstrumented virtualenv
+cSpell:ignore: distro grpcio mkdir psutil uninstrumented virtualenv
 ---
 
 If you run your Python service in Kubernetes, you can take advantage of the
 [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator)
 to inject auto-instrumentation without having to modify each of your services
 directly.
 [See the OpenTelemetry Operator Auto-instrumentation docs for more details.](/docs/kubernetes/operator/automatic/)
+
+### Python-specific topics
+
+#### Libraries with binary wheels
+
+Some Python packages we instrument or need in our instrumentation libraries,
+might ship with some binary code. This is the case, for example, of `grpcio` and
+`psutil` (used in `opentelemetry-instrumentation-system-metrics`).
+
+The binary code is tied to a specific C library version (glibc or musl) and to a
+specific Python version. The
+[OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator)
+provides images for a single Python version based on the glibc C library. If you
+want to use it you might need to build your own image operator Docker image for
+Python auto-instrumentation.