"We kindly request your response by Friday, July 25, 2025"
...
@otto @serpentroots @christopherkunz @bagder @musevg It doesn't sound like they're sending an "or else" here; they have a lot of "kindlies" in there. On the off chance someone is willing to do work for them (and anyone else who might ask similar questions) for free, maybe they get an answer. And open-source maintainers aren't known for *not* making free stuff for people.
Nobody *has* to do free support. But if these questions are frequently asked, they could go in the project FAQs.
@bagder I find that, for tight deadlines, a short email is often the quickest to both write and read.
"no" is the shortest that has meaning 😀
"Thank you for your support inquiry. Please contact our business office at ___ . I am confident we will be able to negotiate a mutually agreeable contract for priority service. Please note that priority service contracts start at $1M."
@bagder I'm most interested in what the table actually is, as are many other people for that matter, because it could inform people of what to expect + prepare boilerplate responses.
Also, for a laugh, it'd allow me to see how quickly an LLM could be prepared to reply...
@bagder They don’t seem to have that option (to stop using curl) is what I mean. After all curl is everywhere…
Which makes their negotiating position rather weak. And any “deadlines” their problem. Have fun!
@bagder wow, they outright refer to you as a "vendor"?
There are so many good ways to answer this. From a simple "no" to a starting a contract wild Goose chase.
I hope you have fun with whatever option you choose.
I got one quite similar last week.
I sent them a formal Time&Material quote from my company.
No response so far.
@bsdphk I hope you quoted high enough to make it worth your while, in the unlikely event that they decide to pay you.
The cheek on these people.
Reading through your posts about CRA, I think there is a chance for a CRUde awakening for these companies.
A reality check even, about how open source actually works. Including having to read the licenses and realizing they use it, for free, on their own risk.
Leaving the eat the risk, get a support contract or stop using.
So after the initial drama, this could be a good thing for open source in the long run.
What happens if you send them an email clearly stating you do none of those things and that curl is just the hobby of some guy that has no business providing a service to a billion people? Will the company have to stop using curl?
@zaffojj @guenther @bagder @KevinOfComputer So it's SOUP. "Software of unknown providence."
This is standard shit for a regulated company. All they have to do is take on the responsibilities they're pushing onto the OP. With an OS project it's pretty easy. You go through the tickets and decide what does and doesn't effect your product. Then you accept the responsibility of taking on bug reports from YOUR customers and dealing with them.
You fork and watch. That's it. It becomes "yours".
@bagder "very dear sirs: I am not selling this software, so I am not a vendor. Have a good day."
Vendor: person or company offering something for sale. From lat. vendere (to sell).
@bagder
I may have suggested the wrong approach:
"Sure, that will be consulting work at xx€/hour, billed in advance in increments of 2h".
And that would be fair.