Corporate User Accuses Open Source Maintainer of Extortion
Description
A screenshot of an email sent from a user with a '@us.ibm.com' address to 'Mr. Hils', an open-source maintainer. The email subject is 'Concerning response'. The sender states they are writing to avoid polluting the GitHub issue tracker and hopes their follow-up isn't offensive. The most critical part of the email is highlighted in yellow: 'I'm assuming your response to my request for the next mitmproxy target date was a joke rather than an official project response or, worse, a thinly veiled extortion attempt.' This image is the third part of a story where a corporate user demanded a release timeline for compliance reasons, the maintainer offered a paid support contract, and the user has now escalated the situation via email, completely misinterpreting the offer of paid support as 'extortion.' It's a stark example of the culture clash between the transactional expectations of large enterprises and the community-driven, often voluntary, nature of open-source software development
Comments
7Comment deleted
In the corporate dictionary, 'extortion' is apparently a synonym for 'an unexpected item that requires a new purchase order'
Enterprise email: “Your ‘when it’s ready’ roadmap feels like a thinly veiled extortion attempt.” Maintainer: “Says the guy shipping my weekend project to prod behind a 40-page MSA and a $0 support contract.”
IBM employee discovers the one pricing model their company didn't invent: asking to be paid for your time before someone wastes it
When your enterprise stakeholder mistakes 'we'll get to it when we get to it' for extortion, you know they've never experienced the true joy of maintaining an open source project with zero SLA guarantees. Nothing says 'I understand OSS culture' quite like threatening legal language over a release timeline question - clearly someone's KPIs depend on a roadmap that doesn't exist outside their Gantt chart
"Thinly veiled extortion" or just indie maintainer hinting at sponsor tiers to fund the next sprint? OSS economics in a nutshell
Enterprise rule of thumb: if you want a date from a volunteer OSS maintainer, that’s called a purchase order - not a 11:56 PM reply‑all; CAP can’t give you Consistency, Availability, and a free SLA
Enterprise OSS strategy in one email: demand a mitmproxy release date at 11:56 PM and call sponsorship “extortion” - that’s not extortion, it’s an SLA without a PO when your vendor is a README