Post

A lot of open-source projects don't fail over time because the idea was bad. They fail because maintaining them is a lonely journey, and finding a successor is incredibly difficult.

We saw this recently when the ngneat organization vanished from GitHub, leaving critical tools like ngneat/spectator missing from the Angular ecosystem. If we do not know why, when such a major project disappears overnight, the whole community feels the impact.

That’s why a group of Angular community members and I have teamed up to create a new GitHub organization dedicated to collective open-source governance and long-term maintenance. The GitHub Organization, OpenNG Foundation, is still empty.

0 reposts1 like

Our priority will be to fork and revive key, unmaintained Angular projects to ensure they stay secure, updated, and community-driven.

I was about to DM you. I'll work on defining the mission over the weekend. On some aspects, we'll be quite close to OpenJS mission (except the web standards part obviously). The goal is not to take over the whole Angular OSS ecosystem but to help where it is needed:

A rescue foundation should preserve its own exit path too: mirrored repositories, transferable credentials, maintainer succession, funding visibility, and a procedure for contested forks. If OpenNG vanished tomorrow, which asset would let the community continue without asking permission?