[TSC] Adopt OpenJS's ESP (Ecosystem Sustainability Program)

[ovflowd]

As members of the OpenJS Foundation, we're covered on OpenJS's ESP program. Under the ESP program we could defer maintenance of our EoL versions (such as Webpack 4) and in the near future Webpack 5 once Webpack 6 releases, to our ESP partner, HeroDevs.

This would remove the burden on us for providing critical security patches to EoL versions and keep them running/alive for an indefinite amount of time through HeroDev's (https://herodevs.com) NES program (Never-Ending-Support)

This would also share the revenue from contracts closed by HeroDevs for Webpack 4/Webpack 5 EoL support directly to us. Allowing us to have extra resources to allocate on the critical work of maintaining our current active release lines.

OpenJS's Board of Directors member Jordan Harband (@ljharb) can provide more details and help us making this happen in case we're interested on it.

[ovflowd]

cc @webpack/tsc

[ljharb]

Due to the existing OpenJS partnership, what I'd recommend y'all do to maximize ESP potential is the following:

• explicitly list version support status (iow, a "Version Support" page that lists release lines, and indicates their support status, and end dates if applicable)
• link, as prominently as possible, to a list of third-party support options, of which HeroDevs would merely be one of the options (assuming more companies join in the future)

Telegraphing a release date for Webpack 6 in advance would be very helpful to the community, as would explicitly declaring an EOL date for Webpack 5.

[evenstensberg]

Let's bring up the roadmapping to v6 in next tsc meeting.

[evenstensberg]

Question: Can we include this issue to be with the codemod issue?