From ba60d9bffb72543f895ed2635bf5706e3687954c Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Fri, 3 Jan 2025 18:05:02 +0100 Subject: [PATCH 01/20] chore: meta docs tidy --- files/en-us/_redirects.txt | 39 +-- files/en-us/_wikihistory.json | 48 ---- .../common_web_layouts/index.md | 2 +- .../design_for_all_types_of_users/index.md | 2 +- .../thinking_before_coding/index.md | 2 +- .../what_is_accessibility/index.md | 2 +- .../index.md | 2 +- .../what_software_do_i_need/index.md | 2 +- .../en-us/mdn/at_ten/history_of_mdn/index.md | 222 ------------------ files/en-us/mdn/at_ten/index.md | 25 -- .../community/communication_channels/index.md | 2 +- .../contributing/getting_started/index.md | 52 ---- .../en-us/mdn/community/contributing/index.md | 8 +- .../contributing/our_repositories/index.md | 2 +- .../en-us/mdn/community/discussions/index.md | 2 +- .../mdn/community/getting_started/index.md | 74 ++++++ files/en-us/mdn/community/index.md | 67 ++---- files/en-us/mdn/community/issues/index.md | 2 +- .../community/open_source_etiquette/index.md | 2 +- .../mdn/community/our_repositories/index.md | 80 +++++++ .../security_vulnerability_response/index.md | 2 +- .../translated_content/index.md | 2 +- files/en-us/mdn/index.md | 31 ++- .../mdn/mdn_product_advisory_board/index.md | 65 ----- .../membership/index.md | 108 --------- .../changelog/index.md | 2 +- .../page_structures/sidebars/index.md | 8 +- 27 files changed, 232 insertions(+), 623 deletions(-) delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/index.md delete mode 100644 files/en-us/mdn/at_ten/index.md delete mode 100644 files/en-us/mdn/community/contributing/getting_started/index.md create mode 100644 files/en-us/mdn/community/getting_started/index.md create mode 100644 files/en-us/mdn/community/our_repositories/index.md rename files/en-us/mdn/community/{contributing => }/security_vulnerability_response/index.md (97%) rename files/en-us/mdn/community/{contributing => }/translated_content/index.md (98%) delete mode 100644 files/en-us/mdn/mdn_product_advisory_board/index.md delete mode 100644 files/en-us/mdn/mdn_product_advisory_board/membership/index.md rename files/en-us/mdn/{ => writing_guidelines}/changelog/index.md (99%) diff --git a/files/en-us/_redirects.txt b/files/en-us/_redirects.txt index 1a18b8f9c08b0a7..40058fc2212bf6b 100644 --- a/files/en-us/_redirects.txt +++ b/files/en-us/_redirects.txt @@ -2678,7 +2678,7 @@ /en-US/docs/Detecting_device_orientation /en-US/docs/Web/API/Device_orientation_events/Detecting_device_orientation /en-US/docs/Determining_the_dimensions_of_elements /en-US/docs/Web/API/CSS_Object_Model/Determining_the_dimensions_of_elements /en-US/docs/DeviceAcceleration /en-US/docs/Web/API/DeviceMotionEventAcceleration -/en-US/docs/Devmo:How_to_Help /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/Devmo:How_to_Help /en-US/docs/MDN/Community/Getting_started /en-US/docs/Distribution_options https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/ /en-US/docs/Distribution_options/Add-ons_for_desktop_apps https://extensionworkshop.com/documentation/publish/distribute-for-desktop-apps/ /en-US/docs/Distribution_options/Add-ons_in_the_enterprise https://extensionworkshop.com/documentation/enterprise/ @@ -3545,7 +3545,7 @@ /en-US/docs/Games/Workflows/Touch_Event_Horizon /en-US/docs/Games/Tutorials /en-US/docs/Games/visual_typescript_game_engine /en-US/docs/Games /en-US/docs/Getting_Started_With_NSS https://firefox-source-docs.mozilla.org/security/nss/index.html -/en-US/docs/Getting_started_on_MDN /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/Getting_started_on_MDN /en-US/docs/MDN/Community/Getting_started /en-US/docs/Glossary/404 /en-US/docs/Web/HTTP/Status/404 /en-US/docs/Glossary/502 /en-US/docs/Web/HTTP/Status/502 /en-US/docs/Glossary/AOM /en-US/docs/Glossary/Accessibility_tree @@ -3984,7 +3984,7 @@ /en-US/docs/How_to_Turn_Off_Form_Autocompletion /en-US/docs/Web/Security/Practical_implementation_guides/Turning_off_form_autocompletion /en-US/docs/How_to_check_the_security_state_of_an_XMLHTTPRequest_over_SSL /en-US/docs/Web/API/XMLHttpRequest /en-US/docs/How_to_create_a_DOM_tree /en-US/docs/Web/API/Document_Object_Model/Using_the_Document_Object_Model -/en-US/docs/How_to_start_contributions_to_Mozilla /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/How_to_start_contributions_to_Mozilla /en-US/docs/MDN/Community/Getting_started /en-US/docs/ICC_color_correction_in_Firefox /en-US/docs/Mozilla/Firefox/Releases/3.5/ICC_color_correction_in_Firefox /en-US/docs/IMAP /en-US/docs/Glossary/IMAP /en-US/docs/IPv6 /en-US/docs/Glossary/IPv6 @@ -5790,13 +5790,17 @@ /en-US/docs/MDC:How_to_Help /en-US/docs/MDN/Community/Contributing /en-US/docs/MDN/About /en-US/docs/MDN/Writing_guidelines /en-US/docs/MDN/At_ten/Contributing_to_MDN /en-US/docs/MDN/Community/Contributing +/en-US/docs/MDN/Changelog /en-US/docs/MDN/Writing_guidelines/Changelog +/en-US/docs/MDN/Community/Contributing/Getting_started /en-US/docs/MDN/Community/Getting_started +/en-US/docs/MDN/Community/Contributing/Security_vulnerability_response /en-US/docs/MDN/Community/Security_vulnerability_response +/en-US/docs/MDN/Community/Contributing/Translated_content /en-US/docs/MDN/Community/Translated_content /en-US/docs/MDN/Community/Issues/Issue_triage /en-US/docs/MDN/Community/Issues /en-US/docs/MDN/Community/MDN_content /en-US/docs/MDN/Community/Contributing /en-US/docs/MDN/Community/MDN_content/Issues /en-US/docs/MDN/Community/Issues /en-US/docs/MDN/Community/MDN_content/Pull_requests /en-US/docs/MDN/Community/Pull_requests /en-US/docs/MDN/Community/Users_teams /en-US/docs/MDN/Community/Roles_teams /en-US/docs/MDN/Contribute /en-US/docs/MDN/Community/Contributing -/en-US/docs/MDN/Contribute/Changelog /en-US/docs/MDN/Changelog +/en-US/docs/MDN/Contribute/Changelog /en-US/docs/MDN/Writing_guidelines/Changelog /en-US/docs/MDN/Contribute/Code_sample_guidelines /en-US/docs/MDN/Writing_guidelines/Writing_style_guide/Code_style_guide /en-US/docs/MDN/Contribute/Content /en-US/docs/MDN/Writing_guidelines /en-US/docs/MDN/Contribute/Content/Content_blocks /en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN @@ -5814,8 +5818,8 @@ /en-US/docs/MDN/Contribute/FAQ /en-US/docs/MDN/Community/Contributing /en-US/docs/MDN/Contribute/Feedback /en-US/docs/MDN/Community /en-US/docs/MDN/Contribute/Fixing_MDN_content_bugs /en-US/docs/MDN/Community/Contributing -/en-US/docs/MDN/Contribute/Getting_started /en-US/docs/MDN/Community/Contributing/Getting_started -/en-US/docs/MDN/Contribute/GitHub_beginners /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/MDN/Contribute/Getting_started /en-US/docs/MDN/Community/Getting_started +/en-US/docs/MDN/Contribute/GitHub_beginners /en-US/docs/MDN/Community/Getting_started /en-US/docs/MDN/Contribute/GitHub_best_practices /en-US/docs/MDN/Community/Issues /en-US/docs/MDN/Contribute/GitHub_cheatsheet /en-US/docs/MDN/Community/Issues /en-US/docs/MDN/Contribute/Guidelines /en-US/docs/MDN/Writing_guidelines @@ -5865,7 +5869,7 @@ /en-US/docs/MDN/Contribute/Howto/Write_an_API_reference/Information_contained_in_a_WebIDL_file /en-US/docs/MDN/Writing_guidelines/Howto/Write_an_api_reference/Information_contained_in_a_WebIDL_file /en-US/docs/MDN/Contribute/Howto/Write_an_API_reference/Sidebars /en-US/docs/MDN/Writing_guidelines/Howto/Write_an_api_reference/Sidebars /en-US/docs/MDN/Contribute/Howto/Write_for_SEO /en-US/docs/MDN/Writing_guidelines/Writing_style_guide -/en-US/docs/MDN/Contribute/Localize /en-US/docs/MDN/Community/Contributing/Translated_content +/en-US/docs/MDN/Contribute/Localize /en-US/docs/MDN/Community/Translated_content /en-US/docs/MDN/Contribute/Markdown_in_MDN /en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN /en-US/docs/MDN/Contribute/Open_source_etiquette /en-US/docs/MDN/Community/Open_source_etiquette /en-US/docs/MDN/Contribute/Processes /en-US/docs/MDN/Community/Contributing @@ -5915,16 +5919,16 @@ /en-US/docs/MDN/Contribute/Style_guide/Quicklinks /en-US/docs/MDN/Writing_guidelines/Page_structures/Sidebars /en-US/docs/MDN/Contribute/Style_guide/Specification_tables /en-US/docs/MDN/Writing_guidelines/Page_structures/Specification_tables /en-US/docs/MDN/Contribute/Tagging /en-US/docs/MDN/Writing_guidelines/Howto -/en-US/docs/MDN/Contribute/Tasks /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/MDN/Contribute/Tasks /en-US/docs/MDN/Community/Getting_started /en-US/docs/MDN/Contribute/Tools https://github.com/mdn/yari/tree/main/docs /en-US/docs/MDN/Contribute/Tools/Document_parameters /en-US/docs/MDN /en-US/docs/MDN/Contribute/Tools/KumaScript https://github.com/mdn/yari/tree/main/docs/kumascript /en-US/docs/MDN/Contribute/Tools/KumaScript/Troubleshooting https://github.com/mdn/yari/tree/main/docs/kumascript/troubleshooting-errors.md /en-US/docs/MDN/Contribute/Tools/Sample_server /en-US/docs/MDN -/en-US/docs/MDN/Contribute/Where_is_everything /en-US/docs/MDN/Community/Contributing/Our_repositories +/en-US/docs/MDN/Contribute/Where_is_everything /en-US/docs/MDN/Community/Our_repositories /en-US/docs/MDN/Doc_status/NSPR https://firefox-source-docs.mozilla.org/nspr/index.html /en-US/docs/MDN/Feedback /en-US/docs/MDN/Community -/en-US/docs/MDN/Getting_started /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/MDN/Getting_started /en-US/docs/MDN/Community/Getting_started /en-US/docs/MDN/Guidelines /en-US/docs/MDN/Writing_guidelines /en-US/docs/MDN/Guidelines/CSS_style_guide /en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN /en-US/docs/MDN/Guidelines/Code_guidelines /en-US/docs/MDN/Writing_guidelines/Writing_style_guide/Code_style_guide @@ -5950,11 +5954,13 @@ /en-US/docs/MDN/Kuma/Introduction_to_KumaScript https://github.com/mdn/yari/tree/main/docs/kumascript /en-US/docs/MDN/Kuma/Tools https://github.com/mdn/yari/tree/main/docs /en-US/docs/MDN/Kuma/Troubleshooting_KumaScript_errors https://github.com/mdn/yari/tree/main/docs/kumascript/troubleshooting-errors.md -/en-US/docs/MDN/MDN_Product_Advisory_Board/Members /en-US/docs/MDN/MDN_Product_Advisory_Board -/en-US/docs/MDN/MDN_Product_Avisory_Board /en-US/docs/MDN/MDN_Product_Advisory_Board -/en-US/docs/MDN/MDN_Product_Avisory_Board/Members /en-US/docs/MDN/MDN_Product_Advisory_Board -/en-US/docs/MDN/MDN_Product_Avisory_Board/Membership /en-US/docs/MDN/MDN_Product_Advisory_Board/Membership -/en-US/docs/MDN/Quick_start /en-US/docs/MDN/Community/Contributing/Getting_started +/en-US/docs/MDN/MDN_Product_Advisory_Board https://github.com/mdn/pab/blob/main/about.md +/en-US/docs/MDN/MDN_Product_Advisory_Board/Members https://github.com/mdn/pab/blob/main/about.md +/en-US/docs/MDN/MDN_Product_Advisory_Board/Membership https://github.com/mdn/pab/blob/main/membership.md +/en-US/docs/MDN/MDN_Product_Avisory_Board https://github.com/mdn/pab/blob/main/about.md +/en-US/docs/MDN/MDN_Product_Avisory_Board/Members https://github.com/mdn/pab/blob/main/about.md +/en-US/docs/MDN/MDN_Product_Avisory_Board/Membership https://github.com/mdn/pab/blob/main/membership.md +/en-US/docs/MDN/Quick_start /en-US/docs/MDN/Community/Getting_started /en-US/docs/MDN/Structures /en-US/docs/MDN/Writing_guidelines/Page_structures /en-US/docs/MDN/Structures/:-ms-input-placeholder_pseudo-class /en-US/docs/Web/CSS/:placeholder-shown /en-US/docs/MDN/Structures/API_references/API_reference_sidebars /en-US/docs/MDN/Writing_guidelines/Howto/Write_an_api_reference/Sidebars @@ -5997,10 +6003,7 @@ /en-US/docs/MDN/Writing_guidelines/Research_technology /en-US/docs/MDN/Writing_guidelines/Howto/Research_technology /en-US/docs/MDN/Writing_guidelines/What_we_write/Inclusion_criteria /en-US/docs/MDN/Writing_guidelines/What_we_write/Criteria_for_inclusion /en-US/docs/MDN/Yari https://github.com/mdn/yari/tree/main/docs -/en-US/docs/MDN_at_ten /en-US/docs/MDN/At_ten /en-US/docs/MDN_at_ten/Contributing_to_MDN /en-US/docs/MDN/Community/Contributing -/en-US/docs/MDN_at_ten/History /en-US/docs/MDN/At_ten/History_of_MDN -/en-US/docs/MDN_at_ten/History_of_MDN /en-US/docs/MDN/At_ten/History_of_MDN /en-US/docs/Main_page /en-US/ /en-US/docs/Managing_screen_orientation /en-US/docs/Web/API/CSS_Object_Model/Managing_screen_orientation /en-US/docs/Manipulating_video_using_canvas /en-US/docs/Web/API/Canvas_API/Manipulating_video_using_canvas diff --git a/files/en-us/_wikihistory.json b/files/en-us/_wikihistory.json index 3fd5971032913e9..85736748b969d2f 100644 --- a/files/en-us/_wikihistory.json +++ b/files/en-us/_wikihistory.json @@ -11229,54 +11229,6 @@ "ziyunfei" ] }, - "MDN/At_ten": { - "modified": "2020-12-14T11:30:31.427Z", - "contributors": [ - "fscholz", - "nasimrja", - "chandan987", - "stephaniehobson", - "jsx", - "daniellascandles", - "h8erofthem8tixs", - "jswisher", - "chrisdavidmills", - "wkforever", - "Sheppy" - ] - }, - "MDN/At_ten/History_of_MDN": { - "modified": "2020-12-12T07:24:50.578Z", - "contributors": [ - "bershanskiy", - "Sheppy", - "jswisher", - "jwhitlock", - "stephaniehobson", - "groovecoder" - ] - }, - "MDN/MDN_Product_Advisory_Board": { - "modified": "2019-06-05T12:41:23.682Z", - "contributors": [ - "Sheppy", - "wbamberg", - "alispivak", - "stephaniehobson", - "chrisdavidmills", - "KadirTopal" - ] - }, - "MDN/MDN_Product_Advisory_Board/Membership": { - "modified": "2020-08-24T15:00:45.099Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "alispivak", - "Sheppy", - "KadirTopal" - ] - }, "MDN/Writing_guidelines/Howto/Document_a_CSS_property": { "modified": "2020-02-18T19:54:27.563Z", "contributors": [ diff --git a/files/en-us/learn_web_development/howto/design_and_accessibility/common_web_layouts/index.md b/files/en-us/learn_web_development/howto/design_and_accessibility/common_web_layouts/index.md index 4713df53059cb35..1fa00696d232d19 100644 --- a/files/en-us/learn_web_development/howto/design_and_accessibility/common_web_layouts/index.md +++ b/files/en-us/learn_web_development/howto/design_and_accessibility/common_web_layouts/index.md @@ -68,7 +68,7 @@ These are rules of thumb you can draw on. There are complex designs and exceptio ## Active learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Deeper dive diff --git a/files/en-us/learn_web_development/howto/design_and_accessibility/design_for_all_types_of_users/index.md b/files/en-us/learn_web_development/howto/design_and_accessibility/design_for_all_types_of_users/index.md index 6c9144167128e51..d27822f7a10804d 100644 --- a/files/en-us/learn_web_development/howto/design_and_accessibility/design_for_all_types_of_users/index.md +++ b/files/en-us/learn_web_development/howto/design_and_accessibility/design_for_all_types_of_users/index.md @@ -36,7 +36,7 @@ When you're building a website, one top issue to consider is [Universal Design]( ## Active Learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Dig deeper diff --git a/files/en-us/learn_web_development/howto/design_and_accessibility/thinking_before_coding/index.md b/files/en-us/learn_web_development/howto/design_and_accessibility/thinking_before_coding/index.md index 49a501dc93f34b7..2d0c134d1212317 100644 --- a/files/en-us/learn_web_development/howto/design_and_accessibility/thinking_before_coding/index.md +++ b/files/en-us/learn_web_development/howto/design_and_accessibility/thinking_before_coding/index.md @@ -35,7 +35,7 @@ All of this is called _project ideation_ and is a necessary first step to reach ## Active Learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Deeper dive diff --git a/files/en-us/learn_web_development/howto/design_and_accessibility/what_is_accessibility/index.md b/files/en-us/learn_web_development/howto/design_and_accessibility/what_is_accessibility/index.md index 0f246166cf6ca72..0b404a6aa3ef8b4 100644 --- a/files/en-us/learn_web_development/howto/design_and_accessibility/what_is_accessibility/index.md +++ b/files/en-us/learn_web_development/howto/design_and_accessibility/what_is_accessibility/index.md @@ -27,7 +27,7 @@ Because of physical or technical limitations, maybe your visitors can't experien ## Active learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Dig deeper diff --git a/files/en-us/learn_web_development/howto/tools_and_setup/checking_that_your_web_site_is_working_properly/index.md b/files/en-us/learn_web_development/howto/tools_and_setup/checking_that_your_web_site_is_working_properly/index.md index 6b004f5bdff8f2f..568937a479234cd 100644 --- a/files/en-us/learn_web_development/howto/tools_and_setup/checking_that_your_web_site_is_working_properly/index.md +++ b/files/en-us/learn_web_development/howto/tools_and_setup/checking_that_your_web_site_is_working_properly/index.md @@ -38,7 +38,7 @@ Let's see how to diagnose and solve those problems. ## Active Learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Dig deeper diff --git a/files/en-us/learn_web_development/howto/tools_and_setup/what_software_do_i_need/index.md b/files/en-us/learn_web_development/howto/tools_and_setup/what_software_do_i_need/index.md index 02abe208b77145c..9855860d15e5d3b 100644 --- a/files/en-us/learn_web_development/howto/tools_and_setup/what_software_do_i_need/index.md +++ b/files/en-us/learn_web_development/howto/tools_and_setup/what_software_do_i_need/index.md @@ -45,7 +45,7 @@ Nearly all operating systems by default include a text editor and a browser, whi ## Active Learning -_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Contributing/Getting_started)._ +_There is no active learning available yet. [Please, consider contributing](/en-US/docs/MDN/Community/Getting_started)._ ## Dig deeper diff --git a/files/en-us/mdn/at_ten/history_of_mdn/index.md b/files/en-us/mdn/at_ten/history_of_mdn/index.md deleted file mode 100644 index 6717fa1a441443c..000000000000000 --- a/files/en-us/mdn/at_ten/history_of_mdn/index.md +++ /dev/null @@ -1,222 +0,0 @@ ---- -title: The history of MDN -slug: MDN/At_ten/History_of_MDN -page-type: guide ---- - -{{MDNSidebar}} - -In this talk from 2015, several contributors of the MDN project look at the past ten years of [developer.mozilla.org](/), and at the decade to come. You will hear the story of different wiki software migrations, how a documentation community was built, and many more highlights of the history of the site. The group then also talks about current challenges and projects the MDN community is working on this year. - -
- -{{ EmbedLiveSample('audio', '100%', '70px') }} - -![The Berlin Office](11073502_781006205281080_8135317797319228200_o-600x400.jpg) - -The [2015 Berlin "Hack on MDN"](https://blog.mozilla.org/community/2015/04/17/a-highly-productive-hack-on-mdn-weekend-in-berlin/), where this talk was recorded. - -## Topics - -Here's an overview of what was discussed, with timestamps and some additional details: - -### What is MDN and who is it for?
A place for the Open Web community - -Time: _0:00:00 - 0:07:15_ - -MDN provides useful information for Web technologies, and encourages learning, sharing, and teaching in the open Web community. On MDN, you come together and make things for yourself and for others. - -MDN is also a place for Mozilla engineers, such as Gecko or Firefox hackers, add-on developers, and Firefox OS contributors. - -### The history of MDN: Pre-wiki era – Netscape DevEdge - -Time: _0:07:15 - 0:08:17_ - -In the early days there was _DevEdge_, the developer documentation from Netscape which formed the basis of some of MDN's documentation. Have a look at the past on [archive.org](https://web.archive.org/web/20020819120942/http://devedge.netscape.com/): - -[![Netscape DevEdge](devedge.png)](https://web.archive.org/web/20020819120942/http://devedge.netscape.com/) - -On October 12, 2004, this popular developer website was shut down by AOL, Netscape's parent company. Only a few months later, in February 2005, [Mitchell Baker](https://blog.lizardwrangler.com/) was able [to rescue DevEdge](https://blog.lizardwrangler.com/2005/02/23/devmo-and-devedge-updates/) and reached an agreement with AOL that allowed Mozilla to post, modify, and create new documents based on the former Netscape DevEdge materials. In other words, what happened to the Mozilla source in 1998 finally happened for Netscape's developer documentation as well: **It became open source**. - -Deb Richardson joined the Mozilla Foundation as a Technical Editor and lead the new _DevMo_ project for community driven developer documentation. - -### MediaWiki
The first wiki engine - -Time: _0:08:17 - 0:14:55_ - -With MediaWiki as the new underlying project platform, the Mozilla developer documentation has been made editable for anyone starting in July 2005. A new collaborative element in Mozilla was established and since then anyone is welcome to help making it better and to share knowledge. A new international community began to grow and to translate developer contents into other languages. - -[![MDC MediaWiki](mediawiki.png)](https://web.archive.org/web/20051226031957/https://developer.mozilla.org/en/docs/Main_Page) - -### DekiWiki
The second wiki engine - -Time: _0:14:55 - 0:26:08_ - -In August 2008, the Mozilla Developer Center switched to [MindTouch DekiWiki](https://sourceforge.net/projects/dekiwiki/), a powerful and new content management system and wiki system for technical documentation. This platform change was quite controversial in the community that was used to MediaWiki from 2005 on and built tools around it. During this phase, we started Doc Sprints to re-engage with the community. - -[![MDC DekiWiki](screenshot_2018-07-24_16.06.55.png)](https://web.archive.org/web/20080907231611/https://developer.mozilla.org/en) - -### Kuma
The third and current wiki engine - -Time: _0:26:08 - 0:31:50_ and _0:43:52 - 0:51:35_ - -[Kuma](https://github.com/mdn/kuma), forked from [Kitsune](https://github.com/mozilla/kitsune) in early 2011 and launched on August 3, 2012, is a Mozilla-built wiki platform based on Django with its own [KumaScript](https://github.com/mdn/yari/tree/main/docs/kumascript) macro system which uses Node.js. - -With the code living on GitHub, the community started to contribute to MDN's CMS as well. From now on, hacking on MDN includes both writing documentation and Kuma coding. - -[![MDN KUMA](kuma.png)](https://web.archive.org/web/20121003233220/https://developer.mozilla.org/en-US/) - -### Redesigning MDN
Kuma with the refreshed design - -Time: _0:31:50 - 0:32:22_ and _0:51:35 - 0:58:05_ - -The redesign of MDN was a big project. [Sean Martell](https://www.seanmartell.com/) designed the new MDN visual identity. It was then an iterative process with a beta user group of 3000 MDNers during several months. The new look was behind a "Waffle flag" (MDN's feature flag system). Major shout-outs also to [David Walsh](https://davidwalsh.name/) who was really championing the entire redesign and gave MDN the front-end that it deserves. - -![Waffle flag](waffle-flag.jpg) - -### Community around Open Web docs
Community-driven, browser-agnostic Open Web documentation - -Time: _0:32:22 - 0:36:55_ - -At some point in 2010, especially when [community members and Technical Writers met in Paris](https://hacks.mozilla.org/2010/10/web-standards-doc-sprint-finis/), it became more obvious that MDN's focus is clearly shifting from "Let's document all things Firefox!" to "Let's document the Web!". Documentation has been cleaned up and restructured over the last few years, so that MDN's open Web documentation is browser-agnostic. This material, useful for anyone developing for the Web, is our most popular and most widely used content. - -Different browser vendors have joined every once in a while to help shape this part of MDN. This cross-browser collaboration has been very successful and is appreciated by MDN's readers. - -### Localization communities
MDN serves a global audience in many languages - -Time: _0:36:55 - 0:43:52_ - -Localization is a big part of the Mozilla community; it is a component of almost every project and product. Using Kuma, MDN is also very localizable and suited for the needs of [our l10n community](/en-US/docs/MDN/Community/Contributing/Translated_content). The W3C specifications and other resources describing the Web's functionality have no direct goals, and have communities that provide specs in multiple languages. Especially for beginners, MDN is the first step to explore web technologies, so it's our aim to be there for everyone. MDN has a broad audience and aims to include not only native English speakers. It is appreciated all around the globe. - -### Learning Area - -Time: _0:58:05 - 1:02:46_ - -The MDN [Learning Area](/en-US/docs/Learn_web_development) is a new effort to teach basic web skills. Over the last 10 years, MDN added a lot of advanced material, serving experts with valuable information. This project is focused on materials for beginners, and tries to fill in a lot of knowledge gaps. - -### The future of MDN
What will be different when we celebrate 20 years of MDN? - -Time: _1:02:46 - 1:11:39_ - -Everyone involved with MDN really cares about the web being open and accessible, and that's why we have the localization teams and all of the people contributing. MDN hopes to continue to be a key player in keeping the Web the way we feel it should be. - -One big part of this future is going to be learning resources. There will be a lot more Web developers over the next ten years. - -Another big part of our job is maintaining and updating the information we already have, so we can always serve relevant content to Web developers. - -What is changing and will likely change more in the future, is how information is consumed. Today people searching for information and looking up documentation. In the future, MDN documentation might be delivered directly in code editors, Firefox Developer Tools, and many other developer tools and services. - -## Speakers - -These are the people who are sharing their memories and thoughts, in the order they appear: - -### Justin Crawford
Product Manager, MDN - -![Justin Crawford](hoosteeno.jpg) - -Justin moderates this talk and makes things with code, words, bike parts, and lumber. He is [@hoosteeno](https://mastodon.social/@hoosteeno) on Mastodon.social. - -### Eric "Sheppy" Shepherd
Technical Writer, MDN - -![Eric Shepherd](a2sheppy.png) - -Sheppy has been here documenting for Mozilla since 2006, and has a lot of history (and crazy ideas) when it comes to MDC and MDN over the years. He is [@sheppy](https://x.com/sheppy) on X. - -### Jérémie Patonnier
Technical Writer, MDN - -![Jérémie Patonnier](jeremiepat.jpg) - -Jérémie is a long time contributor to the Mozilla Developer Network, and a professional web developer since 2000. He's advocating web standards and write documentation about web technologies with the will to make them accessible to everybody. He is [@JeremiePat](https://github.com/JeremiePat) on GitHub. - -### Janet Swisher
Community Manager, MDN - -![Janet Swisher](jmswisher.jpg) - -Janet is a Mozilla Community Manager for Mozilla Developer Network. She joined Mozilla in 2010, and has been involved in open source software since 2004 and in technical communication since the 20th century. She is [@jmswisher](https://mastodon.social/@jmswisher) on Mastodon.social. - -### Stormy Peters - -![Stormy Peters](yaacgvya.jpg) - -You can find Stormy at [StormysCorner.com](https://stormyscorner.com/). - -### Ali Spivak
Herder of awesome MDN cats - -![Ali Spivak](iyqi3qpv.jpg) - -Ali Spivak manages content & community on the Mozilla Developer Network and spends her time thinking of ways to help make the Web even more awesome. She is passionate about maintaining a free and open Web, and, after jumping into open source when she joined Mozilla in 2012, has focused on building and participating in the developer communities at Mozilla. She is [@alispivak](https://x.com/alispivak) on X. - -### Jean-Yves Perrier
Technical Writer, MDN - -![Jean-Yves Perrier](teoli2003.png) - -Jean-Yves has been a Technical Writer on MDN since 2010 and joined Mozilla full-time at the end of 2011. He is passionate about the open Web, with 15 years of C++ experience. He is Swiss but lives in London, UK. His Erdös number is 5 and he is [@teoli2003](https://github.com/teoli2003) on GitHub. - -### Florian Scholz
Technical Writer, MDN - -![Florian Scholz](elchi3.jpg) - -Florian is a Technical Writer at Mozilla focused on open web technologies. He is a wiki gnome, gardening the documentation as if it were flowers, and he likes to work with the community toward the goal of documenting the Web and making it accessible to everyone. Florian is passionate about open source, he is based in Bremen, Germany, and commits as [@Elchi3](https://github.com/Elchi3) on GitHub. - -### David Walsh
Web developer, MDN - -![David Walsh](darkwing.png) - -Mozilla Sr. Web Developer, Front-End Engineer, MooTools Core Developer, JavaScript Fanatic, CSS Tinkerer, PHP Hacker, web and open source lover. David's home on the web is [davidwalsh.name](https://davidwalsh.name/). - -### Luke Crouch
Web developer, MDN - -![Luke Crouch](groovecoder.png) - -Luke Crouch is a home-brewer, soccer fan and web developer for Mozilla. He's been developing on the web since 1996, using Firefox since 2004, writing open source software since 2006, and joined Mozilla as the first staff MDN web dev in 2010. Luke is [@groovecoder](https://github.com/groovecoder) on GitHub. - -### Julien (a.k.a. Sphinx)
French localization, MDN - -![Julien](ensemble.png) - -Julien spent many nights and weekends over several month, translating JavaScript articles into French. He is not a developer, but has a background in IT and wants to learn more about new technologies. He contributes to MDN instead of watching TV. - -### Biraj Karmakar
Mozilla Reps Mentor - -![Biraj Karmakar](birajkarmakar.png) - -Biraj is an Open Source Contributor, interested in the FOSS movement and Localizations. - -## Our awesome contributors - -Many more people have done amazing work on MDN: - -- Les Orchard -- John Karahalis -- David Walsh -- Jannis Leidel -- Stephanie Hobson -- James Bennett -- Isac Lagerblad -- Piotrek Koszuliński -- Craig Cook -- Rob Hudson -- John Whitlock -- … - And many more [Kuma contributors.](https://github.com/mdn/kuma/graphs/contributors) - - - -- Chris Mills -- Will Bamberg -- David Bruant -- Thierry Régagnon -- ethertank -- Saurabh Nair -- Deb Richardson -- Sebastian Zartner -- Tooru Fujisawa -- Karen Scarfone -- Niklas Barning -- … - And hundreds more wiki collaborators. diff --git a/files/en-us/mdn/at_ten/index.md b/files/en-us/mdn/at_ten/index.md deleted file mode 100644 index 692816098260763..000000000000000 --- a/files/en-us/mdn/at_ten/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: MDN at 10 -slug: MDN/At_ten -page-type: guide ---- - -{{MDNSidebar}} - -Celebrate 10 years of documenting your Web. - -## The history of MDN - -In early 2005, a small team of idealists set out to create a new, free, community-built online resource for all Web developers. Their brilliant but offbeat idea grew into today's Mozilla Developer Network—the premier resource for all open Web technologies. Ten years later, our global community is bigger than ever, and together we're still creating documentation, sample code and learning resources for all open Web technologies, including CSS, HTML, JavaScript and everything else that makes the open Web as powerful as it is. - -[Learn more about the history](/en-US/docs/MDN/At_ten/History_of_MDN) - -## Contributing to MDN - -For ten years, the MDN community has been documenting the open Web. From fixing simple typos to writing entire suites of an entirely new API, everyone has something to offer and no contribution is too large or too small. We have over 90,000 pages of content that have been written or translated by members of our outstanding community of Mozillians. You can become one of them. - -[Learn more about contributing](/en-US/docs/MDN/Community/Contributing) - -## See also - -- [The history of MDN](/en-US/docs/MDN/At_ten/History_of_MDN) diff --git a/files/en-us/mdn/community/communication_channels/index.md b/files/en-us/mdn/community/communication_channels/index.md index 9c8406a2fc9a10a..ec5ebbbccb37c42 100644 --- a/files/en-us/mdn/community/communication_channels/index.md +++ b/files/en-us/mdn/community/communication_channels/index.md @@ -56,7 +56,7 @@ You can use the forums listed below for discussing code problems. ## Localization channels -Each localization team has its own [method of communication](/en-US/docs/MDN/Community/Contributing/Translated_content). +Each localization team has its own [method of communication](/en-US/docs/MDN/Community/Translated_content). ## Email diff --git a/files/en-us/mdn/community/contributing/getting_started/index.md b/files/en-us/mdn/community/contributing/getting_started/index.md deleted file mode 100644 index 08a86c7e000c942..000000000000000 --- a/files/en-us/mdn/community/contributing/getting_started/index.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Getting started with MDN Web Docs -slug: MDN/Community/Contributing/Getting_started -page-type: mdn-community-guide ---- - -{{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. - -[Join us!](/en-US/docs/MDN/Community/Communication_channels) - -## What can I do to help? - -There are multiple avenues you can take to contribute to MDN, depending on your skill set and interests. Therefore, along with each task, we provide a short description and an approximate time each type of task typically takes. - -> If you're unsure what to do, you can always ask for help in one of [our communication channels](/en-US/docs/MDN/Community/Communication_channels). -> Also note that our small but mighty docs team maintains this repo. To preserve our bandwidth, off-topic conversations will be closed. - -## Primary contribution types - -We have created a [contributors task board](https://github.com/orgs/mdn/projects/25/views/1) to help you find contribution opportunities that will meaningfully impact the project. The board has an overview and separate views for specific contribution types. - -### Getting ready to contribute - -To contribute, you will need a GitHub account. If you do not already have one, go ahead and [sign up](https://github.com/signup) for an account before continuing. If you are new to GitHub, we encourage you to take the following free, self-paced courses and reading material offered by GitHub. With this knowledge, you can focus on your contributions without the burden of learning a new tool at the same time. - -> [!NOTE] -> Do not feel overwhelmed or like you have to read through and complete _all_ of the course work. With the knowledge gained from the "Introduction to GitHub" course, you will be well on your way. - -- [Introduction to GitHub](https://github.com/skills/introduction-to-github) -- [Setting up Git](https://docs.github.com/en/get-started/getting-started-with-git/set-up-git) -- [GitHub workflow](https://docs.github.com/en/get-started/using-github/github-flow) -- [Using Markdown](https://github.com/skills/communicate-using-markdown) - -### Additional reading and learning material - -- [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](/en-US/docs/Learn_web_development): 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) - -Some writing-specific contribution opportunities will require a reasonable understanding of the English language. That said, do not let perfect be the enemy of "good enough." Even if your grammar isn't good, don't worry about it! We have a team of people who aim to ensure that MDN's contents are as good as possible. In addition, someone will be along to ensure your work is tidy and well-written. - -Once you've decided what kind of task you want to work on, it is time to head over to the [contributors task board](https://github.com/orgs/mdn/projects/25/views/1), pick an issue, and let us know by commenting on the issue and tagging the `@mdn/mdn-community-engagement` team. Someone from the team will respond and assign the issue to you. - -This ensures that two people do not work on the same issue, and you will know who to contact should you get stuck. - -### Contributions - -When contributing, you agree to make your contributions available under the [Attribution-ShareAlike license](https://creativecommons.org/licenses/by-sa/4.0/) (or an alternative license already specified by the page you are editing). In addition, code samples are available under [Creative Commons CC-0](https://creativecommons.org/public-domain/cc0/) (a Public Domain dedication). - -> If you have any questions or concerns about anything discussed here, please [contact us](/en-US/docs/MDN/Community/Communication_channels). diff --git a/files/en-us/mdn/community/contributing/index.md b/files/en-us/mdn/community/contributing/index.md index 1fa9be19512a725..5754758cf96c000 100644 --- a/files/en-us/mdn/community/contributing/index.md +++ b/files/en-us/mdn/community/contributing/index.md @@ -6,7 +6,7 @@ page-type: mdn-community-guide {{MDNSidebar}} -- [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) +- [Getting started](/en-US/docs/MDN/Community/Getting_started) +- [Our repositories](/en-US/docs/MDN/Community/Our_repositories) +- [Translated content](/en-US/docs/MDN/Community/Translated_content) +- [Security vulnerability response](/en-US/docs/MDN/Community/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 c097dd17f332cc9..0f31171ef8c0cee 100644 --- a/files/en-us/mdn/community/contributing/our_repositories/index.md +++ b/files/en-us/mdn/community/contributing/our_repositories/index.md @@ -1,6 +1,6 @@ --- title: MDN Web Docs Repositories -slug: MDN/Community/Contributing/Our_repositories +slug: MDN/Community/Our_repositories page-type: mdn-community-guide --- diff --git a/files/en-us/mdn/community/discussions/index.md b/files/en-us/mdn/community/discussions/index.md index c14fb0d74e9a545..de79e2f714a6f45 100644 --- a/files/en-us/mdn/community/discussions/index.md +++ b/files/en-us/mdn/community/discussions/index.md @@ -1,5 +1,5 @@ --- -title: Community discussions +title: GitHub Discussions slug: MDN/Community/Discussions page-type: mdn-community-guide --- diff --git a/files/en-us/mdn/community/getting_started/index.md b/files/en-us/mdn/community/getting_started/index.md new file mode 100644 index 000000000000000..32681b9d7939171 --- /dev/null +++ b/files/en-us/mdn/community/getting_started/index.md @@ -0,0 +1,74 @@ +--- +title: Getting started with MDN Web Docs +short-title: Getting started +slug: MDN/Community/Getting_started +page-type: mdn-community-guide +--- + +{{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 has an impact on millions of readers. +Learn how to contribute and drive innovation on the Open Web. + +## What can I do to help? + +There are multiple avenues you can take to contribute to MDN, depending on your skill set and interests. Therefore, along with each task, we provide a short description and an approximate time each type of task typically takes. +If you're unsure what to do, you can always ask for help in one of [our communication channels](/en-US/docs/MDN/Community/Communication_channels). + +We have created a [contributors task board](https://github.com/orgs/mdn/projects/25/views/1) to help you find contribution opportunities that will meaningfully impact the project. The board has an overview and separate views for specific contribution types. +Note that our small but mighty docs team maintains this repo. +To preserve our bandwidth, off-topic conversations will be closed. + +## What do I need to get started? + +To contribute, you will need a GitHub account. +If you do not already have one, go ahead and [sign up](https://github.com/signup) for an account before continuing. +If you are new to GitHub, we encourage you to take the following free, self-paced courses and reading material offered by GitHub. With this knowledge, you can focus on your contributions without the burden of learning a new tool at the same time. + +- [Introduction to GitHub](https://github.com/skills/introduction-to-github) +- [Setting up Git](https://docs.github.com/en/get-started/getting-started-with-git/set-up-git) +- [GitHub workflow](https://docs.github.com/en/get-started/using-github/github-flow) +- [Using Markdown](https://github.com/skills/communicate-using-markdown) + +> [!NOTE] +> Do not feel overwhelmed or like you have to read through and complete all of the course work. +> With the knowledge gained from the "Introduction to GitHub" course, you will be well on your way. + +We also recommend reading the following learning material: + +- [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](/en-US/docs/Learn_web_development): 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) + +Some writing-specific contribution opportunities will require a reasonable understanding of the English language. +That said, do not let perfect be the enemy of "good enough." Even if your grammar isn't good, don't worry about it! +We have a team of people who aim to ensure that MDN's contents are as good as possible. +In addition, someone will review your work to make sure what gets published is tidy and accurate. + +## Choosing what to work on and getting started + +Once you've decided what sort of task you want to work on, it is time to head over to the [contributors task board](https://github.com/orgs/mdn/projects/25/views/1), pick an issue, and let us know by commenting on the issue and tagging the `@mdn/mdn-community-engagement` team. +Someone from the team will respond with some comments, hints, or guidance. + +Make sure you're not working on something that's already in-progress - it can be frustrating to duplicate or lose work. +If in doubt, ask questions on the issue. + +## Ways to contribute + +Here's a list of ways you can contribute to MDN Web Docs: + +- [Fixing known high impact issues](https://github.com/orgs/mdn/projects/25/views/1) +- [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](/en-US/docs/MDN/Community/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) + +## Contributions + +When contributing, you agree to make your contributions available under the [Attribution-ShareAlike license](https://creativecommons.org/licenses/by-sa/4.0/) (or an alternative license already specified by the page you are editing). +In addition, code samples are available under [Creative Commons CC-0](https://creativecommons.org/public-domain/cc0/) (a Public Domain dedication). + +If you have any questions or concerns about anything discussed here, please [contact us](/en-US/docs/MDN/Community/Communication_channels). diff --git a/files/en-us/mdn/community/index.md b/files/en-us/mdn/community/index.md index 1dae4b8f160212d..e0823ee777d7a40 100644 --- a/files/en-us/mdn/community/index.md +++ b/files/en-us/mdn/community/index.md @@ -1,5 +1,6 @@ --- -title: Community guidelines +title: Community resources +short-title: Resources slug: MDN/Community page-type: mdn-community-guide --- @@ -7,64 +8,38 @@ page-type: mdn-community-guide {{MDNSidebar}} 👋 Welcome to MDN Web Docs, 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_web_development) for early-stage developers and students. - -## Ways to contribute - -Here's a list of ways you can contribute to MDN Web Docs: - -- [Fixing known high impact issues](https://github.com/orgs/mdn/projects/25/views/1) -- [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](/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) +We also provide extensive [learning resources](/en-US/docs/Learn) for early-stage developers and students. ## Community resources -- [Communication channels](/en-US/docs/MDN/Community/Communication_channels) - - - : This page lists communication channels used by the MDN team and our community, with hints on which might be best for you. - -- [Contributing](/en-US/docs/MDN/Community/Contributing) - +- [Getting started](/en-US/docs/MDN/Community/Getting_started) - : This section explains how you can start contributing and the type of contributions we accept. - It covers [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), and [Security vulnerability response steps](/en-US/docs/MDN/Community/Contributing/Security_vulnerability_response). - -- [Open source etiquette](/en-US/docs/MDN/Community/Open_source_etiquette) - - - : This article gives guidance on how to behave when contributing to our open source project including rules for contributing, etiquette, and how to handle conflicts. - -- [Issues](/en-US/docs/MDN/Community/Issues) - + Anyone can contribute, and each person who does contribute has an impact on millions of readers. + Learn how to contribute and drive innovation on the Open Web. +- [Our repositories](/en-US/docs/MDN/Community/Our_repositories) + - : This document describes the GitHub repositories (repos) you may need when contributing to MDN Web Docs. +- [GitHub Issues](/en-US/docs/MDN/Community/Issues) - : Issues are used to track all bugs and work that has a clear actionable outcome. - This article contains guidelines on opening and working on issues and also covers [Issue triage](/en-US/docs/MDN/Community/Issues) and [Content and feature suggestions](/en-US/docs/MDN/Community/Issues/Content_suggestions_feature_proposals). - + This article contains guidelines on opening and working on issues and also covers issue triage and content suggestions. - [Pull requests](/en-US/docs/MDN/Community/Pull_requests) - - : This section covers our guidelines for submitting pull requests and what you should expect from the review process. - - [Roles and teams](/en-US/docs/MDN/Community/Roles_teams) - - : This section provides an overview of the users and teams that are part of the MDN Web Docs project and details what it means to be part of a team. +- [Translated content](MDN/Community/Translated_content) + - : MDN Web Docs Localization information, with details about teams, communication channels, and how to get involved. +- [Open source etiquette](/en-US/docs/MDN/Community/Open_source_etiquette) + - : This article gives guidance on how to behave when contributing to our open source project including rules for contributing, etiquette, and how to handle conflicts. +- [Communication channels](/en-US/docs/MDN/Community/Communication_channels) + - : This page lists communication channels used by the MDN team and our community, with hints on which might be best for you. ## Code of conduct -By participating in and contributing to our projects and discussions, you acknowledge that you have read and agree to the [Mozilla community participation guidelines](https://github.com/mdn/mdn-community/blob/main/CODE_OF_CONDUCT.md). +By participating in and contributing to any of our projects in-person or online, you acknowledge that you have read and agree to the [Mozilla Community Participation Guidelines](https://github.com/mdn/mdn-community/blob/main/CODE_OF_CONDUCT.md) (CPG). -## Get in touch - -You can communicate with the MDN Web Docs team and community using the [communication channels](/en-US/docs/MDN/Community/Communication_channels). - -### General support +## General support We are a small team working hard to keep up with the documentation demands of a continuously changing web ecosystem. -Unfortunately, we can't help with general support questions. -If you're learning to code, you can refer to the following resources: - -- [Learn web development](/en-US/docs/Learn_web_development) -- [MDN Web Docs learn forum](https://discourse.mozilla.org/c/mdn/learn/250) -- [Stack Overflow](https://stackoverflow.com/questions/) +Unfortunately, we can't help with general support questions, such as troubleshooting code. +If you're learning, the [Learn web development](/en-US/docs/Learn_web_development) is a great start, and you can post coding questions or search for answers on [Stack Overflow](https://stackoverflow.com/questions/). -Any issues, discussions, or pull requests opened on repositories asking for general support will be directed here and may be closed and locked. +Issues, discussions, or pull requests on MDN repositories asking for general support will be directed here and may be closed and locked. diff --git a/files/en-us/mdn/community/issues/index.md b/files/en-us/mdn/community/issues/index.md index 5316815665c88df..377c7bc3970af64 100644 --- a/files/en-us/mdn/community/issues/index.md +++ b/files/en-us/mdn/community/issues/index.md @@ -32,7 +32,7 @@ Avoid doing the following: ### Before filing an issue -If you think you've found a bug with the content on MDN Web Docs or with the look and feel of the website, search the current open issues in the [relevant repository](/en-US/docs/MDN/Community/Contributing/Our_repositories) and make sure nobody else has reported the issue. +If you think you've found a bug with the content on MDN Web Docs or with the look and feel of the website, search the current open issues in the [relevant repository](/en-US/docs/MDN/Community/Our_repositories) and make sure nobody else has reported the issue. ### Reporting an issue 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 481039d357f6e07..39061053b806ff1 100644 --- a/files/en-us/mdn/community/open_source_etiquette/index.md +++ b/files/en-us/mdn/community/open_source_etiquette/index.md @@ -90,7 +90,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 [Get in touch](/en-US/docs/MDN/Community#get_in_touch)). 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 [Get in touch](/en-US/docs/MDN/Community/Communication_channels)). 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/our_repositories/index.md b/files/en-us/mdn/community/our_repositories/index.md new file mode 100644 index 000000000000000..0f31171ef8c0cee --- /dev/null +++ b/files/en-us/mdn/community/our_repositories/index.md @@ -0,0 +1,80 @@ +--- +title: MDN Web Docs Repositories +slug: MDN/Community/Our_repositories +page-type: mdn-community-guide +--- + +{{MDNSidebar}} + +[MDN Web Docs](/) 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. + +## Repository tiers + +### Tier 1 + +Code in these repositories is core to the MDN Web Docs project and runs on Mozilla-owned domains. + +- [mdn/content](https://github.com/mdn/content) +- [Yari](https://github.com/mdn/yari) +- [rumba](https://github.com/mdn/rumba) +- [browser-compat-data](https://github.com/mdn/browser-compat-data) +- [interactive-examples](https://github.com/mdn/interactive-examples) +- [bob](https://github.com/mdn/bob) + +A Tier 1 project should have at least 3 members, including at least two with admin permissions. + +### Tier 2 + +These repositories are mainly concentrated on supporting content such as code examples, the MDN Web Docs learn area, localization, and examples projects. Examples include: + +- [dom-examples](https://github.com/mdn/dom-examples) +- [translated-content](https://github.com/mdn/translated-content) +- [learning-area](https://github.com/mdn/learning-area) + +A Tier 2 project should have at least 2 members, including at least one with admin permissions. + +### Tier 3 + +These are repository used for project planning, documenting the project itself, and community engagement. Examples include: + +- [mdn-community](https://github.com/mdn/mdn-community) +- [mdn/mdn](https://github.com/mdn/mdn) +- [content-team-projects](https://github.com/mdn/content-team-projects) + +A Tier 3 project needs 1 admin. + +## Core repos + +- **Core content**: . The most important repo for MDN Web Docs content — this is where all the core English content of the site is stored, and where you'll make all standard changes to page content. +- **MDN Web Docs Platform**: . This is where the MDN Web Docs platform is stored, and where you'll go if you want to make changes to our high level page structure or rendering machinery. +- **Browser compatibility data**: . This is where the data used to generate the browser compatibility tables found on our reference pages is stored ([example](/en-US/docs/Web/HTML/Element/progress#browser_compatibility)). If you have information about browser compatibility of Web features — or are willing and able to do some research and/or experimentation — you can help update MDN's [Browser Compatibility Data](https://github.com/mdn/browser-compat-data/blob/main/docs/contributing.md) +- **Interactive examples**: . This repo stores the example code blocks that are found at the top of many of our reference pages ([example](/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis)). Edit those examples here. +- **Bob** aka Builder of Bits: + This repo stores the rendering code that produce the nice editable, copyable examples found at the top of many of our reference pages ([example](/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis)). +- **Translated content**: . This is where localized content lives. Go here if you want to help translate pages into any of our [actively maintained locales](https://github.com/mdn/translated-content#locales). +- **Workflows**: + A growing collection of reusable GitHub Actions for use on MDN Web Docs repositories. + +## Code example + +### Code examples and demos + +[//]: # "TODO: UPDATE WITH REPO TRIAGE" + +The MDN Web Docs GitHub org contains a huge number of example repos. These generally contain freestanding code examples that are too big or can not be rendered using the [`EmbedLiveSample`](/en-US/docs/MDN/Writing_guidelines/Page_structures/Live_samples#live_sample_macros) macro. These examples are embedded into the content pages using a macro call like this — `\{{EmbedGHLiveSample("css-examples/learn/tasks/grid/grid1.html", '100%', 700)}}`. + +Always remember, if you are updating the code on any given page, you'll need to update the corresponding example repo as well. + +- [**dom-examples**](https://github.com/mdn/dom-examples) +- [**css-examples**](https://github.com/mdn/css-examples) +- [**webaudio-examples**](https://github.com/mdn/webaudio-examples) +- [**webassembly-examples**](https://github.com/mdn/webassembly-examples) +- [**indexeddb-examples**](https://github.com/mdn/indexeddb-examples) +- [**js-examples**](https://github.com/mdn/js-examples) +- [**html-examples**](https://github.com/mdn/html-examples) +- [**web-components-examples**](https://github.com/mdn/web-components-examples) +- [**webextension-examples**](https://github.com/mdn/webextensions-examples) +- [**pwa-examples**](https://github.com/mdn/pwa-examples) +- [**houdini-examples**](https://github.com/mdn/houdini-examples) +- [**headless-examples**](https://github.com/mdn/headless-examples) +- [**perf-examples**](https://github.com/mdn/perf-examples) diff --git a/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md b/files/en-us/mdn/community/security_vulnerability_response/index.md similarity index 97% rename from files/en-us/mdn/community/contributing/security_vulnerability_response/index.md rename to files/en-us/mdn/community/security_vulnerability_response/index.md index 8b09171dafa4755..24517043ed7173e 100644 --- a/files/en-us/mdn/community/contributing/security_vulnerability_response/index.md +++ b/files/en-us/mdn/community/security_vulnerability_response/index.md @@ -1,6 +1,6 @@ --- title: Security vulnerability response steps -slug: MDN/Community/Contributing/Security_vulnerability_response +slug: MDN/Community/Security_vulnerability_response page-type: mdn-community-guide --- diff --git a/files/en-us/mdn/community/contributing/translated_content/index.md b/files/en-us/mdn/community/translated_content/index.md similarity index 98% rename from files/en-us/mdn/community/contributing/translated_content/index.md rename to files/en-us/mdn/community/translated_content/index.md index 49354c4514d1449..4749754c39a1248 100644 --- a/files/en-us/mdn/community/contributing/translated_content/index.md +++ b/files/en-us/mdn/community/translated_content/index.md @@ -1,6 +1,6 @@ --- title: MDN Web Docs Localization -slug: MDN/Community/Contributing/Translated_content +slug: MDN/Community/Translated_content page-type: mdn-community-guide --- diff --git a/files/en-us/mdn/index.md b/files/en-us/mdn/index.md index 8675145a3e8156f..50fab452bb559c8 100644 --- a/files/en-us/mdn/index.md +++ b/files/en-us/mdn/index.md @@ -1,26 +1,23 @@ --- -title: The MDN Web Docs project +title: Contributing to MDN slug: MDN page-type: landing-page --- {{MDNSidebar}} -**MDN Web Docs** is free-to-use resource on which we document the open web platform. Our mission is to provide _developers_ with the _information_ they need to _easily_ build projects on the _web platform_. - -This is the landing page for the MDN Web Docs project itself. Here you'll find guides on how the site works, how we do our documentation, the guidelines and conventions we adhere to, and how you can help. - -We invite everyone to help! MDN Web Docs is an open-source project and accepts contributions. There are many different tasks you can help with, from the simple (proofreading and correcting typos) to the complex (writing API documentation). - -To find out how to help, visit our [Getting started](/en-US/docs/MDN/Community/Contributing/Getting_started) page. If you want to talk to us and ask questions, join the discussion on the [MDN Web Docs chat rooms](/en-US/docs/MDN/Community/Communication_channels#chat_rooms). - -- [Community guidelines](/en-US/docs/MDN/Community) - - - : These guides help you get started with contributing to MDN Web Docs. They also cover topics such as how you can help with tasks and issues, open discussions, and suggest content. If you need help or want to contact us, you'll find the information here. +**MDN Web Docs** is a free-to-use resource documenting open web technologies. +Our mission is to provide developers with the information they need to easily build projects on the web platform. +The resources below describe how the site works, how we write documentation, the guidelines and conventions we follow, and how you can get involved. +- [MDN Web Docs Community](/en-US/docs/MDN/Community) + - : These pages describe how to get started contributing to MDN Web Docs. + You can find out where to look for answers, how to work on GitHub issues, open discussions, or suggest new content. + If you need help or want to get in touch with us, you'll find all the information here. - [Writing guidelines](/en-US/docs/MDN/Writing_guidelines) - - - : These guides provide all the information about how to write for MDN Web Docs. They outline the policies for the type of content we write and the type of content we don't write. You'll also find our writing style guide here, how-to guides to perform various content tasks, and also information about the structure of our different pages. - -- [MDN Product Advisory Board](/en-US/docs/MDN/MDN_Product_Advisory_Board) - - : The MDN Product Advisory Board's mission is to build collaboration between Mozilla, its documentation team, and the key collaborating organizations that help the MDN community collectively maintain MDN Web Docs. + - : These guides describe how to write for MDN Web Docs. + They contain the editorial policies defining the types of content we write and the types of content we don't write. + You'll find our writing style guide, how-to guides for specific tasks, and information about the structure of different types of pages. +- [About MDN Web Docs](/en-US/about) + - : MDN Web Docs serves millions of readers every month and connects developers with the tools and information they need to easily build projects on the open web. + Learn about the history of MDN, the team working on MDN Web Docs, our values, and our partners. diff --git a/files/en-us/mdn/mdn_product_advisory_board/index.md b/files/en-us/mdn/mdn_product_advisory_board/index.md deleted file mode 100644 index 7faf86d0ef2519b..000000000000000 --- a/files/en-us/mdn/mdn_product_advisory_board/index.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: MDN Product Advisory Board -slug: MDN/MDN_Product_Advisory_Board -page-type: guide ---- - -{{MDNSidebar}} - -MDN Web Docs is a trusted source of technical documentation for web developers, built on an open-source web development documentation platform based on wiki technology, which allows virtually anyone to write and edit content. - -The MDN Product Advisory Board's mission is to build collaboration between Mozilla, its documentation team, and the key collaborating organizations that help the MDN community collectively maintain MDN as the most comprehensive, complete, and trusted reference documenting the most important aspects of modern browsers and web standards. - -The Product Advisory Board provides advice from external leaders, helping MDN in its mission to provide unbiased, browser-agnostic documentation of HTML, CSS, JavaScript, and Web APIs to ensure that it's the top reference for standards-based web development. - -## Members - -Current members of the MDN Product Advisory Board are: - -- **Reeza Ali** - Principal Program Manager, Microsoft Edge Developer Experiences - - : Reeza Ali is a Program Manager at Microsoft, who leads the content strategy on the Edge developer relations team. Throughout his Microsoft career, he's been a strong advocate for developer success. Over the past 7+ years, he's led several web content documentation teams and projects at Microsoft. He believes that product content and learning experiences play a pivotal role in creating successful outcomes for developers. He's passionate about content strategy, technology, and technical communication. -- **Sukriti Chadha** - Product Manager, Spotify - - : Sukriti Chadha is a mobile developer-turned-product manager at Spotify where she leads efforts in cross-platform accessibility and developer experience on mobile. She also serves as an Invited Expert at the [W3C WCAG (Web Content Accessibility Guidelines) Working Group](https://www.w3.org/WAI/standards-guidelines/wcag/) and the [Mobile Accessibility Task Force (MATF)](https://www.w3.org/WAI/standards-guidelines/mobile/), where she contributes to industry guidelines for accessible web and mobile applications. She built a new way of making data visualization accessible for visually impaired users, and [open-sourced the Android solution in 2019](https://developer.yahoo.com/blogs/612790529269366784/). Sukriti's product role entails managing developer experience roadmaps, automated testing, and embedding accessibility in the product lifecycle. -- **Hermina Condei** - Head of Product CE, Marketing Operations, Mozilla - - : Hermina Condei leads product management and engineering for MDN Web Docs and platform engineering for SUMO at Mozilla. Over the past years, she's driven company-wide projects focused on access and identity management for employees and the community. She also led the product team in the **Open Innovation Group**, with a focus on managing internal and external stakeholders for the team's portfolio of projects. -- **Dominique Hazael-Massieux** - W3C Web Technology Expert including [Telecommunications Vertical champion](https://www.w3.org/Telco/), [Web Real-Time Communications Working Group](https://www.w3.org/groups/wg/webrtc), [Device and Sensors Working Group](https://www.w3.org/das/) - - : Dominique Hazael-Massieux is part of the W3C staff, leading W3C efforts in developer relations. Dom has been working for W3C since 2000, and in addition to devrel, is currently involved in the standardization of WebRTC, device APIs and WebVR. -- **Brian Kardell** - Developer Advocate, Igalia - - : Brian is a Developer Advocate at Igalia. He participates in W3C where he is Igalia's Advisory Committee Representative and participates in various working groups and community groups. He also has represented the Open JS Foundation there. -- **Eric Meyer** - Developer Advocate, Igalia - - : [Eric](https://meyerweb.com/) ([@meyerweb](https://mastodon.social/@Meyerweb)) is an [author](https://meyerweb.com/eric/writing.html), speaker, blogger, sometimes teacher and consultant, Developer Advocate at [Igalia](https://www.igalia.com/), and co-founder of [An Event Apart](https://aneventapart.com/). He's been working on the Web since 1993 and still finds it deeply compelling. -- **Laura Morinigo** - Web Developer Advocate, Samsung - - : Laura is a software developer, advocate, and mentor. She is passionate about sharing her knowledge and connecting with different tech communities worldwide. Thanks to her contributions, she has been recognized as a Google Developer Expert and a Woman Techmakers Ambassador. As a mentor, she helped startups participating in accelerator programs like Google Launchpad and the World Food Programme by the United Nations. Currently, she is a web developer advocate for Samsung Internet. She contributes to web standards and spreads the word about advanced web features, helping developers create great and more inclusive web apps. -- **Sheila Moussavi** - Principal, Bocoup - - : Sheila is a Principal at [Bocoup](https://www.bocoup.com/about), where she leads a team working on web standards like HTML and CSS, and no-code programming tools like [Scratch](https://www.scratchfoundation.org/). Sheila oversees Bocoup's web standards strategy at the W3C, and is passionate about building more equitable spaces in web standards and stronger connections between the standards process and web developer education. Throughout her career in tech (and previously in health equity and disability justice), she has been focused on cultivating effective, justice-oriented organizations and work spaces. -- **Robert Nyman** - Global Lead for Programs & Initiatives, Web Developer Relations, at Google - - : Robert Nyman is the Global Lead for Developer Feedback & Communities, Web Platform at Google. In his role, he works to make the web the best platform for developers. Prior to Google, Robert was a technical evangelist at Mozilla, focused on the Open Web and the company's various products and initiatives. He lives in Stockholm, and has a passion for traveling and meeting people. He claims the title of "Most Well-Traveled Speaker" on Lanyrd, having presented in 42 countries. -- **Kyle Pflug** - Senior Program Manager, Microsoft Edge Developer Experiences - - : Kyle Pflug is a Program Manager at Microsoft, leading developer relations and community outreach for Microsoft Edge. Over the past five years, he has worked to champion web developer and partner perspectives within Microsoft. He is passionate about making the web more inclusive and accessible to developers across platforms and devices. - -**MDN Product Advisory Board Alumni:** - -- Ali Spivak, Okta -- Daniel Appelquist, Samsung -- Jory Burson, Bocoup -- Joe Medley, Formerly Google -- Meggin Kearney, Google -- Erika Doyle Navara, Microsoft -- Patrick Kettner, Microsoft -- Travis Leithead, Microsoft -- Chris Mills, Mozilla -- Kadir Topal, Mozilla - -## See also - -- [Product Advisory Board Charter & Membership](/en-US/docs/MDN/MDN_Product_Advisory_Board/Membership) diff --git a/files/en-us/mdn/mdn_product_advisory_board/membership/index.md b/files/en-us/mdn/mdn_product_advisory_board/membership/index.md deleted file mode 100644 index 07a9bb2869d9401..000000000000000 --- a/files/en-us/mdn/mdn_product_advisory_board/membership/index.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Product Advisory Board Charter & Membership -slug: MDN/MDN_Product_Advisory_Board/Membership -page-type: guide ---- - -{{MDNSidebar}} - -## 1. Purpose and Objectives - -The primary purpose of the PAB is to provide advice, input, and feedback on content strategy, content prioritization, strategic direction, and platform/site features to MDN's Product Manager and Content Lead. Mozilla will consider input and advice from the PAB; however PAB input and recommendations are non-binding. The primary objectives of the PAB are: - -- Provide feedback into content strategy and prioritization of standards documentation -- Help define product strategy, roadmap, and priorities including: - - - Suggest and comment on Objectives and Key Results (OKRs) - - Suggest and comment on yearly and quarterly content roadmaps - -- Make organizational and individual commitments to contribute to MDN based on the defined strategies, roadmaps and priorities -- Represent and promote user requirements, ensuring that MDN continues to evolve and meet users' needs and challenges -- Suggest and give feedback on new opportunities -- Provide feedback on recruiting and retaining contributors (both corporate and individual) -- Share experience and best practices - -## 2. Membership Selection and Termination - -a. The PAB shall consist of 10 to 12 Members (as defined in the MDN Product Advisory Board Agreement and including those individuals representing a Member organization), to be selected by Mozilla. - -b. There are two types of membership: organizational and individual. Organizations who meet the membership criteria and are accepted as member organizations may nominate up to 2 individuals to serve as their representatives ("Member Representatives" as defined in the MDN Product Advisory Board Agreement) on the PAB. - -c. Organizations/individuals who wish to become PAB members must submit a MDN Product Advisory Board Interest Form. Membership will be subject to review and approval by Mozilla, and notification will be sent to the applicant within 30 days of application. - -d. Membership start dates will be based upon review meeting schedules; any new Members will begin their term on the PAB at the next scheduled review meeting. - -e. Members of the PAB will serve terms of 1 year, renewed automatically for up to 3 years (unless terminated by either party). At the end of the 1-year term, the PAB Member and Mozilla will review membership and decide whether to continue Member participation. - -f. Members may resign in writing, via email to the PAB mailing list. Member organizations can nominate replacements for resigned members before the start of the next review meeting. - -g. Mozilla may terminate a Member in the case of violation of the MDN Advisory Board Agreement, violation of the MDN PAB Code of Conduct, violation of the Antitrust Policy, or if the Member fails to participate in two consecutive review meetings without notice. At that time, a notice will be sent to the principal contact stating that they have been removed as a Member. - -## 3. PAB Membership Qualifications - -a. PAB Members have in-depth industry knowledge and expertise. Members will be knowledgeable about web standards, with the ability and experience to align MDN's overall strategic goals and content plans with evolution of web standards, industry direction, and the needs of developers using MDN's documentation. - -b. Membership in the PAB is limited to organizations and individuals who make significant contributions to MDN and/or the advancement, development, and implementation of web standards. - -c. Member organizations must play a significant role in the creation, implementation, or adoption of Web standards and guidelines. It is also preferred that PAB Member organizations be members of an established Web standards group, such as W3C. Member organizations may nominate up to 2 individual representatives to serve on the board. - -d. Individual Members of the PAB must have at least one of the following qualifications: - -- Plays a significant role in the creation, implementation, or adoption of Web standards; -- Participates in a Web standards group dedicated to the development of specifications for features implemented in a Web browser or used in Web content that is sent to browsers. Participation in W3C or a similar standards group is preferred but not required. Individual Members may also meet this qualification by having served on a standards working group or as an invited expert on an established Web standards working group; -- Is a member of a Web-focused Developer Relations team; -- Works as part of a group doing technical documentation of Web standards; or -- Makes significant, sustained contributions to MDN Web standards documentation as a volunteer. - -## 4. Member Responsibilities and Commitments - -a. Members are expected to provide feedback and responses in a timely manner, and attend a minimum number of review meetings. Participation is welcome from all over the world. Members' expectations include: - -Provide feedback on scheduling annual and quarterly meetings; - -- Attend annual meeting; -- Attend at least 2 quarterly reviews per year; -- Review proposals and provide feedback; -- Join the PAB mailing list; -- and Agree not to promote a specific corporate or individual agenda, particularly in the creation or editing of content on MDN. - -b. Members may be required to provide personal information and material (bios, etc.) for analyst, press, and/or trade publications and press releases. - -c. All Members must sign the MDN Product Advisory Board Agreement and agree to the MDN PAB [Code of Conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/) and Antitrust Policy. - -## 5. MDN PAB Member Benefits - -It is anticipated that PAB membership will have the following benefits: - -- Impact content strategy and priorities for MDN; -- Influence the strategic direction of MDN; Have advance knowledge of MDN plans and development; -- Make suggestions for features and platform improvements to grow MDN audience and contribution; and -- Provide feedback and technical reviews of content. - -## 6. Scheduled and Ad Hoc Meetings - -a. Members will be invited to the following meetings: - -- Annual Product Strategy review meetings to take place between October and December of each calendar year; -- Quarterly content strategy and prioritization review meetings ("Quarterly Reviews); and -- Ad hoc product review/check-in meetings, which can be initiated by Mozilla or any Member as needed ("Ad Hoc Meetings"). - -b. Annual Product Strategy review meetings will review the previous year's progress and make recommendations for MDN's strategy and objectives for the following year. - -c. Annual Product Strategy review meetings can take place in Mozilla headquarters or worldwide office, the offices of a Member, or external locations, as determined by vote of the PAB. Virtual attendance will be accommodated for Members who are unable to attend in person. - -d. Quarterly Reviews and Ad Hoc Meetings will primarily be held via video/conference call, although in-person attendance will be possible at the discretion of Members. - -e. Ad Hoc Meeting dates will depend upon the work in development. Review points will have a specific emphasis such as coordination around product release dates and major features or new specs and standards reaching broad release that require more in-depth coordination and planning beyond the Quarterly Review. - -## 7. Time Commitment and Costs - -a. Members are asked to make a commitment to the PAB for at least 12 months. - -b. Members are asked to commit the time to prepare for, attend (sometimes in person), and participate in regularly scheduled and ad hoc PAB meetings. - -c. Costs for participant travel and living expenses or other involvement are to be paid by the individual board member or the sponsoring organization. - -## See also - -- [Product Advisory Board home](/en-US/docs/MDN/MDN_Product_Advisory_Board) diff --git a/files/en-us/mdn/changelog/index.md b/files/en-us/mdn/writing_guidelines/changelog/index.md similarity index 99% rename from files/en-us/mdn/changelog/index.md rename to files/en-us/mdn/writing_guidelines/changelog/index.md index 0cd3765e74ab63f..b7e0894d6808224 100644 --- a/files/en-us/mdn/changelog/index.md +++ b/files/en-us/mdn/writing_guidelines/changelog/index.md @@ -1,6 +1,6 @@ --- title: MDN Web Docs changelog -slug: MDN/Changelog +slug: MDN/Writing_guidelines/Changelog page-type: guide --- diff --git a/files/en-us/mdn/writing_guidelines/page_structures/sidebars/index.md b/files/en-us/mdn/writing_guidelines/page_structures/sidebars/index.md index 776d61864358d9e..e724d5f67e14ba9 100644 --- a/files/en-us/mdn/writing_guidelines/page_structures/sidebars/index.md +++ b/files/en-us/mdn/writing_guidelines/page_structures/sidebars/index.md @@ -142,10 +142,10 @@ sidebar: details: closed children: - /MDN/Community/Contributing - - /MDN/Community/Contributing/Getting_started - - /MDN/Community/Contributing/Our_repositories - - /MDN/Community/Contributing/Translated_content - - /MDN/Community/Contributing/Security_vulnerability_response + - /MDN/Community/Getting_started + - /MDN/Community/Our_repositories + - /MDN/Community/Translated_content + - /MDN/Community/Security_vulnerability_response - /MDN/Community/Open_source_etiquette - /MDN/Community/Communication_channels - /MDN/Community/Discussions From 080890d2d6a2a393086a24bf688c90c9843cd237 Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Fri, 3 Jan 2025 18:07:13 +0100 Subject: [PATCH 02/20] chore: meta docs tidy --- files/sidebars/mdnsidebar.yaml | 73 ++++++++++------------------------ 1 file changed, 21 insertions(+), 52 deletions(-) diff --git a/files/sidebars/mdnsidebar.yaml b/files/sidebars/mdnsidebar.yaml index 347ad7c5300bbfb..73bef9e88248e03 100644 --- a/files/sidebars/mdnsidebar.yaml +++ b/files/sidebars/mdnsidebar.yaml @@ -4,44 +4,41 @@ sidebar: - type: section link: /MDN - title: community_guidelines - details: closed + details: open children: - /MDN/Community - - title: contributing_to_mdn_web_docs - details: closed - children: - - /MDN/Community/Contributing - - /MDN/Community/Contributing/Getting_started - - /MDN/Community/Contributing/Our_repositories - - /MDN/Community/Contributing/Translated_content - - /MDN/Community/Contributing/Security_vulnerability_response + - /MDN/Community/Getting_started + - /MDN/Community/Our_repositories - /MDN/Community/Open_source_etiquette - - /MDN/Community/Communication_channels - - /MDN/Community/Discussions - - /MDN/Community/Learn_forum - /MDN/Community/Issues - /MDN/Community/Pull_requests + - /MDN/Community/Discussions + - /MDN/Community/Translated_content - /MDN/Community/Roles_teams + - /MDN/Community/Communication_channels + - /MDN/Community/Learn_forum - title: writing_guide details: closed children: - /MDN/Writing_guidelines - /MDN/Writing_guidelines/What_we_write - /MDN/Writing_guidelines/Writing_style_guide + - /MDN/Writing_guidelines/Experimental_deprecated_obsolete + - /MDN/Writing_guidelines/Attrib_copyright_license - title: how_to_guides details: closed children: - /MDN/Writing_guidelines/Howto - - /MDN/Writing_guidelines/Howto/Images_media + - /MDN/Writing_guidelines/Howto/Research_technology + - /MDN/Writing_guidelines/Howto/Markdown_in_MDN - /MDN/Writing_guidelines/Howto/Creating_moving_deleting + - /MDN/Writing_guidelines/Howto/Write_a_new_entry_in_the_glossary - /MDN/Writing_guidelines/Howto/Document_a_CSS_property + - /MDN/Writing_guidelines/Howto/Write_an_api_reference - /MDN/Writing_guidelines/Howto/Document_an_HTTP_header - /MDN/Writing_guidelines/Howto/Document_web_errors - - /MDN/Writing_guidelines/Howto/Research_technology - /MDN/Writing_guidelines/Howto/JSON_Structured_data - - /MDN/Writing_guidelines/Howto/Write_an_api_reference - - /MDN/Writing_guidelines/Howto/Write_a_new_entry_in_the_glossary - - /MDN/Writing_guidelines/Howto/Markdown_in_MDN + - /MDN/Writing_guidelines/Howto/Images_media - title: page_structures details: closed children: @@ -56,19 +53,7 @@ sidebar: - /MDN/Writing_guidelines/Page_structures/Syntax_sections - /MDN/Writing_guidelines/Page_structures/Macros - /MDN/Writing_guidelines/Page_structures/Feature_status - - /MDN/Writing_guidelines/Attrib_copyright_license - - /MDN/Writing_guidelines/Experimental_deprecated_obsolete - - title: advisory_board - details: closed - children: - - /MDN/MDN_Product_Advisory_Board - - /MDN/MDN_Product_Advisory_Board/Membership - - title: history - details: closed - children: - - /MDN/At_ten - - /MDN/At_ten/History_of_MDN - - /MDN/Changelog + l10n: de: history: Geschichte @@ -79,49 +64,37 @@ l10n: how_to_guides: Anleitungen page_structures: Seitenstrukturen en-US: - history: History - advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures es: - history: History - advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures fr: - history: History - advisory_board: Advisory Board community_guidelines: Règles de la communauté contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures ja: - history: History - advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures ko: - history: History - advisory_board: Advisory Board community_guidelines: 커뮤니티 지침 contributing_to_mdn_web_docs: MDN에 기여하기 writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures pt-BR: - history: History - advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides @@ -129,23 +102,19 @@ l10n: ru: history: History advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides page_structures: Page structures zh-CN: - history: History - advisory_board: Advisory Board community_guidelines: 社区指南 contributing_to_mdn_web_docs: 为 MDN 做贡献 writing_guide: 撰写指南 how_to_guides: MDN 写作指南 page_structures: 页面结构 zh-TW: - history: History - advisory_board: Advisory Board - community_guidelines: Community guidelines + community_guidelines: Community resources contributing_to_mdn_web_docs: Contributing to MDN Web Docs writing_guide: Writing guidelines how_to_guides: How-to guides From 7950cb06ca029ad998d008f2cffc657e170d9a5c Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Fri, 3 Jan 2025 18:15:08 +0100 Subject: [PATCH 03/20] chore: meta docs tidy --- files/en-us/mdn/community/index.md | 2 +- files/en-us/mdn/community/issues/index.md | 3 +-- files/en-us/mdn/community/open_source_etiquette/index.md | 7 ++++--- files/en-us/mdn/community/pull_requests/index.md | 2 +- files/en-us/mdn/community/roles_teams/index.md | 3 ++- .../writing_guidelines/attrib_copyright_license/index.md | 2 +- 6 files changed, 10 insertions(+), 9 deletions(-) diff --git a/files/en-us/mdn/community/index.md b/files/en-us/mdn/community/index.md index e0823ee777d7a40..91d44bede549696 100644 --- a/files/en-us/mdn/community/index.md +++ b/files/en-us/mdn/community/index.md @@ -40,6 +40,6 @@ By participating in and contributing to any of our projects in-person or online, We are a small team working hard to keep up with the documentation demands of a continuously changing web ecosystem. Unfortunately, we can't help with general support questions, such as troubleshooting code. -If you're learning, the [Learn web development](/en-US/docs/Learn_web_development) is a great start, and you can post coding questions or search for answers on [Stack Overflow](https://stackoverflow.com/questions/). +If you're learning, the [Learn web development](/en-US/docs/Learn) is a great start, and you can post coding questions or search for answers on [Stack Overflow](https://stackoverflow.com/questions/). Issues, discussions, or pull requests on MDN repositories asking for general support will be directed here and may be closed and locked. diff --git a/files/en-us/mdn/community/issues/index.md b/files/en-us/mdn/community/issues/index.md index 377c7bc3970af64..b4936f1d8e92705 100644 --- a/files/en-us/mdn/community/issues/index.md +++ b/files/en-us/mdn/community/issues/index.md @@ -1,5 +1,5 @@ --- -title: Guidelines to open and work on issues +title: Creating and working on issues slug: MDN/Community/Issues page-type: mdn-community-guide --- @@ -7,7 +7,6 @@ page-type: mdn-community-guide {{MDNSidebar}} As a contributor, you can [report](#guidelines_for_reporting_an_issue) and [work](#guidelines_for_working_on_an_issue) on issues. - After you report an issue, the issue gets triaged. Issue [triaging](#guidelines_for_triaging_issues) is typically done by people assigned the role of a maintainer or an owner. ## General guidelines for participation 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 39061053b806ff1..acb6896042ef99d 100644 --- a/files/en-us/mdn/community/open_source_etiquette/index.md +++ b/files/en-us/mdn/community/open_source_etiquette/index.md @@ -6,9 +6,10 @@ page-type: mdn-community-guide {{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. +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 behaviors to adopt that will help you and the other project contributors feel valued and safe, and stay productive. -This article won't teach you everything about contributing to open source; the aim here is more to give you some good starting points to think about as you get started with open source contributions. +This article won't teach you everything about contributing to open source; the aim is to cover foundational topics for taking part in open source communities. ## Think about why you are contributing to an OSP @@ -82,7 +83,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 Web Docs](/en-US/docs/MDN/Community/Contributing)). +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 Web Docs](/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. diff --git a/files/en-us/mdn/community/pull_requests/index.md b/files/en-us/mdn/community/pull_requests/index.md index bc75f4ffe3626e7..ec9b2cde82327dc 100644 --- a/files/en-us/mdn/community/pull_requests/index.md +++ b/files/en-us/mdn/community/pull_requests/index.md @@ -1,5 +1,5 @@ --- -title: Pull request submission and review guidelines +title: Pull request submission and reviews slug: MDN/Community/Pull_requests page-type: mdn-community-guide --- diff --git a/files/en-us/mdn/community/roles_teams/index.md b/files/en-us/mdn/community/roles_teams/index.md index e1f0fcffb741572..f072a0eed1531d4 100644 --- a/files/en-us/mdn/community/roles_teams/index.md +++ b/files/en-us/mdn/community/roles_teams/index.md @@ -1,12 +1,13 @@ --- title: MDN Web Docs roles and teams +short-title: Roles and teams slug: MDN/Community/Roles_teams page-type: mdn-community-guide --- {{MDNSidebar}} -The success and growth of the MDN Web Docs project is, in large part, due to our community of contributors. Some contributors have committed a portion of their time to assist with the daily tasks of running MDN Web Docs. Changes to the site, including maintenance tasks, are performed by employees, contractors, and a network of partners who are all dedicated to the health, growth, and maintenance of MDN Web Docs. The project relies heavily on [roles](#roles) and [teams](#teams) in the [MDN organization on GitHub](https://github.com/mdn) to manage and incorporate changes from these different groups. A list of the organization's members can be [found here](https://github.com/orgs/mdn/people). +The success and growth of the MDN Web Docs project is, in large part, due to our community of contributors. Some contributors have committed a portion of their time to assist with the daily tasks of running MDN Web Docs. Changes to the site, including maintenance tasks, are performed by employees, contractors, and a network of partners who are all dedicated to the health, growth, and maintenance of MDN Web Docs. The project relies heavily on [roles](#roles) and [teams](#teams) in the [MDN organization on GitHub](https://github.com/mdn) to manage and incorporate changes from these different groups. A list of the organization's current members can be found at [github.com/orgs/mdn](https://github.com/orgs/mdn/people). Community contributions help this open source project immensely. Contributors can use their work on MDN Web Docs to show their writing, technical, and collaboration skills, and the ability to work with people from diverse backgrounds. This section describes the roles you can take on while volunteering on the MDN Web Docs project. diff --git a/files/en-us/mdn/writing_guidelines/attrib_copyright_license/index.md b/files/en-us/mdn/writing_guidelines/attrib_copyright_license/index.md index fe472125059770e..2d2308647850df2 100644 --- a/files/en-us/mdn/writing_guidelines/attrib_copyright_license/index.md +++ b/files/en-us/mdn/writing_guidelines/attrib_copyright_license/index.md @@ -6,7 +6,7 @@ page-type: mdn-writing-guide {{MDNSidebar}} -MDN Web Doc's content is available free of charge and is available under various open-source licenses. +MDN Web Docs content is available free of charge and is available under various open-source licenses. ## Using MDN Web Docs content From b2877a794e630d09ceb134a3b55b37811ce292be Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Fri, 3 Jan 2025 18:19:34 +0100 Subject: [PATCH 04/20] chore: meta docs tidy --- ...05281080_8135317797319228200_o-600x400.jpg | Bin 37629 -> 0 bytes .../mdn/at_ten/history_of_mdn/a2sheppy.png | Bin 5169 -> 0 bytes .../at_ten/history_of_mdn/birajkarmakar.png | Bin 9523 -> 0 bytes .../mdn/at_ten/history_of_mdn/darkwing.png | Bin 8257 -> 0 bytes .../mdn/at_ten/history_of_mdn/devedge.png | Bin 34479 -> 0 bytes .../mdn/at_ten/history_of_mdn/elchi3.jpg | Bin 2549 -> 0 bytes .../mdn/at_ten/history_of_mdn/ensemble.png | Bin 55743 -> 0 bytes .../mdn/at_ten/history_of_mdn/groovecoder.png | Bin 11620 -> 0 bytes .../mdn/at_ten/history_of_mdn/hoosteeno.jpg | Bin 2656 -> 0 bytes .../mdn/at_ten/history_of_mdn/iyqi3qpv.jpg | Bin 2311 -> 0 bytes .../mdn/at_ten/history_of_mdn/jeremiepat.jpg | Bin 2428 -> 0 bytes .../mdn/at_ten/history_of_mdn/jmswisher.jpg | Bin 4092 -> 0 bytes .../en-us/mdn/at_ten/history_of_mdn/kuma.png | Bin 18532 -> 0 bytes .../mdn/at_ten/history_of_mdn/mediawiki.png | Bin 34281 -> 0 bytes .../screenshot_2018-07-24_16.06.55.png | Bin 75402 -> 0 bytes .../mdn/at_ten/history_of_mdn/teoli2003.png | Bin 11310 -> 0 bytes .../mdn/at_ten/history_of_mdn/waffle-flag.jpg | Bin 13625 -> 0 bytes .../mdn/at_ten/history_of_mdn/yaacgvya.jpg | Bin 8099 -> 0 bytes .../mdn/community/our_repositories/index.md | 105 ++++++++---------- 19 files changed, 47 insertions(+), 58 deletions(-) delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/11073502_781006205281080_8135317797319228200_o-600x400.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/a2sheppy.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/birajkarmakar.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/darkwing.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/devedge.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/elchi3.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/ensemble.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/groovecoder.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/hoosteeno.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/iyqi3qpv.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/jeremiepat.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/jmswisher.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/kuma.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/mediawiki.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/screenshot_2018-07-24_16.06.55.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/teoli2003.png delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/waffle-flag.jpg delete mode 100644 files/en-us/mdn/at_ten/history_of_mdn/yaacgvya.jpg diff --git a/files/en-us/mdn/at_ten/history_of_mdn/11073502_781006205281080_8135317797319228200_o-600x400.jpg b/files/en-us/mdn/at_ten/history_of_mdn/11073502_781006205281080_8135317797319228200_o-600x400.jpg deleted file mode 100644 index cef1ed09c193dd259da818a34cfd1faf17e858f2..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 37629 zcmb@sWpG?g&nA4#j4?CE%#1NJGcz;C9NUQ*rm000BMfcJBNQ_0HF&C%7$(TRkOks06? zk(P&q1pX2(0k|cA!N4ZxXzZ?|#A4zhW@2w_Z09U21-$Pd{E-$FHB?ejl#rGa|EEKQ zqrXbvptrq)n~RF12#J=q4hhUE00H0wm;ePpY;5Z4^ta9bk3e?(e{{d}*D3&*XZU-i z`6IAZbFE(eS>$PNESLxBuk8OqsAlG_rl5(5f!cVPfCdNgy&xXLL`_8$#4i8*)21QQ3715*Lh1~US)1akm$2lE9B28#fT2TKRb11kfo18W281N#9s z3$_aO3+x!|8te%i0vr(>1Dp_?3Y-a?8(bJ%7F-QnAKVh$8QdHED|j?`DtJD4C3rJ< zANV-4ALvNvEa)2OUg%lqUFbU) z7#Lg_Iv4>MMHpikH<%EZG?+@59+)|peV9M62(ZMktgsTWIda~({TH6&+usQAK?Yy)!=R51L0HQtKo;>H{fp&5D>@^ zco38ktP#E-q$1QJj3WF(ctk`;q(u}()I)Sfj7BU$>_uEfyg@=jqC)zFq=V#!6pd7d zG=Q{)^auF^G9$7yvKev!at3lU@*MI73LFY0iZF@+iZ@C!N(0I?${8vgDix|IsxhiR zY6fZ>>N4sb+6OciG(|Lfv`Dmav>#|k=rHJ1=;G*R=wHzb&0KDYR+RW3N9nAOs-{a3~nXvNbXS{ zC>{}>0G>{sM_x`|H{N>Q-+T;wwtVG$NBkf8&G`%YcLm4*pJY9TC zf=t3vqC((aPYFV04+Elts`cj5V#!qHY7ExAJHeGf{j#kb^u3a8n zUPeAaenWv$!9k%#5m1y?OiyHy89M?|IhQ@{sMo>nYM&(8?#)`)I#&;&tCYdIerlO`Prl)3~%o5Fx z%>~Tk%?~XEEaEMWECnnRERU^(tdgzHtVONUt*>mPY;tTKY!z)wY~SrP?P}~{?Tzf) z9MBzX9R?kV96vkGI?*|WIBh%gIwv__y2!c|yMnpuySBPvfF3Xt?$qwz+<$opdSrO~ z@zn5a_>A`1;q!zStyh@Wp|^y0kq@MgsZYNzsc)d~FF#?wJby5M6aW4I@_?@a`(Gr# zlm@~F+6GPrF$cv5-3Dt0w|^!4`sM5HH_2}mA;=*vA}krtcwl5Um0m?4r;lSz;nmidrnmNl3CDZ4s{Fef7C zDc3r8B~LQ1IiD&&xd6Jrqu`)Wqj02%yQr)fuQ;OkwZx%hyHurgu#Bs$tel`crUJae zz2dl1uX3hJtg5w|p*pVyt0tlrsCBPBsWYlus+X|?qgA`rt2K|c=k+feP#fW!sGG@K z1Y7w(X@1shb8dJ268kl=qq?)cYr1>7=eqZ@|MdXrAo-B^uwg8HKI_ov?zms*$mS1woY*O524Hzl|1xBYiYcU$-N_sf zJZU~1K6}2vyrjO;ytco|zHPkQzrX(%Hem$85|V#$iI};CvAdlc$zQ-C>S*Wa?n0vK zWNd0q!a(vD#QX<9{EuD##VICf0MPOc0C3j+m4Sv)`p;1R!EOKW|AjCA4>Q33)q}tS z00=e^dM*4{=9muv+;<>(tgE#p$zM%T6*ZFo@&kj4xrMolxdUjb8rJ5X)()1S`8$|d zyIDIrkXSqXMQ{JQ>Hiq{f8fi%cK(Z*-ON9Oa3#o2M<*{AYfCFP5@`oFa~B8WzZMzW z{j)kQe{FPibaAtGx2GpzWoG6909Ok()_+U_LlgtSyr1vyH&g%slL!E>G4JosdGGJ9 zAYVYN13<6)`#SIyfQ5#Jfrf$wArv?`Sa?JXBt!%RL|pU_C>Vrz#6*O61Oy}$j2}tJ z=*bBPsJUq9nOWG`*@-{$2ynCVGqSO>g2BPTAtE5+AR*zff*zQx|IhT^51_$<#e!== zfRO>Ztp^7=_{&FlHmtC1M|CYlp}{n zo=fAK8)=bHs?^^*D>f$~Q+!f7;*s3tP^$FHALox>n363V8SF8_^NMvZRO7tzk1CPe zY)Y?T_r_LM#^RsP_ih#^@?9QWu3;3=#1t+}Cur}IJzG>?JXboVjR-b%L#a3*?7}|W z`!ETARvP$tnD~{3G@Fb~?Se;<^9w_69E}zLTjD8ysVM;OuOf4kuJ=kY@(_W%reV+o zEJUqdZ@Ad9U;W}{s?8djv4^GH8=1V@qNBhKkstB8L#8$6?#?+v(#9cM% zPz`NyacRwi7^M!^y!j1RCsurO)Ivg0c1b>sO5VXHoLtXAw$VPM4~{N)DDZ zh050WB$ugYcK8beIw@`(dIiIeB7ZY<>*k}oTj$GSnw>s&X(ft}z<$!v>eszIjMI zH5NfXqQ(Npwo$$H%%H@cGh17)F&KhR(;xGRBJn1McQ?dFu7ydcy1pheh}-8o-d8Y? zuC@~Nnhl|^oVWgyVbs0^$<4-~1$vLBjp1_sk{tJCxk>eq{X-8A z=8q)EoWsbu%5{z(OU(kCGmJyh$5vO5I=k%YwjHV}_)i6D=jbh)2*3gVfJP51b!qL3 z*3)RbM7{1Bu8tgN8`z!7Z5y#q_~X{;RO{x+sn(rMMOBAM-|hrF3l(av*AVm($Ichm zjX3CgQfk|0#LN8|lJHee_N1HUSbhnP=o<5+Rpah8rujS|#x$gROg5)lC+j%U*xNfF zFvy4D&u&KT&G@zdVfN6-WcbCQl$x8>jj^lJaP z`!fpb#8cU6Gg?kX;_qzzrDHJwf80j5a>SO(Rh|uH+WhH@7sjbKE>XzJ=e#Gv+p_Ou z^pDN=lylo%(8!ju=-I*QmOQTanB6ijJ>s{MzLuv4#3@_Lpj01k{6x1bcV;}Yx5@BZ z+6jY~-duUYv2($n*A1REKbP+jMD`uW@@8D_TEx=9dp830qS1K5P_Ar8-l_2w<|%20 zeKTJm><>5?*l_oQ6YDcHBN9%kycYSB)9*%=e8=?|6c#&!=pU2Mj?I<5DN!*X$zQuP0M>*Y0xHoSMsoqUF$@tZ&xs4$`p~BQ!Bh71K6%NNm;42lcCl;=!vMRKF4T<==t&(9C^uo?CT8-m~c7 z_}*uaN>XFrjJ30GkUacv6-)dZM>ZCHQI)k^2F@d!b7pnv6H`vjp2B5LFF_iXE0o(u z&x(ueyfso22iG&x$K*EbQVdYUg?f!>1)pK+v~weD7r3Xj$LhXRcLgiEmU0z#?%tH_ z@t>*;3DAeFPqrivPTEE2W(U8M6o2`)r7^poL3)i>&g7-zCcv>PtoRRV~Qm$VISuYuMA5V4=| z4=E_1qjK2pAO{xfj#RI`>@rYz$d!|8;5q~%JvT``EL4ePzOT2-2V|P<${<)fS8=u3 zbd<@pfns>4I&^jq-~NL+L%9l-vtUffm$Qodm#Jbnf*i?l%YyGK_O}BruCbmreBoIZx)bK1AQThZAa*kt``I=^WjE^emASUAWN3SF)GmeUu6 zLQEyyEBuGmEUpS=^r#UZ*S!y1g5Ck<9S~qGOP<=OV)qz>4bv7DHIz=fzprhT*fKk0 zU*(x0bTT`ud^umeeb7a)h_)bDNK(_u&y|PNJ4JD7ni@^=wioCkr+Lyf|8)VM!#e20 z_Sun@59h#z+@*nFOe17#WP*JB&@EcsjCfU_wuZU|ogLb!;X}KgyZ4=OhU+WXJnL~g zUy;JTj1asQ=A}+;5=J{;ALf*+%w32}8kYVq4GR?cB1!`V<7lZm=w^r^*70}>?k?M7 z6~u`obF1o@l#YFArBoZZEv&6QfCnJ>8xi6Ps5u>l-&~KJ*zHqYe!GY3NLqo&7?bPwasKpWgv8Y_dx( zRYO*K2hIcG?*!>p&lhQFXlSl2%Qarnu2Ys;{fTE2;w@nK7g9&4dvnxoeJLeVlZ##2 z2yI?UI^{(ULfpp%R4Y{DHqXNrVq#*Qo&g-f2w|Bnbf(g_iJJkrL!lcRX=P-)_J{Qx zYj#=8pz6;zO4u6$rU@7}&>~!S7CB6$>+v`dyO5mF5y`?3Fe}mplg4p0~CzwOj0d6%#8LGZese{_;VE z&}+WTGi%Rb8%@ykt&pN~&6pl+VmQpyht?gizW=#21y&4ZoV&Y(GwGH7gV= zECQtrcwhiH#D8ZD02ny%H)r@KVE{)3r4l>VpNhW5OU72BOHsrIQ@}G)uVyyJi{e1e z=V=nei;@IkC#$&DdIs{MnzQnym$FI&U#)pKEnQRB)xU}iql3YF;5oL{s^u zZ_=M*u{k!jz=;~EG5 zHg7MVSfjC{k=e&d4ozO1+B0o$_MZ|qnES6INvjh1MepHj~og9m_;U zc1NcyET{3LN?6RAW2ZGFJaa6g_(%8VZCHxq zp=#?%e*}AiSMN4qi!%?T&PRIA)9Q)R3f?O#J{Fezh+xAXh{IC1IP2LJ4g)&Dv(Odn z%3|fR^aTuNEBn@+j9p2lTMPT8bx>8av^v^n^Wxm%o>scl-siSg^3f@#V0%nnsv7>; z;XGAg5*gT@Wa~tD7vc9eE?FLRTsXUe!!0?1q-{Bh7)5*lD8z8V08oVeS5gYfQX#-0q5g?5h`$kb zYj!&aAV#r#LBxYZbk&`_{7UsP`KKWJMK5Y9v}IF=krXlW$xvq1;&-sz_+~#LHm+fI zxXLdqT&eg+U?HXz*H8Q_M+cKQeT)=8<=l=x0Y~e*hgF}SxRUUZiV>!e++76>DlzEJ z977Y5?{<#z`)5|Zdj0ral6BH-$Dh6RHZADewB^}^Y4%j~L(XvulXs7IS;}8B?_`I0 z|8xn=+(GxGBwHfep+RAV%Ql!lz_5Ym@bKv37ZJN?M){5`kyF_+*sZDv|4+@i>zNMw zgBAwEjP#||%$w_Dhbv-nH{AWxjnR=}-G=dvwqSFBo&k1y~MG z>xsE}UZu%2H7`BtyF9tC|9TjRTyPlVNKK#Q z?HqOURxWz-Y9r?IcdxD#gx+T?pOVK-H9OnZI%}WnSH1}1s^W0>J3wD zDU}l2&vKhrjJs8gZJdgOb?tt6bS& zt^Q3n35Ju$RwECN%zQK(uCr0ol0aJz=oKGC56{3|K^&R=_DtfnQCXq<(UrE?3+S1` z8)o>i94_)MxC-OMRaR|S0ifWaL4}L{dOzy*yI5cXf9phKPhnz%+dAiS;W9wNf5Bj`$~S*9 zf0e0Z83y9R$0v+Cx<}Y>oF1m>C0$xotvIN=tKD9RlPOTjGsLT)=~=TVs;Ld-$c0#Y z>bkrWZ`T;=)+{JZ3;i+eS=)@38vA^;d-Jy| z!zpupU$q_~MMXnHLrq)!4E%L$U38;Y!Je4b)kRlby_r6Bjy)8m5I7rlx$JIcsAyjA zY-d5yXxB2(+_FNVQ4dy%M2*5D|#wQ zZT1=(os@R-@t)frdE%KL_h6c+i6LS}?H48q*qD6sp&d|>54d^YG$cepLve()seD@xZrMwflq$xM(C!<1(Mz31 zo7O@S^om`6%PZOnoBun|a{3Bx^lKmtebK(rkV5=g#5X+a#G}PuxMxMa-fQ9u>~1*x zkRI;DH!%Yog0&U$Y^fzuhR{BUKB_nl6~-$OwLrF32N!|#{=47x-mrrvEW~?cFJjE% z9!w(vSP@AMc#N3cypGZMy9K>&yx;R|#Rm_5KD+~(udp7(lTNCJDiiNOE_Ve1no4wQ z==6?rR#A??R*(Lr@CkRhw(pX4BBJCzrmJ%nE6;_ z)|s6J@9LC#Jo1PWX(1F>pw%W7X_yw3YlBj`VH?TX+cZH%j`n?7=4yyQSu9RQmHwh| zOMiXR$dW9YjL<%FZ;3;0b8G(VYBO3W?^veVW>b~Stz~9w@DggCNO`GJp2#-@bw{Qe zIiAr-w}cy()G^=4KpsezM9@7WU!QsyGgClLs;E+YbIW?C`nxefg!7)PQG@w-bokMb z&$=O6s~>5&Co@RvCo%y~V{mrfhMAJxuLCpjD_Bt1rC=go0G$YTKX2!JrACZ0MUftI zY6BLTBwD31{dUYOnIv=4V6z$N%J^WhMeb3f$-CLwGUYjIFLB?ptirTmiqH8z{QDV8 zg#)3;azQyxB-7Jk37;TI)zOrdm8d@j3fLe7kEpm=pVks^{1GFPFB84 zsm@FzX)uDUeUyMXfCKs+s0%UZU@zO%>4qhVzUulcP7(x58Zs%BCd0~FU+dHth(|IY zQfn!Zxg9%NS0fmoj<8UtAHbp;rhuYqnSN+l5sGa8+qyn^V2}G&AGyZ3s-+8%Ai<^| zU#xMdniS%}WfW`#r?Xi6bglQyvC3>I7gDC4xHgk3@7Q=KGN%WhfE_2jhdR5) z=~>(1<`;5Qr243@v9=ed`$d|H#4Jc1{4K%@L|PstF*Dk`Cs(3h6u<+bsQz^LjQ&~X zS#F{#U0lP8$;uc^tE;s?Eg}tuM#N|Lxtg=JVNa@=NmN}4=PAdQH?|%Vvy{bFM)`w*`9j{P0-86lL0i|~U-}>{^J5Wo-Lzd%QyGxcs zvpu%TCbjv)ZreYaz>a&EEuJt8&rc1O0L$*9F$0`Y3WKFMQT*ibr5X6Wo{i3Fqsh{8 zMR_`xkR-Bv#(&F1&PO^nViD|1MbSn0Zag5H^IpT?Te%GnulEyywo zKY!Uw5{g}PX;;+~z3dE|oiNs8A69-zhsF5V6i(ch3XwJu+tHwV2VJo$$;V9|XZ@Jj zfdu3nsyNr?o)Qe5O#K&}sU?cV5p^`N&#;0e0t+4Ie1awi!~3>L7q*@c&7O?Esaikh zN{?71PTbh6Pb=25U>f7BuxfTtWj&nZE~Yiucth0GnTV#(u-<08HFvdoH+8n@z&9$+ zJ|*xKO4MX^d`ec;dtD%_I@P#8FwogBW345v`y_xZ_LIi;)MfQLMi{isYksmOU)NX{ zubWJ8;n{1PblAuU?l`bqmvxOhv}82=X+f#uqNI>EfoD}j$WV2j#a=&gV~vr0?acqZ z>2?WS_7xG|H1vGLQBu?*wtKb`???45{+Na*;`Nl(X7x#L2qLVJ58+}N?IGLDOTIsC zDSJe2gMqx>h2w8?z)nk;(bJ3xRgmmsxllf=2>ZL3r0r~MA_h-Rd4%`|T%J++jp z%r9I#_!(?VO(l~x(^Jn~pv(?LWsIeBh|i(StKHSy%T9D37qPC}W)6;x^@d#IPc3CR z*mf+YJZ8TG1Fq|vXYB%x6KjHFbh`J4KV0U!*Q8gcheK@bsm2y?^;TQg2Rir)*F8{t z{08A%E8ChId^{n&Pa8BY+?QzjWZmWPen}P)d2l{)i-jR~SiGcV|KxK_p9&$;_muZl z?UrQlZb~8zghaJZhuLH4n2IT!KRb4?z0p++Z}Jv&_Li8-ait7h!pUJ4Y?Tv=1?v`<B3wp%7@N^$vL|_i5P4 zEkpJ^llhcU2%v%ei}f2Na)h9x6^0%W*E4o#Y}dnvD04Y>f@a0Eb&YEr6LS3Om)vyi z&nN1-cXlYmsc5Kg!!jZ$Pmvvjd#ULtt=vZED)z1r|QeR^{ z=d2)&F~_KtF5he8&{iw4E)7cIyLI~2FKqXlX27P!A3LZj-3pGq)gn zrEcM|`|Z8*bMK<5-RHtQ#$tKHG*0wm4&FF6MfRfeO4geI$>WCUWmSdhD)}mGM~y_2 z?)DV5@HH&>(l9()YPne3=`k2}%B-mY|AvsF`aIj+UmaK%T5Ad~OF;@BvS#o2#<2ox zuoB`qp6ogFIs7yZElq}tbs@|$@6bY#QJr?_7K;!adEUyXybNrfUMaL(O}kg!@S6Kl z@_XoesO|m5GR!5;ZB(?^HlP#TY2bfo(}nM}4>8)t{MhTANl&Vm3Y#Cf>To=_$J(3G zuWGI9ShCsMf$k}pj&kE8EO`)4pm7UIVrV*U_Q}BV9kkHrJ1bc=;C6|6V>4M;C`QCNuvp58SA98r96k(~EXE=+t6Qa5$dvW87cjF;q{cMZ?SOZfo-vJ&1on9!T$7!=kdYyZ0pXaz568loDnNs zrr}Rkxg28gV(SV=1xp^^>#(Rs{mt)=HGF)Yu0RxpE}bl;Xf8!uQR9;1QK^0?_e5LW zuIaruQpLxBl*fRKubdfs*kQ&qg2T=0$~HZte11{#8tX+3lx4SzKPgt4p7gOrSsD{0 zxlX4RmRy_ZnlJ|2n|Gp8Oikd(vOmo0SLm3|o9m=t;aY93+BKNvC^N`=1RJlF93#nM z&f%PrYaAWlLFD2eY;Bx0y=qLYaka#cfO!-)dn0HV8?$e-j?v?8M`Q#s`WT9wuP;|J zWqGgHHCHiUxH3`K;%ams2qc&9Y`mJDUf7>%ew?d8cf;l8ooeL)Dq!1Jex6&Yj~#-vnVcUd-8r4i>c?*4$G%^}LRqre zX<}GiJ9#4fsgw*+3r$#cd@S3zRwR!bqd*?SHo2Air|S0w{`y2rC56(KJQG_ctBS2 zJ(Sj>F;)KH@l4_Lu%@3A3ixbl4}(d1$@+pp`T6-d-Yk8tz$?4!;$NU8NZ}3dAWSk@ z%uoGZm?RJ!n(eqGZR8Q9npHVsDO2?=(aeKA*FK|%aBq{_s4ooNYxoD!Vs<9`U<