Heck, IBM could probably put together their own internal release of mitmproxy today if they cared that much.
Heck, IBM could probably put together their own internal release of mitmproxy today if they cared that much.
Seriously though, I am kind of curious why IBM can't cough up cash. I'm guessing it takes a while to set up a vendor in their system. So they probably //could// pay for a support contract, but by the time they set it up they'll have blown through some internal deadline. Or maybe this request is being made from a lower level person and someone in their reporting chain has blocked the idea of setting up a support contract.
My memory of IBM is they're pretty insular, the particular person involved could just not understand what open source is. For instance, I was hired into a team in Boca Raton in the late 80s because my resume said I had experience with multiple Virtual Machines (VMs). I actually had experience with VMS, which was an operating system from Digital Equipment Corporation. When I asked my boss about that, her response was "What's VMS? What's Digital Equipment Corporation?" Which was a very strange thing to say as they had (more than) decimated IBM's S/36 and S/38 sales. Later on when I worked for the AIX division, I found many people who were clueful.
I think what I'm saying is:
1. IBM is a big company. It's probably not accurate to judge the whole organization from one person's interaction.
2. You can survive at IBM without understanding the outside world. (though I'm just extrapolating that assertion from what I saw in the 80s,90s and late 2000s.)
They could, and so could I, and most people here if they wanted to. That doesn't mean it's an unreasonable question to ask. If anything it's exactly the sort of question you would ask if you planned to make your own release, so you know if it's going to be worth the effort.
> The initial question was polite and reasonable, as was @mhils's response.
Some people in this thread didn’t read that far, and now seem to be to twisting reality to defend their judgement.
Not being a logged in Twitter user, the remainder of the thread is hidden to me.
> 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. In reviewing the project's official documentation...