You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.
New Collaborator @puzpuzpuz would like to be on the correct team for the benchmarks in Node.js core. It's not clear to me if @nodejs/benchmarking is the right group or not. Is it safe for me to go ahead and add them to @nodejs/benchmarking or does the Benchmarking Workgroup (is it still active?) have a different process?
The WG is being de-charteted (nodejs/TSC#822) which is why I didn't add my name to the readme. But the GitHub team will be kept for notifications, so +1 on adding @puzpuzpuz to it.
New Collaborator @puzpuzpuz would like to be on the correct team for the benchmarks in Node.js core. It's not clear to me if @nodejs/benchmarking is the right group or not. Is it safe for me to go ahead and add them to @nodejs/benchmarking or does the Benchmarking Workgroup (is it still active?) have a different process?
/cc @addaleax
The text was updated successfully, but these errors were encountered: