Gregory's ServerNothing will destroy Open Source quicker than treating all the devs who work on open source software as suppliers in a supply chain.
 6 comments
@ddr @ramsey It's not always so easy. The patches WERE toward a goal we already had (support for next PHP version). But the outsourced devs were largely unresponsive, and in some cases shared an account, which made communication difficult. In many cases, we ended up closing the request and authoring new ones. But reviewing meant we lost time we could have spent elsewhere. That's another issue with the "supply chain" mentality - while we can ignore requests, we still spend time evaluating. @ramsey @mwop @ddr traditional outsourcing devs that were mostly bashing their keyboard without any thinking. Turns out that it's easier for the big corporate user of the OSS project to burn money on outsourcing consulting "registered vendors" than to actually pay the maintainers, probably due to internal bureaucracy. |
@ramsey So, a large company I won't name but which now owns a commercial OSS product that builds on top of Laminas libraries... each year asks us when we will support PHP.next, demanding we be ready by release.
They're treating us as suppliers. And due to "legal issues", never even donate monetarily to the project.
This year, they outsourced patches to help the migration... To a team with 0 history with us, creating patches that broke CI. So, more work for us in the end.
It's untenable.
@ramsey So, a large company I won't name but which now owns a commercial OSS product that builds on top of Laminas libraries... each year asks us when we will support PHP.next, demanding we be ready by release.
They're treating us as suppliers. And due to "legal issues", never even donate monetarily to the project.