4 ms·
While I respect the angst the author feels, this snippet ... "... allowing an entity like VMware to join, despite their many years long disrespect for the most
by ChuckMcM 10y ago
While I respect the angst the author feels, this snippet ... "... allowing an entity like VMware to join, despite their many years long disrespect for the most basic principles of the FOSS Community (such as: Following the GPL and its copyleft principle), really is hard to understand and accept."
I think this presumes a different rationale on the part of the Linux foundation. The answer to the question "Here is some money, can I join?" is always yes. And with enough money it is "heck yes!"
And that leads to "I guess I was being overly naive :("
Which is yes, you were.
Why do politicians, managers, and ex-lovers all have to just "put their differences aside and move on." ? Because if you don't you can't make any progress even if the penultimate step here was one that hurt you badly.
The best way to score this is that VMWare is going to participate in a forum with others who can help guide them to a better compliance record. Both to understand why compliance is good, and to alleviate fears that VMWare might have that complying would leave them vulnerable. What they were before is in the past, now you have a way to work with them to move forward. Consider the alternative that they don't join, they continue to be huge FOSS scofflaws and continue to provide some sort of 'you don't really have to comply' example to others who might be uncomfortable with the GPL. When you look at it this way, it really is a good thing.
- rrdharan 10y ago> alleviate fears that VMWare might have that complying would leave them vulnerable I don't think this is the case. VMware (and their lawyers) have studied the GPL and genuinely do not believe they are not complying with its requirements. This isn't the typical "shady hardware vendor embeds modified busybox" situation where the (in this case alleged) lack of compliance is out of laziness, fear or ignorance. [Disclaimer: as per my other comment, I used to work at VMware, and am inherently biased in that sense, although I also happen to agree with VMware on the whole ESXi/vmklinux situation.]
- paxcoder 10y agoI didn't study the busybox connection, but why would anyone think vmkernel and vmklinux could be "reasonably considered independent and separate works in themselves" especially considering the source from the sfconservancy site linked to in the article?
- rrdharan 10y agoI don't think anyone considers vmklinux independent, and indeed vmklinux is itself open-sourced (in a kludgey but compliant way): https://my.vmware.com/group/vmware/details?downloadGroup=ESXI650-OSS&productId=614 https://my.vmware.com/group/vmware/details?downloadGroup=ESX... The debate has always been about whether the vmkernel is itself a derived work of vmklinux or Linux.
- belorn 10y agoCan vmware replace the linux kernel and vmklinux, and still have a functioning vmkernel? Ie, for some definition of independence and separation, how independent are vmklinux and vmkernel, and how separated are they in function and use? Could one simply remove the linux parts and plug in a different unix like kernel? With two independent work I should be able to put them each on a different computer and have a meaningful result from doing so. Two work can have a cumulative effect when brought together, but independent they need to still be meaningful and working on their own. If I arbitrary separate a program, I can obviously not do so since they will not start, function proper or produce a meaningful effect on their own.
- deleted 10y ago[deleted]
- paxcoder 10y agoI asked why anyone would think that vmklinux (the linux derivative) and vmkernel were independent. Please refer to the quote from the license I've provided, and belorn's thought experiment here.
- monochromatic 10y ago> genuinely do not believe they are not complying with its requirements What's the basis for this position?
- rrdharan 10y agohttps://communities.vmware.com/message/726899#726899 https://communities.vmware.com/message/726899#726899 It's a little too long to copy/paste here, but read Zach Amsden's reply.
- cmurf 10y agoSometimes trust is simply broken, and until the other party unwinds some of the deeds leading to that loss of trust, at least to a degree that both sides are equally unhappy, there can be no new trust. Just moving on for the sake of moving on is also common in abusive relationships. So I think VMware needs to settle their lawsuit with Hellwig and the SFC.
- robert_foss 10y agoA willfully GPL non-compliant vendor joins an open source industry coalition. VMware has a long and inexcusable history of GPL violations. And that history has not yet seen an end, it continues to this day. Of course there is something wrong with this.