Use relative links

COMMUNICATION.md

@@ -2,8 +2,7 @@
 
 ## Document purpose
 
-OpenTelemetry has a [Code of
-Conduct](https://github.com/open-telemetry/community/blob/master/code-of-conduct.md)
+OpenTelemetry has a [Code of Conduct](./code-of-conduct.md)
 where maintainers and community members pledge to foster a welcoming and open
 community. The code of conduct cites examples of unacceptable behavior by
 participants – like harassment, trolling or personal attacks – that would lead to

assets.md

@@ -328,7 +328,7 @@ The OpenTelemetry Bot addresses two common issues:
 
    It is recommended to push to branch names that start with `opentelemetrybot/`, and to add a branch protection
    rule for `opentelemetrybot/**/**` with the same setup as documented for
-   [`dependabot/**/**`](https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md#branch-protection-rule-dependabot). Note that branch protection rule ordering matters, so you will need to
+   [`dependabot/**/**`](docs/how-to-configure-new-repository.md#branch-protection-rule-dependabot). Note that branch protection rule ordering matters, so you will need to
    delete the `**/**` branch protection rule temporarily, then add the `opentelemetrybot/**/**` branch protection
    rule, then add back the `**/**` branch protection rule.
 

code-of-conduct.md

@@ -39,8 +39,7 @@ [email protected], which goes to all GC members. If
 you do not want your report to be received by all GC members, either because you
 want to submit a report anonymously or because one of the GC members has a
 conflict of interest, you may send your report directly to any individual GC
-member. The [current list of
-members](https://github.com/open-telemetry/community/blob/main/community-members.md#governance-committee)
+member. The [current list of members](./community-members.md#governance-committee)
 can be found on our community repository, and you can ping any of them directly
 on [CNCF’s Slack](https://slack.cncf.io)
 

community-members.md

@@ -18,8 +18,8 @@ in alphabetical order:
 
 ## Technical Committee
 
-This is the current Technical Committee, per the [Technical Committee
-Charter](https://github.com/open-telemetry/community/blob/master/tech-committee-charter.md),
+This is the current Technical Committee, per the
+[Technical Committee Charter](./tech-committee-charter.md),
 in alphabetical order:
 
 - [Armin Ruech](https://github.com/arminru), Dynatrace

docs/how-meeting-recordings-upload-works.md

@@ -1,13 +1,13 @@
 # How automatic video upload works
 
-Videos are being recorded using one of [zoom accounts](https://github.com/open-telemetry/community/blob/main/assets.md#zoom-accounts) used by OpenTelemetry. OpenTelemetry zoom accounts are paid for and owned by CNCF.
+Videos are being recorded using one of [zoom accounts](../assets.md#zoom-accounts) used by OpenTelemetry. OpenTelemetry zoom accounts are paid for and owned by CNCF.
 
 ## Video upload process
 
 - All meetings are configured for automatic recording start. No host present necessary.
 - Once meeting is concluded, all participants need to leave the meeting room so the recording will be uploaded to zoom cloud.
 - Every recorded meeting (of length 1 minute or longer) is picked up by
-  [Zapier](https://github.com/open-telemetry/community/blob/main/assets.md#zapier-account) (https://zapier.com).
+  [Zapier](../assets.md#zapier-account) (https://zapier.com).
   Zapier is configured to automatically post links of the Zoom cloud recordings
   (along with the meeting name, start time and duration) to a
   [publicly viewable Google spreadsheet](https://docs.google.com/spreadsheets/d/1SYKfjYhZdm2Wh2Cl6KVQalKg_m4NhTPZqq-8SzEVO6s).
@@ -24,7 +24,7 @@ Videos are being recorded using one of [zoom accounts](https://github.com/open-t
 
 ### Steps to find the missing video
 
-- Find the zoom account corresponding to the meeting link. Mapping from static rooms to the account may be found in the zoom bombing document referred from [this page](https://github.com/open-telemetry/community/blob/main/docs/how-to-handle-public-calendar.md#zoom-bombing-prevention).
+- Find the zoom account corresponding to the meeting link. Mapping from static rooms to the account may be found in the zoom bombing document referred from [this page](../docs/how-to-handle-public-calendar.md#zoom-bombing-prevention).
 - If non OpenTelemetry zoom account was used, there will be no recording available. Please contact the owner of the zoom account linked from the event.
 - In the zoom account, check if the meeting recording present. If recording is there, it is a Zapier integration issue.
 - If recording is missing in zoom account, check the meeting room settings. Make sure that automatic meeting recording is enabled.

elections/2021/governance-committee-election.md

@@ -79,7 +79,7 @@ As per
 anybody is eligible to run for the Governance Committee. During the “call for
 nomination” period, people can be nominated or nominate themselves by
 submitting a Pull Request adding said candidate to the
-[governance-committee-candidates.md](https://github.com/open-telemetry/community/blob/master/elections/2021/governance-committee-candidates.md)
+[governance-committee-candidates.md](./governance-committee-candidates.md)
 file in the OpenTelemetry community repository. The template in that file includes
 the following columns:
 * Full name

elections/2022/governance-committee-election.md

@@ -17,7 +17,7 @@ We highly encourage participation in this election cycle to ensure that the comm
 
 # TL;DR
 
-* If you've been nominated or are willing to nominate yourself: check the [charter document](https://github.com/open-telemetry/community/blob/main/governance-charter.md) and confirm you are ready for the commitment. Make sure to provide all necessary information before 8 October 2022 00:00 UTC
+* If you've been nominated or are willing to nominate yourself: check the [charter document](../../governance-charter.md) and confirm you are ready for the commitment. Make sure to provide all necessary information before 8 October 2022 00:00 UTC
 * If you are an active community member: confirm that you are on the voters list (see [election announcements issue](https://github.com/open-telemetry/community/issues/1173)) or register yourself before 18 October 2022 00:00 UTC.
 * Vote between 18 October 2022 00:00 UTC and 20 October 2022 23:59 UTC via the [voting link](https://vote.heliosvoting.org/helios/elections/76558134-3384-11ed-8688-02871af94755/view)
 * Keep being awesome and contributing to the project!
@@ -52,7 +52,7 @@ The election committee should evaluate the following alternatives for the 2023 e
 
 # Nominations
 
-As per [the charter document](../../governance-charter.md#elections), anybody is eligible to run for the Governance Committee. During the "call for nomination" period, people can be nominated or nominate themselves by submitting a Pull Request adding said candidate to the [governance-committee-candidates.md](https://github.com/open-telemetry/community/blob/main/elections/2022/governance-committee-candidates.md) file in the OpenTelemetry community repository. The template in that file includes the following columns:
+As per [the charter document](../../governance-charter.md#elections), anybody is eligible to run for the Governance Committee. During the "call for nomination" period, people can be nominated or nominate themselves by submitting a Pull Request adding said candidate to the [governance-committee-candidates.md](./governance-committee-candidates.md) file in the OpenTelemetry community repository. The template in that file includes the following columns:
 
 * Full name
 * GitHub alias
@@ -68,14 +68,14 @@ The Governance Committee or appointed people will contact every nominee directly
 
 # Voter Eligibility
 
-All [members of standing](https://github.com/open-telemetry/community/blob/main/governance-charter.md#members-of-standing) will automatically be eligible to vote. To confirm your eligibility status, see the [election announcements issue](https://github.com/open-telemetry/community/issues/1173). If your code contributions do not meet eligibility requirements but you believe your non-code contributions should make you eligible to vote, you can request an exemption by submitting an exemption [request form](https://forms.gle/mEDWyn6G7iCe4bvJ7).
+All [members of standing](../../governance-charter.md#members-of-standing) will automatically be eligible to vote. To confirm your eligibility status, see the [election announcements issue](https://github.com/open-telemetry/community/issues/1173). If your code contributions do not meet eligibility requirements but you believe your non-code contributions should make you eligible to vote, you can request an exemption by submitting an exemption [request form](https://forms.gle/mEDWyn6G7iCe4bvJ7).
 
 One of two options will be available in the form to prove eligibility:
 
 * GitHub handle
 * List either:
   * Your contributions to OpenTelemetry that make you eligible to vote, or
-  * Your non-code contributions per the [Members of Standing section of the charter](https://github.com/open-telemetry/community/blob/main/governance-charter.md#members-of-standing): particularly, your relationship to a well-known project that's taken a hard dependency on OpenTelemetry, or your involvement with a well-known organization's adoption of OpenTelemetry as an end-user.
+  * Your non-code contributions per the [Members of Standing section of the charter](../../governance-charter.md#members-of-standing): particularly, your relationship to a well-known project that's taken a hard dependency on OpenTelemetry, or your involvement with a well-known organization's adoption of OpenTelemetry as an end-user.
 
 All exemption forms are private. Only the current governance and election committee members will have access to this information. The governance committee will discard the lists one month after the election.
 

elections/2023/governance-committee-candidates.md

@@ -226,7 +226,7 @@ mentors of new interns. My goal is to participate in all Outreachy cohorts for
 the next two years.
 
 For your reference, my 2021 platform can be found
-[here](https://github.com/open-telemetry/community/blob/main/elections/2021/governance-committee-candidates.md#Juraci-Paix%C3%A3o-Kr%C3%B6hling).
+[here](../2021/governance-committee-candidates.md#Juraci-Paix%C3%A3o-Kr%C3%B6hling).
 
 Thank you for your support in ensuring the continued growth and success of
 OpenTelemetry.

elections/2024/governance-committee-candidates.md

@@ -61,7 +61,7 @@ Join me in shaping the future of OpenTelemetry. Together, we can build a robust
 - Company: [Dynatrace](https://dynatrace.com)
 - GitHub: [dyladan](https://github.com/dyladan)
 
-I'm Daniel Dyla. I've been a [GC member](https://github.com/open-telemetry/community/blob/main/community-members.md#governance-committee) for 4 years, maintainer of [OpenTelemetry JS](https://github.com/open-telemetry/opentelemetry-js?tab=readme-ov-file#maintainers-open-telemetryjavascript-maintainers) and contributor to the specification for 5 years, and was recently named a [specification sponsor](https://github.com/open-telemetry/community/blob/main/community-members.md#specifications-and-proto) by the Technical Committee in recognition of my contributions. I have contributed to primarily to governance, tracing, metrics, and instrumentation, but have also been involved in logs/events, semantic conventions, organizational process, and tooling work. I have spoken on OpenTelemetry at several conferences including 6 different KubeCons in both Europe and North America, OpenTelemetry Community Day, and Observe 20/20. In addition to speaking, I have immensely enjoyed connecting with other contributors and users at these events.
+I'm Daniel Dyla. I've been a [GC member](../../community-members.md#governance-committee) for 4 years, maintainer of [OpenTelemetry JS](https://github.com/open-telemetry/opentelemetry-js?tab=readme-ov-file#maintainers-open-telemetryjavascript-maintainers) and contributor to the specification for 5 years, and was recently named a [specification sponsor](https://github.com/open-telemetry/community/blob/main/community-members.md#specifications-and-proto) by the Technical Committee in recognition of my contributions. I have contributed to primarily to governance, tracing, metrics, and instrumentation, but have also been involved in logs/events, semantic conventions, organizational process, and tooling work. I have spoken on OpenTelemetry at several conferences including 6 different KubeCons in both Europe and North America, OpenTelemetry Community Day, and Observe 20/20. In addition to speaking, I have immensely enjoyed connecting with other contributors and users at these events.
 
 During my years on the GC I have helped evolve the project from an experimental tracing specification to an industry-standard observability API with thousands of contributors, hundreds of maintainers and approvers, and more than 10 stable implementations. Because of this experience, especially that of a long-time client implementation maintainer, and because of my long involvement with the GC, I am ideally suited to represent the needs of maintainers, approvers, and contributors.
 

gc-check-ins.md

@@ -9,7 +9,7 @@ As defined in the [charter of the GC](./governance-charter.md#regular-check-ins-
 The check in process is as follows:
 
 * For each SIG a GC member is appointed as a GC liaison. The name of that person is listed [here](https://github.com/open-telemetry/community/tree/main?tab=readme-ov-file#special-interest-groups).
-* If a GC member was the sponsor for [the formation of the SIG](https://github.com/open-telemetry/community/blob/main/project-management.md), they are by default the GC liaison for this SIG.
+* If a GC member was the sponsor for [the formation of the SIG](./project-management.md), they are by default the GC liaison for this SIG.
 * If a GC member is the maintainer themselves, they are by default the GC liaison for this SIG.
 * The GC liaison is appointed for the duration of the project lifecycle, or until they do not get reelected into the GC. Outside of that regular duration, a GC liaison can resign by providing a named successor.
 * The GC liaison is responsible to check in with the maintainers at least once per month. This can either happen via a (private, non recorded) meeting or through a text-based conversation initiated by the GC liaison.

governance-charter.md

@@ -61,7 +61,7 @@ Efforts and initiatives that are too large, detailed, or important to be
 resolved in an issue or pull request are referred to as *projects*. These
 larger efforts often require collaboration between subject matter experts,
 the Technical Committee, and OpenTelemetry community members, and involve
-the creation of a SIG. The [project management](https://github.com/open-telemetry/community/blob/main/project-management.md)
+the creation of a SIG. The [project management](./project-management.md)
 document describes the process for creating and executing projects of this size.
 
 The GC is responsible for reviewing project proposals, aligning their execution
@@ -70,7 +70,7 @@ clear goals and are staffed sufficiently to deliver on an agreed upon deadline.
 The Governance Committee is also responsible for deciding if a project is out of
 scope for the OpenTelemetry project.
 
-For proposals that involve [donating](https://github.com/open-telemetry/community/blob/main/guides/contributor/donations.md)
+For proposals that involve [donating](guides/contributor/donations.md)
 code bases to OpenTelemetry, the Governance Committee is responsible for
 performing due diligence in determining if the donation is a strategic
 fit for OpenTelemetry before referring the donation to the TC for

guides/contributor/donations.md

@@ -55,6 +55,6 @@ Committees follow to handle a prospective donation.
 5. If accepted, the contributing organization – particularly if it's a
    commercial entity – must formally acknowledge via the GitHub issue that its
    respective sales and marketing departments have received, understood, and
-   accepted the terms of the [OpenTelemetry marketing guidelines](https://github.com/open-telemetry/community/blob/main/marketing-guidelines.md).
+   accepted the terms of the [OpenTelemetry marketing guidelines](../../marketing-guidelines.md).
 6. Given all of the above, the GitHub issue is closed and the donation moves
    forward as agreed to by the TC and GC.

guides/contributor/membership.md

@@ -57,8 +57,7 @@ Defined by: Member of the OpenTelemetry GitHub organization
     chat, email, and discussion forums)
 - [Joined the Slack channel](https://cloud-native.slack.com/archives/CJFCJHG4Q)
   - [Get an invite to join CNCF](https://slack.cncf.io/)
-- Have read the [contributor
-  guide](https://github.com/open-telemetry/community/blob/main/guides/contributor)
+- Have read the [contributor guide](../../guides/contributor)
 - Actively contributing to 1 or more subprojects.
 - Sponsored by 2 approvers. Note the following requirements for sponsors:
   - Sponsors must have close interactions with the prospective member - e.g.
@@ -72,8 +71,8 @@ Defined by: Member of the OpenTelemetry GitHub organization
   against the
   [OpenTelemetry/community](https://github.com/open-telemetry/community) repo
   - Ensure your sponsors are `@mentioned` on the issue
-  - Complete every item on the checklist ([preview the current version of the
-    template](https://github.com/open-telemetry/community/blob/main/.github/ISSUE_TEMPLATE/membership.md))
+  - Complete every item on the checklist
+    ([preview the current version of the template](../../.github/ISSUE_TEMPLATE/membership.md))
   - Make sure that the list of contributions included is representative of your
     work on the project.
 - Have your sponsoring reviewers reply confirmation of sponsorship: `I support`

guides/contributor/processes.md

@@ -173,8 +173,7 @@ need you to:
   the bot sends you to guide you through the PR process
 
 Reviewers, the people giving the review, are highly encouraged to revisit the
-[Code of
-Conduct](https://github.com/open-telemetry/community/blob/master/code-of-conduct.md)
+[Code of Conduct](../../code-of-conduct.md)
 and must go above and beyond to promote a collaborative, respectful community.
 
 When reviewing PRs from others [The Gentle Art of Patch

mission-vision-values.md

@@ -132,7 +132,7 @@ acknowledging that people come from different backgrounds and cultures.
 There might be situations where community members act in a dubious manner. If
 you have seen or experienced unacceptable behavior or anything that would make
 our community less welcoming, please speak up! See
-[our code of conduct](https://github.com/open-telemetry/community/blob/main/code-of-conduct.md)
+[our code of conduct](./code-of-conduct.md)
 for more information on how to report unacceptable behavior.
 
 While we want to encourage everyone to express themselves in their own way,