├── .github └── workflows │ └── agenda.yml ├── 2019-standards-meetings.md ├── CODE_OF_CONDUCT.md ├── GOVERNANCE.md ├── LICENSE ├── MEMBER_EXPECTATIONS.md ├── MEMBER_REPRESENTATION.md ├── README.md ├── img ├── poster1.jpg ├── poster2.jpg └── poster3.jpg ├── meeting-notes ├── 2019.05.31_collabsummit_session.md ├── 2019.07.02_meeting_notes.md ├── 2019.08.13_meeting_notes.md ├── 2019.09.10_meeting_notes.md ├── 2019.12.17_meeting_notes.md ├── 2020.01.14_meeting_notes.md ├── 2020.01.28_meeting_notes.md ├── 2020.02.25_meeting_notes.md ├── 2020.03.10_meeting_notes.md ├── 2020.03.23_meeting_notes.md ├── 2020.04.07_meeting_notes.md ├── 2020.05.05_meeting_notes.md ├── 2020.05.19_meeting_notes.md ├── 2020.06.02_meeting_notes.md ├── 2020.06.16_meeting_notes.md ├── 2020.07.14_meeting_notes.md ├── 2020.08.25_meeting_notes.md ├── 2020.09.08_meeting_notes.md ├── 2020.10.06_meeting_notes.md ├── 2020.12.01_meeting-notes.md ├── 2021-06-15_meeting_notes.md ├── 2021-08-10_meeting_notes.md ├── 2021.01.12_meeting_notes.md ├── 2021.01.26_meeting_notes.md ├── 2021.02.23_meeting_notes.md ├── 2021.03.23_meeting_notes.md ├── 2021.04.13_meeting_notes.md ├── 2021.04.20_meeting_notes.md ├── 2021.05.18_meeting_notes.md ├── 2021.06.01_meeting_notes.md ├── 2021.06.29_meeting_notes.md ├── 2021.07.13_meeting_notes.md ├── 2021.08.24_meeting_notes.md ├── 2021.09.07_meeting_notes.md ├── 2021.09.21_meeting_notes.md ├── 2021.10.05_meeting_notes.md ├── 2021.10.19_meeting_notes.md ├── 2021.11.02_meeting_notes.md ├── 2021.11.16_meeting_notes.md ├── 2021.12.14_meeting_notes.md ├── 2022.01.25_meeting_notes.md ├── 2022.02.08_meeting_notes.md ├── 2022.02.22_meeting_notes.md ├── 2022.04.05_meeting_notes.md ├── 2022.05.17_meeting_notes.md ├── 2022.07.12_meeting_notes.md ├── 2022.11.01_meeting_notes.md ├── 2022.11.15_meeting_notes.md ├── 2022.11.29_meeting_notes.md ├── 2023.02.07_meeting_notes.md ├── 2023.02.20_meeting_notes.md ├── 2023.03.07_meeting_notes.md ├── 2023.03.21_meeting_notes.md ├── 2023.04.04_meeting_notes.md ├── 2023.04.18_meeting_notes.md ├── 2023.05.02_meeting_notes.md ├── 2023.05.16_meeting_notes.md ├── 2023.05.30_meeting_notes.md ├── 2023.06.13_meeting_notes.md ├── 2023.06.27_meeting_notes.md ├── 2023.08.08_meeting_notes.md ├── 2023.08.22_meeting_notes.md ├── 2023.09.05_meeting_notes.md ├── 2023.10.03_meeting-notes.md └── 2023.10.17_meeting_notes.md ├── proposals └── stage1 │ └── REQUIREMENTS │ └── README.md ├── resources └── concise-guide-to-fixing-web-standards.md └── standards-calendar.md /.github/workflows/agenda.yml: -------------------------------------------------------------------------------- 1 | 2 | name: Standards Collab Space 3 | on: 4 | workflow_dispatch: 5 | 6 | jobs: 7 | create_issue: 8 | name: Create agenda issue 9 | runs-on: ubuntu-latest 10 | permissions: write-all 11 | steps: 12 | - name: Create agenda issue 13 | run: | 14 | if [[ $CLOSE_PREVIOUS == true ]]; then 15 | previous_issue_number=$(gh issue list \ 16 | --label "$LABELS" \ 17 | --json number \ 18 | --jq '.[0].number') 19 | if [[ -n $previous_issue_number ]]; then 20 | gh issue close "$previous_issue_number" 21 | gh issue unpin "$previous_issue_number" 22 | fi 23 | fi 24 | meeting_date=`date +"%Y-%m-%d" -d "next Tuesday"` 25 | new_issue_url=$(gh issue create \ 26 | --title "$meeting_date OpenJS Foundation Collaboration Space Meeting" \ 27 | --assignee "$ASSIGNEES" \ 28 | --label "$LABELS" \ 29 | --body "$BODY") 30 | if [[ $PINNED == true ]]; then 31 | gh issue pin "$new_issue_url" 32 | fi 33 | env: 34 | GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} 35 | GH_REPO: ${{ github.repository }} 36 | ASSIGNEES: jorydotcom 37 | LABELS: standards-agenda 38 | BODY: | 39 | ## Meeting notices 40 | 41 | **Reminder - Meeting is recorded** 42 | 43 | ## Agenda 44 | - [ ] OpenJS Announcements, Reminders & FYIs 45 | - [ ] Liaison Reports 46 | - [ ] Review Open Issues and PRs 47 | - [ ] Any Other Business 48 | 49 | ### OpenJS Announcements, Reminders & FYIs 50 | - [ ] Add any project shares, news, FYIs or reminders to share with the community 51 | 52 | ### Liaison Reports 53 | - [ ] TC 39 54 | - [ ] TC 53 55 | - [ ] W3C AC 56 | - [ ] W3C TAG 57 | - [ ] OSI 58 | - [ ] OPA 59 | 60 | ## [Review Open Issues & PRs](https://github.com/openjs-foundation/standards/labels/standards-agenda) 61 | - [ ] Add issues that need review, assignment, triage, or other clarification 62 | 63 | ## AOB 64 | - [ ] Add any other items 65 | 66 | ## Adjournment 67 | PINNED: false 68 | CLOSE_PREVIOUS: false 69 | -------------------------------------------------------------------------------- /2019-standards-meetings.md: -------------------------------------------------------------------------------- 1 | # 2019 Calendar of Standards Meetings 2 | 3 | This list is not exhaustive - it reflects meetings we may or may not be interested in sending an OpenJS Foundation representative to on our behalf. 4 | 5 | | Date | Event | SDO | 6 | |----------|-------|-----| 7 | | 06.18-19 | TC53 In-person Meeting (CA) | Ecma | 8 | | 06.26-27 | Ecma International General Assembly Meeting (Geneva) | Ecma | 9 | | 07.23-25 | TC39 Meeting (Redmond) | Ecma | 10 | | 09.16-20 | TPAC | W3C | 11 | | 10.01-03 | TC39 Meeting (NYC) | Ecma | 12 | | 12.03-05 | TC39 Meeting (Bay Area) | Ecma | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | The OpenJS Foundation and its member projects use the Contributor 4 | Covenant v1.4.1 as its Code of Conduct. Refer to the following 5 | for the full text: 6 | 7 | * [english](https://www.contributor-covenant.org/version/1/4/code-of-conduct) 8 | * [translations](https://www.contributor-covenant.org/translations) 9 | 10 | Refer to the section on reporting and escalation in this document for the specific emails that can be used to report and escalate issues. 11 | 12 | # Reporting 13 | 14 | ## Project Spaces 15 | 16 | For reporting issues in spaces related to a member project please use the email provided by the project for reporting. Projects handle CoC issues related to the spaces that they maintain. Projects maintainers commit to: 17 | 18 | * maintain the confidentiality with regard to the reporter of an incident 19 | * to participate in the path for escalation as outlined in 20 | the section on Escalation when required. 21 | 22 | ## Foundation Spaces 23 | For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `report@lists.openjsf.org`. The Cross Project Council (CPC) is responsible for managing these reports and commits to: 24 | 25 | * maintain the confidentiality with regard to the reporter of an incident 26 | * to participate in the path for escalation as outlined in 27 | the section on Escalation when required. 28 | 29 | # Escalation 30 | 31 | The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `"coc-escalation@lists.openjsf.org`. 32 | 33 | For more information, refer to the full 34 | [Code of Conduct governance document](https://github.com/openjs-foundation/bootstrap/blob/HEAD/proposals/stage-1/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md). -------------------------------------------------------------------------------- /GOVERNANCE.md: -------------------------------------------------------------------------------- 1 | # OpenJS Standards Collaboration Space 2 | 3 | 4 | For the current list of the Collaboration Space members, see the project [README.md](./README.md). 5 | 6 | ## Members 7 | 8 | The [openjs-foundation/standards](https://github.com/openjs-foundation/standards) GitHub 9 | repository is maintained by the Collaboration Space and additional Members who are 10 | added on an ongoing basis. 11 | 12 | * Invited to all meetings 13 | * Can participate in [consensus seeking process](#consensus-seeking-process) 14 | * Counted towards quorum in [Collaboration Space Meetings](#collaboration-space-meetings) 15 | * Participates in voting 16 | 17 | ## Collaboration Space Membership 18 | 19 | Collaboration Space Membership is not time-limited. There is no fixed size of the Collaboration Space. 20 | 21 | There is no specific set of requirements or qualifications for Collaboration Space Membership beyond these rules. 22 | 23 | The following groups automatically qualify for membership and can request to be added to the GitHub team: 24 | 25 | * OpenJS Foundation CPC Members 26 | * OpenJS Foundation Project Maintainers 27 | 28 | ## Collaboration Space Meetings 29 | 30 | The Collaboration Space meets bi-weekly on Zoom.us. A designated moderator 31 | approved by the Collaboration Space runs the meeting. Each meeting should be 32 | published to YouTube. 33 | 34 | Items are added to the Collaboration Space agenda that are considered contentious or 35 | are modifications of governance, contribution policy, Collaboration Space membership, 36 | or release process. 37 | 38 | The intention of the agenda is not to approve or review all patches; 39 | that should happen continuously on GitHub and be handled by the larger 40 | group of Collaborators. 41 | 42 | Any community member or contributor can ask that something be added to 43 | the next meeting's agenda by logging a GitHub Issue. Any Collaborator, 44 | Collaboration Space member or the moderator can add the item to the agenda by adding 45 | the ***standards-agenda*** tag to the issue. 46 | 47 | Prior to each Collaboration Space meeting the moderator will share the agenda with 48 | members of the Collaboration Space. Collaboration Space members can add any items they like to the 49 | agenda at the beginning of each meeting. The moderator and the Collaboration Space 50 | cannot veto or remove items. 51 | 52 | The moderator is responsible for summarizing the discussion of each 53 | agenda item and sends it as a pull request after the meeting. 54 | 55 | ## Attending External Standards Meetings 56 | 57 | At various times members of the Standards Collaboration Space or foundation projects will attend Standards Meetings 58 | at external organizations as a representative of the OpenJS Foundation. 59 | If a member would like to attend a meeting as a delegate of the OpenJS Foundation 60 | they should open an issue stating: 61 | 62 | * The standards meeting or series of meetings they wish to attend 63 | * The OpenJS Foundation's relationship to this standards organization 64 | * The date and location of the meeting or meetings 65 | * If they will be attending in person or remotely 66 | * The estimated cost to the foundation of their participation 67 | * The scope of the work they plan to participate in 68 | 69 | This issue should be labelled with `standards-agenda` and will be approved in the 70 | next Collaboration Space meeting via the consensus seeking process. 71 | 72 | ## Consensus Seeking Process 73 | 74 | The Collaboration Space follows a 75 | [Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 76 | decision-making model. 77 | 78 | When an agenda item has appeared to reach a consensus, the moderator 79 | will ask "Does anyone object?" as a final call for dissent from the 80 | consensus. 81 | 82 | If an agenda item cannot reach a consensus, a Collaboration Space member can call for 83 | the item to be decided by a vote or to table the issue to the next 84 | meeting. In both cases the decision must be seconded by a majority of the Collaboration Space 85 | or else the discussion will continue. Simple majority wins. Only Active 86 | Members participate in a vote. 87 | 88 | ## Pull Requests 89 | 90 | Pull requests require approval by at least two members and must remain open for at least 72 hours before being landed. If there are any objections the Pull Request cannot land until they are resolved. 91 | 92 | A pull request that is opposed will be discussed in the meeting. 93 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /MEMBER_EXPECTATIONS.md: -------------------------------------------------------------------------------- 1 | # Member Expectations 2 | 3 | All participants in the OpenJS Foundation projects and groups must follow the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md). 4 | There are further expectations for members who represent the Standards Collaboration Space (hereafter called representatives). 5 | 6 | It is understood that representatives may form opinions based on the needs of their employers' or their personal projects. While representing 7 | the Standards Collaboration Space, however, they should decide/discuss/promote based on the interest of the Standards Collaboration Space. 8 | If there is a conflict (due to personal or company specific projects), then the representative should be explicit 9 | about the hat they are wearing while deciding/discussing/promoting the project. 10 | 11 | Since many members are often a part of one or more projects in the foundation, feel free to discuss it with the members 12 | if there is a potential conflict while representing. The representative can raise an issue and discuss them during 13 | the Standards Collaboration Space meeting. 14 | 15 | If the representative or any member of Standards Collaboration Space feels there will be a controversial topic, they can call for a 16 | `pre-meeting` to discuss it with the other members of the Collaboration Space. Our representatives should always need to focus on 17 | representing the foundation and the consensus/expectations that we’ve built to those organizations (if they are representing 18 | OpenJS Foundation). 19 | 20 | If a representative has an objection or dissent they should express it as early as possible to ensure 21 | there is ample time to discuss and reach consensus before representing Standards Collaboration Space. 22 | 23 | Representatives must also conduct themselves in a professional and respectful manner. Some general guidelines include: 24 | 25 | * When in doubt/foreseeing any potential conflict, a representative should choose one "role" with which to express an opinion instead of invoking multiple at once. 26 | * Aim to remediate first and then discuss. If other members of the group express concerns about actions, acknowledge their concerns by stopping the actions in question and then discuss within the group to come to a common agreement. 27 | * Treat all community members with respect, consideration, and highest standards of ethical conduct. 28 | * Build trust by keeping your promises. 29 | * Be the model of accountability and leadership. Provide the example of ownership and stewardship that everyone can follow to success. 30 | * Commit to ongoing development and learning best practices for governing. 31 | * Follow the code of conduct of both the Open JS Foundation, _and_ the organization they are a representative to. 32 | -------------------------------------------------------------------------------- /MEMBER_REPRESENTATION.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Representatives 2 | 3 | The following document lists OpenJS Foundation's memberships and liaison relationships, along with [Collaboration Space Members] and community members who participate in these organizations. An asterisk (*) denotes delegates of the OpenJS Foundation. Where applicable, organizational affiliation has been added in parens. 4 | 5 | * [Ecma International] 6 | * [TC39] 7 | * Jory Burson * 8 | * Guy Bedford * 9 | * Jordan Harband (HeroDevs) 10 | * Lea Verou * 11 | * Richard Gibson * 12 | * Eemeli Aro (Mozilla) 13 | * Joe Sepi (IBM) 14 | * Chris de Almeida (IBM) 15 | * Ulises Gascón * 16 | * [TC53] 17 | * Donovan Buck * 18 | * [TC54] 19 | * Chris de Almeida (IBM) 20 | * Jordan Harband (HeroDevs) 21 | * [TC55] 22 | * Chris de Almeida * 23 | * Jordan Harband (HeroDevs) 24 | * General Assembly Representative 25 | * Jory Burson * 26 | * [Open Source Initiative] 27 | * Tobie Langel 28 | * [Open Policy Alliance] 29 | * Tobie Langel 30 | * [Unicode MessageFormat Working Group] 31 | * Eemeli Aro* 32 | * [W3C] 33 | * [Web History Community Group] 34 | * Brian Kardell * (Igalia) 35 | * [Web Platform Incubator Community Group] 36 | * Brian Kardell * (Igalia) 37 | * [Touch Events Community Group] 38 | * Scott Gonzalez 39 | * [Spec Editors Community Group] 40 | * Jory Burson * 41 | * [Interledger Payments Community Group] 42 | * Kris Borchers 43 | * [CSS Working Group] 44 | * Lea Verou (Invited Expert) 45 | * Chris de Almeida (IBM) 46 | * [Browser Testing and Tools Working Group] 47 | * Christian Bromann (Invited Expert) 48 | * [Web Application Security Working Group] 49 | * Chris de Almeida (IBM) 50 | * All Affiliated Accounts 51 | * Richard Gibson 52 | * Brian Kardell 53 | * Jory Burson 54 | * Michael Champion (AC Rep.) 55 | * Tobie Langel (Alt AC Rep.) 56 | * Anne-Gaelle Colom 57 | * David Methvin 58 | * Alexander Schmitz 59 | * Mike Sherov 60 | * Robin Ginn 61 | * Kris Borchers 62 | 63 | [Collaboration Space Members]: https://github.com/openjs-foundation/standards#collaboration-space-members 64 | [Ecma International]: https://www.ecma-international.org 65 | [Open Source Initiative]: https://opensource.org/ 66 | [Open Policy Alliance]: https://opensource.org/programs/open-policy-alliance/ 67 | [TC39]: https://tc39.es/ 68 | [TC53]: https://www.ecma-international.org/technical-committees/tc53/ 69 | [TC54]: https://www.ecma-international.org/technical-committees/tc54/ 70 | [W3C]: https://www.w3.org/ 71 | [Unicode MessageFormat Working Group]: https://github.com/unicode-org/message-format-wg 72 | [Interledger Payments Community Group]: https://www.w3.org/community/interledger/ 73 | [Web-interoperable Runtimes Community Group]: https://www.w3.org/community/wintercg/ 74 | [Touch Events Community Group]: https://www.w3.org/community/touchevents/ 75 | [Web History Community Group]: https://www.w3.org/community/webhistory/ 76 | [Web Platform Incubator Community Group]: https://www.w3.org/community/wicg/ 77 | [Spec Editors Community Group]: https://www.w3.org/community/speced-cg/ 78 | [CSS Working Group]: https://www.w3.org/groups/wg/css/ 79 | [Browser Testing and Tools Working Group]: https://www.w3.org/groups/wg/browser-tools-testing/ 80 | [Web Application Security Working Group]: https://www.w3.org/groups/wg/webappsec/ 81 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | Openjs Foundation Logo 5 | 6 | 7 | 8 | # Standards Collaboration Space 9 | 10 | The Standards Collaboration Space actively monitors evolving standards to educate projects about developments that might affect them, and helps projects formulate standards strategies and advance them before standards bodies. 11 | 12 | ## This Repository 13 | 14 | The purpose of this repository is to provide a central coordination and documentation point for project communities about foundation standards activities. 15 | 16 | The Standards Collaboration Space's responsibilities, as ratified by the OpenJS Foundation's Cross Project Council, can be found in the [CPC's Working Groups Document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/WORKING_GROUPS.md#standards) 17 | 18 | Interested parties can also [join our #standards channel](https://communityinviter.com/apps/js-foundation/join-openjs-foundation-on-slack) on Slack. 19 | 20 | For historical documents about our standards work as the jQuery Foundation and JS Foundation, please see this [repository](https://github.com/JSFoundation/standards). 21 | 22 | ## Collaboration Space Members 23 | 24 | ### Active Members 25 | 26 | - [@bkardell](https://github.com/bkardell) - Brian Kardell 27 | - [@christian-bromann](https://github.com/christian-bromann) - Christian Bromann 28 | - [@ctcpip](https://github.com/ctcpip) - Chris de Almeida 29 | - [@darcyclarke](https://github.com/darcyclarke) - Darcy Clarke 30 | - [@dtex](https://github.com/dtex) - Donovan Buck 31 | - [@eemeli](https://github.com/eemeli) - Eemeli Aro 32 | - [@gibson042](https://github.com/gibson042) - Richard Gibson 33 | - [@joesepi](https://github.com/joesepi) - Joe Sepi 34 | - [@jorydotcom](https://github.com/jorydotcom) - Jory Burson 35 | - [@leaverou](https://github.com/leaverou) - Lea Verou 36 | - [@ljharb](https://github.com/ljharb) - Jordan Harband 37 | - [@mikesamuel](https://github.com/mikesamuel) - Mike Samuel 38 | - [@tobie](https://github.com/tobie) - Tobie Langel 39 | - [@ulisesGascon](https://github.com/UlisesGascon) - Ulises Gascón 40 | - [@VoltrexKeyva](https://github.com/VoltrexKeyva) - Mohammed Keyvanzadeh 41 | - [@michaelchampion](https://github.com/michaelchampion) - Michael Champion 42 | - [@sendilkumarn](https://github.com/sendilkumarn) - Sendil Kumar N 43 | - [@rxmarbles](https://github.com/rxmarbles) - Rick Markins 44 | - [@nektro](https://github.com/nektro) - Meghan Denny 45 | 46 | ### Past Members 47 | 48 | - [@antsmartian](https://github.com/antsmartian) - antsmartian 49 | - [@craftninja](https://github.com/craftninja) - Emily Platzer 50 | - [@Eomm](https://github.com/Eomm) - Manuel Spigolon 51 | - [@LaRuaNa](https://github.com/LaRuaNa) - Onur Laru 52 | - [@obensource](https://github.com/obensource) - Ben Michel 53 | - [@MylesBorins](https://github.com/MylesBorins) - Myles Borins 54 | - [@littledan](https://github.com/littledan) - Daniel Ehrenberg 55 | 56 | 57 | 58 | -------------------------------------------------------------------------------- /img/poster1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/standards/1aa6011cfde3acec3f164a1bbe1e874c81754c87/img/poster1.jpg -------------------------------------------------------------------------------- /img/poster2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/standards/1aa6011cfde3acec3f164a1bbe1e874c81754c87/img/poster2.jpg -------------------------------------------------------------------------------- /img/poster3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/standards/1aa6011cfde3acec3f164a1bbe1e874c81754c87/img/poster3.jpg -------------------------------------------------------------------------------- /meeting-notes/2019.05.31_collabsummit_session.md: -------------------------------------------------------------------------------- 1 | # Notes from the OpenJS Foundation Collaborator Summit 2 | 3 | Date: 2019.05.31 4 | Location: Berlin 5 | Present: (Attendance was not taken; please make a PR to add your name if you wish to do so) 6 | Reference Links: 7 | * [proposal issue](https://github.com/nodejs/open-standards/issues/18) 8 | * [slides](https://docs.google.com/presentation/d/1tW7y1G0XYrIzujS_u82WWU9iO8-H2gWZODJQUmfnF7w/edit) 9 | 10 | ## Notes 11 | 12 | * @jorydotcom provided a brief overview of the JS Foundation's past and present participation at TC39 and W3C. 13 | * @littledan, @jasnell, @mylesborins, @jorydotcom & others fielded questions about standards participation. 14 | * The group brainstormed ideas for things a standards working group at the OpenJS Foundation could provide to the organization and community (see images below) 15 | * The group came up with several next steps we can take to get started, including: 16 | 17 | - [x] create a standards repo 18 | - [ ] create a calendar of events 19 | - [ ] schedule another working meeting 20 | - [ ] create a standards 'team' to collaborate on GH 21 | - [ ] confirm standards travel budget (board follow-up) 22 | 23 | ### Board steps 24 | 25 | - [ ] Mentorship in standards 26 | - [ ] Information distillation 27 | - [ ] impact to projects 28 | - [ ] reporting to ecosystem 29 | - [ ] Getting started in standards 30 | - [ ] documentation 31 | - [ ] why standars? 32 | - [ ] how W3C, WHATWG and TC39 work together? 33 | - [ ] specification writing and editing workshop 34 | - [ ] explainer for [MDN](https://mdn.dev/) 35 | 36 | 37 | *images of poster board notes* 38 | 39 | ![poster1](../img/poster1.jpg) 40 | ![poster2](../img/poster2.jpg) 41 | ![poster3](../img/poster3.jpg) 42 | -------------------------------------------------------------------------------- /meeting-notes/2019.07.02_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards WG meeting 2019-07-02 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/7 7 | 8 | ## Present 9 | 10 | - Myles Borins (@MylesBorins) 11 | - Jory Burson (@jorydotcom) 12 | - Richard Gibson (@gibson042) 13 | - Eemeli Aro (@eemeli) 14 | - Sendil Kumar (@sendilkumarn) 15 | - Brian Kardell (@bkardell) 16 | - Christian Bromann (@bromann) 17 | 18 | 19 | ## To discuss 20 | 21 | * [JB] FYI - Update on Status @ W3C & Ecma International 22 | 23 | EA: I would like to participate in 402 as a delegate 24 | JB: Let’s figure that out! 25 | MB: We need to bear in mind that we do not want to undermine the bus. Model of these orgs. Need to make sure people understand they are representing organizations and not themselves as individuals. 26 | RG: I think this is good summary - I work for an org that could join Ecma but in practice is not going to. 27 | EA: This is my situation as well. I would rather us not be in a position to have to define the terms (independent vs. not). 28 | MB: I think we need to be thoughtful and careful about how many reps we send and make sure they are going with the ‘OpenJSF’ hat on. Should we send people with very specific goals in mind? 29 | EA: I think it makes little sense to figure out what the rules are at this point and deal with this case by case. 30 | JB/RG: short description of how these decisions were made in the JS Foundation 31 | JB: {} 32 | BK: I think in general it would be good to have more cross-project discussion about what needs to exist or what needs to advance. That speaks more to our value of representing the JS Ecosystem. 33 | MB: The board charters the CPC, the CPC can charter other groups. We can put together a charter for this group. We tried to put as little as possible into the charter and as much as possible into the governance. We could go through this exercise as a group to get chartered by the CPC. 34 | EA: I don’t think there’s any need to make changes in the CPC charter. {reads relevant section from charter} 35 | MB: Then this group can get chartered by the CPC to handle that. 36 | BK: I think this is all useful, it;s also a little meta. I wonder in very practical ways is there something very simple we can do that we’re not doing? 37 | MB: Great question. We could do a TC39 or TPAC premeeting, etc. 38 | BK: Yes, this is a great example, +1 to that idea. 39 | 40 | * [JB] What is our Scope - what are things we could be doing 41 | Asking for feedback on specific proposals 42 | Outreach things that Dan et al are doing around TC39 43 | See stage-0 proposals 44 | https://github.com/openjs-foundation/cross-project-council/blob/HEAD/proposals/incubating/SHARED_INTERFACES/README.md 45 | https://github.com/openjs-foundation/cross-project-council/blob/HEAD/proposals/incubating/STANDARDS_OUTREACH/README.md 46 | Pre-meetings for TPAC, TC39 meetings 47 | BUDDY SYSTEM! 48 | Play a connector role around standards and working groups 49 | Meetups with TAG, etc 50 | Disseminate information about what these groups are doing/talking about/working on 51 | EA: I was not aware that the JSF was participating. It was not easy to get that info. I hope we can do more to inform people about what we’re doing. 52 | CB: It should be easy for someone from the outside to understand and get involved/participate. 53 | BK: One of the things W3C does now is that they have a buddy system to help you navigate 54 | 55 | * [JB] Travel Budget Clarification 56 | 57 | BK: No thoughts beyond I have no idea - rely on other people :) 58 | 59 | * [JB] TPAC in September 60 | 61 | Who’s attending? Christian, Myles, Brian, Jory - 62 | AI: Open an issue in the Standards repo to discuss the agenda and figure out if anyone needs proxies/etc 63 | AI: Schedule a pre-meeting for those interested? 64 | 65 | ## To decide 66 | 67 | * How often are we gonna meet (weekly or bi-weekly or other)? Decide the time and day for the recurring meeting? 68 | 69 | BK: weekly seems excessive 70 | SK: once every two weeks? 71 | MB: this webinar is set as a recurring bi-weekly 72 | DONE 73 | MB: Will update the meeting tool to generate all this for us 74 | 75 | ## Questions 76 | 77 | * [SK] Getting started with Standards: 78 | - What is the general plan here? What do we expect to have in MVP? 79 | 80 | JB: We could add learning resources to the repo 81 | EA: How do we want to present ourselves to the SDOs and to the JSDev audience at large? Are we really pitching ourselves as part of the projects or as part of the larger organization (OpenJSF) 82 | BK: Excellent question - historically we were rooted in the projects 83 | CB: Maybe this is something we want to define as a Working group 84 | EA: it also extends to the OpenJSF as a whole 85 | 86 | * [SK] Specification Writing & Workshop: 87 | - Are there any resources already available? 88 | - Are we gonna have this during the collab summit? 89 | -------------------------------------------------------------------------------- /meeting-notes/2019.08.13_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2019-08-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Yszomt26QpI 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/12 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Jory Burson (@jorydotcom) 15 | * Joe Sepi 16 | * Mike Dolan 17 | * Sendil Kumar (@sendilkumarn) 18 | * Even Stensberg 19 | * Ajay 20 | * Richard Gibson! 21 | 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | What are the deliverables this group wants to work on? 30 | A proposal for selecting Reps for us to W3C / Ecma 31 | 32 | What are some of the things we should focus on? 33 | What are the things we can move forward on? 34 | 35 | JB: I suggest we start with some process for selecting individuals to represent us ... 36 | SK: Onboarding ... 37 | JB: Open Source to Standards path for OJS 38 | JS: What about the diff. hats people wear 39 | 40 | Possible Requirements for reps? 41 | * Need to consider conflicts of interest 42 | * Meeting travel availability 43 | * promote agenda topics / notes etc?~ 44 | * do we need to have some meeting or call for comments / open office hour discussion time prior to meetings 45 | * RG: try something - Richard to send out a request for review/comment/feedback/desire for summary ahead of the October Meeting. 46 | * JB: to do the same with TC53 47 | * what about W3C? Maybe hold off because it’s a bit more complicated 48 | * projects may be more interested in spec bugs and gaps more commonly than say, getting a feature etc standardized 49 | * perhaps collaborate with WPT / Test262 50 | 51 | AI: Richard & Jory to do a test call for responses prior to TC39 / TC53 meetings 52 | AI: Create an issue for rep selection process proposal, to deliver to CPC 53 | AI: Create an issue for what a rep might need to know for onboarding 54 | AI: Create an issue for capturing requirements for the reps 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Calendar**: https://nodejs.org/calendar 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | -------------------------------------------------------------------------------- /meeting-notes/2019.09.10_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2019-09-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=7Rr9UTmMj8k 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/26 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | Jory Burson (@jorydotcom) 15 | Donovan Buck (@dtex) 16 | Brian Kardell (@briankardell) 17 | Joe Sepi (@joesepi) 18 | Richard Gibson (@gibson042) 19 | Joe Sepi (@joesepi) 20 | Dan Ehrenberg (@littledan) 21 | Jordan Harband (@ljharb) 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Document governance for the standards-wg [#19](https://github.com/openjs-foundation/standards/issues/19) 32 | 33 | We can use the [cpc governance doc](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/GOVERNANCE.md) to start as a starter. 34 | Brian + Jory + TPAC group to workshop a draft next week to share with the group 35 | 36 | * Define and Document the on-boarding process for the Representative [#14](https://github.com/openjs-foundation/standards/issues/14) 37 | https://github.com/openjs-foundation/standards/pull/21 38 | 39 | Does this capture everything? 40 | Hard to say. Reporting requirement - summary back to the community 41 | Also perhaps a pre-meeting conversation 42 | “We won’t cover your expenses unless you are claiming to represent the foundation” 43 | People who have some specific proposal to champion vs. people who are playing an ambassador type role 44 | Ambassador roles could be part of the TC39 outreach project effort 45 | Clarity should be required around what capacity someone is serving and what 46 | Maybe work on some talking point/goal/objective doc to focus this prior to a meeting 47 | Responsibility to convey the viewpoint of foundation members that gave it, this includes the representatives themselves who are free and encouraged to provide their technical opinion as well 48 | Responsibility to make sure the things you say that do not reflect the foundation’s opinion are not misconstrued as such 49 | 50 | * Define and Document requirements for the (Standards) Representative [#13](https://github.com/openjs-foundation/standards/issues/13) 51 | 52 | * Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6) 53 | 54 | Need estimates for next year’s participation 55 | 56 | * TC53 participation 57 | https://github.com/openjs-foundation/standards/issues/24 58 | 59 | Action Items: Discuss getting OpenJSF added to the TC53 roster. Clarify policy/IPR commmitments between representatives and the OpenJS Foundation. 60 | 61 | ## Q&A, Other 62 | 63 | ## Upcoming Meetings 64 | 65 | * **Calendar**: https://nodejs.org/calendar 66 | 67 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 68 | 69 | 70 | -------------------------------------------------------------------------------- /meeting-notes/2019.12.17_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2019-12-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=yIDtmaepsHM 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/40 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | ## Agenda 15 | 16 | ### Announcements 17 | 18 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 19 | 20 | ### openjs-foundation/standards 21 | 22 | * TC-53 Participation [#24](https://github.com/openjs-foundation/standards/issues/24) 23 | * Start accepting nominations for "active" members [#23](https://github.com/openjs-foundation/standards/issues/23) 24 | * Define and Document the on-boarding process for the Representative [#14](https://github.com/openjs-foundation/standards/issues/14) 25 | * Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6) 26 | 27 | ## Q&A, Other 28 | 29 | ## Upcoming Meetings 30 | 31 | * **Calendar**: https://calendar.openjsf.org 32 | 33 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 34 | 35 | 36 | -------------------------------------------------------------------------------- /meeting-notes/2020.01.14_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-01-14 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=3Zo9NmvgOms 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/54 7 | 8 | ## Present 9 | 10 | * Jory Burson (@jorydotcom) 11 | * Brian Kardell (@bkardell) 12 | * Myles Borins (@MylesBorins) 13 | * Jordan Harband (@LJHarb) 14 | * Sendil Kumar (@sendilkumarn) 15 | * Richard 16 | * Mike Samuel 17 | 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 24 | 25 | * Brian: shares that the results from the TAG are in. David, Kenneth, Rossen were elected. 26 | 27 | ### openjs-foundation/standards 28 | 29 | * Audit membership list [#53](https://github.com/openjs-foundation/standards/issues/53) 30 | 31 | Suggested cleanup of existing membership list. 14 members on the team. Culled from the list after 14 days. Myles to close issue and Jory to follow up with the 2-3 list members who haven’t been participating. 32 | 33 | * Joining the Unicode Consortium 34 | [#43](https://github.com/openjs-foundation/standards/issues/43) 35 | 36 | * Eemeli isn’t present; will table discussion until they are present 37 | * There is a cost related to membership - it would be reasonable for the proposal to find out which level we would want to join. 38 | 39 | * OSI Affiliate Membership [#32](https://github.com/openjs-foundation/standards/issues/32) 40 | 41 | * We brought this up at the CPC meeting; it was well received. 42 | * Ref: https://opensource.org/affiliates; https://opensource.org/affiliates/about 43 | * we would want to be Affiliate members; it is a non-profit membership. We have to apply and meet the qualifications. 44 | * “Make annual contributions where possible” but there is no direct expectation for fees 45 | * we would be able to nominate / vote for affiliate director. 46 | * Time sensitivity due to upcoming elections 47 | * Group generally agrees; the idea would be that this membership would be managed through the standards wg. Foundation could execute paperwork on behalf of the group. 48 | * Next step: Board approval 49 | 50 | * TC-53 Participation [#24](https://github.com/openjs-foundation/standards/issues/24) 51 | 52 | * Still waiting to hear back from Robin and Brian; Jory to bump again and add Donovan & Myles 53 | * Upcoming meetings related to TC53: teleconference on 1/15 and in person meeting at the end of Feb. in TX 54 | 55 | * Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6) 56 | 57 | * We have a $60k budget for the foundation this year, we used $30k last year. 58 | * Standards travel could eat in to that. 59 | * In general we would expect companies who are members of the foundation and are sending people on behalf of their organizations to pay for their people 60 | 61 | * On-boarding process PR [#50](https://github.com/openjs-foundation/standards/pull/50) 62 | 63 | * MV process 64 | 65 | 66 | ## Q&A, Other 67 | 68 | * Calendar? Let’s give it a try. 69 | * Note taking is a great way to get started in a standards group. 70 | 71 | ## Upcoming Meetings 72 | 73 | * **Calendar**: https://calendar.openjsf.org 74 | 75 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 76 | 77 | 78 | -------------------------------------------------------------------------------- /meeting-notes/2020.01.28_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-01-28 2 | 3 | ## Links 4 | 5 | * **Recording**: http://www.youtube.com/watch?v=KkKCCs9QIY4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/61 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Sendil Kumar N (@sendilkumarn) 15 | * Myles Borins (@MylesBorins) 16 | * Jory 17 | * Eemeli Aro (@eemeli) 18 | * Mike 19 | * Jordan Harband (@LJHarb) 20 | * Richard 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | * TC39 next week in Sunny HI 29 | 30 | ### openjs-foundation/standards 31 | 32 | * Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58) 33 | 34 | * Was briefly presented at today’s CPC meeting. Example used: OSI membership. 35 | * No concerns or objectives, the ball is in our court to create a charter and bring it to the CPC for review and approval 36 | * Theoretically similar to the project chartering process for project onboarding 37 | Getting the process together and figuring it out - 38 | Mike: how can I help? 39 | Myles: I’ll open a PR with the template charter, we should review and comment; I think we need true consensus before we go to the CPC for sign-off 40 | * Discussion about ensuring the charter and the governance docs are well aligned 41 | Mike: PRs take awhile for people to incorporate edits - can we start with a gdoc for faster iteration? 42 | Myles we can do that esp for getting the first pass done. Let’s make a doc and drop it in teh issue 43 | Mike: makes a link & drops it 44 | Jory: do the docs from /Admin have any bearing on this? 45 | Myles: I don’t think so. Kindof seems like the working groups in Node just have governance docs. We have 90% of what the Node Admin reqs have, just a couple of things missing 46 | Are we a working group of the CPC or a different autonomous entity? 47 | Eemeli: I think its simplest if we are under the CPC 48 | Myles: I think these issues would go to the CPC and only go to the board if we were unhappy with the results 49 | Myles: should we amend our gov. Docs and take this to the CPC? 50 | Group: +1 51 | Myles: I’ll take the AI 52 | 53 | * governance: getting permission to attend meetings [#56](https://github.com/openjs-foundation/standards/pull/56) 54 | 55 | * do we need to require the person to be a member / representative of the standards wg? 56 | Should attend a standards wg meeting as requested 57 | Should be a member of one of our project communities 58 | Discussion of the purpose of the group (node modules wg example) 59 | Empowering the projects to participate 60 | The ask is for projects to report their participation 61 | There is a bit of internal conflict; we need to be able to serve projects and provide a consistently applied process 62 | What’s the minimum process? We shouldn’t introduce a regression. 63 | What are the simplest steps? File an issue & tell us about it. If you want to rep the foundation that would require approval. 64 | 65 | * Joining the Unicode Consortium [#43](https://github.com/openjs-foundation/standards/issues/43) 66 | 67 | * Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6) 68 | 69 | 70 | ## Q&A, Other 71 | 72 | ## Upcoming Meetings 73 | 74 | * **Calendar**: https://calendar.openjsf.org 75 | 76 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 77 | 78 | -------------------------------------------------------------------------------- /meeting-notes/2020.02.25_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-02-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=6gVlu3rBm0g 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/63 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Joe Sepi 15 | * Mike Samuel (@mikesamuel) 16 | * Jory Burson 17 | * Jordan Harband (@LJHarb) 18 | * Myles Borins 19 | * Eemeli Aro (@eemeli) 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58) 32 | 33 | The thing we need to land is the document about who can go to meetings, etc. (#56) 34 | Need to get the WG docs added from Admin (some of which Joe has started) - Joe will work on this before next CPC meeting. (#443) 35 | Joe - would you like to break up this work into separate PRs? 36 | That’s not necessary - whoever wants to do the work should just do it’ 37 | Mike: what kind of help (copy editing, etc), what should I be looking at? 38 | Converting language from ‘Node’ Foundation, etc 39 | Joe: I would like to make progress on this before the next meeting 40 | 41 | * governance: getting permission to attend meetings [#56](https://github.com/openjs-foundation/standards/pull/56) 42 | 43 | Myles: have had some suggestions from Eemeli 44 | 45 | Myles: 46 | 47 | * Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6) 48 | 49 | ## Q&A, Other 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Calendar**: https://calendar.openjsf.org 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | 57 | -------------------------------------------------------------------------------- /meeting-notes/2020.03.10_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-03-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ZNo-Thqz_wc 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/65 7 | 8 | ## Present 9 | 10 | * Myles Borins (@MylesBorins) 11 | * Jory Burson (@jorydotcom) 12 | * Robin Ginn (@rginn) 13 | * Brian Kardell (@bkardell) 14 | * Sendil Kumar N (@sendilkumarn) 15 | * Jordan Harband (@LJHarb) 16 | * Eemeli Aro (@eemeli) 17 | 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 24 | 25 | ### openjs-foundation/standards 26 | 27 | * Participation in the Unicode MessageFormat WG [#64](https://github.com/openjs-foundation/standards/issues/64) 28 | * Robin: Legal team approved. Waiting for final approval from the consortium. 29 | * Myles: Relatedly, is there any updated on the OSI? 30 | * Robin: This is in a similar state, no status update at the moment. Will checkin with OSI. 31 | * AI: remove the agenda label. 32 | * Standards-related Travel Budget Clarification - [#6](https://github.com/openjs-foundation/standards/issues/6) 33 | * Jory: The issue is stale. We moved past other conversations. 34 | * Myles: Projects may sign in to vouch for travel. The CPC will eventually approve the travel request. 35 | * AI: remove the agenda label. 36 | * Request to attend TC39 as OpenJS delegate [#66](https://github.com/openjs-foundation/standards/issues/66) 37 | * Myles: Gus attended TC39 before (both remotely and in-person). He is technically on-boarded. Appreciate that he took part in the process. Does anyone have objections? 38 | * Jordan: No objections. (he is qualified). Gus is not a regular member, can he attend? 39 | * Myles: Empower those who want to attend. 40 | * Jordan: Thanks. 41 | * Jory: Encourage other folks to do. Getting early feedback and sharing this will be awesome. 42 | * Myles: Do you (Richard) think it is reasonable to ask the delegate representation to be permanent? 43 | * Richard: There is a lot of value in those. If Gus wanted to attend regularly that makes sense. It is also nice if he wants to focus. 44 | * Jordan: Even with one delegate it makes sense. If there are multiple delegates they have to coordinate between them but it is also good to have. 45 | * Myles: Some of this topics might be sensitive, it would have been better to do it privately first. Explore the governance and make it part of the process for this discussion. 46 | * AI: Edit Governance to accommodate the above text. 47 | * Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58) 48 | * Myles: CPC is in process to review. There is a PR in CPC (https://github.com/openjs-foundation/cross-project-council/pull/443). Once that lands. 49 | * The scope is outlined here - https://hackmd.io/kkjTah1XTh2-ubcKLxQD4Q. Review this and make a PR. 50 | * Myles: going through the https://hackmd.io/kkjTah1XTh2-ubcKLxQD4Q 51 | * Jordan: preference for the 1st paragraph 52 | * Removed the second para 53 | * Myles: Does anyone object to the responsibility? 54 | * (all): none 55 | * --- 56 | * Eemeli: Should we preemptively include Michael Dawson’s Working Group initiative. Meeting about effectively creating WG and be in charge of the space for standards. 57 | * Myles: It is about more ad-hoc groups. Standards is one of those areas. What is the relationship between that group and our group. In WASM, CG is where work happens and WG is administrative. It might be premature for us to document. It might be possible if Standards WG is spin up, we might then draft something on how both should work. 58 | * Eemeli: --- 59 | * Myles: Maybe a good litmus test, would anyone will be concerned about affiliation with a group for direct engagement 60 | * Robin: Can you elaborate more on the direct engagement 61 | * Brian: You have to clear when you are representing the foundation. Wearing multiple hats. 62 | * Myles: describing the spaces (when there is a difference of opinions and disagreements). This group is responsible for facilitating that. 63 | * Jordan: delegates from the same company disagreed and they handled it beforehand. But it did not happen correctly in the past. 64 | * Robin: It has to be open and transparent. 65 | * Brian: Perhaps one aspect, gauge and provide opportunities for internal consensus seeking. We don’t have any example or any possible process. It would be pretty powerful if we have single voice 66 | * Myles: People having individual voices is also important. Each of these hats is extremely important and we should facilitate that. 67 | * Richard: Do we have any thoughts on the mechanism? 68 | * Myles: --- 69 | * Richard: OpenJS sends multiple delegates and they focus on different items. 70 | * Myles: It is situational here. (explaining with a few examples) 71 | * Myles: may be there is an educational angle here. (ordering the resp.) 72 | * Myles: the scope document will live in the CPC not in standards. (going through the member-expectations document) 73 | * Myles: create an auto populated issue template from member expectations. 74 | * Brian: W3C has the AC role. It seems it will be good if some of them come to standards Group. 75 | * (No objections for the edited document) 76 | * Myles: Will @ the standards team when the document is PR’ed into the CPC. (no objections). 77 | 78 | 79 | ## Q&A, Other 80 | 81 | No questions :) 82 | 83 | ## Upcoming Meetings 84 | 85 | * **Calendar**: https://calendar.openjsf.org 86 | 87 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 88 | 89 | 90 | -------------------------------------------------------------------------------- /meeting-notes/2020.03.23_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-03-24 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=EhGbbJOycaw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/73 7 | 8 | ## Present 9 | 10 | * Jory Burson 11 | * Mike Samuel 12 | * Donovan Buck 13 | * Jordan Harband 14 | * Joe Sepi 15 | * Myles Borins 16 | * Richard Gibson 17 | * Senthil 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 24 | 25 | We did not have any agenda items so instead spent the time brainstorming session ideas for the collab summit. Those ideas will be documented in a new issue. 26 | 27 | 28 | ## Q&A, Other 29 | 30 | ## Upcoming Meetings 31 | 32 | * **Calendar**: https://calendar.openjsf.org 33 | 34 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 35 | -------------------------------------------------------------------------------- /meeting-notes/2020.04.07_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Team Meeting 2020-04-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | 16 | ## Agenda 17 | 18 | No issue for this: Content for OpenJS 19 | Would like to do a blog post introducing the first chartered WG 20 | Also a quarterly update post 21 | How to track the content that we would want to report on 22 | Who do we delegate this to - in order to get it done 23 | Shouldn’t be a heavy lift 24 | Mike Samuel volunteers to help with producing this 25 | Start a Hack.md to collaborate on announcement doc 26 | “Here’s how a project I worked on” - ground the relevance 27 | What would the call for action be? 28 | Call for projects to get involved 29 | Calendar 30 | AI to Jory to talk to Brian about groups.io 31 | AMA for the Standards WG? July is the next opening 32 | Other standards related topics to cover on the blog? 33 | Recaps of meetings or “this is what it was like” 34 | Richard sync with Rachel 35 | 36 | News - approval from OSI has been received 37 | Myles & Brian figuring out what is needed for the affiliate membership and how we participate 38 | 39 | 40 | 41 | ### Announcements 42 | 43 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 44 | 45 | 46 | 47 | ## Q&A, Other 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Calendar**: https://calendar.openjsf.org 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | 56 | -------------------------------------------------------------------------------- /meeting-notes/2020.05.05_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-05-05 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/87 7 | 8 | ## Present 9 | 10 | * Myles Borins (@MylesBorins) 11 | * Sendil Kumar N (@sendilkumarn) 12 | * Brian Kardell (@bkardell) 13 | * Mike Samuel (@mikesamuel) 14 | * Jordan Harband (@ljharb) 15 | * Donovan Buck (@dtex) 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 22 | 23 | 24 | 25 | ### openjs-foundation/standards 26 | 27 | * Nominate OSI Representative [#89](https://github.com/openjs-foundation/standards/issues/89) 28 | Scope is not well known 29 | Myles self nominated. Cross posted to CPC. 30 | Robin why is this limited to standards? 31 | Myles: charter includes “manage relationships with standards organizations” 32 | Jordan: who do we want to reach who is not in standards WG and would be appropriate nominee? 33 | Jory: ok to cross post. If projects are paying attention to one [GH project] it’s probably CPC 34 | Robin: Is OSI just a “standards organization”? 35 | Myles: [If CPC wants to undelegate] do we need to massage the standards charter. CPC should be careful before acting on something that seems to have been delegated. 36 | Jordan: Robin, what is OSI 37 | Robin: Interactions with OSI include things unrelated to technical standards making 38 | Brian: It's sometimes a little hard to say "what is an SDO" it is listed on http://www.openstandards.net/viewOSnet2C.jsp?showModuleName=Organizations for example and W3C was created with the view that it wouldn't be an SDO, but it is largely seen as one. 39 | Myles: OSI may be on the line. There may be other organizations which are on the line but which Standards WG wants to manage, and seek CPC approval for delegation of additions. A list would clarify. 40 | Jory: Nomination will remain open for a week. 41 | 42 | * Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84) 43 | 44 | Current discussion is over thematic disagreement over individual autonomy, for example to block consensus 45 | Relationship between the Foundation as a Member Trade org, and its membership / expectations for participation in an SDO 46 | Action Item: if people expressed opinions last meeting or have thoughts from this meeting, please add them to issue #84. 47 | Myles: actions taken by delegates on behalf of OpenJS Fdn should be “built on a bed of consensus” 48 | Jordan: my experience from TC39 is people are clearly balancing their own opinions and their organizational duties. Some employers put people on leash, but it’s not infrequent for people to say “my opinion is ...; my employer wants …” 49 | Jordan: power to block comes from procedures 50 | Myles: blocking is voting 51 | Jordan disagrees with framing 52 | Mike Samuel: Need rigorous facility for assessing / building consensus or opinions (see comment) but ultimately have to trust delegates to advance their understanding of the consensus and deal with repeated failure to represent consensus after the fact. 53 | Brian: Blocking seems a discrete question so we can build a process specifically for that. 54 | Robin: I spoke up last week supporting Myles. 55 | Jordan: Any action has to be justified after the fact. In TC39, most actions are blocking. Not advocating for lack of accountability; just for not constraining actions [in unforeseen situations?]. The perception of blocking as a hammer does not match my experiences with TC39 specifically; blocking is often a good thing since the organization biases towards not changing the language. 56 | 57 | * Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83) 58 | 59 | * Collect info from standards meeting attendees [#81](https://github.com/openjs-foundation/standards/issues/81) 60 | 61 | https://hackmd.io/vj30p217SZa8U3KLZTVXOg?view 62 | 63 | * Craft the Standards Working Group Mission statement [#80](https://github.com/openjs-foundation/standards/issues/80) 64 | 65 | Mike Samuel submitted related PR: https://github.com/openjs-foundation/standards/pull/88 66 | 67 | The Standards Working Group actively monitors evolving standards to educate projects about developments that might affect them, and helps projects formulate standards strategies and advance them before standards bodies. 68 | 69 | 70 | 71 | 72 | 73 | ## Q&A, Other 74 | 75 | ## Upcoming Meetings 76 | 77 | * **Calendar**: https://calendar.openjsf.org 78 | 79 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 80 | 81 | -------------------------------------------------------------------------------- /meeting-notes/2020.05.19_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-05-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=W7s2B1xBgwA 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/90 7 | 8 | ## Present 9 | 10 | * Jory Burson (@jorydotcom) 11 | * Jordan Harband (@ljharb) 12 | * Eemeli Aro (@eemeli) 13 | * Donovan Buck (@dtex) 14 | * Mike Samuel (@mikesamuel) 15 | * Robin Ginn (@rginn) 16 | * Joe Sepi (@joesepi) 17 | 18 | * OpenJS Foundation Cross Project Council 19 | * OpenJS Foundation Project Maintainers 20 | * OpenJS Foundation Board of Directors 21 | 22 | 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | Jory: 29 | * Open Office Hours this Thursday 30 | * Marketing meeting after this meeting 31 | * Board meeting this Friday 32 | * OpenJS World and Collab Summit is in about 4 weeks. Projects: submit sessions for summit; everyone register for event. 33 | 34 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 35 | 36 | ### openjs-foundation/standards 37 | 38 | * Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84) 39 | * Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83) 40 | * Collect info from standards meeting attendees [#81](https://github.com/openjs-foundation/standards/issues/81) 41 | 42 | 43 | 44 | * Craft the Standards Working Group Mission statement [#80](https://github.com/openjs-foundation/standards/issues/80) 45 | Ship related PR 46 | 47 | Standards Blog Post - Ship it 48 | 49 | Collab Summit Sessions 50 | 51 | Private email list discussion: Legal recommends against it 52 | Private discussions should be held verbally 53 | Suggest language such as “discussion ensued over X” 54 | 55 | Unicode Consortium 56 | Waiting on official acceptance from the Org - check in with 57 | Talk to Rafael RE participation 58 | 59 | 60 | 61 | 62 | ## Q&A, Other 63 | 64 | ## Upcoming Meetings 65 | 66 | * **Calendar**: https://calendar.openjsf.org 67 | 68 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 69 | 70 | 71 | -------------------------------------------------------------------------------- /meeting-notes/2020.06.02_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-06-02 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | 16 | ## Agenda 17 | 18 | ### Announcements 19 | 20 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 21 | 22 | ### openjs-foundation/standards 23 | 24 | * New relationship with Unicode Consortium 25 | https://github.com/openjs-foundation/standards/issues/43 26 | 27 | We were accepted as associate members 28 | Ben Michel would like to participate as well 29 | Discussion with Steven & Ben: Bookmarking this to continue the conversation effectively for next time 30 | Idea to do a presentation on the Unicode Consortium & the other member orgs 31 | Invite Alolita to come present 32 | 33 | * \[TC39\] Potentially blocking "Module Attributes" proposal [#91](https://github.com/openjs-foundation/standards/issues/91) 34 | 35 | * Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84) 36 | 37 | * Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83) 38 | 39 | 40 | 41 | 42 | ## Q&A, Other 43 | 44 | ## Upcoming Meetings 45 | 46 | * **Calendar**: https://calendar.openjsf.org 47 | 48 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 49 | -------------------------------------------------------------------------------- /meeting-notes/2020.06.16_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-06-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/94 7 | 8 | ## Present 9 | * Mike Samuel (@mikesamuel) 10 | * Myles Borins (@MylesBorins) 11 | * Jordan Harband (@LJHarb) 12 | * Ben Michel (@obensource) 13 | * Sendil Kumar (@sendilkumarn) 14 | 15 | 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 22 | 23 | ### openjs-foundation/standards 24 | 25 | * Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84) 26 | 27 | Myles: There’s a difference of opinions at the moment, such that I don’t think we’re going to reach consensus. We’ll need to move forward with people acting in good faith in the position they have. There’s so much going on that we don’t have time to discuss every single issue. 28 | 29 | It’s possible that someone can raise an issue as a pre-meeting, potentially topics that are controversial, which we can come to consensus on before moving forward with a meeting. 30 | 31 | How much consensus do we need before moving on with decisions under general agreement without getting into too much process? The blocks in tc39 are very particular to a specific organization, in OpenJS – we need to answer the questions as to how we want to do this in our own regard. 32 | 33 | Brian: We’re very in the weeds on what you can or can’t do. If you’re in the room and you can wear multiple hats, you can speak up all along the way and be very clear as to which hat you’re wearing at the time. So, how do we communicate, and can we build consensus? Are there ways that we can come to consensus on with a wider voice of the openjs community. I agree with Myles. 34 | 35 | Sendil: I agree too. Bringing the discussions down before going to any particular standards body is good. If we need to we can formalize it later rather than discussing it now. 36 | 37 | Eemeli: We haven’t been clear – there ought to be an expectation on delegates for them to actively let us know what’s going on in other bodies. Tc39 is the only one we’ve only been actively discussing hear in the standards WG. Are there other things we need to talk about in the Standards group right now? 38 | 39 | Brian: We’ve had multiple areas of interest across many standards bodies. For example, I’ve been involved in the CSS WG – and we care about it, but we can’t bring all the concerns of that body to this group. 40 | 41 | Sendil: Is there any historic precedent for us, and/or any info as to how we can operate in this way? In the past, was there a standards body that has been through this before? Can we leverage their experience? 42 | 43 | Robin: Many organizations will have this in order to make business decisions across orgs, etc. 44 | 45 | Myles: At google we had pre meetings like this, and this is a good way to handle this sort of thing. Maybe we can have people sign up for a mailing list where we are setting up clarity for anyone and any project who wants to be involved. Our reps who represent OpenJS need to focus on representing the foundation and the consensus that we’ve built to those organizations. 46 | 47 | Robin: Our staff can help with the community resources, and we’d love to stay informed on what’s happening and where change is needed. 48 | 49 | Donovan: We don’t have guidelines for delegates. Is there a document for expectations of delegates anywhere? Communicating through email lists, etc, is what I’d expect of delegates. 50 | 51 | Sendil: If we can extend our document to reflect that, it would be a good decision. 52 | 53 | Brian: We also have i18n, and 402, and Embedded, and other things in ECMA etc, and other stuff delegates are interested in – testing, privacy, ietf, etc. Do we need a single catch all list for everything? Are we working on expectations for tc39 as a starting point? 54 | 55 | Myles: I hope that a lot of the guidance that we have should be clear across orgs. We should have a document about how we support organizations. We could have a folder or structure to reflect in documenting our interactions with each org. What’s the decision making, how do you get involved with a project. Maybe we could use our Wiki for this? 56 | 57 | Brain: But how do we keep up with standards and projects, do we do a pre meeting, etc? We don’t want a firehose? 58 | 59 | Ben: What’s our scope per standards body that we wish to discuss at each Standards meeting? In other words, how much & what does our Foundation care about needing to know? 60 | 61 | Myles: What is appropriate, what makes sense? Maybe there’s something we need to formalize with this Liaison role? Something we can surface per liaison, and within the foundation – what is the way we represent what matters per organization to the Foundation? 62 | 63 | If you represent a standards body here within the Standards WG, are a liaison, etc: please add your name to this list. 64 | 65 | * Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83) 66 | 67 | ## Q&A, Other 68 | 69 | ## Upcoming Meetings 70 | 71 | * **Calendar**: https://calendar.openjsf.org 72 | 73 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 74 | 75 | 76 | -------------------------------------------------------------------------------- /meeting-notes/2020.07.14_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-07-14 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/99 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Donovan Buck (@dtex) 12 | * Jordan Harband (@ljharb) 13 | * Myles Borins (@MylesBorins) 14 | * Brian Kardell (@bkardell) 15 | * Robin Ginn 16 | * Mike Samuel 17 | 18 | 19 | 20 | 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | ### openjs-foundation/standards 29 | 30 | * Discuss necessity or lack thereof, of having a chairperson for the team. Discussed the possibility of a “chore wheel”. 31 | 32 | 33 | * MBS: We could explore automating the transfer of notes from the Google doc to the repo. Might be worth looking into. 34 | 35 | * MBS: TC-39 deadline for discussion is upcoming and it’s a good time to take a look at proposals that are up for advancement 36 | 37 | * JBN: TC-53 is meeting tomorrow 38 | 39 | * BKL shares announcement from Igalia: I work for Igalia and we work on all the open source web browsers. Tons of companies participate in creating web standards, Igalia helps gets them implemented. We thought it would be good if groups could collaborate and prioritize things to implement. We’ve identified 6 that anyone can go and contribute to help get the feature implemented. We hope this experiment will help start some healthy discussions about how the web can move forward. 40 | 41 | https://www.igalia.com/open-prioritization/ 42 | 43 | ## Q&A, Other 44 | 45 | ## Upcoming Meetings 46 | 47 | * **Calendar**: https://calendar.openjsf.org 48 | 49 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 50 | 51 | 52 | -------------------------------------------------------------------------------- /meeting-notes/2020.08.25_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-08-25 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/104 7 | 8 | ## Present 9 | 10 | * Jory Burson 11 | * Robin Ginn 12 | * Myles Borins 13 | * Mike Samuel 14 | * Richard Gibson 15 | * Donovan Buck 16 | * Eemeli Aro 17 | * Sendil Kumar 18 | * Mike Samuel 19 | 20 | * OpenJS Foundation Cross Project Council 21 | * OpenJS Foundation Project Maintainers 22 | * OpenJS Foundation Board of Directors 23 | 24 | 25 | 26 | ## Agenda 27 | 28 | ### Announcements 29 | 30 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 31 | 32 | ### openjs-foundation/standards 33 | 34 | * Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102) 35 | 36 | What gap do we fill? 37 | How do we track / continue to support? 38 | Distinction between representing the project (Node) vs. the foundation (all of OpenJS) 39 | Action: Create venue for soliciting feedback 40 | Action: Documenting proposal process 41 | Action: Similar for W3C votes 42 | Action: Check in with Gus! 43 | 44 | * Meeting time (Ad Hoc, raised from CPC meeting) 45 | * CPC meetings are alternating with an earlier meeting time as an experiment 46 | * back to back with CPC meeting is probably ideal 47 | * 48 | 49 | * TC53 Meeting Update 50 | * working on first specification(s) - first draft expected in about a month 51 | * After first draft we would love to get feedback from the broader community - need to identify which projects would be interested 52 | * Robin happy to use marketing resources to help share information 53 | 54 | * Check with Ben on Unicode Blog 55 | 56 | 57 | * Chore Wheel Items 58 | Agenda 59 | Triage 60 | Meeting reminders to people 61 | Hosting 62 | Notes taking 63 | 64 | * Make 2021 Strategy Meeting - file issue 65 | * Note about the word “Member” 66 | 67 | 68 | ## Q&A, Other 69 | 70 | ## Upcoming Meetings 71 | 72 | * **Calendar**: https://calendar.openjsf.org 73 | 74 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 75 | 76 | 77 | -------------------------------------------------------------------------------- /meeting-notes/2020.09.08_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-09-08 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | Brina Kardell 15 | Myles Borins 16 | Eemeli 17 | Jory Burson 18 | Donovan Buck 19 | Jordan Harband 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | ### openjs-foundation/standards 28 | 29 | * Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102) 30 | 31 | * TPAC Breakout proposals - Discussion regarding ongoing things at W3C, and how OpenJS and W3C can work together. Will be revisited at the end of October. BK will share a schedule and breakouts for TPAC event (https://www.w3.org/wiki/TPAC/2020/GroupMeetings
) 32 | 33 | * Possible role for OpenJS Foundation in helping to maintain/steward proposal polyfills for new language features. MDN had been moving towards pointing to NPM packages instead of including polyfills on MDN pages. Not sure what will happen at MDN going forward so can OpenJS help with this? BK will open a new issue for discussion (tag with “standards-agenda”). 34 | 35 | * Discussion of opportunities to share information from standards bodies activities with member projects. No role for OpenJS to have early discussion of notes prior to their public release, as attendees will need an opportunity to ensure their words are fairly represented. DB will open a new issue for discussion (tag with “standards-agenda”). 36 | 37 | * WICG is creating a new way to create proposals. Might be interesting to various projects (https://github.com/WICG/proposals) 38 | 39 | * Discussion around set of “Getting started” resources for community members who are interested. 40 | 41 | ## Q&A, Other 42 | 43 | RG: Re-iterates importance of agendas and notes as they pertains to foundation. 44 | MB: Reminds the group that in the event of little or no events on agenda, we can always cancel. 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Calendar**: https://calendar.openjsf.org 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | 52 | 53 | -------------------------------------------------------------------------------- /meeting-notes/2020.10.06_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2020-10-06 2 | 3 | ## Links 4 | 5 | * **Recording**:https://www.youtube.com/watch?v=34DxEp4x2lk&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/108 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn 12 | * Myles Borins 13 | * Mike Samuel 14 | * Brian Kardell 15 | * Mike Champion 16 | * Jordan Harband 17 | * Richard Gibson 18 | * Jory Burson 19 | * Donovan Buck (@dtex) 20 | 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | ### openjs-foundation/standards 29 | 30 | * A home for reference-implementation polyfills [#106](https://github.com/openjs-foundation/standards/issues/106) 31 | BK: Currently in the standards dev process, proposal go from speculative idea polyfill to a “true” polyfill to patch browsers that haven’t added the functionality. Currently there is no way to ensure those polyfills don’t fall subject or bit rot. We need an easy way for those communities to submit their polyfills to a place where they will be maintained and can be shared with the community. That’s the gist. There’s a lot to work out yet. 32 | JH: I am one of the people that maintains widely used JS polyfills. There really isn’t a community that needs collecting and managing. These tend to be “single-maintainer” projects. Unless the foundation is removing obstacles for the maintainers I’m skeptical about this as an idea. Secondly, JS spec implementations already link to polyfills, but makes an effort to not endorse or choose a preferred solution. 33 | BK: There is definitely some conversation to be had about “blessing” a polyfill. 34 | JH: The long term challenge isn’t around creating a polyfill while people are excited about a proposal. Long term maintenance (after browsers start shipping) is the real problem. 35 | JB: So this may not address the needs of polyfill maintainers unless long term maintenance is an added benefit. 36 | MS: Agree with JH. Long-term maintenance is super important. 37 | JH: I think a project that provides tests would be embraced. There isn’t an easy way to run 262 tests against anything that’s not a browser. That’s a problem I’d love to see solved that would definitely help. 38 | MS: So, to restate, being able to run tests on a bunch of different platforms would be helpful. 39 | JH: Many projects out there, whether they be polyfills, transpilers, etc could benefit from the ability to run conformance tests. 40 | JB: Maybe this is a good thing for us to talk about on a higher level. 41 | BK: One of the things we could do is provide a means for actually running tests. I support this. 42 | MB: My gut on this, based on our charter, is that this is something better suited for the collaboration network. I’m not saying this work isn’t important or worthy, but for the sake of our meetings we should be facilitating discussion. 43 | BK: I agree. We have heard from W3C and individual developers about this, so I brought this issue to see if we can facilitate some actual action. 44 | MB: I think the goos path forward would be to set up a Collaboration Space and see if some traction can be established there. 45 | 46 | Action Item: Jory and Brian to speak with Micheal Dawson about initializing a space for “Polyfillers” 47 | 48 | * Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102) 49 | 50 | FYI - prepping for 2021 Standards strategy session - what questions do we want to try to answer? 51 | * How do we communicate to the broader community - how do we make member projects more aware of what we’re doing? 52 | * Can we poll the projects - how would you like to be represented, how would you like to get involved, etc? 53 | * How do the projects imagine this working? 54 | 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Calendar**: https://calendar.openjsf.org 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | 64 | 65 | -------------------------------------------------------------------------------- /meeting-notes/2020.12.01_meeting-notes.md: -------------------------------------------------------------------------------- 1 | ## Meeting Notes - 2020.12.02 Standards Working Group Strategic brainstorming session 2 | 3 | **Present:** Mike Samuel, Richard Gibson, Brian Kardell, Jordan Harband, Jory Burson, Eemeli Aro, Michael Champion, Sendil Kumar, Robin Ginn 4 | 5 | This meeting was not recorded and lightly noted to make space for free discussion. 6 | 7 | ### Intro/Welcome 8 | - Reviewed questions/prompts and limited survey data: https://hackmd.io/bz9SKl87SYCIECAXi4zOGA 9 | 10 | ### Discussion: 11 | 12 | - Who are we? How do we define our scope? Who is interested? 13 | - We need to fit into the projects' own rhythm, meet them where they are. We could do some quarterly information sharing? 14 | - Who are our core constituencies? 15 | - Project Maintainers / Leaders 16 | - users of our open source projects 17 | - end users 18 | - Where are we on the scale of "consumption of" and "activism in" standards? e.g. do we ever imagine developing standards inside OpenJS Foundation? 19 | - An example from messageformat, that the latter could be needed/useful 20 | - Useful to identify and shore up the pieces that appear to "fall through the cracks" between existing working groups 21 | - **Takeaway:** we tend toward activism in participation and would be interested in providing a standardization path for our projects 22 | 23 | ### Strategic Direction(s) Ideas 24 | 1. OpenJS Foundation is a place to develop standards proposals / workstreams which are being missed by the bigger SDOs - "Fill the Cracks" 25 | 1. OpenJS Foundation is a place where the JS Community convenes to build & develop opinions for different proposals which are active in an SDO 26 | 1. OpenJS Foundation is a place for discovery of "standard stacks" e.g. we do analysis of our projects to present common pathways / approaches 27 | - "Does anyone else; or is it just me" type process or forum (we could expand on this from an educational perspective and post blogs "Are you experiencing X, you might be entitled to compensation etc") 28 | 1. OpenJS Foundation is a place where projects with standards-related goals (AMP, Node) receive support for their work, and where folks in those project groups cross-collaborate 29 | 1. OpenJS Foundation is a place where people can learn and begin to onboard into standards development 30 | - Including programs to support and mentor people to become (chairs, editors, note-takers, etc) 31 | - Hub for materials around presenting on certain standards proposals / issues - create(ing) ambassadors 32 | - Hub for getting involved with other educational works (e.g. Standards in 2 minutes) 33 | 1. OpenJS Foundation helps make standards bodies nicer places to do work (no jerks!) 34 | - "what can the openjs foundation do to make standards development "NICER" in 2021" 35 | 36 | ### Ideas for Action 37 | - Meet with Project Maintainers to discuss the Strategic Direction Ideas above and gather input on which direction(s) are most appealing 38 | - interview our projects to see which projects are experiencing shared problems/issues/challenges (research) - get a sense to develop a bigger picture similar to the TAG. RQ - is there something we can proactively assess/review 39 | - Recruit a rep from each project to participate in standards wg 40 | - Assess: 41 | - What is an example of something we can do? What is an example of something we can't do? 42 | - What do we have the best/most resources to do? 43 | - What should we do? 44 | - create an FAQ for questions / answers based on profile 45 | - "I am a community member with a proposal for {tc39}" 46 | - "I want to discover standards work" 47 | - "I think {module blocks} are a good idea, how do I build consensus for this across the OpenJS Foundation projects?" 48 | - "I want to standardize {X}" 49 | - "I want to follow developments in {some standards body} in order to determine if I would like to get involved" 50 | - "I want to stay abreast of things at {late stage} standards" 51 | -------------------------------------------------------------------------------- /meeting-notes/2021-06-15_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-06-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=jHto2zR-nN4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/145 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Jory Burson (@jorydotcom) 15 | * Joe Sepi (@joesepi) 16 | * Mike Samuel (@mikesamuel) 17 | * Brian Kardell (@bkardell) 18 | * Jordan Harband (@ljharb) 19 | * Mike Champion (@michaelchampion) 20 | * Tierney Cyren (@bnb) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | * marketing committee meeting at 3 pm 29 | * jory finally updated the notes, there are PRs for notes to review - please +1 30 | * Check out openjs world videos 31 | 32 | ### openjs-foundation/standards 33 | 34 | * Requesting 10 minutes to discuss API translation effort [#144](https://github.com/openjs-foundation/standards/issues/144) 35 | 36 | Mike Samuel shared a presentation on supporting many human languages in development environments. Goal is to help pre-English fluent developers navigate english-heavy apis. Issue of factorials in IDE development. Work happening on cross-language Language translation standards. LSP provides the language smarts & map translations. Additive to translation of documentation. Mike requests people who work as devs while pre-fluent to drive goal setting/prioritization; changes to LSP so a language server can connect identifiers to translations; Developer US expertise; A VSCode plugin; registry website; home org to provide structure. Would be good to have a “test project” from openjs but not necessary. OpenJS Collab Space could be helpful. Microsoft is driving a lot of work on LSP and it would be ideal to involve them. 37 | 38 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 39 | 40 | See: https://github.com/openjs-foundation/standards/blob/main/MEMBER_REPRESENTATION.md 41 | Do we have any strong feelings about how to handle this? No. Jory to open an PR to update the file. Will operationalize this in the future. 42 | 43 | * Discussion Request: Standards/Education & Onboarding Resources [#130](https://github.com/openjs-foundation/standards/issues/130) 44 | 45 | Jory has created the new repo and added new issues to the repo. 46 | Do we want to start with a couple of personas (per Mike Samuel’s idea last time)? How can we do a better job recognizing groups with different needs when it comes to the standards process? 47 | We could start taking notes / collecting examples / figuring out the gaps. Connected back to the AMA. Brian notes that devs have different impressions/frustrations/fears about engaging with SDOs. What comes up a lot is that groups are different even within a SDO. Is there a way to help explain that nuance (e.g. when should you expect a response, why are responses terse? etc). 48 | Mike's Persona Doc: https://docs.google.com/document/d/122hfS0jdglvCWtKn8TwqKo8Yja9duICgW-_a5aGgiKQ/edit 49 | 50 | ## Q&A, Other 51 | 52 | ## Upcoming Meetings 53 | 54 | * **Calendar**: 55 | 56 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 57 | -------------------------------------------------------------------------------- /meeting-notes/2021-08-10_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-08-10 2 | 3 | ## Links 4 | 5 | * **Recording**: session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Richard Gibson (@gibson042) 16 | * Hemanth HM (@hemanth) 17 | * Jory Burson (@jorydotcom) 18 | * Mike Samuel (@mikesamuel) 19 | 20 | ## Agenda 21 | 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | SXSW Panel picker for south by - vote 28 | OpenJS World 29 | W3C AC Chat 30 | Book club 31 | 32 | ### openjs-foundation/standards 33 | Minutes 34 | 35 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 36 | 37 | Document broadly 38 | Poke #standards channel peeps 39 | 40 | * Standards ed site 41 | https://github.com/openjs-foundation/standards-ed-site 42 | Unknotting 43 | Disentangling 44 | Acronyms 45 | wise information of standards and technology (WIST, WISTful) 46 | Wisteria - flowering (gardening) 47 | Wistopia 48 | List of people who can mentor 49 | 50 | 51 | AOB 52 | OpenJS World - Austin, June 7-8 - reach out to Robin or Jory if you’re interested in convening a standards meeting there. We’ve already reached out to TC39 co-chairs. 53 | 54 | 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Calendar**: 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | 64 | -------------------------------------------------------------------------------- /meeting-notes/2021.01.12_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-01-12 2 | 3 | ## Links 4 | * **Recording**: https://www.youtube.com/watch?v=3QRWhDJzkSo&ab_channel=OpenJSFoundation 5 | 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/120 7 | 8 | ## Present 9 | * Michael Dawson (@mhdawson) 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn (@rginn) 12 | * Jory Burson (@jorydotcom) 13 | * Brian Kardell (@bkardell) 14 | * Donovan Buck (@dtex) 15 | * Eemeli Aro (@eemeli) 16 | * Mike Samuel (@mikesamuel) 17 | * Richard Gibson (@gibson042) 18 | * Seth Newberry (guest presenter) 19 | * David Rudin (guest presenter) 20 | * Myles Borins (@MylesBorins) 21 | * Michael Champion (@michaelchampion) 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | * OpenJS World Announced - June 9, as well as the CFP 28 | * JSLandia, Individual Contributor program, launched 29 | * W3C TAG election results - congratulations to all candidates and the newly elected representative 30 | * Robin will work out bringing Lea Vereou to present to CPC from time to time 31 | 32 | ### openjs-foundation/standards 33 | 34 | * Presentation from David Rudin and Seth Newberry of the Joint Development Foundation. Discussion and Q&A ensued. 35 | 36 | ## Q&A, Other 37 | 38 | ## Upcoming Meetings 39 | 40 | * **Calendar**: https://calendar.openjsf.org -------------------------------------------------------------------------------- /meeting-notes/2021.01.26_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-01-26 2 | 3 | ## Links 4 | 5 | * **Recording**: [https://www.youtube.com/watch?v=-Dhy-QmjFrc&ab_channel=OpenJSFoundation](https://www.youtube.com/watch?v=-Dhy-QmjFrc&ab_channel=OpenJSFoundation) 6 | 7 | * **GitHub Issue**: [https://github.com/openjs-foundation/standards/issues/121](https://github.com/openjs-foundation/standards/issues/121) 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * Robin Ginn (@rginn) 13 | * Jory Burson (@jorydotcom) 14 | * Michael Champion (@michaelchampion) 15 | * Donovan Buck (@dtex) 16 | * Brian Kardell (@bkadell) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | 22 | * TC53 spec work is wrapping up and will head to a vote in June. Embedded JS’rs are invited to comment! 23 | * Standards content is encouraged for the OpenJS World event 24 | * First TAG meeting for Lea Verou this week 25 | * OpenJS World 26 | 27 | ### openjs-foundation/standards 28 | 29 | 2021 Strategic Planning and Goal Setting [#114]([https://github.com/openjs-foundation/standards/issues/114](https://github.com/openjs-foundation/standards/issues/114)) 30 | 31 | * Key action is to complete the feedback gathering from Project TSCs 32 | * Additional thought - trying to bootstrap a review process & documenting dependencies. Related to one of the strategic ideas around research. 33 | * We could invest in this; perhaps a grant or outreachy effort 34 | * This is related to the question of building our technical strategy 35 | * ACTION: write down the proposal / problem statement for the project 36 | * Recent survey results - do we want to pursue more responses? 37 | * We should sent out a couple of reminders and call it done by Mid-Feb. 38 | * Give some “for instances” - are you excited about X features, etc 39 | 40 | A home for reference-implementation polyfills [#106]([https://github.com/openjs-foundation/standards/issues/106](https://github.com/openjs-foundation/standards/issues/106)) 41 | 42 | * Status is relatively unchanged, not advanced in part due to understanding of long-term strategy & fitness with that plan 43 | * Have positive feedback on this; we shouldn’t close this issue. Perhaps add a backlog label? 44 | 45 | Discussion of JDF presentation from last week 46 | 47 | * Context is anti-trust; anti-trust as an obstacle to open collaboration. Standards work is intrinsically the kinds of things AT is concerned about but Standards making gets a pass because of historical process. The wrapper of a formal process may help them on down the line because the environment is changing. 48 | * We should assist the projects with structure and best practice as their open source codebases become “de facto” standards in a given tech stack 49 | * Robin: the perception of how standards processes work does not reflect the reality - we could do more to educate our projects on the agile 50 | * We could do a JDF blurb 51 | 52 | ## Q&A, Other 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Calendar**: https://calendar.openjsf.org 57 | -------------------------------------------------------------------------------- /meeting-notes/2021.02.23_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-02-23 2 | 3 | ## Links 4 | 5 | * **Recording**: [https://www.youtube.com/watch?v=cEF-lLQAwxs&ab_channel=OpenJSFoundation](https://www.youtube.com/watch?v=cEF-lLQAwxs&ab_channel=OpenJSFoundation) 6 | 7 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/124 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * Jory Burson (@jorydotcom) 13 | * Brian Warner (@brianwarner) 14 | * Robin Ginn (@rginn) 15 | * Eemeli Aro (@eemeli) 16 | * Jordan Harband (@ljharb) 17 | * Brian Kardell 18 | * Donovan Buck (@dtex) 19 | * Mike Samuel (@mikesamuel) 20 | * Richard Gibson (@gibson042) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | * TC39 Meetings early March 27 | 28 | * Lots of interesting proposals happening at TC39, add to agenda ends in 5 days 29 | 30 | * https://github.com/tc39/agendas/blob/master/2021/03.md 31 | 32 | * OpenJS World CFP closed last night 33 | 34 | * OpenJS World program committee welcomes talk proposal reviewers please :) 35 | 36 | ### openjs-foundation/standards 37 | 38 | New W3C AC Rep Switch 39 | 40 | * Brian has been AC rep for some time 41 | * We have been using a mailing list to share info with each other (with approval from Ralph) 42 | * Looking for +1 to agree to Jory to be rep 43 | * Action: Open Nominations for one week, 44 | * Action: Follow up with Ben About blog post 45 | 46 | * 2021 Strategic Planning and Goal Setting [#114]([https://github.com/openjs-foundation/standards/issues/114](https://github.com/openjs-foundation/standards/issues/114)) 47 | 48 | * Jory and Robin provided an update on feedback they've received from projects thus far. 49 | * Mike C., Brian & Jory will be meeting with W3C Dev Rel to continue related conversations started on the AC Forum. 50 | 51 | A home for reference-implementation polyfills [#106]([https://github.com/openjs-foundation/standards/issues/106](https://github.com/openjs-foundation/standards/issues/106)) 52 | 53 | * Agenda label removed & item tabled for the time being. 54 | 55 | ## Q&A, Other 56 | 57 | ## Upcoming Meetings 58 | 59 | * **Calendar**: https://calendar.openjsf.org -------------------------------------------------------------------------------- /meeting-notes/2021.03.23_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-03-23 2 | 3 | ## Links 4 | 5 | * **Recording**: [https://www.youtube.com/watch?v=ihI_TNhyktc](https://www.youtube.com/watch?v=ihI_TNhyktc) 6 | 7 | * **GitHub Issue**: Error Generating Issue 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * Jory Burson (@jorydotcom) 13 | * Robin Ginn (@rginn) 14 | * Jordan Harband (@ljharb) 15 | * Brian Kardell (@bkardell) 16 | * Richard Gibson (@gibson042) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | 22 | * Book Club meeting tomorrow - discussing "Working in Public" at 3 p.m. EST 23 | * OpenJS World event date moved to June 2; Speakers announced in a couple of weeks 24 | * Jory featured for standards work on GH Readme project 25 | 26 | ### openjs-foundation/standards 27 | 28 | Shared Principles Statement 29 | 30 | * We're considering authoring a shared statement with W3C on importance of relationship between Open Source and Standardisation activities - interest on the W3C side in this 31 | * Would be ideal to put it out and have other organizations sign on as well 32 | * Robin to start drafting statement, will work with our Board and the W3C team 33 | * Jory to file issue to track 34 | 35 | Nominations Sought: Designated W3C AC Representative [#128]([https://github.com/openjs-foundation/standards/issues/128](https://github.com/openjs-foundation/standards/issues/128)) 36 | 37 | * Jory was sole nominee; no vote needed 38 | * Next steps: Inform CPC at next meeting; work with Brian and Ralph to transfer AC role; draft blog post. 39 | * Issue is closed. 40 | 41 | 2021 Strategic Planning and Goal Setting [#114]([https://github.com/openjs-foundation/standards/issues/114](https://github.com/openjs-foundation/standards/issues/114)) 42 | 43 | * Robin and Jory reported on further input from Node's TSC 44 | * Growing preference across projects for strategies 2, 5, & 4 45 | * Group consensus is to move on for 2021, focusing on strategies 2 & 5 to start 46 | * Action: close #114 and open new issues 47 | 48 | Discussion Request: Standards/Education & Onboarding project ideas [#130]([https://github.com/openjs-foundation/standards/issues/130](https://github.com/openjs-foundation/standards/issues/130)) 49 | 50 | * Ad-hoc discussion of different approaches we could take for building resources to support onboarding into standards/careers 51 | * Helpful info? 52 | * Expectations style guidance for how long it takes, etc 53 | * Expectations for leadership roles - editing, chairing, joining an AC/GA 54 | * Multi-channel approach 55 | * Who do we cater to? 56 | * It should be generalized for a broad audience 57 | * Slack channel for q&a support? 58 | * Who can I go to for what - let people find names & faces 59 | * Centralized resource area(s) 60 | 61 | TC39 Meeting Updates 62 | 63 | * Jordan & Richard shared outcomes of the TC39 Meeting last week 64 | * Temporal moved to stage 3 65 | * brief discussion RE Moment and Polyfills 66 | * Error Cause also moved to stage 3 67 | * Other proposals moved to stage 2 68 | * Richard will be sending more preliminary emails ahead of meetings to project leads 69 | * Jory to reach out to Hemanth about sending his post-analysis to projects list 70 | 71 | 72 | ## Q&A, Other 73 | 74 | ## Upcoming Meetings 75 | 76 | * **Calendar**: https://calendar.openjsf.org -------------------------------------------------------------------------------- /meeting-notes/2021.04.13_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-04-06 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=5nriSV0Fg2U&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/135 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Jory Burson (@jorydotcom) 16 | * Eemeli Aro (@eemeli) 17 | * Joe Sepi (@joesepi) 18 | * Mike Samuel (@mikesamuel) 19 | * Richard Gibson (@gibson042) 20 | * Hemanth HM (@gnumanth) 21 | * Michael Champion (@michaelchampion) 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | * LF scholarships for training and certification are available. 28 | * Programming Committee meeting for OpenJS World - participants are welcome. Speakers will be announced soon. 29 | * New W3C Spec editors community group has been announced - lots of potential overlap in interest from this group. 30 | * New W3C Web Editor working group charter is out for review as well. 31 | * Welcome Hemanth! 32 | 33 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 34 | 35 | ### openjs-foundation/standards 36 | 37 | * Joint Statement on Open Source and Standards with W3C [#132](https://github.com/openjs-foundation/standards/issues/132) 38 | 39 | Looking to describe shared principles / pledge between open source and and open standards, how they work better together etc. 40 | Value of Open Source, Standardization activities; Building Inclusivity / Diverse Communities; How to read & understand, contribute back to the spec / Agility, feedback, iteration, planning; one often begets the other; Social impact; multi-stakeholders not just corp. Interests (invited experts example); No one right way; Neutrality / Transparency / Openness; things co-exist; Predictability; Knowing where to go to propose new things (e.g. for open source, it's largely GitHub/Gitlab, platforms for standards are lest clear). 41 | Robin will follow up with a draft for the group to review and comment on. 42 | 43 | * Discussion Request: Standards/Education & Onboarding Resources [#130](https://github.com/openjs-foundation/standards/issues/130) 44 | 45 | What are some of the tools and resources we can help make available for people who are interested in onboarding into "standards culture." 46 | What information would we like to gather, and how would we like to share this information? 47 | Hemanth shared some of the similarity and work happening in Standards in 2 Minutes. 48 | Jory and Hemanth discussed the need to make the materials consumable and in-context for developers. What is the view that helps make standardization more understandable? How can we help developers find the proper entry point? 49 | How much do we need to curate/contextualize the information to start? Jory advocates starting small, with something. Robin and others agree. 50 | Michael prompted the group to think about the users stories and who the target audience for the material is. 51 | Mike Samuel wondered if there could be an office hours type event to answer standards related questions and to channel materials. The group liked the idea of creating a feedback loop and gathering new questions. 52 | Robin wondered if we could find some university partnerships and outreach to field those questions. We could start with an AMA session? 53 | Hemanth suggested that perhaps there could be an opportunity within Google Summer of Code related to assisting content and resources around standards. The group liked this idea as well. 54 | Next steps would be to set up an office hour/AMA session for the Standards to gather. 55 | Also continue thinking about the use cases/user stories for the website. 56 | 57 | * Recurring meeting Conflict with CPC Working Group 58 | 59 | We can resolve this by having the meeting earlier or shifting a week. The group decided to shift the meeting one hour earlier. Jory will send a poll in slack to confirm this would work. 60 | 61 | ## Q&A, Other 62 | 63 | Joe suggested that the Standards WG could be a 'collab space'. Jory suggested that some of the Standards WG projects could be created as collab spaces and that we should continue thinking about it. 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Calendar**: 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | 71 | -------------------------------------------------------------------------------- /meeting-notes/2021.04.20_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-04-20 2 | 3 | ## Links 4 | * **Recording**: https://www.youtube.com/watch?v=n2jokQVWFNI 5 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/136 6 | 7 | ## Present 8 | 9 | * OpenJS Foundation Cross Project Council 10 | * OpenJS Foundation Project Maintainers 11 | * OpenJS Foundation Board of Directors 12 | 13 | Eemeli Aro (@eemeli) 14 | Robin Ginn (@rginn) 15 | Jory Burson (@jorydotcom) 16 | Mike Samuel (@mikesamuel) 17 | Sendil Kumar (@sendilkumarn) 18 | Joe Sepi (@joesepi) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | * Node v. 16 is live today! Congrats Node team. 27 | * Marketing committee meeting today following this meeting 28 | * Board meeting Friday, people are welcome to attend public session 29 | * Session to meet / discuss Spec Ed Community Group on April 28 30 | * Speakers announced and the schedule will go live this week for OpenJS world - register to get emails and event notifications. 31 | 32 | ### openjs-foundation/standards 33 | 34 | * Deal with Recurring CPC Working Session Conflict [#134](https://github.com/openjs-foundation/standards/issues/134) 35 | 36 | We resolved this issue by moving the meeting one hour earlier. 37 | Jory and Joe fixed the calendar invite to resolve. 38 | 39 | * Discussion Request: Standards/Education & Onboarding Resources [#130](https://github.com/openjs-foundation/standards/issues/130) 40 | We are compiling resources for a resource to help people gain skills they need or want to get involved in standardization activities. 41 | Question is how we want to present this information - e.g. build a standalone website. Simplest would be to have a GitHub repo with GH pages. We could give it a name and url. Do want to make this separately branded or more closely brand it with OpenJS? Eemeli encourages OpenJS to own the brand, but make it clear the information is not specific to OpenJS and is SDO neutral. 42 | Foundation’s preference would be to use a jekyll template; Joe would prefer the group to use a js tool, such as eleventy. 43 | Request is to continue adding recommendations to the issue and think of a name. 44 | 45 | * News from our Liaison groups 46 | * TC39 meeting happening today and tomorrow. 47 | * Next week: W3C Advisory Council Meeting 48 | * Spec Ed Community Group has spun up 49 | * W3C Advisory Board Elections 50 | * Unicode messageformat working group continues, meeting bi-weekly. Currently stuck on the shape of the data model for the spec. Going to start parallel implementations; Eemeli is championing one of the models and developing tooling/parsing. Work will likely take several months. 51 | * No update from the OSI. They are re-running board elections. 52 | 53 | The group closed the public meeting to discuss the following topics in a private session. 54 | 55 | * Place to discuss what we are doing without it being public (Eemeli) 56 | * Joint Statement on Open Source and Standards with W3C [#132](https://github.com/openjs-foundation/standards/issues/132) 57 | 58 | * Upcoming Standards group meetings 59 | 60 | 61 | 62 | ## Q&A, Other 63 | 64 | ## Upcoming Meetings 65 | 66 | * **Calendar**: 67 | 68 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 69 | -------------------------------------------------------------------------------- /meeting-notes/2021.05.18_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-05-18 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/UAxrkAYTxH8 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/139 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn (@rginn) 12 | * Jory Burson (@jorydotcom) 13 | * Ben Michel (@obensource) 14 | * Michael Champion (@michaelchampion) 15 | * Tierney Cyren (@bnb) 16 | * Jordan Harband (@ljharb) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | 22 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 23 | 24 | * Marketing Committee meeting later today for those interested. 25 | * Reminder that OpenJS World is in a couple of weeks - register! 26 | * Let us know if you want to help facilitate Speaker Q&A 27 | * Thank you to the programming committee - that committee meets Thursday 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Ad Hoc Meeting - Spec-Ed CG discussion with Marcos Caceres - April 28 [#137](https://github.com/openjs-foundation/standards/issues/137) 32 | 33 | Jory reported on this during the last meeting. The CG is a subset of people interested in Spec Production. They are looking to provide mentorship and tutorials for people interested in becoming editors and there are definite overlaps of interest with our educational resource planned. It looks like a great opportunity for joint participation. Members are encouraged to join the CG. Jory removed the agenda label and closed the issue. 34 | 35 | * Discussion Request: Standards/Education & Onboarding Resources [#130](https://github.com/openjs-foundation/standards/issues/130) 36 | 37 | We have collected a lot of resources so far. We plan to create a separate repo for the resource and collect 2 lists of information, one being a list of resources and the second being a list of questions we hope to answer for people arriving at the site. Jory has not completed this action. 38 | Robin shared that an LF web designer is happy to help but needs content. Jory asked, what are some of the questions we’d like to help answer? Discussion ensued and some of the questions raised were: 39 | 1. How do I learn to read a spec 40 | 1. Where and how do I learn a process for ____ (TC39, W3C, ect) 41 | 1. How do I understand the IPR policy of a given SDO? 42 | 43 | Ben pointed out that a lot of this material, which is primarily in written format, would make good video content as well, given that many people prefer learning via video. Robin suggested it could be a series of videos. 44 | 45 | Hemanth asked if it would be nice to have something of an online lab or tutorial to demonstrate how a spec advances (like a ‘hello world’ playground app). Jordan thought this was a good idea. Jordan also wanted to be sure that the application also helped people understand the constraints, to limit the risk that some people will over-enthusiastically rush into a proposal and be disappointed. Jory suggested that such an app can be part of the learning process, where step 1 is learning to read a spec, step 2 is understanding process, and step 3 is learning the “what/why/why not”. Hemanth suggested that we could create a framework for helping people understand their proposals, specifically “guiding questions that you should ask.” 46 | 47 | Robin suggested that we could start drafting content based on the initial questions, then share it with the group for feedback. 48 | 49 | The group noted that the project does not have a name, and spent a few minutes contemplating a name. Thematic areas were word puns, art, cookbook/recipe books, libraries, commons, sparknotes/cliffnotes, standards camp, hitchhiker’s guide. 50 | 51 | * Joint Statement on Open Source and Standards with W3C [#132](https://github.com/openjs-foundation/standards/issues/132) 52 | 53 | The recording was stopped for discussion of this issue, which included some private feedback from some of the organizations we were hoping to complete the statement with. 54 | 55 | ## Q&A, Other 56 | 57 | ## Upcoming Meetings 58 | 59 | * **Calendar**: 60 | 61 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 62 | -------------------------------------------------------------------------------- /meeting-notes/2021.06.01_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-06-01 2 | 3 | ## Links 4 | 5 | * **Recording**: Recording failed this week 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/140 7 | 8 | ## Present 9 | Jory Burson (@jorydotcom) 10 | Ben Michel (@obensource) 11 | Hemanth HM (@hemanth) 12 | Mike Samuel (@mikesamuel) 13 | Jordan Harband (@ljharb) 14 | Mike Champion (@michaelchampion) 15 | Richard Gibson (@gibson042) 16 | 17 | * OpenJS Foundation Cross Project Council 18 | * OpenJS Foundation Project Maintainers 19 | * OpenJS Foundation Board of Directors 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | * reminder - OpenJS World is tomorrow 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Joint Statement on Open Source and Standards with W3C [#132](https://github.com/openjs-foundation/standards/issues/132) 32 | 33 | Jory and Robin updated the group - most of the organizations we approached were unable to get sign-off on the statement in time for the event. W3C and TC39 provided 30 second cameo statements during the opening Keynote. The statements reinforce standards-wg focus areas for this year. 34 | We will continue to consider the statement, and perhaps evolve it in the future. 35 | A discussion ensued about some of the feedback we received on the statement. Mike Samuel suggested that we could evolve the statement to accommodate the different perspectives people and organizations will bring to the statement. Such an approach could allow us to think more along the lines of personas and “lego pieces” that would help readers identify themselves and their use cases within the statement, and could potentially correlate to the personas we create for the learning site. The group was excited about this path and will look to develop that direction and idea further. 36 | 37 | * Discussion Request: Standards/Education & Onboarding Resources [#130](https://github.com/openjs-foundation/standards/issues/130) 38 | 39 | Jory reported that she didn’t have the bandwidth to create the new site repo and move the issue, but hopes to have the time after the conference. 40 | In the meantime the community is encouraged to continue sharing their favorite resources. 41 | 42 | ## Q&A, Other 43 | 44 | Jordan and Richard shared a few highlights from the recent TC39 meeting. In addition to the advancement of Top Level Await, they highlighted that Tierney’s proposal for `hasOwnProperty()` reached stage 3. Congratulations, @bnb! 45 | 46 | Ben Michel shared that he is excited to return to the group’s work after a brief absence. 47 | 48 | The next meeting is 15 June. 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | -------------------------------------------------------------------------------- /meeting-notes/2021.06.29_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-06-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=YZ9k3HGjZ4o 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/149 7 | 8 | ## Present 9 | 10 | Robin Ginn, @rginn 11 | Ben Michel, @obensource 12 | Donovan Buck, @dtex 13 | Sonal Bhoraniya, @sonalpbhoraniya 14 | Michael Champion, @michaelchampion 15 | Jordan Harband, @ljharb 16 | Hemanth HM, gnumanth 17 | Richard Gibson, @gibson042 18 | 19 | * OpenJS Foundation Cross Project Council 20 | * OpenJS Foundation Project Maintainers 21 | * OpenJS Foundation Board of Directors 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Requesting 10 minutes to discuss API translation effort [#144](https://github.com/openjs-foundation/standards/issues/144) 32 | Discussion held in the last Standards WG meeting. Follow ups will be noted in the issue. 33 | 34 | * Request to attend TC39 as OpenJS delegate [#143](https://github.com/openjs-foundation/standards/issues/143) 35 | Private session discussion. 36 | 37 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 38 | Defining terms a work in progress. People often represent more than one organization - “wear different hats.” 39 | Start by listing all OpenJS participants who participate in standards. See PR #148 - this is meant to be all standards-adjacent people. 40 | How do we index - by person or organization? Consensus is both, although list by person and include their affiliation -- people often continue their standards participant roles even when switching companies. 41 | To determine status on representation, file an issue to be approved to be affiliated with OpenJS. 42 | 43 | ## Q&A, Other 44 | 45 | ## Upcoming Meetings 46 | 47 | * **Calendar**: 48 | 49 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 50 | -------------------------------------------------------------------------------- /meeting-notes/2021.07.13_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-07-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=nJm5LNmGBOA 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/150 7 | 8 | ## Present 9 | 10 | * Jordan Harband (@ljharb) 11 | * Eemeli Aro (@eemeli) 12 | * Robin Ginn (@rginn) 13 | * Jory Burson (@jorydotcom) 14 | * Richard Gibson (@gibson042) 15 | * Hemanth (@gnumanth) 16 | * Brian (@bkardell) 17 | * Sonal (@bhoraniya) 18 | * Michael Champion (@michaelchampion) 19 | * Joe Sepi (@joesepi) 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | OpenJS World Programming Committee Meeting this Thursday - all are welcome 28 | Check out the public board meeting video for info on the event’s impact 29 | 30 | ### openjs-foundation/standards 31 | 32 | * Requesting 10 minutes to discuss API translation effort [#144](https://github.com/openjs-foundation/standards/issues/144) 33 | 34 | Group is chatting this Friday at 1 EST to follow up on this discussion. 35 | 36 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 37 | 38 | See related PR - #148. List of all the people in the foundation - what is the scope? 39 | 40 | ## Q&A, Other 41 | 42 | ## Upcoming Meetings 43 | 44 | * **Calendar**: 45 | 46 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 47 | -------------------------------------------------------------------------------- /meeting-notes/2021.08.24_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-08-24 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | Jordan Harband 15 | Sonal Bhoraniya 16 | Richard Gibson 17 | Hemanth HM 18 | Jory Burson 19 | Mike Samuel 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | TC39 meeting next week! 26 | 27 | 28 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 29 | 30 | ### openjs-foundation/standards 31 | 32 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 33 | 34 | 35 | https://docs.google.com/document/d/1vnYJFnVB3wHsIRWNiLnes48PgDgkuaxCqdlJFg-RdO4/edit 36 | 37 | TPAC - next time 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | 47 | -------------------------------------------------------------------------------- /meeting-notes/2021.09.07_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-09-07 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Jordan Harband 15 | * Michael Champion 16 | * Richard Gibson 17 | * Hemanth HM 18 | * Robin Ginn 19 | * Jory Burson 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | * TC39 - https://dev.to/hemanth/updates-from-the-85th-meeting-of-tc39-2kep 28 | * Book Club today @ 3 p.m. ET 29 | * Web Directions Conference happenings - PWA only conf happening 30 | * AC Office Hours 31 | * W3C TPAC - October 32 | 33 | ### openjs-foundation/standards 34 | 35 | * Creative Services Brief: https://docs.google.com/document/d/1vnYJFnVB3wHsIRWNiLnes48PgDgkuaxCqdlJFg-RdO4/edit 36 | 37 | * https://documentation.divio.com/#about-the-system 38 | * https://docusaurus.io/ 39 | 40 | 41 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 42 | 43 | 44 | 45 | ## Q&A, Other 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | 53 | -------------------------------------------------------------------------------- /meeting-notes/2021.09.21_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-09-21 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | Robin 15 | Hemanth 16 | Eemeli 17 | Jordan 18 | Jory 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | Marketing COmmittee Meeting today 25 | Speaking next week at OSSNA Seattle 26 | The Next Web Conf 27 | Patches 28 | Web Directions 29 | EasyCLA Working Session 30 | 31 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 32 | 33 | ### openjs-foundation/standards 34 | 35 | * W3C TAG Nominations to Open Soon [#157](https://github.com/openjs-foundation/standards/issues/157) 36 | 37 | * Support Liaison Travel for Unicode Conference [#156](https://github.com/openjs-foundation/standards/issues/156) 38 | * No concerns - proceed 39 | * Check in with Ben 40 | * Communicate Social / RE Eemeli Aro 41 | 42 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 43 | 44 | 45 | 46 | ## Q&A, Other 47 | 48 | ## Upcoming Meetings 49 | 50 | * **Calendar**: 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | 54 | -------------------------------------------------------------------------------- /meeting-notes/2021.10.05_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-10-05 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Donovan Buck (@dtex) 15 | * Jordan Harband (@ljharb) 16 | * Eemeli Aro (@eemeli) 17 | * Richard Gibson (@gibson42) 18 | * Sonal Bhoraniya () 19 | * Joe Sepi (@joesepi) 20 | * Robin Ginn (@rginn) 21 | * Jory Burson (@jorydotcom) 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | * Node LiFT Scholarship open through Oct. 15! 30 | * Programming Committee Meeting - Thursday! 31 | * OpenJS CPC 32 | * SOS Announcements (https://sos.dev/) 33 | * OpenSSF Projects Looking to support JavaScript projects 34 | * TC39 Meeting Oct. 25-28 35 | * TC39 TPAC 36 | 37 | ### openjs-foundation/standards 38 | 39 | * W3C TAG Nominations to Open Soon [#157](https://github.com/openjs-foundation/standards/issues/157) 40 | 41 | * Support Liaison Travel for Unicode Conference [#156](https://github.com/openjs-foundation/standards/issues/156) 42 | 43 | * 44 | 45 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 46 | 47 | 48 | 49 | ## Q&A, Other 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | 57 | -------------------------------------------------------------------------------- /meeting-notes/2021.10.19_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-10-19 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Eemeli Aro (@eemeliaro) 16 | * Richard Gibson (@gibson42) 17 | * Jory Burson (@jorydotcom) 18 | * Hemanth HM (@hemanthHM) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | * Eemeli - spoke at the unicode conf from messageformat WG - went well! Spoke along with co-presenters - talk was recorded but not sure when / how available. Also had a wg meeting there and was nice to meet everyone in person. Plan for series of design documents to address challenging spec issues. Ratified at monthly WG meeting yesterday, and hoping to see progress go further - spec in some number of months or low number of years. Eemeli to share more info on how messageformat would advance through unicode tech spec. Eemeli to work with 27 | * Lots of shipping happening - Node 17; nvm - adds support for windows; 28 | * Monday TC39 meeting - BST 29 | * TPAC Developer days - this week 30 | * NearForm Node Conf 31 | * Programming Committee meeting this week (Thursday) 32 | * Marketing Committee call later today - noon pacific 33 | 34 | ### openjs-foundation/standards 35 | 36 | * W3C TAG Nominations to Open Soon [#157](https://github.com/openjs-foundation/standards/issues/157) 37 | Closed 38 | 39 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 40 | Jory to do a PR for next Client 41 | 42 | * Spec Ed site 43 | Design resource may be needed to unblock 44 | Jory doesn’t think they have started 45 | 46 | * Exciting TC39 Agenda next week 47 | Extending Null 48 | Stage 4 proposals 49 | Temporal changes 50 | 51 | ## Q&A, Other 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Calendar**: 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | 59 | -------------------------------------------------------------------------------- /meeting-notes/2021.11.02_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-11-02 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/162 7 | 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * Richard Gibson (@gibson42) 13 | * Jonathan Lipps 14 | * Jory Burson (@jorydotcom) 15 | * Eemeli Aro 16 | * Robin Ginn (@rginn) 17 | * Brian Kardell 18 | * Mike Samuel 19 | * Christian Bromann 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | * New Node.js Releases 25 | * Joe Speaking at JS Poland event on Open Governance / OpenJS 26 | * TPAC last week, recordings now available online 27 | * Brian spoke recently about has() which is now in CSS from jQuery 28 | * Robin, Jordan, Todd at the Member Summit this week 29 | 30 | 31 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 32 | 33 | ### openjs-foundation/standards 34 | 35 | * Discussing a standard for cross-platform UI-based app automation [#161](https://github.com/openjs-foundation/standards/issues/161) 36 | 37 | * Jonathan shared a presentation on ideas for a standard, “universal” UI automation framework 38 | 39 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 40 | 41 | 42 | 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | 52 | -------------------------------------------------------------------------------- /meeting-notes/2021.11.16_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-11-16 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Eemeli Aro (@eemeli) 16 | * Jordan Harband (@ljharb) 17 | * Joe Sepi (@joesepi) 18 | * Hemanth 19 | * Mike Samuel 20 | 21 | 22 | 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | * Marketing Committee Meeting - noon pacific 29 | * CPC Working Session - after this call 30 | * Programming Committee for event - Thursday! 31 | 32 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 33 | 34 | ### openjs-foundation/standards 35 | 36 | * Discussing a standard for cross-platform UI-based app automation [#161](https://github.com/openjs-foundation/standards/issues/161) 37 | 38 | * Document Delegates & Delegate Approval Process [#142](https://github.com/openjs-foundation/standards/issues/142) 39 | 40 | * 41 | 42 | 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | 52 | -------------------------------------------------------------------------------- /meeting-notes/2021.12.14_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2021-12-14 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | * Robin Ginn (@rginn) 16 | * Eemeli Aro (@eemeli) 17 | * Jory Burson (@jorydotcom) 18 | * Joe Sepi (@joesepi) 19 | * Michael Champion 20 | 21 | ## Agenda 22 | 23 | W3C TAG Election 24 | Nominations to be recorded per slack discussion 25 | 26 | Creative Services Meeting / List Website 27 | Discussion about adding copyright guidance for OpenJS projects who are defining specifications outside an organization; e.g. how to interpret/use “Community Spec” license. 28 | CS wants to meet with us to review designs/requirements 29 | 30 | Meetings resuming in January 31 | Robin to run meetings in Jory’s absence 32 | Jory encourages group to take up the topic of coordination / feedback between projects, their efforts and the standards organizations 33 | 34 | 35 | 36 | ### Announcements 37 | 38 | * OpenJS World Programming Committee Meeting - Thursday 39 | * Today is Jory’s last meeting until she returns from Maternity Leave 40 | * OpenJS public meetings canceled for remaining 2 weeks of 2021 41 | 42 | 43 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 44 | 45 | 46 | 47 | ## Q&A, Other 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Calendar**: 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | -------------------------------------------------------------------------------- /meeting-notes/2022.01.25_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-01-25 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | Robin Ginn 11 | Michael Champion 12 | Eemeli Aro 13 | Mike Samuel 14 | 15 | * OpenJS Foundation Cross Project Council 16 | * OpenJS Foundation Project Maintainers 17 | * OpenJS Foundation Board of Directors 18 | 19 | 20 | ## Agenda 21 | 22 | Update on LIST website (Learning in Standards & Technology). Graphic designer needed to complete the work. Robin recommended and consensus reached that we start the site as a web page on openjsf.org. 23 | 24 | Standards WG at OpenJS World 2022: Standards WG at OpenJS World 2022 · Issue #168 · openjs-foundation/standards (github.com) 25 | Discussion followed by Michael Champion’s points in issue. 26 | Use foundation as voice of the user. 27 | Explore ways to create a forum for filling in the cracks and expanding the social network of those providing feedback to standards orgs. 28 | Robin and Mike Samuel identified potential spec editors to ask for support. 29 | Recruit and train new editors. 30 | Explore training or breakout session at OpenJS World or during this event’s Collab Summit. 31 | Recognition. Explore awards to be presented at OpenJS World (similar to CNCF “Chop and carry wood awards) 32 | 33 | 34 | ### Announcements 35 | 36 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 37 | 38 | 39 | 40 | ## Q&A, Other 41 | 42 | ## Upcoming Meetings 43 | 44 | * **Calendar**: 45 | 46 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 47 | 48 | -------------------------------------------------------------------------------- /meeting-notes/2022.02.08_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-02-08 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * Robin Ginn 11 | * Donovan Buck 12 | * Jordan Harband 13 | * Michael Champion 14 | 15 | 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 22 | 23 | ### openjs-foundation/standards 24 | 25 | * Standards WG at OpenJS World 2022 [#168](https://github.com/openjs-foundation/standards/issues/168) 26 | Discussion around two of the three summarized points from the last meeting: 27 | Explore ways to recruit and train new editors. 28 | Recruiting is best done through current contributors. 29 | Education effort recommended through breakout session at OpenJS World. Invite Hemanth HM to share his ReadSpecWith.us content in a one-hour training session, with Jordan on hand to support. 30 | Explore recognition and awards program (potential addition to CPC Community Fund thank you program in development) 31 | For standards heroes, leverage and amplify the awards already given by Ecma and other standards orgs. 32 | As projects to identify their unsung heroes and work through the CPC on awards program presented at OpenJS World. 33 | 34 | 35 | ## Q&A, Other 36 | 37 | ## Upcoming Meetings 38 | 39 | * **Calendar**: 40 | 41 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 42 | 43 | -------------------------------------------------------------------------------- /meeting-notes/2022.02.22_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-02-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=cc6ifK0pNxw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/171 7 | 8 | ## Present 9 | 10 | * Robin Ginn 11 | * Joe Sepi (@joesepi) 12 | * Jordan Harband 13 | * Michael Champion 14 | * Richard Gibson 15 | 16 | 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | 22 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 23 | 24 | ### openjs-foundation/standards 25 | 26 | * Standards WG at OpenJS World 2022 [#168](https://github.com/openjs-foundation/standards/issues/168) 27 | 28 | Recognition / Awards: 29 | Reframe achievements. Measure impact. Demonstrate to employer and industry accomplishments. OpenJS marketing / OpenJS World recognition. < 30 | 31 | TC39: Readme, bugs, implementations (transpilers, polyfills, early browser movement), respectful pushback, adding tests, spec editors 32 | 33 | W3C: like above. + organizing user groups 34 | 35 | Working in Public: a book describes how maintainers are often not rewarded. 36 | 37 | Blog posts, conference talks, writing/improving MDN articles, general “evangelism” things (+1) 38 | 39 | FOSS/node contributions? 40 | Process: identify people comprised of many positive actions in addition to creating specific buckets. 41 | 42 | First time contributors’ awards? 43 | Before feature: design phase 44 | Implementation phase 45 | After feature: evangelize, educate / onboard 46 | Organize 47 | 48 | Design, Build, Teach? 49 | 50 | Execution: crowdsource / ask champions for proposals. Look at commits in project repos. 51 | 52 | Branding brainstorm: 53 | No stone unturned. 54 | JavaScriptLandia + (play on words) 55 | Don’t imply that you have to “do something” like code to be rewarded. 56 | Like GitHub Star 57 | Hero but not glorified 58 | Connectors 59 | Fruit behind the leaf 60 | Caterpillar 61 | Weeders 62 | Cultivators 63 | Ants 64 | Fungus 65 | Caretaker 66 | Green or groundskeeper 67 | 68 | 69 | 70 | ## Q&A, Other 71 | 72 | ## Upcoming Meetings 73 | 74 | * **Calendar**: 75 | 76 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 77 | 78 | -------------------------------------------------------------------------------- /meeting-notes/2022.04.05_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-04-05 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | 16 | ## Agenda 17 | 18 | ### Announcements 19 | 20 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 21 | 22 | ### openjs-foundation/standards 23 | 24 | * Standards WG at OpenJS World 2022 [#168](https://github.com/openjs-foundation/standards/issues/168) 25 | 26 | Theater space? 27 | 28 | Awards nominations now open: https://forms.gle/Na5DH3DAyCKj41b66 29 | 30 | 31 | 32 | ## Q&A, Other 33 | 34 | ## Upcoming Meetings 35 | 36 | * **Calendar**: 37 | 38 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 39 | 40 | -------------------------------------------------------------------------------- /meeting-notes/2022.05.17_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-05-17 2 | 3 | ## Links 4 | 5 | * **Recording**: Session was not recorded 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | 16 | ## Agenda 17 | 18 | ### Announcements 19 | 20 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 21 | 22 | ### openjs-foundation/standards 23 | 24 | Standards WG at OpenJS World 2022 #168 25 | Panel @ Community Space 26 | JSLandia Awards - discussion of nominees for Standards award 27 | W3C AB Election 28 | 29 | 30 | 31 | 32 | ## Q&A, Other 33 | 34 | ## Upcoming Meetings 35 | 36 | * **Calendar**: 37 | 38 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 39 | 40 | -------------------------------------------------------------------------------- /meeting-notes/2022.07.12_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-07-12 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/183 7 | 8 | ## Present 9 | 10 | Robin Ginn 11 | Jordan Harband 12 | Christian Bromann 13 | Donovan Buck 14 | Richard 15 | 16 | * OpenJS Foundation Cross Project Council 17 | * OpenJS Foundation Project Maintainers 18 | * OpenJS Foundation Board of Directors 19 | 20 | 21 | 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | ### openjs-foundation/standards 30 | 31 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 32 | 33 | Expectations for participation. 34 | Participation in Standards WG: Prep before and debrief after. (Regular WG attendance is encouraged but not required) 35 | Person is already a credible/established participant in relevant standards. 36 | 37 | Possible reasons for declining: 38 | Another more appropriate funding source has not been explored 39 | Reputational issues we do not want associated with the foundation 40 | The standards arena in question is not sufficiently relevant to OpenJS 41 | The requester is not already a credible/established participant in the relevant standards arena (eg, no past record of participation) 42 | 43 | Requesting funds does not imply that the requester is representing OpenJS, and as such, there are no inherent constraints applied to their participation solely based on usage of funds. 44 | 45 | Add expense limit guidelines (ie lowest travel costs). 46 | Consider and clarify why remote participation is not an option. 47 | It is strongly recommended that you submit your request far enough in advance to get approval before making relevant expenditures. Review of requests will take at least 72 hours and may take considerably longer. 48 | 49 | Approvers: At least one approver from each: Standards WG and CPC. 50 | 51 | Terms: 52 | 53 | * Standards WG at OpenJS World 2022 [#168](https://github.com/openjs-foundation/standards/issues/168) 54 | 55 | 56 | 57 | ## Q&A, Other 58 | 59 | ## Upcoming Meetings 60 | 61 | * **Calendar**: 62 | 63 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 64 | 65 | -------------------------------------------------------------------------------- /meeting-notes/2022.11.01_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-11-01 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtube.com/live/_qzWR5Wow4M?feature=share 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn 12 | * Lea Verou 13 | * Michael Champion 14 | * Luke Schantz 15 | *Jordan Harband 16 | 17 | 18 | ## Agenda 19 | 20 | 21 | ### Announcements 22 | 23 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 24 | 25 | ### openjs-foundation/standards 26 | 27 | * 2022-2023 Public Calendar for web standards group meetings [#191](https://github.com/openjs-foundation/standards/issues/191) 28 | * discussed briefly but no comments/concerns 29 | 30 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 31 | 32 | Michael Champion shared link to document - Concise Guide to Improving Web Standards 33 | https://docs.google.com/document/d/1yDxUCnvZC23HfZXOz7OAbyWHZqqqNXBZHk0y3GBeIds/edit#heading=h.pzjcr6mk132n 34 | Feedback and help on documents. Wordsmithing and making things more concise. 35 | Robin: Set a goal to have something published? And weigh in before publishing? 36 | Lea: Do we just start editing? (google docs is good for initial editing IMO) 37 | Michael: Google docs has history or could move to github. Whatever works for you as long as it is in writing. 38 | Robin: Deadline of 2 weeks …. 4 weeks. Lea: Conscious of thanksgiving timing. 39 | Lea: Not obvious to people which speck contains each feature. Look up on MDN. Seems to be the best source. Has a bookmark to take to spec. 40 | Jordan: Series of questions to help determine which spec to point to. 41 | Luke: In plant/biology identification there is the concept of “dichotomous key” for identification. 42 | Jordan: Reading the Spec - Hemanth HM, PayPal & Jordan Harband, Coinbase https://www.youtube.com/watch?v=uPFOdaGe9Zw 43 | 44 | 45 | 46 | 47 | * Submit Foundation Ballot for W3C Board Election [#189](https://github.com/openjs-foundation/standards/issues/189) 48 | 49 | Issue closed. 50 | 51 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 52 | 53 | Jordan: Consider the $ will change between request and approval times. 54 | Lea: Range of prices. 55 | Robin: Linking standards and eligibility criteria. Active participation in the group etc. 56 | This was fleshed out but standards section is blank: 57 | https://github.com/openjs-foundation/community-fund/blob/main/programs/travel-fund.md 58 | Each group makes a decision on who they want to support. 59 | Robin: case by case basis. May need to be different criteria for some with yearly approval of x number of meetings. Up to a certain point because we have a finite budget. 60 | Eligibility criteria and DEI scholarships. 61 | Recommendation for eligibility 62 | Person be representative for XYZ meeting N number of meetings this year. 63 | Lea: look into how it is listed as an innovative and if it complicates work or student visa. 64 | If it shows up as income. 65 | Jordan: reimbursement is not income. Filing a report does not necessarily make it income. Important concern that should be independent of the platform we use. 66 | Robin: Work on language from a process perspective and make suggestions. 67 | 68 | 69 | ## Q&A, Other 70 | 71 | Lea: Tag nominations end next week. Do I need to open an issue? Lea is up for reelection as her term is ending. It is important work. If she can find support she can run again. 72 | Robin: Looking for the issue. Ask Brian C. 73 | https://github.com/openjs-foundation/standards/issues/117 74 | Put the agenda tag on it. Deadline is Nov 8th, 2022. 75 | Flag it in slack too in case people don’t see it. 76 | Process 77 | Link to previous issue. Create issue 78 | Community Member posts in slack. Jordan will post it. 79 | 80 | ## Upcoming Meetings 81 | 82 | * **Calendar**: 83 | 84 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 85 | 86 | -------------------------------------------------------------------------------- /meeting-notes/2022.11.15_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-11-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=PP5navr6FB4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/200 7 | 8 | ## Present 9 | 10 | * Luke Schantz 11 | * Richard Gibson 12 | * Joe Sepi 13 | * Emeli Aro 14 | * Robin Ginn 15 | * Jory Burson 16 | * Lea Verou 17 | * Mike Champion 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | CSL Webinar Announcement 24 | 25 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 26 | 27 | ### openjs-foundation/standards 28 | 29 | * 2022-2023 Public Calendar for web standards group meetings [#191](https://github.com/openjs-foundation/standards/issues/191) 30 | 31 | CSS WG Meetings - Wednesdays at Noon EST 32 | No dates yet for TC39 33 | OpenJS World co-locating May 8 OSSNA Vancouver 34 | Add link to the Readme on standards repo 35 | Add to website & collaboration page 36 | 37 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 38 | 39 | Need some contributions - real world examples. Talk to Dom / Dan / Mike T / Marcos?. Group to continue brainstorming - e.g. bugs from CSS WG. Lea to consider recent examples. Example from JSON Schema? Multiple kinds of examples could be helpful. 40 | Action: Lea to brainstorm CSS example 41 | Action: Jory / Robin &/or Luke Interview Ben Hutton 42 | 43 | 44 | 45 | 46 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 47 | 48 | Use of community fund for SMEs - approval is for a year of travel. SME to provide an estimate for travel expenses for the year. 49 | Review reps in December for the upcoming year? 50 | Document this on GitHub 51 | 52 | * https://github.com/openjs-foundation/standards/issues/197 53 | * is there anyone we would like to run from the OpenJS community? 54 | * What will the AB focus on now that the management duties have been upleveled to the Board? 55 | * Mike would be interested in the interim, but concerned about time commitments 56 | 57 | 58 | 59 | 60 | ## Q&A, Other 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Calendar**: 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 67 | 68 | -------------------------------------------------------------------------------- /meeting-notes/2022.11.29_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2022-11-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtube.com/live/JBNPYMradaY?feature=share 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | Jory Burson 11 | Robin Ginn 12 | Joe Sepi 13 | Jordan Harband 14 | Michael Champion 15 | Luke Schantz 16 | 17 | * OpenJS Foundation Cross Project Council 18 | * OpenJS Foundation Project Maintainers 19 | * OpenJS Foundation Board of Directors 20 | 21 | 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | TC39 in Spain 28 | 29 | FINOS in NYC Dec 8th 30 | 31 | Antitrust training on Dec. 13 32 | 33 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 34 | 35 | ### openjs-foundation/standards 36 | 37 | * 2022-2023 Public Calendar for web standards group meetings [#191](https://github.com/openjs-foundation/standards/issues/191) 38 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 39 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 40 | 41 | * PRs 42 | * Calendar 43 | 2023 events 44 | Should the WG meet in person in 2023 45 | Web App Sec Workship W3C 46 | Antitrust training 47 | Document! 48 | Dec 27 meeting canceled 49 | 50 | 51 | ## Q&A, Other 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Calendar**: 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | 59 | -------------------------------------------------------------------------------- /meeting-notes/2023.02.07_meeting_notes.md: -------------------------------------------------------------------------------- 1 | TC39 was a couple of weeks ago 2 | Import assertions went down to stage 2 3 | Next Plenary 4 | 5 | W3C 6 | Tag F2F in Japan in April 7 | 8 | AC Meeting in France at the same time as OpenJS World 9 | 10 | 11 | Participation in TC shouldn’t change? 12 | Reporting 13 | Participation is fluid 14 | 15 | 16 | # OpenJS Foundation Standards Working Group Meeting 2023-02-07 17 | 18 | ## Links 19 | 20 | * **Recording**: https://youtube.com/live/vHM65WQQQ4I?feature=share 21 | * **GitHub Issue**: $GITHUB_ISSUE$ 22 | 23 | ## Present 24 | 25 | * OpenJS Foundation Cross Project Council 26 | * OpenJS Foundation Project Maintainers 27 | * OpenJS Foundation Board of Directors 28 | 29 | Luke Schantz 30 | Robin Ginn 31 | Joe Sepi 32 | Jory Burson 33 | Mike Champion 34 | Richard Gibson 35 | 36 | ## Agenda 37 | 38 | ### Announcements 39 | 40 | Google Season of Docs / Season of Code 41 | W3C AB requesting input on sessions to cover at AC meeting 42 | Web Fonts WG - charter update for W3C 43 | W3C AB Election results: 44 | Qing An (Alibaba Group) 45 | Tantek Çelik (Mozilla Foundation) 46 | Elika J Etemad (W3C Invited Expert) 47 | Charles Nevile (ConsenSys) 48 | OpenJS World Ticket Sales - May 9 is collab summit. 10-12 is the conference. This is in May! Vancouver. 49 | 50 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 51 | 52 | ### openjs-foundation/standards 53 | 54 | Report or update from January/Feb TC39? 55 | Richard gave a brief report. One proposal went back - import assertions. 56 | Process changes - active consensus - explicit report is now required. Better documentation on when things are ready for advancement https://github.com/tc39/how-we-work/pull/130 . Active consensus https://github.com/tc39/how-we-work/pull/122 . 57 | 58 | * 2022-2023 Public Calendar for web standards group meetings [#191](https://github.com/openjs-foundation/standards/issues/191) 59 | *Jory added meetings to TC39, TC53 & W3C meetings. 60 | *Checking on Unicode meetings and see what we should include on the public calendar. 61 | *Other groups who would be interested in being tracked on the public calendar. Avoid collisions. And find opportunities to coexist in the same space. 62 | *Winter CG has a public calendar 63 | 64 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 65 | *Jory to edit document this week and review it in next weeks meeting. 66 | 67 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 68 | *Need to define how we are going to represent the details of a person, their expertise and how they are providing SME value in the documentation for an application for travel funds. 69 | *Action Item to write the policy in March. 70 | 71 | *OpenJS World and Summit & Standards Working Group 72 | *Content - program committee has been working. We have 15 onsight sessions. 10 -15 virtual sessions. Portions of those sessions will be curated. 73 | *The Standard track was well received in the past. 74 | *Awards: Unsung hero, Leading by example, Outstanding contribution by a new arrival, Education 75 | *Event is the 9th. 3 or 4 weeks to have the award made and shipped. Need to have an award recommendation by April 4th. Put a call out for nominations soon. 76 | * Security working group has planned a working session or public session at the Summit in the past. 77 | *Luke will let Claudio know about needing 1 hour for the Standards Working Group and coordinate follow up. 78 | 79 | 80 | ## Q&A, Other 81 | 82 | ## Upcoming Meetings 83 | 84 | * **Calendar**: 85 | 86 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 87 | -------------------------------------------------------------------------------- /meeting-notes/2023.02.20_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-02-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/U4AWd4jAHHs 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | 15 | 16 | ## Agenda 17 | 18 | ### Announcements 19 | 20 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 21 | 22 | ### openjs-foundation/standards 23 | 24 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 25 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 26 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 27 | 28 | 29 | 30 | ## Q&A, Other 31 | 32 | ## Upcoming Meetings 33 | 34 | * **Calendar**: 35 | 36 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 37 | 38 | -------------------------------------------------------------------------------- /meeting-notes/2023.03.07_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-03-07 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/89Opm3Q9z9A 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/208 7 | 8 | ## Present 9 | 10 | * Jory Burson 11 | * Richard Gibson 12 | * Lea Verou 13 | * Guy Bedford 14 | * Joe Sepi (@joesepi) 15 | * Jordan Harband (@ljharb) 16 | * Darcy Clarke (@darcyclarke) 17 | * 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 24 | 25 | ### openjs-foundation/standards 26 | 27 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 28 | 29 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 30 | 31 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 32 | 33 | ## Q&A, Other 34 | 35 | * Is there interest &/or potential resourcing available to help standardize [SemVer](https://semver.org/) as a Web API? (ref. https://github.com/nodejs/tooling/issues/146) ~ @darcyclarke 36 | * Is this the right venue? If not, where should this be brought? 37 | * This proposal was originally brought to the Node.js Tooling WG but there’s limited availability & OpenJSF has access to/connections with ECMA, W3C, OSI etc. 38 | * Various pieces of feedback have been given about where the implementation could/should live (runtime/web api etc.) 39 | * Scope of this functionality may be limited to the 2.0.0 schema & corresponding comparators (may not be 1:1 with “node-semver” - as that expands on range comparators) 40 | 41 | 42 | ## Upcoming Meetings 43 | 44 | * **Calendar**: 45 | 46 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 47 | -------------------------------------------------------------------------------- /meeting-notes/2023.03.21_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-03-21 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/NqU1kBPFbik 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Jory Burson (@jorydotcom) 15 | * Robin Ginn (@rginn) 16 | * Lea Verou 17 | * Richard Gibson 18 | * Ben Sternthal 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | LF Standards program manager role open. Send referrals to Jory. Linux Foundation Standards Program Manager | SmartRecruiters 27 | 28 | 29 | 30 | 31 | 32 | ### openjs-foundation/standards 33 | 34 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 35 | 36 | Reminder to think about the persons you would like to nominate someone for the pathfinder award 37 | Jory to request session on participation with Standards Group at OpenJS World Collab Summit 38 | 39 | * Concise Guide to Participating in Web Standards Document WIP [#190](https://github.com/openjs-foundation/standards/issues/190) 40 | 41 | Merged! 42 | Will also be added to website - preferring to make this automatic tool 43 | 44 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 45 | No update 46 | 47 | * Becoming a TC39 delegate [#211](https://github.com/openjs-foundation/standards/issues/211) 48 | Lea wanted feedback from TC-39 49 | Help Lea Reach quorum on +1 50 | 51 | * /standards repo issue cleanup 52 | https://www.youtube.com/@OpenJSFoundation!! 53 | 54 | * Secure the Web Forward Workshop - Call for Papers [#213](https://github.com/openjs-foundation/standards/issues/213) 55 | 56 | workshop now officially announced https://www.w3.org/blog/news/archives/9860 57 | https://w3c.social/@w3c/110055807072909771 58 | https://twitter.com/w3c/status/1637805952156966912 59 | https://w3c.social/@w3cdevs/110055799616511612 60 | 61 | 62 | AOB 63 | Lea will submit a request for TAG travel. 64 | 65 | ## Q&A, Other 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Calendar**: 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | 73 | -------------------------------------------------------------------------------- /meeting-notes/2023.04.04_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-04-04 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtube.com/live/pehwjNg0O40?feature=share 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Jory Burson (@jorydotcom) 16 | * Donovan Buck (@dtex) 17 | * Eemeli Aro (@eemeli) 18 | * Jordan Harband (@ljharb) 19 | * Joe Sepi (@joesepi) 20 | * Mike Champion (@michaelchampion) 21 | * Richard Gibson (@gibson042) 22 | * Tobie Langel (@tobie) 23 | * Hemanth (@hemanth) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | 29 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 30 | 31 | GraphQL Conf announced - Sept. 19-21 32 | V2 Ecma 209 TC53 announcement! Lots of examples 33 | TC39 has cut candidate spec for ES2023 34 | 2 updates to stage 2, 1 stage 1 for awaitdictionary 35 | Import assertions is now import attributes, back to stage 3 36 | Class decoratators 37 | Updates from the 95th TC39 meeting - DEV Community 38 | W3C update 39 | Charter proposal for machine learning apis in the browser - no controversy there 40 | Member survey to give guidance to committee for CEO search 41 | Action to Jory to review; is there anything useful we can say/share? 42 | Survey closes Friday 43 | 44 | 45 | 46 | ### openjs-foundation/standards 47 | 48 | * Clean up Working Group Members List [#215](https://github.com/openjs-foundation/standards/issues/215) 49 | See #216 50 | PR Merged & Issue Closed 51 | 52 | * Secure the Web Forward Workshop - Call for Papers [#213](https://github.com/openjs-foundation/standards/issues/213) 53 | workshop now officially announced 54 | https://www.w3.org/blog/news/archives/9860 55 | https://w3c.social/@w3c/110055807072909771 56 | https://twitter.com/w3c/status/1637805952156966912 57 | https://w3c.social/@w3cdevs/110055799616511612 58 | CFP Closes April 24th! 59 | Bring concrete problems and use cases 60 | Whom should we encourage from our community to submit a proposal or to attend? 61 | jQuery team + to talk about the IDC survey we’re fielding for security 62 | Use cases + dev focused experience - good oppty for first time standards people 63 | Tobie has offered to help people prepare a proposal or to review 64 | Node security work + Web APIs 65 | Webpack? 66 | Imports / new feature security reviews 67 | 68 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 69 | JSLandia Award Nomination Form: 70 | https://forms.gle/y7qvGgzJCD9eJGuh9 71 | We have until April 18 to determine the recipient for the Standards Pathfinder Award 72 | Session for Standards WG: 73 | https://github.com/openjs-foundation/summit/issues/356 74 | Idea - check with James Snell RE WinterCG session? 75 | 76 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 77 | No Update 78 | 79 | AOB 80 | Tobie will be available to go to Nice to represent OpenJS Foundation if we are interested - - would running a 81 | Welcome back Hemanth 82 | 83 | 84 | 85 | 86 | ## Q&A, Other 87 | 88 | ## Upcoming Meetings 89 | 90 | * **Calendar**: 91 | 92 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 93 | 94 | -------------------------------------------------------------------------------- /meeting-notes/2023.04.18_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-04-18 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtube.com/live/JA9FVz_Yt7E 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * Robin Ginn (@rginn) 15 | * Brian Kardell (@bkardell) 16 | * Michael Champion (@michaelchampion) 17 | * Jory Burson (@jorydotcom) 18 | * Richard Gibson (@gibson042) 19 | * Joe Sepi (@joesepi) 20 | * Jordan Harband (@ljharb) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | * Nominations open for W3C AB - open through May 1. 6 positions 27 | * Node.js 20! 28 | * Call for papers - Secure the Web Forward Workshop this June 29 | 30 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 31 | 32 | ### openjs-foundation/standards 33 | 34 | * PR to add Mohammed Keyvanzadeh to the Standards WG - Node.js Contributor 35 | https://github.com/openjs-foundation/standards/pull/218 36 | Some issue with timezone to attend this meeting 37 | Please +1, will merge after call 38 | 39 | * PR to add meeting minutes - https://github.com/openjs-foundation/standards/pull/220 40 | Please +1, will merge after call 41 | 42 | * Response to W3C CEO search survey: 43 | https://github.com/openjs-foundation/standards/issues/219 44 | This has been sent in, but Lea’s points RE ways we could engage and other open source-relevant topics are 45 | Will close #219; open new item to reach out to new key partners RE themes - what would our consensus message be? 46 | 47 | * Secure the Web Forward Workshop - Call for Papers [#213](https://github.com/openjs-foundation/standards/issues/213) 48 | ACTION: Post this issue/website to the #general and #security channels 49 | 50 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 51 | Joe volunteers to participate 52 | 53 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 54 | Table 55 | 56 | Private Session: 57 | JSLandia - Standards Pathfinder Award Nominee Discussion & Recommendation 58 | 59 | 60 | ## Q&A, Other 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Calendar**: 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 67 | 68 | -------------------------------------------------------------------------------- /meeting-notes/2023.05.02_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-05-02 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/4p7GWlbfCMk 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/227 7 | 8 | ## Present 9 | * Robin Ginn (@rginn) 10 | * Ben Sternthal (@bensternthal) 11 | * Lea Verou (@LeaVerou) 12 | * Joe Sepi (@joesepi) 13 | * Richard Gibson (@gibson042) 14 | * Jory Burson (@jorydotcom) 15 | * Jordan Harband (@ljharb) 16 | * Michael Champion (@michaelchampion) 17 | * Hemanth HM (@hemanth) 18 | * Darcy Clarke (@darcyclarke) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | Sovereign Tech Fund - congratulations to our projects and thank you to the fund! 🎉 27 | Reminder to submit proposals for the Secure the Web Forward Workshops 28 | OpenJS World & Collab Summit next week 🎉 29 | 30th Anniversary - Web Platform is RF 🎉 30 | 31 | ### openjs-foundation/standards 32 | 33 | * Minutes of previous meeting - approval & merge 34 | * Liaison Reports & Updates 35 | * Lea / Tag Face to Face Report from April 36 | * Agreed that there is a lot of work and we need more input from more people on design reviews - ex. API design, security, accessibility. Going to ask the AB/AC for more seats on the TAG. 2 elected, one appointed. Also looking for some lightweight appointment roles to fill in gaps - e.g. as a liaison - to help train/sustain the group more efficiently. 37 | * Discussion of closer collab between TAG and TC39. Groups are not working together a lot, but not a lot of input on design principles and other ideas. More consistency would be potentially better for devs. Will have Tc39 tracker label on TAG issues and inviting participants to use this and provide advice. Design principles are web centric, TC39 are broader. Suggestion to W3C to make it more inclusive.Related issue on TAG repo: https://github.com/w3ctag/design-principles/issues/436 38 | * Discussion about the confusion of ownership of some APIs & issues that arise when non-JS programmers write JS APIs in webIDL 39 | * OpenJS can help make the case for more inclusivity 40 | * Jory: can we have Tobie talk about prioritization of user needs at the AC meeting next week. “How can we help server side and browser side devs have more coherent experiences” 41 | * Jordan: TC39 Plenary after OpenJS World in Vancouver. No updates at this time. 42 | 43 | * Request to be designated as W3C AC alternate for next W3C AC F2F [#226](https://github.com/openjs-foundation/standards/issues/226) 44 | * +1 to the request and to the travel support 45 | * Question - what are the 2-3 things on our Agenda that Tobie will support. 46 | * Jory to sync with Tobie on the engagement plan 47 | 48 | * Add Tobie Langel as OSI Representative [#224](https://github.com/openjs-foundation/standards/pull/224) 49 | * tabled until Tobie can attend and suggest opportunities for deeper engagement. 50 | 51 | * Nominations open for W3C Advisory Board [#223](https://github.com/openjs-foundation/standards/issues/223) 52 | * Nomination period has closed. 53 | 54 | * Secure the Web Forward Workshop - Call for Papers [#213](https://github.com/openjs-foundation/standards/issues/213) 55 | * Reminder shared 56 | 57 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 58 | * Collab summit and Friday sessions scheduled. 59 | 60 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 61 | * Tabled for time. 62 | 63 | 64 | 65 | 66 | ## Q&A, Other 67 | 68 | ## Upcoming Meetings 69 | 70 | * **Calendar**: 71 | 72 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 73 | 74 | -------------------------------------------------------------------------------- /meeting-notes/2023.05.16_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-05-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/xFLq_U8jpSg 6 | * **GitHub Issue**: [#230](https://github.com/openjs-foundation/standards/issues/230) 7 | ## Present 8 | 9 | * Robin Ginn (@rginn) 10 | * Jordan Harband (@ljharb) 11 | * Tobie Langel (@tobie) 12 | * Michael Champion (@michaelchampion) 13 | * Brian Kardell (@bkardell) 14 | * Lea Verou (@LeaVerou) 15 | * Rick Markins (@rxmarbles) 16 | * Ethan Arrowood (@Ethan-Arrowood) 17 | * Hemanth HM (@hemanth) 18 | * Wes Todd (@wesleytodd) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | ### openjs-foundation/standards 27 | 28 | * W3C AB Election Ballot Due June 1 ([#232](https://github.com/openjs-foundation/standards/issues/232) 29 | - Tobie notes that this is a special election due to the change in legal entity. Expectations is that the same persons will be reconfirmed, pending votes. 30 | - Discussion about the role of the AB, as well as historical evolution of W3C Community and roles related to dispute resolution and other functions 31 | - Tobie reported that the AC meeting was productive and that the atmosphere seemed to be moving past the uncertainty of the Legal entity transition 32 | - Robin reminded people that the W3C is hiring. 33 | 34 | 35 | * W3C TPAC 11-15 September 2023 - Break out session? [#231](https://github.com/openjs-foundation/standards/issues/231) 36 | - Tobie, Brian and Lea plan attend TPAC 37 | - Would there be interest in doing a breakout session? Action: brainstorm 38 | 39 | 40 | * Add Tobie Langel as OSI Representative [#224](https://github.com/openjs-foundation/standards/pull/224) 41 | - Tobie provided context about the OSI and some of the work it does 42 | - Noted that he is willing to be the point of contact for Myles, who stepped away 43 | - Tobie noted that the role the OpenJS Foundation could play in its advocacy and education work 44 | - Michael C. noted that Tobie should work to gather consensus and report regularly with this group 45 | 46 | * Secure the Web Forward Workshop - Call for Papers [#213](https://github.com/openjs-foundation/standards/issues/213) 47 | - Robin noted that the Test the Web Forward has been postponed and that we are considering doing a workshop around TPAC 48 | 49 | * Discuss `package.json` standardization and governance [#233](https://github.com/openjs-foundation/standards/issues/233) 50 | - Ethan A. discussed his idea about opportunities for standards around the package.json format. Further discussion ensued, and has also been captured on the issue. 51 | - Ethan and others will further develop these thoughts into a one-page paper summarizing the problem statements and key stakeholders for engagement. 52 | 53 | * Standards Group Participation at OpenJS World [#205](https://github.com/openjs-foundation/standards/issues/205) 54 | 55 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 56 | * Stepping down as OSI Affiliate Representative [#170](https://github.com/openjs-foundation/standards/issues/170) 57 | - will be closed by #224 58 | 59 | 60 | 61 | ## Q&A, Other 62 | 63 | ## Upcoming Meetings 64 | 65 | * **Calendar**: 66 | 67 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 68 | 69 | -------------------------------------------------------------------------------- /meeting-notes/2023.05.30_meeting_notes.md: -------------------------------------------------------------------------------- 1 | 2 | # OpenJS Foundation Standards Working Group Meeting 2023-05-30 3 | 4 | ## Links 5 | 6 | * **Recording**: https://youtu.be/yUq3M-W8Zy8 7 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/234 8 | 9 | ## Present 10 | 11 | - Jory Burson (@jorydotcom) 12 | - Lea Verou (@leaverou) 13 | - Leo Cunha 14 | - Jordan Harband (@ljharb) 15 | - Joe Sepi (@joesepi) 16 | - Robin Ginn (@rginn) 17 | - Tobie Langel (@tobie) 18 | - Michael Champion (@michaelchampion) 19 | - Darcy Clarke (@darcyclarke) 20 | - Sendil Kumar (@sendilkumarn) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | * Notes/Recording from May 16 meeting in progress… 29 | * CPC WG meeting today 30 | * Program Committee meeting tomorrow 31 | 32 | ### Liaison Updates 33 | * TC39 34 | * Jordan recommends reading Hemanth’s summaries. A number of stage changes. 35 | * https://dev.to/hemanth/updates-from-the-96th-tc39-meeting-4goe 36 | * 3 proposals at stage 4 37 | * TC53 38 | * No update 39 | * W3C TAG 40 | * No Updates 41 | * Test the Web Forward - planning the virtual session Sept. 26-28 - would be (3) 2-hour session with some pre-work 42 | * OSI 43 | * None yet 44 | * Unicode 45 | * No update 46 | * Tobie asks if the IEEE Governance WG should be reported on 47 | * Could be relevant to some open CPC issues 48 | * Some setbacks related to process and system, group may be moving its activities to another forum. 49 | 50 | ### openjs-foundation/standards 51 | 52 | * W3C AB Election Ballot Due June 1 (not recorded) ([#232](https://github.com/openjs-foundation/standards/issues/232) 53 | 8 Candidates for 6 positions 54 | https://www.w3.org/2023/04/ab-nominations.html 55 | Action: Jory to look at our votes from last time and submit ballot 56 | Chris, Elika, Wendy, Max, Avneesh, Tantek, Heejin, Song 57 | 58 | * W3C TPAC 11-15 September 2023 - Break out session? [#231](https://github.com/openjs-foundation/standards/issues/231) 59 | Tobie: we should work on the topic and identify outcomes we would like to have 60 | Tobie: would be happy to help with this if we have a proposal we want to get behind 61 | MC: multiple, interoperable implementations is increasingly harder to do. Slippery slope if chromium becomes the standard. Nuanced issue that we could lead/raise a voice in. 62 | Would need to discuss further to avoid contention. May not be well received if we raise it? 63 | Action: reliable and discuss further in slack 64 | 65 | * Add Tobie Langel as OSI Representative [#224](https://github.com/openjs-foundation/standards/pull/224) 66 | Sounds like we approved this last week with the understanding that Tobie will focus on opportunities for OpenJS communities to influence/advocate on policy matters particularly with regard to the CRA 67 | Action: merge PR and determine next steps with OSI 68 | 69 | * Discuss `package.json` standardization and governance [#233](https://github.com/openjs-foundation/standards/issues/233) 70 | Word document that Tobie and ethan have been working on to fully understand whether this is an opportunity for standardization. Darcy suggests that we really need the people from npm to weigh. Also spdx, and web manifest space. Probably learnings from that. People need to be “lured in” and we need to define problem space and what problems need to be solved in order to bring those people in. Need to better wordsmith / phrase problem statements. Feels like it’s unclear what the real value is for the people who need to be around the table (e.g. npm). May be coming from concern in the ecosystem, codifying common keys to keep people from stepping on others’ toes. Lots of people who need to be bought in (eslint, others who do not want to see a standard) 71 | [WIP] Future of package.json 72 | Action: Followup when the document is further baked and ready for discussion. 73 | 74 | * Stepping down as OSI Affiliate Representative [#170](https://github.com/openjs-foundation/standards/issues/170) 75 | Will close with #224 76 | 77 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 78 | tabled 79 | 80 | ## Q&A, Other 81 | 82 | ## Upcoming Meetings 83 | 84 | * **Calendar**: 85 | 86 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 87 | 88 | -------------------------------------------------------------------------------- /meeting-notes/2023.06.13_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-06-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=27ZKiaw90lY 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/242 7 | 8 | ## Present 9 | * Ben Sternthal (@bensternthal) 10 | * Robin Ginn (@rginn) 11 | * Rick Marlins (@rxmarbles) 12 | * Jordan Harband (@ljharb) 13 | * Luke Karrys (@lukekarrys) 14 | * Jory Burson (@jorydotcom) 15 | * Ethan Arrowood (@Ethan-Arrowood) 16 | * Hemanth HM (@hemanth) 17 | * Joe Sepi (@joesepi) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | New sec eng champion -> Jordan Harband 23 | ES 2023 Blog - Hemanth 24 | 25 | TC39 26 | Next Month 27 | ECMA 28 | General assembly June 27 29 | WinterCG 30 | 31 | W3C 32 | TPAC / Secure the Web Forward Workshop updating 33 | 34 | * Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 35 | 36 | ### openjs-foundation/standards 37 | 38 | * Add @rxmarbles as active member [#241](https://github.com/openjs-foundation/standards/pull/241) 39 | * Joe makes a point that we should make sure we add the person to the standards team on GitHub and/or any other resources. We don’t have a mailing list. Rick has a tool as does CNCF. 40 | ACTION: Joe/Rick to look into tooling options to help keep sources synced. 41 | 42 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 43 | * Related PRs: 44 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 45 | * Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) 46 | * Modifications requested on #239 47 | * add @sendilkumarn as Active member [#238](https://github.com/openjs-foundation/standards/pull/238) 48 | * Approved & to be merged after resolving merge conflict 49 | * Add @darcyclarke as Active Member [#237](https://github.com/openjs-foundation/standards/pull/237) 50 | * Approved & Merged 51 | 52 | ## Q&A, Other 53 | 54 | Package.json - group will plan to present next standards meeting 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Calendar**: 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | 62 | -------------------------------------------------------------------------------- /meeting-notes/2023.06.27_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-06-27 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=f6NF-UCpfF0 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/244 7 | 8 | ## Present 9 | 10 | * Jordan Harband (@ljharb) 11 | * Ethan Arrowood (@Ethan-Arrowood) 12 | * Joe Sepi (@joesepi) 13 | * Robin Ginn (@rginn) 14 | * Jory Burson (@jorydotcom) 15 | * Hemanth HM (@hemanth) 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | * Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 22 | 23 | ### TC Reports/News - check out the standard 24 | * Ecma 25 | * TC39: Meeting in July in Norway. September in Tokyo 26 | * TC53 - no updates 27 | * OSI - no updates 28 | * W3C 29 | * WinterCG - no updates 30 | * Unicode Consortium - no updates 31 | 32 | ### openjs-foundation/standards Issues 33 | 34 | * Be a founding member of Open Policy Alliance [#243](https://github.com/openjs-foundation/standards/issues/243) 35 | * This has not yet been announced as far as we can see; WG generally supports OpenJS's participation 36 | * To be discussed further with @tobie 37 | * Would need Board approval - @rginn to discuss with Board 38 | 39 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 40 | * Related PRs: 41 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 42 | * Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) 43 | * Action: @jorydotcom to complete requested edits / clarifications 44 | 45 | ## Q&A, Other 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | 53 | -------------------------------------------------------------------------------- /meeting-notes/2023.08.08_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-08-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/afscmT85ZiU 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/251 7 | 8 | ## Present 9 | 10 | * Tobie Langel (@tobie) 11 | * Robin Ginn (@rginn) 12 | * Joe Sepi (@joesepi) 13 | * Rick Markins (@rxmarbles) 14 | * Chris de Almeida (@ctcpip) 15 | * Darcy Clarke (@darcyclarke) 16 | * Richard Gibson (@gibson042) 17 | * Jory Burson (@jorydotcom) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * Birds of A Feather in Bilboa - Sept. 19. Secure the Web Forward. Happening Week after TPAC! 24 | * State of Open Standards report out 25 | * Noon CT - TC39 TG3 repo & calendar. Also, join the TG3 room in Matrix, and contact Chris or another chair for more information. Currently meeting bi-weekly and alternating timezones 26 | 27 | * Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | Liaison Updates 30 | * OSI - See notes under #243 31 | * W3C - TPAC / Wednesday is the developer/community day. Open for participation. 32 | * TC53 - no updates 33 | * Unicode - no updates 34 | * Ecma 35 | * TC39 36 | * TG3 meets tomorrow. 37 | * New Task Group - TG4 for sourcemaps 38 | * https://github.com/guybedford/import-maps-extensions#integrity 39 | 3️⃣ Array Grouping 40 | 3️⃣ Promise.withResolvers 41 | 3️⃣ Source Phase Imports 42 | 3️⃣ Time Zone Canonicalization 43 | 2️⃣ Deferred Import Evaluation 44 | 1️⃣ DataView get/set Uint8Clamped methods 45 | 1️⃣ Optional Chaining assignment 46 | Related: Package Data Interop Work. On Hiatus with that but back when Ethan is back. 47 | 48 | ### openjs-foundation/standards 49 | 50 | * Be a founding member of Open Policy Alliance (an OSI project) [#243](https://github.com/openjs-foundation/standards/issues/243) 51 | 52 | OSI - we agreed to move ahead with the open policy alliance. We will be showcased as a member. No news on that specifically. How will the group be updated on the CRA as it progresses, for example? Not sure. We could ask Mirko to do a briefing on the CRA to the group. Also, what are the specific things OpenJS or its projects can do / weigh in on with respect to policy? 53 | Action: invite Mirko to attend / present 54 | Action: Merge 55 | 56 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 57 | 58 | * Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) 59 | * Merged 60 | 61 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 62 | 63 | Meta Action Items: 64 | Update the notes template & make an issue template for the Liaison updates 65 | 66 | ## Q&A, Other 67 | 68 | Question: Should we liaise with IETF / IESG? Are there projects or efforts we should be tracking? Are there things that are blocking other efforts? Example: https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/ 69 | What other IETF groups would we want to follow? 70 | Potentially: 71 | https://datatracker.ietf.org/wg/sedate/about/ 72 | https://datatracker.ietf.org/wg/jose/about/ 73 | https://datatracker.ietf.org/wg/jmap/about/ 74 | https://datatracker.ietf.org/wg/jsonpath/about/ 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | 82 | -------------------------------------------------------------------------------- /meeting-notes/2023.08.22_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-08-22 2 | 3 | ## Links 4 | 5 | * **Recording**: Meeting was not recorded. 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/255 7 | 8 | ## Present 9 | 10 | * Brian Kardell (@bkardell) 11 | * Hemanth HM (@hemanth) 12 | * Chris de Almeida (@ctcpip) 13 | * Robin Ginn (@rginn) 14 | * Jory Burson (@jorydotcom) 15 | * Richard Gibson (@gibson042) 16 | * Rick Markins (@rxmarbles) 17 | * Ethan Arrowood (@Ethan-Arrowood) 18 | * Jordan Harband (@ljharb) 19 | * Tobie Langel (@tobie) 20 | * Lea Verou (@leaverou) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | FYI: APAC-friendly TC39-TG3 meetings is tonight at 01 UTC 27 | 28 | * Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 29 | 30 | ### Liaison Reports 31 | 32 | * Template for liaison reports #252 [#252](https://github.com/openjs-foundation/standards/issues/252) 33 | 34 | ### openjs-foundation/standards Agenda 35 | 36 | * Create 2023.08.08_meeting_notes.md #257 [#257](https://github.com/openjs-foundation/standards/pull/257) 37 | - please review! 38 | 39 | * update active members #254 [#254](https://github.com/openjs-foundation/standards/pull/254) 40 | - Merged! 41 | 42 | * Check Standards WG agrees to migrate to a Collab Space #253 (https://github.com/openjs-foundation/standards/issues/253) 43 | - Difference is decision-making authority. No real difference except name. 44 | - Ref: https://github.com/openjs-foundation/cross-project-council#openjs-collaboration-spaces 45 | - We would update our charter to call it a collab space and clarify what items we have 46 | 47 | * Travel request for Jordan Harband for TC39 #40 [#40](https://github.com/openjs-foundation/community-fund/pull/40) 48 | - Agreed, assuming Jordan’s amount was factored into the forecasting 49 | 50 | * Document Guidance for requesting travel funds for Standards WG-related activities #256 [#256](https://github.com/openjs-foundation/standards/issues/256) 51 | - Chen. is a champion of a proposal that is benefitting Node. Chen. is a valued member of the TSC. It is clarified that this approval is a one-time approval and not an ongoing approval for future travel 52 | - We can create/identify some eval criteria. Is this person a community member/leader? Are they presenting the work they have been doing? How will it drive impact? Are they reasonably geographically located? 53 | - Concern: let’s make sure that the process doesn’t overly favor what looks like high-level impact. Lea’s example of the work of design reviews. Need to make sure the process also works for “Work” 54 | - An after-event report may not be the most useful activity. 55 | - What are the travel commitments assumed for participation - e.g. W3C TAG nominees are expected to travel to most of the meetings as part of the nomination process. 56 | - Staff and CPC are working on processes and guidelines. Considering putting a cap on the expense totals. 57 | - Proposal - Signal prioritization of standards WG-related travel that are connected to work items that will be discussed 58 | - Action Item: Create a scope/bucket that defines what kinds of travel fund requests we will be considering/recommending for funding for 2024, and attempt to frontload what those expense requests will be. Need to consider the variables (cost, proximity of location, urgency of requests, deadlines, how long in advance the event was announced/known) Consider recommending things like, asking people to share expenses with another organization. 59 | - Action Item - Talk to Samina about whether Ecma could create and support a travel fund, and put it on the ExeCom meeting agenda 60 | - Action Item - Understand from Ben what the balance of the fund 61 | 62 | * W3C TPAC 11-15 September 2023 - Break out session? #231 [#231](https://github.com/openjs-foundation/standards/issues/231) 63 | - Closed 64 | 65 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 66 | - Noted that Tobie and Jordan are in alignment a this point 67 | 68 | Tabled for time 69 | 70 | * Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) 71 | 72 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 73 | 74 | ## Q&A, Other 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | 82 | -------------------------------------------------------------------------------- /meeting-notes/2023.09.05_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-09-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=i7Uo7Z9h-p8 6 | * **GitHub Issue**: Issue #261 7 | 8 | ## Present 9 | 10 | * Jory Burson (@jorydotcom) 11 | * Tobie Langel (@tobie) 12 | * Joe Sepi (@joesepi) 13 | * Rick Markins (@rxmarbles) 14 | * Eemeli Aro (@eemeli) 15 | * Mike Samuel (@mikesamuel) 16 | * Jordan Harband (@ljharb) 17 | * Richard Gibson (@gibson042) 18 | * Lea Verou (@leaverou) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | * Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 25 | 26 | TPAC is next week! Go see Eemeli and Lea. Relevant breakout sessions: 27 | * [DOM Localization](https://github.com/w3c/tpac2023-breakouts/issues/52) 28 | * [The Future of Powerful APIs on the Web Platform](https://github.com/w3c/tpac2023-breakouts/issues/76) 29 | 30 | Travel Fund progress continues - follow CPC meetings and WG sessions for more. 31 | 32 | ### openjs-foundation/standards 33 | 34 | * W3C wants to increase the size of the TAG [#260](https://github.com/openjs-foundation/standards/issues/260) 35 | Lea brought up the issue with others; Tobie submitted our support. 36 | 1 elected, 1 appointed. Would likely happen during the next election cycle. 37 | Vote closes today (Sept. 5) 38 | 39 | * 2024 Meeting / Schedule Conflicts [#259](https://github.com/openjs-foundation/standards/issues/259) 40 | Jory to update the public calendar as dates are locked in 41 | 42 | * Document Guidance for requesting travel funds for Standards WG-related activities [#256](https://github.com/openjs-foundation/standards/issues/256) 43 | CPC is looking to create a rubric for scoring. 44 | https://github.com/openjs-foundation/cross-project-council/issues/1154 45 | Action: provide any feedback/comments to #1154 46 | Related: what are the P0s for Standards Related travel in 2024? How can we tie the impact of this work to specific 47 | 48 | * Check Standards WG agrees to migrate to a Collab Space [#253](https://github.com/openjs-foundation/standards/issues/253) 49 | No further discussion needed 50 | We need a charter and small tasks - CPC will let us know what next. 51 | 52 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 53 | Comments to be addressed and PR merged 54 | 55 | * Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) 56 | Conflict to be resolved and merged 57 | 58 | * Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) 59 | 60 | AOB 61 | Mike Samuel asked in chat about language translations and thread models. A brief discussion ensued about which organizations are keeping this in mind. 62 | MessageFormat spec update from Eemeli - feels like this spec will be out in spring 2024 63 | 64 | 65 | ## Q&A, Other 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Calendar**: 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | 73 | -------------------------------------------------------------------------------- /meeting-notes/2023.10.03_meeting-notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-10-03 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/265 7 | 8 | ## Present 9 | 10 | * Ethan Arrowood (@Ethan-Arrowood) 11 | * Divy Tolia (@designmoreweb) 12 | * Richard Gibson (@gibson042) 13 | * Tobie Langel (@tobie) 14 | * Joe Sepi (@joesepi) 15 | * Robin Ginn (@rginn) 16 | * Lea Verou (@leaverou) 17 | * Jory Burson (@jorydotcom) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * First package metadata interoperability collab space meeting. See PR # https://github.com/openjs-foundation/package-metadata-interoperability-collab-space/pull/2 24 | * Liaison Reports/Updates 25 | * TC39 - Plenary in Tokyo, community event was the JSConf-JP. One proposal went to stage 4, many advanced to stage 1 & 2. One proposal went back a stage. 26 | * TC53 - no updates 27 | * OSI / OPA - Some initial calls are starting to take place with the OPA. Tobie will report when he learns more. 28 | * W3C 29 | * Congratulations to Seth Dobbs, recently announced as next CEO of W3C. Robin will send a congratulations/welcome note on behalf of the org. 30 | * TPAC was productive and very high turnout. Lea met with Eemeli and discussed a lot about message format, inspired the need for design principles for text-based. Discussion about standardized paths for APIs. Good feedback on State of HTML survey. Take the survey https://survey.devographics.com/en-US/survey/state-of-html/2023 31 | * BoF / Secure the Web Forward 32 | * jQuery Infra Report findings - good discussion about creating more of a coalition among key stakeholder organizations 33 | * STF Findings - went well 34 | 35 | ### openjs-foundation/standards 36 | 37 | * PR - update member representation [#263](https://github.com/openjs-foundation/standards/pull/263) 38 | * merged 39 | 40 | * PR - meeting notes from 9/5 [#262](https://github.com/openjs-foundation/standards/pull/262) 41 | * Jory to accept editorial from Mohammed and merge 42 | 43 | * W3C wants to increase the size of the TAG [#260](https://github.com/openjs-foundation/standards/issues/260) 44 | * We voted for this but need to follow up to see if the resolution was passed. 45 | * Per email to ac-forum: Deadline is October 10 - Next election is Oct. 10 - Nov. 7 for nominations. 46 | * ACTION: Consider if there are people you would like to encourage to run/nominate 47 | 48 | * 2024 Meeting / Schedule Conflicts [#259](https://github.com/openjs-foundation/standards/issues/259) 49 | * Richard reported that first meeting of 2024 will be San Diego in person for TC39 / Also will be meeting 100 50 | * https://github.com/tc39/agendas 51 | * Pre-planning of travel would be ideal - TAG plans 2 in person meetings per year and 2 remote meetings 52 | * ACTION: Jory to update the standards wg 53 | 54 | * Document Guidance for requesting travel funds for Standards WG-related activities [#256](https://github.com/openjs-foundation/standards/issues/256) 55 | * No update from CPC Working Group 56 | * Tobie will update the issue 57 | 58 | * Check Standards WG agrees to migrate to a Collab Space [#253](https://github.com/openjs-foundation/standards/issues/253) 59 | * Tasks needed: 60 | * Update documents in repo 61 | * Update the name / other things 62 | * Create a Charter 63 | * Move collab to the collab space on the website etc 64 | 65 | ## Q&A, Other 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Calendar**: 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | -------------------------------------------------------------------------------- /meeting-notes/2023.10.17_meeting_notes.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Standards Working Group Meeting 2023-10-17 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: #267 7 | 8 | ## Present 9 | 10 | * Robin Ginn (@rginn) 11 | * Jory Burson (@jorydotcom) 12 | * Ethan Arrowood (@Ethan-Arrowood) 13 | * Chris de Almeida (@ctcpip) 14 | * Donovan Buck (@dtex) 15 | * Rick Markins (@rxmarbles) 16 | * Lea Verou (@leaverou) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | 22 | * Join us for the OpenJS in Finance track at the FINOS summit in NYC on Nov. 1 23 | 24 | ### Liaison Reports 25 | 26 | * Ecma Execom 27 | * Provisionally approved new TC - standardizing the Cyclone DX - https://owasp.org/blog/2023/10/11/OWASP-Foundation-Pursues-Ecma-International-Standardization-of-CycloneDX.html 28 | * TC39 29 | * INTL Message format proposal incubator call Next week https://github.com/tc39/incubator-agendas/blob/main/2023/10-25.md 30 | * There has been some conversation about a new stage or incremental step in order to reduce churn in stage 3 related to things that should have been covered in stage 2. 31 | * We have dates (and locations) determined for 2024 TC39 plenary meetings - not yet publicized but will be published soon 32 | * Action: Jory to add them to public Open Web Standards calendar 33 | * W3C TAG 34 | * Usual design reviews, regular activities proceeding as usual. Nothing too specific to this community at this time. 35 | * Discussion ensued about how and whether to get TC39 review of proposals. Opportunity to reconnect on this again related to the changes under discussion for “TC39 stage 2.5”. 36 | * Also discussion about where in the TC process the TAG review would be the best fit 37 | * TC53 38 | * Cupertino workship on Dec 6~ Next generation on Ecma 419 Workshop - https://www.ecma-international.org/news/invitation_to-ecma_tc53_workshop_in_cupertino_6_december_2023/ 39 | * OSI - no update 40 | * OPA - no update 41 | * Unicode - no update 42 | * Winter CG 43 | * No major updates, some discussion about home for Open Source implementations. 44 | * Jory to send Ethan the CSL spec. 45 | * Package Interop 46 | * First meeting went really well. Starting to get traction. Meeting once a month, interested persons are invited to join the discussion in the #package-meta-interop channel on OpenJS's Slack workspace. 47 | 48 | ### openjs-foundation/standards (Discussion Issues) 49 | 50 | * Meeting Minutes PR for review: https://github.com/openjs-foundation/standards/pull/266/files 51 | * Missing recording link. Jory to merge after updating link. 52 | 53 | * W3C wants to increase the size of the TAG [#260](https://github.com/openjs-foundation/standards/issues/260) 54 | * Still no confirmation / record of this outcome on the AC-Forum list. Email to W3C team last week on the question has not been answered. To be updated. 55 | * However, TAG Nominations are now open for 3 seats. 56 | * Jory to update the issue. 57 | 58 | * Document Guidance for requesting travel funds for Standards WG-related activities [#256](https://github.com/openjs-foundation/standards/issues/256) 59 | * CPC Requests a proposal from the Standards Collab Group on the importance of standards related travel and what we would want to fund and why. 60 | * Action: Open and issue and collaborate on proposal 61 | 62 | * Check Standards WG agrees to migrate to a Collab Space [#253](https://github.com/openjs-foundation/standards/issues/253) 63 | * No update, but need to amend the issue to track the tasks necessary to complete this. 64 | 65 | * WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) 66 | * Need @tobie to approve. 67 | 68 | ## Q&A, Other 69 | 70 | ## Upcoming Meetings 71 | 72 | * **Calendar**: 73 | 74 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 75 | -------------------------------------------------------------------------------- /proposals/stage1/REQUIREMENTS/README.md: -------------------------------------------------------------------------------- 1 | # Requirements 2 | > Stage 1 3 | 4 | ## Champion 5 | 6 | [Sendil Kumar](https://github.com/sendilkumarn) 7 | 8 | ## Description 9 | 10 | This document outlines requirements for the Standards committee's representatives. 11 | 12 | ## Who would be responsible? 13 | 14 | The elected representative, the OpenJS Foundation 15 | 16 | ## Why this proposal is important 17 | 18 | The needs of projects and ecosystem stakeholders being delegated via the representatives. These representatives are vital for voicing the collective view of and for the foundation. 19 | 20 | ## Requirements of the representatives 21 | 22 | The requirements for the elected representatives are as follows: 23 | 24 | * They should be a member of the OpenJS Foundation. 25 | * They should be available to travel to standards organizations' meetings. 26 | * For any meeting at which they represent the OpenJS Foundation: 27 | * They should be ready to handle any conflicts of interest that might arise. 28 | - For any potential conflict, please create a `pre-meeting` or use `weekly-meeting` to address the conflict. 29 | * They should be responsible for making sure the agenda is ready before the meeting. 30 | * They should focus / address concerns from the OpenJS Foundation's and its projects' prespectives. 31 | * They should update the community about the meetings (either present/write). 32 | 33 | Questions that are essential to address before moving to next stage: 34 | * Create a document about how we support organizations, how to interact with each org, What’s the decision making process, how to get involved with a project. 35 | -------------------------------------------------------------------------------- /resources/concise-guide-to-fixing-web-standards.md: -------------------------------------------------------------------------------- 1 | # Concise Guide to Identifying (and resolving) a Web Platform Bug 2 | 3 | Web developers rely on a great many software packages, libraries, and tools to build applications. End users expect to have the same experience on these applications regardless of their environment. The web is an ever-evolving platform to target as platforms add new features and APIs, and web standards bodies incorporate them into final specifications. Thus, hitting a bug can be a frustrating experience particularly when it is not clear _where_ the bug originates - is it in your code, the library code, the browser, the specification, or something else? Below are some questions to guide you through determining whether you have found a platform bug, and how to report it. 4 | 5 | 6 | 7 | 1. **Reduce, reduce, reduce** 8 | 9 | Bugs often appear in complex setups, and it can be unclear which part or which feature the bug is stemming from. The first step of any bug investigation is to eliminate code unrelated to the bug so that its causes can be more clearly investigated. This is called a _reduced testcase_ or _reduction_. A reduction will not only help you understand what is happening much better, it will also help you communicate about the issue with spec developers, browser engineers, and other stakeholders. Moreover, it will also help your bug being fixed faster: bugs that include links to reduced testcases are generally triaged a lot faster. \ 10 | \ 11 | Copy over the current page, script, or even your entire project and start aggressively *removing* code, checking that you can still reproduce the bug with the code left. This also applies to the UI: Shorten any non-relevant text, eliminate any unrelated CSS styling, simplify any HTML subtree. You can almost always reduce more than you think. Most bugs can be reduced to < 20 lines of code, often significantly less than that. If you’ve used unit tests before, it's a very similar process: imagine that you are writing a unit test to test if that particular bug is fixed. 12 | 13 | 14 | 15 | These additional resources may be helpful in learning how to create better reduced testcases: 16 | * [https://webkit.org/test-case-reduction/](https://webkit.org/test-case-reduction/) 17 | * [https://css-tricks.com/reduced-test-cases/](https://css-tricks.com/reduced-test-cases/) 18 | 19 | 20 | 2. **What kind of bug do you have?** 21 | In addition to the cross-browser compatibility bugs you might run into as you build your application, you may also hit bugs in a test environment, or in sample code/documentation, or in areas where a feature has been underspecified. Interoperability bugs deal with situations in which browsers behave differently from each other, and the specification either: agrees with one or more; requires a behavior that is not implemented anywhere; or is not clear about the correct behavior. Sometimes, browsers will agree on a behavior, and the relevant specification will be inaccurate, or underspecified for the correct behavior - let’s call these clarification bugs. \ 22 | \ 23 | To determine which is the case (and that you’re interpreting the issue correctly as well) start with reputable source documentation for the feature you are trying to use, such as [MDN Web Docs](https://github.com/mdn/content) or the documentation site for your browser engine. These resources will often note where there are known bugs, and will typically link you directly to the relevant specification(s) and their test suite(s) from these pages. A careful read of the spec may further clarify which kind of bug you are dealing with. 24 | 25 | 3. **Does the problem exist across multiple browsers?** \ 26 | Before you report the bug, you’ll want to have a good understanding of its behavior under certain conditions and which browsers may be impacted. Verify your bug by testing in multiple browsers - and multiple versions of the browser, such as the latest stable and latest nightly edition. This information is critical to writing a great bug report that browser engineers and spec authors can use. If you’re seeing what appears to be the same (incorrect) behavior across multiple browsers, you may want to first create a reduced test case to determine if your interpretation is faulty, or if supporting documentation needs to be improved. If you’re seeing different behavior across multiple browsers, you’ve found a compatibility bug. Check whether others have reported your bug. 27 | 28 | 29 | 4. **Is the feature/API you are trying to use available in all browsers?** \ 30 | Web standards are often updated on a “living” basis - meaning that the feature may be made available to use by browsers before it’s been enshrined into the specification, or that the specification has described intended behaviors that have not yet been put into implementations by all browsers. It also means that certain features may have been deprecated and are no longer available. Tools such as the Browser Compat Data tables and caniuse.com are great resources to help determine whether a feature is ready for you to use in production. Generally, these tables are updated as web specifications advanced through their respective committees, and as test suites and supporting documentation are added. Experimental features may also be represented in the data, but are often marked as such and should be used carefully - experimental features may change their behavior without notice. If you find a bug on an experimental feature, it can be really helpful to report it - it can provide the feature developer more information about developer behavior. 31 | 32 | 5. **Is there a test for the feature you are using, and if so, is it passing or failing?** \ 33 | Most modern web standards have either a test suite or a reference implementation associated with them: for HTML and CSS, the Web Platform Tests project contains the most authoritative test suite; Javascript’s test suite is called Test262. If there is a test suite, run tests relating to the bug you found in the implementation you were using. Does your implementation run the tests correctly? If the implementation seems to be correct, double-check your application code - you may have found an issue with the way a library or tool you’re using has implemented the standard, rather than an issue with the standard itself. 34 | 35 | 36 | If there is a reference implementation, try the scenario in which you found a bug in the presumably standard-compliant reference implementation. If you see behavior you think is buggy in the reference implementation, the specification itself may need fixing. 37 | 38 | 39 | 6. **Have other developers reported a similar issue?** \ 40 | Check whether your bug, or similar bugs, have already been filed - look at the repositories for the browser engines, the specification (final and draft versions, if these are kept separately), and test suites. Look at what other developers have reported, and whether the appropriate team has already provided a status update or other information relevant to your issue. Duplicating a bug report is generally seen as poor etiquette, but you may be able to add additional information, context, or data to an existing bug report that helps the team. \ 41 | \ 42 | If you’ve found a new bug - congratulations! Web platform bugs can be very fun problems to solve, but you may also find that you have to work a bit differently to resolve them. In addition to thoroughly understanding the bug, you may find that you have to do a lot of leg work to help others understand it - and agree to the resolution. It may require you to build consensus between engineers with competing implementations, contribute tests, or present research about usage patterns to spec proposal authors. 43 | 44 | **Additional Resources:** 45 | 46 | 47 | 48 | * Web Platform Contribution Guide [https://wpc.guide/bug-guide/](https://wpc.guide/) 49 | * Web Compat Project [https://webcompat.com/](https://webcompat.com/) 50 | * How to Report a Bug [http://testthewebforward.org/docs/bugs.html](http://testthewebforward.org/docs/bugs.html) 51 | * Case Study: The Caper of the Flaky Test [https://bocoup.com/blog/the-caper-of-the-flaky-test](https://bocoup.com/blog/the-caper-of-the-flaky-test) 52 | -------------------------------------------------------------------------------- /standards-calendar.md: -------------------------------------------------------------------------------- 1 | # 2019 Calendar of Standards Meetings 2 | 3 | This list is not exhaustive - it reflects meetings we may or may not be interested in sending an OpenJS Foundation representative to on our behalf. 4 | 5 | ## 2019 6 | 7 | | Date | Event | Location | SDO | 8 | |----------|-------|----------|-----| 9 | | 06.18-19 | TC53 In-person Meeting | Bay Area, CA | Ecma | 10 | | 06.26-27 | Ecma International General Assembly Meeting | Geneva | Ecma | 11 | | 07.23-25 | TC39 Plenary Meeting | Redmond | Ecma | 12 | | 09.16-20 | TPAC 2019 | Japan | W3C | 13 | | 09.18 | TC53 Meeting | Teleconference | Ecma | 14 | | 10.01-03 | TC39 Plenary Meeting | NYC | Ecma | 15 | | 10.29-30 | TC53 Plenary Meeting | Boston | Ecma | 16 | | 11.20 | TC53 Meeting | Teleconference | Ecma | 17 | | 12.03-05 | TC39 Plenary Meeting | Bay Area, CA | Ecma | 18 | | 12.10-11 | Ecma International General Assembly Meeting | Tokyo | Ecma | 19 | | 12.11 | TC53 Plenary Meeting | Tokyo | Ecma | 20 | 21 | ## 2020 22 | 23 | | Date | Event | Location | SDO | Representing members | 24 | |----------|-------|----------|-----|-----| 25 | | 01.22-24 | CSS WG F2F | Igalia @ A Coruña | W3C | | 26 | | 02.04-06 | TC39 Plenary Meeting | University of Honolulu / JSConfHI | Ecma | @gibson042 | 27 | | 02.25-26 | TC53 In-person Meeting | Palo Alto, CA | Ecma | | 28 | | 03.31-04.02 | TC39 Plenary Meeting | Cupertino, CA | Ecma | | 29 | | 04.27-29 | CSS WG F2F | Apple @ Cork, Ireland | W3C | | 30 | | 05.17-19 | AC 2020 | Seoul | W3C | | 31 | | 06.02-04 | TC39 Plenary Meeting | Chicago | Ecma | | 32 | | 06.17-18 | Ecma International General Assembly Meeting | Geneva | Ecma | | 33 | | 07.21-23 | TC39 Plenary Meeting | Seattle | Ecma | | 34 | | 07.27-31 | CSS WG F2F | Google @ Waterloo, ON or New York, NY | W3C | | 35 | | 09.22-24 | TC39 Plenary Meeting | Tokyo | Ecma | | 36 | | 10.26-30 | TPAC 2020 | Vancouver | W3C | | 37 | | 11.17-19 | TC39 Plenary Meeting | TBD | Ecma | | 38 | | 12.09-10 | Ecma International General Assembly Meeting | TBD North America | Ecma | | 39 | 40 | *To-do - add W3C working group meetings and workshops. See https://www.w3.org/participate/eventscal.html for all W3C events.* 41 | --------------------------------------------------------------------------------