profile
viewpoint
Michael Dawson mhdawson ottawa, ontario IBM Community lead for Node.js, Node.js collaborator and TSC member, IoT hacker at home.

ibmruntimes/v8ppc 90

Port of Google V8 javascript engine to PowerPC®

ibmruntimes/yieldable-json 71

Asynchronous JSON parser and stringify APIs that make use of generator patterns

ibmruntimes/node 70

This repository hosts the ports of Node.js for IBM platforms not yet upstreamed to the community (i.e. z/OS port). For community support for Linux On Z, Linux on P or AIX, please visit https://github.com/nodejs/help. Visit http://ibm.biz/nodejs-zos-support for z/OS support content, including how open PMRs and buy IBM Service and Support.

mhdawson/AlexaMqttBridge 62

Bridge between Amazon Alexa and Mqtt

ibmruntimes/v8z 40

Port of Google V8 JavaScript engine to z/OS. The Linux on Z port is maintained in the community: https://chromium.googlesource.com/v8/v8.git

mhdawson/arduino-esp8266 7

arduino-esp8266 based sensors

gireeshpunathil/report 4

diagnostic report lab material

ianwjhalliday/node 3

Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:

andrewlow/libuv 2

Cross-platform asychronous I/O

boingoing/leveldown 2

Pure C++ Node.js LevelDB binding serving as the back-end to LevelUP

pull request commentnodejs/node

benchmark: fix error on server close in AsyncLocalStorage benchmark

CI run: https://ci.nodejs.org/job/node-test-pull-request/30348/

puzpuzpuz

comment created time in 12 hours

issue commentnodejs/build

Give libuv collaborators permission to edit libuv job configuration in Jenkins

For other team, we did create a -admins team and then let that team managed who was part of of the admins (I think that approach is even documented somewhere). I'd be +1 for that for libuv.

richardlau

comment created time in 12 hours

Pull request review commentnodejs/node-addon-examples

add daily build test against Node.js nightly build

-# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node-# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions- name: Node.js CI -on: [push, pull_request]+on:+  push:+  pull_request:+  schedule:+    - cron: "0 0 * * *"  jobs:   test:-    runs-on: ${{ matrix.operating-system }}     +    runs-on: ${{ matrix.operating-system }}      strategy:       matrix:         node-version: [10.x, 12.x, 13.x]         operating-system: [ubuntu-latest, windows-latest, macos-latest]      steps:-    - uses: actions/checkout@v2-    - name: Use Node.js ${{ matrix.node-version }}-      uses: actions/setup-node@v1-      with:-        node-version: ${{ matrix.node-version }}-    - run: npm install -g cmake-js@5.3.2-    - run: npm install-    - name: Environment Information-      run: npx envinfo-    - name: Run Test-      run: npm test  +      - uses: actions/checkout@v2+      - name: Use Node.js ${{ matrix.node-version }}+        uses: actions/setup-node@v1+        with:+          node-version: ${{ matrix.node-version }}+      - run: npm install -g cmake-js@5.3.2+      - run: npm install+      - name: Environment Information+        run: npx envinfo+      - name: Run Test+        run: npm test +  nightly-daily-test:+    runs-on: ubuntu-latest+    container: gengjiawen/node-build

I wonder if this is something we should try to have as an image managed under the project versus a personal name?

gengjiawen

comment created time in 12 hours

push eventmhdawson/io.js

Michael Dawson

commit sha 90bcb9427cdbf66caba448d8a7718943cd322aa7

doc: clarify behavior of napi_get_typedarray_info Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> Fixes: https://github.com/nodejs/node/issues/32089

view details

push time in 13 hours

PR opened nodejs/node

Napi undef

<!-- Thank you for your pull request. Please provide a description above and review the requirements below.

Bug fixes and new features should include tests and possibly benchmarks.

Contributors guide: https://github.com/nodejs/node/blob/master/CONTRIBUTING.md -->

Checklist

<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

  • [X] make -j4 test (UNIX), or vcbuild test (Windows) passes .- [X] documentation is changed or added
  • [X] commit message follows commit guidelines

<!-- Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. -->

+340 -86

0 comment

18 changed files

pr created time in 13 hours

create barnchmhdawson/io.js

branch : napi-undef

created branch time in 13 hours

Pull request review commentnodejs/diagnostics

doc: document how to examine `--trace_gc` output

 v8.setFlagsFromString('--trace_gc'); setTimeout(() => { v8.setFlagsFromString('--notrace_gc'); }, 60e3); ``` -## Examining a trace\ No newline at end of file+## Examining a trace++Obtained traces of garbage collection looks like the following lines.++```+[19278:0x5408db0]  44 ms: Scavenge 2.3 (3.0) -> 1.9 (4.0) MB, 1.2 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure++[23521:0x10268b000]  120 ms: Mark-sweep 100.7 (122.7) -> 100.6 (122.7) MB, 0.15 / 0.0 ms  (average mu = 0.132, current mu = 0.137) deserialize GC in old space requested+```++This is how to interpret the trace data:++```+[PID: isolate] < time taken since GC started in ms> : < type/phase of GC > <heap used before GC call in MB> ( < allocated heap before GC call in MB > ) -> < heap used after GC in MB> ( < allocated heap after GC in MB>) <time spent in GC in ms> [ < reason for GC >]

This is hard to read. A graphic where we point to the sections and say what they are might work better.

If we have examples of how to use the traces to identify problems that would also be good. For example in terms of running out of memory. If you first see that that the old space size is continually increasing but it takes too long to hit the max, setting the max old space size to a smaller value can help.

Another one is that if you see that the time spent in GC is continually increasing or is a large portion of the overall that can mean you are short on memory even if you don't OOM.

HarshithaKP

comment created time in 13 hours

push eventopenjs-foundation/cross-project-council

Myles Borins

commit sha 259bf5fb7b0a936df32ea6d353af500a26c7c6ed

doc: charter standards working group (#496) * doc: charter standards working group Closes: https://github.com/openjs-foundation/standards/issues/58 Refs: https://github.com/openjs-foundation/standards/issues/58#issuecomment-597256462

view details

push time in 13 hours

PR merged openjs-foundation/cross-project-council

doc: charter standards working group governance working group

Closes: https://github.com/openjs-foundation/standards/issues/58 Refs: https://github.com/openjs-foundation/standards/issues/58#issuecomment-597256462

This charter has reached consensus within the current standards team and we agreed to submit upstream in our last meeting

+16 -1

4 comments

1 changed file

MylesBorins

pr closed time in 13 hours

issue closedopenjs-foundation/standards

Chartering the standards team

I think we should ask the CPC to charter this group to oversee / own the OpenJS foundations engagement in standards activities. This would allow us to independently make decisions without a need to proxy them through the CPC. To be clear I 100% trust the CPC to make good decisions, but those who are active in these decisions are participating in this group. It is not efficient for either committee to have to bounce ideas between the two spaces.

Rough idea for steps for us:

  • Write charter
  • Apply with CPC for official chareter

Rough idea for steps for CPC:

  • Reach consensus that chartered working groups will be a thing
  • Document process for chartering

Anything missing?

closed time in 13 hours

MylesBorins

pull request commentopenjs-foundation/cross-project-council

doc: charter standards working group

Landing as I believe this has met the requirements for number of days open and approvals

MylesBorins

comment created time in 13 hours

push eventopenjs-foundation/cross-project-council

Michael Dawson

commit sha 9d61892b221f29a392bcc6520f74f45d5c6c2114

doc: clarify process that applies to WG approvals (#498) * doc: clarify process that applies to WG approvals Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

view details

push time in 13 hours

pull request commentopenjs-foundation/cross-project-council

doc: clarify process that applies to WG approvals

Landing as I believe it's meet the criteria in terms of days open and approvals.

mhdawson

comment created time in 13 hours

pull request commentnodejs/node-addon-api

add doc auto deploy action

@gengjiawen that was the plan, we have been remiss in not removing it.

gengjiawen

comment created time in 13 hours

Pull request review commentnodejs/TSC

doc: Add minutes for 1 April 2020

+# Node.js Technical Steering Committee (TSC) Meeting 2020-04-01
+
+## Links
+
+* **Recording**:  
+* **GitHub Issue**: https://github.com/nodejs/TSC/issues/842
+
+
+## Present
+
+
+* Anna Henningsen @addaleax (TSC)
+* Сковорода Никита Андреевич @ChALkeR (TSC)
+* Franziska Hinkelmann @fhinkel (TSC)
+* Gabriel Schulhof @gabrielschulhof (TSC)
+* Gireesh Punathil @gireeshpunathil (TSC)
+* James Snell @jasnell (TSC)
+* Joyee Cheung @joyeecheung (TSC)
+* Matheus Marchini @mmarchini (TSC)
+* Matteo Collina @mcollina (TSC)
+* Michael Dawso* Ruben Bridgewater @BridgeAR (TSC)

@cjihrig fixed

mhdawson

comment created time in 13 hours

push eventmhdawson/TSC

Michael Dawson

commit sha 531c72bc1ca342254aadded31cbdddb807bfd121

squash: address comments

view details

push time in 13 hours

push eventmhdawson/resume

Michael Dawson

commit sha 5a1a6661519a765a97338a7baa4d660a303b9ff5

doc: add OpenJS AMA

view details

push time in 14 hours

pull request commentnodejs/TSC

doc: Add minutes for 1 April 2020

No link to video as something seems messed up on the YouTube side. Even though there is entry for meeting it points to a different video. Same thing seems to have happened with the N-API meeting although one I can't even find now inYouTube Studio. Have reached out to Foundation staff to figure out ho we might get help in resolving.

mhdawson

comment created time in 15 hours

PR opened nodejs/TSC

doc: Add minutes for 1 April 2020

Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com

+96 -0

0 comment

1 changed file

pr created time in 15 hours

create barnchmhdawson/TSC

branch : 1Apr

created branch time in 15 hours

push eventnodejs/create-node-meeting-artifacts

Michael Dawson

commit sha e0aa90bd981f1fe31c23e0cc19cd8adab127893e

Fixup: add Ruben back Fixup bad commit which removed Ruben by accident.

view details

push time in 15 hours

issue commentnodejs/node

[v12.x] --jitless not working on aix on v12.x

@miladfarca, @john-yan can you take a look.

MylesBorins

comment created time in 16 hours

issue openednodejs/package-maintenance

Node.js Package Maintenance Team Meeting 2020-04-07

Time

UTC Tue 07-Apr-2020 19:00 (07:00 PM):

Timezone Date/Time
US / Pacific Tue 07-Apr-2020 12:00 (12:00 PM)
US / Mountain Tue 07-Apr-2020 13:00 (01:00 PM)
US / Central Tue 07-Apr-2020 14:00 (02:00 PM)
US / Eastern Tue 07-Apr-2020 15:00 (03:00 PM)
London Tue 07-Apr-2020 20:00 (08:00 PM)
Amsterdam Tue 07-Apr-2020 21:00 (09:00 PM)
Moscow Tue 07-Apr-2020 22:00 (10:00 PM)
Chennai Wed 08-Apr-2020 00:30 (12:30 AM)
Hangzhou Wed 08-Apr-2020 03:00 (03:00 AM)
Tokyo Wed 08-Apr-2020 04:00 (04:00 AM)
Sydney Wed 08-Apr-2020 05:00 (05:00 AM)

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Package%20Maintenance%20Team+Meeting+2020-04-07&iso=20200407T19
  • or http://www.wolframalpha.com/input/?i=07PM+UTC%2C+Apr+07%2C+2020+in+local+time

Links

Agenda

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

nodejs/package-maintenance

  • [RFC] Governance Models and Methodologies for Package Maintainers #309
  • PkgJS Org for WG supported tooling #271
  • Next steps on Support levels in Package.json #192

Invited

  • Package Maintenance team: @nodejs/package-maintenance

Observers/Guests

Notes

The agenda comes from issues labelled with package-maintenance-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

  • link for participants: https://zoom.us/j/431077278
  • For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live
  • youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

created time in a day

issue openednodejs/tooling

Node.js Tooling Group Meeting 2020-04-03

Time

UTC Fri 03-Apr-2020 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Fri 03-Apr-2020 13:00 (01:00 PM)
US / Mountain Fri 03-Apr-2020 14:00 (02:00 PM)
US / Central Fri 03-Apr-2020 15:00 (03:00 PM)
US / Eastern Fri 03-Apr-2020 16:00 (04:00 PM)
London Fri 03-Apr-2020 21:00 (09:00 PM)
Amsterdam Fri 03-Apr-2020 22:00 (10:00 PM)
Moscow Fri 03-Apr-2020 23:00 (11:00 PM)
Chennai Sat 04-Apr-2020 01:30 (01:30 AM)
Hangzhou Sat 04-Apr-2020 04:00 (04:00 AM)
Tokyo Sat 04-Apr-2020 05:00 (05:00 AM)
Sydney Sat 04-Apr-2020 07:00 (07:00 AM)

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Tooling%20Group+Meeting+2020-04-03&iso=20200403T20
  • or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Apr+03%2C+2020+in+local+time

Links

Agenda

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

nodejs/tooling

  • fs hooks #63
  • chmod -R #59
  • tracking "hot module reloading" for ESM in core #51
  • Support for hooking spawn / spawnSync without patching. #48
  • A better way to detect a process is exiting #42
  • Source Map V3 Support in Node.js #40
  • argument parsing #19

Invited

  • Tooling team: @nodejs/tooling

Observers/Guests

Notes

The agenda comes from issues labelled with tooling-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

  • link for participants: https://zoom.us/j/113867470
  • For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live
  • youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

created time in a day

issue commentopenjs-foundation/cross-project-council

Self-managed maintainer directory + Groups.io mailing lists on @lists.openjsf.org

@brianwarner I wonder if we should make it that easy to get to the emails. I know they are in the raw files/mailing list but not sure if a clickable link helps/hurts. Generally the directory should be helping people managed the mailing list and possibly find the email for the mailing list.

brianwarner

comment created time in 2 days

Pull request review commentnodejs/diagnostics

doc: add mintues for 25 mar 2020

+# Node.js  Diagnostics WorkGroup Meeting 2020-03-25++## Links++* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/367+* **Minutes Google Doc**: https://docs.google.com/document/d/1DAss-D2v2zlblkc9fPaX9vNjd31yS9Z1vf5I3vI54sM/edit+* **Recording**: Unavailable++## Present++* Harshitha K P(@harshithakp)+* Matheus Marchini (@mmarchini)+* Peter Marton (@hekike)+* Chengzhong Wu (@legendecas)+* Gireesh Punathil (@gireeshpunathil)++## Agenda++* COVID-19 and WG+ * Some companies encourages to cancel recurring meeting+ * Should we reduce frequency or WG or limit to sync and postpone deep dives+ * Gireesh: I feel I can work effectively+ * Gireesh: wondering people who are not in the call what do they think, like Michael+ * Gireesh: will ask Michael+ * Action item: ping people on an issue (Gireesh)++## Announcements+ +*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.++### nodejs/diagnostics++* reportVersion semantics are not defined [#349](https://github.com/nodejs/diagnostics/issues/349)+  * Matheus going to propose schema based “versioning”+  * Report was promoted to experimental, does it change this conversation?+  * Gireesh I don’t think it changes conversation+  * Mattheus will comment on issue+* Proposal to drive Diagnostics WG initiatives through user journeys [#295](https://github.com/nodejs/diagnostics/issues/295)+  * Doing CPU profiling on next WG meeting+  * How to popularize user journeys+  * There was an idea to make it part of the official Node.js documentation as it is the main place where people look for help. Who would be the right person to make such a decision?+* There is a website repository, probably opening an issue there+* Other idea was to run it on upcoming conferences+* Is OpenJS still happening?+* We are waiting for news on that+* What would be the way to popularize it at conferences?+* Gireesh: we could propose session for the collaborator summit+* Maybe we could turn user-journeys and symptom discovery to an interactive website that guides you through+* Matheus: we discovered a gap in user-journey around debugging a native addon. When I write an addon there is no good tool to debug it mainly because currently recommended tools would require a debug build of Node. Probably llnode is the closest. I think it’s a gap in both user journeys and in tools.+* Peter: how should we handle it? Discuss next meeting?+* Mattheus: yes discussing on next meeting + opening a PR to add to empty files+* Action items: reach out to website repo [Peter], collaborator summit submissions (will write a draft and discuss with WG) [Gireesh], Opening a PR about native addon use-case and gap [Matheus]++* Diagnostics "Best Practices" Guide? [#211](https://github.com/nodejs/diagnostics/issues/211)+* As part of user journeys we also provide best practices we feel we can collapse the two and remove this from the agenda+* Worth bringing it back if user journey outcomes doesn’t make it to the docs (PR’s are not open or merged)++* \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)+* A benchmark was added by @legendecas+* Promises are slow, currently trying to tackle it+* Is Promises the last missing piece?+* Not sure, but maybe API still needs some work+* Gireesh: async local storage API I think will require refining+* Gireesh: async hooks and async local storage would go hand in hand? Like would they come out together from experimental? I would expect async local storage is based on async-hooks+* Gireesh: async-hooks looks like making a good progress to come out from experimental

Good, point. I think mostly he's been focused on the work related to Context Local Storage. @Qard sorry about that.

gireeshpunathil

comment created time in 2 days

Pull request review commentnodejs/diagnostics

doc: add mintues for 25 mar 2020

+# Node.js  Diagnostics WorkGroup Meeting 2020-03-25++## Links++* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/367+* **Minutes Google Doc**: https://docs.google.com/document/d/1DAss-D2v2zlblkc9fPaX9vNjd31yS9Z1vf5I3vI54sM/edit+* **Recording**: Unavailable++## Present++* Harshitha K P(@harshithakp)+* Matheus Marchini (@mmarchini)+* Peter Marton (@hekike)+* Chengzhong Wu (@legendecas)+* Gireesh Punathil (@gireeshpunathil)++## Agenda++* COVID-19 and WG+ * Some companies encourages to cancel recurring meeting+ * Should we reduce frequency or WG or limit to sync and postpone deep dives+ * Gireesh: I feel I can work effectively+ * Gireesh: wondering people who are not in the call what do they think, like Michael+ * Gireesh: will ask Michael+ * Action item: ping people on an issue (Gireesh)++## Announcements+ +*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.++### nodejs/diagnostics++* reportVersion semantics are not defined [#349](https://github.com/nodejs/diagnostics/issues/349)+  * Matheus going to propose schema based “versioning”+  * Report was promoted to experimental, does it change this conversation?+  * Gireesh I don’t think it changes conversation+  * Mattheus will comment on issue+* Proposal to drive Diagnostics WG initiatives through user journeys [#295](https://github.com/nodejs/diagnostics/issues/295)+  * Doing CPU profiling on next WG meeting+  * How to popularize user journeys+  * There was an idea to make it part of the official Node.js documentation as it is the main place where people look for help. Who would be the right person to make such a decision?+* There is a website repository, probably opening an issue there+* Other idea was to run it on upcoming conferences+* Is OpenJS still happening?+* We are waiting for news on that+* What would be the way to popularize it at conferences?+* Gireesh: we could propose session for the collaborator summit+* Maybe we could turn user-journeys and symptom discovery to an interactive website that guides you through+* Matheus: we discovered a gap in user-journey around debugging a native addon. When I write an addon there is no good tool to debug it mainly because currently recommended tools would require a debug build of Node. Probably llnode is the closest. I think it’s a gap in both user journeys and in tools.+* Peter: how should we handle it? Discuss next meeting?+* Mattheus: yes discussing on next meeting + opening a PR to add to empty files+* Action items: reach out to website repo [Peter], collaborator summit submissions (will write a draft and discuss with WG) [Gireesh], Opening a PR about native addon use-case and gap [Matheus]++* Diagnostics "Best Practices" Guide? [#211](https://github.com/nodejs/diagnostics/issues/211)+* As part of user journeys we also provide best practices we feel we can collapse the two and remove this from the agenda+* Worth bringing it back if user journey outcomes doesn’t make it to the docs (PR’s are not open or merged)++* \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)+* A benchmark was added by @legendecas+* Promises are slow, currently trying to tackle it+* Is Promises the last missing piece?+* Not sure, but maybe API still needs some work+* Gireesh: async local storage API I think will require refining+* Gireesh: async hooks and async local storage would go hand in hand? Like would they come out together from experimental? I would expect async local storage is based on async-hooks+* Gireesh: async-hooks looks like making a good progress to come out from experimental

I'm not sure about this. It's been lacking a champion and there were previous concerns about it exposing internals. Main issue though is not having a Champion pushing it forward.

gireeshpunathil

comment created time in 2 days

Pull request review commentnodejs/diagnostics

doc: add mintues for 25 mar 2020

+# Node.js  Diagnostics WorkGroup Meeting 2020-03-25++## Links++* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/367+* **Minutes Google Doc**: https://docs.google.com/document/d/1DAss-D2v2zlblkc9fPaX9vNjd31yS9Z1vf5I3vI54sM/edit+* **Recording**: Unavailable++## Present++* Harshitha K P(@harshithakp)+* Matheus Marchini (@mmarchini)+* Peter Marton (@hekike)+* Chengzhong Wu (@legendecas)+* Gireesh Punathil (@gireeshpunathil)++## Agenda++* COVID-19 and WG+ * Some companies encourages to cancel recurring meeting+ * Should we reduce frequency or WG or limit to sync and postpone deep dives+ * Gireesh: I feel I can work effectively+ * Gireesh: wondering people who are not in the call what do they think, like Michael+ * Gireesh: will ask Michael+ * Action item: ping people on an issue (Gireesh)++## Announcements+ +*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.++### nodejs/diagnostics++* reportVersion semantics are not defined [#349](https://github.com/nodejs/diagnostics/issues/349)+  * Matheus going to propose schema based “versioning”+  * Report was promoted to experimental, does it change this conversation?+  * Gireesh I don’t think it changes conversation+  * Mattheus will comment on issue+* Proposal to drive Diagnostics WG initiatives through user journeys [#295](https://github.com/nodejs/diagnostics/issues/295)+  * Doing CPU profiling on next WG meeting+  * How to popularize user journeys+  * There was an idea to make it part of the official Node.js documentation as it is the main place where people look for help. Who would be the right person to make such a decision?+* There is a website repository, probably opening an issue there+* Other idea was to run it on upcoming conferences+* Is OpenJS still happening?+* We are waiting for news on that+* What would be the way to popularize it at conferences?+* Gireesh: we could propose session for the collaborator summit+* Maybe we could turn user-journeys and symptom discovery to an interactive website that guides you through+* Matheus: we discovered a gap in user-journey around debugging a native addon. When I write an addon there is no good tool to debug it mainly because currently recommended tools would require a debug build of Node. Probably llnode is the closest. I think it’s a gap in both user journeys and in tools.+* Peter: how should we handle it? Discuss next meeting?+* Mattheus: yes discussing on next meeting + opening a PR to add to empty files+* Action items: reach out to website repo [Peter], collaborator summit submissions (will write a draft and discuss with WG) [Gireesh], Opening a PR about native addon use-case and gap [Matheus]++* Diagnostics "Best Practices" Guide? [#211](https://github.com/nodejs/diagnostics/issues/211)+* As part of user journeys we also provide best practices we feel we can collapse the two and remove this from the agenda+* Worth bringing it back if user journey outcomes doesn’t make it to the docs (PR’s are not open or merged)++* \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)+* A benchmark was added by @legendecas+* Promises are slow, currently trying to tackle it+* Is Promises the last missing piece?+* Not sure, but maybe API still needs some work+* Gireesh: async local storage API I think will require refining+* Gireesh: async hooks and async local storage would go hand in hand? Like would they come out together from experimental? I would expect async local storage is based on async-hooks

The purpose of creating the Async Local Storage API was to provide a higher level API that we hoped could become non-experimental sooner than Async Hooks as it exposes less internals. So tying them together I don't think makes sense.

gireeshpunathil

comment created time in 2 days

issue commentnodejs/admin

New repos for sample ci configs

Tagged for agenda as FYI, if no objections after meeting time will consider approved and move to create.

mhdawson

comment created time in 2 days

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-04-01

Going to add issue to discuss meeting time to the agenda as well.

mhdawson

comment created time in 2 days

Pull request review commentnodejs/diagnostics

doc: add mintues for 25 mar 2020

+# Node.js  Diagnostics WorkGroup Meeting 2020-03-25++## Links++* **Recording**:  +* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/367+* **Minutes Google Doc**: https://docs.google.com/document/d/1DAss-D2v2zlblkc9fPaX9vNjd31yS9Z1vf5I3vI54sM/edit+* **Recording**: Unavailable

There are two Recording sections. @gireeshpunathil we should also make sure to get you setup so you can help stream/record. Have we gotten you access to the community Zoom and made you a YouTube manager?

gireeshpunathil

comment created time in 2 days

pull request commentnodejs/node-addon-api

add doc auto deploy action

Can you add a bit more details as to what this is doing? At some point I think we were going to delete the generated doc, so not sure if this is related to that or not?

gengjiawen

comment created time in 2 days

issue commentnodejs/TSC

Review meeting date times ?

My opinion is that taking people down from 50% to 40% is not worth the benefit of having greater possibility of interaction in meetings. If it was 90% to 80% that might be different but those at 50% are already challenged in terms of the meeting times and going down even further I don't think would be the right choice.

mhdawson

comment created time in 2 days

issue commentnodejs/TSC

Review meeting date times ?

@ChALkeR ping?

mhdawson

comment created time in 3 days

push eventmhdawson/bootstrap

Michael Dawson

commit sha bd4658bb0d9172d7ff19c3b92d89f8e074926ee3

Update README.md Co-Authored-By: Dave Methvin <dave.methvin@gmail.com>

view details

push time in 3 days

push eventmhdawson/bootstrap

Michael Dawson

commit sha 92e1ec8a6d48134dd9011877156da5a63c6e0e84

Update README.md Co-Authored-By: Dave Methvin <dave.methvin@gmail.com>

view details

push time in 3 days

pull request commentexpressjs/express

docs: added CODE_OF_CONDUCT.md

@brianwarner thanks !

wesleytodd

comment created time in 3 days

issue closednodejs/abi-stable-node

Evaluate if feature should be in node-add-api or not

https://github.com/nodejs/node-addon-api/issues/639

closed time in 3 days

mhdawson

issue commentnodejs/abi-stable-node

Evaluate if feature should be in node-add-api or not

Child issue closed so closing.

mhdawson

comment created time in 3 days

issue commentnodejs/abi-stable-node

Transfer the N-API tutorials into the OpenJS Foundation

Jim landed PR to get examples into node-addon-examples last week.

As next step he's going to document proposal for getting the labs into one of the repos/website etc.

jschlight

comment created time in 3 days

push eventnodejs/abi-stable-node

Nicola Del Gobbo

commit sha 3492df0545910200a313de8938dff20c59cd16fa

Added badge for N-API v6. (#394)

view details

push time in 3 days

PR merged nodejs/abi-stable-node

Added badge for N-API v6.

In this PR I added the badge for new version of N-API v6.

+2 -0

1 comment

2 changed files

NickNaso

pr closed time in 3 days

Pull request review commentnodejs/node-addon-api

src: add support for addon instance data

 namespace Napi {   ///   /// In the V8 JavaScript engine, a N-API environment approximately corresponds to an Isolate.   class Env {+#ifdef NAPI_EXPERIMENTAL

Same comment as before here as well with respect to NAPI_VERSION > 5 and the next one as well.

gabrielschulhof

comment created time in 3 days

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-04-01

Not a large agenda, but since we skipped last week and there are a couple of issues I'm thinking we keep the meeting even if it ends up being shorter.

mhdawson

comment created time in 3 days

issue commentnodejs/TSC

Node.js future directions - any interest in online or in person summit?

think yes. Role in Package management, should we have more influence on Package.json? - will this cover the ongoing need / choice of default package manager discussion as well?

I'd say yes.

mhdawson

comment created time in 3 days

issue commentnodejs/TSC

Node.js future directions - any interest in online or in person summit?

@mmarchini merged your suggestions into https://docs.google.com/document/d/1O4qk5iPN9_8ICJbk4svjnUnDoMcZtoUn8pMSkOHcVDk

mhdawson

comment created time in 3 days

pull request commentexpressjs/express

docs: added CODE_OF_CONDUCT.md

I pinged @brianwarner on slack today to see if we can get an email this this week.

wesleytodd

comment created time in 3 days

issue openedopenjs-foundation/cross-project-council

OpenJS Foundation Cross Project Council Meeting 2020-03-31

Time

UTC Tue 31-Mar-2020 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Tue 31-Mar-2020 11:00 (11:00 AM)
US / Mountain Tue 31-Mar-2020 12:00 (12:00 PM)
US / Central Tue 31-Mar-2020 13:00 (01:00 PM)
US / Eastern Tue 31-Mar-2020 14:00 (02:00 PM)
London Tue 31-Mar-2020 19:00 (07:00 PM)
Amsterdam Tue 31-Mar-2020 20:00 (08:00 PM)
Moscow Tue 31-Mar-2020 21:00 (09:00 PM)
Chennai Tue 31-Mar-2020 23:30 (11:30 PM)
Hangzhou Wed 01-Apr-2020 02:00 (02:00 AM)
Tokyo Wed 01-Apr-2020 03:00 (03:00 AM)
Sydney Wed 01-Apr-2020 05:00 (05:00 AM)

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Cross%20Project%20Council+Meeting+2020-03-31&iso=20200331T18
  • or http://www.wolframalpha.com/input/?i=06PM+UTC%2C+Mar+31%2C+2020+in+local+time

Links

Agenda

Extracted from cross-project-council-agenda labelled issues and pull requests from the openjs-foundation org prior to the meeting.

openjs-foundation/summit

  • Travel Fund Questions for Project Community Members #249

openjs-foundation/cross-project-council

  • Voting members chosen by Regular members #504
  • Self-managed maintainer directory + Groups.io mailing lists on @lists.openjsf.org #501
  • [Action Requested] Nominations Sought for 2020-2021 Voting CPC Membership #488
  • webhint: project charter review #482
  • OpenJS Collaboration Network ? #474
  • Populate the Code Of Conduct Panel #469
  • Add Foundation-wide copyright guidance #414
  • Add post-graduation checklist #386
  • Responsible security disclosures #326

openjs-foundation/standards

  • Chartering the standards team #58

Invited

  • OpenJS Foundation Cross Project Council
  • OpenJS Foundation Project Maintainers
  • OpenJS Foundation Board of Directors

Observers/Guests

Notes

The agenda comes from issues labelled with cross-project-council-agenda across all of the repositories in the openjs-foundation org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

link for participants: Zoom link: https://zoom.us/j/920010234

  • For those who just want to watch: https://livestream.openjsf.org

Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • :+1: - Attending
  • :-1: - Not attending
  • :confused: - Not sure yet

created time in 3 days

issue openednodejs/community-committee

Node.js Community Committee Meeting 2020-04-02

Time

UTC Thu 02-Apr-2020 16:00 (04:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee+Meeting+2020-04-02&iso=20200402T16
  • or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Apr+02%2C+2020+in+local+time

Links

Agenda

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

nodejs/admin

  • Create nodejs/examples repository #474
  • Additional org owned by Node.js project for package maintenance team #470

nodejs/community-committee

  • Do we need a newsletter? #590
  • OpenJS Foundation Cross-Project Council - Node.js CommComm Seat Election #586

nodejs/nodejs-collection

  • Update readme with new process #37

nodejs/nodejs.dev

  • Subscribe-to-newsletter Action. #331

Invited

  • CommComm Members: @nodejs/community-committee

Observers/Guests

Feel free to follow along on the YouTube live stream, or attend meeting as a guest by calling in to Zoom, using the links below. If you will be attending as a guest, please comment on this issue to let us know you'll be joining.

Notes

The agenda comes from issues labelled with cc-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

  • Link for participants: https://zoom.us/j/523381536
  • For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • :+1: - Attending
  • :-1: - Not attending
  • :confused: - Not sure yet

created time in 3 days

issue openednodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-04-01

Time

UTC Wed 01-Apr-2020 15:00 (03:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2020-04-01&iso=20200401T15
  • or http://www.wolframalpha.com/input/?i=03PM+UTC%2C+Apr+01%2C+2020+in+local+time

Links

Agenda

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

nodejs/node

  • Nominate @Flarna as a collaborator #32333
  • Update npm on all supported release lines to address CVE scored 9.8 in minimist package #32296

nodejs/Release

  • Release cadence due to COVID-19 Pandemic #553

nodejs/TSC

  • Node.js future directions - any interest in online or in person summit? #797

nodejs/admin

  • New repos for sample ci configs #477

Invited

  • Anna Henningsen @addaleax (TSC)
  • Anatoli Papirovski @apapirovski (TSC)
  • Beth Griggs @BethGriggs (TSC)
  • Сковорода Никита Андреевич @ChALkeR (TSC)
  • Colin Ihrig @cjihrig (TSC)
  • Daniel Bevenius @danbev (TSC)
  • Franziska Hinkelmann @fhinkel (TSC)
  • Gabriel Schulhof @gabrielschulhof (TSC)
  • Gireesh Punathil @gireeshpunathil (TSC)
  • James Snell @jasnell (TSC)
  • Joyee Cheung @joyeecheung (TSC)
  • Matheus Marchini @mmarchini (TSC)
  • Matteo Collina @mcollina (TSC)
  • Michael Dawson @mhdawson (TSC)
  • Myles Borins @MylesBorins (TSC)
  • Sam Roberts @sam-github (TSC)
  • Michaël Zasso @targos (TSC)
  • Tobias Nießen @tniessen (TSC)
  • Rich Trott @Trott (TSC)
  • Shelley Vohr @codebytere (TSC)

Observers/Guests

Notes

The agenda comes from issues labelled with tsc-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

Zoom link: https://zoom.us/j/611357642 Regular password

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.

Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.


Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • :+1: - Attending
  • :-1: - Not attending
  • :confused: - Not sure yet

created time in 3 days

issue openednodejsafrica/admin

Node.js Africa Team leadership Meeting 2020-04-03

Time

UTC Fri 03-Apr-2020 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Fri 03-Apr-2020 10:00 (10:00 AM)
US / Mountain Fri 03-Apr-2020 11:00 (11:00 AM)
US / Central Fri 03-Apr-2020 12:00 (12:00 PM)
US / Eastern Fri 03-Apr-2020 13:00 (01:00 PM)
London Fri 03-Apr-2020 18:00 (06:00 PM)
Amsterdam Fri 03-Apr-2020 19:00 (07:00 PM)
Moscow Fri 03-Apr-2020 20:00 (08:00 PM)
Chennai Fri 03-Apr-2020 22:30 (10:30 PM)
Hangzhou Sat 04-Apr-2020 01:00 (01:00 AM)
Tokyo Sat 04-Apr-2020 02:00 (02:00 AM)
Sydney Sat 04-Apr-2020 04:00 (04:00 AM)

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+leadership+Meeting+2020-04-03&iso=20200403T17
  • or http://www.wolframalpha.com/input/?i=05PM+UTC%2C+Apr+03%2C+2020+in+local+time

Links

Agenda

Extracted from leadershp-agenda labelled issues and pull requests from the nodejsafrica org prior to the meeting.

Invited

  • Node.js Africa Members: @nodejsafrica/members
  • Node.js Africa Members: @nodejsafrica/leadership

Observers/Guests

Notes

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

Joining the meeting

  • Link for participants: https://zoom.us/j/526318636
  • We stream our conference call straight to YouTube so anyone can listen to it live. It should start playing at https://www.youtube.com/c/nodejs+africa/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
  • For those who just want to watch: https://www.youtube.com/nodejs-africa

created time in 3 days

issue commentnodejs/TSC

Node.js future directions - any interest in online or in person summit?

See this related comment on how we might schedule across time-zones: https://github.com/nodejs/TSC/issues/836#issuecomment-605273977

mhdawson

comment created time in 6 days

issue commentnodejs/TSC

Node.js future directions - any interest in online or in person summit?

@nodejs/tsc pulled this together based on the suggestions made:

https://docs.google.com/document/d/1O4qk5iPN9_8ICJbk4svjnUnDoMcZtoUn8pMSkOHcVDk/edit?usp=sharing

Please comment. A few key things to think about

  • Any missing topics
  • Too much ? 10 sessions at 1.5 to 2 hours each would probably take 2 weeks if we did 1 session day.
  • Is this close enough to ask for input from all collaborators more directly (we've mostly been talking among TSC members so far).
mhdawson

comment created time in 6 days

issue commentnodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

I'd also suggest we have people pre-register for topics/slots so that people don't go out of their way to get to a session that ends up not having enough attendees.

apapirovski

comment created time in 6 days

issue commentnodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

With the suggestion that we have 2 slots per topic to get broad coverage I'd then suggest we go in this order:

Topic 1 - Slot1, Slot3 Topic 2 - Slot2, Slot4 etc..

apapirovski

comment created time in 6 days

issue commentnodejs/TSC

Logistics of organizing a TSC summit to discuss the future direction of Node.js

Been thinking about it to see what might make sense. It's really hard to cover all of the timezones. The best I've come up with so far is the following:

  • Assume sessions are 2 hours
  • Assume starting at 9AM and ending by 6 is Good
  • Assume starting at 8AM and ending by 8PM is Tolerable

Then we could look at these slots:

image

The result is at least one slot which is Good for each timezone, and at least one more that is Tolerable. There is also 1 more slot which is not Impossible for most of the timezones except for Pacific.

apapirovski

comment created time in 6 days

pull request commentnodejs/node

src: clean v8 namespaces in env.cc file

Retry of just the failing sub-jobs

https://ci.nodejs.org/job/node-test-binary-windows-js-suites/2663/ https://ci.nodejs.org/job/node-test-commit-windows-fanned/

juanarbol

comment created time in 7 days

pull request commentnodejs/admin

WIP - doc: allow multiple orgs and add pkgjs org

@mcollina thanks, will add that to the list.

mhdawson

comment created time in 7 days

issue commentnodejs/node

Retry on failed ICU data load, ignoring NODE_ICU_DATA or --icu-data-dir

@srl295 I like the idea of the error message for the case where the requested data cannot be found indicating that you may not need the command line option anymore for versions where the data is bundle in.

srl295

comment created time in 7 days

issue commentnodejs/Release

Release plan - v10.x Active LTS

+1 to moving from me as well due to the notarization issue.

BethGriggs

comment created time in 7 days

issue commentnodejs/diagnostics

COVID-19 and WG sittings

Business as usual for me.

gireeshpunathil

comment created time in 7 days

pull request commentnodejs/node

[v10.x] Backport N-API 6 to v10.x

Sorry got that backwards, it is at the end in 10.x but not in master.

gabrielschulhof

comment created time in 7 days

pull request commentnodejs/node

[v10.x] Backport N-API 6 to v10.x

@gabrielschulhof thanks.

Not a big deal but I noted that the order of the functions in the NAPI-VERSION >= block is different in 10.x versus master. (napi_get_all_property_names is at the end in master but not in 10.x)

gabrielschulhof

comment created time in 7 days

Pull request review commentnodejs/build

[WIP] ansible: add 1015 orka test macs

 hosts:         macos10.11-x64-2: {ip: 207.254.58.162, port: 10004, user: administrator}         macos10.12-x64-1: {ip: 207.254.58.162, port: 10001, user: administrator}         macos10.12-x64-2: {ip: 207.254.58.162, port: 10002, user: administrator}+        macos10.15-x64-1: {ip: 199.7.167.99, port: 8823, user: administrator}+        macos10.15-x64-2: {ip: 199.7.167.100, port: 8823, user: administrator}+        macos10.15-x64-3: {ip: 199.7.167.99, port: 8824, user: administrator}

LGTM

AshCripps

comment created time in 7 days

issue commentnodejs/package-maintenance

PkgJS Org for WG supported tooling

Opened this to tweak governance. https://github.com/nodejs/admin/pull/484

We'll also need to request that the package maintenance team be chartered and delegated some ownership of the pkgjs repo unless we want to request repos using the existing process. This is an option but I think discussion with @wesleytodd gave me the impression that was not what the team wanted.

wesleytodd

comment created time in 7 days

pull request commentnodejs/admin

WIP - doc: allow multiple orgs and add pkgjs org

This is first part of several that are needed for https://github.com/nodejs/admin/issues/470. Should not land until those have been covered off:

  • [ ] Proposed charter for Package Maintenance team which delegates approval of the creation of new repos to that team, addition of members, along with some org owner capability. I believe this is what the package maintenance team wants, but need to work through the details.
mhdawson

comment created time in 7 days

PR opened nodejs/admin

WIP - doc: allow multiple orgs and add pkgjs org

Refs: https://github.com/nodejs/admin/issues/470

Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com

+13 -9

0 comment

1 changed file

pr created time in 7 days

create barnchmhdawson/admin

branch : orgman

created branch time in 7 days

issue commentnodejs/admin

Additional org owned by Node.js project for package maintenance team

No objections by Monday so considered approved.

mhdawson

comment created time in 7 days

push eventmhdawson/resume

Michael Dawson

commit sha 2e30ff176e4ae057ebcc15aa87a268dbb8ad2ae8

doc: more fixup

view details

push time in 7 days

push eventmhdawson/resume

Michael Dawson

commit sha 99826703e5f4d8ff3940caa5786ae312dae19e5c

doc: fix formatting

view details

push time in 7 days

push eventmhdawson/resume

Michael Dawson

commit sha e7a1e3b117d48a8db8d7f39f679c04dd53c15522

squash: add SEMIUG talk

view details

push time in 7 days

push eventmhdawson/presentations

Michael Dawson

commit sha e8852d1f7c4cd64aeece91566cbaf28208f3bff4

doc: add SEMIUG presentation

view details

push time in 7 days

issue commentopenjs-foundation/cross-project-council

Self-managed maintainer directory + Groups.io mailing lists on @lists.openjsf.org

Great to hear its working. Maybe the next ones to do are the CPC related ones?

brianwarner

comment created time in 7 days

issue commentopenjs-foundation/cross-project-council

Voting members chosen by Regular members

I also agree its a good time to discuss if we should start that now as well.

joesepi

comment created time in 7 days

issue commentopenjs-foundation/cross-project-council

Voting members chosen by Regular members

You are correct that we've not done it before.

joesepi

comment created time in 7 days

issue commentnodejs/Release

Release cadence due to COVID-19 Pandemic

To clarify, the decision on using a beta is in the scope of the Release team, but I think it's an important enough change from our regular process that I think it's important the TSC has an FYI which is why I've added to the agenda.

MylesBorins

comment created time in 7 days

pull request commentnodejs/node

src: clean v8 namespaces in env.cc file

And again: https://ci.nodejs.org/job/node-test-pull-request/30068/

juanarbol

comment created time in 8 days

issue commentnodejs/node

Retry on failed ICU data load, ignoring NODE_ICU_DATA or --icu-data-dir

My current thinking is that I'd prefer that if we can't do what you ask it results in an error like it does now. In terms of being able to additionally specify to fall back I wonder if it is a common enough use case to warrant the extra work/code?

srl295

comment created time in 8 days

pull request commentnodejs/node

[v10.x] Backport N-API 6 to v10.x

@gabrielschulhof did the commits apply cleanly?

gabrielschulhof

comment created time in 8 days

pull request commentnodejs/node

[v12.x] Backport n api 6 to v12.x

@gabrielschulhof did the commits apply cleanly?

gabrielschulhof

comment created time in 8 days

issue commentnodejs/Release

Release cadence due to COVID-19 Pandemic

Going to mark for TSC agenda so that we have discussion on whether our project is comfortable shipping with a beta.

MylesBorins

comment created time in 8 days

push eventnodejs/TSC

Michael Dawson

commit sha a0f357df4fc4662442da628229264aa434c4ebed

doc: add minutes for meeting 18 March 2020 (#839) * doc: add minutes for meeting 18 March 2020 PR-URL: https://github.com/nodejs/TSC/pull/839 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>

view details

push time in 8 days

PR merged nodejs/TSC

doc: add minutes for meeting 18 March 2020

Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com

+115 -0

0 comment

1 changed file

mhdawson

pr closed time in 8 days

push eventnodejs/TSC

Michael Dawson

commit sha d5a608a3eec697d5c091e41ce1054d5bbc6fd107

doc: update strategic initiatives (#833) * Move N-API to complete * Move Standards to complete * Move New Stream APIs to needs mentor * Remove Mentoring from needs volunters as owned by CommComm * Remove nsp and modules as modules has an entry and not sure what other this was covering PR-URL: https://github.com/nodejs/TSC/pull/833 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>

view details

push time in 8 days

PR merged nodejs/TSC

doc: update strategic initiatives
  • Move N-API to complete
  • Move Standards to complete
  • Move New Stream APIs to needs mentor
  • Remove Mentoring from needs volunters as owned by CommComm
  • Remove nsp and modules as modules has an entry and not sure what other this was covering
+7 -10

2 comments

1 changed file

mhdawson

pr closed time in 8 days

issue commentnodejs/TSC

Review meeting date times ?

@nodejs/tsc I think we'll all have shifted (if a shift was going to occur next week). Please make sure to have updated your entries by end of this week.

@ChALkeR can you do another pass at good times next monday?

mhdawson

comment created time in 8 days

issue commentnodejs/Release

Release cadence due to COVID-19 Pandemic

@MylesBorins can you clarify what you mean by that. Do you mean that it will be out of beta by the time we ship 14.x or that you are saying that its ok to use a beta in 14.x based on discussion with the V8 team?

MylesBorins

comment created time in 8 days

issue closednodejs/TSC

Re-nominate @gireeshpunathil to TSC

@gireeshpunathil stepped down from the TSC as IBM was over the maximum numbers after one of the TSC members resigned. As part of that discussion it was suggested we should re-nominate him as soon as the numbers were expanded. I'm formalizing that suggestion in this issue,

Once we confirm @BridgeAR (see https://github.com/nodejs/TSC/issues/811). I'd like to nominate @gireeshpunathil to rejoin the TSC.

I'd also suggest we can waive the usual 3 weeks of attending the TSC meetings as an observer due to his recent participation in the TSC over the last year.

closed time in 8 days

mhdawson

issue commentnodejs/TSC

Re-nominate @gireeshpunathil to TSC

Checklist complete, closing.

mhdawson

comment created time in 8 days

issue closednodejs/TSC

Nominating Matheus Marchini (mmarchini) to the TSC

I would like to nominate @mmarchini to the TSC. Matheus is a long time contributor to the Node project, particularly in the areas of diagnostics and post-mortem debugging.

There have been no objections from the private TSC discussion, and I have contacted Matheus privately to verify their interest.

closed time in 8 days

cjihrig

issue commentnodejs/TSC

Nominating Matheus Marchini (mmarchini) to the TSC

Checklist complete, closing.

cjihrig

comment created time in 8 days

issue closednodejs/TSC

Nominating Shelley Vohr (codebytere) to the TSC

I would like to nominate @codebytere to the TSC. In addition to her excellent code contributions to Node.js core, Shelley is the only active releaser not yet on the TSC. She would also bring representation of significant entities to the TSC, specifically Electron, embedders in general, and Microsoft. Shelley is also a current member of the Moderation Team.

There have been no objections from the private TSC discussion, and I have contacted Shelley privately to verify their interest.

closed time in 8 days

Trott

issue commentnodejs/TSC

Nominating Shelley Vohr (codebytere) to the TSC

Checklist complete, closing.

Trott

comment created time in 8 days

pull request commentnodejs/email

doc: add new TSC members to mailing lists

Deployed

mhdawson

comment created time in 8 days

push eventnodejs/email

Michael Dawson

commit sha 10e64205a10d8c10e62435b158b93d2607642f72

doc: add new TSC members to mailing lists (#155) Refs: https://github.com/nodejs/TSC/issues/829 Refs: https://github.com/nodejs/TSC/issues/832 Refs: https://github.com/nodejs/TSC/issues/831 Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

view details

push time in 8 days

PR merged nodejs/email

doc: add new TSC members to mailing lists

Refs: https://github.com/nodejs/TSC/issues/829 Refs: https://github.com/nodejs/TSC/issues/832 Refs: https://github.com/nodejs/TSC/issues/831

Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com

+6 -0

0 comment

1 changed file

mhdawson

pr closed time in 8 days

push eventnodejs/create-node-meeting-artifacts

Michael Dawson

commit sha 879c9b0892a5e2884b0b6f65dbd5933906ab7ad5

doc: add new TSC members (#89) Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

view details

push time in 8 days

more