3 ms·
Wow, I am surprised we haven't seen one of these[1] sooner. Also surprised they got advice from counsel that they might be able to prevail here. From the blurb
by ChuckMcM 13y ago
Wow, I am surprised we haven't seen one of these[1] sooner. Also surprised they got advice from counsel that they might be able to prevail here. From the blurb in the Times it seems pretty cut and dried. And if the unit really does make nearly half a billion dollars a year, it seems like throwing a few million over the fence in licensing fees wouldn't be a huge burden. Of course, it could be a bit more predatory than that, and RBS has been scrambling like mad to replace this chunk while their lawyers fight a delaying action in the courts.
[1] Major Corp getting screwed because some tricky licensing provision in their tech stack bites them in the backside.
- jamesaguilar 13y agoIt doesn't seem that tricky to me. You have to have a license to use the software. You sell the portion of your org that owns the license, you need to buy another one to continue using the software.
- rayiner 13y agoThe takeover was hostile, and the sale happened in a rush because the target was hoping that divesting LaSalle Bank would make it a less attractive buy: http://www.washingtonpost.com/wp-dyn/content/article/2007/07/13/AR2007071300249.html http://www.washingtonpost.com/wp-dyn/content/article/2007/07....
- ChuckMcM 13y agoThat isn't the tricky bit, generally you have a large organization, it has many moving parts, and general staff turnover. At some point there are parts of the system that "just work" and nobody at the place really knows all the various bits that go into the works. When one of those bits is carrying a license that needs to be paid, negotiated, but you don't know it, it bites you in the backside. A more common example of this is a hard working engineer who, practicing DRY, finds a perfectly serviceable piece of code on Github which he plugs into the source tree with just a few small changes to hook up the plumbing. Never once checking the license terms. Those things blow up when you get a demand letter from the owner of the code. Most shops though have a license compliance officer type person who is checking for such things.
- cube13 13y agoIf it's a core part of your technology strategy, as RBS/ABN say it is, then your legal people need to make sure that you don't accidentally sell it away. The problem seems to stem(from a ruling last year linked here: https://news.ycombinator.com/item?id=7722956 https://news.ycombinator.com/item?id=7722956) from the fact that ANB didn't actually specify that the license was staying with it instead of getting sold as a packaged part of one of their subsidiaries. For a core tech requirement, that's amazingly idiotic, no matter what size organization you're in.
- jamesaguilar 13y agoMaybe it's just me, but I'd never even think of doing that. The place I work for has a group responsible for third party licensing and stuff like that. It seems pretty foolish -- maybe even negligent -- to just grab shit off GitHub and stick it in your source tree.