2 ms·
That assumes a monolithic design style, I think. There are a lot of projects that are factored into small pieces with separate maintainership, where the projec
by derefr 7y ago
That assumes a monolithic design style, I think.
There are a lot of projects that are factored into small pieces with separate maintainership, where the project as a whole—or its "core"—might be corporate-sponsored; yet individual parts/plugins/connectors—including fairly-critical ones!—might turn out to be one person's hobby-project.
How many maintainers do you think the average Kafka connector has? The average Postgres extension? The average Redis or Nginx module? Etc.
These ecosystem components move the project-as-a-whole forward, and yet they don't necessarily need to be as "corporate" as the project-as-a-whole does to accomplish that. Even though, in the end, a corporation might use one of them, it won't really matter as long as nobody sees them doing so. (If they ever need to patch the un-corporate extension, though, they'll probably fork the thing and flense out all references to the original. I've seen that happen a lot, and done it a few times myself.)