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/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.

ibmruntimes/yieldable-json 68

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

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

issue commentnodejs/TSC

De-charter Benchmark WG

In terms of the core benchmark is extremely important and we run it very often. I'd agree that we should keep that.

Sounds like we'd like to keep all of the current Benchmarking WG jobs going. One challenge is if we archive the repo is that is where they scripts etc. are maintained. Maybe we'd need to look at migrating them to the core of build repos? Or maybe just leave as is but report issues in the core or build repos?

We'll need some volunteers to help with whatever we decided to keep around. The one for the core benchmark maybe a more manageable as it's smaller/less work but even there its been some trouble getting the cyles to do requested updates.

mhdawson

comment created time in an hour

issue commentnodejs/TSC

De-charter Benchmark WG

@mmarchini we can keep it going, the main thing is having people who will help investigate issues/fixup the jobs if they stop working.

mhdawson

comment created time in an hour

issue commentnodejs/TSC

De-charter Benchmark WG

The job to run the core benchmarks was setup by the Benchmarking WG, but if there is still interest it can just be taken over by core/build as any other CI job.

mhdawson

comment created time in 3 hours

issue commentnodejs/benchmarking

Node.js Foundation Benchmarking WorkGroup Meeting 2020-02-18

Had a quick chat with @octaviansoldea, end result is captured in: https://github.com/nodejs/TSC/issues/822

mhdawson

comment created time in 3 hours

issue closednodejs/benchmarking

Node.js Foundation Benchmarking WorkGroup Meeting 2020-02-18

Time

