Giter VIP home page Giter VIP logo

next-10's Introduction

next-10

Join us on OpenJS slack (channel #nodejs-next-10)

The purpose of this repository is to work collaboratively on the strategic directions for the next 10 years of Node.js (Building on the successful first 10).

For more context see: nodejs/TSC#797

We meet every other week and an issue with the agenda for the meeting will be opened in the repo a few days in advance. You can find the dates/times for future meetings on the Node.js calendar labeled as Node.js Next 10 years.

Team members

Emeritus

next-10's People

Contributors

augustinmauroy avatar benjamingr avatar bnb avatar f3n67u avatar iansu avatar lespacedunmatin avatar marco-ippolito avatar mhdawson avatar mmarchini avatar nomadtechie avatar ovflowd avatar sheplu avatar sonicdoe avatar trivikr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

next-10's Issues

Node.js Next 10 Years team Meeting 2021-01-06

Time

UTC Wed 06-Jan-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 06-Jan-2021 07:00 (07:00 AM)
US / Mountain Wed 06-Jan-2021 08:00 (08:00 AM)
US / Central Wed 06-Jan-2021 09:00 (09:00 AM)
US / Eastern Wed 06-Jan-2021 10:00 (10:00 AM)
EU / Western Wed 06-Jan-2021 15:00 (03:00 PM)
EU / Central Wed 06-Jan-2021 16:00 (04:00 PM)
EU / Eastern Wed 06-Jan-2021 17:00 (05:00 PM)
Moscow Wed 06-Jan-2021 18:00 (06:00 PM)
Chennai Wed 06-Jan-2021 20:30 (08:30 PM)
Hangzhou Wed 06-Jan-2021 23:00 (11:00 PM)
Tokyo Thu 07-Jan-2021 00:00 (12:00 AM)
Sydney Thu 07-Jan-2021 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Should we use TCQ for meetings?

https://tcq.app/ is used on TC39 meetings to coordinate discussions, give everyone a fair chance to reply, and avoid people talking over each others. Since this WG has a lot more discussions than other WGs (where we go over issues), it might make sense to use TCQ on our meetings. Thoughts?

Node.js Next 10 Years team Meeting 2021-01-21

Time

UTC Thu 21-Jan-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 21-Jan-2021 08:00 (08:00 AM)
US / Mountain Thu 21-Jan-2021 09:00 (09:00 AM)
US / Central Thu 21-Jan-2021 10:00 (10:00 AM)
US / Eastern Thu 21-Jan-2021 11:00 (11:00 AM)
EU / Western Thu 21-Jan-2021 16:00 (04:00 PM)
EU / Central Thu 21-Jan-2021 17:00 (05:00 PM)
EU / Eastern Thu 21-Jan-2021 18:00 (06:00 PM)
Moscow Thu 21-Jan-2021 19:00 (07:00 PM)
Chennai Thu 21-Jan-2021 21:30 (09:30 PM)
Hangzhou Fri 22-Jan-2021 00:00 (12:00 AM)
Tokyo Fri 22-Jan-2021 01:00 (01:00 AM)
Sydney Fri 22-Jan-2021 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Key Technical Areas - Brainstorm to generate list #39
  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-04-08

Time

UTC Thu 08-Apr-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 08-Apr-2021 09:00 (09:00 AM)
US / Mountain Thu 08-Apr-2021 10:00 (10:00 AM)
US / Central Thu 08-Apr-2021 11:00 (11:00 AM)
US / Eastern Thu 08-Apr-2021 12:00 (12:00 PM)
EU / Western Thu 08-Apr-2021 17:00 (05:00 PM)
EU / Central Thu 08-Apr-2021 18:00 (06:00 PM)
EU / Eastern Thu 08-Apr-2021 19:00 (07:00 PM)
Moscow Thu 08-Apr-2021 19:00 (07:00 PM)
Chennai Thu 08-Apr-2021 21:30 (09:30 PM)
Hangzhou Fri 09-Apr-2021 00:00 (12:00 AM)
Tokyo Fri 09-Apr-2021 01:00 (01:00 AM)
Sydney Fri 09-Apr-2021 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-02-11

Time

UTC Thu 11-Feb-2021 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Thu 11-Feb-2021 09:00 (09:00 AM)
US / Mountain Thu 11-Feb-2021 10:00 (10:00 AM)
US / Central Thu 11-Feb-2021 11:00 (11:00 AM)
US / Eastern Thu 11-Feb-2021 12:00 (12:00 PM)
EU / Western Thu 11-Feb-2021 17:00 (05:00 PM)
EU / Central Thu 11-Feb-2021 18:00 (06:00 PM)
EU / Eastern Thu 11-Feb-2021 19:00 (07:00 PM)
Moscow Thu 11-Feb-2021 20:00 (08:00 PM)
Chennai Thu 11-Feb-2021 22:30 (10:30 PM)
Hangzhou Fri 12-Feb-2021 01:00 (01:00 AM)
Tokyo Fri 12-Feb-2021 02:00 (02:00 AM)
Sydney Fri 12-Feb-2021 04:00 (04:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Key Technical Areas - Brainstorm to generate list #39
  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-10-01

Time

UTC Thu 01-Oct-2020 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Thu 01-Oct-2020 14:00 (02:00 PM)
US / Mountain Thu 01-Oct-2020 15:00 (03:00 PM)
US / Central Thu 01-Oct-2020 16:00 (04:00 PM)
US / Eastern Thu 01-Oct-2020 17:00 (05:00 PM)
EU / Western Thu 01-Oct-2020 22:00 (10:00 PM)
EU / Central Thu 01-Oct-2020 23:00 (11:00 PM)
EU / Eastern Fri 02-Oct-2020 00:00 (12:00 AM)
Moscow Fri 02-Oct-2020 00:00 (12:00 AM)
Chennai Fri 02-Oct-2020 02:30 (02:30 AM)
Hangzhou Fri 02-Oct-2020 05:00 (05:00 AM)
Tokyo Fri 02-Oct-2020 06:00 (06:00 AM)
Sydney Fri 02-Oct-2020 07:00 (07:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • doc: add compatibility/interop technical value #35323

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-08-09

Time

UTC Mon 09-Aug-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 09-Aug-2021 08:00 (08:00 AM)
US / Mountain Mon 09-Aug-2021 09:00 (09:00 AM)
US / Central Mon 09-Aug-2021 10:00 (10:00 AM)
US / Eastern Mon 09-Aug-2021 11:00 (11:00 AM)
EU / Western Mon 09-Aug-2021 16:00 (04:00 PM)
EU / Central Mon 09-Aug-2021 17:00 (05:00 PM)
EU / Eastern Mon 09-Aug-2021 18:00 (06:00 PM)
Moscow Mon 09-Aug-2021 18:00 (06:00 PM)
Chennai Mon 09-Aug-2021 20:30 (08:30 PM)
Hangzhou Mon 09-Aug-2021 23:00 (11:00 PM)
Tokyo Tue 10-Aug-2021 00:00 (12:00 AM)
Sydney Tue 10-Aug-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-11-25

Time

UTC Wed 25-Nov-2020 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 25-Nov-2020 07:00 (07:00 AM)
US / Mountain Wed 25-Nov-2020 08:00 (08:00 AM)
US / Central Wed 25-Nov-2020 09:00 (09:00 AM)
US / Eastern Wed 25-Nov-2020 10:00 (10:00 AM)
EU / Western Wed 25-Nov-2020 15:00 (03:00 PM)
EU / Central Wed 25-Nov-2020 16:00 (04:00 PM)
EU / Eastern Wed 25-Nov-2020 17:00 (05:00 PM)
Moscow Wed 25-Nov-2020 18:00 (06:00 PM)
Chennai Wed 25-Nov-2020 20:30 (08:30 PM)
Hangzhou Wed 25-Nov-2020 23:00 (11:00 PM)
Tokyo Thu 26-Nov-2020 00:00 (12:00 AM)
Sydney Thu 26-Nov-2020 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-08-20

Time

UTC Thu 20-Aug-2020 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Thu 20-Aug-2020 14:00 (02:00 PM)
US / Mountain Thu 20-Aug-2020 15:00 (03:00 PM)
US / Central Thu 20-Aug-2020 16:00 (04:00 PM)
US / Eastern Thu 20-Aug-2020 17:00 (05:00 PM)
London Thu 20-Aug-2020 22:00 (10:00 PM)
Amsterdam Thu 20-Aug-2020 23:00 (11:00 PM)
Moscow Fri 21-Aug-2020 00:00 (12:00 AM)
Chennai Fri 21-Aug-2020 02:30 (02:30 AM)
Hangzhou Fri 21-Aug-2020 05:00 (05:00 AM)
Tokyo Fri 21-Aug-2020 06:00 (06:00 AM)
Sydney Fri 21-Aug-2020 07:00 (07:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Prioritizing Technical Values #5
  • Values/directions document for core #2

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-02-04

Time

UTC Thu 04-Feb-2021 22:00 (10:00 PM):

Timezone Date/Time
US / Pacific Thu 04-Feb-2021 14:00 (02:00 PM)
US / Mountain Thu 04-Feb-2021 15:00 (03:00 PM)
US / Central Thu 04-Feb-2021 16:00 (04:00 PM)
US / Eastern Thu 04-Feb-2021 17:00 (05:00 PM)
EU / Western Thu 04-Feb-2021 22:00 (10:00 PM)
EU / Central Thu 04-Feb-2021 23:00 (11:00 PM)
EU / Eastern Fri 05-Feb-2021 00:00 (12:00 AM)
Moscow Fri 05-Feb-2021 01:00 (01:00 AM)
Chennai Fri 05-Feb-2021 03:30 (03:30 AM)
Hangzhou Fri 05-Feb-2021 06:00 (06:00 AM)
Tokyo Fri 05-Feb-2021 07:00 (07:00 AM)
Sydney Fri 05-Feb-2021 09:00 (09:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Key Technical Areas - Brainstorm to generate list #39
  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Revisit time slots

The currently proposed meeting time slots were borrowed from TSC meetings, where we optimized for attendance of TSC members. Since in general the next-10 meetings are composed by many other folks, I suggest we revisit the time slots in an attempt to increase participation. It might also be easier to reduce to one or two time slots (instead of four), as well as consider other days instead of Wed/Thu.

Create issue templates for next-10

Is your feature request related to a problem? Please describe.

Currently there are no GitHub issue templates in the next-10 repo. If we add templates, users will be able to provide suggestions as requested in #55

Describe the solution you'd like

Add GitHub Issue templates based on the kind of issues next-10 would expect from users.

Describe alternatives you've considered

Should we use GitHub Discussions feature instead for ideas?
Both the npm/feedback and github/feedback - and more repos - have been using the Discussions feature efficiently.

Values/directions document for core

In the last meeting the first thing we agreed to work on was a value/directions document that would go into the node.js core repo.

Initial thoughts on contents included:

  • Intro
    • Mission
    • Values of the project, and priority list
      • Prefer X over y
    • Key technical areas for next 10 years

This issue is to continue work on refining what it should look like and getting it into core.

Prioritizing Technical Values

Context from discussion:

This is around technical values, other values are important but not covered here. Make sure to clarify that up front.

Values from the brainstorm:

  • Approachability (both technical and community)
  • Stability
  • User experience
  • Developer experience
  • Community
  • Security
  • Backwards compatibility(?)
  • Performance
  • Diagnostics
  • Maintainability
  • Web API compatibility
  • Ecosystem (from FunRetro)
  • Collaborator Velocity
  • Great Documentation
  • Adoption of new technologies
  • Simplicity over complexity
  • Planning for today versus all possible future options, Avoid needless complexity
  • Tight focus/minimal surface
  • LTS support for users still using older versions of Node
  • Clear expectations set around support?
  • Suitability for cloud/deployments?
  • Suitability for IoT (e.g. low memory footprint)?

The goal is to expand this list to make it complete and to come up with some sort of prioritization that would be used in cases where they all cannot be satisfied.

An example might be Security over Performance or vice versa. We were not clear on what that might look like and how to arrange but this issue is to discuss see what progress we can make on that front.

Node.js Next 10 Years team Meeting 2020-10-28

Time

UTC Wed 28-Oct-2020 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 28-Oct-2020 07:00 (07:00 AM)
US / Mountain Wed 28-Oct-2020 08:00 (08:00 AM)
US / Central Wed 28-Oct-2020 09:00 (09:00 AM)
US / Eastern Wed 28-Oct-2020 10:00 (10:00 AM)
EU / Western Wed 28-Oct-2020 14:00 (02:00 PM)
EU / Central Wed 28-Oct-2020 15:00 (03:00 PM)
EU / Eastern Wed 28-Oct-2020 16:00 (04:00 PM)
Moscow Wed 28-Oct-2020 17:00 (05:00 PM)
Chennai Wed 28-Oct-2020 19:30 (07:30 PM)
Hangzhou Wed 28-Oct-2020 22:00 (10:00 PM)
Tokyo Wed 28-Oct-2020 23:00 (11:00 PM)
Sydney Thu 29-Oct-2020 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • doc: add compatibility/interop technical value #35323

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-09-17

Time

UTC Thu 17-Sep-2020 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Thu 17-Sep-2020 08:00 (08:00 AM)
US / Mountain Thu 17-Sep-2020 09:00 (09:00 AM)
US / Central Thu 17-Sep-2020 10:00 (10:00 AM)
US / Eastern Thu 17-Sep-2020 11:00 (11:00 AM)
EU / Western Thu 17-Sep-2020 16:00 (04:00 PM)
EU / Central Thu 17-Sep-2020 17:00 (05:00 PM)
EU / Eastern Thu 17-Sep-2020 18:00 (06:00 PM)
Moscow Thu 17-Sep-2020 18:00 (06:00 PM)
Chennai Thu 17-Sep-2020 20:30 (08:30 PM)
Hangzhou Thu 17-Sep-2020 23:00 (11:00 PM)
Tokyo Fri 18-Sep-2020 00:00 (12:00 AM)
Sydney Fri 18-Sep-2020 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Next 10 years for collaborators #16
  • Prioritizing Technical Values #5
  • Values/directions document for core #2

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Gather Data for Tension in Constituencies

We need to gather data / create a process around what happens when constituencies are in conflict.

We should try to find examples of tensions (performance seems the easiest to gather data around) and see what kinds of compromises or solutions were made reactively and see if we can form some sort of historical record of patterns/processes/data that were important in making those decisions. Importantly, this is not just about implementation, but also around identifying experts in the affected systems and which systems were affected.

From that record, we could then start to create a list of important things to consider and/or even a checklist of things that have been considered.

Node.js Next 10 Years team Meeting 2021-03-25

Time

UTC Thu 25-Mar-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 25-Mar-2021 09:00 (09:00 AM)
US / Mountain Thu 25-Mar-2021 10:00 (10:00 AM)
US / Central Thu 25-Mar-2021 11:00 (11:00 AM)
US / Eastern Thu 25-Mar-2021 12:00 (12:00 PM)
EU / Western Thu 25-Mar-2021 16:00 (04:00 PM)
EU / Central Thu 25-Mar-2021 17:00 (05:00 PM)
EU / Eastern Thu 25-Mar-2021 18:00 (06:00 PM)
Moscow Thu 25-Mar-2021 19:00 (07:00 PM)
Chennai Thu 25-Mar-2021 21:30 (09:30 PM)
Hangzhou Fri 26-Mar-2021 00:00 (12:00 AM)
Tokyo Fri 26-Mar-2021 01:00 (01:00 AM)
Sydney Fri 26-Mar-2021 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Where to make a suggestion?

Hi. This is definitely not the right place to ask this, but I'm not sure where is...

I have a particular point I'd like to raise as part of this consultation. Can anyone please advise where would be a good place to submit it?

I've seen the survey and funretro board, and explored the various docs in this repository, but I can't see an obvious place for a more discursive suggestion. Or maybe the time for specific points comes later in the process?

Node.js Next 10 Years team Meeting 2021-06-21

Time

UTC Mon 21-Jun-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 21-Jun-2021 08:00 (08:00 AM)
US / Mountain Mon 21-Jun-2021 09:00 (09:00 AM)
US / Central Mon 21-Jun-2021 10:00 (10:00 AM)
US / Eastern Mon 21-Jun-2021 11:00 (11:00 AM)
EU / Western Mon 21-Jun-2021 16:00 (04:00 PM)
EU / Central Mon 21-Jun-2021 17:00 (05:00 PM)
EU / Eastern Mon 21-Jun-2021 18:00 (06:00 PM)
Moscow Mon 21-Jun-2021 18:00 (06:00 PM)
Chennai Mon 21-Jun-2021 20:30 (08:30 PM)
Hangzhou Mon 21-Jun-2021 23:00 (11:00 PM)
Tokyo Tue 22-Jun-2021 00:00 (12:00 AM)
Sydney Tue 22-Jun-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Meeting time for next week?

Last week our meeting was at 7am PST, in the calendar it's showing the same time for next week. We discussed using the TSC rotation, which would mean next week the meeting would be at 1pm PST. I just want to double check if the meeting next week will be at 7am or 1pm PST. Also, I noticed the event doesn't repeat (next week is the last one), is that intentional so we evaluate after each meeting if we should keep having those?

Node.js Next 10 Years team Meeting 2021-07-05

Time

UTC Mon 05-Jul-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 05-Jul-2021 08:00 (08:00 AM)
US / Mountain Mon 05-Jul-2021 09:00 (09:00 AM)
US / Central Mon 05-Jul-2021 10:00 (10:00 AM)
US / Eastern Mon 05-Jul-2021 11:00 (11:00 AM)
EU / Western Mon 05-Jul-2021 16:00 (04:00 PM)
EU / Central Mon 05-Jul-2021 17:00 (05:00 PM)
EU / Eastern Mon 05-Jul-2021 18:00 (06:00 PM)
Moscow Mon 05-Jul-2021 18:00 (06:00 PM)
Chennai Mon 05-Jul-2021 20:30 (08:30 PM)
Hangzhou Mon 05-Jul-2021 23:00 (11:00 PM)
Tokyo Tue 06-Jul-2021 00:00 (12:00 AM)
Sydney Tue 06-Jul-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Needs/want of constituencies

As agreed in meeting this week next focus area should be:

Discussed that next focus area should be what does each constituencies need

* This should actually include #16 as the Node.js maintainers are one of the constituencies
   listed.
* Next meeting to brainstorm on what each constituency needs
* Action -> Darcy to setup boards, for each constituency , with following headings:need, don’t
  need, want, don’t want

Created this issue so that it's on the agenda for next time.

Node.js Next 10 Years team Meeting 2021-05-31

Time

UTC Mon 31-May-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 31-May-2021 08:00 (08:00 AM)
US / Mountain Mon 31-May-2021 09:00 (09:00 AM)
US / Central Mon 31-May-2021 10:00 (10:00 AM)
US / Eastern Mon 31-May-2021 11:00 (11:00 AM)
EU / Western Mon 31-May-2021 16:00 (04:00 PM)
EU / Central Mon 31-May-2021 17:00 (05:00 PM)
EU / Eastern Mon 31-May-2021 18:00 (06:00 PM)
Moscow Mon 31-May-2021 18:00 (06:00 PM)
Chennai Mon 31-May-2021 20:30 (08:30 PM)
Hangzhou Mon 31-May-2021 23:00 (11:00 PM)
Tokyo Tue 01-Jun-2021 00:00 (12:00 AM)
Sydney Tue 01-Jun-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-05-06

Time

UTC Thu 06-May-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 06-May-2021 09:00 (09:00 AM)
US / Mountain Thu 06-May-2021 10:00 (10:00 AM)
US / Central Thu 06-May-2021 11:00 (11:00 AM)
US / Eastern Thu 06-May-2021 12:00 (12:00 PM)
EU / Western Thu 06-May-2021 17:00 (05:00 PM)
EU / Central Thu 06-May-2021 18:00 (06:00 PM)
EU / Eastern Thu 06-May-2021 19:00 (07:00 PM)
Moscow Thu 06-May-2021 19:00 (07:00 PM)
Chennai Thu 06-May-2021 21:30 (09:30 PM)
Hangzhou Fri 07-May-2021 00:00 (12:00 AM)
Tokyo Fri 07-May-2021 01:00 (01:00 AM)
Sydney Fri 07-May-2021 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Adding native fetch() to node.js

Hello,

it would be nice to add fetch() to node.js even when we don't have window object. A lot of programmers need it, and now they must use node-fetch package/library for this. I think, server should have possibility to communicate with other servers/APIs, and without package we would need a lot of code to do so, why not add fetch() to node.js ?

Node.js Next 10 Years team Meeting 2021-03-11

Time

UTC Thu 11-Mar-2021 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Thu 11-Mar-2021 09:00 (09:00 AM)
US / Mountain Thu 11-Mar-2021 10:00 (10:00 AM)
US / Central Thu 11-Mar-2021 11:00 (11:00 AM)
US / Eastern Thu 11-Mar-2021 12:00 (12:00 PM)
EU / Western Thu 11-Mar-2021 17:00 (05:00 PM)
EU / Central Thu 11-Mar-2021 18:00 (06:00 PM)
EU / Eastern Thu 11-Mar-2021 19:00 (07:00 PM)
Moscow Thu 11-Mar-2021 20:00 (08:00 PM)
Chennai Thu 11-Mar-2021 22:30 (10:30 PM)
Hangzhou Fri 12-Mar-2021 01:00 (01:00 AM)
Tokyo Fri 12-Mar-2021 02:00 (02:00 AM)
Sydney Fri 12-Mar-2021 04:00 (04:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-07-12

Time

UTC Mon 12-Jul-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 12-Jul-2021 08:00 (08:00 AM)
US / Mountain Mon 12-Jul-2021 09:00 (09:00 AM)
US / Central Mon 12-Jul-2021 10:00 (10:00 AM)
US / Eastern Mon 12-Jul-2021 11:00 (11:00 AM)
EU / Western Mon 12-Jul-2021 16:00 (04:00 PM)
EU / Central Mon 12-Jul-2021 17:00 (05:00 PM)
EU / Eastern Mon 12-Jul-2021 18:00 (06:00 PM)
Moscow Mon 12-Jul-2021 18:00 (06:00 PM)
Chennai Mon 12-Jul-2021 20:30 (08:30 PM)
Hangzhou Mon 12-Jul-2021 23:00 (11:00 PM)
Tokyo Tue 13-Jul-2021 00:00 (12:00 AM)
Sydney Tue 13-Jul-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-08-12

Time

UTC Wed 12-Aug-2020 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 12-Aug-2020 07:00 (07:00 AM)
US / Mountain Wed 12-Aug-2020 08:00 (08:00 AM)
US / Central Wed 12-Aug-2020 09:00 (09:00 AM)
US / Eastern Wed 12-Aug-2020 10:00 (10:00 AM)
London Wed 12-Aug-2020 15:00 (03:00 PM)
Amsterdam Wed 12-Aug-2020 16:00 (04:00 PM)
Moscow Wed 12-Aug-2020 17:00 (05:00 PM)
Chennai Wed 12-Aug-2020 19:30 (07:30 PM)
Hangzhou Wed 12-Aug-2020 22:00 (10:00 PM)
Tokyo Wed 12-Aug-2020 23:00 (11:00 PM)
Sydney Thu 13-Aug-2020 00:00 (12:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Prioritizing Technical Values #5
  • Values/directions document for core #2

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-02-25

Time

UTC Thu 25-Feb-2021 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Thu 25-Feb-2021 09:00 (09:00 AM)
US / Mountain Thu 25-Feb-2021 10:00 (10:00 AM)
US / Central Thu 25-Feb-2021 11:00 (11:00 AM)
US / Eastern Thu 25-Feb-2021 12:00 (12:00 PM)
EU / Western Thu 25-Feb-2021 17:00 (05:00 PM)
EU / Central Thu 25-Feb-2021 18:00 (06:00 PM)
EU / Eastern Thu 25-Feb-2021 19:00 (07:00 PM)
Moscow Thu 25-Feb-2021 20:00 (08:00 PM)
Chennai Thu 25-Feb-2021 22:30 (10:30 PM)
Hangzhou Fri 26-Feb-2021 01:00 (01:00 AM)
Tokyo Fri 26-Feb-2021 02:00 (02:00 AM)
Sydney Fri 26-Feb-2021 04:00 (04:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Draft of blog post to go along with Survey

Next 10 years of Node.js - Understanding the the needs of the Node.js constituencies

TLDR; We need your help to make sure the Next 10 years of Node.js are as successful as the first. We are launching a survey, you can take here to help us do that. To get a bit more context on why this survey is important, read on….

Node.js had a very successful first 10 years of Node.js and the project is working to make the next 10 years even better. As part of that we’ve kicked off the Next-10 effort to document what we think is important for that to happen. You can follow the ongoing work of that team in this repo: https://github.com/nodejs/next-10.

Without a handy crystal ball, it turns out that it’s a lot harder than just diving in and discussing our favorite technologies to see what the keys to success are going to be. Are things like WebAssembly, Typescript, etc. important to the people who use Node.js ? I guess we need to better understand/document who uses Node.js first…..

So far the team has spent most of its time laying the foundation on which we hope to base discussions around specific technologies.

We started by documenting our understanding of the project’s technical values as these will help us balance different aspects when necessary: https://github.com/nodejs/node/blob/master/doc/guides/technical-values.md. It’s not as simple as X overrides Y but instead highlight what key values need to be factored into decisions. For example, there was consensus that good developer experience has been a key part of the success of Node.js and that it’s important for future success that we maintain that.

Next the team documented the Node.js “Constituencies”. The people/groups who have a stake in the Node.js ecosystem. We captured these in CONSTITUENCIES.md are include:

  • Direct end users
  • Application operators
  • Application Developers
  • Back-end server authors
  • Library/package authors
  • Node.js core maintainers
  • Organizations with investments in Node.js

We also documented what we thought was important to those “constituencies” in CONSTITUENCY-NEEDS.md.

We think we’ve got a good start, but at this point it only reflects the understanding of the small number of Next-10 team members contributing. At this point we need your help to make sure we’ve got it right and/or update until we do. You can do that by:

Thanks for reading and we hope to get your feedback through the survey or see you get involved in the ongoing work of the Next-10 team. Thanks in advance for your help.

Node.js Next 10 Years team Meeting 2020-09-02

Time

UTC Wed 02-Sep-2020 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 02-Sep-2020 07:00 (07:00 AM)
US / Mountain Wed 02-Sep-2020 08:00 (08:00 AM)
US / Central Wed 02-Sep-2020 09:00 (09:00 AM)
US / Eastern Wed 02-Sep-2020 10:00 (10:00 AM)
London Wed 02-Sep-2020 15:00 (03:00 PM)
Amsterdam Wed 02-Sep-2020 16:00 (04:00 PM)
Moscow Wed 02-Sep-2020 17:00 (05:00 PM)
Chennai Wed 02-Sep-2020 19:30 (07:30 PM)
Hangzhou Wed 02-Sep-2020 22:00 (10:00 PM)
Tokyo Wed 02-Sep-2020 23:00 (11:00 PM)
Sydney Thu 03-Sep-2020 00:00 (12:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Prioritizing Technical Values #5
  • Values/directions document for core #2

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-04-22

Time

UTC Thu 22-Apr-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 22-Apr-2021 09:00 (09:00 AM)
US / Mountain Thu 22-Apr-2021 10:00 (10:00 AM)
US / Central Thu 22-Apr-2021 11:00 (11:00 AM)
US / Eastern Thu 22-Apr-2021 12:00 (12:00 PM)
EU / Western Thu 22-Apr-2021 17:00 (05:00 PM)
EU / Central Thu 22-Apr-2021 18:00 (06:00 PM)
EU / Eastern Thu 22-Apr-2021 19:00 (07:00 PM)
Moscow Thu 22-Apr-2021 19:00 (07:00 PM)
Chennai Thu 22-Apr-2021 21:30 (09:30 PM)
Hangzhou Fri 23-Apr-2021 00:00 (12:00 AM)
Tokyo Fri 23-Apr-2021 01:00 (01:00 AM)
Sydney Fri 23-Apr-2021 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-06-21

Time

UTC Mon 21-Jun-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 21-Jun-2021 08:00 (08:00 AM)
US / Mountain Mon 21-Jun-2021 09:00 (09:00 AM)
US / Central Mon 21-Jun-2021 10:00 (10:00 AM)
US / Eastern Mon 21-Jun-2021 11:00 (11:00 AM)
EU / Western Mon 21-Jun-2021 16:00 (04:00 PM)
EU / Central Mon 21-Jun-2021 17:00 (05:00 PM)
EU / Eastern Mon 21-Jun-2021 18:00 (06:00 PM)
Moscow Mon 21-Jun-2021 18:00 (06:00 PM)
Chennai Mon 21-Jun-2021 20:30 (08:30 PM)
Hangzhou Mon 21-Jun-2021 23:00 (11:00 PM)
Tokyo Tue 22-Jun-2021 00:00 (12:00 AM)
Sydney Tue 22-Jun-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Next 10 years for collaborators

So far most of the discussion has been user-focused, which is great as it helps us set user-centric goals for the project. In the future we also need to discuss what the next 10 years should look like for collaborators, discussing and re-evaluating our current contribution workflow, consensus seeking model, leadership model, etc. We might come out of the discussion agreeing that everything is fine as is, or we might come up with ideas for improvements. Either way, I think it's an important topic to discuss.

Node.js Next 10 Years team Meeting 2020-07-29

Time

UTC Wed 29-Jul-2020 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 29-Jul-2020 07:00 (07:00 AM)
US / Mountain Wed 29-Jul-2020 08:00 (08:00 AM)
US / Central Wed 29-Jul-2020 09:00 (09:00 AM)
US / Eastern Wed 29-Jul-2020 10:00 (10:00 AM)
London Wed 29-Jul-2020 15:00 (03:00 PM)
Amsterdam Wed 29-Jul-2020 16:00 (04:00 PM)
Moscow Wed 29-Jul-2020 17:00 (05:00 PM)
Chennai Wed 29-Jul-2020 19:30 (07:30 PM)
Hangzhou Wed 29-Jul-2020 22:00 (10:00 PM)
Tokyo Wed 29-Jul-2020 23:00 (11:00 PM)
Sydney Thu 30-Jul-2020 00:00 (12:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Values/directions document for core #2

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Define a Security Model

We have some old documents on Node's set of security goals and guarantees. They are several years old and were not merged into repositories on Node core.

In order to properly deal w/ constituencies that are impacting security invariants of Node, we need to define the actual security guarantees, scope, and concerns of the core runtime.

Likely this would be looking at internals and user code separately and what we wish to enable for both. E.G. If we recommend users do something, why would core not follow the same recommendation by default.

Node.js Next 10 Years team Meeting 2021-07-26

Time

UTC Mon 26-Jul-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 26-Jul-2021 08:00 (08:00 AM)
US / Mountain Mon 26-Jul-2021 09:00 (09:00 AM)
US / Central Mon 26-Jul-2021 10:00 (10:00 AM)
US / Eastern Mon 26-Jul-2021 11:00 (11:00 AM)
EU / Western Mon 26-Jul-2021 16:00 (04:00 PM)
EU / Central Mon 26-Jul-2021 17:00 (05:00 PM)
EU / Eastern Mon 26-Jul-2021 18:00 (06:00 PM)
Moscow Mon 26-Jul-2021 18:00 (06:00 PM)
Chennai Mon 26-Jul-2021 20:30 (08:30 PM)
Hangzhou Mon 26-Jul-2021 23:00 (11:00 PM)
Tokyo Tue 27-Jul-2021 00:00 (12:00 AM)
Sydney Tue 27-Jul-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2020-11-12

Time

UTC Thu 12-Nov-2020 22:00 (10:00 PM):

Timezone Date/Time
US / Pacific Thu 12-Nov-2020 14:00 (02:00 PM)
US / Mountain Thu 12-Nov-2020 15:00 (03:00 PM)
US / Central Thu 12-Nov-2020 16:00 (04:00 PM)
US / Eastern Thu 12-Nov-2020 17:00 (05:00 PM)
EU / Western Thu 12-Nov-2020 22:00 (10:00 PM)
EU / Central Thu 12-Nov-2020 23:00 (11:00 PM)
EU / Eastern Fri 13-Nov-2020 00:00 (12:00 AM)
Moscow Fri 13-Nov-2020 01:00 (01:00 AM)
Chennai Fri 13-Nov-2020 03:30 (03:30 AM)
Hangzhou Fri 13-Nov-2020 06:00 (06:00 AM)
Tokyo Fri 13-Nov-2020 07:00 (07:00 AM)
Sydney Fri 13-Nov-2020 09:00 (09:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • doc: add compatibility/interop technical value #35323

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Edit to technical values document

  • Add text about revisiting the values frequently (each year?)
  • Should we have rules/guidelines to how changes to the doc should land? For example, does it require TSC approval (similar to collaborator guide changes and semver major)?
  • Add section about how the document should be interpreted, and how ambiguity should be handled
  • Add text explaining it is a living doc
  • More line items
  • Clarify if the current doc reflects the current state of the project or what we envision that the technical values should be
  • Should we remove the priorities?

(living issue, will keep writing on it until the meeting is over)

Node.js Next 10 Years team Meeting 2020-12-10

Time

UTC Thu 10-Dec-2020 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 10-Dec-2020 08:00 (08:00 AM)
US / Mountain Thu 10-Dec-2020 09:00 (09:00 AM)
US / Central Thu 10-Dec-2020 10:00 (10:00 AM)
US / Eastern Thu 10-Dec-2020 11:00 (11:00 AM)
EU / Western Thu 10-Dec-2020 16:00 (04:00 PM)
EU / Central Thu 10-Dec-2020 17:00 (05:00 PM)
EU / Eastern Thu 10-Dec-2020 18:00 (06:00 PM)
Moscow Thu 10-Dec-2020 19:00 (07:00 PM)
Chennai Thu 10-Dec-2020 21:30 (09:30 PM)
Hangzhou Fri 11-Dec-2020 00:00 (12:00 AM)
Tokyo Fri 11-Dec-2020 01:00 (01:00 AM)
Sydney Fri 11-Dec-2020 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Needs/want of constituencies #20
  • Next 10 years for collaborators #16
  • Revisit time slots #13

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Node.js Next 10 Years team Meeting 2021-05-10

Time

UTC Mon 10-May-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 10-May-2021 08:00 (08:00 AM)
US / Mountain Mon 10-May-2021 09:00 (09:00 AM)
US / Central Mon 10-May-2021 10:00 (10:00 AM)
US / Eastern Mon 10-May-2021 11:00 (11:00 AM)
EU / Western Mon 10-May-2021 16:00 (04:00 PM)
EU / Central Mon 10-May-2021 17:00 (05:00 PM)
EU / Eastern Mon 10-May-2021 18:00 (06:00 PM)
Moscow Mon 10-May-2021 18:00 (06:00 PM)
Chennai Mon 10-May-2021 20:30 (08:30 PM)
Hangzhou Mon 10-May-2021 23:00 (11:00 PM)
Tokyo Tue 11-May-2021 00:00 (12:00 AM)
Sydney Tue 11-May-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Survey to get feedback on needs of consituencies

Survey questions from previous minutes ( https://github.com/nodejs/next-10/pull/44/files)

  • Which constituencies are part of?

    • Please check those which are important to you (with list from table)
    • What needs do you have which are not covered in the list?
    • Are you part of a constituency that is not covered?
    • Is there anything else you would want to add on this topic?
    • Are you interested in joining a group session to discuss the constituencies and needs?
    • Are you interested in participating in a one-on-one session to discuss the constituencies and needs?
  • Want to do both as public survey and then a copy for foundation members

    • use the same questions as the survey, but have second copy of the survey so that
      we know what foundation member responses look like versus the overall community

Node.js Next 10 Years team Meeting 2021-06-07

Time

UTC Mon 07-Jun-2021 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Mon 07-Jun-2021 08:00 (08:00 AM)
US / Mountain Mon 07-Jun-2021 09:00 (09:00 AM)
US / Central Mon 07-Jun-2021 10:00 (10:00 AM)
US / Eastern Mon 07-Jun-2021 11:00 (11:00 AM)
EU / Western Mon 07-Jun-2021 16:00 (04:00 PM)
EU / Central Mon 07-Jun-2021 17:00 (05:00 PM)
EU / Eastern Mon 07-Jun-2021 18:00 (06:00 PM)
Moscow Mon 07-Jun-2021 18:00 (06:00 PM)
Chennai Mon 07-Jun-2021 20:30 (08:30 PM)
Hangzhou Mon 07-Jun-2021 23:00 (11:00 PM)
Tokyo Tue 08-Jun-2021 00:00 (12:00 AM)
Sydney Tue 08-Jun-2021 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/next-10

  • Survey to get feedback on needs of consituencies #48
  • Key Technical Areas - Brainstorm to generate list #39
  • Next 10 years for collaborators #16

Invited

*Next 10 years team: @nodejs/next-10

Observers/Guests

Notes

The agenda comes from issues labelled with next-10-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Next-10 - Mini-Summit - Aug 5

I've had some positive feedback on the idea of a mini-summit. Based on proposal and comments indicating a good number of people could make this time it is now planned as follows:

Time: Aug 5 10-2 ET
Zoom link: https://zoom.us/j/91519802204

Agenda:

  • Quick review of work to date (Constituencies, needs, write in survey results) - 20 mins
  • Review the technical priorities input we got from collaborators - Key Technical Areas - Brainstorm to generate list Key Technical * Areas - Brainstorm to generate list #39 - 60 mins
  • Talk about next-10 priorities for collaborators - Next 10 years for collaborators Next 10 years for collaborators #16 60 mins
  • Work on initial cut of priorities list and next steps 60 mins

With 10 minute break between sections

Who are Node.js' constituencies

Context from discussion:

Having a clear idea of who are our constituencies (could also be called stakeholders?) can help us prioritize decisions and/or which features/changes should be included in the project. Inspired on the HTTP spec.

Constituencies brainstorm:

  • Direct end users
    • Users who run tools themselves (install Node, run tool, deal with errors)
  • Application operators
  • Application Developers
    • front-end tool consumers
    • back-end server authors
    • hobby developers
    • professional developers
    • tool authors
  • library/package authors
  • Node.js core maintainers

The list above is not prioritized or exhaustive and we should continue discussion on this topic.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.