├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONSTITUENCIES.md ├── CONSTITUENCY-NEEDS.md ├── CONTRIBUTING.md ├── LICENSE.md ├── README.md ├── TECHNICAL_PRIORITY_WORKING_SUMMARY.md ├── VALUES_AND_PRIORITIZATION.md ├── collaborator summit ├── 2022-dublin │ ├── community-brainstorm.md │ └── technical-priorities.md └── 2023-vancouver │ ├── community-brainstorm.md │ └── technical-priorities.md ├── meetings ├── 2020-07-15.md ├── 2020-07-29.md ├── 2020-08-12.md ├── 2020-09-02.md ├── 2020-09-17.md ├── 2020-10-01.md ├── 2020-10-28.md ├── 2020-11-12.md ├── 2021-01-06.md ├── 2021-01-21.md ├── 2021-02-04.md ├── 2021-02-11.md ├── 2021-03-25.md ├── 2021-04-08.md ├── 2021-05-10.md ├── 2021-06-07.md ├── 2021-07-12.md ├── 2021-08-23.md ├── 2021-09-27.md ├── 2021-10-13.md ├── 2021-10-27.md ├── 2021-11-10.md ├── 2021-12-08.md ├── 2022-01-19.md ├── 2022-02-16.md ├── 2022-03-02.md ├── 2022-03-16.md ├── 2022-03-30.md ├── 2022-04-27.md ├── 2022-07-06.md ├── 2022-07-20.md ├── 2022-09-07.md ├── 2022-09-21.md ├── 2022-10-12.md ├── 2022-10-26.md ├── 2022-11-23.md ├── 2023-01-04.md ├── 2023-01-18.md ├── 2023-03-01.md ├── 2023-03-15.md ├── 2023-03-29.md ├── 2023-04-12.md ├── 2023-04-26.md ├── 2023-05-24.md ├── 2023-06-07.md ├── 2023-06-21.md ├── 2023-08-02.md ├── 2023-08-16.md ├── 2023-08-30.md ├── 2023-10-11.md ├── 2023-10-25.md ├── 2024-01-10.md ├── 2024-01-24.md ├── 2024-03-06.md ├── 2024-03-20.md ├── 2024-04-17.md ├── 2024-05-01.md ├── 2024-05-15.md ├── 2024-05-29.md ├── 2024-06-12.md ├── 2024-06-26.md ├── 2024-07-24.md ├── 2024-08-07.md ├── 2024-08-21.md ├── 2024-09-04.md ├── 2024-09-18.md ├── 2024-10-16.md ├── 2024-11-13.md ├── 2024-11-27.md ├── 2025-01-08.md ├── 2025-01-22.md ├── 2025-02-05.md ├── 2025-02-19.md ├── 2025-03-05.md ├── 2025-03-19.md ├── 2025-04-16.md ├── summit-apr-2022.md ├── summit-aug-2021 │ ├── agenda.pdf │ └── minutes.md ├── summit-jan-2022.md ├── summit-jun-2022.md ├── summit-nov-2021.md └── summit-typescript-jul-2022.md └── surveys ├── 2021-05-03 ├── Node.js Next 10 Survey-Qs3,4.pdf └── NodeNext10SurveyResults.pdf ├── 2023-04 ├── Node.js Next 10 Survey Results - Slides.pdf ├── Node.js Survey Results 2023.pdf ├── Node.js Survey open ended answers.pdf └── questions.md ├── 2024-04 ├── Next-10 survey 2024.pdf ├── Node Next 10 Survey Results OVERVIEW.pdf └── questions.md └── 2024-09 ├── collaborator health survey results.pdf └── questions.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | node_modules 3 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | The Node.js project and its initiatives are committed to upholding the Node.js Code of Conduct. 4 | 5 | The Node.js Code of Conduct document can be found at 6 | https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md 7 | -------------------------------------------------------------------------------- /CONSTITUENCIES.md: -------------------------------------------------------------------------------- 1 | # Constituencies 2 | 3 | > Document Status: Proposal, Work In Progress 4 | 5 | ## Context 6 | 7 | Having a clear idea of who are our constituencies will help us prioritize decisions as well as which features or changes should be included in the project. 8 | 9 | ## List of constituencies 10 | 11 | * Direct end users 12 | * Users who run tools themselves (install Node.js, run tool, deal with errors including writing/using 13 | scripts) 14 | * Application operators 15 | * Users who interact with existing, running applications (regardless if they wrote the application or not) 16 | * Service and infrastructure providers 17 | * Application Developers 18 | * Front-end tool consumers 19 | * Back-end server authors 20 | * Hobby developers 21 | * Professional developers 22 | * Tool authors 23 | * Library/package authors 24 | * Users who write libraries and packages to be included on other applications 25 | * Node.js contributors 26 | * Developers working directly on [nodejs/node](https://github.com/nodejs/node) 27 | * Individuals participating in Working Groups and teams 28 | * Organizations with investments in Node.js (eg: Enterprises, Government bodies, 29 | startups, non-profits, standards groups like TC39) 30 | * C level executives (CTO, CEO, etc.) 31 | * Planning/program offices 32 | * Managers 33 | * Education 34 | * Teachers 35 | * Students 36 | * Organizations who help people learn Node.js (colleges, University, boot camps, 37 | online learning resources, etc.) 38 | * Programs to help people demonstrate capability (certification programs, etc.) 39 | * Security Practitioners 40 | * People involved in the life-cycle of handling security issues including: 41 | * Penetration testing 42 | * Incident response 43 | * CVE scanning/remediation, 44 | * Legal, Public relations 45 | 46 | ## Prior art 47 | 48 | - [Priority of constituencies on HTTP spec](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies). 49 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to next-10 2 | 3 | We welcome participation in this effort. Please feel free to 4 | raise or comment on issues and join any of the scheduled meetings. 5 | 6 | ## Becoming a member 7 | 8 | If you'd like to become a member please submit a PR to add yourself 9 | to the members list in the README.md. 10 | 11 | 12 | ## Developer's Certificate of Origin 1.1 13 | 14 | By making a contribution to this project, I certify that: 15 | 16 | * (a) The contribution was created in whole or in part by me and I 17 | have the right to submit it under the open source license 18 | indicated in the file; or 19 | 20 | * (b) The contribution is based upon previous work that, to the best 21 | of my knowledge, is covered under an appropriate open source 22 | license and I have the right under that license to submit that 23 | work with modifications, whether created in whole or in part 24 | by me, under the same open source license (unless I am 25 | permitted to submit under a different license), as indicated 26 | in the file; or 27 | 28 | * (c) The contribution was provided directly to me by some other 29 | person who certified (a), (b) or (c) and I have not modified 30 | it. 31 | 32 | * (d) I understand and agree that this project and the contribution 33 | are public and that a record of the contribution (including all 34 | personal information I submit with it, including my sign-off) is 35 | maintained indefinitely and may be redistributed consistent with 36 | this project or the open source license(s) involved. 37 | 38 | 39 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | MIT License (MIT) 2 | ===================== 3 | 4 | Copyright (c) Node.js package-maintenance collaborators 5 | ----------------------------------- 6 | 7 | *Node.js package-maintenance collaborators listed at * 8 | 9 | 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: 10 | 11 | The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. 12 | 13 | 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. 14 | 15 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # next-10 2 | 3 | [![Join us on OpenJS slack (channel #nodejs-next-10)](https://img.shields.io/badge/OpenJS%20Slack-%23nodejs--next--10-blue)](https://slack-invite.openjsf.org/) 4 | 5 | 6 | The purpose of this repository is to work collaboratively on the strategic 7 | directions for the next 10 years of Node.js (Building on the successful 8 | first 10). 9 | 10 | For more context see: https://github.com/nodejs/TSC/issues/797 11 | 12 | We meet every other week and an issue with the agenda for the meeting will be opened in the repo a few days 13 | in advance. You can find the dates/times for future meetings on the Node.js [calendar](https://calendar.google.com/calendar/u/0/embed?src=c_16f0ae5d3a22625175d199dbdb1cac84c2d09eab7f173e94f558417cb5cdbfd8@group.calendar.google.com) labeled as `Node.js Next 10 years`. 14 | 15 | # Team members 16 | 17 | - [@BethGriggs](https://github.com/BethGriggs) - Bethany Nicolle Griggs 18 | - [@bmeck](https://github.com/bmeck) - Bradley Farias 19 | - [@bnb](https://github.com/bnb) - Tierney Cyren 20 | - [@darcyclarke](https://github.com/darcyclarke) - Darcy Clarke 21 | - [@dominykas](https://github.com/dominykas) - Dominykas Blyžė 22 | - [@joesepi](https://github.com/joesepi) - Joe Sepi 23 | - [@legendecas](https://github.com/legendecas) - legendecas 24 | - [@ljharb](https://github.com/ljharb) - Jordan Harband 25 | - [@mhdawson](https://github.com/mhdawson) - Michael Dawson 26 | - [@ovflowd](https://github.com/ovflowd) - Claudio Wunder 27 | - [@Qard](https://github.com/Qard) - Stephen Belanger 28 | - [@ruyadorno](https://github.com/ruyadorno) - Ruy Adorno 29 | - [@sheplu](https://github.com/sheplu) - Jean Burellier 30 | - [@nomadtechie](https://github.com/nomadtechie) - Amal Hussein 31 | - [@marco-ippolito](https://github.com/marco-ippolito) - Marco Ippolito 32 | - [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón 33 | - [@JakobJingleheimer](https://github.com/JakobJingleheimer) - Jacob Smith 34 | 35 | # Emeritus 36 | 37 | - [@ahmadawais](https://github.com/ahmadawais) - Ahmad Awais ⚡️ 38 | - [@andrewhughes101](https://github.com/andrewhughes101) - Andrew Hughes 39 | - [@bengl](https://github.com/bengl) - Bryan English 40 | - [@BridgeAR](https://github.com/BridgeAR) - Ruben Bridgewater 41 | - [@designMoreWeb](https://github.com/designMoreWeb) - Divy Tolia 42 | - [@devsnek](https://github.com/devsnek) - devsnek 43 | - [@F3n67u](https://github.com/F3n67u) - Feng Yu 44 | - [@ghinks](https://github.com/ghinks) - Glenn 45 | - [@iansu](https://github.com/iansu) - Ian Sutherland 46 | - [@jasnell](https://github.com/jasnell) - James M Snell 47 | - [@keywordnew](https://github.com/keywordnew) - Manil Chowdhury 48 | - [@mcollina](https://github.com/mcollina) - Matteo Collina 49 | - [@mmarchini](https://github.com/mmarchini) - mmarchini 50 | - [@MylesBorins](https://github.com/MylesBorins) - Myles Borins 51 | - [@puzpuzpuz](https://github.com/puzpuzpuz) - Andrey Pechkurov 52 | - [@richardlau](https://github.com/richardlau) - Richard Lau 53 | - [@ronag](https://github.com/ronag) - Robert Nagy 54 | - [@targos](https://github.com/targos) - Michaël Zasso 55 | - [@tniessen](https://github.com/tniessen) - Tobias Nießen 56 | - [@trivikr](https://github.com/trivikr) - Trivikram Kamat 57 | - [@wesleytodd](https://github.com/wesleytodd) - Wes Todd 58 | -------------------------------------------------------------------------------- /TECHNICAL_PRIORITY_WORKING_SUMMARY.md: -------------------------------------------------------------------------------- 1 | # Technical Priority Working Summary 2 | ## Modern HTTP 3 | ### Deep Dives 4 | * [Jan 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) 5 | 6 | ### Project agreement 7 | * [maintaining-http.md](https://github.com/nodejs/node/blob/main/doc/contributing/maintaining-http.md) 8 | 9 | ### Related work 10 | * fetch landed in core 11 | 12 | ## Suitable types for end-users 13 | ### Deep Dives 14 | * [Nov 20221](https://github.com/nodejs/next-10/blob/main/meetings/summit-nov-2021.md) 15 | 16 | ### Project agreement 17 | * [maintaining-types-for-nodejs.md](https://github.com/nodejs/node/blob/main/doc/contributing/maintaining-types-for-nodejs.md) 18 | 19 | ### Related work 20 | * additions to style guide in order to support better type info generation - https://github.com/nodejs/node/pull/41025 21 | * documented next steps - https://github.com/nodejs/next-10/issues/104 22 | 23 | ## Documentation 24 | ### Deep Dives 25 | * [Jan 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) 26 | 27 | ### Project agreement 28 | 29 | ### Related work 30 | * Document metadata - https://github.com/nodejs/next-10/issues/121 31 | 32 | ## WebAssembly 33 | ### Deep Dives 34 | * [April 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-apr-2022.md) 35 | 36 | ### Project agreement 37 | * [maintaining-web-assembly.md](https://github.com/nodejs/node/blob/main/doc/contributing/maintaining-web-assembly.md) 38 | 39 | ### Related work 40 | 41 | ## ESM 42 | Deep Dives 43 | * [June 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-jun-2022.md) 44 | 45 | ### Project agreement 46 | 47 | ### Related work 48 | * [loaders](https://github.com/nodejs/loaders) 49 | * Try to encourage/get work started on support for ESM in the vm module. 50 | 51 | ## Support for features from the latest ECMAScript spec 52 | ### Deep Dives 53 | N/A - we get new features from V8, and have a decent process for keeping up to date with V8 54 | ### Project agreement 55 | ### Related work 56 | * V8 strategic initiative in - https://github.com/nodejs/node/blob/main/doc/contributing/strategic-initiatives.md 57 | * Plan to document current approach in ../doc/contributing 58 | 59 | ## Observability 60 | ### Deep Dives 61 | * [June 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-jun-2022.md) 62 | 63 | ### Project agreement 64 | ### Related work 65 | * Entrypoint Hooks[43408](https://github.com/nodejs/node/issues/43408) 66 | * Create feature request for - Replacing trace events implementation with Perfetto 67 | * Start documentation/advocacy initiative to modules owners, Michael to open issue in Diagnostics WG around this. 68 | 69 | ## Permissions/policies/sec model 70 | ### Deep Dives 71 | * [April 2022](https://github.com/nodejs/next-10/blob/main/meetings/summit-apr-2022.md) 72 | 73 | ### Project agreement 74 | * [security-model-strategy](https://github.com/nodejs/node/blob/main/doc/contributing/security-model-strategy.md) 75 | 76 | ### Related work 77 | * work on security model definition - https://github.com/nodejs/security-wg/issues/799 78 | 79 | ## Better multithreaded support 80 | 81 | ### Deep Dives 82 | ### Project Agreement 83 | ### Related Work 84 | * Next-10 - Deep dive session for Better multithreaded support[139](https://github.com/nodejs/next-10/issues/139) 85 | 86 | ## Single Executable Applications 87 | 88 | ### Deep Dives 89 | * [Nov 2021](https://github.com/nodejs/next-10/blob/main/meetings/summit-nov-2021.md) 90 | 91 | ### Project agreement 92 | 93 | ### Related work 94 | 95 | * Experimental support for SEA - https://github.com/nodejs/node/pull/42334 96 | 97 | 98 | -------------------------------------------------------------------------------- /VALUES_AND_PRIORITIZATION.md: -------------------------------------------------------------------------------- 1 | # Values and Priorities 2 | 3 | > Document Status: Proposal, Work In Progress 4 | 5 | ## Context 6 | 7 | Prioritize the **Technical** values shared by the project and use these to guide us when making tradeoffs. 8 | 9 | 10 | ## Values and priority level 11 | 12 | This is only a subset of the overall priorities, listing only those which are at the 13 | top of the priority list. Anything on this list is very important for the project 14 | despite the relative priorities shown. 15 | 16 | - Priority 1 - Developer experience 17 | - Priority 2 - Stability 18 | - Priority 3 - Operational qualities 19 | - Priority 4 - Node.js maintainer experience 20 | - Priority 5 - Technology and API currency 21 | 22 | ## Value descriptions 23 | 24 | ### Developer Experience 25 | We value ensuring that developers are productive and enjoy developing with Node.js. Some key elements of this include: 26 | - Approachability (both technical and community) 27 | - Great Documentation 28 | - Bundling friction-reducing APIs and components, even though they could be provided externally 29 | - Enabling/supporting external packages to ensure overall developer experience 30 | 31 | ### Stability 32 | To avoid introducing churn into Node.js' ecosystem, we value stability and consistency across releases and avoid breaking changes. Some key elements of this include: 33 | - Backwards compatibility 34 | - Predictable and stable releases 35 | - A strong safety net, including explicitly testing how changes in Node.js affect userland packages. 36 | - Careful consideration of what goes into LTS releases 37 | 38 | ### Operational Qualities 39 | We value keeping Node.js safe, performant and lightweight as well as the ability to investigate and debug problems in development and production. Some key elements of this include: 40 | - Throughput (speed) 41 | - Startup time 42 | - Binary size 43 | - Memory footprint 44 | - Debug tooling (debugger) 45 | - Diagnostic tooling (profilers, heapdumps, coredumps, etc.) 46 | - Addressing security vulnerabilities in a responsible manner 47 | 48 | ### Node.js Maintainer Experience 49 | We value the productivity and happiness of Node.js' maintainers. Some key elements of this include: 50 | - Approachability of the codebase 51 | - Good internal documentation and guides 52 | - Low-friction policies and processes 53 | - Good CI and tooling to make maintainers productive 54 | 55 | ### Providing modern APIs and Technologies 56 | We value providing developers with modern APIs and technologies following existing standards whenever possible. Some key elements of this include: 57 | - Participating in standards work and organizations 58 | - Web API compatibility 59 | - Supporting and exposing new technologies and standards through early adoption 60 | 61 | ## References 62 | 63 | [First pass at list of values](https://github.com/nodejs/next-10/issues/5) 64 | [Original priorities brainstorm document](https://docs.google.com/document/d/1sbO_zCn9n_JH2zuGtqNAahUhA_mGFA89DdAme8nEdsw) 65 | -------------------------------------------------------------------------------- /collaborator summit/2022-dublin/community-brainstorm.md: -------------------------------------------------------------------------------- 1 | ## Key focus area 2 | 3 | | 2021 | 2022 | Change | 4 | |---|---|---| 5 | | Collaborator profile / Growing collaborators / Succession plannig & technical talent pool / existing collaborators | Increase corporate contributions: getting a few unicorn startups and companies to allocate some engineers to Node.js / Keeping the lights on, build, security releases / Corporate Investment: How do we make it happen? | new | 6 | | Attracting new collaborators / Making your first contribution / newcomers / Engage and help people wanting to collaborate & help (Collaborator Summit is great but Covid) | Funnel contributor onboarding into relevant working groups / Communication about initiative and help people to be involved / Could use more followup after Code & Learns / Onboarding the next generation: what happens when we all die | = | 7 | | Consensus process / PR review & approval flow | Education | new | 8 | | More communication about initiative | Enabling larger initiatives | +1 | 9 | | Large & significant changes | Further built in tooling | +3 | 10 | | Mentorship programm is a good idea (but maybe with a bit more follow up) | Being well welcomed in WG / being well welcomed in working group | -5 | 11 | | Leadership / Leadership model | Faster startup time | new | 12 | | Build technology, flow to being able to test | Sustainable outreach / Adjacent community engagement | new | 13 | 14 | > Good collaboration coming but hard to retain 15 | 16 | > Need to reach for companies for support / money / contribution 17 | 18 | > Need to work on better follow up with new contributor 19 | 20 | > How to have bigger initiatives? 21 | 22 | ## Obstacles 23 | 24 | | 2021 | 2022 | Change | 25 | |---|---|---| 26 | | Current consensus seeking model / Finding consensus is difficult sometimes / Some MR are blocked for a long time (some others are quite fast) / hard to reach consensus on issue (long discussion lead to collaborator burnout) | Flaky CI / CI reliability / Flaky CITGM / CI time | | 27 | | Different agendas & goals | Lack of "good first issues" | new | 28 | | How to contribute and help people understanding how to contribute & guide them (example, tuto, pair programming) | Some niche or complicated areas have a really hard time getting reviews | +2 | 29 | | Timezones | Communicating with the community about adding npm module functionalities into core | new | 30 | | Certain areas have too few knowledgeable people involved (stream, crypto) | ESM and CJS interoperability in npm module: do we have a recommandation for the community? | new | 31 | | PRs get staled due to lack of reviews | A lot of different topic, how to prioritize | +1 | 32 | | Size of the project | Timezone / Meeting time for WG | -3 | 33 | | Jenkins logs hard to navigate for newcomers | Primordials | new | 34 | | Long build times in developments (increase barrier unless you have a powerfull machine) | Money | new | 35 | | | Corporate priorities | new | 36 | | | OpenJS Fundation limitations | new | 37 | | | Burnout | new | 38 | | | Not getting enough contribution from the ecosystem | new | 39 | | | Work more asynchronously | new | 40 | 41 | > Area without enough contributors (project size, burnout, ...) 42 | 43 | > timezone is still an issue 44 | 45 | > tests/build is long and log can be hard 46 | 47 | > money/corporate support was a big talk 48 | 49 | ## Working well 50 | 51 | | 2021 | 2022 | Change | 52 | |---|---|---| 53 | | Active working group / working groups / Online WG is a great way for people to join and start to collaborate | Collaborator Summit | | 54 | | Release cadence | Onboarding new collaborators | | 55 | | Codeowner (still room for improvement) | PR process | | 56 | | Automation | New collaborators (seems a lot new people this year than before) | | 57 | | | OpenSSF contribution to make Node.js more secure | | 58 | | | Making sure the ecosystem is stable and breaking changes are few. Few complaintes from the ecosystem | | 59 | | | Automating away a lot of things with labels and GitHub Actions has made the contributing experience friendlier | | 60 | 61 | > Working group onboarding collaborator and people joining seems fine 62 | 63 | > automation played a key role on helping members 64 | 65 | > PR speed seems to be better 66 | -------------------------------------------------------------------------------- /collaborator summit/2023-vancouver/community-brainstorm.md: -------------------------------------------------------------------------------- 1 | ## Key focus area 2 | 3 | | 2022 | 2023 | Change | 4 | |---|---|---| 5 | | Increase corporate contributions: getting a few unicorn startups and companies to allocate some engineers to Node.js / Keeping the lights on, build, security releases / Corporate Investment: How do we make it happen? | Increase the outreach to add more collaborators / maintainers / New contributors onboarding / growing long term collaboratos | =/+1 | 6 | | Funnel contributor onboarding into relevant working groups / Communication about initiative and help people to be involved / Could use more followup after Code & Learns / Onboarding the next generation: what happens when we all die | Standards / JavaScript / Introducing and improving standards-based interfaces to encourage their use over existing non-standard equivalents. | new | 7 | | Education | Balancing evolution and stability | new | 8 | | Enabling larger initiatives | Documentation | new | 9 | | Further built in tooling | Performance | +2 | 10 | | Being well welcomed in WG / being well welcomed in working group | Community communication | +2 | 11 | | Faster startup time | Security | new | 12 | | Sustainable outreach / Adjacent community engagement | Observability | new | 13 | 14 | 15 | > More coordination with new contributor and sharing knowledge 16 | 17 | > Core functionnalities around Observability and security while balancing with stability 18 | 19 | > Standardization and Documentation 20 | 21 | ## Obstacles 22 | 23 | | 2022 | 2023 | Change | 24 | |---|---|---| 25 | | Flaky CI / CI reliability / Flaky CITGM / CI time | Node.js core is very complex for new contributors / Mentorship/new contributor on-ramp / Extremely hard ramp up to become a prolific maintainer of Node.js / Maintainer Sustainability / It's often unclear to first time contributors who are the primary reviewers of certain areas of the project. | +1 | 26 | | Lack of "good first issues" | npm / Lack of standardization/specification of package.json | +3 (new functions?) | 27 | | Some niche or complicated areas have a really hard time getting reviews | flaky CI / node.js ci / Flaky tests | -3 | 28 | | Communicating with the community about adding npm module functionalities into core | CI performance, especially on not common combination / CI UX / CI/CD | -4 | 29 | | ESM and CJS interoperability in npm module: do we have a recommandation for the community? | Bun / other javascript runtime. It's will create confusion for junior javascript dev / Deno | new | 30 | | A lot of different topic, how to prioritize | CJS | -1 | 31 | | Timezone / Meeting time for WG | rigidly adhering to web api choices adds burden for node users | new | 32 | | Primordials | Slack is quite big and sometimes is hard to know where to ask specific questions | new | 33 | | Money | | | 34 | | Corporate priorities | | | 35 | | OpenJS Fundation limitations | | | 36 | | Burnout | | | 37 | | Not getting enough contribution from the ecosystem | | | 38 | | Work more asynchronously | | | 39 | 40 | > Flaky tests and CI are still an issue 41 | 42 | > Hard to onboard / have contributor in specific area 43 | 44 | > Lack of standards and some standards are only for web 45 | 46 | ## Working well 47 | 48 | | 2022 | 2023 | Change | 49 | |---|---|---| 50 | | Collaborator Summit | Community | new | 51 | | Onboarding new collaborators | teams and autonmy/indepedence / Working Groups | = | 52 | | PR process | Minimal breakage | +3 | 53 | | New collaborators (seems a lot new people this year than before) | Collaborator summit | -3 | 54 | | OpenSSF contribution to make Node.js more secure | Running part of the projects outside of the main repo. As an exapmle, Undici has a steady flow of collaborators and PRs from individuals. | +1 | 55 | | Making sure the ecosystem is stable and breaking changes are few. Few complaintes from the ecosystem | slack for team | new | 56 | | Automating away a lot of things with labels and GitHub Actions has made the contributing experience friendlier | Youtube/meeting minutes/recording in public | new | 57 | 58 | > Async work 59 | 60 | > Collaborator Summit 61 | 62 | > "External" projects 63 | -------------------------------------------------------------------------------- /collaborator summit/2023-vancouver/technical-priorities.md: -------------------------------------------------------------------------------- 1 | ## Technology trends 2 | 3 | | 2022 | 2023 | Change | 4 | |--- |--- |--- | 5 | | ESM support | Observability / Observability / Diagnostics and Observability | +4 | 6 | | Types in JavaScript (TaC or TS) / Types / Server-Side TypeScript | Performance improvements | new | 7 | | Serverless / Seemless hosting of Node.js server. Support latest version serverless hosting by major cloud providers / Node.js as a cloud function runtime / Cloud deployment | Rust (Easier NAPI / better perf / improve bridge part) | new | 8 | | Small footprint JavaScript runtimes | Web assembly/WASM | +5 | 9 | | Observability (Otel, prometheus, etc.) | Package policies | new | 10 | | Developers-first DX | Supply chain security with respect to dependecies | +4 | 11 | | WinterCG | Rust (and potentially other similar languages) as first-class citizen in core | new | 12 | | http 3 | WinterCG | -1 | 13 | | WASM | Serverless | -6 | 14 | | Supply chain security | JSDoc for generating typescript types | -8 | 15 | | eBPF | larger core stdlib | new | 16 | | Multi-pages Apps (MPAs) / Full-stack JavaScript | HTTP APIs | -5 (WinterCG?) | 17 | | Edge / Can we lift something from workerd? Are there any approches or features? | Server Rendered Web Apps | new | 18 | | GraphQL / gRPC | | | 19 | | Kubernetes / Containerization | | | 20 | | | | | 21 | 22 | > Bridge with other languages seems important, both in core and around Node-API (Rust as main citizen) 23 | 24 | > Observability is one of the big topic - linked to diagnostic channel? 25 | 26 | > New technologies around HTTP and Serverless 27 | 28 | 29 | ## Node.js features 30 | 31 | | 2022 | 2023 | Change | 32 | |--- |--- |--- | 33 | | Docs: production ready recommendations / Rustdoc but make it Node.js / Documentation (better documentation for new people) / Docs best practice for module authors / Docs: official tutorials | First-class Support for TypeScript | new | 34 | | Stable fetch() | New HTTP1/.1 server similar to the undici initiative / Unified HTTP architecture /HTTP/3 | +1 | 35 | | Undici / undici in core | faster startup time | new | 36 | | ESM import mocking | Better perf AsyncLocalStorage | new | 37 | | Hot reload / dev server | opt-in/opt-out from builtin modules | new | 38 | | More complet ESM/CJS interop | node, while aligning itself with browsers, should not shackle itself to browser choices | new | 39 | | More assertion for test runners / | Undici in Node when? | -4 | 40 | | python -m SimpleHTTPServer equivalent | WebSocket | new | 41 | | Better support embedding Node.js into other projects (related to build systems support) | ServiceWorker FetchEvent standard API | +7 | 42 | | Improving performance of Web APIm WHATWG streams specifically | process replacement | new | 43 | | Expanded use of diagnostic channel | packages from cdn (like Deno) | new | 44 | | WASM / WASI status | Vendoring in libraries | new | 45 | | llhttp and its dependency llparse is mostly a blackbox | Import Maps!! / Import maps support | new | 46 | | Disk backed blob object | | | 47 | | Module quality assessment tool: (eg. check if you have dual exports) | | | 48 | | FetchEvent and familly (CloudFlare workers-like server) | | | 49 | | logger | | | 50 | | build in bundler and transpiler | | | 51 | 52 | > TypeScript and types are important 53 | 54 | > Fetch and HTTP / Websocket is important 55 | 56 | > Functionnalities and libraries related to core, browser spec 57 | 58 | 59 | ## Other 60 | 61 | | 2022 | 2023 | Change | 62 | |--- |--- |--- | 63 | | Improving CI reliability | A next generation package registry and accompanying package manager | new | 64 | | CITGM (smoke test suite) maintenance | Performance | new | 65 | | Fuzzing | ensuring a smooth migration story (for any new thing), as a higher priority than the end goal itself | new | 66 | | Competing with Bun and Deno on performances / keep up with them | | | 67 | | Vulnerability management | | | 68 | 69 | > New package manager 70 | 71 | > Performance -------------------------------------------------------------------------------- /meetings/2020-07-15.md: -------------------------------------------------------------------------------- 1 | Attendees: 2 | 3 | * Michael Dawson (@mhdawson) 4 | * Divy Tolia (@designmoreweb) 5 | * Bradley Farias (@bmeck) 6 | * Andrey Pechkurov (@puzpuzpuz) 7 | * Richard Lau (@richardlau) 8 | * Chengzhong Wu (@legendecas) 9 | * Beth Griggs (@BethGriggs) 10 | * Bryan English (@bengl) 11 | * Darcy Clarke (@darcyclarke) 12 | * Matheus Marchini (@mmarchini) 13 | * Jean Burellier (@sheplu) 14 | 15 | 16 | Google doc from first session: https://docs.google.com/document/d/1oBC-l6lTSjKijhwXeJXgBcz4qNPDZlkj4DFKGgWNvV8/edit#heading=h.kfsrb8jml706 17 | 18 | 19 | Proposed Agenda 20 | 21 | * Logistics, schedule etc. 22 | * Matheus, not sure we need a WG, but generating issues would help people know when the 23 | meetings are, we likely need several meetings 24 | * Michael volunteer to add calendar/auto generation 25 | * Try to figure out time in a separate issue, 26 | * Matheus may need to rotate time, how about use alternate to TSC meetings. 27 | * Michael that makes sense, no objections from any others 28 | * Michael Bi-weekly or monthly 29 | * Bethany likely needs to be bi-weekly otherwise due to timezones it may be a long time 30 | between seeing people. 31 | * Michael, where should issues 32 | * Bethany likely need to generate meeting issues, likely new repo at least for auto meetings 33 | and minutes 34 | * Volunteer to create issue to request repo? 35 | 36 | * Discuss initial priority work streams (1-2 I think) 37 | 38 | 39 | * Continue discussion on Technical Evolution 40 | * Key technology trends and Node.js 41 | * Priority Themes/Strategic investment areas (roadmap, technical strategy or whatever?) 42 | * Priority of constituencies, hierarchy of priorities 43 | * what gets into core, 44 | 45 | * Talked about first doc we should contribute to core which would include 46 | 47 | * Intro 48 | * Mission 49 | * Values of the project, and priority list 50 | * Prefer X over y 51 | * Key technical areas for next 10 years 52 | -------------------------------------------------------------------------------- /meetings/2020-07-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-07-29 2 | 3 | ## Links 4 | 5 | 6 | * **Recording**: https://youtu.be/5vpZzMRj4m0 7 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/3 8 | 9 | ## Present 10 | 11 | * Michael Dawson (@mhdawson) 12 | * Wes Todd (@wesleytodd) 13 | * Andrey Pechkurov (@puzpuzpuz) 14 | * Beth Griggs (@BethGriggs) 15 | * @mmarchini 16 | * Divy Tolia (@designmoreweb) 17 | * Joe Sepi (@joesepi) 18 | * Chengzhong Wu (@legendecas) 19 | * Jean Burellier (@sheplu) 20 | 21 | ## Agenda 22 | 23 | ## Announcements 24 | 25 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 26 | 27 | ### nodejs/next-10 28 | 29 | * Values/directions document for core [#2](https://github.com/nodejs/next-10/issues/2) 30 | * From discussion in the meeting today lets start with the name for the file being `mission.md` 31 | * Values Brainstorm, initial list: 32 | * version from html spec as one example: https://www.w3.org/TR/html-design-principles/#priority-of-constituencies 33 | * Values should be a general suggestion, not a hard rule 34 | * Wes, this is around technical values, other values are important but not covered here. Make sure to clarify that up front. 35 | * Approachability (both technical and community) 36 | * Stability 37 | * User experience 38 | * Developer experience 39 | * Community 40 | * Security 41 | * Backwards compatibility(?) 42 | * Performance 43 | * Diagnostics 44 | * Maintainability 45 | * Web API compatibility 46 | * Ecosystem (from FunRetro) 47 | * Collaborator Velocity 48 | * Great Documentation 49 | * Adoption of new technologies 50 | * Simplicity over complexity 51 | * Planning for today versus all possible future options, Avoid needless complexity 52 | * Tight focus/minimal surface 53 | * Same as small core? - was trying to capture without saying that :) 54 | * “Right sized core”? I think we want to have a discussion around the balance between 55 | “small” and still providing the most value 56 | * LTS support for users still using older versions of Node 57 | * Clear expectations set around support? 58 | * Yes, also for people who use different flavors of linux or other operating systems less popular than windows, mac and ubuntu 59 | * I think that falls more under supported platforms 60 | * Suitability for cloud/deployments? 61 | * Suitability for IoT (e.g. low memory footprint)? 62 | 63 | * We should make a clear list of constituencies, brainstormed list: 64 | * Direct end users 65 | * Users who run tools themselves (install Node, run tool, deal with errors) 66 | * Application operators 67 | * Application Developers 68 | * front-end tool consumers 69 | * back-end server authors 70 | * hobby developers 71 | * professional developers 72 | * tool authors 73 | * library/package authors 74 | * Node.js core maintainers 75 | 76 | * Next steps 77 | * Open PR to capture constituencies in repo (Matheus) 78 | * Open issue with values and ask people to comment on their ranking of priorities, and tag for 79 | the agenda for next time. (Michael) 80 | 81 | ## Q&A, Other 82 | 83 | 84 | ## Upcoming Meetings 85 | 86 | 87 | NOTE: had to see the time for the next meeting to 10-11 EST (same as this time) as the other 88 | 2 TSC timeslots already have a meeting scheduled during that week. 89 | 90 | 91 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 92 | 93 | 94 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 95 | -------------------------------------------------------------------------------- /meetings/2020-08-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-08-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/zF8ZV57hj-8 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/9 7 | 8 | ## Present 9 | 10 | *Michael Dawson (@mhdawson) 11 | * Stephen Belanger (@qard) 12 | * Jean Burellier (@sheplu) 13 | * Beth Griggs (@BethGriggs) 14 | * Mary Marchini 15 | * Wesley Todd 16 | * Matteo Colina 17 | * Divy 18 | * Tierney Cyren 19 | 20 | ## Agenda 21 | 22 | 23 | ## Announcements 24 | 25 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 26 | 27 | 28 | ### nodejs/next-10 29 | 30 | 31 | * [chore(doc): add initial Constituencies document](https://github.com/nodejs/next-10/pull/7) 32 | * lets review/land in this group, FYI node.js collaborators and incorporate feedback as we get 33 | it. 34 | 35 | * Prioritizing Technical Values [#5](https://github.com/nodejs/next-10/issues/5) 36 | 37 | * Doc that we used to disucuss/brainstorm: https://docs.google.com/document/d/1sbO_zCn9n_JH2zuGtqNAahUhA_mGFA89DdAme8nEdsw 38 | * Michael will take action to open PR based on the discussion. 39 | 40 | * Values/directions document for core [#2](https://github.com/nodejs/next-10/issues/2) 41 | * We ran out of time before getting to this one 42 | 43 | ## Q&A, Other 44 | 45 | ## Upcoming Meetings 46 | 47 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 48 | 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2020-09-02.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-09-02 2 | 3 | ## Links 4 | 5 | 6 | * **Recording**: https://youtu.be/vvVPozqnkcI 7 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/15 8 | 9 | ## Present 10 | 11 | * Next 10 years team: @nodejs/next-10 12 | * Myles Borins (@MylesBorins) 13 | * Andrey Pechkurov (@puzpuzpuz) 14 | * Ruy Adorno (@ruyadorno) 15 | * Darcy Clarke (@darcyclarke) 16 | * Jean Burellier (@sheplu) 17 | * Michael Dawson (@mhdawson) 18 | 19 | ## Agenda 20 | 21 | 22 | ## Announcements 23 | 24 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 25 | 26 | ### nodejs/next-10 27 | 28 | 29 | * Prioritizing Technical Values [#5](https://github.com/nodejs/next-10/issues/5) 30 | * We spent the meeting working on PR https://github.com/nodejs/next-10/pull/11 which covers the 31 | technical values and the prioritization 32 | * Its looking pretty good, please review/comment hoping we can land later this week, followed by PR for core 33 | under [#2](https://github.com/nodejs/next-10/issues/2). 34 | 35 | 36 | * Values/directions document for core [#2](https://github.com/nodejs/next-10/issues/2) 37 | * This will be based on the PR we discussed today as part of [#5](https://github.com/nodejs/next-10/issues/5) 38 | 39 | 40 | 41 | ## Q&A, Other 42 | 43 | 44 | ## Upcoming Meetings 45 | 46 | 47 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 48 | 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2020-09-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-09-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/xeXjCK4fCIA 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/18 7 | 8 | ## Present 9 | * Michael Dawson (@mhdawson) 10 | * Wes Todd (@wesleytodd) 11 | * Darcy Clarke (@darcyclarke) 12 | * Ruy Adorno (@ruyadorno) 13 | * Jean Burellier (@sheplu) 14 | * Joe Sepi (@joesepi) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 25 | * added by Mary, one of the things we should consider as next step 26 | 27 | * Prioritizing Technical Values [#5](https://github.com/nodejs/next-10/issues/5) 28 | * Values/directions document for core [#2](https://github.com/nodejs/next-10/issues/2) 29 | * PR open don’t need more discussion https://github.com/nodejs/node/pull/35145 30 | 31 | * Discussion on what our next major focus area should be. 32 | * what we should do on the collaborator front [#16](https://github.com/nodejs/next-10/issues/16) 33 | * steps toward technical priorities 34 | 35 | * We spent most of the time discussion the steps toward technical priorities. 36 | * Discussion around how we get feedback from the right people get the right people involved 37 | * Discussion on constituencies and what is important to them as next step for defining 38 | Technical priorities. We should be able to map the priorities back to the constituencies. 39 | * Noticed gap in that we are missing enterprises as a constituency 40 | * We brainstormed the following addition 41 | * Organizations with investments in Node.js (eg: Enterprises, Government bodies, startups, non-profits) 42 | * Darcy will PR in. 43 | * Discussed that next focus area should be what does each constituencies need 44 | * This should actually include [#16](https://github.com/nodejs/next-10/issues/16) as the Node.js maintainers 45 | are one of the constituencies listed. 46 | * Next meeting to brainstorm on what each constituency needs 47 | * Action -> Darcy to set up boards, for each constituency, with following headings: need, don’t 48 | need, want, don’t want 49 | 50 | ## Q&A, Other 51 | 52 | ## Upcoming Meetings 53 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /meetings/2020-10-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-10-01 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=aYVhHONKads 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/22 7 | 8 | ## Present 9 | * Stephen Belanger (@qard) 10 | * Mary Marchini (@mmarchini) 11 | * Jean Burellier (@sheplu) 12 | * Michael Dawson (@mhdawson) 13 | * Wes 14 | * Tierney 15 | * Ruy 16 | * ? 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | * Wes, having a lot of discussion on the future of HTTP in the web frameworks team/discussion. 25 | 26 | ### nodejs/node 27 | 28 | * doc: add compatibility/interop technical value [#35323](https://github.com/nodejs/node/pull/35323) 29 | * Spent first half of meeting on this. Want to balance that compatibility is 30 | important but at the same time does not override everything else and there are 31 | cases where it does not make sense. 32 | 33 | ### nodejs/next-10 34 | 35 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 36 | * Defer to next meeting. 37 | 38 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 39 | * Need more answers. So please fill it in. (link in the issue) 40 | 41 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 42 | * spend the second half of the meeting focussed on this. 43 | 44 | ## Q&A, Other 45 | 46 | 47 | ## Upcoming Meetings 48 | 49 | 50 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 51 | 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | -------------------------------------------------------------------------------- /meetings/2020-10-28.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-10-28 2 | 3 | 4 | ## Links 5 | 6 | 7 | * **Recording**: https://youtu.be/piqjhC4ZXBI 8 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/29 9 | 10 | 11 | ## Present 12 | 13 | 14 | * Michael Dawson (@mhdawson) 15 | * Ben Coe 16 | * Tierney Cyren 17 | * Wes Todd 18 | * Jean Burellier (@sheplu) 19 | 20 | 21 | ## Agenda 22 | 23 | 24 | ## Announcements 25 | 26 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 27 | 28 | 29 | ### nodejs/node 30 | 31 | 32 | * doc: add compatibility/interop technical value [#35323](https://github.com/nodejs/node/pull/35323) 33 | * Discussed a bit more, We will add suggested path forward, but also see if Geoffery can make 34 | it to the next next-10 meeting so we can discuss real-time 35 | 36 | 37 | ### nodejs/next-10 38 | 39 | 40 | * We had a working session on this and update results are in the issue. 41 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 42 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 43 | 44 | 45 | 46 | 47 | ## Q&A, Other 48 | 49 | 50 | ## Upcoming Meetings 51 | 52 | 53 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 54 | 55 | 56 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 57 | -------------------------------------------------------------------------------- /meetings/2020-11-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2020-11-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/3M6qN-u6CTM 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/32 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Geoffrey Booth (@GeoffreyBooth) 12 | * Wes Todd (@wesleytodd) 13 | * Mary Marchini (@mmarchini) 14 | * Christopher Hiller (@boneskull) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/node 23 | 24 | * doc: add compatibility/interop technical value [#35323](https://github.com/nodejs/node/pull/35323) 25 | * Proposed text: “Maximizing compatibility and interoperability with browsers and other 26 | JavaScript environments” 27 | 28 | * Other proposals: 29 | * Compatibility and interoperability with browsers and other JavaScript environments where it makes sense 30 | 31 | * agreed the following seemed good 32 | * Compatibility and interoperability with browsers and other JavaScript environments so that as 33 | much code as possible runs as is both in Node.js and in the other environments 34 | 35 | * Other notes 36 | * Add intro to the doc explaining that this should be revisited from time to time. This is a guide for making decisions but not a substitute for deliberation. Different subsystems may have different priorities. Tracking issue: [#34](https://github.com/nodejs/next-10/issues/34) 37 | 38 | 39 | ### nodejs/next-10 40 | 41 | Ran out of time to get to the rest of the issues, will tackle next time: 42 | 43 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 44 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 45 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 46 | 47 | 48 | ## Q&A, Other 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 53 | 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /meetings/2021-01-06.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-01-06 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=GwtF6SnfUdw&ab_channel=node.js 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/38 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Jean Burellier (@sheplu) 13 | * Beth Griggs (@BethGriggs) 14 | * Tierney Cyren 15 | * Bradley Farais 16 | * Ruy Adorno 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | * No announcements this week. 25 | 26 | ### nodejs/next-10 27 | 28 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 29 | * We spend all of the time reviewing/updating the issue 30 | * Next steps are to finish review and discuss how we should get broader input 31 | 32 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 33 | * skipped until next time 34 | 35 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 36 | * skipped until next time 37 | 38 | ## Q&A, Other 39 | 40 | 41 | ## Upcoming Meetings 42 | 43 | 44 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 45 | 46 | 47 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 48 | -------------------------------------------------------------------------------- /meetings/2021-01-21.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-01-21 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/15NaXM5xWv4 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/41 7 | 8 | 9 | ## Present 10 | 11 | * Michael Dawson (@mhdawson) 12 | * Darcy Clarke (@darcyclarke) 13 | * Ruy Adorno (@ruyadorno) 14 | * Tierney Cyren (@bnb) 15 | * Jean Burellier (@sheplu) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | 24 | ### nodejs/next-10 25 | 26 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 27 | * https://github.com/nodejs/next-10/blob/main/CONSTITUENCY-NEEDS.md is what we have landed. 28 | * How do we get confirmation that we get it right 29 | * survey 30 | * Which constituencies are part of? 31 | * Please check those which are important to you (with list from table) 32 | * What needs do you have which are not covered in the list? 33 | * Are you part of a constituency that is not covered? 34 | * Is there anything else you would want to add on this topic? 35 | * Are you interested in joining a group session to discuss the constituencies and needs? 36 | * Are you interested in participating in a one-on-one session to discuss the constituencies and needs? 37 | 38 | * Michael will send email to Foundation communications team and Joe to ask for Survey, Tierney will 39 | work with them to agree demographic questions that we should include. 40 | 41 | * user interviews 42 | * One group session - based on answer to survey 43 | * Tierney happy to set up and run several individual sessions, based on answers to survey 44 | 45 | * Tweets from node.js account 46 | * promote survey, option for group/one-on-one sessions as follow up. 47 | 48 | * email to Foundation members 49 | * use the same questions as the survey, but have second copy of the survey so that 50 | we know what foundation member responses look like versus the overall community. 51 | 52 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 53 | * Worked on fun retro to brainstorm - https://easyretro.io/publicboard/cLBIBu3wA2Um7qIziXq1zmC4gdi1/f2334393-fe0f-4202-8ee5-0ef677e0ff9e?sort=votes 54 | * Create issue to have fun retro we tweet out to get broader input. New issue - https://github.com/nodejs/next-10/issues/43. 55 | 56 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 57 | * Skipped until we have Mary to help lead 58 | 59 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 60 | * Skipped until we have Mary 61 | 62 | 63 | ## Q&A, Other 64 | 65 | 66 | ## Upcoming Meetings 67 | 68 | 69 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 70 | 71 | 72 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 73 | -------------------------------------------------------------------------------- /meetings/2021-02-04.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-02-04 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=xJm8tICkxVA&ab_channel=node.js 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/45 7 | 8 | ## Present 9 | 10 | * Michael Dawson(@mhdawson) 11 | * Ian Sutherland (@iansu) 12 | * Joe Sepi (@joesepi) 13 | * Jean Burellier (@sheplu) 14 | * Darcy Clarke (@darcyclarke) 15 | * Mary Marchini (@mmarchini) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Joe - Node.js survey is open, link on website. 22 | 23 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | ### nodejs/next-10 26 | 27 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 28 | * Darcy will open close of initial EasyRetro and well ask collaborators to 29 | add to that and then discuss next time. 30 | 31 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 32 | * First cut done, Michael will close 33 | * Will open new issue to track work to get broader input. 34 | 35 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 36 | * our current contribution workflow, consensus seeking model, leadership model, etc 37 | * Barrier to start contributing is still high 38 | * custom commit message 39 | * requires time building, 40 | * takes time for PRs to be merged 41 | * Has been brought up a few times that lazy consensus might not be scaling 42 | * may favor some (privileged) 43 | * may disfavor others (less time and/or ability to focus on contributing) 44 | * We did some brainstorming in this Easy Retro for this conversation: 45 | https://easyretro.io/publicboard/8284sHrgEOQQG7KZMlDeSoYfTq73/bbf510ad-bc9c-41f7-ab8c-ea19a1fc8377 46 | 47 | * Revisit time slots [#13](https://github.com/nodejs/next-10/issues/13) 48 | * Adjusted to Thurs at 12 ET, will that out for a while. 49 | * Closed out this issue. 50 | 51 | 52 | 53 | 54 | ## Q&A, Other 55 | 56 | 57 | ## Upcoming Meetings 58 | 59 | 60 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 61 | 62 | 63 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 64 | -------------------------------------------------------------------------------- /meetings/2021-02-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-02-11 2 | 3 | 4 | ## Links 5 | 6 | 7 | * **Recording**: https://youtu.be/mO67YUEAmAU 8 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/47 9 | 10 | ## Present 11 | 12 | * Michael Dawson (@mhdawson) 13 | * Wes Todd (@wesleytodd) 14 | * Darcy Clarke (@darcyclarke) 15 | * Tierney Cyren (@bnb) 16 | * Jean Burellier (@sheplu) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | * No annoucements this week 25 | 26 | 27 | ### nodejs/next-10 28 | 29 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 30 | * new Retro to get additional feedback - 31 | https://easyretro.io/publicboard/cLBIBu3wA2Um7qIziXq1zmC4gdi1/1db5ea23-fee3-4da0-bb7b-a5ea49d810e7 32 | * we discussed how to get input 33 | * as next step agreed to create node discussion to ask for more input: https://github.com/nodejs/node/discussions/37323 34 | * Agreed to park this until next meeting where we can look at the additional input. 35 | 36 | * Needs/want of constituencies [#20](https://github.com/nodejs/next-10/issues/20) 37 | * We have agreement to launch the survey First thing in March 38 | * created this issue to track -> https://github.com/nodejs/next-10/issues/48 39 | 40 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 41 | * Going to wait for next meeting until we have Mary 42 | 43 | ## Q&A, Other 44 | 45 | 46 | ## Upcoming Meetings 47 | 48 | 49 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 50 | 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | -------------------------------------------------------------------------------- /meetings/2021-03-25.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-03-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/c4g-NSZQjG4 6 | * **GitHub Issue**: https://github.com/nodejs/next-10/issues/54 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Tierney Cyren (@bnb) 12 | * Jean Burellier (@sheplu) 13 | * Beth Griggs (@BethGriggs) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * Our survey went out, if you can please fill it out - 22 | 23 | ### nodejs/next-10 24 | 25 | * Survey to get feedback on needs of constituencies [#48](https://github.com/nodejs/next-10/issues/48) 26 | * Launched a few weeks back, good turn out, already good number of responses but still 27 | working promote to get more. 28 | 29 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 30 | * looked at the board we created to get broader input, added @ mentions to try to get more 31 | input 32 | * will wait on that input before discussing further. 33 | 34 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 35 | * Defer until we have Mary as she was helping to champion. 36 | 37 | ## Q&A, Other 38 | 39 | ## Upcoming Meetings 40 | 41 | * **Node.js Foundation Calendar**: 42 | 43 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 44 | -------------------------------------------------------------------------------- /meetings/2021-04-08.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-04-08 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Bradley Farias 12 | * Jean Burellier 13 | * Darcy Clarke 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Meeting time 24 | * The new time does not seem to be working so well 25 | * Michael will create issue to try and find a better time 26 | 27 | * Survey to get feedback on needs of consituencies [#48](https://github.com/nodejs/next-10/issues/48) 28 | * ~2500 responses 29 | * agreed that one last “it’s your last chance” and then close in end of next week 30 | 31 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 32 | * discussion around security policy/supporting info 33 | * We could write up some cases where security compromise made sense 34 | * Darcy - might be good as practice to start documenting when 2 values are at odds 35 | When we make a decision, capture its somewhere 36 | * Key thing could be to build process/data to help project make decisions with conflicting 37 | values/constituencies, start by documenting historical data 38 | * Also discussed well defined security model, and supporting pieces could be one of the 39 | important things 40 | 41 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 42 | * skipped for this time 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Foundation Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2021-05-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-05-10 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Wes Todd (@wesleytodd) 12 | * Chengzhong Wu (@legendecas) 13 | * Beth Griggs (@BethGriggs) 14 | * Jean Burellier (@sheplu) 15 | * Tierney 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | * Many thanks to the over 2800 people who completed the survey! 21 | 22 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/next-10 25 | 26 | * Survey to get feedback on needs of constituencies [#48](https://github.com/nodejs/next-10/issues/48) 27 | 28 | * Good review/discussion on constituencies as reported in the survey. 29 | * From that agreed we should add 2 new constituencies(still need a bit of refinement): 30 | * Education: Teachers, students, programs to help people learn Node.js(college, University, boot camps, learning resources etc.), programs to help people demonstrate capability(certification programs). 31 | * Security Practitioners: people involved in the life-cycle of security issues. Penetration testing, incident response, CVE scanning, remediation, legal, PR. etc. 32 | * We also agreed we needed to tweak the content of the others a bit 33 | * [Wes] Add cli support to the app developer/lib author/end user 34 | * [Michael] - What about standards? 35 | 36 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 37 | * Ran out of time, will cover next time 38 | 39 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 40 | * Ran out of time, will cover next time 41 | 42 | ## Q&A, Other 43 | 44 | ## Upcoming Meetings 45 | 46 | * **Node.js Foundation Calendar**: 47 | 48 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 49 | -------------------------------------------------------------------------------- /meetings/2021-06-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-06-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@shepsheplu) 12 | * Chengzhong Wu (@legendecas) 13 | * Stephen Belanger (@qard) 14 | * Wes Todd (@wesleytodd) 15 | * Beth Griggs (@BethGriggs) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Survey to get feedback on needs of constituencies [#48](https://github.com/nodejs/next-10/issues/48) 26 | * Additional need -> Assets that show Node.js is a good choice. 27 | * Maybe better about page on website 28 | * Typescript was mentioned as a need multiple times 29 | * Game developers 30 | * Stephen 31 | * looking forward to QUIC 32 | * WebGL support would also be nice (run-anywhere style, webaudio as well etc.) 33 | * A few requests in terms of missing APIs 34 | * Standard library request 35 | * http api to replace frameworks 36 | * Version management 37 | * should we add nvm to the docs? 38 | 39 | * Want to be able to think less about what they are pulling in. 40 | * package maintenance wg may be part of where this discussion should take place 41 | 42 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 43 | * ran out of time, keep on agenda for next time 44 | 45 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 46 | * ran out of time, keep on agenda for next time 47 | 48 | 49 | ## Q&A, Other 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Node.js Foundation Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /meetings/2021-07-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-07-12 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Tierney Cyren 12 | * Joe Sepi (@joesepi) 13 | * Beth Griggs (@BethGriggs) 14 | * Bradley Farias (@bmeck) 15 | * Jean Burellier (@sheplu) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | * Planning a min-summit for 24 | 25 | ### nodejs/next-10 26 | 27 | * Survey to get feedback on needs of consituencies [#48](https://github.com/nodejs/next-10/issues/48) 28 | * Version Management 29 | * We should add to the list of constituencies 30 | * linter 31 | * Bradley, common default rules would be biggest benefit 32 | * Tierny, only for “just starting” and then likely follow team based rules 33 | * global cache for libraries 34 | * Bradley, used to be node_libraries in the past, but removed as it was problematic in the past. 35 | * install to well known directory that is shared across working directories 36 | * we already have tools doing this, pnpm, npm, what can we do versus 37 | * add package management as one of the needs, mention that it’s like to be out of scope for core project. (Expand Module/dependency info and management) 38 | * Confidence in security of widely used “should be in more”, 39 | * Add need, Common solid base along the lines of Standard library, commonly used, common functionality beyond the APIs in core 40 | 41 | * Packaging and distribution for deployments 42 | * Embedder API (now only C++) 43 | * Packaging node with rest of app versus other environments where you can drop a single file on disk. 44 | * Boxnode is an example, 45 | * Add as need Bundling/ember 46 | 47 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 48 | * No time deferred to next time 49 | 50 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 51 | * No time deferred to next time 52 | 53 | ## Q&A, Other 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Node.js Foundation Calendar**: 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | -------------------------------------------------------------------------------- /meetings/2021-08-23.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-08-23 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Jean Burellier (@sheplu) 12 | * Joe Sepi (@joesepi) 13 | * Michael Dawson (@mhdawson) 14 | * Darcy Clarke (@darcyclarke) 15 | * Bradley 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Survey to get feedback on needs of consituencies [#48](https://github.com/nodejs/next-10/issues/48) 26 | * Closed as survey is complete and results are landed. 27 | 28 | * Key Technical Areas - Brainstorm to generate list [#39]() 29 | * closing as covered in mini-summit and we will open follow on issues as outlined in: [#82] 30 | 31 | * Next 10 years for collaborators [#16](https://github.com/nodejs/next-10/issues/16) 32 | * closing as covered in mini-summit and we will open follow on issues as outlined in: [#82] 33 | 34 | * Created a number of issues for the follow ons from the summit 35 | * 36 | * 37 | * 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Foundation Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /meetings/2021-09-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-09-27 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | 13 | ## Agenda 14 | 15 | ## Announcements 16 | 17 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 18 | 19 | ### nodejs/node 20 | 21 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 22 | * No update this week. 23 | 24 | ### nodejs/next-10 25 | 26 | * Technical Priority Deep Dive - Documentation [#89](https://github.com/nodejs/next-10/issues/89) 27 | * Deferred until we have more attendees 28 | 29 | * deep dive on Maintaining/growing the level of contribution in future Next-10 meeting [#86](https://github.com/nodejs/next-10/issues/86) 30 | * Deferred until we have more attendees 31 | 32 | * Draft content of technical priorities for PR to Node.js core [#84](https://github.com/nodejs/next-10/issues/84) 33 | * Discussed the current draft based on brainstorms and discussion in mini-summit. 34 | * Agreed we’ll create the PR to kick of the next discussion and go from there. 35 | 36 | * Key Technical Areas - Brainstorm to generate list [#39](https://github.com/nodejs/next-10/issues/39) 37 | * Should have been closed already, Michael closed for real this time. 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Foundation Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /meetings/2021-10-13.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-10-13 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Beth Griggs (@BethGriggs) 13 | * Tierney Cyren (@bnb) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * Priorities PR is open, getting some discussion - 22 | 23 | ### nodejs/node 24 | 25 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 26 | * Skipped, discuss next time 27 | 28 | ### nodejs/next-10 29 | 30 | * Technical Priority Deep Dive - Documentation [#89](https://github.com/nodejs/next-10/issues/89) 31 | * Discussed what we should be doing. Electron has a set of tools that help them ensure more 32 | consistent and well structured docs. 33 | * Tierney is going to put together an issue in the Next-10 34 | repo with proposal that includes: benefits, approach, next steps 35 | * Discussed translations, is this key/holding us back ? 36 | * Python/ruby do have a number of translations 37 | * For Java we did not find any 38 | * Certifications were translated 39 | * Maybe we can ask the Foundation in terms of how they see the importance 40 | * Tierney looking at where we get downloads/not might also give us some info 41 | * Electron uses crowdin 42 | * Michael will open issue to discuss how critical we think translations are to future Node.js success 43 | 44 | * Planning deep dives 45 | * We discussed that it seems hard to get regular attendance. Still finding a good time. 46 | * Beth suggested could make sense to repeat the mini-summit that seemed to work pretty well. 47 | * We agreed to do mini summit covering these two topics 48 | * Suitable types for end-users 49 | * Single Executable Applications 50 | * Michael will create issue to plan mini-summit 51 | 52 | * deep dive on Maintaining/growing the level of contribution in future Next-10 meeting [#86](https://github.com/nodejs/next-10/issues/86) 53 | * skipped as we were out of time 54 | 55 | * Draft content of technical priorities for PR to Node.js core [#84](https://github.com/nodejs/next-10/issues/84) 56 | * close since PR is opened. 57 | 58 | ## Q&A, Other 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Node.js Foundation Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | -------------------------------------------------------------------------------- /meetings/2021-10-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-10-27 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Tierney Cyren (@bnb) 13 | * Joe Sepi (@joesepi) 14 | * Bradley Farias 15 | * Parris Lucas 16 | * Beth Griggs (@BethGriggs) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/node 25 | 26 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 27 | * Continue to work on it. Have a good image which is a good dev image 28 | * Challenge is to get it small enough so that CodeSpaces will launch in standard image (32G) 29 | * Good discussion about why might be so big 30 | * May be due to using in debug, agreed that non-debug would be a good start and it useful for most of the time. 31 | 32 | ### nodejs/next-10 33 | 34 | * Planning for summit 35 | * We agreed it would cover 36 | * Suitable types for end-users 37 | * Single Executable Applications 38 | * Target Nov 18 10-2 ET 39 | * Put TSC agenda, post a collaborators discussion, Tierney will see if somebody from Types 40 | Team, Node.js tweet. 41 | 42 | * Technical Priority Deep Dive - Documentation [#89](https://github.com/nodejs/next-10/issues/89) 43 | * Next steps are 44 | * Tierney is going to put together an issue in the Next-10 45 | repo with proposal that includes: benefits, approach, next steps 46 | * Michael will open issue to discuss how critical we think translations are to 47 | future Node.js success 48 | 49 | * deep dive on Maintaining/growing the level of contribution in future Next-10 meeting [#86](https://github.com/nodejs/next-10/issues/86) 50 | * Challenges in contributing 51 | * Assumed, harder to get investment both company and individual 52 | * Requires sustained contribution over time 53 | * Two types of contributions 54 | * Scratching and itch/solving personal problem 55 | * Moving the platform forward 56 | * We need boiler plate pitch, TSC members available to talk to leadership in companies 57 | Networking/social 58 | * Potential roadblocks 59 | * How easy to ramp up 60 | * Support from employer 61 | * Interest 62 | 63 | ## Q&A, Other 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Node.js Foundation Calendar**: 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | -------------------------------------------------------------------------------- /meetings/2021-11-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-11-10 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Richard Dixon 11 | * Tierney 12 | * Michael Dawson (@mhdawson) 13 | * Beth Griggs 14 | * Joe Sepi 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/node 23 | 24 | * Mini summit 25 | * Issue in DT, some interest in being involved, 26 | * Should invite Anna on the single binary front 27 | * Vercel, ncc (cli), Tierney will figure out who to invite. 28 | 29 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 30 | * Updated issue in node core with status, general agreement that we should move forward 31 | * Next steps create an issue in admin, to move repo into Node.js project 32 | * PR dev container to node core, and set up actions to build/publish. Hopeful that we can get 33 | an extra-large runner from the GitHub actions team. 34 | 35 | ### nodejs/next-10 36 | 37 | * Technical Priority Deep Dive - Documentation [#89](https://github.com/nodejs/next-10/issues/89) 38 | * Skipped for this week 39 | 40 | * deep dive on Maintaining/growing the level of contribution in future Next-10 meeting [#86](https://github.com/nodejs/next-10/issues/86) 41 | * Skipped for this week 42 | 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Foundation Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2021-12-08.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2021-12-08 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Beth Griggs (@BethGriggs) 12 | * Jean Burellier (@sheplu) 13 | * Joe Sepi (@joesepi) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/node 22 | 23 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 24 | * Issue in admin repo to move repo that @bnb has been working on to the Node.js report - 25 | 26 | * No objections so we just need to give access to right people and then it can be moved over 27 | 28 | ### nodejs/next-10 29 | 30 | * Actions from next-10 summit 31 | * Opened this issue - 32 | * Discussion issue - 33 | * PR to add style guide needed to parse docs 34 | * 35 | * Next step is likely to close that PR and then open a new PR to add the structural changes 36 | needed into the existing style guide. 37 | * Think @bnb is working on that. 38 | * Further explore Electron TypesParser to see if it can be used to generate JSON for Node.js project 39 | * Looked at parser and created PR - 40 | * There was another PR earlier that was larger change but likely more complete that 41 | stalled out. 42 | 43 | * Planning for next mini-summit 44 | * Michael what would be the next to cover? 45 | * Jean, documentation would be good as it links to discussion around electron style 46 | guide as well as other issues that are in active discussion 47 | * Beth, Modern HTTP seems like a good choice. We should talk to the Undici team 48 | and James who is working on QUIC team to see if that makes sense. 49 | * Joe will reach out to them to start the discussion 50 | * James talks about HTTP3/QUIC 51 | * Lets target Thursday the 27th from 10-2 ET 52 | 53 | * Lets cancel meeting on Dec 22nd. 54 | 55 | ## Q&A, Other 56 | 57 | ## Upcoming Meetings 58 | 59 | * **Node.js Foundation Calendar**: 60 | 61 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 62 | -------------------------------------------------------------------------------- /meetings/2022-01-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-01-19 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Michael Dawson (@mhdawson) 12 | * Bradley Farias (@bmeck) 13 | * Jean Burellier (@sheplu) 14 | * Ruy 15 | * Tierney (@bnb) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/node 24 | 25 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 26 | * Tierney - 27 | * built/functional 28 | * working on getting the Node.js user on docker hub 29 | * Bradley did we figure out if it would work with codespaces? 30 | * Yes, once added, was looking to see if we can get resources 31 | * Already have some minutes in the free tier 32 | 33 | * node: document flow for supporting type generation - 34 | * FYI to team to help get landed. 35 | 36 | ### nodejs/next-10 37 | 38 | * Mini Summit 17 Jan 10 ET 39 | * Discussed who/how to make sure those interested in Docs, modern http are aware 40 | * Tierney will tweet out from Node.js account 41 | * Bradley and others will also tweet out promote 42 | * Good discussion of how we get things like this into the weekly newsletters that go out 43 | * Bradley and Tierney have reached out to a couple 44 | * Bradley will open an issue in the Next-10 issue on how we can better do this. 45 | * Jean asked about the summit and if we should propose a session 46 | * All agreed that was a good idea. 47 | 48 | ## Q&A, Other 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Node.js Foundation Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | -------------------------------------------------------------------------------- /meetings/2022-02-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-02-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Beth Griggs (@BethGriggs) 12 | * Ruy Adorno (@ruyadorno) 13 | * Arnaud Debec (@arnaud_debec) 14 | * Jean Burellier (@sheplu) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/node 23 | 24 | * build: provide pre-built nodejs/node images or cache [#39672](https://github.com/nodejs/node/issues/39672) 25 | * No major update this week. 26 | 27 | ### nodejs/next-10 28 | 29 | * Summit recap and next steps - 30 | * plan for modern http - 31 | * Michael gave an overview, agreeing that with the doc capturing the strategy we are in a decent state on this front for modern http so only next step is to plan to revisit in 3 months or something like that. 32 | * Ruy asked about how we make sure collaborators are: 33 | * aware of the strategy and related docs 34 | * know they can change/make additions 35 | * know they can participate in Next-10 and future mini-summits 36 | * Should some of the other team’s docs point to these docs as well? 37 | * Next actions (Michael volunteered to create issues for these) 38 | * PR in references to the collaborator onboarding docs 39 | * Look at Undici docs to see where it would make sense to PR in references 40 | * Plan for session in the collaborator summit at OpenJS World 41 | (hopefully cross everybody versus breakout) + breakout sessions 42 | * Second session was on documentation 43 | * Concrete next steps 44 | * PR into for now that every method should have an example. 45 | * PR into - documentation for the metadata and how it is used. Michael will create issue in Next-10 to track that work - create issue to document metadata. 46 | 47 | * Beth should next-10 be a strategic initiative ? 48 | * Michael: makes sense to me. Lets do it. 49 | 50 | * We discussed issues/tagged a number for discussion in the next meeting. 51 | 52 | ## Q&A, Other 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Node.js Foundation Calendar**: 57 | 58 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 59 | -------------------------------------------------------------------------------- /meetings/2022-03-02.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-03-02 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Jean Burellier (@sheplu) 13 | * Beth Griggs (@BethGriggs) 14 | * Costas 15 | * Bradley Farias 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Identify next mini-summit topics [#117](https://github.com/nodejs/next-10/issues/117) 26 | * Jean 27 | * WASM 28 | * Security 29 | 30 | * These two would make a good pair 31 | * ESM 32 | * Observability 33 | 34 | * Beth 35 | * ESM/Observability would make sense in person (wider audience) 36 | * WASM/Security - virtual 37 | 38 | * Agreed April March 7th is a good time to target. 39 | * Jean will open the issue 40 | * Discuss/mention people in the issue in terms of who we hope to be there 41 | * node-api team is a good one to include in the WASM discussion. 42 | * Modules team for the ESM one. 43 | 44 | * Next 10 - Summit OpenJS World 2022 [#112](https://github.com/nodejs/next-10/issues/112) 45 | * Common session (all collaborators) intro to Next-10 call to get involved 46 | * Review modern HTTP plan/progress 47 | * Baseline review (start with review of what we have, then whiteboard session to brainstorm 48 | additions/removals) 49 | * 50 | * 51 | * 52 | * 53 | * Technical deep dives 54 | * ESM 55 | * Observability 56 | 57 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 58 | * Discussed, Michael/Joe will reach out to some on the list. 59 | 60 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 61 | * short discussion, working on steps to update the style guide. 62 | 63 | ## Q&A, Other 64 | 65 | ## Upcoming Meetings 66 | 67 | * **Node.js Project Calendar**: 68 | 69 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 70 | -------------------------------------------------------------------------------- /meetings/2022-03-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-03-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Joe Sepi (@joesepi) 11 | * Michael dawson (@mhdawson) 12 | * Beth Griggs 13 | * Bradley Farias 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * No announcements this week 22 | 23 | ### nodejs/next-10 24 | 25 | * Identify next mini-summit topics [#117](https://github.com/nodejs/next-10/issues/117) 26 | * Jean volunteered to create issue, lets work to get open before the end of the week. 27 | 28 | * Next 10 - Collab Summit OpenJS World 2022 [#112](https://github.com/nodejs/next-10/issues/112) 29 | * Joe, great if there was a bit more instructions in the issue, but we could start submitting now 30 | * Submitting proposal 31 | * Common session - Michael 32 | * Baseline review - Michael 33 | * Technical deep dive (afternoon) - Joe 34 | * ESM 35 | * Observability 36 | 37 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 38 | * Tierney going to talk to Rich about increment changes to docs to support 39 | 40 | * Summit next steps - single executable application support 41 | * This PR documenting what we discussed - along 42 | with a PoC 43 | 44 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 45 | * Joe had reached out to group that provides newsletter and they are interested 46 | * Michael key question 47 | * How do we put requests in a place where the PR/Comms people from the newsletters will 48 | watch/see 49 | * How do we easily let collaborators identify topics that should be fed to those groups 50 | * Bradley there are different crowds 51 | * many developers don’t have social media 52 | * youtube, tens of thousands that just use youtube for their news 53 | * blogs/news 54 | * newsletters, is a good first step to other 55 | * Joe sounds like problem is “making sure wider community is aware of changes, so they are 56 | no surprised” 57 | * Bradley 58 | * already have twitter automation 59 | * maybe we can just tag issues that should be surfaced 60 | * problem is there is lack of explanation for things like notable changes 61 | 62 | * Initial solution 63 | * News repo with template for adding potential news items 64 | * Ask Foundation Comms team to review weely, generate summary and email onto newsletter contacts 65 | * Email Alex (or some Foundation email) to be added to list 66 | * Joe will confirm that that approach makes sense to Fondation. 67 | 68 | ## Q&A, Other 69 | 70 | ## Upcoming Meetings 71 | 72 | * **Node.js Project Calendar**: 73 | 74 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 75 | -------------------------------------------------------------------------------- /meetings/2022-03-30.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-03-30 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Joe Sepi 13 | * Ruy 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Identify next mini-summit topics [#117](https://github.com/nodejs/next-10/issues/117) 24 | * nothing to discuss can close out issue. 25 | 26 | * Next 10 - Summit OpenJS World 2022 [#112](https://github.com/nodejs/next-10/issues/112) 27 | * Michael/Joe to submit by next meeting. 28 | 29 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 30 | * Joe talked to Robin, open to figuring out what works well 31 | * Wanted to find middle ground between github and marketing folks that might not use github 32 | regularly. 33 | * Some discussion about internal/versus use case 34 | * PR into technical strategy the process/offering. Michael to open PR 35 | 36 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 37 | * Nothing new to report this week. 38 | 39 | * Talked about mini-summit next week - to 40 | brainstorm who might be interested and give them FYIs 41 | 42 | ## Q&A, Other 43 | 44 | ## Upcoming Meetings 45 | 46 | * **Node.js Project Calendar**: 47 | 48 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 49 | -------------------------------------------------------------------------------- /meetings/2022-04-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-04-27 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Joe Sepi (@joesepi) 13 | * Tierney 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Next 10 - Summit OpenJS World 2022 [#112](https://github.com/nodejs/next-10/issues/112) 24 | * Sessions submitted 25 | * Mini summit on ESM and Observability can follow plan from past summits 26 | * Track level agenda (30 minutes) 27 | * Short intro on work so far 28 | * constituencies/technical priorities 29 | * Past mini-summits 30 | * Intro to longer sessions planned 31 | * Revalidation of technical priorities (15 mins) 32 | * Put slide up with existing ones 33 | * Missing priorities ? 34 | * No longer a priority? 35 | 36 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 37 | * PR landed which outlines how this will work - 38 | 39 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 40 | * Finished up reviewing with Rich. Ping TSC with proposal 41 | * Should be ready to land just want to get Rich’s approval 42 | * Tierney will submit a strategic initiative in next couple of weeks. 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Project Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2022-07-06.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-07-06 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | 13 | ## Agenda 14 | 15 | ## Announcements 16 | 17 | * No announcements 18 | 19 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 24 | * Pinged Robin to see if it’s time for the implementation to start 25 | * Jean, will open issue in nodejs/social-team to discuss tweets for 26 | * Weekly heads up of meetings 27 | * Tweet when each meeting starts 28 | 29 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 30 | * could be updated based on discussion in collaborator summit but items listed still make sense 31 | 32 | * Mini summit recap and next steps 33 | * Jean will create issue to look at green/yellow/red on technical priorities overview 34 | * We spent most of the time working on - https://github.com/nodejs/next-10/pull/136 adding 35 | next steps/info from the deep dives at the collaborator summit. 36 | 37 | ## Q&A, Other 38 | 39 | ## Upcoming Meetings 40 | 41 | * **Node.js Project Calendar**: 42 | 43 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 44 | -------------------------------------------------------------------------------- /meetings/2022-07-20.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-07-20 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Joe Sepi (@joesepi) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 23 | * Added to CPC agenda to see if now is the time to move that forward 24 | 25 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 26 | * No update this week 27 | 28 | * Next-10 - Deep dive session for Better multithreaded support[130](https://github.com/nodejs/next-10/issues/139) 29 | * Lets plan for the next collab submit which should be early Oct 30 | 31 | * Discussed technical priority status - 32 | * If we don’t have maintaining ESM doc that would be a good one to work on 33 | * Try to encourage/get work started on support for ESM in the vm module. (Michael to open issue on this) 34 | * Support for features from the latest ECMAScript spec - Plan to document current approach in ../doc/contributing (Michael to open issue for this) 35 | * Create feature request for - Replacing trace events implementation with Perfetto (Michael to create issue) 36 | * Start documentation/advocacy initiative to modules owners, Michael to open issue in Diagnostics WG around this. (Michael to create issue for this) 37 | * Jean will open an issue for survey, plan to go into details next time. 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Project Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /meetings/2022-09-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-09-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Ruy Adorno (@ruyadorno) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | * Upcoming collaborator summit - 21 | * Register: 22 | 23 | ### nodejs/next-10 24 | 25 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 26 | * Defer discussion to next time 27 | * i18n/documentation 28 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 29 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 30 | * Started some discussions, possibly have session at collaborator summit to move forward. 31 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 32 | * Update/revalidate the Technical Priorities 33 | * Session at Collab summit 34 | * White space - what are people’s key priorities? 35 | * Review against existing lists (priority/watch list) 36 | * Survey to ask broader community similar questions 37 | * Plan to do session at collaborator summit and then use output from that for broader survey. 38 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 39 | * pinged Foundation team again to see if we are ready to go. 40 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 41 | * No update this week. 42 | 43 | ## Q&A, Other 44 | 45 | ## Upcoming Meetings 46 | 47 | * **Node.js Project Calendar**: 48 | 49 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 50 | -------------------------------------------------------------------------------- /meetings/2022-09-21.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-09-21 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Ruy Adorno (@ruyadorno) 12 | * Tierney Cyren (@bnb) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Plan for collaborator session in Dublin [#159](https://github.com/nodejs/next-10/issues/159) 24 | * [Put together a tentative agenda for the first session](https://github.com/nodejs/next-10/issues/159#issuecomment-1253797074) 25 | * [Call to action to other collaborators to contribute](https://github.com/nodejs/next-10/issues/159#issuecomment-1253813579) 26 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 27 | * defer to next time 28 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 29 | * Discuss during the summit 30 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 31 | * Discuss during the summit 32 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 33 | * Jean will open PR for draft questions and we’ll use that to discuss/tweak 34 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 35 | * no update this week 36 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 37 | * no update this week 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Project Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /meetings/2022-10-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-10-12 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Claudio Wunder (@ovflowd) 13 | * Joe Sepi (@joesepi) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Plan for collaborator session in Dublin [#159](https://github.com/nodejs/next-10/issues/159) 24 | * PR to review collab submit brainstorms - 25 | * Next 10 for docs 26 | * PR to capture discussion and next steps - 27 | * one existing PR to try and get landed - 28 | * Issue for doc on how to support ES6 and CommonJS - 29 | 30 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 31 | * no update this week. 32 | 33 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 34 | * what do we want to do beyond the API docs 35 | * lots of discussion 36 | * Claudio, problem of giving example of one library, that ends up advocating for that library. 37 | Possibly link to outside resources. 38 | * Jean, would be good to have examples of how to create packages which support both ESM 39 | and CommonJS 40 | 41 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 42 | * covered in prior discussion 43 | * quite hard to support i18n, how to get community involved, requires automation 44 | * from discussion at collab summit, biggest benefit would be to have translation to chinese 45 | * If we did one, the infra should be able to support others 46 | 47 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 48 | * ran out of time, will discuss along with brainstorm review next time. 49 | 50 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 51 | * No update this week 52 | 53 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 54 | * No update this week 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Node.js Project Calendar**: 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | -------------------------------------------------------------------------------- /meetings/2022-10-26.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-10-26 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Darcy Clarke (@darcyclarke) 13 | * Jean Burellier (@sheplu) 14 | * Claudio Wunder 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Get collab summit attendee list for follow on discussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 25 | * Michael has asked for it, still working it. 26 | 27 | * Draft: Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 28 | * good discussion on the proposal 29 | * Jean, would like to piggy back on a concrete example for i18n testing 30 | 31 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 32 | * some discussion but ran out of time. Jean has added some sumarization to the issue as 33 | as starting point. 34 | 35 | * Plan for collaborator session in Dublin [#159](https://github.com/nodejs/next-10/issues/159) 36 | * some discussion but ran out of time. Jean has added some sumarization to the issue as 37 | as starting point. 38 | 39 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 40 | * No time 41 | 42 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 43 | * No time 44 | 45 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 46 | * No time 47 | 48 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 49 | * Jean has added some suggested questions, rest of team please review for next meeting 50 | as we might want to plan for getting it out before the end of the year. 51 | 52 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 53 | * No update 54 | 55 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 56 | * No update 57 | 58 | ## Q&A, Other 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Node.js Project Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | -------------------------------------------------------------------------------- /meetings/2022-11-23.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2022-11-23 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Joyee Cheung (@joyeecheung) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Get collab summit attendee list for follow on disussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 23 | * no update that yet 24 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 25 | * Jean should likely set up a separate meeting 26 | * Michael has meeting with Claudio to discuss this afternoon 27 | * Claudio put together this to help people understand where we are starting. 28 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 29 | * Last step 30 | * Plan for collaborator session in Dublin [#159](https://github.com/nodejs/next-10/issues/159) 31 | * Nothing more to discuss, closing issue. 32 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 33 | * No update this week 34 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 35 | * discussed 36 | * Concept as Jean outlined would be much more tightly coupled to Node.js APIs, examples 37 | using Node.js APIs only (or mostly) more along the lines of node-addon-examples 38 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 39 | * some coverage in the metadata proposal for docs above [#166](https://github.com/nodejs/next-10/issues/166) 40 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 41 | * Good discussion on the survey 42 | * Other priority is PR to update the technical priorities 43 | * Jean is going to reach out to Robin/Kaylie to see if they can help support/and timing 44 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 45 | * Suitable types - Mini Summit Deep Dive next steps 46 | * Some discussion in the issue 47 | [#104](https://github.com/nodejs/next-10/issues/104) 48 | * No update this week 49 | 50 | ## Q&A, Other 51 | 52 | ## Upcoming Meetings 53 | 54 | * **Node.js Project Calendar**: 55 | 56 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 57 | -------------------------------------------------------------------------------- /meetings/2023-01-04.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-01-04 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Claudio Wunder (@ovflowd) 12 | * Jean Burellier (@sheplu) 13 | * Ruy Adorno (@ruyadorno) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * OpenJS track at Open Source Summit in Vancouver 10-12 in May, planning collaborator summit May 9th, the day before the summit. 22 | 23 | ### nodejs/next-10 24 | 25 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 26 | * Presentation of the proposal by Claudio [node-doc-proposal](https://github.com/ovflowd/node-doc-proposal) 27 | * Next step was to create demo repository 28 | * Claudio walked us through the sample structure, we spent all of the time discussing 29 | 30 | We ran out of time and skipped all of the other issues 31 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 32 | * Get collab summit attendee list for follow on disussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 33 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 34 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 35 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 36 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 37 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 38 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 39 | 40 | ## Q&A, Other 41 | 42 | ## Upcoming Meetings 43 | 44 | * **Node.js Project Calendar**: 45 | 46 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 47 | -------------------------------------------------------------------------------- /meetings/2023-01-18.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-01-18 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Joe Sepi (@joesepi) 12 | * Ruy Adorno (@ruyadorno) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Get collab summit attendee list for follow on disussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 24 | * Jean added list of people at the summit 25 | 26 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 27 | * Nothing new to report this week 28 | * Some discussion around how we do backports 29 | * Need to figure out that transition prior to adopting the new docs 30 | * Next step is to get ready for presentation to TSC 31 | 32 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 33 | * @sheplu working on PR, should have by next week. 34 | 35 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 36 | * related to #165 @sheplu also working on this. 37 | 38 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 39 | * Might be a good fit for learn section on website. Will try to keep a short list of what we might do. 40 | * We can then see if we want to link to existing external articles or come up with something 41 | 42 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 43 | * Nothing to report 44 | 45 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 46 | * Jean will incorporate suggestions and then we’ll review to see if its too big 47 | 48 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 49 | * Discussed using “What’s new” issues in team/WG/repos, maybe add one for node.js core 50 | * Michael will create TSC issue to outline as an FYI, and then we could start with node-api and next-10 teams doing it and forward to the periodicals we listed. 51 | * Some discussion around Mastodon and Twitter handles for sharing project news. 52 | 53 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 54 | * Nothing to report this week. 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Node.js Project Calendar**: 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | -------------------------------------------------------------------------------- /meetings/2023-03-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-03-01 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Augustin Mauroy (@AugustinMauroy) 13 | * Joe Sepi (@joesepi) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * No announcements this week 22 | 23 | ### nodejs/next-10 24 | 25 | * Session proposals for the next Collaborator Summit 26 | * Serverless/Functions Deep dive? 27 | * Observability/Diagnostic channel (sync with Diagnostics team on this one) 28 | * Building long term collaborators 29 | 30 | * Get collab summit attendee list for follow on discussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 31 | * Think list complete, if people just review and move off the agenda 32 | 33 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 34 | * Skip until next time when we have Claudio 35 | 36 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 37 | * Jean: to push updated priorities 38 | 39 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 40 | 41 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 42 | 43 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 44 | 45 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 46 | * Joe will ask how foundation will be able to help. 47 | * Target to get survey out April 1, open for 3 weeks 48 | 49 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 50 | * Michael has action to PR in approach somewhere 51 | 52 | * Suitable types - Mini Summit Deep Dive next steps [#104](https://github.com/nodejs/next-10/issues/104) 53 | * Open [PR](https://github.com/nodejs/node/pull/41025/files) on styleguide what should we do with it ?: 54 | 55 | ## Q&A, Other 56 | 57 | ## Upcoming Meetings 58 | 59 | * **Node.js Project Calendar**: 60 | 61 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 62 | -------------------------------------------------------------------------------- /meetings/2023-03-15.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-03-15 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Next 10 years team: @nodejs/next-10 11 | * Augustin Mauroy (@AugustinMauroy) 12 | * Michael Dawson (@mhdawson) 13 | * Kiran Mahale 14 | * Jean Burellier (@sheplu) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | * Augustin, Tierney commented that initiative was different than what Jean was proposing 22 | * Jean 23 | * OpenJS collab summit in 1 ½ months in Vancouver 24 | * Another one at Open Source Summit in Spain in September 19-21 25 | 26 | ### nodejs/next-10 27 | 28 | * Session proposals for the next Collaborator Summit - what should we submit [#194](https://github.com/nodejs/next-10/issues/194) 29 | * We discussed proposals. Jean has action to submit one and Michael will submit the other. 30 | * Get collab summit attendee list for follow on discussion on priorities [#167](https://github.com/nodejs/next-10/issues/167) 31 | * Michael to review/land. 32 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 33 | * Claudio could not make it today, leave on agenda for next time 34 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 35 | * Jean: need to push / finish the list 36 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 37 | * discussed proposal, looking good 38 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 39 | * Jean: discuss with Tierney 40 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 41 | * No major update here 42 | * Some feedback that translated docs are not that valuable 43 | * Agustin mentioned that a single repo for the website (with docs and other pages) makes it harder to contribute. Its idea it’s to have one repo for docs. 44 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 45 | * Joe Sepiwas going to check with the OpenJS communication team. 46 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 47 | * Next step is for Michael to PR in some doc in the main repo. 48 | 49 | ## Q&A, Other 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Node.js Project Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /meetings/2023-03-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-03-29 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burelier (@sheplu) 12 | * Robin Ginn 13 | * Claudio Wunder (@ovflowd) 14 | * Benjamin Sternthal (@bensternthal) 15 | * Joe Sepi 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | * Claudio - reminder will be presenting about updated documentation proposal in TSC today 24 | * Michael - Reminder about collaborator summit 25 | 26 | ### nodejs/next-10 27 | 28 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 29 | * constituencies: change the word 30 | * what is your use case: change to plural if multiple one, or primary ? => Jean to review last year survey and answers 31 | * OS: Operating System 32 | * add “which package manager is used” ? cnpm, pnpm, yarn (v1,2,3) … 33 | * worked through the survey, Foundation is going to help get it done by the collab summit 34 | 35 | * Session proposals for the next Collaborator Summit - what should we submit [#194](https://github.com/nodejs/next-10/issues/194) 36 | * 2 sessions proposed, issue closed. 37 | 38 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 39 | * Claudio presenting today to TSC on updates to proposal based on previous feedback. 40 | 41 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 42 | * Jean: TO PUSH 43 | 44 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 45 | * Jean shared some visualizations last time, plan to use/share at collab summit. 46 | 47 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 48 | * hoping for some additional feedback, but Jean will start with some small commits 49 | 50 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 51 | * no update this week. 52 | 53 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 54 | * Michael created PR to document in node core repo - nodejs/node#47189 55 | 56 | ## Q&A, Other 57 | 58 | ## Upcoming Meetings 59 | 60 | * **Node.js Project Calendar**: 61 | 62 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 63 | -------------------------------------------------------------------------------- /meetings/2023-04-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-04-12 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Claudio Wunder (@wunderacle) 13 | * Augustin Mauroy (@augustinmauroy) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Jean in a month OpenJS and collaborator summit. Hope to see people there. Next-10 has some sessions near the start. 21 | 22 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/next-10 25 | 26 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 27 | * Presented to TSC since last update 28 | * Updated proposal went over well, some follow on comments on issue. 29 | * Thinking about how to respond to the comments 30 | * Discussion is around who gets the friction 31 | * Michael - 2 main things 32 | * Out of line parameters has a cost 33 | * suggestion of standard format for parameters (TypeScript) 34 | * Claudio, idea of tooling to help with view of docs, as already you can’t see 35 | everything already in the markdown docs. 36 | * Some discussion on the comments, will be thinking about. 37 | 38 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 39 | * PR opened - (feat: update technical priorities for 2023)[ ] 40 | * Mostly the same as last, year, major change is addition of Serverless, developer experience, 41 | 42 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 43 | * Jean - no update this week, going to present during upcoming collaborator summit 44 | 45 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 46 | * Jean - need to push some examples, will see if reviews happen 47 | 48 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 49 | * Crowdin used for web site 50 | * In the discussion of the API docs proposal the feeling was that translating the API docs is not a priority. 51 | * Jean would like to pursue 52 | * Jean will ping Nick from WebSite team has contributed to MDN to see if there is stats in terms of usage of different languages. 53 | * Augustin mentioned some work by Alexendr tovmach on translation here - 54 | 55 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 56 | * Draft survey ready, deadline to review is this week I think. 57 | 58 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 59 | * Next step is to promote to working groups/teams 60 | * Michael 61 | * Will open for Node core 62 | * Michael will ask uvwasi team 63 | * Michael will ask Diagnostic team 64 | * Michael Security team 65 | * Jean - will reach out to 66 | * Performance team 67 | * Will create for Next-10 team 68 | * Will reach out to SEA team 69 | 70 | ## Q&A, Other 71 | 72 | ## Upcoming Meetings 73 | 74 | * **Node.js Project Calendar**: 75 | 76 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 77 | -------------------------------------------------------------------------------- /meetings/2023-04-26.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-04-26 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Claudio Wunder (@ovflowd) 13 | * Ruy Adorno (@ruyadorno) 14 | * Joe Sepi (@joesepi) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Next-10 Survey is active, please complete already a good number of response, Link is - 21 | twitter message: 22 | direct link: 23 | 24 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 25 | 26 | ### nodejs/next-10 27 | 28 | * Went through review of outlines for sessions at the upcoming collaborator summit 29 | 30 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 31 | * No update this week 32 | 33 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 34 | * PR in progress, need some updates 35 | 36 | * Visualization technical priorities [#155](https://github.com/nodejs/next-10/issues/155) 37 | * Using upcoming collab summit 38 | 39 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 40 | * Starting a few examples, seeing how that goes 41 | 42 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 43 | * Jean to put together demo for discussion in upcoming Next-10 meeting 44 | 45 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 46 | * Open now, please respond ! - 47 | 48 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 49 | * Working through list of teams to ask/create issue 50 | 51 | ## Q&A, Other 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Node.js Project Calendar**: 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | -------------------------------------------------------------------------------- /meetings/2023-05-24.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-05-24 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Jean Burellier (@sheplu) 11 | * Ulises Gascon (@ulisesgascon) 12 | * Michael Dawson (@mhdawson) 13 | * Ruy Adorno (@ruyadorno) 14 | * Augustin Mauroy (@AugustinMauroy) 15 | * Claudio Wunder (@ovflowd) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | * No announcements this week. 24 | 25 | ### nodejs/next-10 26 | 27 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 28 | * Jean will add the data for next time 29 | * Next-10 Serverless Deep Dive [#200](https://github.com/nodejs/next-10/issues/200) 30 | * Agreed on June 22, 11-1 ET. 31 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 32 | * Jean will pull in feedback from collaborator summit and add to the issue 33 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 34 | * No update this week, mostly focussed on website work right now. 35 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 36 | * Jean working on PR. 37 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 38 | * Jean opened - to capture a wish list of areas where examples could make sense. 39 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 40 | * No update this week 41 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 42 | * Jean/Michael will do final pass through write in comments and the get landed in the repo. 43 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 44 | * Michael and Jean will continue to talk to working groups and then start reaching out to the 45 | periodicals. 46 | 47 | ## Q&A, Other 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Project Calendar**: 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | -------------------------------------------------------------------------------- /meetings/2023-06-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-06-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Ruy Adorno (@ruyadorno) 12 | * Ulises Gascon (@ulisesGascon) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | *Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 23 | * We still need to pull in boards and then discuss 24 | * Next-10 Serverless Deep Dive [#200](https://github.com/nodejs/next-10/issues/200) 25 | * Need to document the agenda 26 | * Michael - dig out agenda based on past deep dives and add 27 | * Need to make sure we invite the right people 28 | * Work on this in the next week 29 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 30 | * No update this week 31 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 32 | * No update this week 33 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 34 | * No update this week 35 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 36 | * No update this week 37 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 38 | * No update this week 39 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 40 | * Working on sanitization/getting into the repo 41 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 42 | * Michael gave update, has reached out to periodicals 43 | * Possibility of automating issues into a RSS feed if anyone is interested in working on that 44 | 45 | ## Q&A, Other 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Node.js Project Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | -------------------------------------------------------------------------------- /meetings/2023-06-21.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-06-21 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson: (@mhdawson) 11 | * Augustin Mauroy: (@AugustinMauroy) 12 | * Ulises Gascon: (@UlisesGascon) 13 | * Jean Burellier: (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * No announcements this week. 22 | 23 | ### nodejs/next-10 24 | 25 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 26 | * No progress 27 | 28 | * Next-10 Serverless Deep Dive [#200](https://github.com/nodejs/next-10/issues/200) 29 | * Scheduled for tomorrow 30 | * Ethan/Michael talking about tweet/thread 31 | * Some discussion on having enough people there 32 | * Maybe work on address book for contacts within companies 33 | 34 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 35 | * what’s the outcome 36 | * Jean will write up a starting point that we can review 37 | 38 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 39 | * Claudio did present the updated version in last TSC meeting 40 | * Should issue soon in nodejs/node for broader input 41 | 42 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 43 | * PR that should be landed 44 | 45 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 46 | * discussion in admin repo to get Jean access so he can move forward 47 | * One pr had been review 48 | 49 | * i18n initiative documentation [#153](https://github.com/nodejs/next-10/issues/153) 50 | * Some discussion, 51 | * Jean, MDN did a good job of translation. 52 | * Took off agenda for now 53 | 54 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 55 | * PR to add results - 56 | * Went through the results and had an initial discussion 57 | * Will leave on agenda for one more meeting to discuss after people have time to read through the detailed comments 58 | 59 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 60 | * Ulises doing great work on building tool to pull news into RSS feed - 61 | * Next step is to move over repo () 62 | * Issue added issue for SEA and Performance 63 | 64 | ## Q&A, Other 65 | 66 | ## Upcoming Meetings 67 | 68 | * **Node.js Project Calendar**: 69 | 70 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 71 | -------------------------------------------------------------------------------- /meetings/2023-08-02.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-08-02 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Ulises Gascon (@ulisesgascon) 12 | * Jean Burellier (@sheplu) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 23 | * Jean is starting to work on this in 24 | 25 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 26 | * Some discussion of Jean’s experience captured in 27 | * Plan full session to discuss next time 28 | 29 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 30 | * No updates this week 31 | 32 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 33 | * No update 34 | 35 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 36 | * Jean now has maintainer access, working on some ideas 37 | 38 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 39 | * Went through detailed results today 40 | * Interesting that 61% of respondents were in Europe. 41 | * Is it because people in NA are using Twitter less? 42 | * Action: ask Kylie if she has any insight as to why there would have been more visibility in Europe 43 | * In terms of organization 44 | * Might be interesting to split technology company by industry 45 | * Might also be interesting to have the size of company 46 | * Interesting that there is 15% for Ops/DevOps which is higher than Mobile and Desktop. Might be higher than we had imagined. 47 | * In terms of environment might be worth mentioning WSL next time as there where quite a few write ins. 48 | * Action: -> Would it make sense for the team to look for ESM success stories and help get them published. 49 | * Multithreading and debugging show up in write in problems, might be an area for more documentation, document curation to help point to available resources. 50 | 51 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 52 | * Main goal is to get more collaborators generating news 53 | 54 | ## Q&A, Other 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Node.js Project Calendar**: 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | -------------------------------------------------------------------------------- /meetings/2023-08-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-08-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Next 10 years team: @nodejs/next-10 11 | * Ruy Adorno (@ruyadorno) 12 | * Ulises Gascon (@UlisesGascon) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | * Jean, reminding people of collaborator summit in Spain in September. 21 | 22 | ### nodejs/next-10 23 | 24 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 25 | * working on PRs 26 | 27 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 28 | * Need education on open source and it’s impact 29 | * common obstacle is that most people in companies don’t understand and hard to convince them to spend $ in ways related to Open Source 30 | * Should ask OpenJS foundation/Linux Foundation - 31 | * Two different conversations: 32 | * Enabling ICs to contribute within companies 33 | * Funding Open Source work (OpenJS Foundation / LF might be a better place to handle that) 34 | * Having a publication to present what is done by groups, what’s going on, big new 35 | * maybe using “what’s news” 36 | * using specific tag / hashtag automatically 37 | 38 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 39 | * No update this week 40 | 41 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 42 | * Still on Jean’s list of work 43 | 44 | * Example / documentation Initiative [#154](https://github.com/nodejs/next-10/issues/154) 45 | * Access has been facilitated, rest of work will be done in the examples repo itself. @sheplu indicated we should close. 46 | 47 | * Next-10 next survey [#152](https://github.com/nodejs/next-10/issues/152) 48 | * Reviewed last meeting, good data, closing. 49 | 50 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 51 | * Nothing to discuss this week. 52 | 53 | ## Q&A, Other 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Node.js Project Calendar**: 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | -------------------------------------------------------------------------------- /meetings/2023-08-30.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-08-30 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawoson (@mhdawson) 11 | * Augustin Mauroy (@AugustinMauroy) 12 | * Jean Burellier (@sheplu) 13 | * Claudio Wunder (@ovflowd) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * No announcements this week. 20 | 21 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 26 | * PRs created, will close when they land. 27 | 28 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 29 | * Good long discussion [in last meeting](https://github.com/nodejs/next-10/pull/225/files). 30 | * Michael will do intro to people on foundation side for Jean and include Claudio on CC. 31 | 32 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 33 | * Still on backlog, as working on Website related stuff. 34 | * Have been talking to Foundation and some Foundation docs, exploring brining look/feel from new Website to the API docs. Would be an intermediate solution. 35 | * 36 | 37 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 38 | * PR ready for review. 39 | 40 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 41 | * Nothing really to discussion this week. 42 | * Planning to cover in Next-10 collaborator summit. 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Project Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2023-10-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-10-11 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Wes Todd (@wesleytodd) 12 | * Jean Burellier (@sheplu) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Next Deep Dive [#228](https://github.com/nodejs/next-10/issues/228) 23 | * Wes should we look at corporate funding/participation 24 | * Michael we have made good progress on technical priorities/work so shift to project growth, etc. makes sense to me 25 | * Wes some things we might focus on as the next deep dives: 26 | * What does the project need/want from the foundation 27 | * Put together some ideas 28 | * Public deep dive to expand 29 | * How to grow corporate support 30 | * Start with one-on-one, one company at a time 31 | * Public deep dive to share summary/anonymized data 32 | 33 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 34 | * looks like it can be closed 35 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 36 | * See discussion under next deep dive 37 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 38 | * no update this 39 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 40 | * still needs updates 41 | * PR: 42 | * should include updates from Bilbao in follow on 43 | 44 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 45 | * Some good ideas from the collaborator summit, Michael still needs to summarize and share so we can discuss next steps. 46 | * 47 | * needs volunteer to review highlights and submit to 48 | * another thread about auto rollup 49 | * Wes, maybe we need to recruit a technical writer? 50 | * Maybe write a blog post with the ask? 51 | 52 | ## Q&A, Other 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Node.js Project Calendar**: 57 | 58 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 59 | -------------------------------------------------------------------------------- /meetings/2023-10-25.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2023-10-25 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson: @mhdawson 11 | * Ulises Gascon: @ulisesgascon 12 | * Stephen Belanger: @qard 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Next Deep Dive [#228](https://github.com/nodejs/next-10/issues/228) 23 | * Stephen - Would be good to do another deep dive on Diagnostics, will create issue proposing 24 | that when ready to start organizing that. 25 | * Deep dive on web standards that would make sense/not make sense in Node.js 26 | * What makes sense to be built into Node.js versus not 27 | 28 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 29 | * Just waiting on Jean to confirm this can be closed. 30 | 31 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 32 | * Stephen, public callouts for people is great. Recent one was good 33 | * Retweeting things from Twitter account 34 | * Contributor highlights blog 35 | * Quarterly, contributor highlight 36 | * Way on website to filter down on news page to specific areas 37 | * Prefer on Node.js website or both 38 | * Stephen, would be good to reach out to Bloomberg to understand what motivates them to 39 | support work through Igalia. 40 | 41 | * Metadata Proposal for Docs [#166](https://github.com/nodejs/next-10/issues/166) 42 | * No update on this 43 | 44 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 45 | * In progress 46 | 47 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 48 | * Some interesting discussions from Wes 49 | * 50 | * 51 | * Some discussion around a weekly tweet request and how to generate a summary for that. 52 | * Ulisses is going to look into that. 53 | 54 | ## Q&A, Other 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Node.js Project Calendar**: 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | -------------------------------------------------------------------------------- /meetings/2024-01-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-01-10 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson @mhdawson 11 | * Jean Burellier @sheplu 12 | * Marco Ippolito @marco-ippolito 13 | * Amal Hussein @nomadtechie 14 | * Ulises Gascon @ulisesGascon 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Next Deep Dive [#228](https://github.com/nodejs/next-10/issues/228) 25 | * Discussion, possible topics, we had discussed doing some more org versus technical ones 26 | * Capturing list of what the Projects needs/wants from the Foundation 27 | * Building better pathways to for new contributors 28 | * How to build corporate support 29 | * Capturing the biggest challenges being faced by the project 30 | * Advocacy and promotion for the project 31 | 32 | * We agreed that next deep dive should be 33 | * Advocacy and promotion for the project 34 | * Date to be agreed through an issue 35 | 36 | * Amal talking about building an Enterprise WG 37 | * Aligning with business needs is the best way to grow investment 38 | 39 | * Non-deep dive suggestions 40 | * Gathering feedback from TSC and internal feedback from collaborators 41 | 42 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 43 | * Ran out of time skipped 44 | 45 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 46 | * Ran out of time skipped 47 | 48 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 49 | * Ran out of time skipped 50 | 51 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 52 | * Ran out of time skipped 53 | 54 | 55 | ## Q&A, Other 56 | 57 | ## Upcoming Meetings 58 | 59 | * **Node.js Project Calendar**: 60 | 61 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 62 | -------------------------------------------------------------------------------- /meetings/2024-01-24.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-01-24 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Amal Hussein (@nomadtechie) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Next Deep Dive [#228](https://github.com/nodejs/next-10/issues/228) 24 | * Jean created [#247](https://github.com/nodejs/next-10/issues/247) which is focused on advocacy and promotion 25 | * Planned for Feb 29 26 | * Maybe 11-1 ET (8am-10am PT / 5pm-7pm CET) 27 | * Need to start on awareness . 28 | * issue is in - 29 | * Mention to TSC 30 | * Michael - tagged for agenda 31 | * Marco will open discussion in Node.js repo for awareness 32 | * Reach out to Website team - added FYI to the issue 33 | * Amal 34 | * Will create tweet to find advocates 35 | * With create survey 36 | 37 | * Next-10 Collaboration Summit: Technical Priorities [#209](https://github.com/nodejs/next-10/issues/209) 38 | * No update this week,just needs to be reviewed 39 | 40 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 41 | * skip to next time as may be a follow on Deep dive 42 | 43 | * Review easy retros from Collab summit and do updates as appropriate [#165](https://github.com/nodejs/next-10/issues/165) 44 | * This can be closed 45 | 46 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 47 | * leave on agenda until next time 48 | 49 | ## Q&A, Other 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Node.js Project Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /meetings/2024-03-06.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-03-06 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson(@mhdawson) 11 | * Marco Ippolito @marco-ippolito 12 | * Jean Burellier (@sheplu) 13 | * Amal Hussein (@nomadtechie) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * Jean, collaborator meeting in just under a month in London 22 | * issue in Admin repo 23 | 24 | ### nodejs/next-10 25 | 26 | * Deep dive recap and next steps 27 | * Survey is still live, let’s close at the end of this week 28 | * PR results into the repo (Amal) 29 | * Summary 30 | * Raw results 31 | * Send recap of meeting and results to the participants (Amal) 32 | * PR in somewhere, or create issue, discussion thread with next steps (Amal) 33 | * Ambassador program 34 | * set parameters and then trust them by promoting their content 35 | * Need a champion 36 | * Need to set up rewards 37 | * find the good way to nominate people 38 | * first batch from invite only 39 | * use next meeting to doc 0.1 40 | * Jean/Marco to lead discussion at collaborator summit 41 | 42 | * Messaging around the governance of the project Scope etc. 43 | 44 | * Corporate Node.js usage stories/studies 45 | * 1/month 46 | * Help identify people 47 | * Have blog post from people 48 | * Maybe some from collaborators 49 | * Have some with companies, all on github: issue to validate the extract then PR 50 | 51 | * Challenge of corporate marketing bashing Node.js, making things more negative/controversial than they are in reality. 52 | 53 | * Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) 54 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 55 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 56 | 57 | ## Q&A, Other 58 | 59 | ## Upcoming Meetings 60 | 61 | * **Node.js Project Calendar**: 62 | 63 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 64 | -------------------------------------------------------------------------------- /meetings/2024-03-20.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-03-20 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito @marco-ippolito 12 | * Richard Torres (@rtorr05) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Marco, new website went live! 19 | 20 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) 25 | * marco will create PR with questions from last year, as starting point to discuss/agree 26 | * Hope to close after next meeting, would be ready for survey to open around Mid April 27 | * Michael, will asking Foundation marketing slack channel after issue is open if we can get support from Foundation. 28 | 29 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 30 | * Nothing to discuss this week 31 | 32 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 33 | * No update on this either. 34 | 35 | * Talked about next steps from Advocacy Deep dive 36 | * Created issue to track and added agenda label. 37 | * Messaging around the governance of the project Scope etc. 38 | * At section to Website 39 | * Monthly tweet from Node.js account pointing to section on the Website 40 | * Quarterly collaborator spotlight 41 | * Ambassador program would help a lot (prioritize that to help spread the info) 42 | 43 | ## Q&A, Other 44 | 45 | ## Upcoming Meetings 46 | 47 | * **Node.js Project Calendar**: 48 | 49 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 50 | -------------------------------------------------------------------------------- /meetings/2024-04-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-04-17 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Next 10 years team: @nodejs/next-10 11 | * Marco Ippolito: @marco-ippolito 12 | * Jean Burelier: @sheplu 13 | * Michael Dawson: @mhdawson 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) 24 | * Marco - lots of feedback 25 | * We walked through the survey, comments etc. 26 | * Discuss about issues with Application Operaters description in - , should do follow on work to resolve. 27 | 28 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 29 | * Skipped 30 | 31 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 32 | * Skipped 33 | 34 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 35 | * Skipped 36 | 37 | ## Q&A, Other 38 | 39 | ## Upcoming Meetings 40 | 41 | * **Node.js Project Calendar**: 42 | 43 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 44 | -------------------------------------------------------------------------------- /meetings/2024-05-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-05-01 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson: @mhdawson 11 | * Stephen Belanger: @qard 12 | * Marco Ippolito: @marco-ippolito 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Marco: survey is online - 19 | 20 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) 25 | * We went through the doc and updated based on discussion and comments 26 | 27 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 28 | * covered this week based on discussion on #266. 29 | 30 | * Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) 31 | * Survey launched on the day of the 22 release 32 | * Planned to be open for a month 33 | * Leave on the agenda until then 34 | 35 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 36 | * skipped for this week 37 | 38 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 39 | * No update this week 40 | 41 | * Next deep dive 42 | * Let's think about that and discuss next week. We created an issue and tagged it with 43 | the agenda label. 44 | 45 | ## Q&A, Other 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Node.js Project Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | -------------------------------------------------------------------------------- /meetings/2024-05-15.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-05-15 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Ulises Gascon (@UlisesGascon) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | * Michael - survey 21 | 22 | ### nodejs/next-10 23 | 24 | * Brainstorm next deep dive topics #268 25 | * Funding for contributors 26 | * How can the project accept and handle contributions of $ 27 | * Use of crowdfunding in the project 28 | * Would we sign up to programs like Hero Devs, how would we spend $ 29 | * How to support linking people who want to pay to get a specific features/task completed 30 | * Next steps 31 | * Michael to open issue to start planning for this deep dive. 32 | * Building a sustainable and healthy collaborator base 33 | * Some relevant aspects: 34 | * long term collaborators 35 | * future leaders 36 | * diverse 37 | * supported/funded 38 | * To start we should gather some data 39 | * A collaborator survey might be good as well 40 | * Next steps 41 | * Marco will open issue to discuss gathering some data 42 | * Should plan for collaborator survey as well 43 | 44 | * Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) 45 | * PR is open, discuss in PR 46 | 47 | * Next steps from Advocacy Deep dive #259 48 | * defer until after PR for ambassador program lands 49 | 50 | * Survey 2024 #250 51 | * Marco, have been getting a good number of response, already more than last year. 52 | * closes May 24th, one week from now. 53 | 54 | * Corporate support and contribution #177 55 | * 56 | * 57 | * Twitter thread on how to contribute to the project 58 | * Hero Devs program 59 | * Probably needs a deep dive 60 | 61 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 62 | * No update this week 63 | 64 | ## Q&A, Other 65 | 66 | ## Upcoming Meetings 67 | 68 | * **Node.js Project Calendar**: 69 | 70 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 71 | -------------------------------------------------------------------------------- /meetings/2024-05-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-05-29 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Ulises Gascon (@UlisesGascon) 12 | * Marco Ippolito (@marco-ippolito) 13 | * Darcy 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | * Marco: survey has closed, thats to everybody who responded, over 3000 reponses. 22 | 23 | ### nodejs/next-10 24 | 25 | * Planning for next deep dive - Funding [#273](https://github.com/nodejs/next-10/issues/273) 26 | * Suggested agenda 27 | Funding for contributors 28 | * How can the project accept and handle contributions of $ 29 | * Use of crowdfunding in the project 30 | * Would we sign up to programs like OpenJS sustainability program, how would we spend $ 31 | * How to support linking people who want to pay to get a specific features/task completed 32 | * We agreed on date/time 33 | * Added to Node.js calendar 34 | * Marco will open discussion item to flag to collaborators 35 | * Michael tagged two related issues that were opened recently with a link to the deep dive info 36 | 37 | * Brainstorm next deep dive topics [#268](https://github.com/nodejs/next-10/issues/268) 38 | * Marco opened two issues 39 | * one on collaborator environment, some feedback from Rafael 40 | * 41 | 42 | 43 | 44 | * Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) 45 | * closed this issue as we discussed and PR in core is open 46 | 47 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 48 | * defer until Ambassador program launches/or not to decide on next step. 49 | 50 | * Survey 2024 [#250](https://github.com/nodejs/next-10/issues/250) 51 | * survey closed, more than 3000 recipients 52 | * Michael/Marco to go through the write in questions, Michael will send invite, and add Marco, and Ulises to see if we can get together to start on that. 53 | 54 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 55 | * Covered under the discussion of the Funding deep dive 56 | 57 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 58 | * Marco, some discussion on trouble delivering news externally 59 | * Michael, kind of have the feeling a bit more coverage, 60 | * Ulises, have releases, link for most commented issues, as well as issue teams can post news 61 | to, still not too many teams publishing info 62 | * Discussion is here - 63 | * Some discussion about use of a “notable issue” tag, as even lower bar to get news out. 64 | * Maybe get some statistics of use of the feed 65 | 66 | ## Q&A, Other 67 | 68 | ## Upcoming Meetings 69 | 70 | * **Node.js Project Calendar**: 71 | 72 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 73 | -------------------------------------------------------------------------------- /meetings/2024-06-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-06-12 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Ulises Gascón (@UlisesGascon) 12 | * Marco Ippolito (@marco-ippolito) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | * No announcements this week. 21 | 22 | ### nodejs/next-10 23 | 24 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 25 | * Scheduled for tomorrow, hope to see people interested in the topic there. 26 | 27 | * Brainstorm next deep dive topics [#268](https://github.com/nodejs/next-10/issues/268) 28 | * Next topic is captured in - 29 | * Some frustration because there are some behaviors which are not CoC violations, but they 30 | make contributing more frustration. 31 | * Would be good to capture info on this and try to document. 32 | * Let's start working on the list of questions for the collaborator survey 33 | * Ulises, need to gather metrics for work, can pull the info using the same tool () 34 | * Michael, also proposal to add LFX Insights has been made so maybe some data from that - 35 | 36 | * Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) 37 | * Michael will rebase, hopefully to get to green and then land. 38 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 39 | * Pulled out this issue - 40 | 41 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 42 | * defer until after deep dive 43 | 44 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 45 | * Agreed we should close and possibly open a new issue in terms of encouraging generating of content. 46 | 47 | ## Q&A, Other 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Project Calendar**: 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | -------------------------------------------------------------------------------- /meetings/2024-06-26.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-06-26 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Marco Ippolito (@marco-ippolito) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 23 | * Publish blog post or draft content and submit candidate as issue in nodejs/coporate-usage-stories (get feedback if there would be any concerns about if submission being public) 24 | * Limited to once per year for a company brand 25 | * Preference is for companies that do not yet have a story 26 | * Light weight review to ensure consistency with the program (Next 10, Foundation staff ?, other volunteers) 27 | * Addition to page on Website listing corporate usage stories 28 | * Promotion on social media 29 | * Article removed if link breaks 30 | 31 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 32 | * Build list of people who are interested in attended 33 | * Use doodle to see when people might be available - Marco will create the doodle 34 | 35 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 36 | * Ulises has captured some data 37 | * Can start by choosing the questions we want to ask 38 | * How long have you been contributing to the project? 39 | * Which working groups or teams do you participate in? 40 | * What makes you want to continue contributing to the project? 41 | * What makes you likely to choose to contribute less likely to continue 42 | contributing to the project? 43 | * Code reviews are to strict 44 | * Code reviews are too slow 45 | * CI is flaky 46 | * My work is not valued 47 | * etc. 48 | * Are you able to contribute as much as you would like? 49 | * If you are not able to contribute as much as you would like, if not why? 50 | * May company actively interferers with Open Source contributions 51 | * My company does not support my contributions 52 | * etc. 53 | 54 | * Discuss initial cut at text for ambassador program [#266](https://github.com/nodejs/next-10/issues/266) 55 | * closed as landed 56 | 57 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 58 | * Covered in other issues above 59 | 60 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 61 | * No update this week. 62 | 63 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 64 | * No update this week 65 | 66 | ## Q&A, Other 67 | 68 | ## Upcoming Meetings 69 | 70 | * **Node.js Project Calendar**: 71 | 72 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 73 | -------------------------------------------------------------------------------- /meetings/2024-07-24.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-07-24 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Jean Burellier (@sheplu) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Survey results 23 | * We spent most of the time going through the survey results 24 | * Q5 Role 25 | * 71% application developers 26 | * 11% direct end users 27 | * Is there anything we can do to get more from the other constituencies? 28 | * Very happy with the number of responses of 2939, versus 1677, so almost 2x last year. 29 | * Q6 Use case 30 | * 50% is developing APIs 31 | * 30% is deploying front ends 32 | * 8% is building static front ends 33 | * 10% scripting and CLI tools 34 | * Missed category for desktop and mobile applications (electron, cordova), also missed IoT, should also include all of the above. Would also be good to pull out people using SEA, bundled binaries 35 | * Q7 Operating system 36 | * Mac was the highest 43% 37 | * Windows was 27%-33% 38 | * Linux 22% 39 | * Interesting that only 11% were using docker 40 | * Q8 Production env 41 | * Linux 85%, with docker being 30% of that 42 | * Would be good to be more specific on the wording, for example: 43 | * Bare metal Linux 44 | * Linux host with Containers 45 | * Should include 46 | * all of the above 47 | * serverless 48 | * Q9 - architecture 49 | * 68% x64 50 | * 23% arm, might be coming from Mac usage 51 | * Would have been good to ask if architecture was production or development? 52 | * Q10 - how do you get your Node executables 53 | * Node version manager 60% 54 | * installers 14% 55 | * Should include -> through containers for the next year 56 | * Might be interesting to ask for development and production 57 | * Q11 - which package manager 58 | * npm 52% 59 | * pnpm 22% 60 | * yarm v1 6% and yarn v3 6% 61 | 62 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 63 | * skipped ran out of time 64 | 65 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 66 | * skipped ran out of time 67 | 68 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 69 | * skipped ran out of time 70 | 71 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 72 | * skipped ran out of time 73 | 74 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 75 | * skipped ran out of time 76 | 77 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 78 | * skipped ran out of time 79 | 80 | ## Q&A, Other 81 | 82 | ## Upcoming Meetings 83 | 84 | * **Node.js Project Calendar**: 85 | 86 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 87 | -------------------------------------------------------------------------------- /meetings/2024-08-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-08-07 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Marco Ippolito (@marco-ippolito) 13 | * Ruy Adorno (@ruyadorno) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * No announcements this week. 20 | 21 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * We continued to work through the survey results 26 | * Q12 27 | * most people 56% use nvm 28 | * 22% don’t use one 29 | * 28% of people use one of the others 30 | * might be good to try to exclude production deployments 31 | * Q13 32 | * 58% one version install globally 33 | * corepack or equivalent 25% 34 | * containers 13% 35 | * For next year, reword to make it a bit clearer 36 | * Q14 37 | * All of the priorities were greater than 25% except for WebAssembly which was around 18% 38 | * Should we dive into some of those more specifically, maybe choose one or two 39 | * Or possibly add text area that asks for more info about the priorities that they have asked for 40 | * Q15 41 | * Seems like we got a good representation from through outside the project as those related 42 | to project are low 43 | * Possibly next year filter down to make survey more external stakeholder focussed. 44 | * Have a separate collaborator survey 45 | * Q16 46 | * 71% of code includes ES module syntax, we were a bit surprised, thought it would be the 47 | inverse. 48 | * Not totally convinced we asked the question in a way that got accurate results 49 | * Something to think on, and we should likely made the question clearer next year 50 | * Add an unsure as an option 51 | * Q17 52 | * Pain points 53 | * dirname and file name 54 | * TypeScript/esm interop 55 | * Jest 56 | * Michael, drive desired content for Ambassador program from common issues 57 | * Q18 58 | * We need to look for common problems again. 59 | * Q19 60 | * experimental features 61 | * corepack at 28%, Async hooks at 32% 62 | * Q20 - new stable features 63 | * 87% on fetch 64 | * Will finish up next time. 65 | 66 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 67 | * skipped as we ran out of time 68 | 69 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 70 | * Jean will submit a session for the next Collaborator summit 71 | 72 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 73 | * Marco will submit a session for the next Collaborator summit 74 | 75 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 76 | * skipped as we ran out of time 77 | 78 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 79 | * skipped as we ran out of time 80 | 81 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 82 | * skipped as we ran out of time 83 | 84 | ## Q&A, Other 85 | 86 | ## Upcoming Meetings 87 | 88 | * **Node.js Project Calendar**: 89 | 90 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 91 | -------------------------------------------------------------------------------- /meetings/2024-08-21.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-08-21 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawsson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Jean Burellier (@sheplu) 13 | 14 | ## Agenda 15 | 16 | # Announcements 17 | 18 | * Jean - issue raised in OpenJS level to create sustainability collaboration space, related to the 19 | funding discussions we’ve had 20 | * 21 | 22 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | * Proposals for upcoming Node.js collaborator summit[#293](https://github.com/nodejs/next-10/issues/293) 25 | * Jean 26 | * we also mentioned one about a healthy collaborator base 27 | * should we have a shorter one for 30 min just about the survey 28 | * Marco 29 | * there would be some work in prep for the healthy collaborator basis 30 | * would like to formalize a bit the value of the survey 31 | * Agreed we will have 3 32 | * Survey results: [#423](https://github.com/openjs-foundation/summit/issues/423) 33 | * Node.js Funding - lets explore funding sources and models 34 | * Collaborator environment - will share results of survey, and discussion [#424](https://github.com/openjs-foundation/summit/issues/424) 35 | 36 | * Review of survey results and next actions 37 | * Q19 38 | * Discussed which experimental features, some seemed high 39 | * Next year maybe have a second question which asks which ones are being used in production 40 | * Q20 41 | * next year update the list, likely just to those which were promoted in the last year 42 | * Q21 - recurring issues 43 | * esm/cjs 44 | * Typescript 45 | * docs 46 | * monitoring/diagnostics 47 | * Performance (is it really valid or just comparison since other runtimes claim being fast) 48 | 49 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 50 | * skipped as we ran out of time 51 | 52 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 53 | * skipped as we ran out of time 54 | 55 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 56 | * skipped as we ran out of time 57 | 58 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 59 | * skipped as we ran out of time 60 | 61 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 62 | * skipped as we ran out of time 63 | 64 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 65 | * skipped as we ran out of time 66 | 67 | ## Q&A, Other 68 | 69 | ## Upcoming Meetings 70 | 71 | * **Node.js Project Calendar**: 72 | 73 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 74 | -------------------------------------------------------------------------------- /meetings/2024-09-04.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-09-04 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Marco Ippolito: @marco-ippolito 11 | * Michael Dawson: @mhdawson 12 | * aagamezl 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | ### nodejs/next-10 21 | 22 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 23 | * Marco to PR in questions 24 | * Finish this week, start survey this week, end at the end of September 25 | 26 | * Proposals for upcoming Node.js collaborator summit [#293](https://github.com/nodejs/next-10/issues/293) 27 | * proposals are in, agreed to close. 28 | 29 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 30 | * agreed to remove agenda tag until there is something more specific to discuss 31 | 32 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 33 | * Next step is session at collaborator summit 34 | 35 | * Actions next steps from the survey 36 | * Put together Highlights 37 | * 81% more respondents, many thanks! 38 | * 71% application developers 39 | * most common use case reported is building APIs, followed by use as tool for front end application 40 | * Mac and Windows most common platforms for develpment 41 | * 85% of production deployments were reported at linux, with docker being 30% of that 42 | * x86 continues to be dominant architecture but arm is growing 43 | * 60% of respondents get their binaries from a version manager, of that 56% use nvm 44 | * npm is still largest package manager, followed by pnpm 45 | * 25% of respondents said they use corepack 46 | * Technical priorities seem aligned based on responses on what people thought was important 47 | * 71% of people reported that their code includes ES module syntax 48 | * Pain points in using ESM 49 | * dirname filename, typescript, jest 50 | * experimental features, seem to be well used, 51 | * New stable features weel used, fetch in particular 52 | * General pain points 53 | * ESM integration 54 | * TypeScript 55 | * Docs 56 | * Monitoring/diagnostics 57 | * This is one which we don’t have any recent initiative, there is diagnostics WG. 58 | * Talk about this one in future meeting 59 | * Performance 60 | * No longer having meetings, need champion. 61 | * Talk about this one in future meeting 62 | 63 | * Actions 64 | * follow on next-10 discussion on 65 | * Monitoring and diagnostics 66 | * Performance 67 | * Marco will build blog post from that. 68 | 69 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 70 | * Next step is to get some advocates nominated. 71 | * Work on messages that the project would like to be shared. 72 | 73 | * Corporate support and contribution [#177](https://github.com/nodejs/next-10/issues/177) 74 | * agreed to take this off the agenda until there is more to discuss 75 | 76 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 77 | * Nothing to discuss this week 78 | 79 | ## Q&A, Other 80 | 81 | ## Upcoming Meetings 82 | 83 | * **Node.js Project Calendar**: 84 | 85 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 86 | -------------------------------------------------------------------------------- /meetings/2024-09-18.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-09-18 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Mert Can Altin(@mertcanaltin) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | * survey for healthy collaborators is out. If you are a Node.js collaborator please fill it out. 20 | 21 | ### nodejs/next-10 22 | 23 | * Follow on discussion from survey - perf and diagnotics [#296](https://github.com/nodejs/next-10/issues/296) 24 | * Michael, already two working groups 25 | * Marco, maybe we should explore this at the summit 26 | 27 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 28 | * lets focus on getting ambassadors into the ambassador program and then come back to this 29 | 30 | * Next 10 - Funding Deep Dive [#273](https://github.com/nodejs/next-10/issues/273) 31 | * going to cover at the summit 32 | 33 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 34 | * survey is open, and session planned for the summit 35 | 36 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 37 | * working on getting ambassadors in. 38 | 39 | * Create Communications Channel to JS Newsletters/Periodicals [#110](https://github.com/nodejs/next-10/issues/110) 40 | * nothing new on that one today. 41 | 42 | * Blog post for first survey is planned for beginning of October. 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Project Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2024-10-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-10-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Parris Lucas (@GrooveCS) 12 | * Marco Ippolito (@marco-ippolito) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Follow on discussion from the survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 24 | * Planned to highlight and discuss at the collaborator summit 25 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 26 | * Defer until we’ve got the ambassador program ramped up 27 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 28 | * Can PR the PDF with the non-write in questions overview 29 | * Asked if there is an Excel download 30 | * If no Excel, then Marco will let us know, and we will probably have to look at writing a tool to parse 31 | * Marco will find a time for us to get together to discuss/prep 32 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 33 | * Current active initiatives, covered by earlier discussions. 34 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 35 | * Promotion of recent notable changes 36 | * look at the changelog and highlight areas of work 37 | * Current initiatives 38 | * strategic initiatives 39 | * Promoting working groups and getting involved in them 40 | * talk to WG members and do profile/why join 41 | * How the project works (non-funded, volunteer, etc.) 42 | * How to get involved in the project 43 | * Using the new Typescript feature with Node.js 44 | * Using ESM with Node.js 45 | 46 | ## Q&A, Other 47 | 48 | ## Upcoming Meetings 49 | 50 | * **Node.js Project Calendar**: 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | -------------------------------------------------------------------------------- /meetings/2024-11-13.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-11-13 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Marco Ippolito (@marco-ippolito) 12 | * Ulises Gascón (@UlisesGascon) 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 24 | * lets leave on list and talk about after some of the other initiatives 25 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 26 | * hoping there were some notes, good input from the survey 27 | * slides - 28 | * next step is to extract some points that need discussion 29 | * CI 30 | * Public recognition 31 | * Identification of work and connecting with collaborators 32 | * RFC suggestion 33 | * Concern about not too many new collaborators 34 | 35 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 36 | * defer after we complete work on the Ambassador program. 37 | 38 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 39 | * Have one ambassador to onboard, another nomination in progress 40 | Git 41 | * Top messages brainstorm 42 | * Threat model and security vulnerability reporting (Ulises) 43 | * Node.js is your best choice for a JavaScript runtime (large number of platforms supported, how widely it is used, openness of the project, the predictable and stable releases from the release process) (Michael) 44 | * Getting to know how the project works, how to get involved, working groups, teams, etc. 45 | * current initiatives including strategic initiatives 46 | * non-funded, volunteer 47 | * Working with the event loop, better understanding of asynchronous applications with Node.js (ask James if he has some input/contributions on that) 48 | * Modern Node.js, with new features and functions, best practices have changed over time, bring people who may have learned Node.js in the past up to date. (Marco) 49 | * Using the new TypeScript features 50 | * Using ESM with Node.js 51 | * Node.js test feature 52 | * Node env 53 | * Node.js best practices (Jean) 54 | * Error handling 55 | 56 | * Discussed example format, see sections below 57 | * Marco, we should get collaborators to PR in their topics 58 | 59 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 60 | 61 | ## Message for promotion (Example format based on brainstorm, with a few of the top messages as examples) 62 | 63 | ### Thread model and security vulnerability reporting 64 | 65 | #### Goal 66 | 67 | Build a better community understanding of the Node.js threat model and how to properly report security issues. We often have people opening public issues in repo versus reporting through Hacker One. 68 | 69 | #### Related Links 70 | 71 | * 72 | * 73 | 74 | #### Project contacts 75 | 76 | @nodejs/security-wg 77 | 78 | ### Node.js is your best choice for a JavaScript runtime 79 | 80 | #### Goal 81 | 82 | Highlight all of the reasons why Node.js is the best choice for a JavaScript runtime. These include: 83 | 84 | * defines the defacto standard API, so most likely to be compatible with modules 85 | * large number of platforms supported 86 | * how widely it is used 87 | * openness of the project 88 | * the predictable and stable releases from the release process 89 | * good security practices 90 | 91 | #### Related Links 92 | 93 | #### Project contacts 94 | 95 | @nodejs/security-wg 96 | 97 | ## Q&A, Other 98 | 99 | ## Upcoming Meetings 100 | 101 | * **Node.js Project Calendar**: 102 | 103 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 104 | -------------------------------------------------------------------------------- /meetings/2024-11-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2024-11-27 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Zach Tanner 12 | * Jacob Smith (@JakobJingleheimer) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 19 | 20 | * No announcements this week 21 | 22 | ### nodejs/next-10 23 | 24 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 25 | * PR to document how to PR in messages landed 26 | * Nothing discuss this week, messages to PR in discussed last week 27 | 28 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 29 | * nothing week 30 | 31 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 32 | * next on our list after we finish launching the ambassador program 33 | 34 | * Building a sustainable and healthy collaborator base [#271](https://github.com/nodejs/next-10/issues/271) 35 | * Marco’s working on some next steps based on the survey and collaborator summit 36 | 37 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 38 | * covered by the earlier issues 39 | 40 | * Zach - survey 41 | * offering to help out with analyzing the survey 42 | * survey results were in - 43 | * Would need the raw spreadsheet to do more analysis 44 | * Zach will take a look and possibly give us some suggestions, and possibly ask for the raw 45 | data. 46 | * At collaborator summit, introduced the concept of introducing RFCs, to a mixed reception 47 | * seems like we all agree the problems exist, but not aligned on how to address them 48 | * not sure if there is another way to address the issues 49 | * Michael, good start is to document the issues we would want to solve, and then go from 50 | there. 51 | 52 | ## Q&A, Other 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Node.js Project Calendar**: 57 | 58 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 59 | -------------------------------------------------------------------------------- /meetings/2025-01-08.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-01-08 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jacob Smith (@JakobJingleheimer) 12 | * Marco Ippolito @marco-ippolito 13 | * Jean Burellier (@sheplu) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 24 | * we continue to work on adding the messages. 25 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 26 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 27 | * Next on the list after getting the advocacy program going 28 | * Next steps from Advocacy Deep dive #259 29 | * Marco: would be good to onboard the workflow for the ambassador onboarding 30 | * Michael: will set up onboarding for next ambassador, invite Jacob as well 31 | * Michael: after that then through slack or or whatever we should discuss kickoff 32 | * Michael: we should also make sure re-posts are covered for bluesky 33 | 34 | * Mentoring workshop(s) in Amsterdam [#318](https://github.com/nodejs/next-10/issues/318) 35 | * Jacob, In collab summit in Ireland there was a session on diversity. Agreed that we want to 36 | do want we can to improve. 37 | * codebar is a DEI coding charity in the UK, Jacob reached out in terms of extending to 38 | Amsterdam. Also thought it would be a good opportunity for the Node.js project to support 39 | * Good discussion. 40 | 41 | * 2025 brainstorm 42 | * Jean: Survey in April for 2025 43 | * Michael: Ramp up Ambassador program 44 | * Michael: Ramp up Corporate Node.js usage stories/studies 45 | * Jean: Collaborator stories 46 | * Randomly pick 1-2 collaborators per month 47 | * Ask them to do short write up 48 | * Jean, maybe at the collaborator summit 49 | * Jakob, what if gather the information ahead of time, create a template and create pokemon 50 | card, and collect them. 51 | * Goal is visibility of people contributing 52 | * Have opt-in list, PR info answering, 53 | * Follow on up survey results on Diagnostics 54 | * How often should we do collaborator survey again ? 55 | * Main pain point was the CI and flakiness 56 | * Michael, turning on crowdfunding accounts to get funding to help is one next step 57 | * Jakob, tooling could also help make it easier to fix the problems 58 | * Michael, as mentioned tools do exist, but still possibly not easy 59 | * Jean, 60 | * Would like to make progress on that before another survey 61 | * other pain point was wasted effort and lack of co-ordination 62 | * Jakob was going to open an issue to lay out the problems, and an RFC process is a potential good. 63 | 64 | ## Q&A, Other 65 | 66 | ## Upcoming Meetings 67 | 68 | * **Node.js Project Calendar**: 69 | 70 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 71 | -------------------------------------------------------------------------------- /meetings/2025-01-22.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-01-22 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Jack Camerano (@jackcamerano) 13 | * Marco Ippolito (@marco-ippolito) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * No announcements 20 | 21 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 26 | * team is working on PR’ing in messages as discussed in earlier meetings 27 | * Marco will add discussion item to let collaborators know they can add their own examples 28 | 29 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 30 | * no progress so far 31 | 32 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 33 | * waiting on ambassador to program to look at this one 34 | 35 | * Next steps from Advocacy Deep dive [#259](https://github.com/nodejs/next-10/issues/259) 36 | * took off the agenda 37 | 38 | * Survey for 2025, 39 | * Jean is going to open PR with questions, to get things started, goal is to get get survey done 40 | before Paris collaborator summit. 41 | 42 | * Default set of questions for people who are collaborators, Jean will open issue/PR for that discussion as well. 43 | 44 | ## Q&A, Other 45 | 46 | ## Upcoming Meetings 47 | 48 | * **Node.js Project Calendar**: 49 | 50 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 51 | -------------------------------------------------------------------------------- /meetings/2025-02-05.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-02-05 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jacob Smith (@JakobJingleheimer) 12 | * Jean Burellier (@sheplu)* 13 | * Zach Tanner (@ZacTanner) 14 | * Mohammed Khadar (@mohammedkhadar) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * No announcements 21 | 22 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/next-10 25 | 26 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 27 | * No update 28 | 29 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 30 | * No update 31 | 32 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 33 | * No update 34 | * Jean: taking a look for next meeting 35 | 36 | * Zach 37 | * Looking at the data from the two surveys (2023-2024) 38 | * Was able to join the results from the two surveys to see if there is any major differences ] 39 | * Significant increase in arm usage 40 | * Interesting results based on Country of residence, lots of differences 41 | * Quite Europe based in terms of survey takers in both years 42 | * Increase in representation for North/South America in 2024 43 | * Which role was application developers for both years 44 | * Direct end-users proportion double in 2024 45 | * In terms of pain points, >⅙ asked for built in TypeScript 46 | * Version management is another recurring theme 47 | * People who want new features, but not breaking changes 48 | * Jacob working on effort around migrations which should help with that 49 | * Main pain points 50 | * 6 % of 300 responses said too slow 51 | * Lack of ESM supports (20 people), particularly CJS ↔︎ ESM 52 | * Lack of memory control, memory usage 53 | 54 | * 2025 - Survey 55 | * Jean will be PR’ing in list of questions etc. 56 | * Jean will open tracking issue as well. 57 | 58 | * DEI mentoring workshop happening [Wed, 12 Feb](https://github.com/nodejs/collaborators/discussions/213) 59 | * Good mentor interest/participation (multiple outside, ex a local edu org and an AI/data firm very excited to mentor, so not just web dev) 60 | * promising so far 61 | * Michael, is there something we can/should do as follow on in terms of follow on 62 | * Jacob, would be great to have more formal mentoring process. Great to have a buddy 63 | * Jean, in 2019 there was a mentorship program, 64 | * Michael true there have been a few attempts 65 | * Jacob, next step 66 | * Some good discussion 67 | * Goal is to identify 1 or 2 great candidates from the session and look for mentors for them 68 | afterwards. 69 | * Longer-term solution: invite/nomination system (via collaborator) for promising contributor who we want to set on a "collaborator track" 70 | * Need way to track available mentors and capacity, who is paired with who, etc 71 | 72 | * Sessions for the upcoming collaborator summit in April 73 | * Mentorship system proposal - Jacob 74 | 75 | ## Q&A, Other 76 | 77 | ## Upcoming Meetings 78 | 79 | * **Node.js Project Calendar**: 80 | 81 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 82 | -------------------------------------------------------------------------------- /meetings/2025-02-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-02-19 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Jacob Smith (@JakobJingleheimer) 13 | * Zach Tanner (@ZacTanner) 14 | * Marco Ippolito (@marco-ippolito) 15 | * Nguyen Duc Thien (@iuuukhueeee) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/next-10 24 | 25 | * Collaborator summit - Next 10 sessions [#326](https://github.com/nodejs/next-10/issues/326) 26 | * Discussion on the sessions 27 | * Jean, what are the pain points for the collaborators? 28 | * Michael, what would get out of that? 29 | * Jean, what we want to do to improve collaborator summit 30 | * Could prepare based on last 31 | * Jean will submit one on this 32 | * Jakob 33 | * session: follow-ups / updates 34 | * DEI: first event last week, having another one next week 35 | * userland-migrations: Also code mod related stuff, userland migrations 36 | * session: Mentoring programme 37 | * will start a "proposals" directory in the next-10 repo 38 | * Marco 39 | * Next-10 survey, small session to gather info/refine the survey 40 | * Would be good to discuss at the summit as we can get real time discussion to close the 41 | loop 42 | * Agreed to do survey after collaborator summit and plan for session to discuss. 43 | * Marco will submit session 44 | * Do we want to do those collaborator pokemon cards? (if so, i'll start designing them and collecting data) 45 | * cost / budget? (how does that work) 46 | 47 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 48 | * Marco has pinged collaborators. Possibly merge with survey discussion, also messages that 49 | we should be sharing. 50 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 51 | * no update 52 | 53 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 54 | * no update 55 | * Jean will open a PR with a proposal to start the discussion 56 | 57 | * Set of base question for collaborators - [329](https://github.com/nodejs/next-10/issues/329) 58 | * 2025 Survey - [330](https://github.com/nodejs/next-10/issues/330) 59 | * Zach, closing off some of the open questions 60 | * asking native spoken language 61 | * Michael, maybe how comfortable in English 62 | * Michael what about a few of the open response 63 | * biggest pain point 64 | * ESM 65 | * Zach, probably worth keeping a few of those 66 | * Marco, we should go to the summit with an outline of what the survey looks like, so we should start working on it in the next meeting 67 | 68 | ## Q&A, Other 69 | 70 | ## Upcoming Meetings 71 | 72 | * **Node.js Project Calendar**: 73 | 74 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 75 | -------------------------------------------------------------------------------- /meetings/2025-03-05.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-03-05 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jean Burellier (@sheplu) 12 | * Marco Ippolito (@marco-ippolito) 13 | 14 | ## Agenda 15 | 16 | ## Announcements 17 | 18 | * No announcements this week 19 | 20 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * 2025 Survey [#330](https://github.com/nodejs/next-10/issues/330) 25 | * Jean, submitted a base set of questions 26 | * 27 | * some tweaks based on last discussions and surveys 28 | * goal is to have questions done by March 19th (end of next meeting) 29 | * Async and keep most of next meeting to finalize, if that does not work we can schedule 30 | another dedicated session. 31 | 32 | * Set of base question for collaborators [#329](https://github.com/nodejs/next-10/issues/329) 33 | * Meant to help us promote collaborators (“initiative” folder) 34 | * We discussed next steps, Jean will add a doc under nodejs/next-10/initiatives to outline the 35 | proposed program. 36 | 37 | * Collaborator summit - Next 10 sessions [#326](https://github.com/nodejs/next-10/issues/326) 38 | * Session Proposal: Node.js Next 10 Survey (submitted) 39 | * Session Proposal: Node.js Follow-ups and quick updates (submitted) 40 | * Session Proposal: Improving collaborator experience (TBD) 41 | 42 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 43 | * will be covered in collab summit session closing. 44 | 45 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 46 | * No update 47 | 48 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 49 | * Next up after we close on ambassador program ramp up. 50 | * Marco will talk a little bit about it in the survey session at the collab summit 51 | * Michael will PR in outline in the initiatives section to describe what it might look like. 52 | 53 | ## Q&A, Other 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Node.js Project Calendar**: 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | -------------------------------------------------------------------------------- /meetings/2025-03-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-03-19 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Jacob Smith (@JakobJingleheimer) 12 | * Zach Tanner (@ZacTanner) 13 | * Nguyen Duc Thien (@iuuukhueeee) 14 | * Marco Ippolito (@marco-ippolito) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/next-10 23 | 24 | * Funding for Node.js project - status updates [#335](https://github.com/nodejs/next-10/issues/335) 25 | * Waiting on board/Foundation on what we are allowed to do 26 | 27 | * 2025 Survey [#330](https://github.com/nodejs/next-10/issues/330) 28 | * we spend a good amount of the meeting going through and generating comments on the PR 29 | 30 | * Set of base question for collaborators [#329](https://github.com/nodejs/next-10/issues/329) 31 | * took a quick look, no specific commands 32 | 33 | * Collaborator summit - Next 10 sessions [#326](https://github.com/nodejs/next-10/issues/326) 34 | * submission made, closed issue 35 | 36 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 37 | * waiting until after next collab summit to review 38 | * Need to onboard Eric 39 | 40 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 41 | * skipped for this week 42 | 43 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 44 | * nothing new this week 45 | 46 | * "Pokemon" collaborator cards 47 | * Jakob showed a sample card 48 | * Derive some of the information based on activity in the project (run thru AI to see what it can generate for "moves" etc) 49 | * Had a good discussion on ideas 50 | 51 | * Proposal: collaborator-track mentorship programme: 52 | * Jakob is going to submit a shorter session to the collaborator summit: 53 | 54 | ## Q&A, Other 55 | 56 | ## Upcoming Meetings 57 | 58 | * **Node.js Project Calendar**: 59 | 60 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 61 | -------------------------------------------------------------------------------- /meetings/2025-04-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Next 10 Years team Meeting 2025-04-16 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: 7 | 8 | ## Present 9 | 10 | * Marco Ippolito: @marco-ippolito 11 | * Michael Dawson: @mhdawson 12 | * Jacob Smith: @JakobJingleheimer 13 | * Zach Tanner: @zactanner 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Extracted from **next10-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/next-10 22 | 23 | * Funding for Node.js project - status updates [#335](https://github.com/nodejs/next-10/issues/335) 24 | * Waiting on feedback/suggestions from the OpenJS board 25 | 26 | * 2025 Survey [#330](https://github.com/nodejs/next-10/issues/330) 27 | * We spend the bulk of the meeting discussing feedback from the collaborator summit on 28 | and doing updates to the survey based on that. 29 | 30 | * Set of base question for collaborators [#329](https://github.com/nodejs/next-10/issues/329) 31 | * Skipped as we ran out of time 32 | * Ambassador program - message and topics for additional content [#302](https://github.com/nodejs/next-10/issues/302) 33 | * Skipped as we ran out of time 34 | * Follow on discussion from survey - perf and diagnostics [#296](https://github.com/nodejs/next-10/issues/296) 35 | * Skipped as we ran out of time 36 | * Corporate Node.js usage stories/studies [#279](https://github.com/nodejs/next-10/issues/279) 37 | * Skipped as we ran out of time 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Project Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /meetings/summit-aug-2021/agenda.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/meetings/summit-aug-2021/agenda.pdf -------------------------------------------------------------------------------- /meetings/summit-aug-2021/minutes.md: -------------------------------------------------------------------------------- 1 | # Next-10 Summit Aug 5 2021 2 | 3 | ## Participants 4 | 5 | * Michael Dawson (@mhdawson) 6 | * Bradley Farias (@bmeck) 7 | * Matteo Collina (@mcollina) 8 | * Jean Burellier (@sheplu) 9 | * Rick Markins (@rxmarbles) 10 | * Joe Sepi (@joesepi) 11 | * Tierney Cyren (@bnb) 12 | * Parris Lucas (@GrooveCS) 13 | * Chengzhong Wu (@legendecas) 14 | * Beth Griggs (@BethGriggs) 15 | 16 | ## Agenda 17 | 18 | Deck with the agenda is available in: 19 | 20 | 21 | ## Recording 22 | Recording is available in: 23 | 24 | ## Constituencies, needs, survey 25 | 26 | We went through quick review of work to date: 27 | 28 | * https://github.com/nodejs/next-10/blob/main/CONSTITUENCIES.md 29 | * https://github.com/nodejs/next-10/blob/main/CONSTITUENCY-NEEDS.md 30 | * https://github.com/nodejs/next-10/tree/main/surveys/2021-05-03 31 | 32 | Some discussion about the survey, would there be future ones. We discussed that 33 | something similarly might make sense to get external validation of what we come 34 | up with for technical priorities. 35 | 36 | ## Technical Priorities 37 | 38 | Full notes are in: 39 | 40 | 41 | We went through the priorities identified in the easy retro we used to get input 42 | from core collaborators: 43 | 44 | 45 | From that and additional discussion we came up with the following priorities in 46 | terms of what is import for the future success of Node.js: 47 | 48 | * Key Priorities 49 | * Modern HTTP 50 | * Suitable types for end-users 51 | * ESM 52 | * Documentation 53 | * Web Assembly 54 | * Up to date ES JavaScript Support 55 | * Observability 56 | * Permissions/policies/security model 57 | * Better multithreaded support 58 | * Single Binary 59 | 60 | We also identified a couple which we did not feel should be on that list but that 61 | we should keep an eye on to see if that change. These we put on a `watchlist` 62 | 63 | * Watch List 64 | * QUIC 65 | * Serverless 66 | 67 | ## Next 10 years for collaborators 68 | 69 | Full notes are in: 70 | 71 | 72 | We talked about key issue in terms of the next 10 years for collaborators/contributors 73 | as suggested in . The following were 74 | used to seed the discussion: 75 | * Contribution workflow 76 | * Consensus seeking model 77 | * Leadership Model 78 | 79 | From those discussions the following priorities were agreed: 80 | * Maintaining/growing the level of contribution 81 | * Ways to get funding to collaborators 82 | * Succession planning 83 | * Helping people from companies justify/make the case to have time to contribute 84 | * Targeted mentoring 85 | * Easier contribution workflow 86 | * Local build time is a major blocker 87 | * Consensus seeking model 88 | * Improve how we handle objections, find “tie-breakers” 89 | * Leadership Model 90 | * Should TSC be more active in future vision/direction? 91 | 92 | 93 | ## Next steps 94 | 95 | We reviewed the discussion and came up with these next steps: 96 | * PR to Node core with technical priorities (Michael, Joe, Tierney, Jean) 97 | * Plan for external validation (Survey, or what ?) - Michael to open issue to discuss 98 | * Deep dive session in Next-10 meeting for each priority, invite other working groups 99 | for particular sessions or go to their meetings. (Michael to Schedule) 100 | * Open issue discussing pre-builds/ways we can reduce impact of long build time (Tierney) 101 | * Plan deep dive on Maintaining/growing the level of contribution in future Next-10 meeting (Michael) 102 | * Open issue in TSC repo for 103 | * “Should TSC be more active in future vision/direction?” 104 | * "Should top level priorities be strategic intiatives?" 105 | * Agreed we should wait to do this until after we have the PR to node core with the 106 | technical priorities. 107 | -------------------------------------------------------------------------------- /surveys/2021-05-03/Node.js Next 10 Survey-Qs3,4.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2021-05-03/Node.js Next 10 Survey-Qs3,4.pdf -------------------------------------------------------------------------------- /surveys/2021-05-03/NodeNext10SurveyResults.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2021-05-03/NodeNext10SurveyResults.pdf -------------------------------------------------------------------------------- /surveys/2023-04/Node.js Next 10 Survey Results - Slides.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2023-04/Node.js Next 10 Survey Results - Slides.pdf -------------------------------------------------------------------------------- /surveys/2023-04/Node.js Survey Results 2023.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2023-04/Node.js Survey Results 2023.pdf -------------------------------------------------------------------------------- /surveys/2023-04/Node.js Survey open ended answers.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2023-04/Node.js Survey open ended answers.pdf -------------------------------------------------------------------------------- /surveys/2024-04/Next-10 survey 2024.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2024-04/Next-10 survey 2024.pdf -------------------------------------------------------------------------------- /surveys/2024-04/Node Next 10 Survey Results OVERVIEW.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2024-04/Node Next 10 Survey Results OVERVIEW.pdf -------------------------------------------------------------------------------- /surveys/2024-09/collaborator health survey results.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nodejs/next-10/2b9063aeca654d6e028951d559714c728b3be14c/surveys/2024-09/collaborator health survey results.pdf -------------------------------------------------------------------------------- /surveys/2024-09/questions.md: -------------------------------------------------------------------------------- 1 | # Healthy collaborator base survey 2 | 3 | ## A bit about you 4 | 5 | ### How long have you been contributing to the project? (single-select question) 6 | 7 | - less than 1 year 8 | - 1-2 years 9 | - 2-5 years 10 | - 5-10 years 11 | - 10+ years 12 | 13 | ## Which working groups or teams do you participate in? (multi-select question) 14 | 15 | - Security team 16 | - Diagnostics working group 17 | - Build working group 18 | - Performance team 19 | - Release working group 20 | - Website team 21 | - Next 10 working group 22 | - Loaders group 23 | - TypeScript team 24 | - uv wasi team 25 | - node api team 26 | - Other (specify) 27 | 28 | ### Is contributing to Node.js part of your job ? 29 | 30 | - Yes (if yes please specify what % or what tasks (new features, bug fixes, etc)) 31 | - No 32 | 33 | ## How did you get involved 34 | 35 | ### How did you first get involved ? (single-select question) 36 | 37 | - Attended Node.js Conference 38 | - Attended collaborator summit 39 | - Code and learn 40 | - Joined working group 41 | - Issues/PR(s) to address problems I was having 42 | - PR(s) to add new features I wanted 43 | - PR(s)/Issue(s) because I wanted to get involved in the project 44 | - PR(s) to improve code coverage 45 | - PR(s) to improve tests 46 | - PR(s) to fix flaky tests 47 | - Pulled in by other collaborators 48 | - Other (specify) 49 | 50 | ### Why did you get involved ? (multi-select question) 51 | 52 | - Hobby, wanted to contributed to a key open source project 53 | - Using Node.js personally wanted to contribute 54 | - Work for a company that uses Node.js, encouraged to contribute 55 | - Joined a team at the company I work for that contributes 56 | - Other (specify) 57 | 58 | ### What would have made it easier to get involved ? (multi-select question) 59 | 60 | - More documentation 61 | - Easier ways to contact existing collaborators 62 | - Easier ways to get guidance/direction from existing collaborators 63 | - Faster build time 64 | - Easier build process 65 | - Mentoring 66 | - Better identification of work that needs to be done across the project 67 | - Other (specify) 68 | 69 | ## What keeps you around 70 | 71 | ### What makes you want to continue contributing to the project? (multi-select question) 72 | 73 | - Working Groups 74 | - Features development 75 | - Bug fixes 76 | - Recognition in the larger community ecosystem 77 | - Other (specify) 78 | 79 | ### What makes you less likely to continue contributing to the project? (multi-select question) 80 | 81 | - Code reviews are to strict 82 | - Code reviews are too slow 83 | - Code reviews are too lax 84 | - CI is flaky 85 | - CI takes a long time 86 | - Builds take a long time 87 | - My work is not valued 88 | - Required process to get a PR landed 89 | - PRs take too long to land 90 | - Long discussions on PRs 91 | - Other (specify) 92 | 93 | ## Level of contribution 94 | 95 | ### How many hours do you dedicate to the project in an average week? (single-select question) 96 | 97 | - 0-5 hours 98 | - 5-10 hours 99 | - 10-40 hours 100 | - 40-80 hours 101 | - 80+ hours 102 | 103 | ### Are you able to contribute as much as you would like? (single-select question) 104 | 105 | - Yes 106 | - Almost 107 | - A bit 108 | - No 109 | 110 | ### If you are not able to contribute as much as you would like, if not why? (multi-select question) 111 | 112 | - May company actively interferers with Open Source contributions 113 | - My company does not support my contributions 114 | - Other (specify) 115 | 116 | > We should add more options here to cover more scenarios 117 | 118 | ## Plans going forward 119 | 120 | ### Are you planning to keep contributing this year? 121 | 122 | - Yes 123 | - No (specify) 124 | 125 | ### Are you planning to keep contributing for the next 5 years? 126 | 127 | - Yes 128 | - No (specify) 129 | 130 | ### What would you like to change to improve the current environment? 131 | --------------------------------------------------------------------------------