Transfer DataDog/import-in-the-middle to the org

[bengl]

Several years ago, we (Datadog) created import-in-the-middle. Modeled after require-in-the-middle, it provides a simple layer for intercepting module loading using roughly the same API as require-in-the-middle, but for ESM, using Node.js loaders. It also manages differences in the loader API across Node.js versions, since our users use a wide range of Node.js versions with ESM.

The project has been a resounding success, and is now in use by several other organizations in the APM space, such as Elastic, NewRelic and OpenTelemetry. As a result, these other groups have submitted PRs, and been helpful in collaborating. At this point, we'd like to open it up even further, handing over governance of the project to a wider group, to ensure that Datadog is not a blocker for releases or maintenance.

Rather than form a separate entity/org to own this, we think that the Node.js org is an ideal place for this library to live. To that end, we're requesting a transfer from the DataDog GitHub org to the nodejs GitHub org, with governance by the TSC, but delegated to the Diagnostics WG. This governance structure aligns with other projects in this GitHub org.

Anticipated Questions

• Why this org and not another one, like OpenTelemetry?
  • The Node.js project already shows a commitment to observability, and while OpenTelemetry might seem like another good home, we think import-in-the-middle is much lower-level than OpenTelemetry (in much the same way diagnostics_channel is), and has use cases outside of OpenTelemetry's scope.
• Why this org and not a higher-level scope, like OpenJSF?
  • We think that the correct scope for import-in-the-middle is Node.js, since the library can only be used with Node.js, and exists only in that ecosystem.
• Why the Diagnostics WG?
  • There's already a lot of overlap between the Diagnostics WG and the set of stakeholders in import-in-the-middle. Primarily this means APM vendors. That said, if desired, a new team could be formed specifically for maintenance of import-in-the-middle, initially composed of its most frequent comitters. This team could also be under the Diagnostics WG's purvey.

[bengl]

cc @nodejs/tsc

[mcollina]

SGTM

[ShogunPanda]

SGTM

[mhdawson]

SGTM

[richardlau]

+1

[BridgeAR]

SGTM

[Qard]

@bengl What remains to be done here? Can we press the button now?

[anonrig]

@bengl Can you initiate the transfer to the Node.js organization?

[bengl]

We're happy to transfer it, so long as the receiving party (@nodejs/tsc, or more likely @nodejs/diagnostics?) indicates that it is prepared to maintain it.

[anonrig]

I'm interested in maintaining it.

cc @nodejs/tsc wdyt?

[Qard]

As a representative of @nodejs/diagnostics I think we're good with owning that, but of course contributors need to exist for maintenance to happen.

[tony-go]

+1 :)

Also interested in maintaining it 💪🏼

[jsumners-nr]

On behalf of the Node.js agent team at New Relic, I am willing to participate as a maintainer.