UTC Tue 18-Feb-2020 20:00 (08:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Benchmarking%20WorkGroup+Meeting+2020-02-18&iso=20200218T20
  • or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Feb+18%2C+2020+in+local+time

Links

Agenda

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

nodejs/benchmarking

  • Investigate the time taken, and number of benchmarks in core #225

Invited

  • Benchmarking team: @nodejs/benchmarking

Observers/Guests

Notes

The agenda comes from issues labelled with benchmarking-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/345481302
  • 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

closed time in 3 hours

mhdawson

issue openednodejs/TSC

De-charter Benchmark WG

Activity in the benchmarking WG has been low over the last year. After some efforts to try to increase interest/participation and looking for people that would be interested in chairing/leading the group I think it is time to de-charter the WG.

I still believe this is an important area but without critical mass I don't think it makes sense for the WG to continue.

The main thing we'll have to spin down is benchmarking.nodejs.org, diable the related jobs and then archive the repo.

coverage.nodejs.org does still use some of the same machines/infra so we'll need to avoid removing the pieces it needs during the spin down.

created time in 3 hours

issue commentnodejs/benchmarking

Node.js Foundation Benchmarking WorkGroup Meeting 2020-02-18

Looks like I have to wait 5 minutes for lastpass to time out

mhdawson

comment created time in 3 hours

issue commentnodejs/benchmarking

Node.js Foundation Benchmarking WorkGroup Meeting 2020-02-18

Trying to login to lastpass to start meeting. Taking a few attempts

mhdawson

comment created time in 3 hours

push eventopenjs-foundation/cross-project-council

Michael Dawson

commit sha 0f0cdb47597f62618b81903bbe56bdd62576b810

doc: add project specific allocation option/process As requested in the discussion related to moving the travel fund to the OpenJS level.

view details

push time in 7 hours

PR merged openjs-foundation/cross-project-council

doc: add project specific allocation option/process

As requested in the discussion related to moving the travel fund to the OpenJS level.

+26 -0

2 comments

1 changed file

mhdawson

pr closed time in 7 hours

pull request commentopenjs-foundation/cross-project-council

doc: add project specific allocation option/process

I think this falls into the Governance change and meets the landing requirements as it has been open >14 days, there are no objections and we have enough approvals.

mhdawson

comment created time in 7 hours

push eventmhdawson/bootstrap

Daijiro Wachi

commit sha 03a5ac7d4a0fed53eec54edb42780cb8570252fd

doc: fix links in proposals index (#452)

view details

Michael Dawson

commit sha 3568888a5a3b799c285246588bbb814557fdc441

doc: add allocation for 2020 (#454)

view details

Jory Burson

commit sha 2bb3e997c515f58d60f40e5c191a0fa0cad9043f

creates directory for project resources per #445 (#456) * creates directory for project resources per #445 * add link in readme to travel fund

view details

Joe Sepi

commit sha 92d318f15e1fd531c22441fd58fc3ed1a4a1dd49

Adding meeting notes Jan 21 and 28 2020 (#457) * Adding meeting notes Jan 21 and 28 2020 * Update meetings/2020-01-21.md Co-Authored-By: Michael Dawson <michael_dawson@ca.ibm.com> * Update meetings/2020-01-28.md Co-Authored-By: Michael Dawson <michael_dawson@ca.ibm.com> Co-authored-by: Michael Dawson <michael_dawson@ca.ibm.com>

view details

Dhruv Jain

commit sha cf1e8552a5a02b579918659ab73f0cfcf61db1a3

add dhruv as regular member (#460)

view details

Michael Dawson

commit sha f5885e388e62dc2f4ef41b1ee009d05defeae8d5

doc: move COC proposal to stage 3 (#379)

view details

Michael Dawson

commit sha ad0d56ad5bf8d65f7c5d799a02d807912654bc32

doc: add project specific allocation option/process As requested in the discussion related to moving the travel fund to the OpenJS level.

view details

push time in 7 hours

issue commentnodejs/security-wg

Change repo name?

@DanielRuf good point on the redirects.

MylesBorins

comment created time in 9 hours

issue commentnodejs/node

Do not pass `napi_env` to async worker's execute callback

@gabrielschulhof if you agree I'll go ahead and create a PR to document.

gabrielschulhof

comment created time in a day

issue commentnodejs/node

Do not pass `napi_env` to async worker's execute callback

+1 to documenting.

gabrielschulhof

comment created time in a day

issue commentnodejs/build

Tracking Jenkins changes

@rvagg I seem to remember there was a way to find the person who triggered a change. Can you remind me how? Looking in https://github.com/nodejs/jenkins-config-test/blob/master/jobs/libuv-test-commit.xml I've not found it yet.

richardlau

comment created time in a day

issue closednodejs/build

Add centos7 PPCle machines

If possible we'd like to build on Centos76 for PPC now that centos is available at OSU. Starting with using them for 12.x and above and then seeing if we can use them for older releases as well.

  • [x] Add 2 test centos machines (test-osuosl-centos7-ppc64-le-1, test-osuosl-centos7-ppc64-le-2)
  • [x] Configure test machines with existing Ansible scripts if possible
  • [x] Validate that compiler is installed properly: devtoolset-6 installed
  • [x] Update ansible scripts if necessary
  • [x] Update regression tests so that tests also run on centos76 for 12.x+, validate all passes
  • [x] Add 1 release centos machine (release-osuosl-centos7-ppc64-le-1)
  • [X] update select-compiler.sh: select devtoolset-6 ONLY for centos7-ppc64le (if it's ubuntu, continue ot use gcc-6)
  • [x] Configure release machine with Ansible
  • [x] Add release machine to release CI.
  • [x] ... add additional required keys to release machine etc.
  • [x] Do test builds with cloned release job where we build releases on centos7 for 13+ instead of unbuntu
  • [x] Land PR for groovy selector to start doing releases on centos7 for 13+ instead of ubuntu
  • [ ] Audit community test jobs to make sure we have added centos7 to all test jobs
  • [ ] Identify next release, and plan switch over so that we get X days of nightly build/testing before next real release.
  • [ ] Land PR for groovy selector to start doing releases on centos7 for 12+ instead of ubuntu

closed time in a day

mhdawson

issue commentnodejs/build

Add centos7 PPCle machines

@sam-github can you confirm and close.

mhdawson

comment created time in a day

push eventnodejs/node-addon-api

ikokostya

commit sha cb498bbe7f8aa601e95c7946df3db6dedf15f709

doc: Add Napi::BigInt::New() overload for uint64_t

view details

push time in a day

PR merged nodejs/node-addon-api

doc: Add Napi::BigInt::New() overload for uint64_t

Link to the source code: https://github.com/nodejs/node-addon-api/blob/7f56a78ff7eab77f1316696aef1de3304b70e639/napi.h#L349-L352

+1 -0

0 comment

1 changed file

ikokostya

pr closed time in a day

push eventnodejs/node-addon-api

legendecas

commit sha baaaa8452c0326f652d6bff2e8f58a2ba8c5f59b

doc: link threadsafe function from JS function * doc: link threadsafe function from JS function

view details

push time in a day

PR merged nodejs/node-addon-api

doc: link threadsafe function from JS function doc

I've seen complains that there is no documents on napi/node-addon-api alternatives for uv_async_ts. Link Napi::ThreadSafeFunction from JS function docs to highlight the option.

+6 -0

0 comment

1 changed file

legendecas

pr closed time in a day

pull request commentopenjs-foundation/cross-project-council

doc: add new reg member to email list

@joesepi, while you say its a governance change, we've already been doing it right? Just want to know if this is proposing a change in practice or documenting what we'd decided to do already.

joesepi

comment created time in a day

issue commentnodejs/package-maintenance

PkgJS Org for WG supported tooling

@wesleytodd do we have a list of those reasons that we can use for the discussions? Most if not all of the teams I know of are using repos under the Node.js org.

Can you also clarify what you mean by "official". I thought one of the concerns that led to a separate org was avoiding the impression of it being official.

wesleytodd

comment created time in a day

push eventnodejs/package-maintenance

Michael Dawson

commit sha cb8b9c0fd8800198e574c46aa950b40c4db77725

doc: integrate npm funding into backing (#312) * doc: integrate npm funding into backing Integrate the npm funding field into the list of options for the backing field.

view details

push time in a day

PR merged nodejs/package-maintenance

doc: integrate npm funding into backing

Integrate the npm funding field into the list of options for the backing field.

+8 -10

1 comment

1 changed file

mhdawson

pr closed time in a day

pull request commentnodejs/package-maintenance

doc: integrate npm funding into backing

More than 4 reviews, no blocking reviews and more than 7 days since 4th approval landing.

mhdawson

comment created time in a day

Pull request review commentnodejs/package-maintenance

doc: add minutes for 2020-02-11

+# Node.js Foundation Package Maintenance Team Meeting 2020-02-11++## Links++* **Recording**:  https://www.youtube.com/watch?v=C3dSzJZWLDw+* **GitHub Issue**: https://github.com/nodejs/package-maintenance/issues/314+* **Minutes Google Doc**: https://docs.google.com/document/d/1qE-qBjsP-Ev773gRD3-U_NCAyeOl2zL1C-BjzBwAkR4+++## Present++* Beth Griggs (@BethGriggs)+* Glenn Hinks (@ghinks)+* Darcy Clarke (@darcyclarke)+* Ruy Adorno (@ruyadorno)+* Wes Todd (@wesleytodd)+* Dominykas Blyžė (@dominykas)+* Andrew Hughes (@andrewhughes101)++## Agenda++## Announcements++* (Wes) A planning meeting for the collaborator summit in Austin happened today.+  * Start thinking about what we would use a package maintenance session for.+  * (Action) Raise an issue to cover the summit.+* Package maintenance tooling breakout [#307](https://github.com/nodejs/package-maintenance/issues/307)+  * First meeting Thursday 13th February 2020 5PM UTC to clarify use cases.++*Extracted from **package-maintenance-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.++### nodejs/package-maintenance++* 2FA in CI [#282](https://github.com/nodejs/package-maintenance/pull/282)+  * Productive RFC call.+  * Follow up with notes and use cases.+  * Some technical details to be addressed+* Document the current 'top 10' express' issues [#233](https://github.com/nodejs/package-maintenance/issues/233)+  * Status board issue where indexing was timing out.+  * Seeking volunteers to do the work.+* Next steps on Support levels in Package.json [#192](https://github.com/nodejs/package-maintenance/issues/192)+  * A CLI help generate the support metadata, potentially as part of pkgjs+  * Requires evangelism and a blog post.+    * Michael would know the correct contact at the foundation to publish the blog.+    * Call for a volunteer to write the blog post.

I'll volunteer to write the blog post.

BethGriggs

comment created time in a day

issue commentnodejs/community-committee

Add licenses to CommComm repositories

@keywordnew I think that despite the "software" mention the suggestion was that for internal community documents it would still be ok.

bnb

comment created time in a day

issue commentnodejs/community-committee

Create Custom Url on Youtube

How about http://www.youtube.com/nodejs-project

SauloNunes

comment created time in a day

issue commentnodejs/TSC

Archival of the node-chakracore repo

+1 to archive once we have confirmation from the msft folks

cjihrig

comment created time in a day

issue commentopenjs-foundation/cross-project-council

OpenJS Foundation Cross Project Council Meeting 2020-02-18

We should add this to the agenda as well: https://github.com/openjs-foundation/cross-project-council/issues/469

mhdawson

comment created time in a day

issue openedopenjs-foundation/cross-project-council

Populate the Code Of Conduct Panel

Now that the base governance for Code of conduct reporting and handling has landed we need to populate the CoCP and/or modify the composition which specified to match what we believe the final form should be.

We agreed in https://github.com/openjs-foundation/cross-project-council/issues/432#issuecomment-585936270 that as an interim measure the members who had volunteered for the temporary Code of Conduct team in #432 could act as temporary CoCP members as we ramp up the members as specified in the governance. As such they should be include in escalation@openjsf.org along with @rginn as the Executive director of the foundation.

report@openjsf.org should already be going to all CPC members.

@brianwarner has agreed to send out/manage

  • call for volunteers/election for Board representative
  • call for volunteers/electrion for CPC representative

We'll need to start the same for representatives from the projects and marketing committee as well.

created time in a day

pull request commentopenjs-foundation/cross-project-council

doc: add marketing committee rep to CoCP

Opening this is one of the actions I took from the discussion in: https://github.com/openjs-foundation/cross-project-council/issues/432

mhdawson

comment created time in a day

PR opened openjs-foundation/cross-project-council

doc: add marketing committee rep to CoCP

Add a representative from the marketing committee to the CoCP. The CoC will be in place for conferences and events run by the marketing committee and handling of CoC reports from those events may be escalated to the CoCP so they should have a represenative.

+1 -0

0 comment

1 changed file

pr created time in a day

create barnchmhdawson/bootstrap

branch : add-marketing

created branch time in a day

push eventopenjs-foundation/cross-project-council

Michael Dawson

commit sha f5885e388e62dc2f4ef41b1ee009d05defeae8d5

doc: move COC proposal to stage 3 (#379)

view details

push time in a day

PR merged openjs-foundation/cross-project-council

doc: move COC proposal to stage 3 cross-project-council-agenda stage-3
+5 -5

12 comments

4 changed files

mhdawson

pr closed time in a day

pull request commentopenjs-foundation/cross-project-council

doc: move COC proposal to stage 3

#413 is complete.

There is agreement as captured in https://github.com/openjs-foundation/cross-project-council/issues/432#issuecomment-585936270. That this can land.

I believe this falls under the existing CPC Charter as per Supporting projects in their enforcement of Code of Conduct violations and escalation. and therefore does not need board approval.

Therefore it can be considered a change to the CPC governance and can be landed as we've met the criteria for landing in https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#merging-prs-into-this-repository:

  • There are no outstanding objections
  • There are two approvals by CPC members
  • The PR has been open for at least 72 hours
  • The PR has been open for at least 14 days
mhdawson

comment created time in a day

push eventmhdawson/bootstrap

Michael Dawson

commit sha 3eb970a2f06f3841873b722ab153e0eef897c120

doc: move COC proposal to stage 3

view details

push time in a day

pull request commentnodejs/node

Readme updates fishrock123

@Trott thanks. Merged those 2 PRs.

Fishrock123

comment created time in a day

push eventmhdawson/bootstrap

Michael Dawson

commit sha 26f69352bf696f09b1cc1526500c4511c43472b0

doc: move COC proposal to stage 3

view details

push time in a day

push eventmhdawson/bootstrap

Michael Dawson

commit sha bcbc6973436b17e7a1036881f0b30ed9d75d6d6b

doc: move COC proposal to stage 3

view details

push time in a day

push eventmhdawson/bootstrap

Jory Burson

commit sha 1a2f1decc4f3842ab5b91fb9e750ac261ae5d5d9

adds missing links for bylaws and mission/vision statements (#406) * adds missing links for bylaws and mission/vision statements per #230, #322

view details

Jory Burson

commit sha e88d3632b464d92566505e46ac37782af041f1d8

adds infra menu PR for discussion per issue #333 & CPC conversation (#396) * adds infra menu PR for discussion per issue #333 & CPC conversation

view details

Waleed Ashraf

commit sha 40b3cdd7f3717afcc830eb3dbf9244163f96415f

added @waleedashraf as member (#410)

view details

Brian Warner

commit sha 8c6bd70ceb8e617aa8251295799ba8cceb1717cb

Add guidance on marketing outreach (#399) Add instructions on how to contact the marketing team with requests, including posting an item to the OpenJS Foundation blog, requesting retweets and amplification, and getting items included in the newsletter which is periodically sent to projects@openjsf.org. Signed-off-by: Brian Warner <brian@bdwarner.com>

view details

Brian Warner

commit sha c0dd6ef2b8015bb7d7cd5918a2d8ab386fa8aed1

Add Electron and Fastify (#421) Update README and PROJECTS to include our most recent incubating projects. Signed-off-by: Brian Warner <brian@bdwarner.com>

view details

Christian Bromann

commit sha 0549ce254f56ee67a7a6db208eb6e1d19e23a36b

minor wording fix on governance doc (#430)

view details

Myles Borins

commit sha 4310af5379d96e13564db26523e4dc3bccf27356

chore: remove templates (#428) We are now doing project onboarding in another repo Refs: https://github.com/openjs-foundation/project-onboarding/pull/33

view details

Myles Borins

commit sha bec25dd6f72467b266343508fe91a34e0e8b7bbf

doc: add missing notes (#427) Closes: https://github.com/openjs-foundation/cross-project-council/issues/353 Closes: https://github.com/openjs-foundation/cross-project-council/issues/381 Closes: https://github.com/openjs-foundation/cross-project-council/issues/395 Closes: https://github.com/openjs-foundation/cross-project-council/issues/401 Closes: https://github.com/openjs-foundation/cross-project-council/issues/408 Closes: https://github.com/openjs-foundation/cross-project-council/issues/412 Closes: https://github.com/openjs-foundation/cross-project-council/issues/416

view details

Eemeli Aro

commit sha 374a94c87d5ef8dc1e0cad2c86089a6c5ea5e9bf

doc: Fix GOVERNANCE typos (#425)

view details

Mike Samuel

commit sha 4e81cf3fab3b7f1f1d601f8143ea22a6a738dcd7

fix markdown typos to make `npm run lint-md` run clean (#423)

view details

Myles Borins

commit sha a154509ec37bb2a7c4ed2cc37e6f1b52d9b08b08

doc: update license copyright to OpenJS foundation (#434) This is a relic of the repo being created in the Node.js foundation org Closes: https://github.com/openjs-foundation/cross-project-council/issues/382 Co-Authored-By: Brian Warner <brian@bdwarner.com>

view details

Myles Borins

commit sha 567e9ad6d6f1db6a1666a8ae5f26ca3cc3c053e7

build: add github action to run linter (#433) Closes: https://github.com/openjs-foundation/cross-project-council/issues/317

view details

Myles Borins

commit sha 13159adc4f8307892bffdbc7bc6a82a228166fda

doc: dec 17 2019 notes (#435) Closes: https://github.com/openjs-foundation/cross-project-council/issues/429

view details

Eemeli Aro

commit sha 7fc5dbd9e14eaf7780c876a48dafdea9339357ad

doc: Add a copy of the Contributor Covenant CoC text (#413)

view details

Mike Samuel

commit sha 79962e538b79e66cad56eba87e4e2aba552e6875

Clarify that champion duties extend through incubation. (#422) * Clarify that champion duties extend through incubation. Fixes #400 per @joesepi's summary of consensus > Champion remains point of contact through incubation. Documentation > needs to be updated to make that clear. * Update PROJECT_PROGRESSION.md Co-Authored-By: Antón Molleda <molant@users.noreply.github.com> * Properly capitalize "GitHub" Co-Authored-By: Antón Molleda <molant@users.noreply.github.com> * Update PROJECT_PROGRESSION.md Co-Authored-By: Tobie Langel <tobie@unlockopen.com> Co-authored-by: Antón Molleda <molant@users.noreply.github.com> Co-authored-by: Tobie Langel <tobie@unlockopen.com>

view details

Joe Sepi

commit sha 57236f1b07c1dc53eee5f9671606d115a8d3614d

doc: adding 2020-01-07 meeting notes (#442) * doc: adding 2020-01-07 meeting notes * Update 2020-01-07.md Added @codeekage to meeting attendees. * Update meetings/2020-01-07.md Co-Authored-By: Jordan Harband <ljharb@gmail.com> * Update meetings/2020-01-07.md Co-Authored-By: Jordan Harband <ljharb@gmail.com> Co-authored-by: Abraham Jr. Agiri <agiriabrahamjunior@gmail.com> Co-authored-by: Jordan Harband <ljharb@gmail.com>

view details

Jory Burson

commit sha 44a5d62e0ae6ccd2488d71a581005d74a93f93b0

adds proposal for charter submission & review per #200 (#405) * adds proposal for charter submission & review per #200 * updates per mcollina & mhdawson

view details

Ben Michel

commit sha c00bb629938775b6f8d23c773a8de818f24bcf30

Add Ben Michel as regular member (#439) * add Ben Michel as regular member * alphabetize members list

view details

Michael Dawson

commit sha 965b700edd25779a63cc7152c484f9b09aff4795

doc: document end date for CPC Director term (#440) * doc: document end date for CPC Director term

view details

Eemeli Aro

commit sha 72754c629ec9f2689d8ba9a056ae5e248bb071c8

Update CoC from Contributor Covenant 1.4 to 2.0 (#418)

view details

push time in a day

push eventmhdawson/bootstrap

Michael Dawson

commit sha 6101f4ed42aa7e3b44187334e7c1b1ea8ce8f144

doc: add minutes for meeting Oct 22 2018

view details

push time in a day

push eventnodejs/create-node-meeting-artifacts

Rich Trott

commit sha 22be38dc48cc0d3204d154be3bea318c80dc582a

update TSC invitation list (#85) * update TSC invitation list

view details

push time in a day

pull request commentnodejs/create-node-meeting-artifacts

update TSC invitation list

Landing since this is a reflection of reality and already has 3 approvals

Trott

comment created time in a day

issue commentopenjs-foundation/summit

Travel Fund Questions for Project Community Members

I think this are a good starting point. I would be nice to be more specific than sustained contributions to the project for the past 90 days but I don't have a better suggestion.

jorydotcom

comment created time in a day

issue commentnodejs/security-wg

Change repo name?

A few things to consider:

  • The repo contains the vulnerability database any any effect that will have tools that use the database. In the past we provide a period of time before making a potentially breaking change like this
  • The vulnerability database also contains the core vulns: https://github.com/nodejs/security-wg/tree/master/vuln/core
MylesBorins

comment created time in a day

pull request commentnodejs/security-wg

vuln: Node.js Feb 2020 security release

Looks to me like the issue is capitalization from the job output:

     { ValidationError: child "cve" fails because ["cve" at position 0 fails because ["0" with value "MOCK-0000-1234" fails to match the required pattern: /CVE-\d{4}-\d+/]]
sam-github

comment created time in a day

issue commentnodejs/security-wg

Triage Buckets and Prioritization

I'm +1 for raising the cutoff for high priority

lirantal

comment created time in a day

push eventnodejs/node-addon-examples

legendecas

commit sha d883f378bdbf00f04263d77a0582a337f07a152e

Prevent asserting with significant expressions (#126) * Move code that is necessary to run out of assert() so it runs in non-debug builds PR-URL: https://github.com/nodejs/node-addon-examples/pull/126 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>

view details

push time in a day

PR merged nodejs/node-addon-examples

Prevent asserting with significant expressions

Also renamed category node-api to napi

Additional to #79.

+99 -63

1 comment

9 changed files

legendecas

pr closed time in a day

pull request commentnodejs/email

remove TSC emeriti from relevant lists

deployed

Trott

comment created time in a day

push eventnodejs/email

Rich Trott

commit sha ab134a5c7e0c9dcc2d35eb1acf9d92d62f7e3946

remove TSC emeriti from relevant lists

view details

push time in a day

PR merged nodejs/email

remove TSC emeriti from relevant lists

@nodejs/tsc

+0 -5

1 comment

1 changed file

Trott

pr closed time in a day

pull request commentnodejs/email

remove TSC emeriti from relevant lists

Landing since it simply a reflection of fact and already has a good number of approvals.

Trott

comment created time in a day

pull request commentnodejs/create-node-meeting-artifacts

update TSC invitation list

@Trott Ruben was added as an observer in https://github.com/nodejs/create-node-meeting-artifacts/pull/83 and showed up in the recent meeting.

If you think he needs to be part of the invited list instead of observer, then you should add the removal of him from the observer list to this PR.

Trott

comment created time in a day

pull request commentnodejs/node-addon-api

Implement AsyncProgressQueueWorker

@nodejs/addon-api this is ready for review.

legendecas

comment created time in a day

issue closednodejs/admin

Approval to promote @weelsytodd to maintainer of nodejs / web-server-frameworks team

I'd like to give @wesleytodd maintainer access to the nodejs / web-server-frameworks team so that he can add/manage members. This seems to be the case for a few other teams (ex security-wg) so I think its ok but wanted to record and get approval here.

closed time in a day

mhdawson

issue commentnodejs/admin

Approval to promote @weelsytodd to maintainer of nodejs / web-server-frameworks team

@wesleytodd you are now a maintainer for that team

mhdawson

comment created time in a day

issue commentnodejs/admin

Approval to promote @weelsytodd to maintainer of nodejs / web-server-frameworks team

No objections and one approval so I'm going to go ahead and do it. @nodejs/tsc @nodejs/community-committee another FYI let me know if you object and I'll revert.

mhdawson

comment created time in a day

push eventnodejs/diagnostics

legendecas

commit sha dde51ccb444aedda2a9695df68dbbed4673ff470

doc: add more symptoms (#353)

view details

push time in a day

PR merged nodejs/diagnostics

doc: add more symptoms structure

Follow up of #333.

+8 -0

0 comment

8 changed files

legendecas

pr closed time in a day

issue commentnodejs/diagnostics

reportVersion semantics are not defined

It is reasonable to expect no data type changes being applied to the fields.

Can we depend on that? Maybe we should add a point to your list that says:

  • changes the data type for a field
addaleax

comment created time in a day

issue commentnodejs/TSC

Ability for website team to transfer issues to nodejs/help

As an FYI to TSC members there are 158 members of the website team https://github.com/orgs/nodejs/teams/website

nschonni

comment created time in a day

issue commentnodejs/TSC

Review meeting date times ?

I've added another sheet for Thursday. I have a feeling we are going to need to use 2 days.

mhdawson

comment created time in a day

issue openedopenjs-foundation/cross-project-council

OpenJS Foundation Cross Project Council Meeting 2020-02-18

Time

UTC Tue 18-Feb-2020 19:00 (07:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Cross%20Project%20Council+Meeting+2020-02-18&iso=20200218T19
  • or http://www.wolframalpha.com/input/?i=07PM+UTC%2C+Feb+18%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

  • OpenJS Office Ours #465
  • Start a Code of Conduct Team #432
  • Add Foundation-wide copyright guidance #414
  • Add post-graduation checklist #386
  • doc: move COC proposal to stage 3 #379
  • Responsible security disclosures #326
  • Add admin policy docs #185
  • Project Directed Funding #90

openjs-foundation/standards

  • Chartering the standards team #58
  • Joining the Unicode Consortium #43

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 a day

issue openednodejs/community-committee

Node.js Foundation Community Committee Meeting 2020-02-20

Time

UTC Thu 20-Feb-2020 17:00 (05:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee+Meeting+2020-02-20&iso=20200220T17
  • or http://www.wolframalpha.com/input/?i=05PM+UTC%2C+Feb+20%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

  • Node.js Social Media Accounts #454

nodejs/community-committee

  • Starting an Examples Initiative #550
  • Community Committee and OKRs #547

nodejs/nodejs-collection

  • Update readme with new process #37

nodejs/nodejs.dev

  • Onboarding: @SauloNunes and @BenHalverson #406

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 a day

issue openednodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-02-19

Time

UTC Wed 19-Feb-2020 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 19-Feb-2020 07:00 (07:00 AM)
US / Mountain Wed 19-Feb-2020 08:00 (08:00 AM)
US / Central Wed 19-Feb-2020 09:00 (09:00 AM)
US / Eastern Wed 19-Feb-2020 10:00 (10:00 AM)
London Wed 19-Feb-2020 15:00 (03:00 PM)
Amsterdam Wed 19-Feb-2020 16:00 (04:00 PM)
Moscow Wed 19-Feb-2020 18:00 (06:00 PM)
Chennai Wed 19-Feb-2020 20:30 (08:30 PM)
Hangzhou Wed 19-Feb-2020 23:00 (11:00 PM)
Tokyo Thu 20-Feb-2020 00:00 (12:00 AM)
Sydney Thu 20-Feb-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-02-19&iso=20200219T15
  • or http://www.wolframalpha.com/input/?i=03PM+UTC%2C+Feb+19%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/TSC

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

nodejs/admin

  • Node.js Social Media Accounts #454

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)
  • Jeremiah Senkpiel @Fishrock123 (TSC)
  • Gabriel Schulhof @gabrielschulhof (TSC)
  • Gireesh Punathil @gireeshpunathil (TSC)
  • James Snell @jasnell (TSC)
  • Joyee Cheung @joyeecheung (TSC)
  • Matteo Collina @mcollina (TSC)
  • Michael Dawson @mhdawson (TSC)
  • Myles Borins @MylesBorins (TSC)
  • Sam Roberts @sam-github (TSC)
  • Michaël Zasso @targos (TSC)
  • Sakthipriyan Vairamani @thefourtheye (TSC)
  • Tobias Nießen @tniessen (TSC)
  • Rich Trott @Trott (TSC)

Observers/Guests

Ruben Bridgewater @BridgeAR (observer)

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 a day

issue openednodejsafrica/admin

Node.js Africa Team leadership Meeting 2020-02-21

Time

UTC Fri 21-Feb-2020 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Fri 21-Feb-2020 09:00 (09:00 AM)
US / Mountain Fri 21-Feb-2020 10:00 (10:00 AM)
US / Central Fri 21-Feb-2020 11:00 (11:00 AM)
US / Eastern Fri 21-Feb-2020 12:00 (12:00 PM)
London Fri 21-Feb-2020 17:00 (05:00 PM)
Amsterdam Fri 21-Feb-2020 18:00 (06:00 PM)
Moscow Fri 21-Feb-2020 20:00 (08:00 PM)
Chennai Fri 21-Feb-2020 22:30 (10:30 PM)
Hangzhou Sat 22-Feb-2020 01:00 (01:00 AM)
Tokyo Sat 22-Feb-2020 02:00 (02:00 AM)
Sydney Sat 22-Feb-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-02-21&iso=20200221T17
  • or http://www.wolframalpha.com/input/?i=05PM+UTC%2C+Feb+21%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 a day

PR closed nodejs/node

doc: guide - using valgrind to debug memory leaks doc

Add doc for using valgrind to debug native memory leaks.

Started writing this up as part of an effort in the Diagnostic WG but think it's better to have it in the core guides and then be referenced by the docs in the Diagnostic WG repo.

For more details on the Diagnostic WG effort see https://github.com/nodejs/diagnostics/issues/254#issuecomment-538853390 This guide is related to /step3 - using_native_tools.md

<!-- 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. -->

+447 -0

5 comments

1 changed file

mhdawson

pr closed time in 4 days

pull request commentnodejs/node

doc: guide - using valgrind to debug memory leaks

`Landed in 89c1aa3

mhdawson

comment created time in 4 days

push eventnodejs/node

Michael Dawson

commit sha 79296dc2d02c0b9872bbfcbb89148ea036a546d0

doc: guide - using valgrind to debug memory leaks Add doc for using valgrind to debug native memory leaks. Started writing this up as part of an effort in the Diagnostic WG but think it's better to have it in the core guides and then be referenced by the docs in the Diagnostic WG repo. For more details on the Diagnostic WG effort see https://github.com/nodejs/diagnostics/issues/254#issuecomment-538853390 This guide is related to `/step3 - using_native_tools.md` PR-URL: https://github.com/nodejs/node/pull/31501 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>

view details

push time in 4 days

Pull request review commentnodejs/diagnostics

doc: add minutes for meeting 2020-02-12

+# Node.js Foundation Diagnostics WorkGroup Meeting 2020-02-12++## Links++* **Recording**:  +* **GitHub Issue**: $GITHUB_ISSUE$
* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/354
mmarchini

comment created time in 4 days

Pull request review commentnodejs/diagnostics

doc: add minutes for meeting 2020-02-12

+# Node.js Foundation Diagnostics WorkGroup Meeting 2020-02-12++## Links++* **Recording**:  +* **GitHub Issue**: $GITHUB_ISSUE$+* **Minutes Google Doc**: $MINUTES_DOC$
mmarchini

comment created time in 4 days

Pull request review commentnodejs/diagnostics

doc: add minutes for meeting 2020-02-12

+# Node.js Foundation Diagnostics WorkGroup Meeting 2020-02-12++## Links++* **Recording**:  
* **Recording**: https://youtu.be/oyl6-HYBw9w
mmarchini

comment created time in 4 days

Pull request review commentnodejs/node-addon-examples

Prevent asserting with significant expressions

 static void ExecuteWork(napi_env env, void* data) {        // Initiate the call into JavaScript. The call into JavaScript will not       // have happened when this function returns, but it will be queued.-      assert(napi_call_threadsafe_function(addon_data->tsfn,+      status = napi_call_threadsafe_function(addon_data->tsfn,                                            the_prime,-                                           napi_tsfn_blocking) == napi_ok);+                                           napi_tsfn_blocking);+      assert(status == napi_ok);     }   }    // Indicate that this thread will make no further use of the thread-safe function.-  assert(napi_release_threadsafe_function(addon_data->tsfn,-                                          napi_tsfn_release) == napi_ok);+  status = napi_release_threadsafe_function(addon_data->tsfn,+                                          napi_tsfn_release);+  assert(status == napi_ok); }  // This function runs on the main thread after `ExecuteWork` exits. static void WorkComplete(napi_env env, napi_status status, void* data) {   AddonData* addon_data = (AddonData*)data;+  napi_status s;

A nit but I'd prefer a more complete name, for example status versus the one letter name

legendecas

comment created time in 4 days

issue commentnodejs/abi-stable-node

Advocate the use of tags in addition to badges

Do you have a proposal for what the npm/github tags would be?

gabrielschulhof

comment created time in 4 days

issue commentnodejs/TSC

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

@joyeecheung, the Node.js/OpenJS event is already so packed I'm not sure we could fit in a full day for something like this. I'd also be concerned that people will not have enough energy left over even if we can. I'd lean towards trying a full day online summit (maybe 2 half days to try to cover timezones) for this one.

mhdawson

comment created time in 4 days

issue commentnodejs/TSC

Review meeting date times ?

I wonder if we should also discuss a different day based on the comment by @targos. Possibly a timeslot on Thursday?

mhdawson

comment created time in 4 days

issue commentnodejs/TSC

Timing of TSC member addition / resignation

@gireeshpunathil thanks for doing that.

tniessen

comment created time in 4 days

push eventmhdawson/io.js

Michael Dawson

commit sha d1773b2f83dd770a9cc7167d4dbb6f5bf1eac0a1

Update doc/guides/investigating_native_memory_leak.md

view details

push time in 4 days

Pull request review commentnodejs/node

doc: guide - using valgrind to debug memory leaks

+# Investigating Memory Leaks with valgrind++A Node.js process may run out of memory due to excessive consumption of+native memory. Native Memory is memory which is not managed by the+V8 Garbage collector and is allocated either by the Node.js runtime, its+dependencies or native [addons](https://nodejs.org/docs/latest/api/n-api.html).++This guide provides information on how to use valgrind to investigate these+issues.
issues on Linux platforms.
mhdawson

comment created time in 4 days

issue commentopenjs-foundation/cross-project-council

Balancing privacy vs. transparency for the travel fund

@tobie will keep an eye out and if you talk to people who have concerns or who are applying because its public please ask them to talk to me or Joe.

tobie

comment created time in 5 days

issue commentopenjs-foundation/cross-project-council

Balancing privacy vs. transparency for the travel fund

I'm not sure it's as clear as it once was for Node.js. At one, you point need to be an individual member of the Node.js Foundation to use the travel fund. Individual membership was free for those who were members of the Node.js org. With the merger, I'm not sure individual membership (or at least the ability to sign up) is still working (see https://github.com/nodejs/admin/issues/445#issuecomment-567211536).

This is something we need to improve. I agree that each project likely needs to set the qualifications and how they are validated and that needs to be documented somewhere relatively easy to find.

tobie

comment created time in 5 days

issue commentnodejs/TSC

Timing of TSC member addition / resignation

@sam-github thanks for jumping in with the offer.

tniessen

comment created time in 6 days

issue commentnodejs/TSC

Timing of TSC member addition / resignation

@nodejs/tsc please chime in on what you think is best.

tniessen

comment created time in 6 days

issue commentnodejs/build

remove ppcle-ubuntu1404?

+1 to removing.

richardlau

comment created time in 6 days

issue commentnodejs/TSC

Timing of TSC member addition / removal

@tniessen thanks for opening, just catching up on latest events.

@Fishrock123 just let me know what your feeling is on this. If you don't want to delay I'll get started on figuring out who drops out on the IBM side.

tniessen

comment created time in 6 days

issue closednodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-02-12

Time

UTC Wed 12-Feb-2020 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 12-Feb-2020 12:00 (12:00 PM)
US / Mountain Wed 12-Feb-2020 13:00 (01:00 PM)
US / Central Wed 12-Feb-2020 14:00 (02:00 PM)
US / Eastern Wed 12-Feb-2020 15:00 (03:00 PM)
London Wed 12-Feb-2020 20:00 (08:00 PM)
Amsterdam Wed 12-Feb-2020 21:00 (09:00 PM)
Moscow Wed 12-Feb-2020 23:00 (11:00 PM)
Chennai Thu 13-Feb-2020 01:30 (01:30 AM)
Hangzhou Thu 13-Feb-2020 04:00 (04:00 AM)
Tokyo Thu 13-Feb-2020 05:00 (05:00 AM)
Sydney Thu 13-Feb-2020 07:00 (07: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-02-12&iso=20200212T20
  • or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Feb+12%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

  • src: remove duplicate env field from CryptoJob #31588
  • doc: add example for cipher.update() #28373

nodejs/TSC

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

nodejs/admin

  • Node.js Social Media Accounts #454

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)
  • Jeremiah Senkpiel @Fishrock123 (TSC)
  • Gabriel Schulhof @gabrielschulhof (TSC)
  • Gireesh Punathil @gireeshpunathil (TSC)
  • James Snell @jasnell (TSC)
  • Joyee Cheung @joyeecheung (TSC)
  • Matteo Collina @mcollina (TSC)
  • Michael Dawson @mhdawson (TSC)
  • Myles Borins @MylesBorins (TSC)
  • Sam Roberts @sam-github (TSC)
  • Michaël Zasso @targos (TSC)
  • Sakthipriyan Vairamani @thefourtheye (TSC)
  • Tobias Nießen @tniessen (TSC)
  • Rich Trott @Trott (TSC)

Observers/Guests

  • Ruben Bridgewater @BridgeAR

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

closed time in 6 days

mhdawson

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-02-12

Closing

mhdawson

comment created time in 6 days

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-02-12

Given that we have open as well around looking at meeting times: https://github.com/nodejs/TSC/issues/809.

can everybody update their availability in the spreadsheet (I'll send out link via email) and then we'll review the meeting times.

mhdawson

comment created time in 6 days

issue commentnodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2020-02-12

There is a conflict with the modules meeting. Normally I would have caught it and switched in advance but just got back today.

Looking at the agenda for today I don't see anything urgent so unless there are objections lets just cancel for this week.

Any objections?

Sorry for the late notice.

mhdawson

comment created time in 6 days

push eventmhdawson/io.js

Michael Dawson

commit sha 7f8ddeba4c3b0adef9e7d8c8656740024aea499a

Update doc/guides/investigating_native_memory_leak.md Co-Authored-By: Denys Otrishko <shishugi@gmail.com>

view details

push time in 6 days

push eventnodejs/create-node-meeting-artifacts

Richard Lau

commit sha 02595e6621f9627b7d45edd6ba04513382ffc1cf

template: add Ruben Bridgewater to TSC observers (#83)

view details

push time in 6 days

PR merged nodejs/create-node-meeting-artifacts

template: add Ruben Bridgewater to TSC observers

Refs: https://github.com/nodejs/TSC/issues/811 Refs: https://github.com/nodejs/TSC/pull/814

+1 -1

1 comment

1 changed file

richardlau

pr closed time in 6 days

issue openednodejs/outreach

Node.js Foundation Outreach Meeting 2020-02-18

Time

UTC Tue 18-Feb-2020 17:00 (05:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Outreach+Meeting+2020-02-18&iso=20200218T17
  • or http://www.wolframalpha.com/input/?i=05PM+UTC%2C+Feb+18%2C+2020+in+local+time

Links

Agenda

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

Invited

  • Outreach Members: @nodejs/outreach

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 outreach-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/526318636
  • For those who just want to watch: https://www.youtube.com/nodejs-foundation

created time in 6 days

issue openednodejs/benchmarking

Node.js Foundation Benchmarking WorkGroup Meeting 2020-02-18

Time

UTC Tue 18-Feb-2020 20:00 (08:00 PM):

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

Or in your local time:

  • http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Benchmarking%20WorkGroup+Meeting+2020-02-18&iso=20200218T20
  • or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Feb+18%2C+2020+in+local+time

Links

Agenda

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

nodejs/benchmarking

  • Investigate the time taken, and number of benchmarks in core #225

Invited

  • Benchmarking team: @nodejs/benchmarking

Observers/Guests

Notes

The agenda comes from issues labelled with benchmarking-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/345481302
  • 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 6 days

more