-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer elastic/require-in-the-middle to the org #890
Comments
SGTM. 👍🏻 |
+1 |
I would be interested in helping maintain! Aside from the open issues are there any areas that |
Thanks for opening this issue @trentm. I'd love to help maintain the module under the Node.js org |
I'm also happy to help out with this one. 🙂 |
I would be interested in helping maintain too! |
+1 from me in terms of the transfer |
This is open for three weeks. I'm reaching out to @trentm to finalize this. |
Still in the middle of internal process. |
Following on import-in-the-middle (IITM) being transferred to the nodejs org and discussion in today's Diagnostics WG meeting, this is a request to also move require-in-the-middle (RITM) from the Elastic org to the Node.js org. As with import-in-the-middle, this would be governed by the TSC, but delegated to the Diagnostics WG. The expectation is that there would be significant overlap in the maintainers of IITM and RITM.
require-in-the-middle
is a fairly mature library for intercepting CommonJS module loading viarequire(...)
. It is widely used in the Observability/APM space -- OpenTelemetry, Elastic, Datadog (though I think they currently have a small fork), New Relic. Reasoning for wanting to donate this to a vendor-neutral org are the same as described for IITM./cc @nodejs/tsc @nodejs/diagnostics
Others, please indicate if you'd be interested in maintaining RITM.
The text was updated successfully, but these errors were encountered: