├── .github ├── ISSUE_TEMPLATE │ ├── config.yml │ └── regular-issue.md └── workflows │ ├── link-checker.yml │ └── linter-workflow.yml ├── .gitignore ├── .remarkrc ├── .travis.yml ├── CODEOWNERS ├── CODE_OF_CONDUCT.md ├── CPC-CHARTER.md ├── Dates-and-Reminders.md ├── LICENSE.md ├── NEW_PROJECT_APPLICATION.md ├── PROJECT_CHARTER_TEMPLATE.md ├── PROJECT_PROGRESSION.md ├── PROJECT_SECURITY_REPORTING.md ├── README.md ├── collaboration-spaces ├── COLLABORATION_NETWORK.md ├── COLLABORATION_SPACE_PROGRESSION.md └── NEW_COLLABORATION_SPACE_APPLICATION.md ├── community-fund └── COMMUNITY_FUND_POLICY.md ├── conduct ├── COC_POLICY.md ├── COC_PROCESS_FOR_INCIDENT_MANAGEMENT.md ├── COC_TEAM_CHARTER.md └── MEMBER_EXPECTATIONS.md ├── governance ├── COMMUNITY_BOARD_SEAT_EXPECTATIONS.md ├── GITHUB_ORG_MANAGEMENT_POLICY.md ├── GOVERNANCE.md ├── IP_POLICY_GUIDANCE.md └── transfer-repo-into-org.md ├── meetings ├── 2018 │ ├── 2018-10-13.md │ ├── 2018-10-22.md │ ├── 2018-10-29.md │ ├── 2018-11-05.md │ ├── 2018-11-12.md │ ├── 2018-11-19.md │ ├── 2018-11-26.md │ ├── 2018-12-03.md │ ├── 2018-12-10.md │ └── 2018-12-17.md ├── 2019 │ ├── 2019-01-07.md │ ├── 2019-01-14.md │ ├── 2019-01-21.md │ ├── 2019-01-28.md │ ├── 2019-02-04.md │ ├── 2019-02-11.md │ ├── 2019-02-25.md │ ├── 2019-03-04.md │ ├── 2019-03-18.md │ ├── 2019-03-25.md │ ├── 2019-04-01.md │ ├── 2019-04-08.md │ ├── 2019-04-15.md │ ├── 2019-04-22.md │ ├── 2019-04-29.md │ ├── 2019-05-06.md │ ├── 2019-05-13.md │ ├── 2019-05-20.md │ ├── 2019-06-10.md │ ├── 2019-06-19.md │ ├── 2019-06-26.md │ ├── 2019-07-03.md │ ├── 2019-07-10.md │ ├── 2019-07-17.md │ ├── 2019-07-23.md │ ├── 2019-07-30.md │ ├── 2019-08-06.md │ ├── 2019-08-13.md │ ├── 2019-08-20.md │ ├── 2019-08-27.md │ ├── 2019-09-03.md │ ├── 2019-09-10.md │ ├── 2019-09-17.md │ ├── 2019-09-24.md │ ├── 2019-10-01.md │ ├── 2019-10-08.md │ ├── 2019-10-15.md │ ├── 2019-10-22.md │ ├── 2019-10-29.md │ ├── 2019-11-05.md │ ├── 2019-11-12.md │ ├── 2019-11-19.md │ ├── 2019-11-26.md │ ├── 2019-12-03.md │ └── 2019-12-17.md ├── 2020 │ ├── 2020-01-07.md │ ├── 2020-01-14.md │ ├── 2020-01-21.md │ ├── 2020-01-28.md │ ├── 2020-02-04.md │ ├── 2020-02-11.md │ ├── 2020-02-18.md │ ├── 2020-02-25.md │ ├── 2020-03-03.md │ ├── 2020-03-10.md │ ├── 2020-03-17.md │ ├── 2020-03-24.md │ ├── 2020-03-31.md │ ├── 2020-04-07.md │ ├── 2020-04-14.md │ ├── 2020-04-21.md │ ├── 2020-04-28.md │ ├── 2020-05-05.md │ ├── 2020-05-12.md │ ├── 2020-05-19.md │ ├── 2020-05-26.md │ ├── 2020-06-02.md │ ├── 2020-06-09.md │ ├── 2020-06-16.md │ ├── 2020-06-30.md │ ├── 2020-07-07.md │ ├── 2020-07-14.md │ ├── 2020-07-21.md │ ├── 2020-07-28.md │ ├── 2020-08-04.md │ ├── 2020-08-11.md │ ├── 2020-08-18.md │ ├── 2020-08-25.md │ ├── 2020-09-01.md │ ├── 2020-09-08.md │ ├── 2020-09-15.md │ ├── 2020-09-22.md │ ├── 2020-09-29.md │ ├── 2020-10-06.md │ ├── 2020-10-13.md │ ├── 2020-10-20.md │ ├── 2020-10-27.md │ ├── 2020-11-03.md │ ├── 2020-11-10.md │ ├── 2020-11-17.md │ ├── 2020-12-01.md │ ├── 2020-12-08.md │ └── 2020-12-15.md ├── 2021 │ ├── 2021-01-05.md │ ├── 2021-01-19.md │ ├── 2021-02-02.md │ ├── 2021-02-16.md │ ├── 2021-03-02.md │ ├── 2021-03-16.md │ ├── 2021-03-30.md │ ├── 2021-04-13.md │ ├── 2021-04-27.md │ ├── 2021-05-11.md │ ├── 2021-05-25.md │ ├── 2021-06-08.md │ ├── 2021-06-22.md │ ├── 2021-07-06.md │ ├── 2021-07-20.md │ ├── 2021-08-03.md │ ├── 2021-08-17.md │ ├── 2021-08-31.md │ ├── 2021-09-14.md │ ├── 2021-10-12.md │ ├── 2021-10-26.md │ ├── 2021-11-09.md │ ├── 2021-11-23.md │ └── 2021-12-07.md ├── 2022 │ ├── 2022-01-04.md │ ├── 2022-01-18.md │ ├── 2022-02-01.md │ ├── 2022-02-15.md │ ├── 2022-03-01.md │ ├── 2022-03-15.md │ ├── 2022-03-29.md │ ├── 2022-04-12.md │ ├── 2022-04-26.md │ ├── 2022-05-10.md │ ├── 2022-05-24.md │ ├── 2022-06-21.md │ ├── 2022-07-05.md │ ├── 2022-07-19.md │ ├── 2022-08-02.md │ ├── 2022-08-30.md │ ├── 2022-09-13.md │ ├── 2022-09-27.md │ ├── 2022-10-11.md │ ├── 2022-10-25.md │ ├── 2022-11-08.md │ └── 2022-11-22.md ├── 2023 │ ├── 2023-01-03.md │ ├── 2023-01-17.md │ ├── 2023-01-31.md │ ├── 2023-02-14.md │ ├── 2023-03-14.md │ ├── 2023-03-28.md │ ├── 2023-04-11.md │ ├── 2023-04-25.md │ ├── 2023-05-23.md │ ├── 2023-06-06.md │ ├── 2023-06-20.md │ ├── 2023-07-11.md │ ├── 2023-07-25.md │ ├── 2023-08-08.md │ ├── 2023-08-22.md │ ├── 2023-10-03.md │ ├── 2023-10-17.md │ ├── 2023-10-31.md │ ├── 2023-11-28.md │ └── 2023-12-12.md ├── 2024 │ ├── 2024-01-09.md │ ├── 2024-01-23.md │ ├── 2024-02-20.md │ ├── 2024-03-05.md │ ├── 2024-03-19.md │ ├── 2024-04-02.md │ ├── 2024-04-16.md │ ├── 2024-04-30.md │ ├── 2024-05-14.md │ ├── 2024-05-28.md │ ├── 2024-06-11.md │ ├── 2024-06-25.md │ ├── 2024-07-09.md │ ├── 2024-07-23.md │ ├── 2024-08-06.md │ ├── 2024-08-20.md │ ├── 2024-09-03.md │ ├── 2024-09-17.md │ ├── 2024-10-01.md │ ├── 2024-10-15.md │ ├── 2024-10-29.md │ ├── 2024-11-12.md │ └── 2024-12-10.md ├── 2025 │ ├── 2025-01-07.md │ ├── 2025-01-21.md │ ├── 2025-02-04.md │ ├── 2025-02-18.md │ ├── 2025-03-04.md │ ├── 2025-03-18.md │ └── 2025-05-27.md └── breakout_meetings │ ├── 2019-01-14-project-progression.md │ └── 2020-02-12-code-of-conduct.md ├── mentorship ├── 2020 │ └── google-season-of-docs │ │ └── README.md └── 2024 │ └── google-season-of-docs │ ├── README.md │ └── node-2024-learn-proposal.md ├── package-lock.json ├── package.json └── project-resources ├── ESP ├── ECOSYSTEM_SUSTAINABILITY_PROGRAM.md ├── esp-herodevs-angular.png ├── esp-herodevs-node.png └── esp-herodevs-vue.png ├── GITHUB_REQUESTS ├── 2023.md └── README.md ├── INFRASTRUCTURE_MENU.md ├── PROJECT_FUND.md ├── PROJECT_FUND ├── 2023.md └── README.md ├── REQUESTING_GITHUB_RESOURCES.md ├── community-health-files-guide.md ├── github-continuity-policy.md ├── openjsf-marketing-services.pdf ├── project-directed-funding-policy.md └── requesting_LFIT_support.md /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Report a Code of Conduct violation 4 | url: https://code-of-conduct.openjsf.org/ 5 | about: "Do you want to report a Code of Conduct violation?" 6 | - name: Legal Help 7 | url: https://github.com/openjs-foundation/cross-project-council#help-with-legal-questions-for-existing-projects-only 8 | about: "Do you need help with legal matters concerning an OpenJSF project?" 9 | - name: Infrastructure Request 10 | url: https://github.com/openjs-foundation/cross-project-council#help-with-project-infrastructure 11 | about: "Do you want to request infrastructure resources for your OpenJSF project?" 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/regular-issue.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Generic issue 3 | about: Open a generic issue for the OpenJSF CPC 4 | --- 5 | -------------------------------------------------------------------------------- /.github/workflows/link-checker.yml: -------------------------------------------------------------------------------- 1 | on: 2 | schedule: 3 | - cron: "0 0 * * 1" 4 | workflow_dispatch: 5 | name: Link Checker 6 | jobs: 7 | linkinator: 8 | runs-on: ubuntu-latest 9 | steps: 10 | - uses: actions/checkout@v3 11 | - uses: JustinBeckwith/linkinator-action@v1 12 | with: 13 | paths: "**/*.md" 14 | markdown: true 15 | retry: true 16 | linksToSkip: "https://github.com/openjs-foundation/directory-private, https://twitter.com/*, https://opensource.org/licenses/*" 17 | urlRewriteSearch: "https://github.com/openjs-foundation/cross-project-council/blob/HEAD/" 18 | urlRewriteReplace: "" 19 | -------------------------------------------------------------------------------- /.github/workflows/linter-workflow.yml: -------------------------------------------------------------------------------- 1 | name: Doc Linter 2 | 3 | on: [pull_request] 4 | 5 | jobs: 6 | doc-lint: 7 | 8 | runs-on: ubuntu-latest 9 | 10 | steps: 11 | - uses: actions/checkout@v3 12 | 13 | - name: Use Node.js 18.x 14 | uses: actions/setup-node@v3 15 | with: 16 | node-version: 18 17 | check-latest: true 18 | 19 | - name: npm install 20 | run: npm ci 21 | 22 | - name: run linter 23 | run: npm test 24 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | -------------------------------------------------------------------------------- /.remarkrc: -------------------------------------------------------------------------------- 1 | { 2 | "plugins": [ 3 | "remark-preset-lint-recommended", 4 | ["remark-lint-list-item-indent", false], 5 | ["remark-lint-list-item-bullet-indent", false], 6 | ["remark-lint-no-literal-urls", false], 7 | ["remark-lint-no-shortcut-reference-link", false], 8 | ["remark-lint-no-auto-link-without-protocol", false], 9 | ["remark-lint-no-undefined-references", false] 10 | ] 11 | } 12 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: node_js 2 | node_js: 3 | - 10 4 | script: 5 | - npm run lint-md 6 | -------------------------------------------------------------------------------- /CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @openjs-foundation/cpc 2 | -------------------------------------------------------------------------------- /Dates-and-Reminders.md: -------------------------------------------------------------------------------- 1 | # Dates and Reminders 2 | 3 | This document captures important dates and reminders. 4 | 5 | ## Elections Calendar 6 | 7 | Position | Term Length | Nomination Period | Voting Period | Term Start/End 8 | -- | -- | -- | -- | -- 9 | CPC Directors (3) | 1 Year | April: 1st & 2nd Week | April: 3rd week | May 1 10 | CPC Impact representative selection (2 per project) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 11 | CPC At Large voting members (2) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 12 | CPC Regular voting members (2) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 13 | 14 | Position | Term Length | Nomination Period | Voting Period | Term Start/End 15 | -- | -- | -- | -- | -- 16 | CPC Chair | 1 Year | Nov: 1st Week | Nov: 2nd Week | Nov 15 17 | CPC Vice Chair | 1 Year | Nov: 1st Week | Nov: 2nd Week | Nov 15 18 | 19 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | MIT License (MIT) 2 | 3 | Copyright (c) OpenJS Foundation and contributors. All rights reserved. 4 | Copyright (c) Node.js contributors. All rights reserved. 5 | 6 | Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 7 | 8 | The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. 9 | 10 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE 11 | -------------------------------------------------------------------------------- /NEW_PROJECT_APPLICATION.md: -------------------------------------------------------------------------------- 1 | # ${Project Name} 2 | 3 | ## Applicant 4 | 5 | Who is the main point of contact during the application process? 6 | 7 | ## Description 8 | 9 | A rough description of the project in less than 100 words. 10 | 11 | ## Reason for Applying 12 | 13 | A short description of the reasons why your project is applying to join the foundation, and your expectations from the foundation. 14 | Please keep your answer to less than 100 words. 15 | 16 | ## Statement of alignment with OpenJS Foundation charter and mission 17 | 18 | Please refer to [the Cross Project Council's Charter](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md). 19 | Please keep your answer to less than 250 words. 20 | 21 | ## Impact and users of the project 22 | - What is the ecosystem impact of the project? 23 | - Who are the biggest users of the project? (_if they are not JavaScript space, then will it ever expand to JavaScript space_) 24 | - What is the potential long term impact and adoption? 25 | - How does it differ from other projects? 26 | 27 | ## Desired Initial Project Phase 28 | 29 | Please refer to [Section III, Stages - Definitions & Expectations](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_PROGRESSION.md#iii-stages---definitions--expectations) of PROJECT_PROGRESSION.md. 30 | 31 | At Large / Impact 32 | 33 | ## Project Website 34 | 35 | Include link 36 | 37 | ## Social Media Accounts 38 | 39 | Links to social media accounts 40 | 41 | ## Official Communication Channels 42 | 43 | List current channels e.g.: Slack / IRC / Mailing lists 44 | 45 | ## Security Policy 46 | 47 | Link to security policy for the project, if applicable. 48 | 49 | ## Governance Structure 50 | 51 | * Is there a leadership team? 52 | * Who are the members of the leadership team? 53 | * How are members of the leadership team nominated? 54 | * How are individuals outside of leadership given commit access? 55 | * Is the project open/willing to move to open governance, if not already in place? 56 | * Is the project willing to adopt the OpenJS Foundation Code of Conduct (CoC)? 57 | * Please share links to all existing documentation e.g. GOVERNANCE.md / CONTRIBUTING.md 58 | 59 | ## List of all repos that are part of the project 60 | 61 | For each repository, please provide: 62 | 63 | - link to repo, 64 | - license information, 65 | - who owns the Intellectual Property (IP), 66 | - link to issue tracker, 67 | - link to code of conduct (CoC), 68 | - optionally, the full list of vendored dependencies contained in the source tree, including license information. 69 | A full audit of all vendored dependencies will be required before your project can officially join the foundation, but this can be done later with foundation support. 70 | 71 | ## Existing Financial Sponsorship 72 | 73 | Does your project currently receive funds? Who do they come from and what are the funds used for? 74 | 75 | ## Infrastructure Needs or Requests 76 | 77 | What needs will your project have from the foundation? Feel free to provide a list. 78 | 79 | ## Questions? 80 | 81 | What questions do you have? What questions might arise during your application? 82 | -------------------------------------------------------------------------------- /PROJECT_SECURITY_REPORTING.md: -------------------------------------------------------------------------------- 1 | # Minimum security reporting requirements for OpenJS Foundation projects 2 | 3 | ## Security policy 4 | 5 | Each OpenJS Foundation project must publish a security policy in an easily accessible place. The recommended approach is to [publish the security policy in each GitHub repository](https://help.github.com/en/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository). 6 | 7 | Projects that have their own organization on GitHub are advised to place the `SECURITY.md` file in the `.github` repository for the organization. 8 | 9 | ## Reporting 10 | 11 | Project security policy should explain how to confidentially report a security vulnerability. 12 | 13 | Each project should support at least one security reporting channel. Common ways of accepting vulnerability reports are: 14 | 15 | 1. Designated email address, e.g. `security@example.com`. 16 | 1. Vulnerability disclosure program, e.g. hosted on platform such as [HackerOne](https://www.hackerone.com/product/community) or similar. 17 | 18 | Projects that have their own reporting channels are encouraged to continue using them and document it in the security policy. 19 | -------------------------------------------------------------------------------- /collaboration-spaces/COLLABORATION_NETWORK.md: -------------------------------------------------------------------------------- 1 | # The OpenJS Collaboration Network 2 | 3 | The formation of the OpenJS Foundation was in support of a number of goals. 4 | The first was to support JavaScript projects, providing a neutral place for people to collaborate and resources needed by those projects (legal, marketing, best practices governance support, infra, etc.). 5 | 6 | The second goal was to foster greater collaboration in the JavaScript ecosystem. 7 | Bringing projects together in a single Foundation provides an easier path to collaboration between projects. 8 | 9 | The OpenJS Collaboration network provides the framework for people to collaborate on areas of importance to the JavaScript ecosystem in a neutral space. 10 | In some cases, this may align with projects and in other cases be independent of the member projects. 11 | Regardless of the alignment with existing member projects, the OpenJS Foundation Collaboration Network provides support for collaboration in a particular area. 12 | Support includes but not be limited to: 13 | * a repo in the OpenJS org 14 | * marketing support 15 | * mailing lists 16 | * slack channels 17 | * representation on the CPC 18 | 19 | The current Collaboration Networks spaces are listed in the main README.md in the CPC repository. 20 | 21 | The [Collaboration Space Progression](./COLLABORATION_SPACE_PROGRESSION.md) document explains how a proposal for a new Collaboration space may be submitted and how Collaboration spaces move between stages. 22 | 23 | ## Authority Delegation 24 | 25 | The Cross Project Council (CPC) may delegate scoped authority to a collaboration space. In such cases, the collaboration space may formally represent the Foundation, for example in a standards organization. 26 | 27 | Collaboration Spaces to which the CPC delegates authority are listed below: 28 | 29 | ### Standards Collaboration Space 30 | 31 | The purpose of the Standards Collaboration Space is to act as a facilitator for OpenJS Foundation projects to support their engagement in various Standards Organizations, Working Groups, Technical Committees, and other spaces where internationally recognized standards are collaborated upon. 32 | 33 | Responsibilities include: 34 | 35 | * approve and support OpenJS Foundation project contributors in attending meetings held by standards organizations 36 | * make OpenJS Foundation project contributors aware of developments in relevant standards 37 | * help OpenJS Foundation projects formulate a standards strategy 38 | * support new contributors to standards-making activities 39 | * mentor project contributors who are unfamiliar with standards-making processes 40 | * make recommendations to the Cross Project Council regarding standards organization membership 41 | * managing ongoing relationships with standards organizations 42 | * ensuring that OpenJS representatives are aware of the responsibility of being a delegate of the foundation as outlined in [the membership expectations](https://github.com/openjs-foundation/standards/blob/HEAD/MEMBER_EXPECTATIONS.md) 43 | * facilitate when different projects' needs conflict 44 | -------------------------------------------------------------------------------- /collaboration-spaces/NEW_COLLABORATION_SPACE_APPLICATION.md: -------------------------------------------------------------------------------- 1 | # ${Collaboration Space Name} 2 | 3 | ## Champion and Participants 4 | 5 | Who is the champion proposing the Collaboration Space ? 6 | 7 | ## Initial participants 8 | 9 | Please provide a list of initial participants and their background/knowledge of the space proposed. 10 | 11 | ## Description 12 | 13 | Please provide a rough description of the collaboration space in less than 100 words and the goals that you hope to achieve. 14 | 15 | ## Impact and users of the project 16 | 17 | Why is the proposed area/topic important to the JavaScript Ecosystem? 18 | 19 | ## Resources 20 | 21 | Which [resources](./COLLABORATION_SPACE_PROGRESSION.md#expectations) would the space need from those listed as available to Collaboration spaces? 22 | 23 | ## Existing assets 24 | 25 | Are there an existing assets, documentation etc. that would be transferred into a Foundation repo upon formation of the Collaboration space? 26 | 27 | ## Questions? 28 | 29 | What questions do you have? What questions might arise during your application? 30 | -------------------------------------------------------------------------------- /conduct/COC_PROCESS_FOR_INCIDENT_MANAGEMENT.md: -------------------------------------------------------------------------------- 1 | This document defines how the OpenJS Foundation implements its code of conduct. 2 | 3 | If you want to report an incident, go to [code-of-conduct.openjsf.org][CoC]. 4 | 5 | *** 6 | 7 | The CPC will be updating these processes shortly. Progress is tracked in [Issue #1256](https://github.com/openjs-foundation/cross-project-council/issues/1256). 8 | 9 | In the meantime, the previous code of conduct incident management processes can be found [here](https://github.com/openjs-foundation/cross-project-council/blob/cf85fee1411de2c06632d83a9e4876fa8eeb0787/conduct/HANDLING_CODE_OF_CONDUCT_REPORTS.md). 10 | 11 | [CoC]: https://code-of-conduct.openjsf.org/ 12 | -------------------------------------------------------------------------------- /conduct/MEMBER_EXPECTATIONS.md: -------------------------------------------------------------------------------- 1 | All participants in the OpenJS Foundation projects and groups must follow the 2 | [Code of Conduct][]. There are further expectations for 3 | members of leadership teams including the 4 | [CPC](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CPC-CHARTER.md). 5 | 6 | It is understood that members will have individual opinions and will express their individual opinions during discussions within the organization. 7 | All contributors are expected to be respectful of these different viewpoints, and to work collaboratively with one another in a manner that constructively elevates all contributors. 8 | If a member has an objection or dissent they should express it as early as possible to ensure there is ample time to discuss and reach consensus. 9 | 10 | When decisions are made within the established guidelines and policies of the OpenJS Foundation projects or groups, those in leadership roles have a responsibility to uphold and respect the decision even if they disagree with it. 11 | This is especially important in external communications, for example in social media. 12 | Should the member be unwilling or unable to do so, then they should resign their leadership position. 13 | This does not mean that decisions cannot be revisited and discussed within the team at a later time. 14 | 15 | Members of our leadership groups must also conduct themselves in a professional and respectful manner. Some general guidelines include: 16 | 17 | - Remediate quickly when you realize you made a mistake. Leaders are human, and they will make mistakes. 18 | However they should act swiftly to acknowledge mistakes and correct them. 19 | - Aim to remediate first and then discuss. 20 | If other members of the team express concerns about actions, acknowledge their concerns by stopping the actions in question and then discuss within the team to come to a common agreement. 21 | - Treat all community members with respect, consideration, and highest standards of ethical conduct. 22 | - Value a diversity of views and opinions. 23 | Avoid preferential treatment, and hold everyone (including ourselves) accountable to the same set of standards. 24 | Everyone gets to speak up. 25 | - Deal with issues directly with the person in question. 26 | Resist complaining about others in the OpenJS Foundation projects or team in a public sphere. 27 | - Build trust by keeping your promises. 28 | - Be the model of accountability and leadership. 29 | 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 | - Criticize ideas rather than people, discussing any concerns in person whenever possible, and taking responsibility for our statements. 32 | 33 | While the guidelines above focus primarily on the spaces where we participate in official OpenJS Foundation work (GitHub, IRC, meetings, conferences), it is important to recognize that the public behavior of members also reflects on the OpenJS Foundation projects and groups. 34 | 35 | If you're interested in an introduction to diversity, inclusion, and unconscious bias, [try this free training offered by our partners at the Linux Foundation](https://training.linuxfoundation.org/training/inclusive-speaker-orientation/). 36 | 37 | If it appears that any member of the leadership groups are acting outside of the expectations set above please refer to our [Code of Conduct][] policy which outlines the process of making an official complaint. 38 | 39 | This policy, and changes to it, are not retroactive. 40 | 41 | [Code of Conduct]: https://code-of-conduct.openjsf.org/ 42 | 43 | -------------------------------------------------------------------------------- /governance/transfer-repo-into-org.md: -------------------------------------------------------------------------------- 1 | # Transferring an existing repository into the organization 2 | 3 | ## Step 1. Get the repository ready 4 | 5 | Ideally, the repository should have the following documents in place: 6 | 7 | - `CODE_OF_CONDUCT.md`: it can be a reference to [the OpenJS Foundation's Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md). 8 | - `CONTRIBUTING.md`: if there isn't one already, [the contributing guide][] of Node.js core could be a good example. Consider including the Developer's Certificate of Origin section in the document to avoid potential copyright conflicts. 9 | - `LICENSE`, or other kind of documents that describe the license of the project. 10 | - `README.md` 11 | 12 | ## Step 2. Open an issue in the cross-project-council repository 13 | 14 | _The person opening the issue should be a member of the Cross Project Council so they can ping the relevant GitHub teams to discuss the request. 15 | If the person who wants to initiate the request is not a member, they could ask an existing member to open the issue._ 16 | 17 | Go to [the issue tracker of the Cross Project Council repository][], open an issue to request moving the repository into the organization. The issue should include: 18 | 19 | - The owner and the name of the repository, and a link to it. 20 | - What the repository is for, why it should be transferred into the organization. 21 | - Mention `@openjs-foundation/cpc` so the Cross Project Council members can be notified about the request and weigh in. 22 | 23 | See the [OpenJS Foundation GitHub Organization Management Policy][] on how the request is approved. 24 | 25 | ## Step 3. Transfer the repository 26 | 27 | When the request is approved, the owner of the repository can start transferring the repository into the OpenJS GitHub organization. 28 | The person can be made a member of the OpenJS GitHub organization so they have the necessary permissions to complete the transfer. 29 | 30 | See [GitHub's documentation on transferring repos][] on how to perform the necessary actions. 31 | 32 | 33 | [GitHub's documentation on transferring repos]: https://help.github.com/articles/about-repository-transfers/ 34 | [OpenJS Foundation GitHub Organization Management Policy]: https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/GITHUB_ORG_MANAGEMENT_POLICY.md 35 | [the contributing guide]: https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md 36 | [the issue tracker of the Cross Project Council repository]: https://github.com/openjs-foundation/cross-project-council/issues 37 | -------------------------------------------------------------------------------- /meetings/2018/2018-11-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Bootstrap Team Meeting 2018-11-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=dIRyJ2nzYCY 6 | * **GitHub Issue**: https://github.com/nodejs/bootstrap/issues/34 7 | 8 | ## Present 9 | 10 | - Myles Borins (@MylesBorins) 11 | - Mike Dolan (@mkdolan) 12 | - Jory Burson (@jorydotcom) 13 | - Adam Miller (@amiller-gh) 14 | - Tracy Hinds (@hackygolucky) 15 | - Bruce MacNaughton (@bmacnaughton) 16 | - Abraham Jr. Agiri (@codeekage) 17 | - Michael Dawson (@mhdawson) 18 | - Brian Warner (@brianwarner) 19 | - Sakthipriyan Vairamani (@thefourtheye) 20 | 21 | ## Agenda 22 | 23 | Extracted from **bootstrap-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | ### Approving PRs (3 minute timebox) 26 | 27 | * Draft Staging Process [#23](https://github.com/nodejs/bootstrap/pull/23) 28 | - 3 minute timebox 29 | - Jory introduced the process and noted that it can be simplified as necessary. 30 | - Myles proposes moving forward once grammatical changes are landed 31 | - Myles takes action to land 32 | 33 | ### Stage Advancement (3 minute timebox) 34 | 35 | * Governance stage 1 [#32](https://github.com/nodejs/bootstrap/pull/32) 36 | - 3 minute timebox 37 | - Proposal to move governance from stage 0 to stage 1 38 | - We have a general idea of how we’re doing it, but don’t need consensus on exact wording 39 | - Myles takes action to land 40 | 41 | ## Update on progress (4 minute timebox) 42 | 43 | * First Pass at Bootstrap Process [#7](https://github.com/nodejs/bootstrap/pull/7) 44 | - 2 minute timebox 45 | - Adam will close current PR. 46 | - New PR to be opened by Adam on the README with the current contents migrated 47 | * Create expectations for foundation draft [#6](https://github.com/nodejs/bootstrap/pull/6) 48 | - 2 minute timebox 49 | - Open question: At what point do we consider the proposals firm enough to start getting feedback from lawyers and board members? 50 | - Open question: How do we ensure that budget responsibility is sufficiently consolidated to ensure that all required actions are taken throughout the year? (establishing budget, ensuring project execution, etc) 51 | - Tracy takes action to incorporate TSC and CommComm’s expectations of the board and the executive committee into PR 52 | 53 | ### Discussion (45 minute timebox) 54 | 55 | * How often / when do we meet? [#21](https://github.com/nodejs/bootstrap/issues/21) 56 | - 2 minute timebox 57 | - Action to revisit in next meeting to find a time that works for Asia, Africa, and Europe, as well as EST and PST 58 | * Drafting initial governance for merged foundation [#33](https://github.com/nodejs/bootstrap/issues/33) 59 | - 40 minute timebox 60 | - Mike D takes action to make governance document public 61 | - Decision to retain name of “Cross Project Council” 62 | - Open question: How will the community be represented? Multiple representation structures have been proposed, this likely merits being broken out into a separate thread. 63 | - Suggestion: begin with the individual membership proposal and modify as necessary. 64 | - Tracy takes action to start a new thread about individual representation 65 | 66 | -------------------------------------------------------------------------------- /meetings/2019/2019-04-08.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Bootstrap Team Meeting 2019-04-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Td3s94nFRK8 6 | * **GitHub Issue**: https://github.com/openjs-foundation/bootstrap/issues/150 7 | 8 | ## Present 9 | 10 | 11 | * Rich Trott (@Trott) 12 | * Michael Dawson (@mhdawson) 13 | * Mike Dolan 14 | * George Adams (@gdams) 15 | * Joe Sepi (@joesepi) 16 | * Manil Chowdhury (@keywordnew) 17 | * Russ Schlossbach 18 | * Kris Borchers (@kborchers) 19 | * Christian Bromann (@bromann) 20 | * Steven Ayr 21 | * Brian Warner 22 | * Hassan Sani (@inidaname) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | *Extracted from **bootstrap-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 29 | 30 | * no announcements this week. 31 | 32 | ### openjs-foundation/bootstrap 33 | 34 | * OpenJS Foundation Executive Director Job Description [#151](https://github.com/openjs-foundation/bootstrap/issues/151) 35 | * Brian: Updated from past version, wanted to get community feedback. 36 | * Have a few people who have indicated they are interested so would like to get it out to 37 | see if there are others 38 | * Worked through a number of the comments that are being discussed in github. 39 | 40 | * Infrastructure: Mailing lists [#134](https://github.com/openjs-foundation/bootstrap/issues/134) 41 | * Brian having been working on getting pieces in place 42 | * Current lists: 43 | * announce@ 44 | * report@ 45 | * coc-escalation@ 46 | * projects@ 47 | * cpc-private@ 48 | * Also created announcement list for key interested parties in the project. Once get list 49 | of current people that she is emailing. 50 | 51 | * Create process for new projects joining foundation [#130](https://github.com/openjs-foundation/bootstrap/issues/130) 52 | * no updates in the issues, and Myles could not make it this week so defer to next week. 53 | 54 | * Review meeting times [#129](https://github.com/openjs-foundation/bootstrap/issues/129) 55 | * Spreadsheet created, but only 3 people have filled in entries, please go fill out. 56 | https://docs.google.com/spreadsheets/d/12e8lN9ywi-2kAtcW08WS3x3S-6TXiOO8_yxs3j0Sm2E/edit#gid=553742071 57 | 58 | * Project Housekeeping: Create Checklist for New Projects / Updating Existing Projects [#121](https://github.com/openjs-foundation/bootstrap/issues/121) 59 | * Agreed PR is ready to land. Michael will take action to land later today. 60 | 61 | * Steps to bootstrap CPC and new Foundation [#115](https://github.com/openjs-foundation/bootstrap/issues/115) 62 | * Good progress on email lists as discussed earlier 63 | * Have confirmed initial impact projects, Michael will land update for express and then 64 | it’s done 65 | * Youtube is setup, don’t have credentials yet 66 | * Chasing down zoom accounts, should. 67 | * Checklists for projects, looks complete no objections to landing, can be updated later 68 | if needed. 69 | * Work to identify initial CPC representatives. Jory opened issues to ping the projects other 70 | than Node.js to help identify reps. Michael will try to push forward issue in Node.js org 71 | to agree on process for electing Node.js reps. 72 | * Manil - based on discussion on report alias is used. Would be good to have a process 73 | written down. Manil can put something together. 74 | 75 | ## Q&A, Other 76 | 77 | ## Upcoming Meetings 78 | 79 | * **Calendar**: https://nodejs.org/calendar 80 | 81 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 82 | 83 | 84 | -------------------------------------------------------------------------------- /meetings/2019/2019-04-15.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Bootstrap Team Meeting 2019-04-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/rhqT6euwGr0 6 | * **GitHub Issue**: https://github.com/openjs-foundation/bootstrap/issues/154 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Matteo Collina (@mcollina) 12 | * Jory Burson (@jorydotcom) 13 | * Tierney Cyren (@bnb) 14 | * Eemeli Aro (@eemeli) 15 | * Jonah Stiennon (@jonahss) 16 | * Brian Warner (@brianwarner) 17 | * Tracy Hinds (@hackygolucky) 18 | * Mike Dolan (@mkdolan) 19 | * Todd Moore (@tmmoore_1) 20 | * Myles Borrins (@MylesBorins) 21 | * Sarah Novotny (@sarahnovotny) 22 | * Russ Schlossbach 23 | * Nick O’Leary (@knolleary) 24 | * Rich Trott (@Trott) 25 | * Kris Borchers (@kborchers) 26 | * Hassan Sani (@inidaname) 27 | * Joe Sepi (@joesepi) 28 | 29 | ## Agenda 30 | 31 | ### Announcements 32 | 33 | *Extracted from **bootstrap-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 34 | 35 | ### openjs-foundation/bootstrap 36 | 37 | * OpenJS Foundation Executive Director Job Description [#151](https://github.com/openjs-foundation/bootstrap/issues/151) 38 | * When the job posting is live we should open a new issue for visibility 39 | * agreed to close issue. 40 | 41 | * Infrastructure: Mailing lists [#134](https://github.com/openjs-foundation/bootstrap/issues/134) 42 | * List are created and populated with initial lists 43 | * Michael: should have doc that describes how to request changes and create new mailing 44 | Lists. Requests can be emailed to Brian Warner (but the better alias to use is 45 | operations@openjsf.org) 46 | 47 | * Myles: process should have waiting period so people can comment or object (ex: we use 48 | something like 48 hours in the Node.js project for something similar) 49 | * Myles, we should probably create an Admin repo, put doc on email list as well as 50 | code of conduct as well. No objections. 51 | * Remove label and we’ll close once the doc lands 52 | 53 | * Create process for new projects joining foundation [#130](https://github.com/openjs-foundation/bootstrap/issues/130) 54 | * Myles has not had a chance, should have time this week 55 | * Main challenge is probably around culture fit, good to have process where that is 56 | identified early so that can be communicated before the request to join is public. 57 | * Todd, Apache foundation has blackout period 58 | * Eemeli: If requirements have not been finalized, have all existing JSF projects been 59 | grandfathered? 60 | * Myles, once set current projects would adopt over time, believe projects will be 61 | able to meet them. 62 | * Next step is for Myles to write first draft of doc. 63 | 64 | * Review meeting times [#129](https://github.com/openjs-foundation/bootstrap/issues/129) 65 | * We have spreadsheet to try and get times that are good for people 66 | * So far 6 people have filled it in. 67 | * Set May 1 as target to review to line up with target for having CPC representatives 68 | Identified. 69 | 70 | * Project Housekeeping: Create Checklist for New Projects / Updating Existing Projects [#121](https://github.com/openjs-foundation/bootstrap/issues/121) 71 | * PR landed, agreed we can close the issue. 72 | 73 | * Steps to bootstrap CPC and new Foundation [#115](https://github.com/openjs-foundation/bootstrap/issues/115) 74 | 75 | 76 | 77 | ## Q&A, Other 78 | 79 | ## Upcoming Meetings 80 | 81 | * **Calendar**: https://nodejs.org/calendar 82 | 83 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 84 | 85 | 86 | -------------------------------------------------------------------------------- /meetings/2019/2019-04-22.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Bootstrap Team Meeting 2019-04-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=zDRcub95L2o 6 | * **GitHub Issue**: https://github.com/openjs-foundation/bootstrap/issues/157 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Manil Chowdhury (@keywordnew) 12 | * Jory Burson (@jorydotcom) 13 | * Mike Dolan (@mkdolan) 14 | * Russ Schlossbach 15 | * Ben Michel (@obensource) 16 | * Kris Borchers (@kborchers) 17 | * Tierney Cyren (@bnb) 18 | * Jonah Stiennon (@jonahss) 19 | * Anton Molleda (@molant) 20 | * Joe Sepi (@joesepi) 21 | * Myles Borins (@MylesBorins) 22 | * Steven Ayr (@stevenayr) 23 | * Dave Methvin (@dmethvin) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | 29 | *Extracted from **bootstrap-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 30 | 31 | ### openjs-foundation/bootstrap 32 | 33 | * Voting CPC Representatives from Projects [#152](https://github.com/openjs-foundation/bootstrap/issues/152) 34 | Update on where we are at with the selections from Impact projects & Growth + At Large nominees (Deadline is May 1) 35 | Update from Node on its selection process 36 | Discussion of Michael & Nick’s thinking around the elections 37 | How much time do we expect to take? We should try to make that clear 38 | 39 | * Create process for new projects joining foundation [#130](https://github.com/openjs-foundation/bootstrap/issues/130) 40 | * PR for stage zero proposal - https://github.com/openjs-foundation/bootstrap/pull/158 41 | * Myles to revise for next week 42 | 43 | * Review meeting times [#129](https://github.com/openjs-foundation/bootstrap/issues/129) 44 | * Sheet is more filled in now, deadline is May 1 45 | 46 | * Steps to bootstrap CPC and new Foundation [#115](https://github.com/openjs-foundation/bootstrap/issues/115) 47 | 48 | 49 | 50 | ## Q&A, Other 51 | 52 | ## Upcoming Meetings 53 | 54 | * **Calendar**: https://nodejs.org/calendar 55 | 56 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 57 | -------------------------------------------------------------------------------- /meetings/2019/2019-04-29.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Bootstrap Team Meeting 2019-04-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/VDMdPCRmkWA 6 | * **GitHub Issue**: https://github.com/openjs-foundation/bootstrap/issues/167 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Project Maintainers 11 | * OpenJS Foundation Board of Directors 12 | 13 | - Myles Borins (@MylesBorins) 14 | - Joe Sepi (@joesepi) 15 | - Kris Borchers (@kborchers) 16 | - Russ Schlossbach 17 | - Agiri Abraham 18 | - Sarah Novotny 19 | - Mike Dolan (@mkdolan) 20 | - Steven Ayr 21 | - Tierney Cyren 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | *Extracted from **bootstrap-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | 29 | ### openjs-foundation/bootstrap 30 | 31 | * Review new project board + Milestone for Bootstrapping the CPC [#164](https://github.com/openjs-foundation/bootstrap/issues/164) 32 | * Myles and Jory went through and filled out the project board 33 | * Currently at ~25% of complete for bootstrapping the CPC judging by the project board 34 | 35 | * proposal: new project application process [#158](https://github.com/openjs-foundation/bootstrap/pull/158) 36 | * Create process for new projects joining foundation [#130](https://github.com/openjs-foundation/bootstrap/issues/130) 37 | * two agenda items presented together (#158 was implementation of #130) 38 | * also goes with #165, which depends on #158 landing 39 | * #165 updates project progression to include #158 40 | * possible need to add a silent phase to the project progression 41 | 42 | * Voting CPC Representatives from Projects [#152](https://github.com/openjs-foundation/bootstrap/issues/152) 43 | * brief overview of the issue, as its tracking the progress 44 | 45 | * Review meeting times [#129](https://github.com/openjs-foundation/bootstrap/issues/129) 46 | * reminder to fill it out 47 | 48 | * Steps to bootstrap CPC and new Foundation [#115](https://github.com/openjs-foundation/bootstrap/issues/115) 49 | 50 | ## Q&A, Other 51 | 52 | ## Upcoming Meetings 53 | 54 | * **Calendar**: https://nodejs.org/calendar 55 | 56 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 57 | -------------------------------------------------------------------------------- /meetings/2019/2019-05-20.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-05-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=gU0H0x3RNks 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/180 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Anton Molleda (@molant) 12 | * Michael Dawson (@mhdawson) 13 | * Myles Borins (@MylesBorins) 14 | * Kris Borchers (@kborchers) 15 | * Ben Michel (@obensource) 16 | * Christian Bromann (@bromann) 17 | * Manil Chowdhury (@keywordnew) 18 | * Rachel Romoff (@rromoff) 19 | * Jory Burson (@jorydotcom) 20 | * Eemeli Aro (@eemeli) 21 | * Matteo Collina (@mcollina) 22 | * Agiri (@codeekage) 23 | * Rich Trott 24 | * Brian Kardell 25 | * Brian Warner (@brianwarner) 26 | * Hassan Sani (@inidaname) 27 | 28 | ## Agenda 29 | 30 | ### openjs-foundation/cross-project-council 31 | 32 | * Nominating Chair and Director [#179](https://github.com/openjs-foundation/cross-project-council/issues/179) 33 | 34 | Quick discussion of differences between the chair and the director roles 35 | Follow existing process from CommComm etc or new 36 | Self-nomination + consent to get nominated 37 | Existing governance says that the nominees must come from the pool of voting members 38 | Eemilio, would be good to meet people at Berlin first, defer until then? 39 | Myles, how about close nomination before but then have vote after. Close nominations on the 5th of June, election begins 5th, voting open until June 19th. Board meeting happens on June 21. 40 | Private versus public nomination. 41 | Alias: operations@openjsf.org (will forward to Brian) 42 | Brian to set up a nominations email alias and drop in issue. 43 | 44 | * Start accepting nominations for "regular" members [#178](https://github.com/openjs-foundation/cross-project-council/issues/178) 45 | * Matteo all people who have been part of bootstrap process should self-nominate 46 | * People submit PR as outlined in the governance, then voting member for project they are involved in validates through comment and then can land (for non-impact, non-impact voting members will validate) 47 | 48 | * New process for CPC reps to share responsibility for Travel Fund [#172](https://github.com/openjs-foundation/cross-project-council/issues/172) 49 | * Good discussion of options and some background. 50 | * Next step is that Matteo will write proposal for Summit travel fund and we’ll 51 | go from there. 52 | 53 | * Draft initial process for electing voting members from the non-impact projects. [#161](https://github.com/openjs-foundation/cross-project-council/issues/161) 54 | * Not pressing since we’ve agreed what to do for this year. 55 | * If anyone wants to start drafting, they are free to do so. 56 | 57 | * Review meeting times [#129](https://github.com/openjs-foundation/cross-project-council/issues/129) 58 | * Decision from last meeting was to discuss in person at the collab summit. 59 | 60 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 61 | 62 | 63 | -------------------------------------------------------------------------------- /meetings/2019/2019-07-03.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-07-03 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=rTMwRC4Vsiw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/243 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Kris Borchers (@kborchers) 12 | * Christian Bromann (@bromann) 13 | * Sendil Kumar (@sendilkumarn) 14 | * Even Stensberg (@evenstensberg) 15 | * Tierney Cyren (@bnb) 16 | * Brian Warner (@brianwarner) 17 | * Jonah Stiennon (@jonahss) 18 | * Timmy Willison (@timmywil) 19 | * Tracy Hinds (@hackygolucky) 20 | * Myles Borins (@MylesBorins) 21 | * Rachel Romoff (@rromoff) 22 | * Michael Dawson (@mhdawson) 23 | * Nick O’Leary (@knolleary) 24 | * Jory Burson (@jorydotcom) 25 | * Abraham Jr. Agiri (@codeekage) 26 | 27 | ## Agenda 28 | 29 | ### Announcements 30 | 31 | *Extracted from **cross-project-council-agenda** labelled issues and pull requests from the **openjs-foundation org** prior to the meeting. 32 | 33 | ### openjs-foundation/cross-project-council 34 | 35 | * email address for the voting members [#236](https://github.com/openjs-foundation/cross-project-council/issues/236) 36 | * Jory: for now projects email list should be ok. But need private thread for voting 37 | members. 38 | * Chris, may be people on the projects who are not members of CPC. Feel 39 | it may not be a great place to post cpc stuff, was meant to be for project 40 | Maintainers, believe there should be a separate email for private stuff. 41 | * Joe, not sure what would be on email as general CPC stuff should be public 42 | anyway. 43 | * Myles +1, should be using issues 44 | * Agreed we don’t need one for regular members, issue closed. 45 | 46 | * Who can be an Observer? [#234](https://github.com/openjs-foundation/cross-project-council/issues/234) 47 | * Discussed in last meeting, and issue was closed. 48 | * Re-opened until we close out next step which is to create PR, Jory or 49 | Joe will create PR to clarify in governance. 50 | 51 | * proposal: move new projects to stage 2 [#229](https://github.com/openjs-foundation/cross-project-council/pull/229) 52 | * Joe looks like it is ready to land. 53 | 54 | * Approve charter changes for Node.js Charter [#199](https://github.com/openjs-foundation/cross-project-council/issues/199) 55 | * just waiting for https://github.com/openjs-foundation/cross-project-council/pull/238 56 | to land and then we’ll land #199 57 | 58 | * Start accepting nominations for "regular" members [#178](https://github.com/openjs-foundation/cross-project-council/issues/178) 59 | * agreed we should open new issue to add info on FYI when regular member 60 | is added. Michael to create (created here: 61 | https://github.com/openjs-foundation/cross-project-council/issues/249) 62 | 63 | * Review meeting times [#129](https://github.com/openjs-foundation/cross-project-council/issues/129) 64 | * Please fill in your available times as we’ll be reviewing to find a second 65 | time slot to alternate between. 66 | 67 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 68 | * Create github template, not needed as going to be application through email 69 | * 70 | 71 | 72 | ## Q&A, Other 73 | * thank you myles for all the issue / pr cleanup yesterday 74 | 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: https://nodejs.org/calendar 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | 82 | 83 | -------------------------------------------------------------------------------- /meetings/2019/2019-07-17.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-07-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=IWvwW84IH58 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/257 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | 14 | * JB: jory burson (@jorydotcom) 15 | * JS: Joe Sepi (@joesepi) 16 | * CH: Christopher Hiller (@boneskull) 17 | * EA: Eemeli Arno () 18 | * ES: Even Stensberg(@evenstensberg) 19 | * MD: Michael Dawson (@mhdawson) 20 | * NOL: Nick O’Leary (@knolleary) 21 | * TW: Timmy Willison (@timmywil) 22 | * JSS: Jonah Stiennon (@jonahss) JAVASCRIPT STYLE SHEETS???!!!! 23 | * RR: Rachel Romoff (@rromoff) 24 | * KB: Kris Borchers (@kborchers) 25 | * BW: Brian Warner (@brianwarner) 26 | * AA: Abraham Jr. Agiri (@codeekage) 27 | 28 | ## Agenda 29 | 30 | ### Announcements 31 | 32 | * Collab summit planning reboot - come one, come all! 33 | * Project AMA opportunities 34 | 35 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 36 | 37 | ### openjs-foundation/cross-project-council 38 | 39 | * Who can be an Observer? [#234](https://github.com/openjs-foundation/cross-project-council/issues/234) 40 | 41 | AI: minor update to the language to make sure it’s clear all are welcome. Group +1’s the change and +1s merging the PR in. 42 | 43 | * Approve charter changes for Node.js Charter [#199](https://github.com/openjs-foundation/cross-project-council/issues/199) 44 | * PR to update Node.js charter landed last week. Closed. 45 | AI: this was landed last week. (added that comment above:)) 46 | 47 | * Review meeting times [#129](https://github.com/openjs-foundation/cross-project-council/issues/129) 48 | 49 | * AI: alternative time selected: Tuesdays at 16:00 UTC and 18:00 UTC. Next week is 18:00 UTC. 50 | 51 | * Ad hoc discussion about the CLA issue (https://github.com/openjs-foundation/cross-project-council/issues/124) 52 | 53 | - kind of complicated; JSF infra is out of date; looking at alternatives 54 | - want to provide better guidance for projects about their options 55 | - possibly take the issue up with Board’s legal subcommittee 56 | - MD requests we update that issue with progress so people can be kept in the loop 57 | 58 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 59 | 60 | Create links to slack / comms channel sign ups from OpenJSF website; assign to BW 61 | Move openjsf cla issue to doing, assign to BW 62 | Travel Fund - assigned to JSS last week who will be working on it this week 63 | Discussion of PR 165 project progression & adding some language for potential projects to the README about how to get started; plan to land to stage 3 if no response from Board; assign to JB 64 | Some updates on new project applications and ‘dogfooding’ for existing project; we want to make some kind of ‘project onboarding guide’ for champions 65 | Ask projects to start updating their docs - will push on this as as #165 lands, also #258 66 | Create another project board to track projects as they are updated; create issue template for all projects to track progress - assigned to JB, KB 67 | Project Directed Funding update - the Board is discussing this 68 | Moderating issue - assigned to Manil 69 | 70 | ## Q&A, Other 71 | 72 | ## Upcoming Meetings 73 | 74 | * **Calendar**: https://nodejs.org/calendar 75 | 76 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 77 | 78 | 79 | -------------------------------------------------------------------------------- /meetings/2019/2019-07-23.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-07-23 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/aVh8sk5bVKs 6 | **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/269 7 | 8 | ## Present 9 | * Joe Sepi (@joesepi) 10 | * Even Stensberg(@evenstensberg) 11 | * Michael Dawson (@mhdawson) 12 | * Kris Borchers (@kborchers) 13 | * Rachel Romoff (@rromoff) 14 | * 15 | * Christopher Hiller (@boneskull) 16 | * Timmy Willison (@timmywil) 17 | * Jonah Stiennon (@jonahss) 18 | * Christian Bromann (@christian-bromann) 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/cross-project-council 27 | 28 | * Create page with links to slack channels and sign up link on OpenJSF.org/slack [#260](https://github.com/openjs-foundation/cross-project-council/issues/260) 29 | * Brian Warner will add pinned message with description of channels and then we’ll close. 30 | 31 | * Review meeting times [#129](https://github.com/openjs-foundation/cross-project-council/issues/129) 32 | * Agreed we can close this for now. 2 new times in place. 33 | 34 | * Update/move jsf-clabot for new fdn [#124](https://github.com/openjs-foundation/cross-project-council/issues/124) 35 | * no updates, in progress 36 | 37 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 38 | 39 | * #261, There appears to be some bug or issue with GH preventing me from committing changes to the PR. I've reached out to GH support but no response so far. @joesepi was having a similar issue on a PR I submitted last week. Once this is solved I should be able to take action on this PR. 40 | * #262, Have created an Project Onboarding Issue template & met with @kborchers & @boneskull to start filling this out for architect and mocha #267. There's a new Project Board. Have triage some stuff into it. 41 | * Related to above, identified several issues that may block people from completing onboarding - #265 is about how & where we store contact details for projects, #266 is about providing some guidelines for displaying OpenJS Foundation logo on their websites, #207 is about project charters (we need a template & I believe were going to get one from the LF or Board), #258 is about the copyright notice, and last but not least we need to define our CoC escalation path so that projects can incorporate it #160. 42 | * Brian took the action to provide a template charter. 43 | 44 | 45 | ## Q&A, Other 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Calendar**: https://nodejs.org/calendar 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | 53 | 54 | -------------------------------------------------------------------------------- /meetings/2019/2019-07-30.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-07-30 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/zkCiKGTFW98 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/272 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jonah Stiennon (@jonahss) 12 | * Nick O’Leary (@knolleary) 13 | * Jory Burson (@jorydotcom) 14 | * Kris Borchers (@kborchers) 15 | * Matteo Collina (@mcollina) 16 | * Michael Rawlings (@mlrawlings) 17 | * Timmy Willison (@timmywil) 18 | * Brian Warner (@brianwarner) 19 | * Michael Dawson (@mhdawson) 20 | * Eemeli Aro (@eemeli) 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/cross-project-council 29 | 30 | * Create page with links to slack channels and sign up link on OpenJSF.org/slack [#260](https://github.com/openjs-foundation/cross-project-council/issues/260) 31 | * Discussed, agreed we can close. Joe to close. 32 | 33 | * ELI5: project charters [#207](https://github.com/openjs-foundation/cross-project-council/issues/207) 34 | * Brian has action to provide a template. 35 | * Leave on agenda as it’s important 36 | 37 | * Review meeting times [#129](https://github.com/openjs-foundation/cross-project-council/issues/129) 38 | * New meeting times agreed, Joe closed. 39 | 40 | * Update/move jsf-clabot for new fdn [#124](https://github.com/openjs-foundation/cross-project-council/issues/124) 41 | * Brian is working at the legal/board level to move this forward. 42 | * Agreed to remove agenda tag until there is something to disuss. 43 | 44 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 45 | * 46 | 47 | ## Project board 48 | 49 | * 2 projects going through the onboading process 50 | * Jory: meeting needs of CPC members, is information being captured what we need. 51 | * Joe: Kris, have not heard any feedback on CPC, from working through it expect that is capturing that is needed. 52 | * Discussed if we are ready for CPC review to see if it covers what’s needed 53 | * Need to unblock some aspects before we are ready for that. 54 | * discussed making individual project maintainer lists for projects contacts & adding a public contact file for documentation (names only) 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 | 64 | 65 | -------------------------------------------------------------------------------- /meetings/2019/2019-08-06.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-08-06 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=sI6i0bGmjM8 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/281 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Sendil Kumar (@sendilkumarn) 13 | * Even Stensberg @evenstensberg 14 | * Christopher Hiller (@boneskull) 15 | * M.Sharaf Hijjeh (@abusharaf) 16 | * Myles Borins (@MylesBorins) 17 | * Manil Chowdhury (@keywordnew) 18 | * Eemeli Aro (@eemeli) 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 | None 27 | 28 | ### openjs-foundation/cross-project-council 29 | 30 | * adds a draft charter template [#279](https://github.com/openjs-foundation/cross-project-council/pull/279) 31 | 32 | Examples suggested in PR 33 | Jory: sharing where she gathered the info for the template (Node.js TSC and K8s Sig) and what a charter is used for 34 | Myles: asks for clarification on if this is for new projects or existing projects 35 | Jory: clarifies that it is for new projects and existing projects that do not already have charters which is many. 36 | Myles: offers to review and suggests LF legal review as well; adds that legal will need to approve new charters regardless 37 | 38 | Action Item: Continue review; request legal review from Andy Updegrove 39 | 40 | * doc: swapping refs to TAC with CPC [#275](https://github.com/openjs-foundation/cross-project-council/pull/275) 41 | 42 | Action Item: 43 | 44 | * ELI5: project charters [#207](https://github.com/openjs-foundation/cross-project-council/issues/207) 45 | 46 | Related: PR for Charter template (#279) 47 | Action Item: Follow up on issue and close. 48 | 49 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 50 | 51 | #172: Travel Fund issue. Proposal at Stage 0, PR to move to stage 1 (#278). Issue open in Node admin and email out to projects list. Will land in ~48 barring any outstanding changes or firm -1s 52 | 53 | #261 54 | Action Item: Open new PR with updated language 55 | 56 | #271 - process for handling reports 57 | Eemeli has outstanding comments on the PR; will look at and address. Next steps may be a merge (merging into a proposal that is at stage 1). 58 | 59 | #263 - onboarding/off boarding regular members 60 | 61 | # Projects: Update docs 62 | Action Item: convert to an issue and add to the project onboarding board 63 | 64 | # Foundation infrastructure 65 | 66 | # Admin policy docs 67 | Joe taking as an action item. 68 | 69 | Issues pertaining to the board: probably not able to make much progress here. 70 | 71 | * New Code & Learn format at the next Interactive 72 | 73 | 74 | ## Q&A, Other 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: https://nodejs.org/calendar 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | 82 | 83 | -------------------------------------------------------------------------------- /meetings/2019/2019-09-10.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-09-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=BJaFvM_bX0M 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/320 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Kris Borchers (@kborchers) 12 | * Jonah Stiennon (@jonahss) 13 | * Matteo Collina (@mcollina) 14 | * Christopher Hiller (@boneskull) 15 | * Michael Dawson (@mhdawson) 16 | * Wes Todd (@wesleytodd) 17 | * Timmy Willison (@timmywil) 18 | * Nick O’Leary (@knolleary) 19 | * Even Stensberg (@evenstensberg) 20 | * Brian Warner (@brianwarner) 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/cross-project-council 30 | 31 | * Move User Feedback Survey efforts from Node.js to OpenJS [#315](https://github.com/openjs-foundation/cross-project-council/issues/315) 32 | * removed from agenda. Joe has action items. Will re-add when needed. 33 | 34 | * doc: incubating projects must have a champion [#309](https://github.com/openjs-foundation/cross-project-council/pull/309) 35 | * From last meeting we expected that we were going to discuss in issue. 36 | * Application Champion (CPC member) 37 | * early on who will begin the process who is applying 38 | * no champion is a barometer on the application 39 | * Michael contentious issue, what does not champion mean. 40 | * Next action is to comment on issue which was discussion that group present felt that at 41 | least for the first few we need to require a champion. 42 | * Requirements on champion 43 | * Provide weekly update on progress 44 | * Be available to answer questions from the project 45 | * Advocate on behalf of the project 46 | * Help to explain why the project is a good fit 47 | * Help the application manager when needed 48 | 49 | 50 | * Application Manager (Foundation Brian/Jory) 51 | * Ensures progress through the process, helps project understand and move 52 | through process steps. 53 | 54 | * Specify the scope of CPC votes during application and incubation [#296](https://github.com/openjs-foundation/cross-project-council/issues/296) 55 | * Need to update docs to cover this. 56 | * Michael need no/nogo on behalf of the project, and last call for objections to CPC member. 57 | * potentially related: https://github.com/openjs-foundation/cross-project-council/pull/319 58 | * Michael volunteered to PR in some additional guidance….. 59 | 60 | * Commit to providing a reply to an application within a specific time frame [#295](https://github.com/openjs-foundation/cross-project-council/issues/295) 61 | * Initial response within 48 hours, strive for 24 (Foundation staff Brian/Jory) - automate 62 | immediate response? 63 | * Updates at least every week until process is concluded. 64 | * Michael will add this to the PR above. 65 | 66 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 67 | 68 | 69 | 70 | ## Q&A, Other 71 | 72 | ## Upcoming Meetings 73 | 74 | * **Calendar**: https://nodejs.org/calendar 75 | 76 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 77 | 78 | 79 | -------------------------------------------------------------------------------- /meetings/2019/2019-09-17.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-09-17 2 | 3 | ## Links 4 | 5 | * **Recording**: http://www.youtube.com/watch?v=Nf6l7rAlxzQ 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/323 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Anton Molleda (@molant) 12 | * Michael Dawson (@mhdawson) 13 | * Brian Warner (@brianwarner) 14 | * Chris Hiller (@boneskull) 15 | * Dave Methvin 16 | * Eemeli Aro (@eemeli) 17 | * Tierney Cyren 18 | * Myles Borins (@MylesBorins) 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/cross-project-council 27 | 28 | * doc: incubating projects must have a champion [#309](https://github.com/openjs-foundation/cross-project-council/pull/309) 29 | * discussed https://github.com/openjs-foundation/cross-project-council/pull/321 which 30 | covers this. 31 | 32 | * Specify the scope of CPC votes during application and incubation [#296](https://github.com/openjs-foundation/cross-project-council/issues/296) 33 | * discussed https://github.com/openjs-foundation/cross-project-council/pull/321 which 34 | covers this. 35 | 36 | * Commit to providing a reply to an application within a specific time frame [#295](https://github.com/openjs-foundation/cross-project-council/issues/295) 37 | * discussed https://github.com/openjs-foundation/cross-project-council/pull/321 which 38 | covers this. 39 | 40 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 41 | * https://github.com/openjs-foundation/cross-project-council/pull/271 42 | * Discussed in CPC meeting, agreed that we can land and them open PR to move 43 | to Stage 2 and address any new questions/issues etc. as part of that PR. 44 | 45 | 46 | ## Q&A, Other 47 | 48 | ## Upcoming Meetings 49 | 50 | * **Calendar**: https://nodejs.org/calendar 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | 54 | 55 | -------------------------------------------------------------------------------- /meetings/2019/2019-09-24.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-09-24 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=F1goQzp1djs 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/329 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Kris Borchers (@kborchers) 13 | * Timmy Willison (@timmywil) 14 | * Rachel Romoff (@rromoff) 15 | * Jory Burson (@jorydotcom) 16 | * Brian Warner (@brianwarner) 17 | * Matteo Colina 18 | * Chris Hiller (@boneskull) 19 | * Myles Borins (@MylesBorins) 20 | * Tierney Cyren 21 | * Even Stensberg 22 | * Anton Molleda (@molant) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 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/cross-project-council 31 | 32 | * Commit to providing a reply to an application within a specific time frame [#295](https://github.com/openjs-foundation/cross-project-council/issues/295) 33 | * Michael: discussion in previous CPC meeting was that we were not comfortable comiting to 34 | a specific time. Instead we agreed to commit to an initial response in 48 hours and then a 35 | weekly update. This is covered in: 36 | https://github.com/openjs-foundation/cross-project-council/pull/321 37 | 38 | * Clarification about whether an application becomes private or public [#327](https://github.com/openjs-foundation/cross-project-council/issues/327) 39 | * Application is private by default as submitted, but after approval application can be made public with consent of both parties 40 | * It would possibly be helpful to have a short list of canonical approved applications to provide examples & ways to encourage other applicants 41 | * Action Item: propose some text to clarify that the application is private; possibly iterate on language that encourages a process to make public versions of the applications available. 42 | 43 | * Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331) 44 | * Would be great if there were tooling we can take advantage of, in order to provide some helpful ‘pokes’ and some metrics around how we’re doing. 45 | * Private GH project repo & other ideas discussed. Folks will continue to explore & discuss 46 | 47 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 48 | * 49 | 50 | 51 | ## Q&A, Other 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Calendar**: https://nodejs.org/calendar 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | 59 | 60 | 61 | -------------------------------------------------------------------------------- /meetings/2019/2019-10-15.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-10-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=C15EnbKswig 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/348 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Jory Burson (@jorydotcom) 13 | * Tobie Langle (@tobie) 14 | * Anton Molleda (@molant) 15 | * Brian Warner (@brianwarner) 16 | * Tierney Cyren (@bnb) 17 | * Myles Borins (@MylesBorins) 18 | * Robin Ginn 19 | * Jordan Harband (@ljharb) 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | * JQ Infra meeting on thurs Oct. 17 26 | * Standards WG next Tues. 27 | * Next Friday - Board meeting! 28 | * #279 draft charter template - okay’ed and merged 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/cross-project-council 33 | 34 | * Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331) 35 | 36 | * how soon should we tell the project who their champion is? 37 | * we discussed tooling options for tracking this - need to continue that conversation 38 | * do we need to add more clarifications on this PR? 39 | * Land PR #321 and then iterate? Some +1s to this idea. Would be ‘soothing’ to the project to know what the next steps. 40 | * also talk with current applicants to get their feedback. 41 | * keep this open to make sure we have some sort of observability into this. Make sure we answer the tooling question. 42 | 43 | * doc: Move COC proposal to stage 2 [#330](https://github.com/openjs-foundation/cross-project-council/pull/330) 44 | * Michael believe is is ready to land 45 | * Joe: no additional comments from last week, plan was to merge. 46 | * ACTION: 47 | * Joe - squash & merge; 48 | * Michael - open PR to move to stage 3 49 | 50 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 51 | 52 | * MDawson brought this up to the Node Security WG 53 | * Joe: Help section on the repo about how to get in touch with people 54 | * MDawson: Node Security WG has volunteered to do that - will post a proposal/recommendation draft in the next few weeks to move this further. 55 | 56 | 57 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 58 | 59 | * https://github.com/openjs-foundation/cross-project-council/projects/3 60 | * NOTHING IS IN PROGRESS 61 | * Joe: Needs to bring admin/policy docs over from Node Admin 62 | * Define / Document style guide - nearing the finish line with signs off from the Board. Documents need to be approved by the board and that is expected to happen soon. 63 | * moving infra work tab to in progress - more updates next week 64 | * Project Directed Funding & JSF CLA bot are in the “Waiting on the board” column 65 | 66 | https://github.com/openjs-foundation/cross-project-council/projects/4 67 | 68 | * need to make new tickets for incubating projects & the rest of the current projects. 69 | * Jory to pick this back up next week. 70 | 71 | * Ad Hoc Conversation about attendance for incubating projects & when it is appropriate to have those representatives are added to things like the formal mailing lists & how to add them to governance/regular membership 72 | 73 | Close for Private Session 74 | 75 | 76 | 77 | ## Q&A, Other 78 | 79 | ## Upcoming Meetings 80 | 81 | * **Calendar**: https://nodejs.org/calendar 82 | 83 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 84 | 85 | -------------------------------------------------------------------------------- /meetings/2019/2019-10-29.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-10-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=u5YJMq399-M 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/381 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Even Stensberg(@evenstensberg) 12 | * Michael Dawson (@mhdawson) 13 | * Chris Hiller (@boneskull) 14 | * Jordan Harband (@ljharb) 15 | * Anton Molleda (@molant) 16 | * Brian Warner 17 | * Myles Borins (@MylesBorins) 18 | * Tierney Cyren 19 | * Timothy Willison (@timmywil) 20 | * Christian Bromann (@christian-bromann) 21 | * Eemeli Aro (@eemeli) 22 | 23 | 24 | * doc: move COC proposal to stage 3 [#379](https://github.com/openjs-foundation/cross-project-council/pull/379) 25 | * Moderation team from the AMP project have indicated that they will review 26 | and give us some feedback/comments. 27 | * Waiting for that before moving forward. 28 | 29 | * Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331) 30 | * Agreed last week to create public/private repositories to track 31 | * Joe has created the public repo, moved over Node onboarding issue 32 | * Started to create repo but org needs to be upgraded first 33 | * Joe, -> could move over the obvious public onboarding issues, should move 34 | over project board as well? Michael, sounds good. No objections from those 35 | in the meeting. 36 | 37 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 38 | * Michael followed up with Marcin and he’s indicated that he hopes to publish a draft 39 | For discussion this week. 40 | 41 | 42 | * Add impact and consumers of the project to new project template [#306](https://github.com/openjs-foundation/cross-project-council/pull/306) 43 | * Myles will give it another review. 44 | 45 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 46 | * Joe has some WIP for moving the Node.js docs over as a baseline 47 | * Issues waiting on the board 48 | * project directed funding discussed in last board meeting and 49 | understood that we need to address some aspects for some projects coming in. 50 | * Guidance on usage of logos etc should be able to proceed now that IP policy has been 51 | Approved. 52 | * Question about CLA being signed both for company and individual (both at the same 53 | time), Brian to ask, believes it will have been considered but does not have answer 54 | off the top of his head. 55 | * Items to discuss with the board is empty 56 | * onboarding board 57 | * Walked through a number of issues 58 | 59 | 60 | ## Q&A, Other 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Calendar**: https://calendar.openjsf.org 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 67 | -------------------------------------------------------------------------------- /meetings/2019/2019-11-12.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2019-11-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=OEUKPkZCvaw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/401 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 | Tierney C (@bnb) 16 | Rachel Romoff (@rromoff) 17 | Christopher Hiller (@boneskull) 18 | Timmy Willison (@timmywil) 19 | Even Stensberg (@evenstensberg) 20 | Ruy Adorno (@ruyadorno) 21 | Tobie Langel (@tobie) 22 | Jordan Harband (@ljharb) 23 | 24 | 25 | 26 | ## Agenda 27 | 28 | ### Announcements 29 | Jory asked for collab summit sessions as we enter into Node+JS Interactive season 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/cross-project-council 34 | 35 | * onboarding meta questions [#398](https://github.com/openjs-foundation/cross-project-council/issues/398) 36 | Where should onboarding topics live? This process should be documented in the repo. 37 | Jory, Brian, and Tobie to speak further to move this forward. 38 | 39 | * Collab Summit sessions [#390](https://github.com/openjs-foundation/cross-project-council/issues/390) 40 | Next step, more input on what sessions the CPC wants to run, and who from the CPC would like to lead these sessions. Please share input on the issue. 41 | 42 | * request: Review CommComm Charter Update [#383](https://github.com/openjs-foundation/cross-project-council/issues/383) 43 | For questions or concerns, please comment or reach out to Tierney 44 | 45 | * doc: move COC proposal to stage 3 46 | [#379](https://github.com/openjs-foundation/cross-project-council/pull/379) 47 | 48 | File an issue for a process for changing the CoC in the future 49 | 50 | Notes from the Ad Hoc CoC Meeting: https://docs.google.com/document/d/1wCZMnfwJnDF9l4sUq0BD5JI-mbPCtQnPfVHmvge_ZWs/edit 51 | 52 | * Administering Project Applications 53 | [#331](https://github.com/openjs-foundation/cross-project-council/issues/331) 54 | Last update was we had a public onboarding repo, and looking into a private repo. 55 | Private repo has been requested from GitHub and we are waiting. Jory to check with Brian on the capability to create private repo. 56 | 57 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 58 | 59 | * Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115) 60 | 61 | Gone through board, checked off relevant issues and checkboxes that are completed. 62 | 63 | *Checklist deadline for Collab Summit graduation 64 | [openjs-foundation/project-onboarding#30](https://github.com/openjs-foundation/project-onboarding/issues/30) 65 | Voting is relatively quick and happens asynchronously. That said there’s still a lot of blocked issues (e.g. the Code of Conduct changes discussed before) that are going to make it really difficult to graduate by the Collab Summit. 66 | 67 | * Communication channel between CPC and AMP infra WG [openjs-foundation/project-onboarding#31](https://github.com/openjs-foundation/project-onboarding/issues/31) 68 | CPC do decide which communication channel is preferred between dedicated mailing list and foundation Slack. 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 | -------------------------------------------------------------------------------- /meetings/2020/2020-04-28.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-04-28 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=xYe0hRY1xwk 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/533 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Eemeli Aro (@eemeli) 13 | * Myles Borins (@MylesBorins) 14 | * Robin Ginn (@rginn) 15 | * Dylan Schiemann (@dylans) 16 | * Sara Chipps (@sarajchipps) 17 | * Saulo Nunes(@saulonunes) 18 | * Shelley Vohr (@codebytere) 19 | * Michael Dawson (@mhdawson) 20 | * Kris Borchers (@kborchers) 21 | * Mike Samuel (@mikesamuel) 22 | * Christopher Hiller (@boneskull) 23 | * Jordan Harband (@ljharb) 24 | * Anton Molleda (@molant) 25 | 26 | 27 | ## Agenda 28 | 29 | This week's meeting will be a working session: 30 | Code of Conduct and related matters. 31 | Two relevant issues: 32 | How do we keep Code of Conduct up to date without upstreaming our modifications to it #503 33 | Populate the Code Of Conduct Panel #469 34 | 35 | As Jory said in the meeting issue: 36 | 37 | to help facilitate the working session meeting tomorrow, I've created a slide deck to help map the different CoC related spaces we're working through: https://docs.google.com/presentation/d/1LsfuVT4yL0CxdJW_76_ORxpQ-B8Jfh39FmXVnzLdywA/edit?usp=sharing 38 | 39 | 40 | https://docs.google.com/document/d/13CVtT8Y507CTvu5qypxz3Lj2PwTk5Xu916wO4dzVBoI/edit 41 | 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 | -------------------------------------------------------------------------------- /meetings/2020/2020-05-05.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-05-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=kMICa2KjneM 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/539 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Brian Kardell (@bkardell) 12 | * Matteo Collina (@mcollina) 13 | * Divy Tolia (@designmoreweb) 14 | * Kris Borchers (@kborchers) 15 | * Dylan Schiemann (@dylans) 16 | * Robin Ginn (@rginn) 17 | * Jordan Harband (@ljharb) 18 | * Tobie Langel (@tobie) 19 | * Rachel Romoff (@rromoff) 20 | * Saulo Nunes (@saulonunes) 21 | * Michael Dawson (@mhdawson) 22 | * Jory Burson (@jorydotcom) 23 | * Timmy Willison (@timmywil) 24 | * Sendil Kumar N (@sendilkumarn) 25 | 26 | 27 | 28 | ## Agenda 29 | 30 | ### Announcements 31 | 32 | Summit planning meeting today! WOOT 33 | Standards WG meeting today, also WOOT! 34 | Node Red AMA tomorrow, WOOT WOOT 35 | New project announcements coming up! 36 | Register for the conference and the collab summit 37 | 38 | ### Board Meeting Updates 39 | 40 | 41 | This week's meeting will be another working session on spinning up the Code of Conduct Working Group but will begin with an update on the Voting Regular Member election. 42 | Proposed Agenda timeboxes for the meeting: 43 | 5min Voting Regular Member update 44 | 15min timebox on Charter language 45 | Remainder: Focus on unblocking onboarding (CoC specific) 46 | See the following issues relating to code of conduct process: 47 | #534 48 | #503 49 | #469 50 | #530 51 | 52 | Voting Regular Member update 53 | * Jory: three nominees; will use OpaVote; Jory will administer; Start voting tomorrow morning; consensus on call to use Scottish STV for this election, following recommendation from https://www.opavote.com/methods/recommended
. 54 | 55 | Underlying flow - clarity about where escalation path lives 56 | 57 | 58 | 59 | ## Q&A, Other 60 | 61 | ## Upcoming Meetings 62 | 63 | * **Calendar**: https://calendar.openjsf.org 64 | 65 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 66 | 67 | -------------------------------------------------------------------------------- /meetings/2020/2020-05-19.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-05-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=dxQRByxORBg 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/550 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Timmy Willison (@timmywil) 13 | * Jordan Harband (@ljharb) 14 | * Sara Chipps (@SaraJChipps) 15 | * Dylan Schiemann (@dylans) 16 | * Sendil Kumar N (@sendilkumarn) 17 | * Robin Ginn (@rginn) 18 | * Brian Warner 19 | * Saulo Nunes 20 | * Eemeli Aro 21 | * Myles Borins 22 | * Rachel Romoff 23 | * Sara Chipps 24 | * Matteo Collina (@mcollina) 25 | * Tobie Langel 26 | * Jory Burson (@jorydotcom) 27 | * Divy Tolia (@designmoreweb) 28 | 29 | 30 | ## Agenda 31 | 32 | ### Announcements 33 | 34 | * Jory 35 | * Today 36 | * Summit planning meeting, immediately following this one 37 | * Standards WG meeting 38 | * Marketing meeting 39 | * Office hours later in week, this week internationalization 40 | * Friday public session of board meeting 41 | 42 | * Michael, PR to move collaboration network to stage 1, please review 43 | https://github.com/openjs-foundation/cross-project-council/pull/548 44 | 45 | * Eemeli: we should start working on the individual membership program. 46 | * Town hall meetings only at stage 0 47 | * Myles, since it’s stale we should revisit from first principles, should be administered by 48 | Foundation staff versus volunteers. Board seat should it be teased apart from the 49 | Program? Summary, find new champion and rethink. 50 | * Sara wanted to take the opportunity to raise my hand to work on this. 51 | * Robin would like to get involved as well. 52 | 53 | ### Board Meeting Updates 54 | 55 | As agreed upon in last weeks meeting, this meeting's agenda will be: 56 | * ½ on 2nd board seat for next year #438 57 | * Board seat was assigned to Node.js project for the first year as a transition 58 | * CPC needs to decide what to do for the 2nd year. 59 | * First question 60 | * Maintain as Node.js seat or not for next year? 61 | * Jory, had thought that we were going to rotate among impact projects 62 | * Myles, could be seen as representation of the projects, maybe open up 63 | to all nominees, and have CPC vote. 64 | * Tobie, would they represent their project versus all projects. 65 | * Eemeli, byles say something about multi-vote approach does that imply anything. 66 | * Michael don’t believe so 67 | * Myles, called “At Large Community Director”, should not be a requirement to be active in 68 | CPC. Part of expectations is that they would become active 69 | * Ask who might be interested 70 | * Dylan can we make it an action to get the description of expectations/guidelines for next 71 | Week? 72 | * On Brian’s TODO list. 73 | 74 | * ½ on Code of Conduct WG ramp up 75 | * Jory start by discussing: https://github.com/openjs-foundation/code-of-conduct/pull/2 76 | 77 | 78 | ## Q&A, Other 79 | 80 | ## Upcoming Meetings 81 | 82 | * **Calendar**: https://calendar.openjsf.org 83 | 84 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 85 | -------------------------------------------------------------------------------- /meetings/2020/2020-06-09.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-06-09 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=iTGce5XCks0 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/561 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Eemeli Aro (@eemeli) 12 | * Michael Dawson (@mhdawson) 13 | * Tobie Langel (@tobie) 14 | * Divy Tolia (@designmoreweb) 15 | * Robin Ginn (@rginn) 16 | * Jordan Harband (@ljharb) 17 | * Mike Samuel (@mikesamuel) 18 | * Dylan Schiemann (@dylans) 19 | * Rachel Romoff (@rromoff) 20 | * Christopher Hiller (@boneskull) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | * OpenJS Conference in a few weeks, plan for a great week. Schedule was published 27 | * Project has asked about DUNNs number, we’ve updated to OpenJS Foundation, can 28 | reach out to Brian or Robin if you need one for some process. 29 | 30 | 31 | ### Board Meeting Updates 32 | 33 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 34 | 35 | * Call scheduled to go over a number of issues with legal committee 36 | 37 | ### openjs-foundation/cross-project-council 38 | 39 | * CPC Collab Summit sessions [#559](https://github.com/openjs-foundation/cross-project-council/issues/559) 40 | * Need to figure out which ones we want to have. 41 | * Robin are these on Jory’s list? Joe not sure. 42 | * 43 | 44 | * Project charter review for AMP [#552](https://github.com/openjs-foundation/cross-project-council/issues/552) 45 | 46 | * CPC Chair election [#549](https://github.com/openjs-foundation/cross-project-council/issues/549) 47 | 48 | * Should outgoing voting members become regular members? [#543](https://github.com/openjs-foundation/cross-project-council/issues/543) 49 | Related PR which changes governance and has been open for 13 days: 50 | [#558](https://github.com/openjs-foundation/cross-project-council/pull/558) 51 | 52 | * OpenJS Collaboration Network ? [#474](https://github.com/openjs-foundation/cross-project-council/issues/474) 53 | 54 | * 2nd Director seat- post July 2020 [#438](https://github.com/openjs-foundation/cross-project-council/issues/438) 55 | 56 | * Add Foundation-wide copyright guidance [#414](https://github.com/openjs-foundation/cross-project-council/pull/414) 57 | 58 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 59 | PR ready at stage 0 -> https://github.com/openjs-foundation/cross-project-council/pull/489 asking that we land unless there are objections in the meeting. Also do we need to go through all stages or can we skip some since it seems pretty straight forward? 60 | 61 | ### openjs-foundation/code-of-conduct 62 | 63 | * Onboarding: Provide explicit feedback on what `escalation path` is and how to implement it + temporarily address in the Onboarding Checklist [#8](https://github.com/openjs-foundation/code-of-conduct/issues/8) 64 | 65 | 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 | -------------------------------------------------------------------------------- /meetings/2020/2020-06-16.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-06-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=XNToJDQR6NI 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/564 7 | 8 | ## Present 9 | 10 | * Kris Borchers (@kborchers) 11 | * Joe Sepi (@joesepi) 12 | * Michael Dawson (@mhdawson) 13 | * Tobie Langel (@tobie) 14 | * Rachel Romoff (@rromoff) 15 | * Dylan Schiemann (@dylans) 16 | * Christian Bromann (@christian-bromann) 17 | * Divy Tolia (@designmoreweb) 18 | * Abraham Jr. Agiri (@codeekage) 19 | * Marcin Hoppe (@MarcinHoppe) 20 | * Timothy Willison (@timmywil) 21 | * Mike Samuel (@mikesamuel) 22 | * Robin Ginn (@rginn) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | * Lost going on this week 29 | * Last summit planning meeting this week 30 | * Rachel: Next week is OpenJS World ! Hope to see you there. 31 | * Collab summit in addition, multiple projects have tracks/sessions 32 | * Collabsummit.qiqochat.com, if you are registered you can go there today 33 | 34 | 35 | 36 | ### Board Meeting Updates 37 | 38 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 39 | 40 | ### openjs-foundation/cross-project-council 41 | 42 | * CPC Collab Summit sessions [#559](https://github.com/openjs-foundation/cross-project-council/issues/559) 43 | 44 | * CPC Chair election [#549](https://github.com/openjs-foundation/cross-project-council/issues/549) 45 | 46 | 47 | * OpenJS Collaboration Network ? [#474](https://github.com/openjs-foundation/cross-project-council/issues/474) 48 | 49 | 50 | * 2nd Director seat- post July 2020 [#438](https://github.com/openjs-foundation/cross-project-council/issues/438) 51 | * last week agree to have people express interest 52 | * A handful of people expressed interest 53 | * 1 new person interested completely new 54 | * 5 people who are already active in the work (voting or regular members) so we 55 | have interested members, 2 of 5 are voting members 56 | * 57 | 58 | * Add Foundation-wide copyright guidance [#414](https://github.com/openjs-foundation/cross-project-council/pull/414) 59 | * Still under way 60 | 61 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 62 | 63 | * PR to move guidelines to stage 2 - https://github.com/openjs-foundation/cross-project-council/pull/566 64 | * Jory will help get in front of projects that don’t normally have people in CPC meeting 65 | 66 | ### openjs-foundation/code-of-conduct 67 | 68 | * Onboarding: Provide explicit feedback on what `escalation path` is and how to implement it + temporarily address in the Onboarding Checklist [#8](https://github.com/openjs-foundation/code-of-conduct/issues/8) 69 | 70 | 71 | 72 | ## Q&A, Other 73 | 74 | ## Upcoming Meetings 75 | 76 | * **Calendar**: https://calendar.openjsf.org 77 | 78 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 79 | 80 | -------------------------------------------------------------------------------- /meetings/2020/2020-07-28.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-07-28 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Q9-np3aAbXw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/598 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Timmy Willison (@timmywil) 12 | * Michael Dawson (@mhdawson) 13 | * Kris Borchers (@kborchers) 14 | * Robin Ginn (@rginn) 15 | * Eemeli Aro (@eemeli) 16 | * Rachel Romof (@rromoff) 17 | * Matteo Collina (@mcollina) 18 | * Jordan Harband (@ljharb) 19 | * Tobie Langel (@tobie) 20 | * Christian Bromann (@christian-bromann) 21 | * Divy Tolia (@designmoreweb) 22 | * Mike Samuel (@mikesamuel) 23 | * Antón Molleda (@molant) 24 | 25 | 26 | ## Agenda 27 | 28 | ### Announcements 29 | 30 | * Blogs + keynote on certification in China coming in next few days. (Linux open source summit) 31 | * If somebody you know has an interesting story to highlight on the blog, please nominate them 32 | by reaching out to Rachel(Slack or email) 33 | * Standards WG meeting is 2pm EST today 34 | 35 | ### Board Meeting Updates 36 | 37 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 38 | 39 | ### openjs-foundation/cross-project-council 40 | 41 | * Incubation process clarifications [#567](https://github.com/openjs-foundation/cross-project-council/issues/567) 42 | * Addressed by PR https://github.com/openjs-foundation/cross-project-council/pull/591 43 | 44 | 45 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 46 | * Joe, would make sense to have proposal. If we can discuss in the issue and then have 47 | somebody pull together into PR for proposal 48 | 49 | * Board seat definitions and process [#587](https://github.com/openjs-foundation/cross-project-council/pull/587) 50 | * Joe will do one last check, will let Michael know if its ready and he will kick of email board 51 | vote 52 | 53 | * Updating the CLA to the Apache-style ICLA and CCLA [#583](https://github.com/openjs-foundation/cross-project-council/issues/583) 54 | * Last question answered 5 days, ago, ready to go 55 | * Board vote thread already open was waiting for this feedback, and it seems there 56 | are not concerns. 57 | * WIll close issue and board vote will proceed. 58 | 59 | * Collaboration for hackathon [#572](https://github.com/openjs-foundation/cross-project-council/issues/572) 60 | * Has been raised as FYI, will take agenda tag off. 61 | 62 | * doc: Governance changes for Collaboration Network [#547](https://github.com/openjs-foundation/cross-project-council/pull/547) 63 | * Michael has action to look at allowed licences. 64 | 65 | * 2nd Director seat- post July 2020 [#438](https://github.com/openjs-foundation/cross-project-council/issues/438) 66 | * Joe, once PR for board seat definitions land, will need to get vote started. 67 | * Primary directory, CPC member, second active OpenJS Collaborator 68 | * Close this issue, open new issue for election proposal. 69 | 70 | * Add Foundation-wide copyright guidance [#414](https://github.com/openjs-foundation/cross-project-council/pull/414) 71 | * No update 72 | 73 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 74 | * Need new PR to move to stage 3. 75 | 76 | 77 | 78 | ## Q&A, Other 79 | 80 | ## Upcoming Meetings 81 | 82 | * **Calendar**: https://calendar.openjsf.org 83 | 84 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 85 | 86 | -------------------------------------------------------------------------------- /meetings/2020/2020-08-18.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-08-18 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=aOJZl2vopJA 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/621 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Kris Borchers (@kborchers) 13 | * Matteo Collina (@mcollina) 14 | * Tierney Cyren (@bnb) 15 | * Divy Tolia (@designmoreweb) 16 | * Sendil Kumar (@sendilkumarn) 17 | * Dylan Schiemann (@dylans) 18 | * Rachel Romoff (@rromoff) 19 | * Shelley Vohr (@codebytere) 20 | * Eemeli Aro (@eemeli) 21 | * Agiri (@codeekage) 22 | * Robin Ginn (@rginn) 23 | * Sara Chipps (@sarajo) 24 | * Brian Warner (@brianwarner) 25 | 26 | 27 | ## Agenda 28 | 29 | ### Announcements 30 | Marketing Committee meeting today, at 12 pm PT/ 3 pm ET 31 | Public Board meeting Friday, Aug 21 32 | 33 | ### Board Meeting Updates 34 | 35 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 36 | 37 | ### openjs-foundation/cross-project-council 38 | 39 | * Fastify charter review [#617](https://github.com/openjs-foundation/cross-project-council/issues/617) 40 | * Please review, hoping to close next week 41 | 42 | * Nominations Open: Community Board Seat for OpenJS Foundation Board of Directors [#616](https://github.com/openjs-foundation/cross-project-council/issues/616) 43 | * 5 self nominations, nominations closed. Great to see a good number of candidates 44 | * Voting is open 45 | 46 | * Next Steps for Supporter Program [#607](https://github.com/openjs-foundation/cross-project-council/issues/607) 47 | * Sara, meeting last Friday on compiling notes into pull request, some exciting suggestions 48 | * Should be PR this week. 49 | 50 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 51 | * Chris Hiller and Tobie were going to move this forward. 52 | 53 | * doc: Governance changes for Collaboration Network [#547](https://github.com/openjs-foundation/cross-project-council/pull/547) 54 | * Some discussion about suggestion for default licence 55 | * Eemeli, ok to have different default, but need to explain why. 56 | * Tierney, initial guess, if suggesting apache, recommend MIT as that is what much 57 | of the ecosystem uses. 58 | * Eemeli, maybe the preference should be in the IP policy itself. 59 | 60 | * Add Foundation-wide copyright guidance [#414](https://github.com/openjs-foundation/cross-project-council/pull/414) 61 | * Eemeli mentioned that it mentions the “project” as opposed to the foundation 62 | * Brian to follow up to see if we can make that change, or if there are some implications. 63 | 64 | * Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326) 65 | * some comments, needs an update 66 | 67 | * We should try an earlier CPC meeting time 68 | [#599](https://github.com/openjs-foundation/cross-project-council/issues/599) 69 | * General discussion around times and goals with meeting times 70 | * Joe will update issue with proposal to alternate an early time with the later time 71 | * Eemeli will create an issue asking for input from folks who want to contribute but have difficulty with current meeting times 72 | 73 | 74 | ## Q&A, Other 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: https://calendar.openjsf.org 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | 82 | -------------------------------------------------------------------------------- /meetings/2020/2020-09-22.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-09-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=3WLD_Gq5Z7E&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/646 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Sendil Kumar (@sendilkumarn) 13 | * Jory Burson (@jorydotcom) 14 | * Robin Ginn (@rginn) 15 | * Tobie Langel (@tobie) 16 | * Dylan Schiemann (@dylans) 17 | * Brian Warner (@brianwarner) 18 | * Shelley Vohr (@codebytere) 19 | * Divy Tolla (@designmoreweb) 20 | * Timmy Willison (@timmywil) 21 | * Matteo Collina (@mcollina) 22 | * Tierney Cyren (@bitnbang) 23 | * Abraham Jr. Agiri (@codeekage) 24 | * Eemeli Aro (@eemeli) 25 | 26 | 27 | ## Agenda 28 | 29 | ### Announcements 30 | 31 | * 2021 event - getting the programming committee band back together! 32 | * AMP Fest - Oct. 13 33 | * Next AMA - Oct. 14 with the AMP TSC 34 | * sign up for the mailing list (projects@) 35 | * standards meeting later today 36 | 37 | ### Board Meeting Updates 38 | 39 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 40 | 41 | ### openjs-foundation/cross-project-council 42 | 43 | * Add examples of successful applications [#643](https://github.com/openjs-foundation/cross-project-council/pull/643) 44 | * waiting on a few more examples to round it out. 45 | * Robin there are 3 public ones, will point Tobie at them so they can be included. 46 | 47 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 48 | * Next step is a PR is needed. 49 | * Joe, call to anybody who wants to help out on this one. 50 | 51 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 52 | * no updated this week 53 | 54 | * doc: Governance changes for Collaboration Network [#547](https://github.com/openjs-foundation/cross-project-council/pull/547) 55 | * Asked that Board vote be restarted. 56 | 57 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 58 | * Focus of second part of the meeting for today 59 | 60 | 61 | ## Q&A, Other 62 | 63 | ## Upcoming Meetings 64 | 65 | * **Calendar**: https://calendar.openjsf.org 66 | 67 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 68 | 69 | -------------------------------------------------------------------------------- /meetings/2020/2020-09-29.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-09-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=w1AC18I4JQs&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/652 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Jory Burson (@jorydotcom) 13 | * Eemeli Aro (@eemeli) 14 | * Tobie Langel (@tobie) 15 | * Sara Chipps (@sarajo) 16 | * Timothy Willison (@timmywil) 17 | * Tierney Cyren (@bnb) 18 | * Christopher Hiller (@boneskull) 19 | * Brian Warner (@brianwarner) 20 | * Divy Tolla (@designmoreweb) 21 | * Shelley Vohr (@codebytere) 22 | * Rachel Romoff (@rromoff) 23 | * Mary Marchini (@mmarchini) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | 29 | * AMP Fest Oct 13th 30 | * AMP TSC AMA Oct 14th 31 | * AMP AC nomination closing this Friday 32 | * Public OpenJSF Board meeting this Friday 33 | * No Board updates 34 | 35 | ### Board Meeting Updates 36 | 37 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 38 | 39 | * Michael: Board meeting this week, nothing new that I know of to bring to the board 40 | 41 | 42 | ### openjs-foundation/cross-project-council 43 | 44 | * Clarify the license of the materials in this repo [#651](https://github.com/openjs-foundation/cross-project-council/issues/651) 45 | * No license in the repo right now? 46 | * Possibly MIT but unclear. 47 | * Can we relicense CC? 48 | * MIT is OK for documentation (see https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/IP_POLICY_GUIDANCE.md#1-licensing 49 | * There’s a license in the repo, so we are all set. Closing. 50 | 51 | * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) 52 | * Suggestion to open an issue on the CPC for an ad-hoc meeting. 53 | * What about creating a dedicated Issue template? Lots of +1. 54 | * Broaden access to the calendar? 55 | * Broaden access to the zoom account? Easier to just use the same zoom link as the CPC meeting. 56 | 57 | * Avoid duplication of Impact stage acceptance criteria [#648](https://github.com/openjs-foundation/cross-project-council/pull/648) 58 | * Joe landed 59 | 60 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 61 | * Marked as ready for review now. 62 | * Input welcomed 63 | 64 | * Add examples of successful applications [#643](https://github.com/openjs-foundation/cross-project-council/pull/643) 65 | * In draft, just waiting on some additional examples from Robin 66 | 67 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 68 | * Still needs a volunteer to create PR 69 | 70 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 71 | * still waiting on Brian for first cut 72 | 73 | * doc: Governance changes for Collaboration Network [#547](https://github.com/openjs-foundation/cross-project-council/pull/547) 74 | * vote underway, should complete soon 75 | 76 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 77 | 78 | 79 | ## Q&A, Other 80 | 81 | ## Upcoming Meetings 82 | 83 | * **Calendar**: https://calendar.openjsf.org 84 | 85 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 86 | 87 | -------------------------------------------------------------------------------- /meetings/2020/2020-10-06.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-10-06 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=5NeIZ7omhOM 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/654 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Rachel Romoff (@rromoff) 13 | * Tobie Langel (@tobie) 14 | * Mary Marchini (@mmarchini) 15 | * Darcy Clarke (@darcyclarke) 16 | * Mike Samuel (@mikesamuel) 17 | * Robin Ginn (@rginn) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * Ampfest, Amp TSC AMA coming up: 24 | * https://amp.dev/events/amp-fest-2020/ 25 | * Electron project has put out a usage survey. 26 | 27 | * Agreed to use second half of next meeting to work on simplified proposal process. 28 | 29 | ### Board Meeting Updates 30 | 31 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 32 | 33 | * collaboration space still under vote 34 | * decision made to make the OpenJS World virtual, likely to keep the same dates 35 | 36 | ### openjs-foundation/cross-project-council 37 | 38 | * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) 39 | 40 | Mike Samuel, good to make it clear that the working groups are exploratory/investigatory might help. 41 | Michael: A lot of the overhead is just scheduling. Eemeli’s suggestion addresses that. Could also split meetings: half for CPC business, half for a deep-dive. 42 | Tobie: Timeboxing could help us get CPC business done in less time. Let’s give it a try. 43 | 44 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 45 | * Tobie has next action. 46 | 47 | * Add examples of successful applications [#643](https://github.com/openjs-foundation/cross-project-council/pull/643) 48 | * Waiting on some additional applications from Robin 49 | 50 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 51 | * Just needs somebody to create a PR. 52 | 53 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 54 | * on Brian’s plate, board approved new ICLA template. 55 | * https://github.com/openjs-foundation/cross-project-council/issues/657 56 | 57 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 58 | * Discussed growth plans last week 59 | * Tobie doing the work on the growth plan 60 | * Michael, could be good to loop back to loop at larger overall review once we complete the 61 | work on the growth side. 62 | * Opened dedicated issue for growth plan here: [#658](https://github.com/openjs-foundation/cross-project-council/issues/658). 63 | 64 | * doc: Governance changes for Collaboration Network [#547](https://github.com/openjs-foundation/cross-project-council/pull/547) 65 | * Update from Brian, sounds like board vote is done ! Michael will land 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 | -------------------------------------------------------------------------------- /meetings/2020/2020-10-20.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-10-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=QDr89HEeYkw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/666 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Eemeli Aro (@eemeli) 13 | * Christopher Hiller (@boneskull) 14 | * Robin Ginn (@rginn) 15 | * Sara Chipps (@sarajo) 16 | * Jordan Harband (@ljharb) 17 | * Myles Borins (@MylesBorins) 18 | * Timothy Willison (@timmywil) 19 | * Tobie Langel (@tobie) 20 | * Brian Warner (@brianwarner) 21 | * Anton Molleda (@molant) 22 | 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | * Node.js 15.x release today! 14.x goes LTS next week. 29 | * Upcoming meetings today: Standards & Marketing see calendar.openjsf.org 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * Develop growth plan template [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 38 | 39 | * Adds Growth plan template 40 | [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 41 | 42 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 43 | 44 | * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) 45 | * Discussion around creating issue template. 46 | 47 | * Add examples of successful applications [#643](https://github.com/openjs-foundation/cross-project-council/pull/643) 48 | * Robin, will add another 3 49 | * Looking at creating web form to booth do initial submission as well as submit one to 50 | be used as an example 51 | 52 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 53 | * This is the week for Brian to get it done. 54 | * Hope to have something we can review by the next meeting 55 | 56 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 57 | * covered under discussion on growth plans 58 | 59 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 60 | * covered in section below 61 | 62 | 63 | ### Working session on proposal process 64 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 65 | Consensus: 66 | * remove term staging 67 | * Two phases: Incubating; ready for review/approval 68 | * As many PRs as you’d like through incubating, essentially providing snapshots 69 | * PR to move artifacts into place is the “ready for approval” phase 70 | * A desire for a Definition of Done; perhaps checklist 71 | 72 | Work on this was done in a shared screen and moved to a PR. 73 | 74 | ## Q&A, Other 75 | 76 | ## Upcoming Meetings 77 | 78 | * **Calendar**: https://calendar.openjsf.org 79 | 80 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 81 | -------------------------------------------------------------------------------- /meetings/2020/2020-10-27.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-10-27 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=T2mmObgxZhc 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/672 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Jordan Harband (@ljharb) 13 | * Eemeli Aro (@eemeli) 14 | * Tobie Langel (@tobie) 15 | * Rachel Romoff (@rromoff) 16 | * Shelley Vohr (@codebytere) 17 | * Brain Warner (@brianwarner) 18 | * Christopher Hiller (@boneskull) 19 | * Robin Ginn (@rginn) 20 | * Sara Chipps (@SaraJo) 21 | * Tierney Cyren (@bnb) 22 | * Divy Tolia (@designmoreweb) 23 | * Muhammed Taha Ayan (@estharian) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | 29 | * Next OpenJS AMA with Dojo project 30 | * Check out Halloween sale on certifications 31 | 32 | ### Board Meeting Updates 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/cross-project-council 37 | 38 | Tobie working on the 3 related to Growth plans, hoping to get to it in next few weeks 39 | 40 | * Develop growth plan template 41 | [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 42 | 43 | * \[WIP\] Proposal to remove the Growth Stage 44 | [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 45 | 46 | * Adds Growth plan template 47 | [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 48 | 49 | * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) 50 | 51 | * Add examples of successful applications [#643](https://github.com/openjs-foundation/cross-project-council/pull/643) 52 | * Landed. 53 | * Robin opening issues to make more discoverable 54 | 55 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 56 | * https://github.com/openjs-foundation/cross-project-council/pull/668 57 | 58 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 59 | * still in the queue 60 | 61 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 62 | * current active work is around the Growth plan. 63 | 64 | 65 | ## Q&A, Other 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Calendar**: https://calendar.openjsf.org 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | -------------------------------------------------------------------------------- /meetings/2020/2020-11-03.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-11-03 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=vYRi3cvoSWY 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/674 7 | 8 | ## Present 9 | 10 | * OpenJS Foundation Cross Project Council 11 | * OpenJS Foundation Project Maintainers 12 | * OpenJS Foundation Board of Directors 13 | * Divy Tolia (@designmoreweb) 14 | * Mike Samuel (@mikesamuel) 15 | * Christopher Hiller (@boneskull) 16 | * Robin Ginn (@rginn) 17 | * Joe Sepi (@joesepi) 18 | * Rachel Romoff (@rromoff) 19 | * Eemeli Aro (walking) 20 | * Sendil Kumar (@sendilkumarn) 21 | * Jory Burson (@jorydotcom) 22 | * Myles Borins (@MylesBorins) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | Standards Meeting for today - cancelled 29 | Dojo AMA - Nov. 9 at 10 a.m. PST 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * Develop growth plan template [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 38 | 39 | No Update 40 | 41 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 42 | 43 | AI to Jory - ask the groups in the growth stage to weigh in 44 | 45 | * Should we have a lightweight mechanism to spin off ad hoc CPC working groups? [#649](https://github.com/openjs-foundation/cross-project-council/issues/649) 46 | Merged the related PR #667 47 | 48 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 49 | 50 | AI to Jory - see about transferring this issue / PR 51 | 52 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 53 | 54 | Comments resolved and PR merged 55 | Would be good to update the directory structure, that can be an alternative issue/PR 56 | 57 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 58 | 59 | No Update for today - folks out 60 | 61 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 62 | 63 | May be blocked on some the issues around what to do with Growth plan 64 | May need to change the charter if we do 65 | Question: Do we want to do review processes for all projects? 66 | Lighter weight, survey would be a possibility 67 | Jory volunteers to tackle the broader “non growth” proposals - open a new issue that is broader 68 | Update labels & RM agenda label for now on this particular issue 69 | 70 | 71 | ### Review process discussion 72 | 73 | Questions for projects: 74 | * How are you doing? 75 | * Are you planning anything big 76 | * Are you planning on winding anything down 77 | 78 | 79 | ## Q&A, Other 80 | 81 | ## Upcoming Meetings 82 | 83 | * **Calendar**: https://calendar.openjsf.org 84 | 85 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 86 | -------------------------------------------------------------------------------- /meetings/2020/2020-11-10.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-11-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=LmUa-rbLvbo&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/678 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson 12 | * Sendil Kumar (@sendilkumarn) 13 | * Robin Ginn (@rginn) 14 | * Jordan Harband (@ljharb) 15 | * Dylan Schiemann (@dylans) 16 | * Jory Burson (@jorydotcom) 17 | * Christopher Hiller (@boneskull) 18 | * Brian Warner (@brianwarner) 19 | * Tobie Langel (@tobie) 20 | * Mary Marchini (@mmarchini) 21 | * Rachel Romoff (@rromoff) 22 | * Eemeli Aro (@eemeli) 23 | * Sara Chipps (@Sarajo) 24 | * Abraham Jr. Agiri (@codeekage) 25 | 26 | ## Agenda 27 | 28 | ### Announcements 29 | 30 | ### Board Meeting Updates 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/cross-project-council 35 | 36 | * Develop growth plan template [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 37 | * Joe moved PR to project-status repo; couple more things to do: https://github.com/openjs-foundation/project-status/pull/56 38 | 39 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 40 | * Jory will send FYI to growth projects soon 41 | * Board has already been given an initial FYI with no objection or concern 42 | 43 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 44 | * Replaced by: https://github.com/openjs-foundation/project-status/pull/56 45 | 46 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 47 | * Remaining work (align directories and README text to new process) captured here: [#675](https://github.com/openjs-foundation/cross-project-council/issues/675) 48 | 49 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 50 | * no news here 51 | 52 | * Discussed moving CPC meetings to bi-weekly 53 | 54 | ## Q&A, Other 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Calendar**: https://calendar.openjsf.org 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | -------------------------------------------------------------------------------- /meetings/2020/2020-11-17.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-11-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=cTSPUfewkN0&ab_channel=OpenJSFoundation 6 | 7 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/683 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * Michael Dawson (@mhdawson) 13 | * Rachel Romoff (@rromoff) 14 | * Robin Ginn (@rginn) 15 | * Timothy Willison (@timmywil) 16 | * Jory Burson (@jorydotcom) 17 | * Kris Borchers (@kborchers) 18 | * Divy Tolia (@designmoreweb) 19 | * Kris Borchers (@kborchers) 20 | * Eemeli Aro (@eemeli) 21 | * Shubhra Kar 22 | * Mary Mancini (@mmarchini) 23 | * Tierney Cyren (@bnb) 24 | * Myles Borins (@MylesBorins) 25 | * Abraham Agiri (@codeekage) 26 | 27 | ## Agenda 28 | 29 | ### Announcements 30 | 31 | * guest presentation from Shubhra on the LF Insights platform 32 | * Standards meeting canceled today; Dec1 standards meeting will be a big planning meeting for Standards group 33 | * Marketing meeting later today 34 | * Go vote for OpenJS Panel at SXSW! 35 | * Creative review happening this friday for JSLandia assets 36 | 37 | ### Board Meeting Updates 38 | 39 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 40 | 41 | * no board update, next meeting is 2 weeks from now. Let Michael or Kris know if there is 42 | something that needs to be taken to the board 43 | 44 | ### openjs-foundation/cross-project-council 45 | 46 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 47 | * Agreed to move forward with it starting with the meeting 2 weeks from now on Dec1. 48 | 49 | * Review Individual Supporter program designs [#679](https://github.com/openjs-foundation/cross-project-council/issues/679) 50 | * Note quite ready, will be soon. You can come to meeting on Friday if you want to see once 51 | ready. 52 | 53 | * Growth plan work 54 | * Develop growth plan template [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 55 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 56 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 57 | 58 | * Jory reached out to projects in the Growth stage, the only responses did not express any 59 | concerns. 60 | * Jory will move forward with process or removing growth stage, and updating projects and 61 | inviting projects to apply for a growth plan if they are interested. 62 | 63 | * Simplify proposal process [#635](https://github.com/openjs-foundation/cross-project-council/issues/635) 64 | * Michael closed as work is done. 65 | 66 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 67 | * Brian has working draft, want a few more attorney reviews, hopeful will get that in next day or 68 | two. 69 | 70 | * moved supporter program to stage 3 71 | [#653](https://github.com/openjs-foundation/cross-project-council/pull/653) 72 | * Joe added to agenda. 73 | * Needs to be updated to reflect new directory structure for proposals, but otherwise ready to 74 | land. 75 | 76 | ## Q&A, Other 77 | 78 | ## Upcoming Meetings 79 | 80 | * **Calendar**: https://calendar.openjsf.org 81 | 82 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 83 | -------------------------------------------------------------------------------- /meetings/2020/2020-12-01.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-12-01 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ShPfv9_D9qc&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/686 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Christian Bromann (@christian-bromann) 13 | * Jory Burson (@jorydotcom) 14 | * Kris Borchers (@kborchers) 15 | * Tobie Langel (@tobie) 16 | * Timmy Willison (@timmywil) 17 | * Mike Samuel (@mikesamuel) 18 | * Sendil Kumar(@sendilkumarn) 19 | * Divy Tolia (@designmoreweb) 20 | * Tierney Cyren (@bnb) 21 | * Rachel Romoff (@rromoff) 22 | * Robin Ginn (@rginn) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | * This afternoon, standards Working Group meeting, 2021 strategy, survey sent out to 29 | maintainers 30 | * Organizing next JSLandia (supporter program) meeting 31 | * Program committee meeting also Thursday 32 | 33 | ### Board Meeting Updates 34 | 35 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 36 | * Michael nothing to bring up, there is meeting this Friday let me/Kris know if there is anything 37 | that should be brought up. 38 | * Probably time to start planning for next board seat vote as it comes due in last day of February 39 | Jory will open issue 40 | 41 | ### openjs-foundation/cross-project-council 42 | 43 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 44 | * Joe: recapting consensus, go to every other week, but keep alternative weeks 45 | for planned working meetings. 46 | 47 | * Review Individual Supporter program designs [#679](https://github.com/openjs-foundation/cross-project-council/issues/679) 48 | * Still need to narrow down choices before sharing, hopefully next week. 49 | 50 | * Develop growth plan template [#658](https://github.com/openjs-foundation/cross-project-council/issues/658) 51 | * Closing in favor of [openjs-foundation/project-status#56](https://github.com/openjs-foundation/project-status/pull/56). 52 | 53 | 54 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 55 | * Two Growth project maintainers responded to Jory’s request. They were both for removing the Growth stage. 56 | 57 | * Adds Growth plan template [#647](https://github.com/openjs-foundation/cross-project-council/pull/647) 58 | * Closing in favor of [openjs-foundation/project-status#56](https://github.com/openjs-foundation/project-status/pull/56). 59 | 60 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 61 | * 62 | 63 | ## Q&A, Other 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Calendar**: https://calendar.openjsf.org 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | -------------------------------------------------------------------------------- /meetings/2020/2020-12-08.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-12-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=dzVLUe0_pV8&ab_channel=OpenJSFoundation 6 | 7 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/691 8 | 9 | ## Present 10 | 11 | * Joe Sepi (@joesepi) 12 | * MIchael Dawson (Michael Dawson 13 | * Jordan Harband (@ljharb) 14 | * Christian Bromann (@christian-bromann) 15 | * Mike Samuel (@mikesamuel) 16 | * Sara Chipps (@SaraJo) 17 | * Jory Burson (@jorydotcom) 18 | * Robin Ginn (@rginn) 19 | * Tierney Cyren (@bitnbang) 20 | * Divy Tolia (@designmoreweb) 21 | * Rachel Romoff (@rromoff) 22 | 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | 28 | ### Board Meeting Updates 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/cross-project-council 33 | 34 | * Non normative changes to the charter shouldn't require board reviews [#689](https://github.com/openjs-foundation/cross-project-council/issues/689) 35 | * Approved by board in meeting last Friday 36 | * Michael will add comment to PR and then land. 37 | 38 | * December CPC meetings 39 | * Planned to do one more meeting next week and then cancel for the rest of the year. 40 | 41 | [#688](https://github.com/openjs-foundation/cross-project-council/issues/688) 42 | 43 | * Prepare to open nominations for 2nd Board seat [#687](https://github.com/openjs-foundation/cross-project-council/issues/687) 44 | * Main thing right now is to socialize that to make sure candidates are aware 45 | 46 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 47 | * Plan is to do this starting next year 48 | 49 | * Review Individual Supporter program designs [#679](https://github.com/openjs-foundation/cross-project-council/issues/679) 50 | * Not quite ready for public review, will do some initial review in private session 51 | 52 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 53 | Related issue: https://github.com/openjs-foundation/cross-project-council/issues/692 54 | 55 | 56 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 57 | *Will wait until next time when we have Brian 58 | 59 | 60 | ### openjs-foundation/project-status 61 | 62 | * Adds Growth plan template [#56](https://github.com/openjs-foundation/project-status/pull/56) 63 | mi 64 | 65 | ## Q&A, Other 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Calendar**: https://calendar.openjsf.org 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | -------------------------------------------------------------------------------- /meetings/2020/2020-12-15.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2020-12-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=94YCDPEXpew 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/694 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jory Burson (@jorydotcom) 12 | * Robin Ginn (@rginn) 13 | * Eemeli Aro (@eemeli) 14 | * Sara Chipps (@SaraJo) 15 | * Tobie Langel (@tobie) 16 | * Divy (@designMoreWeb) 17 | * Christopher Hiller (@boneskull) 18 | * Tierney Cyren (@bnb) 19 | * Rachel Romoff (@rromoff) 20 | * Shelley Vohr (@codebytere) 21 | * Jordan Harband (@ljharb) 22 | * Darcy Clarke (@darcyclarke) 23 | * Timothy Willison (@timmywil) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | * Marketing committee 29 | * Standards meeting is transformed into working session 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * December CPC meetings [#688](https://github.com/openjs-foundation/cross-project-council/issues/688) 38 | * Closed 39 | 40 | * Prepare to open nominations for 2nd Board seat [#687](https://github.com/openjs-foundation/cross-project-council/issues/687) 41 | * one seat is up for election early in new year (CPC representative) 42 | * open call for nominees the first meeting of 2021 43 | * This describes the expectations - https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/COMMUNITY_BOARD_SEAT_EXPECTATIONS.md 44 | 45 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 46 | * Suggestion to create a pinned yearly issue inspired from AMP’s Advisory Committee’s https://github.com/ampproject/meta-ac/issues/101 47 | 48 | * Review Individual Supporter program designs [#679](https://github.com/openjs-foundation/cross-project-council/issues/679) 49 | * News on this front, this week. 50 | 51 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 52 | * Tobie also wanted to get feedback from AMP TSC, but won’t be able to get that feedback 53 | until next year. 54 | 55 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 56 | * No update this week. 57 | 58 | ### openjs-foundation/project-status 59 | 60 | * Adds Growth plan template [#56](https://github.com/openjs-foundation/project-status/pull/56) 61 | * blocked on adding process to README.md, Tobie has started on it today. 62 | 63 | ## Q&A, Other 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Calendar**: https://calendar.openjsf.org 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | -------------------------------------------------------------------------------- /meetings/2021/2021-01-05.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-01-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=CC7mjmdEVyw&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/698 7 | 8 | 9 | ## Present 10 | * Robin Ginn (@rginn) 11 | * Joe Sepi (@joesepi) 12 | * Dylan Schiemann (@dylans) 13 | * Tierney Cyren (@bnb) 14 | * Tobie Langel (@tobie) 15 | * Divy Tolia (@designmoreweb) 16 | * Jordan Harband (@ljharb) 17 | * Sara Chipps (@sarajo) 18 | * Sendilkumarn (@sendilkumarn) 19 | * Michael Dawson (@mhdawson) 20 | * Christopher Hiller (@boneskull) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | ### Board Meeting Updates 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/cross-project-council 31 | 32 | * Prepare to open nominations for 2nd Board seat [#687](https://github.com/openjs-foundation/cross-project-council/issues/687) 33 | * New term start 1 day of march 34 | * Vote Complete 9th Feb 35 | * Open Vote 2nd Feb 36 | * Eligible candidates: Current CPC members 37 | * Ones who vote: CPC Voting members 38 | 39 | * In terms of socializing 40 | * Open issue in Repo (Michael to open) 41 | * Send email to CPC list (Jory will send email) 42 | * Remind in each of the CPC meetings 43 | 44 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 45 | * Discussion and agreement. Joe will update calendar. 46 | 47 | * Review Individual Supporter program designs [#679](https://github.com/openjs-foundation/cross-project-council/issues/679) 48 | * This can be closed out. 49 | 50 | * \[WIP\] Proposal to remove the Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 51 | * Tobie is getting feedback from AMP TSC 52 | 53 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 54 | 55 | * Improving Diversity and Inclusion at the OpenJSF 56 | [#699](https://github.com/openjs-foundation/cross-project-council/issues/699) 57 | * Link shared by Robin: https://openjsf.org/blog/training-course-on-diversity-in-open-source 58 | * Link shared by Robin: https://inclusivenaming.org 59 | * Prompt from Tierney: do we have materials to give to member companies which could also be used by non-member companies to show how leadership provides value in open source projects; specifically around URM being able to show their work/effort/participation 60 | * Robin will pull data from LF Insights 61 | 62 | 63 | ### openjs-foundation/project-status 64 | 65 | * Adds Growth plan template [#56](https://github.com/openjs-foundation/project-status/pull/56) 66 | * Tobie should be able to wrap that up this week. 67 | 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 | -------------------------------------------------------------------------------- /meetings/2021/2021-01-19.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-01-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ERC3pyC3aIc&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/706 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Eemeli Aro (@eemeli) 13 | * Kris Borchers (@kborchers) 14 | * Mike Samuel (@mikesamuel) 15 | * Rachel Romoff (@rromoff) 16 | * Timothy Willison (@timmywil) 17 | * Tierney Cyren (@bnb) 18 | * Mary Marchini (@mmarchini) 19 | * Shelley Vohr (@codebytere) 20 | * Robin Ginn (@rginn) 21 | * Brian Warner (@brianwarner) 22 | 23 | ## Agenda 24 | 25 | ### Announcements 26 | 27 | * Speaker submissions open through Mid Feb for OpenJS world 28 | * Node.js user survey open -https://www.surveymonkey.com/r/nodesurvey21 29 | 30 | ### Board Meeting Updates 31 | 32 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 33 | 34 | * Board meeting this week, let Michael/Kris know if there is anything you want us to bring up. 35 | 36 | ### openjs-foundation/cross-project-council 37 | 38 | * Improving Diversity and Inclusion at the OpenJSF [#699](https://github.com/openjs-foundation/cross-project-council/issues/699) 39 | 40 | * Move CPC meetings to bi-weekly cadence [#680](https://github.com/openjs-foundation/cross-project-council/issues/680) 41 | 42 | * Prepare to open nominations for 2nd Board seat [#687](https://github.com/openjs-foundation/cross-project-council/issues/687) 43 | Kris has declining availability. Happy to talk to people who might seek that seat. 44 | PR discussing opening the election: https://github.com/openjs-foundation/cross-project-council/issues/707 45 | 46 | * Google Summer of Code 2021 [#673](https://github.com/openjs-foundation/cross-project-council/issues/673) 47 | If applying as a project and can support a mentee, go ahead. Can help smaller projects. 48 | Umbrella projects get extra slots. 49 | It’s a shared slot, so we might have to figure out how to allocate mentees if demand > availability. 50 | Let’s not submit at deadline (19 Feb) as we’ve done in past. Let’s aim for first two weeks of Feb. 51 | JS: Let’s put this on projects’ radars via slack. 52 | 53 | * Remove Growth Stage [#650](https://github.com/openjs-foundation/cross-project-council/pull/650) 54 | Could use more eyes 55 | 56 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 57 | BW: Remediation commit support makes it easier to use DCO if DCO check failed. Fewer abandoned commits. Discussed with probot maintainer, waiting for guidance. 58 | Three pillars 59 | Explaining when to use which of (DCO, CLA) 60 | How to use CLA 61 | Probot integration guidance 62 | 63 | ### openjs-foundation/project-status 64 | 65 | * Adds Growth plan template [#56](https://github.com/openjs-foundation/project-status/pull/56) 66 | 67 | ## Next week's working session 68 | 69 | Are there any initiatives or agenda items that we should use a working session to further progress on? 70 | 71 | ## Q&A, Other 72 | 73 | ## Upcoming Meetings 74 | 75 | * **Calendar**: https://calendar.openjsf.org 76 | 77 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 78 | -------------------------------------------------------------------------------- /meetings/2021/2021-03-30.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-03-30 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=xcgxQbykwCg 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/737 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Sendil Kumarn (@sendilkumarn) 13 | * Jordan Harband (@ljharb) 14 | * Anton Molleda (@molant) 15 | * Tobie Langel (@tobie) 16 | * Mike Samuel (@mikesamuel) 17 | * Sara Chipps (@SaraJo) 18 | * Rachel Romoff (@rromoff) 19 | * Timmy Willison (@timmywil) 20 | * Parris Lucas (@GrooveCS) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | * Upcoming Q&A with WebDriver IO team 27 | * Congratulations on NVM release! 28 | * Discounts on Node trainings and certifications - https://twitter.com/nodejs/status/1376547426375401473 29 | * Book club was fun! Come to the next one! 30 | * Node - Next 10 survey! https://twitter.com/nodejs/status/1372253048173658112 31 | 32 | ### Board Meeting Updates 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/summit 37 | 38 | * Collaborator summit this year ? [#306](https://github.com/openjs-foundation/summit/issues/306) 39 | * per discussion last session and today, updated repo issue with status. We are not planning to co-locate or co-time the summit with the OpenJS World event at this time. We would like to brainstorm additional options for a summit in 2020. 40 | 41 | ### openjs-foundation/cross-project-council 42 | 43 | * Private slack channel for Node.js build team machine management [#729](https://github.com/openjs-foundation/cross-project-council/issues/729) 44 | * Closed 45 | 46 | * doc: add travel fund allocation for 2021 [#725](https://github.com/openjs-foundation/cross-project-council/pull/725) 47 | * Waiting on an update from the board 48 | 49 | * Rename master branches [#711](https://github.com/openjs-foundation/cross-project-council/issues/711) 50 | * We can close this issue 51 | * Discussion ensued about tracking projects which had updated their branch names; we opted not to track at this time 52 | 53 | * Improving Diversity and Inclusion at the OpenJSF [#699](https://github.com/openjs-foundation/cross-project-council/issues/699) 54 | * Jory updated on the CoC process improvement work 55 | * Tobie updated on the DEI work, including a survey. Tobie will organize a meeting for interested parties for further discussions. 56 | 57 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 58 | * Brian still working on this with ProBot DCO team 59 | 60 | ## Next week's working session 61 | 62 | Are there any initiatives or agenda items that we should use a working session to further progress on? 63 | * Discussion about tracking/planning future Working session meetings - jory to open new issues for April 6 and 20 th meetings 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 | -------------------------------------------------------------------------------- /meetings/2021/2021-04-13.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-04-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=mYrK77Eeih8&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/743 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Eemeli Aro (@eemeli) 12 | * Mike Samuel (@mikesamuel) 13 | * Tobie Langel (@tobie) 14 | * Michael Dawson (@mhdawson) 15 | * Tierney Cyren (@bnb) 16 | * Jory Burson (@jorydotcom) 17 | * Jordan Harband (@ljharb) 18 | * Rachel Romoff (@rromoff) 19 | * Robin Ginn (@rginn) 20 | * Darcy Clarke (@darcyclarke) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | LiFT Scholarships are available now: https://openjsf.org/blog/lift-scholarship 26 | Link to Tweet: https://twitter.com/openjsf/status/1381983199488794625?s=20 27 | 28 | Standards meeting happening today (rescheduled) at 2pm ET. 29 | 30 | Jory is now AC Rep at W3C 31 | 32 | 33 | ### Board Meeting Updates 34 | 35 | 36 | 37 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 38 | 39 | ### openjs-foundation/summit 40 | 41 | * Collaborator summit this year ? [#306](https://github.com/openjs-foundation/summit/issues/306) 42 | 43 | ### openjs-foundation/cross-project-council 44 | 45 | * doc: add travel fund allocation for 2021 [#725](https://github.com/openjs-foundation/cross-project-council/pull/725) 46 | * CPC should work on a proposal for spending this funds. Including process on how to allocate it. Decision to file new issue. 47 | 48 | * Improving Diversity and Inclusion at the OpenJSF [#699](https://github.com/openjs-foundation/cross-project-council/issues/699) 49 | Tobie to coordinate some follow up meetings. Anticipates hearing from survey vendors next week. Vendor recommendations include working with other orgs to lighten to cost. 50 | 51 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 52 | 53 | * Update on [Package Vulnerability Management & Reporting Collaboration Space](https://github.com/openjs-foundation/pkg-vuln-collab-space) 54 | * @darcyclarke planning kick-off meeting with initial members (ref. [tracking issue](https://github.com/openjs-foundation/pkg-vuln-collab-space/issues/1)) & sync’d up last week with @jorydotcom / @rromoff for future marketing/comms 55 | * @rromoff has a blog post ready once we determine day/time of meeting 56 | 57 | 58 | ## Next week's working session 59 | 60 | Are there any initiatives or agenda items that we should use a working session to further progress on? 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 | -------------------------------------------------------------------------------- /meetings/2021/2021-05-25.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-05-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=pF_7tFjQE7g 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/765 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Jory Burson (@jorydotcom) 13 | * Dylan Schiemann (@dylans) 14 | * Robin Ginn (@rginn) 15 | * Rachel Romoff (@rromoff) 16 | * Sara Chipps (@sarajo) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | * OpenJS World!!! 22 | 23 | 24 | ### Board Meeting Updates 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/cross-project-council 29 | 30 | * approve Node.js TSC Charter revisions [#762](https://github.com/openjs-foundation/cross-project-council/issues/762) 31 | * Just waiting now for 14 days as required by -https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/GOVERNANCE.md#approving-project-charters 32 | * Please review/comment as would be good to have more +1s 33 | 34 | * move `nvm` from Incubating to At-Large [#760](https://github.com/openjs-foundation/cross-project-council/pull/760) 35 | * Was ready to land, landed. Yay! 36 | 37 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 38 | * List the items we want to be reminded about / capture through automated issues (director elections, voting CPC member elections, etc). 39 | * Perhaps do this as part of a working CPC meeting 40 | 41 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 42 | * Propose a working session on this as well - using Brian’s PR as a starting point 43 | 44 | * Slack Moderators - Volunteers requested [#747](https://github.com/openjs-foundation/cross-project-council/issues/747) 45 | * Jory provided some of the details of the ask. 46 | 47 | * doc: add travel fund allocation for 2021 [#725](https://github.com/openjs-foundation/cross-project-council/pull/725) 48 | * approved and open for long enough - Michael merged 49 | 50 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 51 | * still underway, no update. 52 | 53 | 54 | ## Next week's working session -- CANCELLING (to focus on OpenJS World) 55 | 56 | Are there any initiatives or agenda items that we should use a working session to further progress on? 57 | 58 | ## Q&A, Other 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | -------------------------------------------------------------------------------- /meetings/2021/2021-06-08.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-06-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=S66SZPmg0-k 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/766 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn (@rginn) 12 | * Rachel Romoff (@rromoff) 13 | * Timmy Willison (@timmy4wil) 14 | * Divy Tolia (@designmoreweb) 15 | * Jory Burson (@jorydotcom) 16 | * Michael Dawson (@mdawson) 17 | * Tobie Langel (@tobie) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * Quieter week 24 | * Robin has a keynote where she will talk about OpenJS and such 25 | 26 | ### Board Meeting Updates 27 | 28 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 29 | * Next board meeting is June 25th 30 | 31 | ### openjs-foundation/cross-project-council 32 | 33 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 34 | 35 | Keeping the issue open for now; looking to do something like create a GH action to help prompt procedural issue. This is also an issue we are looking for help on. 36 | 37 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 38 | * tackle in next working session on June 15. See below 39 | 40 | * Slack Moderators - Volunteers requested [#747](https://github.com/openjs-foundation/cross-project-council/issues/747) 41 | * Now have 7 people on the @moderator group in moderation 42 | * Can now close 43 | 44 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 45 | * No update this week - Brian is out on vacation! 46 | 47 | ## Next week's working session 48 | 49 | Are there any initiatives or agenda items that we should use a working session to further progress on? 50 | 51 | June 15th working meeting: tackle [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 52 | 53 | ## Q&A, Other 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Calendar**: 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | -------------------------------------------------------------------------------- /meetings/2021/2021-06-22.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-06-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=mLITjkPxAcg 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/768 7 | 8 | ## Present 9 | 10 | * Robin Ginn (@rginn) 11 | * Sara Chipps (@sarajochipps) 12 | * Eemeli Aro (@eemeliaro) 13 | * Jory Burson (@jorydotcom) 14 | * Joe Sepi (@joesepi) 15 | * Rachel Romoff (@rromoff) 16 | * Michael D’awesome (@mhdawson) 17 | * Jordan Harband (@ljharb) 18 | * Divy Tolia (@designmoreweb) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | * This Friday is board meeting, public session check out the calendar 25 | * 5 ECMA JavaScript related specs approved today, several people from the OpenJS 26 | community were involved. 27 | * LF Event in China - Robin will be speaking & excited to share the JS news there! 28 | 29 | ### Board Meeting Updates 30 | 31 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 32 | 33 | * No update - board meeting this Friday! 34 | 35 | ### openjs-foundation/cross-project-council 36 | 37 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 38 | * No update this week. 39 | 40 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 41 | * No update this week 42 | 43 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 44 | 45 | * Jory provided a recap of the conversation from the working meeting last tuesday. The ask today is to the CPC to confirm the direction of this work so we can expand on more details. Sara asked whether we had put bounds around the amount each of the programs might fund. The group agreed this would be good to calculate, noting that the travel fund in the past has only spent around $30k. The group discussed taking a more experimental approach to test where the spend is. 46 | 47 | 48 | ## Next week's working session 49 | 50 | Are there any initiatives or agenda items that we should use a working session to further progress on? 51 | 52 | https://github.com/openjs-foundation/cross-project-council/issues/739 53 | 54 | ## Q&A, Other 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Calendar**: 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | -------------------------------------------------------------------------------- /meetings/2021/2021-07-06.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-07-06 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=BqnDbv_Vda0 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/771 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Eemeli Aro (@eemeli) 12 | * Michael Dawson (@mhdawson) 13 | * Robin Ginn (@rginn) 14 | * Sara Chipps (@sarajo) 15 | * Tierney Cyren (@bnb) 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | * OpenJS Program committee will pick back up in August 22 | * 23 | 24 | ### Board Meeting Updates 25 | 26 | * Huge event 🎉 celebration 27 | * Community fund discussion 28 | * Discussion around 2022 OpenJS World event - June 7, 8 in Austin 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/cross-project-council 34 | 35 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 36 | 37 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 38 | 39 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 40 | 41 | ## Next week's working session 42 | 43 | * Do Community Fund working session 44 | 45 | 46 | Are there any initiatives or agenda items that we should use a working session to further progress on? 47 | 48 | ## Q&A, Other 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | -------------------------------------------------------------------------------- /meetings/2021/2021-07-20.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-07-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=fLTuNBJ9-Po 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/776 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Robin Ginn (@rginn) 13 | * Sara Chipps (@sarajo) 14 | * Tierney Cyren (@bnb) 15 | * Nathan Walker (@wwwalkerrun - NativeScript) 16 | * Eemeli Aro (@eemeli) 17 | * Eduardo Speroni (@Eduardo Speroni - NativeScript) 18 | * Rachel Romoff (@rromoff) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | Marketing Committee Meeting today - after these messages 25 | Program committee for OpenJS World 2021 is happening! 26 | Book club call is upcoming 27 | 28 | ### Board Meeting Updates 29 | 30 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 31 | * Board meeting this Friday, nothing to bring to board that we are aware of. Let Michael/Sara 32 | know if we’ve missed something. 33 | 34 | ### openjs-foundation/cross-project-council 35 | 36 | * CPC Chairperson election 2021 [#772](https://github.com/openjs-foundation/cross-project-council/issues/772) 37 | * opening nominations today, start elections Aug 3 38 | * Jory volunteered to take point for accepting nominations, running vote etc. 39 | 40 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 41 | * Would be great if we had something to create issues on a schedule 42 | * Was mentioned that possibly pkgjs/meet might be a good starting point. 43 | 44 | * Provide implementation guidance for DCO/CLA 45 | [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 46 | * No update. Bot is looking for new sources of support (code review). 47 | 48 | * Clarify 49 | [#778](https://github.com/openjs-foundation/cross-project-council/issues/778) 50 | * Is having a DCO or CLA required? CPC says yes; Robin or Michael will find the source that sets the requirement. 51 | * Yes as per https://github.com/openjs-foundation/cross-project-council/blob/HEAD/governance/IP_POLICY_GUIDANCE.md 52 | * Text of the CLA is the same across projects; exceptions must be cleared by Board 53 | * OpenJS Foundation has strong preference for certain tools. 54 | * Project to upgrade OpenJSF Projects on JSF CLA Bot is slow going but on the books 55 | 56 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 57 | * Lift scholarships provide a good model to follow, recommending that we leverage the 58 | approach and brand. 59 | * Recommend we start with 20 scholarships 60 | * Needs based, honor system 61 | * Thoughts on categories 62 | * Diverse groups 63 | * Do-gooders 64 | * Robin is draft proposal 65 | * LF found worked well to have 2 people on initial review before it went to larger group for final 66 | approval (CPC private vote). Review would be private. 67 | * Next step is proposal from Robin 68 | 69 | ## Next week's working session 70 | 71 | * Next week’s working session will be: 72 | New Collaboration Spaces 73 | 74 | * Meta scheduling issue: https://github.com/openjs-foundation/cross-project-council/issues/739 75 | 76 | ## Q&A, Other 77 | 78 | ## Upcoming Meetings 79 | 80 | * **Calendar**: 81 | 82 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 83 | -------------------------------------------------------------------------------- /meetings/2021/2021-08-31.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-08-31 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=xG05PDZ8JSk 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/792 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Rich Trott (@trott) 13 | * Tobie Langel (@tobie) 14 | * Michael Dawson (@mdawson) 15 | * Tierney Cyren (@bnb) 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | * Jory to add Rich to contact list(s) & update GH 21 | * News items - send to Robin, Jory, Brian &/or #pr-marketing channel in GH 22 | * OpenJS World Programming Committee Meetings - every other week on Thursdays 23 | * Book Club - Sept. 7 24 | * EasyCLA migrations happening for projects! 25 | * Thank you for the Cookies 26 | * Elections - last day! 27 | * Node JS Security releases, yay! 28 | 29 | ### Board Meeting Updates 30 | 31 | * Board meeting for this month cancelled 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/cross-project-council 36 | 37 | * \[WIP\] Start listing documents maintained by the CPC [#789](https://github.com/openjs-foundation/cross-project-council/pull/789) 38 | * WIP, please add those that you think should be included. 39 | 40 | 41 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 42 | * Next steps agreed, just need to do them 43 | 44 | * Kickoff election process for Secondary CPC Director. [#784](https://github.com/openjs-foundation/cross-project-council/issues/784) 45 | * Final day is today, results will be announced either tomorrow or once final voters have voted. 46 | 47 | * Simplify CoC page [#782](https://github.com/openjs-foundation/cross-project-council/pull/782) 48 | * Board review happening async due to cancelled meeting 49 | 50 | * Build stronger ties between At Large maintainers and their CPC Rep [#761](https://github.com/openjs-foundation/cross-project-council/issues/761) 51 | * checkboxes complete 52 | * We should review in 1 quarter 53 | * Possible close once the doc for 758 is created 54 | 55 | * Reminders for long term events [#758](https://github.com/openjs-foundation/cross-project-council/issues/758) 56 | * Joe is going to doc where we can add things 57 | * Review as Chair in each meeting 58 | 59 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 60 | * Have proposal for Lift Scholarships, please comment, otherwise will be rolling out soon 61 | * Next working session will be talking about community fund (what else can we do) 62 | 63 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 64 | * Long conversation about this one last time. Jory Briefed Brian who was not able to make it 65 | * Talking to Mike Dolan and LF IT to explore feasibility of taking maintenance of the tool 66 | (Probot DCO) 67 | * Link to EasyCLA test repo from IP policy? 68 | 69 | ## Next week's working session 70 | 71 | * Sept 7 working session will be more work on Community Fund proposal ideas 72 | * Notes from Previous Working Session - the “supporting the nebraska projects” 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 | -------------------------------------------------------------------------------- /meetings/2021/2021-10-26.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-10-26 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/dtSodnIB1qQ 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/806 7 | 8 | ## Present 9 | 10 | * Jory Burson (@jorydotcom) 11 | * Jordan Harband (@ljharb) 12 | * Michael Dawson (@mhdawson) 13 | * Rich Trott (@trott) 14 | * Eemeli Aro (@eemeli) 15 | * Tierney Cyren (@bnb) 16 | * Dylan Schiemann (@dylans) 17 | * Parris Lucas (@GrooveCS) 18 | 19 | ## Agenda 20 | 21 | Private Session 22 | 23 | ### Announcements 24 | 25 | * jQuery Story in New Stack - check it out! https://web.archive.org/web/20221205165626/https://thenewstack.io/why-outdated-jquery-is-still-the-dominant-javascript-library/ 26 | * Reminder - attend Programming Committee calls on Thursdays to get involved with OpenJS World planning 27 | * Node.js v. 17 release out last week, Node 16 moving to LTS today! 28 | * Thank you to the LiFT applicants and to the Node Mentorship team for reviewing - hope to have announcements out for receipients soon! 29 | * Reminder: Board meeting moved to Monday, Nov. 1 30 | * Working session last week was cancelled; Next week's session is 'Tech Strategy' 31 | 32 | ### Board Meeting Updates 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/cross-project-council 37 | 38 | Regular agenda was tabled due to attendance. Group shared some private project announcements then concluded. 39 | 40 | ## Next week's working session 41 | 42 | Are there any initiatives or agenda items that we should use a working session to further progress on? 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 | -------------------------------------------------------------------------------- /meetings/2021/2021-11-23.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-11-23 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=fBAb8cCXGrw 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/812 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Robin Ginn (@rginn) 13 | * Jory Burson (@jorydotcom) 14 | * Tierney Cyren (@bnb) 15 | * Mike Samuel (@mikesamuel) 16 | * Timothy Willison (@timmywil) 17 | * Tobie Langel (@tobie) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * OpenJS World Announcements - starting to invite keynotes, CFP out early to mid-January, Sponsorship prospectus will be out soon. 24 | 25 | ### Board Meeting Updates 26 | 27 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 28 | * No update this week 29 | 30 | ### openjs-foundation/cross-project-council 31 | 32 | * \[WIP\] Start listing documents maintained by the CPC [#789](https://github.com/openjs-foundation/cross-project-council/pull/789) 33 | * No update 34 | 35 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 36 | * No update 37 | * Robin has completed an audit of all the projects 38 | * https://github.com/openjs-foundation/cross-project-council/issues/786#issuecomment-900562549 39 | 40 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 41 | * Need documentation / housekeeping work around the specific funding areas (travel, Diversity travel and related, thank you program, Scholarship, etc). 42 | * Propose Working Session to clarify 43 | * Propose closing this issue to focus on sub-issues with more granularity 44 | 45 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 46 | * things are happening. More news soon 47 | 48 | ## Next week's working session 49 | 50 | Are there any initiatives or agenda items that we should use a working session to further progress on? 51 | 52 | ## Q&A, Other 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Calendar**: 57 | 58 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 59 | 60 | -------------------------------------------------------------------------------- /meetings/2021/2021-12-07.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2021-12-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/818 7 | 8 | ## Present 9 | 10 | * Jory Burson (@jordotcom) 11 | * Robin Ginn (@rginn) 12 | * Jordan Harband (@ljharb) 13 | * Tierney Cyren (@bnb) 14 | * Alix Robinson 15 | * Eemeli Aro (@eemeli) 16 | * Michael Dawson (@mhdawson) 17 | * Rich Trott (@trott) 18 | * Tobie Langel (@tobie) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | * Welcome Alix Robinson !!! New Marketing team member for OpenJS!!! 25 | * Last week or two of meetings - 26 | 27 | ### Board Meeting Updates 28 | 29 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 30 | 31 | Today is the last day for Cyber Monday Training & Certification Sales 32 | Event in June in Austin moving ahead as planned 33 | 34 | ### openjs-foundation/cross-project-council 35 | 36 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 37 | 38 | Introduced by Michael Dawson. Do we have a tool for license checking? 39 | LFX Security, Fossa are available tools; https://github.com/oss-review-toolkit/ort 40 | Desire: 1 or more easy ways to identify actions/issues for projects 41 | “As an OSS Maintainer, how do we have some automation that helps us with due diligence on …” 42 | Focus on the initial need - Licenses for project repos rather than dependencies 43 | Quick script to do initial analysis on all projects 44 | Actions 45 | Post info on LFX security tool and check to see if it handles the ask 46 | Create machine readable doc (json?) with orgs in project within the OpenJS repo 47 | Jory to check if there are any other recommend licence check tools 48 | 49 | * \[WIP\] Start listing documents maintained by the CPC [#789](https://github.com/openjs-foundation/cross-project-council/pull/789) 50 | * no update this week 51 | * Ideally have multiple entry points; README + other repos? 52 | * “Spring Cleaning” working session? 53 | 54 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 55 | * no update this week 56 | 57 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 58 | * Discussed pulling this out into a separate repo 59 | * Gist from last working session - https://hackmd.io/RnT9C7ClT_O3ZcNfuDweIw 60 | 61 | * Provide implementation guidance for DCO/CLA [#632](https://github.com/openjs-foundation/cross-project-council/issues/632) 62 | * No new update this week. LF IT is working on bringing in Probot as a supporting tool. 63 | 64 | ## Next week's working session 65 | 66 | Tech Strategy 67 | 68 | Are there any initiatives or agenda items that we should use a working session to further progress on? 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 | -------------------------------------------------------------------------------- /meetings/2022/2022-01-04.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-01-04 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=mKyqmBVJf_o&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/819 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Robin Ginn 13 | * Alix Robinson 14 | * Jordan Harband 15 | * Sara Chipps (@sarajo) 16 | 17 | ## Agenda 18 | 19 | ### Announcements 20 | 21 | * OpenJS World is still moving forward. Staying on top of COVID concerns. Updated site with some speakers. Registrations are open. Sponsorships are open. Collab Summit will be the last two days of the week. CFPs will open next week. 22 | 23 | * OpenSSF announced the MFA project. Blog on OpenSSF Site 24 | 25 | * Article on Bloomberg about White House meeting next week with tech folks on security. LF will be there. 26 | 27 | ### Board Meeting Updates 28 | 29 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 30 | 31 | * No updates this week. 32 | 33 | ### openjs-foundation/cross-project-council 34 | 35 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 36 | * Update from Brian (via Robin). Linux foundation does not have anything in LFX tool yet, but 37 | in roadmap. 38 | * Jordan - repo-report (done through major league hacks), scans all repos that he has access to and. Could add licenses. 39 | * Michael, that would be a great starting point. 40 | 41 | * Track issues outside of Dates-and-Reminders.md [#804](https://github.com/openjs-foundation/cross-project-council/pull/804) 42 | * Landed 43 | * Joe created a new issue to add review of Dates and reminders to CPC meeting template. 44 | 45 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 46 | * Audit done. 47 | * Next step: use working session to define process template / language for projects. 48 | 49 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 50 | * 51 | 52 | OpenJS World 2022 53 | Explore Saturday space for project Collab Summit because TC39 will overlap on Thursday. 54 | 55 | ## Next week's working session 56 | 57 | Are there any initiatives or agenda items that we should use a working session to further progress on? 58 | 59 | | Jan. 11 | Working Meeting | Community Fund | 60 | | Jan. 18 | Regular | | 61 | | Jan. 25 | Working Meeting | Tech Strategy | 62 | | Feb. 1 | Regular | | 63 | | Feb. 8 | Working Meeting | Clarify requirements around CoC violation | 64 | | Feb. 15 | Regular | | 65 | | Feb. 22 | Working Meeting | "Repo Clean-up" | 66 | 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 | 76 | -------------------------------------------------------------------------------- /meetings/2022/2022-02-01.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-02-01 2 | 3 | ## Links 4 | 5 | * **Recording**: http://www.youtube.com/watch?v=rFkZVbuYcA4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/828 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Christian Bromann (@christian-bromann) 12 | * Robin Ginn 13 | * Joe Sepi 14 | * Nick O’Leary 15 | * Rich Trott 16 | * Alix Robinson 17 | * Eemeli Aro 18 | * Jordan Harband 19 | * Tobie Langel 20 | * Myles Borins (OpenJS board) 21 | * Sonal Bhoraniya (OpenJS board) 22 | * Sara Chipps 23 | * Alex Liu (OpenJS board) 24 | 25 | ## Agenda 26 | 27 | ### Announcements 28 | 29 | ### Board Meeting Updates 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/cross-project-council 34 | 35 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 36 | 37 | 38 | * 2022 Google Summer of Code [#821](https://github.com/openjs-foundation/cross-project-council/issues/821) 39 | * deferred since ran out of time 40 | * Add Dates and Reminders to biweekly CPC Meeting template [#820](https://github.com/openjs-foundation/cross-project-council/issues/820) 41 | * deferred since ran out of time 42 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 43 | * deferred since ran out of time 44 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 45 | * deferred since ran out of time 46 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 47 | * deferred since ran out of time 48 | 49 | ## Next week's working session 50 | 51 | Are there any initiatives or agenda items that we should use a working session to further progress on? 52 | 53 | ## Dates and Reminders 54 | 55 | Please review regularly our list of dates and reminders: 56 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 57 | 58 | ## Q&A, Other 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | 66 | 67 | -------------------------------------------------------------------------------- /meetings/2022/2022-02-15.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-02-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ba_D31w_0MU 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/831 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Rich Trott (@Trott) 13 | * Jordan Harband (@ljharb) 14 | * Eemeli Aro 15 | * Tierney Cryen 16 | * Robin Ginn 17 | * Christian Bromann <@christian-bromann> 18 | * Tobie Langel (@tobie) 19 | * Sara Chipps 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | * Robin 26 | - Jordan new board representative for Silver members 27 | - Gold and end user representatives re-elected 28 | - OpenJS World CFP extended to Feb 25 (week end likely ok as well) 29 | - Node.js trademark transferred to OpenJS Foundation from Joyent - Yay! 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 38 | * Held working session on this last week 39 | * Discussed if there some minimum requirements to consider 40 | 41 | * Going to set up slack channel on security (just called security) 42 | * Planned to have follow up session 43 | * Joe could we use the working session next week - 12 ET? 44 | 45 | * 2022 Google Summer of Code [#821](https://github.com/openjs-foundation/cross-project-council/issues/821) 46 | * Electron is working to get involved and hoping to have a couple of mentors 47 | * 48 | 49 | * Add Dates and Reminders to biweekly CPC Meeting template [#820](https://github.com/openjs-foundation/cross-project-council/issues/820) 50 | * Plan is to add today links to the meeting template. 51 | 52 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 53 | * Next step is for LF to respond on whether they are going to take ownership for providing 54 | Something. Added that to the issue 55 | 56 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 57 | * Tobie has some notes, will turn into text that will share in issue or doc and we can discuss in 58 | the next meeting. 59 | 60 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 61 | * 62 | 63 | 64 | 65 | ## Next week's working session 66 | 67 | Are there any initiatives or agenda items that we should use a working session to further progress on? 68 | 69 | CPC Meeting schedule issue: https://github.com/openjs-foundation/cross-project-council/issues/816 70 | 71 | CPC Meeting schedule says "Repo Clean-up". Is that what we want to be doing next working session? 72 | 73 | 74 | ## Dates and Reminders 75 | 76 | Please review regularly our list of dates and reminders: 77 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | 88 | 89 | -------------------------------------------------------------------------------- /meetings/2022/2022-03-01.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-03-01 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/834 7 | 8 | ## Present 9 | 10 | * Christian Bromann (@christian-bromann) 11 | * Robin Ginn (@rginn) 12 | * Rich Trott 13 | * Brian Warner 14 | * Mike Samuel (@mikesamuel) 15 | * Alix Robinson 16 | * Jordan Harband 17 | * Ib Green 18 | * Chris Gervang 19 | * Michael Dawson (@mhdawson) 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | ### Board Meeting Updates 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/cross-project-council 30 | 31 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 32 | * 2022 Google Summer of Code [#821](https://github.com/openjs-foundation/cross-project-council/issues/821) 33 | * Add Dates and Reminders to biweekly CPC Meeting template [#820](https://github.com/openjs-foundation/cross-project-council/issues/820) 34 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 35 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 36 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 37 | 38 | ## Next week's working session 39 | 40 | Are there any initiatives or agenda items that we should use a working session to further progress on? 41 | 42 | ## Dates and Reminders 43 | 44 | Please review regularly our list of dates and reminders: 45 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | -------------------------------------------------------------------------------- /meetings/2022/2022-03-15.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-03-15 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=akclV_-I_ZU 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/837 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Alix Robinson 12 | * Joe Sepi (@joesepi) 13 | * Tierney Cyren (@bnb) 14 | * Tobie Langel (@tobie) 15 | * Rich Trott (@Trott) 16 | * Jordan Harband (@ljharb) 17 | * Eemeli Aro (@eemeli) 18 | * Jory Burson (@jorydotcom) 19 | * Christian Bromann (@christian-bromann) 20 | * Parris Lucas (@GrooveCS) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | * OpenJS Foundation Marketing Committee - later today 26 | * OpenJS World Program Committee - happens every thursday 27 | * OpenJS Board Meeting - week from friday 28 | 29 | ### Board Meeting Updates 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/cross-project-council 34 | 35 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 36 | * Joe will take action items 37 | 38 | * Add Dates and Reminders to biweekly CPC Meeting template [#820](https://github.com/openjs-foundation/cross-project-council/issues/820) 39 | * closed in favor of the open issue on missing dates. PR coming from Joe 40 | 41 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 42 | * No update 43 | 44 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 45 | * Tobie is working on PR 46 | 47 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 48 | * No updates; suggestion is for folks to help flesh out the comm fund repo as well. 49 | 50 | 51 | 52 | ## Next week's working session 53 | 54 | Next working session is “Repo cleanup” 55 | 56 | ## Dates and Reminders 57 | 58 | Please review regularly our list of dates and reminders: 59 | https://github.com/openjs-foundation/cross-project-council/blob/HEAD/Dates-and-Reminders.md 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 | -------------------------------------------------------------------------------- /meetings/2022/2022-03-29.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-03-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=hXDy-7DnbU8 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/849 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Robin Ginn (@rginn) 12 | * Michael Dawson (@mhdawson 13 | * Timmy Willison (@timmywil) 14 | * Christian Bromann (@christian-bromann) 15 | * Rich Trott (@Trott) 16 | * Tobie Langel (@tobie) 17 | * Alix Robinson 18 | * Jory Burson (@jorydotcom) 19 | * Sara Chipps (@Sarajo) 20 | 21 | ## Agenda 22 | 23 | ### Announcements 24 | 25 | OpenJS World 26 | * CFP notification extended 27 | * Check for speakers on site 28 | * We have scholarships available 29 | * Live band karaoke will be a part of the event 30 | * Hybrid options are being fleshed out for the event, not for live band karaoke 31 | 32 | ### Board Meeting Updates 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/cross-project-council 37 | 38 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 39 | * Plan to start things up in next couple of days 40 | 41 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 42 | * Waiting on LF 43 | * Met with LF team who will start in Mid April to start, will use Joran’s tool as a starting point 44 | 45 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 46 | * No update this week 47 | 48 | * Create proposal(s) for the Community Fund [#756](https://github.com/openjs-foundation/cross-project-council/issues/756) 49 | * progress made in last working session. PR created for awards - https://github.com/openjs-foundation/community-fund/pull/11 50 | ## Next week's working session 51 | 52 | Are there any initiatives or agenda items that we should use a working session to further progress on? 53 | 54 | ## Dates and Reminders 55 | 56 | Please review regularly our list of dates and reminders: 57 | https://github.com/openjs-foundation/cross-project-council/blob/HEAD/Dates-and-Reminders.md 58 | 59 | ## Q&A, Other 60 | 61 | ## Upcoming Meetings 62 | 63 | * **Calendar**: 64 | 65 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 66 | 67 | -------------------------------------------------------------------------------- /meetings/2022/2022-05-10.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-05-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ZI-NcGsRY1U 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/883 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Robin Ginn (@rginn) 13 | * Christian Bromann (@christian-bromann) 14 | * Jordan Harband (@ljharb) 15 | * Eemeli Aro (@eemeli) 16 | * Tobie Langel (@tobie) 17 | * Sara Chipps (@sarajo) 18 | * Michael Dawson (@mhdawson) 19 | * Alix Robinson 20 | * Rifa Achrinza (@achrinza) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | FYI, RE staffing changes and updates at the LF 27 | JSLandia Nomination form: https://forms.gle/wLTPPpzBoByWTPREA 28 | OpenJS World - June 7-9! Community theater space still available for projects to take advantage of. Let us know if you would like to participate. 29 | Loopback maintainer meeting tomorrow; let us know if you want to add your public project meetings to the OpenJS calendar 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * Welcome VoltrexMaster to the CPC as a Regular Member [#875](https://github.com/openjs-foundation/cross-project-council/issues/875) 38 | * on agenda as part of process, thanks for joining. 39 | 40 | * CPC Board Seat Term Limits [#874](https://github.com/openjs-foundation/cross-project-council/issues/874) 41 | Should we use term limits to help increase diversity 42 | Discussion about the problems, and merits, of term limits and other tools to improve CPC/Board communication 43 | Discussion & ideation about supporting CPC Board reps and information gathering/sharing between 44 | 45 | * CPC Board Seat: Election Information and Call for Nominations [#859](https://github.com/openjs-foundation/cross-project-council/issues/859) 46 | 47 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 48 | * action is to have working session on it. 49 | 50 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 51 | * Joe planning to get collab space spun up in next few weeks 52 | 53 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 54 | * Skipping this week 55 | 56 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 57 | * No update this week. 58 | 59 | ## Next week's working session 60 | 61 | Are there any initiatives or agenda items that we should use a working session to further progress on? 62 | 63 | ## Dates and Reminders 64 | 65 | Please review regularly our list of dates and reminders: 66 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | 76 | -------------------------------------------------------------------------------- /meetings/2022/2022-05-24.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-05-24 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=OrycuK0bkr4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/893 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Jory Burson (@jorydotcom) 12 | * Robin Ginn (@rginn) 13 | * Christian Bromann (@christian-bromann) 14 | * Jordan Harband (@ljharb) 15 | * Michael Dawson (@mhdawson) 16 | * Sara Chipps (@sarajo) 17 | * Divy Tolia (@designmoreweb) 18 | * Christian Bromann (@christian-bromann) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | ### Board Meeting Updates 25 | 26 | *Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. 27 | 28 | * Board meeting on June 6 instead of 3rd Friday of June since there will be in person board meeting June 6 in advance of OpenJS World 29 | 30 | ### openjs-foundation/cross-project-council 31 | 32 | * CPC Board Seat Term Limits [#874](https://github.com/openjs-foundation/cross-project-council/issues/874) 33 | * Believe we agreed last time we could close this and focus on the board member 34 | pipeline/nurturing aspect. 35 | 36 | * CPC Board Seat: Election Information and Call for Nominations [#859](https://github.com/openjs-foundation/cross-project-council/issues/859) 37 | * closed nothing to discuss 38 | 39 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 40 | * Last Tuesday, CPC working meeting on Code of Conduct 41 | * Agreed that for the time being should scope to CoC to be “project”, ie 42 | each project has adopted the Same Code of conduct but applies to 43 | each individually. 44 | * Would like to work to expand scope across projects, but don’t have that 45 | in place and it will require a bigger conversation to achieve that. 46 | * Agreed we should land without modification, and then have new PR/discussion for 47 | a change to the base code of conduct. 48 | 49 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 50 | * Joe sent in application for collab space 51 | * Jory needs to send to CPC as next step for comments/support etc. 52 | 53 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 54 | * next on the feature list, some delays due to staffing. 55 | 56 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 57 | * No updates this week 58 | 59 | ## Next week's working session 60 | 61 | Are there any initiatives or agenda items that we should use a working session to further progress on? 62 | 63 | ## Dates and Reminders 64 | 65 | Please review regularly our list of dates and reminders: 66 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | 76 | -------------------------------------------------------------------------------- /meetings/2022/2022-09-13.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-09-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=hvYlmCNEx0M 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Sara Chipps (@SaraJo) 12 | * Robin Ginn (Robin Ginn 13 | * Jordan Harband 14 | * Rishit Dagli 15 | 16 | ## Agenda 17 | 18 | ### Announcements 19 | 20 | ### Board Meeting Updates 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/cross-project-council 25 | 26 | * Clarify voting processes [#923](https://github.com/openjs-foundation/cross-project-council/issues/923) 27 | * Was working session last week 28 | 29 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 30 | * Jordan, some uncertainty on next steps 31 | * Michael, Jordan had commented with steps, just waiting for somebody to implement 32 | 33 | * OpenJS World 2023 planning [#908](https://github.com/openjs-foundation/cross-project-council/issues/908) 34 | * Not planning to do large event 35 | * Plan to do smaller events as part of other events like Open Source Summit 36 | * If people can past in their favorite events/best places for us to go that would make sense 37 | * JS Nation maybe? -Rishit 38 | * Jordan, send out tweet 39 | 40 | * CPC At Large voting member election [#906](https://github.com/openjs-foundation/cross-project-council/issues/906) 41 | * Two categories (at large Jordan/Michael elected by regular CPC members and Emilie,Toby are at large members for non-impact members) 42 | 43 | * CPC Impact voting member selection [#905](https://github.com/openjs-foundation/cross-project-council/issues/905) 44 | 45 | * Opportunity: Grace Hopper Open Source Day (virtual) Sept 16, 2022 [#898](https://github.com/openjs-foundation/cross-project-council/issues/898) 46 | * Posted blog this morning, will have booth at event also hosting a happy hour on Tuesday, let us know if you want tickets. 47 | 48 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 49 | * Related to issue above 50 | 51 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 52 | * Looking to get more people involved 53 | 54 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 55 | 56 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 57 | 58 | * Build stronger ties between At Large maintainers and their CPC Rep [#761](https://github.com/openjs-foundation/cross-project-council/issues/761) 59 | 60 | * Update docs to indicate projects can just use ICLA if they want [#657](https://github.com/openjs-foundation/cross-project-council/issues/657) 61 | * Michael - Web site is already updated, closed. 62 | 63 | ## Next week's working session 64 | 65 | Are there any initiatives or agenda items that we should use a working session to further progress on? 66 | 67 | ## Dates and Reminders 68 | 69 | Please review regularly our list of dates and reminders: 70 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 71 | 72 | ## Q&A, Other 73 | 74 | ## Upcoming Meetings 75 | 76 | * **Calendar**: 77 | 78 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 79 | 80 | -------------------------------------------------------------------------------- /meetings/2022/2022-09-27.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-09-27 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/940 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Rich Trott (@Trott) 12 | * Tobie Langel 13 | * Robin Ginn (@rginn) 14 | * Jordan Harband 15 | * Tierney Cyren 16 | * Abigail Cabunoc Mayes 17 | * Michael Dawson (@mhdawson) 18 | * Matteo Collina 19 | * Kylie Wagar-Dirks (@kyliewd) 20 | * Sara Chipps 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | * savings on training/certs 26 | * collab summit happening soon! 27 | * NodeConfEU happening soon! 28 | * travel funding is available! 29 | * Security Collab Space happening after this meeting 30 | 31 | ### Board Meeting Updates 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/cross-project-council 36 | 37 | * Clarify voting processes [#923](https://github.com/openjs-foundation/cross-project-council/issues/923) 38 | 39 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 40 | 41 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 42 | 43 | * OpenJS World 2023 planning [#908](https://github.com/openjs-foundation/cross-project-council/issues/908) 44 | 45 | * CPC At Large voting member election [#906](https://github.com/openjs-foundation/cross-project-council/issues/906) 46 | 47 | * CPC Impact voting member selection [#905](https://github.com/openjs-foundation/cross-project-council/issues/905) 48 | 49 | * Opportunity: Grace Hopper Open Source Day (virtual) Sept 16, 2022 [#898](https://github.com/openjs-foundation/cross-project-council/issues/898) 50 | 51 | * A focus on JavaScript security at OpenJS [#826](https://github.com/openjs-foundation/cross-project-council/issues/826) 52 | 53 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 54 | 55 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 56 | 57 | * Build stronger ties between At Large maintainers and their CPC Rep [#761](https://github.com/openjs-foundation/cross-project-council/issues/761) 58 | 59 | ## Next week's working session 60 | 61 | Next week will be an open working session 62 | 63 | ## Dates and Reminders 64 | 65 | Please review regularly our list of dates and reminders: 66 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | 76 | -------------------------------------------------------------------------------- /meetings/2022/2022-10-25.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-10-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=oKGOWOguBR4 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/952 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Abby Cabunoc Mayes (@abbycabs) 12 | * Yagiz Nizipli (@anonrig) 13 | * Kylie Wagar-Dirks (@kyliewd) 14 | * Luke Schantz (@lukeschantz) 15 | * Michael Dawson (@mhdawson) 16 | * Jordan Harband (@ljharb) 17 | * Tobie Langel (@tobie) 18 | * Rich Trott (@trott) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | - OpenSSF awards jQuery grant money 24 | - FINOS program committee will be announcing speakers soon 25 | 26 | ### Board Meeting Updates 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/cross-project-council 31 | 32 | * Clarify voting processes [#923](https://github.com/openjs-foundation/cross-project-council/issues/923) 33 | * No updates 34 | 35 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 36 | * Hoping to get patching work done this week 37 | 38 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 39 | * Hoping to get patching work done this week and can merge this then… 40 | 41 | * OpenJS World 2023 planning [#908](https://github.com/openjs-foundation/cross-project-council/issues/908) 42 | Microconference - open source summit or Kubecon 43 | @ Open Source Summit in Vancouver, May 2023 44 | 15 sessions - no cost to the foundation 45 | More money to invest in 3rd party events 46 | Get program committee set up 47 | CFP in early January 48 | 49 | * CPC Impact voting member selection [#905](https://github.com/openjs-foundation/cross-project-council/issues/905) 50 | * Waiting on update to website and then can close 51 | 52 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 53 | * Robin met with new CTO of linux foundation 54 | * They are short staffed, trying to staff up, probably can’t start until January. 55 | 56 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 57 | * planning to work on it this week. 58 | 59 | ## Next week's working session 60 | 61 | Next week: Code of Conduct 62 | 63 | ## Dates and Reminders 64 | 65 | Please review regularly our list of dates and reminders: 66 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | 76 | -------------------------------------------------------------------------------- /meetings/2022/2022-11-22.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2022-11-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ufcW891ls30 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/971 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Rich Trott (@Trott) 12 | * Darcy Clarke (@darcyclarke) 13 | * Abby Cabunoc Mayes (@abbycabs) 14 | * Robin Ginn (@rginn) 15 | * Tobie Langel (@tobie) 16 | * Kylie Wagar-Dirks (@kyliewd) 17 | 18 | ## Agenda 19 | 20 | ### Announcements 21 | * Open Source in Finance - FINOS event in NYC on Dec 8 22 | * Security Collab Space meeting after this meeting 23 | 24 | ### Board Meeting Updates 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/cross-project-council 29 | 30 | * What are these repos? [#957](https://github.com/openjs-foundation/cross-project-council/issues/957) 31 | * Can do this sort of cleanup in a working session 32 | 33 | * Funds for project-driven initiatives [#953](https://github.com/openjs-foundation/cross-project-council/issues/953) 34 | * Robin will be adding comment in issue. The Board is open and we’re working on a process. 35 | 36 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 37 | * See PR https://github.com/openjs-foundation/cross-project-council/pull/972 for initial effort 38 | 39 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 40 | * 41 | 42 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 43 | * No update 44 | 45 | * Code of Conduct missing for a number of projects in projects table in README [#664](https://github.com/openjs-foundation/cross-project-council/issues/664) 46 | * Agreed to remove that column from the table and make the CoC the canonical resource for this. Make sure that the readme very clearly references the main CoC. 47 | 48 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 49 | * LF IT is looking at this for early 2023. There is interest from other LF sub-foundations. 50 | 51 | * Develop annual review process for projects [#592](https://github.com/openjs-foundation/cross-project-council/issues/592) 52 | * Use working session to build this out. 53 | 54 | ## Next week's working session 55 | 56 | * Working session: Simplifying CPC governance [#958](https://github.com/openjs-foundation/cross-project-council/issues/958) 57 | 58 | ## Dates and Reminders 59 | 60 | Please review regularly our list of dates and reminders: 61 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 62 | 63 | ## Q&A, Other 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Calendar**: 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | 71 | -------------------------------------------------------------------------------- /meetings/2023/2023-01-03.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2023-01-03 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Sv6XwT5SYNc 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/989 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Jordan Harband (@ljharb) 13 | * Robin Ginn (@rginn) 14 | * Kylie Wagar-Dirks (@kyliewd) 15 | * Abby Cabunoc Mayes (@abbycabs) 16 | * Tierney Cyren (@bnb) 17 | * Luke Schantz (@lukeschantz) 18 | * Mike Samuel (@mikesamuel) 19 | 20 | ## Agenda 21 | 22 | ### Announcements 23 | 24 | ### Board Meeting Updates 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/cross-project-council 29 | 30 | * Determine what a realistic 360 review process could look like [#982](https://github.com/openjs-foundation/cross-project-council/issues/982) 31 | * do an NPS style survey 32 | * send to leadership of projects 33 | * get rid of 360 style because of nazis 34 | 35 | * What are these repos? [#957](https://github.com/openjs-foundation/cross-project-council/issues/957) 36 | * have done some work on repo cleanup. More needed to do. 37 | 38 | * Funds for project-driven initiatives [#953](https://github.com/openjs-foundation/cross-project-council/issues/953) 39 | CPC evaluates requests before presenting to the board. 40 | Based on need. No set amounts or dedicated budget for funding. 41 | 42 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 43 | * Joe will try to get this done this week 44 | 45 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 46 | * Joe will try to get this done this week 47 | 48 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 49 | * Still waiting on LF IT staffing 50 | * There may be a similar effort at OpenSSF 51 | 52 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 53 | * some of this work may have been done in recent working session 54 | * as we move forward with other CoC work, keep an eye on this to make sure we are moving task list forward 55 | 56 | ## Next week's working session 57 | 58 | Next weeks working session: review process issue #982 59 | 60 | EDIT post meeting: will work on Code of Conduct issues in working session next week 61 | 62 | ## Dates and Reminders 63 | 64 | Please review regularly our list of dates and reminders: 65 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 66 | 67 | ## Q&A, Other 68 | 69 | ## Upcoming Meetings 70 | 71 | * **Calendar**: 72 | 73 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 74 | -------------------------------------------------------------------------------- /meetings/2023/2023-01-17.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2023-01-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=nqauZxq69Mo 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/998 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Claudio Wunder (@ovflowd) 13 | * Cody Zuschlag (@codyzus) 14 | * Luke Schantz (@lukeschantz) 15 | * Paula Paul (@paulapaul) 16 | * Erick Zhao (@erickzhao) 17 | * Jordan Harband (@ljharb) 18 | * Yagiz Nizipili (@anonrig) 19 | * Kylie Wagar-Dirks(@kyliewd) 20 | * Tobie Langel (@tobie) 21 | * Robin Ginn (@rginn) 22 | * Darcy Clarke (@darcyclarke) 23 | 24 | ## Agenda 25 | 26 | ### Announcements 27 | *CFP open for OpenJS World - Deadline February, 5th 2023 28 | *January Board of Directors meeting Friday, 20th 2023 29 | 30 | ### Board Meeting Updates 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/cross-project-council 35 | 36 | * Determine what a realistic foundation/cpc review process could look like [#982](https://github.com/openjs-foundation/cross-project-council/issues/982) 37 | * Decision to create a doc in which to start hammering out questions and goals. https://docs.google.com/document/d/1WEWB_ZcwUAXGX7uAe2jXk2HviuN5ep6Dq9mopy0seUA/edit?usp=sharing 38 | * Foundation staff are happy to run the survey with project maintainers. 39 | 40 | * What are these repos? [#957](https://github.com/openjs-foundation/cross-project-council/issues/957) 41 | * will review and close 42 | 43 | * Funds for project-driven initiatives [#953](https://github.com/openjs-foundation/cross-project-council/issues/953) 44 | * Need someone to make a PR adding a file outlining the process for project funds & how they are requests/approved; example outline of items include: 45 | * the ad-hoc nature of foundation funding 46 | * requirement of CPC evaluation 47 | * requirement of Board approval 48 | * the funding amounts are not predetermined 49 | 50 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 51 | * Progress being made 52 | 53 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 54 | * blocked by #910 55 | 56 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 57 | * no update 58 | 59 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 60 | * no update 61 | 62 | ## Next week's working session 63 | 64 | CoC work 65 | 66 | ## Dates and Reminders 67 | 68 | Please review regularly our list of dates and reminders: 69 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 70 | 71 | ## Q&A, Other 72 | 73 | ## Upcoming Meetings 74 | 75 | * **Calendar**: 76 | 77 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 78 | -------------------------------------------------------------------------------- /meetings/2023/2023-01-31.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2023-01-31 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=X_M7lUPc-Fo 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/1001 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Yagiz Nizipli (@anonrig) 13 | * Tierney Cyren (@bnb) 14 | * Tobie Langel (@tobie) 15 | * Robin Ginn (@rginn) 16 | * Luke Schantz (@lukeschantz) 17 | * Sean Larkin (@thelarkinn) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | Ticket sales went live on Jan 25, 2023 for OpenJS World 23 | CFP deadline is February 5, 2023 24 | 25 | ### Board Meeting Updates 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/cross-project-council 30 | 31 | * Determine what a realistic foundation/cpc review process could look like [#982](https://github.com/openjs-foundation/cross-project-council/issues/982) 32 | * working on NPS questions 33 | 34 | * What are these repos? [#957](https://github.com/openjs-foundation/cross-project-council/issues/957) 35 | * closed 36 | 37 | * Funds for project-driven initiatives [#953](https://github.com/openjs-foundation/cross-project-council/issues/953) 38 | *Copy: https://github.com/openjs-foundation/cross-project-council/pull/999 39 | 40 | * Add patching script for CoC modifications [#910](https://github.com/openjs-foundation/cross-project-council/issues/910) 41 | * new changes; please review 42 | 43 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 44 | * blocked by #910 45 | 46 | * License check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 47 | * IBM’s scanner is being open sourced to OWASP 48 | * LF IT can review that tool and make decisions on moving forward 49 | 50 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 51 | * looking to discuss during future working session 52 | 53 | ## Next week's working session 54 | 55 | Continuing working on CoC process and progress 56 | 57 | ## Dates and Reminders 58 | 59 | Please review regularly our list of dates and reminders: 60 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | -------------------------------------------------------------------------------- /meetings/2023/2023-06-20.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2023-06-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=OUtw9nTgpd8 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/1098 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Ben Sternthal (@bensternthal) 12 | * Rich Trott (@Trott) 13 | * Rick Markins (@rxmarbles) 14 | * Ethan Arrowood (@Ethan-Arrowood) 15 | * Claudio Wonder (@ovflowd) 16 | * Ruy Adorno (@ruyadorno) 17 | * Michael Dawson (@mhdawson) 18 | 19 | ## Agenda 20 | 21 | ### Announcements 22 | 23 | * Collab Summit will be happening on Sept 18th alongside OpenJS World EU OSS SUMMIT EU 24 | 25 | ### Board Meeting Updates 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/cross-project-council 30 | 31 | * Document process for requesting Organisation Billing (Codespaces + Runners + Etc) [#1092](https://github.com/openjs-foundation/cross-project-council/issues/1092) 32 | * Brainstorm in issue! 33 | 34 | * Enable Payments for Paid Actions/Large Runners/macOS Runners for webpack [#1089](https://github.com/openjs-foundation/cross-project-council/issues/1089) 35 | * let this sit for one week 36 | * off-topic (but related): Aby/GitHub -> proof of concept -> value of GitHub sponsoring us if there’s enough 37 | 38 | * Enable ability to have pseudonimity for EasyCLA. [#1088](https://github.com/openjs-foundation/cross-project-council/issues/1088) 39 | * need to understand what was discussed with the board and if any decisions were made 40 | * Ben will circle up with Robin next week on next steps 41 | 42 | * Requirements for Projects ingesting other existing external projects [#1059](https://github.com/openjs-foundation/cross-project-council/issues/1059) 43 | 44 | * Simplify CPC Board representation [#1055](https://github.com/openjs-foundation/cross-project-council/pull/1055) 45 | * Need update from board 46 | 47 | * Open Up Community Board Seat [#1054](https://github.com/openjs-foundation/cross-project-council/issues/1054) 48 | * Need update from board 49 | 50 | * Should we have a co-chair? [#1043](https://github.com/openjs-foundation/cross-project-council/issues/1043) 51 | 52 | * Update Contributor Covenant Code of Conduct to v2.1 [#851](https://github.com/openjs-foundation/cross-project-council/pull/851) 53 | 54 | * Licence check support/tooling [#815](https://github.com/openjs-foundation/cross-project-council/issues/815) 55 | * Ben followup with IT on status 56 | 57 | * Clarify requirements around CoC violation [#786](https://github.com/openjs-foundation/cross-project-council/issues/786) 58 | 59 | * Balancing privacy vs. transparency for the travel fund [#397](https://github.com/openjs-foundation/cross-project-council/issues/397) 60 | 61 | ## Next week's working session 62 | 63 | Are there any initiatives or agenda items that we should use a working session to further progress on? 64 | 65 | ## Dates and Reminders 66 | 67 | Please review regularly our list of dates and reminders: 68 | https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 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 | -------------------------------------------------------------------------------- /meetings/2025/2025-03-18.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation Cross Project Council Meeting 2025-03-18 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ra28G4cXvEk&ab_channel=OpenJSFoundation 6 | * **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/1426 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael Dawson (@mhdawson) 12 | * Adrian Estrada (@edsadr) 13 | * Chris de Almeida (@ctcpip) 14 | * Ryan Roemer (@ryan-roemer) 15 | * Kate Powell (@kj-powell) 16 | * Ulises Gascón (@UlisesGascon) 17 | * Michaela Laurencin (@mlaurencin) 18 | * Ethan Arrowood (@Ethan-Arrowood) 19 | * Darcy Clarke (@darcyclarke) 20 | * Sebastian Beltran (@bjohansebas) 21 | 22 | ## Agenda 23 | 24 | ### Announcements 25 | 26 | ### Board Meeting Updates 27 | 28 | - https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-board 29 | 30 | ### Staff Updates 31 | 32 | - https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-legal-info 33 | - https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-staff-update 34 | - https://github.com/openjs-foundation/cross-project-council/labels/waiting-on-website-update 35 | 36 | _Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting._ 37 | 38 | ### openjs-foundation/cross-project-council 39 | 40 | * Proposal To Add A SERVICES.md or similar documentation to OpenJS Projects [#1425](https://github.com/openjs-foundation/cross-project-council/issues/1425) 41 | * Discussed but without Ben here, we didn’t go far 42 | 43 | * Link to same page for CoC Team info [#1422](https://github.com/openjs-foundation/cross-project-council/pull/1422) 44 | * merged 45 | 46 | * Code of Conduct Plan of Action - Remaining Items [#1417](https://github.com/openjs-foundation/cross-project-council/issues/1417) 47 | * will work on in next working session 48 | 49 | * Health-check on the NativeScript TSC charter [#1387](https://github.com/openjs-foundation/cross-project-council/issues/1387) 50 | 51 | * Adding affiliation clause to NativeScript charter [#1386](https://github.com/openjs-foundation/cross-project-council/issues/1386) 52 | 53 | * continuity policy and package registries? [#1355](https://github.com/openjs-foundation/cross-project-council/issues/1355) 54 | 55 | 56 | ### Next week's working session 57 | 58 | Are there any initiatives or agenda items that we should use a working session to further progress on? 59 | - https://github.com/openjs-foundation/cross-project-council/labels/cpc-working-session 60 | 61 | * NEXT WEEK’S working session will be a private working session meeting 62 | 63 | ### Regular reviews 64 | 65 | Please review regularly our list of dates and reminders, our quarterly review issues, and check the list of issues that can be closed: 66 | 67 | - https://github.com/openjs-foundation/cross-project-council/blob/main/Dates-and-Reminders.md 68 | - https://github.com/openjs-foundation/cross-project-council/labels/cpc-quartely-review 69 | - https://github.com/openjs-foundation/cross-project-council/labels/cpc-can-issue-be-closed 70 | 71 | ### Q&A, Other 72 | 73 | ## Upcoming Meetings 74 | 75 | - **Calendar**: 76 | 77 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 78 | 79 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "cross-project-council", 3 | "version": "0.0.0", 4 | "description": "OpenJS Foundation Cross Project Council", 5 | "scripts": { 6 | "lint-md": "remark . -f", 7 | "test": "npm run lint-md" 8 | }, 9 | "repository": { 10 | "type": "git", 11 | "url": "git+https://github.com/openjs-foundation/cross-project-council.git" 12 | }, 13 | "keywords": [ 14 | "javascript", 15 | "openjs-foundation" 16 | ], 17 | "author": "openjs-foundation", 18 | "license": "MIT", 19 | "homepage": "https://openjsf.org", 20 | "devDependencies": { 21 | "remark-cli": "^12.0.0", 22 | "remark-lint": "^9.1.2", 23 | "remark-preset-lint-markdown-style-guide": "^5.1.3", 24 | "remark-preset-lint-recommended": "^6.1.3" 25 | } 26 | } 27 | -------------------------------------------------------------------------------- /project-resources/ESP/esp-herodevs-angular.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/cross-project-council/40c0722d1d4a1afea854fbf7fcd98fad5ff72bd0/project-resources/ESP/esp-herodevs-angular.png -------------------------------------------------------------------------------- /project-resources/ESP/esp-herodevs-node.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/cross-project-council/40c0722d1d4a1afea854fbf7fcd98fad5ff72bd0/project-resources/ESP/esp-herodevs-node.png -------------------------------------------------------------------------------- /project-resources/ESP/esp-herodevs-vue.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/cross-project-council/40c0722d1d4a1afea854fbf7fcd98fad5ff72bd0/project-resources/ESP/esp-herodevs-vue.png -------------------------------------------------------------------------------- /project-resources/GITHUB_REQUESTS/2023.md: -------------------------------------------------------------------------------- 1 | # 2023 GitHub Resources Request Record 2 | 3 | Project | Request | Monthly Cost | Date | Champions | Pull Request Link 4 | -|-|-|-|-|- 5 | Node.js | GitHub Codespaces | 100.00 USD | 2023.08.16 | Claudio Wunder | https://github.com/openjs-foundation/cross-project-council/pull/1149 | 6 | -------------------------------------------------------------------------------- /project-resources/GITHUB_REQUESTS/README.md: -------------------------------------------------------------------------------- 1 | # GitHub Resource Requests 2 | 3 | For details on Requesting GitHub Resources, please see [REQUESTING_GITHUB_RESOURCES.md](../REQUESTING_GITHUB_RESOURCES.md). 4 | -------------------------------------------------------------------------------- /project-resources/PROJECT_FUND/2023.md: -------------------------------------------------------------------------------- 1 | # 2023 Project Fund Request Record 2 | 3 | First Name | Last Name | Project | Amount requested | Pull Request date | Pull Request link 4 | -|-|-|-|-|- 5 | -------------------------------------------------------------------------------- /project-resources/PROJECT_FUND/README.md: -------------------------------------------------------------------------------- 1 | # Project Fund 2 | 3 | For details on the Project Fund, please see [PROJECT_FUND.md](../PROJECT_FUND.md). 4 | -------------------------------------------------------------------------------- /project-resources/REQUESTING_GITHUB_RESOURCES.md: -------------------------------------------------------------------------------- 1 | # OpenJS Foundation GitHub Resources Requests 2 | 3 | OpenJS Foundation can provide monthly funding for the following Github resources: 4 | 5 | - Actions 6 | - Codespaces 7 | - Extra Large Runners (Actions) 8 | 9 | Funding for resources requires: 10 | 11 | 1. CPC Approval 12 | 2. OpenJS Foundation Budget Approval 13 | 14 | ## Archive of Approved Requests 15 | 16 | The list below contains a historical archive and reference of past approved project fund requests. 17 | 18 | - [2023](./GITHUB_REQUESTS/2023.md) 19 | 20 | ## Requesting GitHub Resources 21 | 22 | The process for requesting Github resources is: 23 | 24 | 1. Estimate your monthly spend using https://github.com/pricing/calculator 25 | 1. Create and submit a PR using the template for CPC approval 26 | 1. If approved the CPC will discuss with OpenJS staff in the next CPC meeting 27 | 1. Once fully approved, you will need to add OpenJS staff as a billing manager on your project 28 | - Billing Managers have only access to Billing Settings on your GitHub organization 29 | 1. OpenJS will add a credit card and implement spending limits consistent with the request 30 | 31 | The Pull Request template below should be completed with a Pull Request containing an addition to the `GITHUB_REQUESTS/{CurrentYear}.md` spreadsheet from this repository, filling the required information. 32 | 33 | > [!NOTE]\ 34 | > The costs are billed on a monthly basis. Hence the costs should be calculated on a monthly basis. 35 | 36 | ### Best Practices 37 | 38 | These best practices are a set of recommendations for maintaining a healthy usage of the resources. 39 | 40 | #### Codespaces Best-Practices 41 | 42 | - When enabling Codespaces, we recommend that only a set of repositories have Codespaces enabled, to avoid it being used on projects that do not require Codespaces. 43 | - We recommend setting policies that best fit your project needs, but that are reasonable in terms of resource usages, such as: 44 | - Limiting the amount of concurrent Codespaces a member might own 45 | - Defining a reasonable timeout policy to avoid extra unnecessary costs 46 | - If your organization has a large amount of members, we recommend limiting the access of Codespaces to members that would benefit from it and possibly making it an opt-in process (so that members request access to Codespaces) 47 | - This is a recommended practice as if individual members accidentally reach the budgetry limit defined, this affects everyones usage of Codespace as the feature would be locked out until the next billing cycle 48 | 49 | ### GitHub Resource Request PR Template 50 | 51 | ```md 52 | ## GitHub Resource Request for {Project Name} 53 | 54 | - **Estimated monthly cost:** USD XXXX 55 | - **Requested Features:** 56 | - [ ] Actions 57 | - [ ] Codespaces 58 | - [ ] Extra Large Runners (Actions) 59 | - **Fund Request Champions:** 60 | - Champion A (@handle) 61 | - Champion B (@handle) 62 | 63 | ### Intended usage of the resources 64 | 65 | 66 | 67 | 68 | 69 | cc @openjs-foundation/cpc 70 | ``` 71 | 72 | ## Approvals 73 | 74 | The request is submitted to the CPC for evaluation. 75 | The CPC evaluates the request following its [decision-making process](https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md#section-9-decision-making) and if approved, informs OpenJS staff that the request needs budget approval. 76 | Requests approved by the CPC are subject to final budget approval by the OpenJS Foundation. 77 | -------------------------------------------------------------------------------- /project-resources/github-continuity-policy.md: -------------------------------------------------------------------------------- 1 | # OpenJS Github Continuity Policy 2 | 3 | ## Summary 4 | 5 | This policy is intended to ensure that OpenJS GitHub projects remain accessible and manageable. 6 | 7 | It addresses the following use cases: 8 | 9 | - Archiving projects when maintainers are no longer reachable 10 | - Managing projects and users when maintainers are inactive or unreachable 11 | - Adding or removing admins in emergency situations 12 | 13 | ## Continuity Options for Projects 14 | 15 | ### Option 1: Add The Executive Director As An Admin 16 | 17 | If you select this option, you will add the OpenJS Foundation executive director (currently https://github.com/rginn) as an admin to your project. 18 | 19 | ### Option 2: Add Your Organization To The OpenJS Enterprise 20 | 21 | If you select this option, you will add your Organization to the [OpenJS Foundation enterprise account](https://github.com/enterprises/openjs-foundation). Doing so gives the foundation the option to become an organization owner if necessary. The admins of the enterprise account are currently limited to the [Executive Director](https://github.com/rginn) and [Director Of Program Management](https://github.com/bensternthal). 22 | 23 | ### Option 3: Opt-out 24 | 25 | Projects that feel their governance is sufficient to provide continuity may opt out of this policy by requesting an exception from the CPC. This can be done by filing an issue in the [CPC repository](https://github.com/openjs-foundation/cross-project-council/issues). 26 | -------------------------------------------------------------------------------- /project-resources/openjsf-marketing-services.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openjs-foundation/cross-project-council/40c0722d1d4a1afea854fbf7fcd98fad5ff72bd0/project-resources/openjsf-marketing-services.pdf -------------------------------------------------------------------------------- /project-resources/project-directed-funding-policy.md: -------------------------------------------------------------------------------- 1 | # Project Directed Funding Policy 2 | 3 | All OpenJS Foundation projects must adhere to the Project Directed Funding policy as outlined on the OpenJS Foundation website: 4 | 5 | * [Project Directed Funding Policy](https://openjsf.org/projects/) 6 | 7 | For any questions, please contact the Cross Project Council (CPC) or Foundation staff. 8 | -------------------------------------------------------------------------------- /project-resources/requesting_LFIT_support.md: -------------------------------------------------------------------------------- 1 | # Requesting Linux Foundation IT Support 2 | 3 | This guide explains how to request help from the Linux Foundation IT team. 4 | 5 | ## Who Is This Document For? 6 | 7 | This document is for OpenJS projects that have formally engaged with LF IT to support one or more of their services. If you have questions about a non-LF supported service, please contact operations@openjsf.org. 8 | 9 | ## How To Contact Linux Foundation IT For Support 10 | 11 | ### Submit an Issue 12 | 13 | The preferred way to request IT support is by [filling an issue](https://github.com/openjs-foundation/infrastructure/issues/new?template=IT-SUPPORT-REQUEST.yml) in the [infrastucture repository](https://github.com/openjs-foundation/infrastructure). Note: 14 | 15 | * This is a public repository, if you wish to file a confidential request please see the below instructions 16 | * Please use the "IT Support Request Ticket" issue template 17 | 18 | ### Submitting Confidential Requests 19 | 20 | Please submit any confidential requests via [Jira Service Desk](https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2). 21 | 22 | ### Alternate Contact Method: OpenJS Foundation Slack 23 | 24 | For less formal inquiries you can reach out to the IT Operations team channel (#lf-it-support) in the [OpenJS Foundation Slack instance](https://slack-invite.openjsf.org/). 25 | 26 | ### How Work Is Prioritized 27 | 28 | Critical issues resulting in unplanned downtime will be prioritized over other severity types. Please clearly indicate the urgency of your request in the issue description. Non-critical issues will be addressed according to their severity and order of submission. 29 | 30 | ### Viewing The Status Of Your Request 31 | 32 | All non-confidential issues are tracked via a public [Github project board](https://github.com/orgs/openjs-foundation/projects/10). 33 | 34 | ## What To Do In An Emergency 35 | 36 | In the event of an emergency (e.g., a critical system is down or there is a security incident), you can use Jira to request priority support 24/7. 37 | 38 | 1. Please fill out the following ticket in Jira [(Report a serious problem](https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/create/30)) 39 | 2. Set urgency and impact appropriately 40 | 41 | ## Have A Unique Situation? 42 | 43 | For urgent, unique, or complex issues that require discussion, please contact operations@openjsf.org. 44 | --------------------------------------------------------------------------------