chore: copy meta docs into repo (#88)

README.md

@@ -1,27 +1,28 @@
 # MDN Web Docs Product Advisory Board
 
-This is the GitHub repo for the [MDN Web Docs](https://developer.mozilla.org/) [Product Advisory Board](https://developer.mozilla.org/en-US/docs/MDN/MDN_Product_Advisory_Board) (MDN PAB). The PAB is a collaborative group of tech organizations and leaders who together advise and make suggestions for the future of MDN, as well as, in many cases, make direct contributions to MDN's code or content.
+This is the GitHub repo for the [MDN Web Docs](https://developer.mozilla.org/) Product Advisory Board (MDN PAB).
+The PAB is a collaborative group of tech organizations and leaders who together advise and make suggestions for the future of MDN, as well as, in many cases, make direct contributions to MDN's code or content.
 
 ## Meetings
 
 You can find notes from our meetings in the [meeting-notes](meeting-notes) directory:
 
-* [March 2021 video call](meeting-notes/2021-03-notes.md)
-* [February 2021 video call](meeting-notes/2021-02-notes.md)
-* [January 2021 video call](meeting-notes/2021-01-notes.md)
-* [December 2020 video call](meeting-notes/2020-12-notes.md)
-* [July 2020 video call](meeting-notes/2020-07-notes.md)
-* [June 2020 video call](meeting-notes/2020-06-notes.md)
-* [May 2020 video call](meeting-notes/2020-05-notes.md)
-* [February 2020 F2F meeting, Mozilla Toronto](meeting-notes/2020-02-notes.md)
-* [June 2019 F2F meeting, Mozilla Berlin](meeting-notes/2019-06-notes.md)
-* [January 2019 F2F meeting, Google New York](meeting-notes/2019-01-notes.md)
-* [July/August 2018 F2F meeting, Microsoft Seattle](meeting-notes/2018-07-notes.md)
-* [January 2018 F2F meeting, Google London](meeting-notes/2018-01-notes.md)
-* [March 2018 video meeting](meeting-notes/2018-03-notes.md)
+- [March 2021 video call](meeting-notes/2021-03-notes.md)
+- [February 2021 video call](meeting-notes/2021-02-notes.md)
+- [January 2021 video call](meeting-notes/2021-01-notes.md)
+- [December 2020 video call](meeting-notes/2020-12-notes.md)
+- [July 2020 video call](meeting-notes/2020-07-notes.md)
+- [June 2020 video call](meeting-notes/2020-06-notes.md)
+- [May 2020 video call](meeting-notes/2020-05-notes.md)
+- [February 2020 F2F meeting, Mozilla Toronto](meeting-notes/2020-02-notes.md)
+- [June 2019 F2F meeting, Mozilla Berlin](meeting-notes/2019-06-notes.md)
+- [January 2019 F2F meeting, Google New York](meeting-notes/2019-01-notes.md)
+- [July/August 2018 F2F meeting, Microsoft Seattle](meeting-notes/2018-07-notes.md)
+- [January 2018 F2F meeting, Google London](meeting-notes/2018-01-notes.md)
+- [March 2018 video meeting](meeting-notes/2018-03-notes.md)
 
-# Other links
+## Other links
 
-* [PAB Charter & Membership](https://developer.mozilla.org/en-US/docs/MDN/MDN_Product_Advisory_Board/Membership)
-* [Current PAB Members](https://developer.mozilla.org/en-US/docs/MDN/MDN_Product_Advisory_Board/Members)
-* [PAB Membership Application](https://www.surveygizmo.com/s3/4024118/MDN-Advisory-Board-Application)
+- [PAB Charter & Membership](./membership.md)
+- [Current PAB Members](./about.md)
+- [PAB Membership Application](https://www.surveygizmo.com/s3/4024118/MDN-Advisory-Board-Application)

about.md

@@ -0,0 +1,59 @@
+# MDN Product Advisory Board
+
+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](./membership.md)

membership.md

@@ -0,0 +1,98 @@
+# Product Advisory Board Charter & Membership
+
+## 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.