diff --git a/files/en-us/mdn/community/contributing/getting_started/index.md b/files/en-us/mdn/community/contributing/getting_started/index.md index 4030f4413c8b775..62a3faaee4145a2 100644 --- a/files/en-us/mdn/community/contributing/getting_started/index.md +++ b/files/en-us/mdn/community/contributing/getting_started/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} We are an open community of developers, technical writers, and learners building resources for a better Web, regardless of brand, browser, or platform. Anyone can contribute, and each person who does contribute makes us stronger. Together we can continue to drive innovation on the Web to serve the greater good. It starts here, with you. @@ -36,7 +37,7 @@ To contribute, you will need a GitHub account. If you do not already have one, g ### Additional reading and learning material -- [Basic etiquette for open source projects](../../open-source-etiquette/index.md): If you've never contributed to an open source project before, we encourage you to read this document. +- [Basic etiquette for open source projects](/en_US/docs/MDN/Community/Open_source_etiquette): If you've never contributed to an open source project before, we encourage you to read this document. - [Learn web development](https://developer.mozilla.org/docs/Learn): If you are new to HTML, CSS, JavaScript, we have some great content to help you get started. - [Deep dive into collaborating with pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests) diff --git a/files/en-us/mdn/community/contributing/index.md b/files/en-us/mdn/community/contributing/index.md index 12e49ba8ca15fb4..8d204ecf55bd097 100644 --- a/files/en-us/mdn/community/contributing/index.md +++ b/files/en-us/mdn/community/contributing/index.md @@ -7,8 +7,9 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} -- [Getting started](getting-started/index.md) -- [Our repositories](our-repositories/index.md) -- [Translated content](translated-content/index.md) -- [Security vulnerability response](security-vulnerability-response/index.md) +- [Getting started](/en-US/docs/MDN/Community/Contributing/Getting-Started) +- [Our repositories](/en-US/docs/MDN/Community/Contributing/Our_repositories) +- [Translated content](/en-US/docs/MDN/Community/Contributing/Translated_content) +- [Security vulnerability response](/en-US/docs/MDN/Community/Contributing/Security_vulnerability_response) diff --git a/files/en-us/mdn/community/contributing/our_repositories/index.md b/files/en-us/mdn/community/contributing/our_repositories/index.md index c061ac18981b4a1..8383752605b4065 100644 --- a/files/en-us/mdn/community/contributing/our_repositories/index.md +++ b/files/en-us/mdn/community/contributing/our_repositories/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} [MDN Web Docs](https://developer.mozilla.org) is a complex project with lots of moving parts. It's a good idea to get familiar with the projects different repositories. This document intends to help you find the different repositories (repos) you may need when contributing to different parts of the MDN Web Docs project. diff --git a/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md b/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md index aec1ab121a9d5e9..db6f19e90e31c20 100644 --- a/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md +++ b/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} ## A little history diff --git a/files/en-us/mdn/community/contributing/translated_content/index.md b/files/en-us/mdn/community/contributing/translated_content/index.md index abf2d17cc359d8d..e57326e322299cd 100644 --- a/files/en-us/mdn/community/contributing/translated_content/index.md +++ b/files/en-us/mdn/community/contributing/translated_content/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} Since December 14th 2020, MDN has been running on the new GitHub-based [Yari platform](https://github.com/mdn/yari). This has a lot of advantages for MDN, but we've needed to make radical changes to the way in which we handle localization. This is because we've ended up with a lot of unmaintained and out-of-date content in our non-en-US locales, and we want to manage it better in the future. diff --git a/files/en-us/mdn/community/discussions/index.md b/files/en-us/mdn/community/discussions/index.md index f9bf9ba711f24b8..2592d161b4397a4 100644 --- a/files/en-us/mdn/community/discussions/index.md +++ b/files/en-us/mdn/community/discussions/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} On MDN Web Docs, we encourage our community to start and/or engage in discussions around topics related to the overall project. Discussions are categorized by different topic areas. We ask that you keep each discussion focused on the topic at hand instead of covering multiple topics in one discussion. diff --git a/files/en-us/mdn/community/index.md b/files/en-us/mdn/community/index.md index 3134b356fbb34ef..73e38ab1107ab83 100644 --- a/files/en-us/mdn/community/index.md +++ b/files/en-us/mdn/community/index.md @@ -7,18 +7,19 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} -👋 Welcome to MDN Web Docs on GitHub! MDN Web Docs is an open-source, collaborative project that documents web platform technologies, including [HTML](https://developer.mozilla.org/en-US/docs/Web/HTML), [CSS](https://developer.mozilla.org/en-US/docs/Web/CSS), [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript), and [Web APIs](https://developer.mozilla.org/en-US/docs/Web/API). We also provide extensive [learning resources](https://developer.mozilla.org/en-US/docs/Learn) for early-stage developers and students. +👋 Welcome to MDN Web Docs on GitHub! MDN Web Docs is an open-source, collaborative project that documents web platform technologies, including [HTML](/en-US/docs/Web/HTML), [CSS](/en-US/docs/Web/CSS), [JavaScript](/en-US/docs/Web/JavaScript), and [Web APIs](/en-US/docs/Web/API). We also provide extensive [learning resources](/en-US/docs/Learn) for early-stage developers and students. ## Ways to contribute [//]: # "TODO: Remember to update these links as we move the documentation around." - [Fixing known high impact issues](https://github.com/orgs/mdn/projects/25/views/1) -- [Reviewing pull requests](pull-requests/) -- [Help beginners to learn on MDN Web Docs](learn-forum/) +- [Reviewing pull requests](/en-US/docs/MDN/Community/Pull_requests/) +- [Help beginners to learn on MDN Web Docs](/en-US/docs/MDN/Community/Learn_forum/) - [Contribute to MDN Web Docs interactive examples](https://github.com/mdn/interactive-examples/blob/main/CONTRIBUTING.md) -- [Help translate MDN Web Docs](https://developer.mozilla.org/en-US/docs/MDN/Contribute/Localize) +- [Help translate MDN Web Docs](/en-US/docs/MDN/Community/Contributing/Translated_content) - [Help fix known platform issues](https://github.com/mdn/yari/issues) - [Help us keep browser compatibility data up to date.](https://github.com/mdn/browser-compat-data) diff --git a/files/en-us/mdn/community/issues/content_suggestions_feature_proposals/index.md b/files/en-us/mdn/community/issues/content_suggestions_feature_proposals/index.md index b3880e228999280..21c51adee35b097 100644 --- a/files/en-us/mdn/community/issues/content_suggestions_feature_proposals/index.md +++ b/files/en-us/mdn/community/issues/content_suggestions_feature_proposals/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} We are always interested in hearing from our community about new content or feature suggestions you may have for MDN Web Docs. However, even though we are open to suggestions, we have to keep the following in mind: diff --git a/files/en-us/mdn/community/issues/index.md b/files/en-us/mdn/community/issues/index.md index 21546a7d83e2e26..21b4300347732d0 100644 --- a/files/en-us/mdn/community/issues/index.md +++ b/files/en-us/mdn/community/issues/index.md @@ -7,8 +7,9 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} -[Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) are used to track all bugs and work that has a clear actionable outcome. If you have found a bug with either our content or the platform, please search current open issues against the [relavant repository](../contributing/our-repositories/) to ensure someone has not already reported the issue. If the issue is new, please file an issue using the relavant template available in the repository. +[Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) are used to track all bugs and work that has a clear actionable outcome. If you have found a bug with either our content or the platform, please search current open issues against the [relavant repository](/en_US/docs/MDN/Community/Contributing/Our_repositories/) to ensure someone has not already reported the issue. If the issue is new, please file an issue using the relavant template available in the repository. > NOTE: If an issue has a triage label, we haven't reviewed it yet, and you shouldn't begin work on it. @@ -79,7 +80,7 @@ Most issues need some investigation before work can start, if you need to ask qu If you take on an issue we expect work to happen in a timely manner. If you can no longer take on the task, leave a comment and unassign yourself. -Fork and branch the repository, do your work and open a [pull request](../pull_requests/index.md). +Fork and branch the repository, do your work and open a [pull request](/en_US/docs/MDN/Community/Pull_requests). _(more stuff)_ diff --git a/files/en-us/mdn/community/issues/issue_triage/index.md b/files/en-us/mdn/community/issues/issue_triage/index.md index b9e202c651957c0..0cbf1cacc493e5b 100644 --- a/files/en-us/mdn/community/issues/issue_triage/index.md +++ b/files/en-us/mdn/community/issues/issue_triage/index.md @@ -14,7 +14,7 @@ This document looks at the process for triaging content bugs and getting them re Anyone can report a content bug by writing an issue at using the "Content bug" issue template, or by using the "Report a problem with this content on GitHub" link at the bottom of each MDN page. -Once reported, content bugs are listed at , and are designed to be done by individuals with minimal process requirements. Anyone is welcome to work on a content bug, using the process outlined at [Fixing MDN content bugs](/en-US/docs/MDN/Contribute/Fixing_MDN_content_bugs). +Once reported, content bugs are listed at , and are designed to be done by individuals with minimal process requirements. Anyone is welcome to work on a content bug, using the process outlined at [Fixing MDN content bugs](/en_US/docs/MDN/Community/Issues). ## Overall triage process diff --git a/files/en-us/mdn/community/learn_forum/index.md b/files/en-us/mdn/community/learn_forum/index.md index e95b91dce684589..f4a518c287ae4cd 100644 --- a/files/en-us/mdn/community/learn_forum/index.md +++ b/files/en-us/mdn/community/learn_forum/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} Our [Learn web development](/en-US/docs/Learn) pages get over a million views per month, and have [active forums](https://discourse.mozilla.org/c/mdn/learn/250) where people go to ask for general help, or request that their assessments be marked. We'd love some help with answering posts, and growing our learning community. @@ -30,9 +31,8 @@ In the [MDN learning forum](https://discourse.mozilla.org/c/mdn/learn/250), ther ## How to help -1. First of all, [sign up for an MDN account](/en-US/docs/MDN/Contribute/Getting_started#step_1_create_an_account_on_mdn), if you don't already have one. You don't absolutely need to do this to help in the learning area, but it will be useful in the long run. -2. Also sign up for [Mozilla Discourse](https://discourse.mozilla.org/), if you haven't already. -3. Have a look at [Learn web development](/en-US/docs/Learn) section and gain a basic level of familiarity with what's there, if you haven't already (see the [Structure of the MDN Learning Area](#structure_of_the_mdn_learning_area) section below for help). +1. Sign up for [Mozilla Discourse](https://discourse.mozilla.org/), if you haven't already. +2. Have a look at [Learn web development](/en-US/docs/Learn) section and gain a basic level of familiarity with what's there, if you haven't already (see the [Structure of the MDN Learning Area](#structure_of_the_mdn_learning_area) section below for help). ### Once you are set up diff --git a/files/en-us/mdn/community/mdn_content/index.md b/files/en-us/mdn/community/mdn_content/index.md index 9c23a9df19fd7af..b535f981ebcb55c 100644 --- a/files/en-us/mdn/community/mdn_content/index.md +++ b/files/en-us/mdn/community/mdn_content/index.md @@ -8,6 +8,7 @@ tags: - governance - mdn-content --- +{{MDNSidebar}} Problems with MDN docs are reported as [content repo issues](https://github.com/mdn/content/issues). This article helps you find the _best_ issues to work on, based on your expertise and how much time you have available, and outlines the main steps to fixing them. @@ -50,4 +51,3 @@ If you'd prefer to browse your tasks and choose by technology category instead, 3. Once you've fixed an issue, ask the submitter for a review and, hopefully, they will tell you whether they think more work is required. We will get involved if needed. 4. Once the issue is verified fixed, it can be closed. The person closing the issue can be either the original issue submitter, or an MDN staff member. -> **Note:** When choosing and working on an issue, you might also find our [GitHub best practices](/en-US/docs/MDN/Contribute/GitHub_best_practices) and [Getting started on MDN](/en-US/docs/MDN/Contribute/Getting_started) guides useful. diff --git a/files/en-us/mdn/community/mdn_content/issues/index.md b/files/en-us/mdn/community/mdn_content/issues/index.md index 0bc97f53f297181..217264f6b60e181 100644 --- a/files/en-us/mdn/community/mdn_content/issues/index.md +++ b/files/en-us/mdn/community/mdn_content/issues/index.md @@ -8,5 +8,6 @@ tags: - governance - mdn-content --- +{{MDNSidebar}} TBD diff --git a/files/en-us/mdn/community/mdn_content/pull_requests/index.md b/files/en-us/mdn/community/mdn_content/pull_requests/index.md index 9a00c73539f5f3a..bb7adb83974b72c 100644 --- a/files/en-us/mdn/community/mdn_content/pull_requests/index.md +++ b/files/en-us/mdn/community/mdn_content/pull_requests/index.md @@ -8,6 +8,7 @@ tags: - governance - mdn-content --- +{{MDNSidebar}} ## Overall process diff --git a/files/en-us/mdn/community/open_source_etiquette/index.md b/files/en-us/mdn/community/open_source_etiquette/index.md index 3ec0f7deedde64e..d1064ec2a96df28 100644 --- a/files/en-us/mdn/community/open_source_etiquette/index.md +++ b/files/en-us/mdn/community/open_source_etiquette/index.md @@ -8,6 +8,7 @@ tags: - governance - open-source --- +{{MDNSidebar}} If you've not worked on an open source project (OSP) before, it is a good idea to read this article before starting to contribute to MDN Web Docs (or other open source projects). There are a few best practices to adopt that will help ensure that you and the other project contributors feel valued and safe, and stay productive. @@ -64,7 +65,7 @@ If you receive anything that makes you feel uncomfortable, you should always rep Think about what you want to do on the project. For example, we have a large list of issues filed at on the [contributtors task board](https://github.com/orgs/mdn/projects/25/views/1), broken up by various task types. -You could also contribute by opening [pull requests](../pull-requests/) to fix problems that you come across while reading MDN articles. +You could also contribute by opening [pull requests](/en_US/docs/MDN/Community/Pull_requests) to fix problems that you come across while reading MDN articles. A lot of the work on MDN revolves around writing documentation and code examples, but there are other ways to contribute too: @@ -85,7 +86,7 @@ In many cases, things are like they are on OSPs for a reason. You should read th ## Read the manual -Good OSPs will always make contributor documentation readily available. On GitHub projects, it is usually in the repo's CONTRIBUTING.md file, or sometimes in the project's README.md file. Being a documentation project, MDN content has a [README](https://github.com/mdn/content/blob/main/README.md) and a decent set of contributor docs on the site itself (see [Contributing to MDN](/en-US/docs/MDN/Contribute)). +Good OSPs will always make contributor documentation readily available. On GitHub projects, it is usually in the repo's CONTRIBUTING.md file, or sometimes in the project's README.md file. Being a documentation project, MDN content has a [README](https://github.com/mdn/content/blob/main/README.md) and a decent set of contributor docs on the site itself (see [Contributing to MDN](/en-US/docs/MDN/Community)). Don't be afraid to ask for help, but ALWAYS try to find the answer to your question first before asking. This way you build up your knowledge of the project and become more independent, and don't put unnecessary burden on the other contributors. @@ -93,7 +94,7 @@ Of course, the docs won't always be perfect. If an explanation is hard to find o ## Find out where to ask questions -Always find out where the best place is to ask questions. Good OSPs will always make this clear in their docs (see [ask for help on MDN](/en-US/docs/MDN/Contribute/Getting_started#step_4_ask_for_help)). If you want to ask general questions, then always make use of these channels. Don't just file an issue on GitHub for every question, as it adds noise to the project (see "Make progress, not noise" below). +Always find out where the best place is to ask questions. Good OSPs will always make this clear in their docs (see [ask for help on MDN](/en-US/docs/MDN/Community)). If you want to ask general questions, then always make use of these channels. Don't just file an issue on GitHub for every question, as it adds noise to the project (see "Make progress, not noise" below). ## Make progress, not noise diff --git a/files/en-us/mdn/community/pull_requests/index.md b/files/en-us/mdn/community/pull_requests/index.md index 3ba695eec2f7d7f..909961dbe58b918 100644 --- a/files/en-us/mdn/community/pull_requests/index.md +++ b/files/en-us/mdn/community/pull_requests/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} ## Guidelines for after submitting a pull request @@ -51,14 +52,14 @@ perfectly in accordance with all of these points immediately. It is more important to make sure the content is readable, useful, correct, and not inappropriate, than it is to follow every guideline to the letter. -1. Familiarize yourself with the [MDN Code example guidelines](../../how-to-write/writing-style-guide/code-example-guidelines/index.md) and make sure that code examples follow the guidelines. You’ll get used to them eventually, and we are intending to automatically lint against our guidelines at some point in the future. -1. Familiarize yourself with the [MDN Writing style guide](../../how-to-write/writing-style-guide/index.md), and use it to inform your reviews of new text content. +1. Familiarize yourself with the [MDN Code example guidelines](/en_US/docs/MDN/Writing_guidelines/Writing_style_guide/Code_example_guidelines) and make sure that code examples follow the guidelines. You’ll get used to them eventually, and we are intending to automatically lint against our guidelines at some point in the future. +1. Familiarize yourself with the [MDN Writing style guide](/en_US/docs/MDN/Writing_guidelines/Writing_style_guide), and use it to inform your reviews of new text content. 1. Familiarize yourself with the MDN [pull request guidelines](https://github.com/mdn/content/blob/main/README.md#pull-request-etiquette). The key points here are - You have the right to request more information to help your review if the submitter has not explained why they are making this change. - You have the right to close a pull request if it is too complex and/or contains multiple unrelated changes and ask the submitter to submit their changes in smaller atomic chunks. 1. When reviewing a pull request, use the [GitHub review tools](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Use "Request changes" when submitting a review that will require the submitter to do some more work, or "Approve" if the submission is ready to add and you want to merge it. [Reviewing proposed changes in a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) is also useful if you want more information. -1. Be polite and constructive at all times when writing review comments, or otherwise interacting with the submitter and other community members. We are all bound by [our Code of Conduct](CODE_OF_CONDUCT.md) when contributing to MDN, which means adhering to Mozilla's [Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/). If anyone has engaged in behavior that is potentially illegal or makes you or someone else feel unsafe, unwelcome, or uncomfortable, you are encouraged to [report it](https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/). We want MDN to be a welcoming, friendly community that we can all be proud of. +1. Be polite and constructive at all times when writing review comments, or otherwise interacting with the submitter and other community members. We are all bound by our Code of Conduct when contributing to MDN, which means adhering to Mozilla's [Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/). If anyone has engaged in behavior that is potentially illegal or makes you or someone else feel unsafe, unwelcome, or uncomfortable, you are encouraged to [report it](https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/). We want MDN to be a welcoming, friendly community that we can all be proud of. 1. If a pull request is fine apart from a small typo or some other minor issue, you might want to just fix the issue yourself rather than ask the submitter to change it. You can do this provided the PR has been set up to allow changes (see [Allowing changes to a pull request branch created from a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) for more details). If you are not sure how to make changes to someone else’s pull request, [@vkWeb](https://github.com/vkWeb/) wrote some nice simple instructions on how to do this on the command line; see [ReviewPRCommands](https://gist.github.com/vkWeb/dcec82b079f1edc19478ddb58b0ffc5e). - Alternatively, you can edit files using the GitHub UI — go to the pull request’s "Files changed" tab, find the file you want to edit, and choose "three dot" menu (...) > Edit file. 1. If you don’t understand a content change that you’ve been selected to review, or feel that it is too large and complex for you to deal with, don’t panic! Feel free to reach out to someone else to ask for help, like a colleague, or someone else in your group of topic review owners (if you know who they are). If you are not sure who to approach for help, then ping our `@core-yari-content` group to ask for help. diff --git a/files/en-us/mdn/community/users_teams/index.md b/files/en-us/mdn/community/users_teams/index.md index a807cbb459bc3d1..5daeb1bfc4c626a 100644 --- a/files/en-us/mdn/community/users_teams/index.md +++ b/files/en-us/mdn/community/users_teams/index.md @@ -7,6 +7,7 @@ tags: - community-guidelines - governance --- +{{MDNSidebar}} The success and growth of MDN Web Docs is thanks, in large part, to our community of contributors. There are also employees, contractors and a network of partners who are dedicated to the health, growth and maintenance of the project as a whole. There are also some individuals who have committed a portion of their time to assist with the daily tasks of running MDN Web Docs. These people are part of our invited experts program. To manage all these different groups, we rely heavily on roles and teams within our GitHub organisation. @@ -53,7 +54,7 @@ If you wish to become a member of a team you should start by [filing an issue in To become a member of a team, you are required to: -- Agree to abide by our [Code of conduct](../../CODE_OF_CONDUCT.md). +- Agree to abide by our [Code of conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/). - Agree to Mozilla's [Commit Access Requirements](https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/). - Set up [Two factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) on your GitHub account. @@ -67,7 +68,7 @@ Invited experts are individuals that have demonstrated in depth knowledge in a p Invited experts should: -- Agree to abide by our [Code of conduct](../../CODE_OF_CONDUCT.md). +- Agree to abide by our [Code of conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/). - Agree to Mozilla's [Commit Access Requirements](https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/). - Set up [Two factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) on your GitHub account. @@ -86,7 +87,7 @@ MDN Web Docs also have volunteers and partners who are assigned maintainer right Mantainers should: -- Agree to abide by our [Code of conduct](../../CODE_OF_CONDUCT.md). +- Agree to abide by our [Code of conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/). - Agree to Mozilla's [Commit Access Requirements](https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/). - Set up [Two factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) on your GitHub account. - Have a vouched [Mozillians](https://people.mozilla.org) profile in the [NDA group](https://people.mozilla.org/a/nda/). @@ -95,7 +96,7 @@ Mantainers should: Owners have wide permissions to manage users, teams, maintainer access across repositories in the MDN organisation, maintain repository settings and deploy to production. Owners are currently limited to Mozilla staff and are also bound by all the requirements of the other user levels. In addition to all the responsibilities of the other user levels, owners have the following additional responsibilities: -- Follow and enforce MDN team norms, including the [code of conduct](CODE_OF_CONDUCT.md) and [Mozilla Policies](https://www.mozilla.org/en-US/about/governance/policies/). +- Follow and enforce MDN team norms, including the [code of conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/) and [Mozilla Policies](https://www.mozilla.org/en-US/about/governance/policies/). - Follow and contribute to issues and discussions across the MDN organisation. - Ensure that an issue or pull request gets feedback from one or more members within one week. - Follow MDN organization policies described in this repo, and lead by example. diff --git a/files/en-us/mdn/writing_guidelines/index.md b/files/en-us/mdn/writing_guidelines/index.md index 978d781734c0ee2..ec452dfa815811d 100644 --- a/files/en-us/mdn/writing_guidelines/index.md +++ b/files/en-us/mdn/writing_guidelines/index.md @@ -6,10 +6,9 @@ tags: - meta - writing-guide --- - {{MDNSidebar}} -MDN Web Docs is an open-source project. The sections outlined below describe our guidelines for *what* we document and *how* we do it on MDN Web Docs. To learn about _how to contribute_, see our [contribution guidelines](/en_US/docs/MDN/Community/Contributing). +MDN Web Docs is an open-source project. The sections outlined below describe our guidelines for *what* we document and *how* we do it on MDN Web Docs. To learn about _how to contribute_, see our [contribution guidelines](/en_US/docs/MDN/Community). - [What we write](/en_US/docs/MDN/Writing_guidelines/What_we_write)