Who Controls Vert.x: Red Hat, VMware, Neither?

← Back to Stories (view on slashdot.org)

Who Controls Vert.x: Red Hat, VMware, Neither?

Posted by Soulskill on Saturday January 12, 2013 @07:47AM from the reply-hazy-try-again dept.

snydeq writes "Simon Phipps sheds light on a fight for control over Vert.x, an open source project for scalable Web development that 'seems immunized to corporate control.' 'Vert.x is an asynchronous, event-driven open source framework running on the JVM. It supports the most popular Web programming languages, including Java, JavaScript, Groovy, Ruby, and Python. It's getting lots of attention, though not necessarily for the right reasons. A developer by the name of Tim Fox, who worked at VMware until recently, led the Vert.x project — before VMware's lawyers forced him to hand over the Vert.x domain, blog, and Google Group. Ironically, the publicity around this action has helped introduce a great technology with an important future to the world. The dustup also illustrates how corporate politics works in the age of open source: As corporate giants grasp for control, community foresight ensures the open development of innovative technology carries on.'"

118 comments

Min score:

Reason:

Sort:

Does not support PHP by Anonymous Coward · 2013-01-12 07:56 · Score: 1, Informative

Funny how they support "the most popular languages", except for the one everyone actually uses. I think they meant "corporate", not popular.
1. Re:Does not support PHP by Anonymous Coward · 2013-01-12 08:03 · Score: 0
  
  I was thinking the same. That, and Perl.
  To be fair, PHP is unbelievably god-awful, so good for them. I guess a case can be made that it's not so much a "Web programming languages" as it is a "digital trainwreck".
2. Re:Does not support PHP by Anonymous Coward · 2013-01-12 08:38 · Score: 0
  
  To be fair, PHP is unbelievably god-awful, so good for them.
  And yet Javascript is a good server side language?
  captcha: nonsense
3. Re:Does not support PHP by Zero__Kelvin · 2013-01-12 08:45 · Score: 2
  
  It also doesn't support COBOL.
  
  --
  Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
4. Re:Does not support PHP by Evardsson · 2013-01-12 09:10 · Score: 3, Informative
  
  That would probably be because the PHP-Java bridge is a kludge and horribly inefficient. Having had occasion to use the bridge for a non-trivial project, I am actually ok with this Java-based server not supporting it.
  
  That said, if you really want the headache, I am sure you can figure out a way to use the PHP-Java bridge to tie to your current PHP apps and use them as Java in the Vert.x server. I do have to say, though, I do pity anyone who has to do this.
  
  --
  Death looks every man in the face. All any man can do is look back and smile. - Marcus Aurelius
5. Re:Does not support PHP by Bitsy+Boffin · 2013-01-12 15:21 · Score: 1
  
  I was thinking the same. That, and Perl. To be fair, PHP is unbelievably god-awful, so good for them.
  Some would say the same about Perl. 99% of the time, it's not the language but the fellow using it that makes it bad. (Admittedly, even I get annoyed at some PHP peculiarities from time to time, then I remember, it's what keeps me fed, and move on.)
  
  --
  NZ Electronics Enthusiasts: Check out my Trade Me Listings
6. Re:Does not support PHP by foniksonik · 2013-01-12 15:54 · Score: 1
  
  All the devs I know switched from php years ago. Ruby and Node are the languages of choice to write web apps.
  
  --
  A fool throws a stone into a well and a thousand sages can not remove it.
7. Re:Does not support PHP by Anonymous Coward · 2013-01-13 01:42 · Score: 0
  
  There isn't a language that doesn't have some peculiarities. Every language out there was created for a reason, some languages doe one thing better others do another better.
8. Re:Does not support PHP by dynamo · 2013-01-13 05:51 · Score: 1
  
  Perl seconded! What the hell, they are supporting Groovy but not perl?
Java = bad by Anonymous Coward · 2013-01-12 08:00 · Score: 0, Insightful

end of this post
1. Re:Java = bad by Anonymous Coward · 2013-01-12 10:16 · Score: 0
  
  noob.
  end of this post.
Assumption is the mother of all fuckups by Shimbo · 2013-01-12 08:03 · Score: 4, Insightful

Moral: if you are working on a FOSS project, make sure you have disclaimers in writing from the company you work for. Double if you're the project lead.
1. Re:Assumption is the mother of all fuckups by fredprado · 2013-01-12 08:08 · Score: 4, Insightful
  
  Either way, if VMWare press the issue they will simply fork and go away, and VMWare will end as the leader of a deceased project.
2. Re:Assumption is the mother of all fuckups by unixisc · 2013-01-12 10:02 · Score: 1
  
  This is a great opportunity for a fork to give it a more meaningful name
3. Re:Assumption is the mother of all fuckups by Shimbo · 2013-01-12 10:08 · Score: 3, Insightful
  
  Either way, if VMWare press the issue they will simply fork and go away, and VMWare will end as the leader of a deceased project.
  It depends how hardball VMware want to play it. If they assert ownership of the code, and decline to release it under an open source licence then they can pretty much kill the fork as well. "Oh sorry, the code you thought was Apache licenced, sorry he had no right to do that - it's ours."
4. Re:Assumption is the mother of all fuckups by rtfa-troll · 2013-01-12 10:49 · Score: 3, Informative
  
  If they assert ownership of the code, and decline to release it under an open source licence then they can pretty much kill the fork as well.
  a) Fortunately not because VMWare and Red Hat have already made a posting otherwise.
  b) Fortunately not because this is a public project and has been explicitly and openly discussed by a number of people from VMWare over a long time. In general, companies are liable for the things their employees do as part of their work. Especially if they knew about it or should have known about it. The only comeback they have is disciplinary action against the employee. Judges sometimes come down really hard on companies which try to wriggle out of this kind of thing.
  c) Just think about it. If what you said was true, wouldn't Barings bank just have said "no; sorry, rogue trader; give us back our stolen dollars". Don't think the tech industry will manage tricks the financial industry has never thought of.
  
  --
  =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
5. Re:Assumption is the mother of all fuckups by Tough+Love · 2013-01-12 12:37 · Score: 1
  
  ... they can pretty much kill the fork as well. "Oh sorry, the code you thought was Apache licenced, sorry he had no right to do that - it's ours."
  Hah, I would like to see VMware try it. The code would be rewritten overnight and VMware would lose tons of karma, and probably some good employees as well. Not to mention the advice that would properly be given to prospective new hires: work for some less carnivorous company that might actually respect you and the community that allowed them to attain the lofty position they enjoy today.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
6. Re:Assumption is the mother of all fuckups by Tough+Love · 2013-01-12 12:40 · Score: 1
  
  if VMWare press the issue they will simply fork and go away, and VMWare will end as the leader of a deceased project.
  ...and end up with a big fat oozing purple bruise right in the middle of their hitherto respectable karma.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
7. Re:Assumption is the mother of all fuckups by Anonymous Coward · 2013-01-12 23:04 · Score: 0
  
  IANAL, but the same facts that VMWare would have to stipulate in order to claim the copyrights in the first place - i.e. that the developer was actually working as an employee of VMWare when he originated the project - might be sufficient to establish agency by estoppel such that his act of releasing under the Apache license would be binding on VMWare.
8. Re:Assumption is the mother of all fuckups by andyp · 2013-01-14 02:50 · Score: 1
  
  VMware and Red Hat jointly stated that the organisations wanted to work together and prefer a solution with an independent foundation (disclosure: I work on Open Source projects at VMware)
9. Re:Assumption is the mother of all fuckups by andyp · 2013-01-14 02:51 · Score: 1
  
  There's no intent that I have heard of to do this - in fact quite the opposite, see VMware and Red Hat joint statements in the vert.x Google Group
  (disclosure: I work on Open Source projects at VMware)
Unless it's it writing elsewhere.... by mark-t · 2013-01-12 08:09 · Score: 1

... his employer at the time that he wrote it has ownership.
This sort of situation just highlights the need for people to get a paper trail. It'd be ideal if a person's word was their bond and you shouldn't need them to sign something to agree to it, but alas.... we live in a notably less than ideal world.

--
File under 'M' for 'Manic ranting'
1. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 08:34 · Score: 4, Insightful
  
  His employer can't have the ownership of the project because he never had any ownership over it. The project is licensed under Apache. They could only forcibly take the governance, but then again the project can be forked at will, and VMWare will end with just a name if they force the issue. There is nothing VMWare can do about it other than concede or hostilize the community and force a Branch. Either way VMWare loses.
2. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-12 08:58 · Score: 1
  
  That it is licensed under an Apache license has no bearing on who owns the copyright. Since he was working for VMWare at the time it was written, VMWare would hold the copyright on it unless there is something *IN WRRITING* from VMWare that says otherwise.
  
  --
  File under 'M' for 'Manic ranting'
3. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 09:01 · Score: 0
  
  If he was working for them at the time he wrote it, then he probably couldn't legally open-source it without their permission.
  If he did that, then the legal status of every copy is in question. It's ultimately the copyright holder's decision.
4. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 09:15 · Score: 1
  
  It is incredible how people like to talk about what they have absolutely no clue about. It is absurd to think that because my employee worked for someone else, I own this person's business of even part of it. Unless the person explicitly signed a contract giving me ownership in exchange of this work.
  
  VMWare has no legal hold over the project. The project was founded as open source. They can even sue their employee for the time he used in a project whilst under their employment depending on the nature of their contract, but they hold absolutely no ownership or copyright on the project.
5. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 09:18 · Score: 1
  
  Sorry, but that is just false. Depending on the contract they have with the employee, they can claim ownership over anything he has ownership over. They can't claim ownership over something just because he sued his time on it. If I decide to wash your garden everyday for free, even with your consent or at your request, that does not give me claim over your house.
6. Re:Unless it's it writing elsewhere.... by forrestt · 2013-01-12 09:20 · Score: 1
  
  IANAL...He was their agent, and I believe that means that anything he did during the exercise of his duties they are responsible for. If they don't like his actions, they can dismiss him, but I don't think that has any bearing on the openness of the code.
7. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 09:28 · Score: 0
  
  they can claim ownership over anything he has ownership over.
  Of course they can claim anything. I doubt if knowing playing an employee to work on an open source project and then demanding that he "return" it to them is enforceable at all.
  VMWare is coming off like idiots here that don't understand forking.
8. Re:Unless it's it writing elsewhere.... by angel'o'sphere · 2013-01-12 09:53 · Score: 1, Flamebait
  
  It is absurd to think that because my employee worked for someone else, I own this person's business of even part of it. Unless the person explicitly signed a contract giving me ownership in exchange of this work. This is exactly what in most work contracts is written. Why? Because it is defined by law so! By repeating it again in the contract the employee should be aware of this. Ofc, at least in germany, you can write the exact opposite into the contract. But if you don't mention it at all, ALL WORK you do, REGARDLESS of on the job or AT YOUR SPARE TIME belongs to the EMPLOYER. And as germany copied this particular part of law from the USA I would really wonder if it is there different.
  
  --
  Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
9. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-12 09:59 · Score: 1
  
  If he wrote it while working for VMWare, then unless there is written proof that VMWare agreed to allow him to retain ownership, the project is VMWare's, period. It doesn't give them license to own part of another company, because the employee wouldn't have the right to bring the project to another company in the first place. If VMWare wanted to change the license on the project, as the lawful copyright holder, they could even do that.
  
  --
  File under 'M' for 'Manic ranting'
10. Re:Unless it's it writing elsewhere.... by unixisc · 2013-01-12 10:03 · Score: 1
  
  Or better yet, don't use any corporate resources in developing this. Do it on your own time, on your own computer which stays w/ ya once you quit the job, and the company has no claims whatsoever over what you did.
11. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 10:16 · Score: 1
  
  It is incredible how dense you can be. If you decide to build a house for me in my property, while employed in your current house building company the house is still mine in the end, unless I sign a contract with you or with your employer saying otherwise. He was never the owner of the project, never held the rights over the project, and so neither the company.
12. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 10:20 · Score: 1
  
  You fail to understand the situation. The contracts you mention gives right to the employer over anything that would otherwise be property of the employee while under its service. It can't possibly give to the employer property over something that is not owned by the employer, period. The employee having contributed with his time to a project does not give in anyway ownership of the project either to him or to his employer.
13. Re:Unless it's it writing elsewhere.... by quetwo · 2013-01-12 10:50 · Score: 1
  
  It all depends... If he was working on the project as a directive of his job at VMWare, then the project was done as a work-for-hire contract, and the copyright could belong to VMWare. If he was doing it in his free time, and VMWare simply used it, then it becomes muddier.
  If he had it in his contract that any IP generated by him while employed at VMWare, that could shift the copyright to VMWare. If his contract says they get an automatic license to any IP generated then he owns the copyright. If it is not in his contract at all, then it is for the courts to figure out -- but generally they would assume that he retains the rights for the IP.
  I just went through this with my employer and some contributions I made to Apache. I made my employer sign an agreement where I keep the rights to my own IP before I submitted anything to them (as required by the Apache by-laws).
14. Re:Unless it's it writing elsewhere.... by samkass · 2013-01-12 11:08 · Score: 1
  
  Unless they explicitly sign it over, everyone has copyright over any creative work they contribute (and coding is creative). However, most employers (in the US) require employees to sign a contract stipulating that the employer gets the copyright assigned to them automatically. If this developer ALSO signed over the copyright to the open source project, then he signed it away twice and it's up to the courts to decide which contract takes precedence.
  So VMWare probably has a reasonable legal claim to the copyright of any source written while under their employ, and can thus change the licensing terms at any time, and even claim that the previous license was never valid. Of course that's trying to close the barn door a little late, so as others have said as a practical matter it makes little sense for VMWare to go nuclear here. But calling people dense for making valid points is unhelpful.
  
  --
  E pluribus unum
15. Re:Unless it's it writing elsewhere.... by Deltaspectre · 2013-01-12 11:12 · Score: 2
  
  Unfortunately in the US at least, that's on a state by state basis, with the minority actually letting you separate work projects from out of work projects.
  List of states and relevant laws: http://answers.onstartups.com/a/20126
  
  --
  My UID is prime... is yours?
16. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 11:16 · Score: 2
  
  It would be nice if anyone RTFA before posting. The project is explicitly registered as a public domain project under Apache license. The only thing that is registered in the name of VMWare is the trademark, the name Vert.x, and that is all this, and the domains associated to it are everything they were able to claim, which you would know had you read the article.
  
  Actually they already decided to go and give the administrative control of the groups back to Tim Fox, but even after VMWare was forced to withdraw after stupidly trying to force their hand, it is not sure that the community will let them get away with it. The talk about forking is not over yet.
17. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 11:20 · Score: 0
  
  Not in California
18. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 11:21 · Score: 0
  
  If I decide to wash your garden everyday for free
  Why would anyone ever wash a garden?
19. Re:Unless it's it writing elsewhere.... by Billly+Gates · 2013-01-12 11:50 · Score: 1
  
  According to the law, VMWare owns the code he worked on in the office or on the clock. THe contract is for extra work off the clock.
  THe question is was it produced at work and especially if VMWare paid him to write it. If the answer is yes then any sane judge would side with VMWare. I believe since VMWare was part of the project that he was paid to write it. Contract or not it is their property.
  If I am wrong feel free to reply back. If he did this at home for example then yes, they can kiss his lawyers ass.
  
  --
  http://saveie6.com/
20. Re:Unless it's it writing elsewhere.... by Billly+Gates · 2013-01-12 11:56 · Score: 1
  
  I think you have it backwards.
  I think it is the gardener claiming he owns your plants because he planted them and provided care and did all teh work. But the law is on your side because he provided the labor on your property. It is owned by you! Same principle with VMWare.
  Of course we do not know all the details but what we do know is VMWare was part of the project, and this man worked for them at the same time. It seems to me that is highly likely he was paid to do it by VMware just on that evidence as VMWare was aware of it and kept paying him.
  
  --
  http://saveie6.com/
21. Re:Unless it's it writing elsewhere.... by fredprado · 2013-01-12 12:04 · Score: 1
  
  RTFA.
22. Re:Unless it's it writing elsewhere.... by Tough+Love · 2013-01-12 12:59 · Score: 1
  
  Look at it this way: those who live in glass houses should not throw stones. Suppose we suddenly all got interested in the question of whether ESX is really an original work, and not derived in any way from Linux source?
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
23. Re:Unless it's it writing elsewhere.... by Tough+Love · 2013-01-12 13:06 · Score: 1
  
  VMWare is coming off like idiots here that don't understand forking.
  ...and who also apparently do not understand PR, community relations, morality, gratitude or how to keep their fat hands in their collective pockets where they belong.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
24. Re:Unless it's it writing elsewhere.... by Fjandr · 2013-01-12 13:13 · Score: 2
  
  Whether WMWare owns copyright or not is irrelevant. VMWare was aware of, and consented to, the licensing terms the code was publicly released under. They can stop contributing new code, but they cannot remove the code already released. Their ownership interest going forward is 100% irrelevant.
25. Re:Unless it's it writing elsewhere.... by Tough+Love · 2013-01-12 13:15 · Score: 3, Interesting
  
  Or better yet, don't use any corporate resources in developing this. Do it on your own time, on your own computer which stays w/ ya once you quit the job, and the company has no claims whatsoever over what you did.
  Or carry on all your work in a highly public way (as in this case). If you do open source work on company time, as many do with the full knowledge of their manager and/or employer, then a thing called estoppel kicks in. That means, if you are doing public work and your employer knows about it but does not tell you to stop, or on the contrary, expresses approval, it means you have tacit agreement to carry on in the way that both you and your employer are presenting themselves to the world. Or in other words, if it walks like an open source project and quacks like an open source project, it's an open source project, and in absence of any specific agreement to the contrary, that cannot be undone at the whim of an employer.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
26. Re:Unless it's it writing elsewhere.... by Attila+Dimedici · 2013-01-12 13:44 · Score: 1
  
  Yes, there is a good chance that you are correct. However, if VMWare changed the license, that could only apply to the parts that were written by Tim Fox (or another VMWare employee) AND would not effect the license on copies that are already released. That is, they would be unable to revoke the Apache license on the project as it exists currently. Which means that someone (Tim Fox, now that he no longer works for VMWare) could fork the project.
  
  --
  The truth is that all men having power ought to be mistrusted. James Madison
27. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 16:50 · Score: 1
  
  The project is explicitly registered as a public domain project under Apache license.
  The terms "public domain" and "license" are mutually exclusive. If something is truly in the public domain, no license is needed to do whatever one wants to with it. However, I actually did RTFA, and nowhere did I see anything that indicated the project is public domain in any way, shape, or form.
28. Re:Unless it's it writing elsewhere.... by HJED · 2013-01-12 18:26 · Score: 1
  
  Only if he was working on it in his employers time or on his employers equipment, what he does in his personal time is his own private property. E.g. if I write a book whilst being employed by employer dosen't own the book.
  
  --
  null
29. Re:Unless it's it writing elsewhere.... by HJED · 2013-01-12 18:32 · Score: 1
  
  Depends if he did whilst he was "on the clock" or using his employers equipment, if he didn't then he would definatly retain ownership as it would be like someone writing a book, there employer dosen't get ownership. If he was doing it in his employers time or using their equipment it becomes murkey and if he was getting paid to do it then the copyright probably belongs to the employer.
  
  --
  null
30. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-12 20:01 · Score: 1
  
  The employee having contributed with his time to a project does not give in anyway ownership of the project either to him or to his employer.
  If the employer paid him for that project, it most certainly does, without written evidence to the contrary.
  
  --
  File under 'M' for 'Manic ranting'
31. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-12 20:07 · Score: 1
  
  Depends if he did whilst he was "on the clock" or using his employers equipment, if he didn't then he would definatly retain ownership
  No... not definitely. It depends largely on what state laws allows, and even then can depend on whether the employer has agreed to allow the employee to do work that could arguably compete with the employer.
  
  --
  File under 'M' for 'Manic ranting'
32. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-12 20:34 · Score: 1
  
  It can be an open source project, but the copyright still belongs to the company. Without written permission to show the contrary, the employee does not have any ownership of the projects he or she worked on while under their employ, nor authority to transfer ownership to anyone else.
  
  --
  File under 'M' for 'Manic ranting'
33. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-12 21:29 · Score: 0
  
  Fred,
  I am going to assume that you are not a lawyer (God help you if you are), and you haven't taken any serious jobs. First, it's law. Second, as angel said, even though it doesn't need to be specifically stated in an employment contract, it usually is anyway just so that an employee can't feign ignorance of the law.
  You may want to argue that this isn't how it should be, but that doesn't change the way it is. I'm not sure how it works in every field, but specifically, in the field of programming, ANY WORK done while you are under contract/employment is owned by your employer whether it is done at you place of work, at home, in your bathroom or anywhere else no matter if it was done before, during, after normal work hours, on a weekend, sick time, vacation, or holiday (actually, I'm not totally sure about on vacation, would have to double check with legal on that one) unless EXPLICITLY specified as an exclusion IN WRITING from your employer.
34. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-12 21:38 · Score: 1
  
  It would be nice if people who posted had a clue about what they were talking about before posting drivel. You are wrong. It doesn't matter what the license was. The license was invalid, and the employee had absolutely no right to distribute stuff under it.
  I can't walk into my office after hours, take all the furniture out of it, place it on the front lawn and have a garage sale. When the police stop by they aren't going to let people walk away with the stuff, they are going to grab it back and give it back to it's rightful owners. Just because I placed a sign on the stuff that said, "It can be yours for free, so long as you give it away when you are finished with it" doesn't change anything.
  In addition to not knowing employment law, I see you don't know anything about copyright law either since you said "The project is explicitly registered as a public domain project under Apache license", which makes absolutely no sense. BTW, I have a bridge to sell you for free for $5,000.
35. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-12 21:40 · Score: 1
  
  You are wrong. Keep posting garbage.
36. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-12 21:56 · Score: 0
  
  ANY WORK done while you are under contract/employment is owned by your employer whether it is done at you place of work, at home, in your bathroom or anywhere else no matter if it was done before, during, after normal work hours, on a weekend, sick time, vacation, or holiday (actually, I'm not totally sure about on vacation, would have to double check with legal on that one) unless EXPLICITLY specified as an exclusion IN WRITING from your employer.
  That's false. Unless you're in certain states in the USA where slavery has made a comeback.
  Does not apply in other countries or states.
37. Re:Unless it's it writing elsewhere.... by Tough+Love · 2013-01-12 23:19 · Score: 1
  
  It can be an open source project, but the copyright still belongs to the company. Without written permission to show the contrary, the employee does not have any ownership of the projects he or she worked on while under their employ, nor authority to transfer ownership to anyone else.
  That's just FUD. What matters is what the distribution license says, not who owns the copyright. Anyway, I don't think VMware will be stupid enough to argue about who owns the copyrights. In that direction lies a much worse bruising than they already got. Remember, VMware needs the community a lot more than the community needs VMware.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
38. Re:Unless it's it writing elsewhere.... by eric_herm · 2013-01-12 23:42 · Score: 1
  
  I am quite doubtful about the spare time part. Or then this would not be spare time anymore. If I work part time and contribute the other time to some project, you cannot at the same time pay me less and enjoy the benefit of a full time coder. There is the thing you do during your work, stuff you are being paid for and that ( depending on local laws and contract, cause that's not the same for all "creations" ), could ( and most of the time would ) be done for the company, so "belong" to the company. Then there is thing you do outside, and that's yours. People telling you otherwise just try to coerce into some kind of unfair practice, and put their own company at risk of someone suing them for that ( while most people wouldn't, I am pretty sure that some disgruntled ex worker would think of it sooner or later, that's just statistics, if you annoy enough people, your errors will soon become fatal ).
  Now, if you work full time on a side project during work hour without being instructed, you would be fired because you do not do your job, but that's all. If you work on a concurrent project, then this could be a problem of loyalty ( not sure if that's a offence in every country, not even how that is important in mine ).
  But asserting "you used the company laptop to work on a project in the evening so it belong to use" is likely not gonna fly. A laptop is not some specialized hardware nowadays. If you used the big cluster of the company, this may be problematic ( improper use of company resources ), but that's doesn't automatically translate to "all your base belong to us" ( especially in more specific case of writing papers, doing research, where I think this would be much more a grey area, even if from what I have seen, the various research institute have no problem paying someone for 3 years and letting him go do a patent and a company after based on the work he did ).
  And the idea of "I use something of the company so it belong to me" would not work, if I use my personal laptop to work on company project, that doesn't make me the owner of their code.
39. Re:Unless it's it writing elsewhere.... by angel'o'sphere · 2013-01-13 01:56 · Score: 1
  
  It is about intellectual property/copyright not whose laptop you use.
  A employer expects you to put all your effort into the work he pays you for. So none of your brilliant ideas you have at work are your own (look at patent law e.g.)
  So he does not want you to use your ideas to work "at home" ...
  the various research institute have no problem paying someone for 3 years and letting him go do a patent and a company after based on the work he did
  Depends if that institute has HIRD him or if he is a student there.
  That "they have no problem" does not mean, they have no right. Just read /. history postings about patent stuff, e.g. Lemple Ziff compression.
  especially in more specific case of writing papers, doing research, where I think this would be much more a grey area
  No there is no grey area at all. thee are laws that EXACTLY define how this is handeld.
  Sorry, if you are in the programming business I strongly suggest you get a very basic lesson about copyright law, ip laws and employment laws.
  Everything a laymen assumes is most of the time WRONG.
  
  --
  Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
40. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-13 04:14 · Score: 1
  
  First of all, who owns the copyright *ALWAYS* matters. The distribution license only states who has permission to copy the work. It does not override copyright.
  Secondly, VMWare already *ARE* stupid enough to argue about who owns copyrights. The vert.x project *DOES* belong to them. The author can, if he chooses, create a fork of the project and call it something else, although he should probably best do so quickly, before VMWare changes the license (although such a change would not be retroactive, it would still apply to the current release from that time forward, and given that they appear to be arguing about this anyways, it wouldn't surprise me if they did).
  
  --
  File under 'M' for 'Manic ranting'
41. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-13 04:21 · Score: 1
  
  Hmm.... yes. Good point. How much of it *was* written by Fox or other VMWare employees?
  Unfortunately, this experience will probably convince VMWare never to allow an employee to use open source license on a future project ever again.
  
  --
  File under 'M' for 'Manic ranting'
42. Re:Unless it's it writing elsewhere.... by Anonymous Coward · 2013-01-13 08:39 · Score: 0
  
  Dude, whoever signs a contract, where stuff he/she does on his/her spare time belongs to someone else is a fucking idiot!
43. Re:Unless it's it writing elsewhere.... by Genda · 2013-01-13 10:56 · Score: 1
  
  And if you look at the "Public Stupid Beating" that Oracle has received... they may own the copyright to a PUBLIC software which can (and will) BY LICENSE forked and begun ANEW... at a different place with a different name and the herd of public resources migrates there leaving, the copyright holder with a virtually empty bag of unfed ego. This is the magic that is open source. Once started its like gravitational collapse... it runs on its own steam and its damn hard to stop. It is in fact one of the best cures for corporate douche baggery. Truth is, I see Open Source as something of a pry bar, to break the whole corporate model apart. The beauty is that its not hostile to Corporate practices in the least, in fact Corporations understand that they need a uniform, reliable, robust infrastructure to succeed and the fact that they don't have to pay for it is simply awesome. They don't see the poison in the pill though, the magic coming in the form of people everywhere seeing the critical value of having globally accessible resources that all human beings need to function, and thrive, a growing meritocracy subsumes the existing profit model. Its stealth, subversive and very clandestine, but I think its the shape of the future and I love the fact that its quietly causing havoc with business as usual.
  Its time for the species to give up childish behavior and engineering a real social operating system that uses what works and discards what doesn't. I figure we're maybe a hundred years over due. The corporate model is a cancer doomed to failure, best it die now before it drags us all down with it.
44. Re:Unless it's it writing elsewhere.... by deKernel · 2013-01-13 11:39 · Score: 1
  
  Actually VMWare does possibly have a legal hold on the code base. The best instance of this if he worked on the code while getting paid by VMWare during normal business hours which more than likely stated in his work contract that anything did while working for them is owned by them.
  The one grey area would be is if he worked on it off-hours AND not using ANY VMWare equipment which was not covered in the article so at this point, everyone who thinks they know the answer is/could be wrong since all the pertinent details aren't know right now.
45. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-13 12:37 · Score: 1
  
  That's false. Unless you're in certain states in the USA where slavery has made a comeback.
  You mean unless you are in the United States, or any territory that US copyright law is enforced. For your reference:
  http://www.copyright.gov/circs/circ09.pdf
  Note that most "programmers" fall under works for hire. Also, the Supreme Court has ruled that
  
  Moreover, it held that supervision or control over creation of the work alone is not controlling.
  So works done that they haven't explicitly asked for, are indeed still covered by works for hire.
  Additionally,
  
  If a work is made for hire, the employer or other person
  for whom the work was prepared is the initial owner of the
  copyright unless both parties involved have signed a written
  agreement to the contrary.
  I can send you links to judgements from other courts that prove you wrong as well if you so like, but talking out of your ass won't help. Please link to either an official document, like from the copyright office as I did, or to Supreme Court rulings on the matter, otherwise, I'll assume this discussion is over.
46. Re:Unless it's it writing elsewhere.... by Tough+Love · 2013-01-13 16:10 · Score: 1
  
  Your blather continues to be FUD. VMware can change licenses all it wants (if it even can, some of the copyrights on the code may not belong to it) and the original, open sourced code will still be licensed the same way. Basic understanding of copyright and licensing seem to be absent on your part.
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
47. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-13 17:02 · Score: 1
  
  Yes, the author can fork any previous release if he wants to... (or the current one, as long as VMWare doesn't change the license). That doesn't mean he can just take the Vert.x project itself and move it to another company, however, which was all I was ever originally saying.
  And obviously, VMWare can't change the licensing on any code that wasn't written by its employees. Again, that doesn't invalidate any of what I was saying.
  
  --
  File under 'M' for 'Manic ranting'
48. Re:Unless it's it writing elsewhere.... by WNight · 2013-01-13 19:30 · Score: 1
  
  Sure, they own the work; and he freed the source on their behalf.
  How many devs would start using a non FOSS framework these days? The freeing of the project is why it's a success.
  They knew this and let it happen. They kept accepting patches (also under the APL), which they couldn't do without upholding the original offer. Otherwise the code their employee was taking wouldn't be usable by them.
49. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-14 02:46 · Score: 1
  
  Sure, they own the work; and he freed the source on their behalf.
  Copyright doesn't work like that. Only the owner has the right to do that. It isn't a chain like FOSS. Additionally, they have the right to revoke it at anytime even if they let it go for a while. Copyrights don't need to be protected unless you lose the right like for say a trademark.
  
  How many devs would start using a non FOSS framework these days? The freeing of the project is why it's a success.
  Two different issues here. The first, how many would? I'm going to assume you are in the FOSS bubble and haven't looked outside it. The vast majority are still under standard copyright, trademark, or patents -- not FOSS. While FOSS has made absolutely huge strides in both quality and popularity, it is still massively dwarfed still. Your typical FOSS language or platform doesn't even make the top 5 (could be top 10, but I don't remember all 10 from memory). Also, while perhaps interesting, this isn't relevant to who owns the rights to the code.
  Secondly, about why the project is a success, also not relevant to who owns the code.
  Lastly, about accepting patches... Well that might muddy the waters some, however, nothing prevents the company from exerting its right to the copyright able portions of the code base. Effectively killing the project unless rewritten. The FOSS project may be able to do the same. Close the source, claim it removed any offending patches and feel free to sue them if you can prove they didn't. But this is much more of a grey area, and while I do have a fair amount of knowledge about copyrights, trademarks, and patents, I am not a lawyer. Even if I was, I think it would be safe to say that it's up to the courts to decide.
50. Re:Unless it's it writing elsewhere.... by mark-t · 2013-01-14 03:41 · Score: 1
  
  I'm pretty sure if it's written for a system that you don't actually use at work, that would add a "preponderance of evidence" for the case that you didn't do any part of it at work.
  
  --
  File under 'M' for 'Manic ranting'
51. Re:Unless it's it writing elsewhere.... by WNight · 2013-01-14 15:51 · Score: 1
  
  Copyright doesn't work like that. Only the owner has the right to do that.
  And he's the company's agent. They knew of and accepted his actions.
  
  Additionally, they have the right to revoke it at anytime even if they let it go for a while.
  They can revoke an offer of a license at any time, yes. But if the code was released by them, and it was, they can't rescind the licenses of those who've received it. They merely don't lose rights for not acting quickly like with trademarks.
  
  Lastly, about accepting patches... Well that might muddy the waters some, however, nothing prevents the company from exerting its right to the copyright able portions of the code base.
  Accepting patches proves they intended the release under the Apache license, or the code they were given back wouldn't have been usable by them. If they hadn't meant to open-source the framework there'd have been some confused emails when they got contributions and they'd have straightened this out.
  It has to be this way, or they're using code they don't have a license to. If they don't want to go there they have to accept the validity of this grant.
  
  How many devs would start using a non FOSS framework these days? The freeing of the project is why it's a success.
  Two different issues here. The first, how many would? I'm going to assume you are in the FOSS bubble and haven't looked outside it.
  Sure, if your manager drops something on you... But people in those positions don't pick anything. And they certainly aren't contributing patches. To get open-source benefits you need to interest open-source devs and to interest them you need to offer them source.
  
  Secondly, about why the project is a success, also not relevant to who owns the code.
  It's their motivation.
52. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-14 16:49 · Score: 1
  
  Copyright doesn't work like that. Only the owner has the right to do that.
  And he's the company's agent. They knew of and accepted his actions.
  Yes, he's the company's agent. However, that doesn't mean he has the right or authority to do so. Claiming they knew of and accepted his actions isn't provable, and in many cases has been proven to not be effective in a court of law. There are so many things wrong with that in itself that in many cases, it isn't. Prove they knew it. Prove they accepted it. Prove they weren't consulting with legal for the past . Now prove that they knew of each and every contribution he made and they accepted each and every single one. If you can't do all of those, you've lost your case. I've seen court cases where it's even more cut and dry and has gone on for longer periods of time and yet, the courts have sided with the company. That is why you ALWAYS need to have it explicitly written down and approved before doing anything in your field outside of work or you risk losing the rights to the company.
  I've had this in every one of my employment contracts for the past 15 years, and it's saved my ass more than once.
53. Re:Unless it's it writing elsewhere.... by KingMotley · 2013-01-14 16:50 · Score: 1
  
  Yay for slashdot eating things that look like html ;-(
  That should have read "Prove they weren't consulting with legal for the past {timeframe}."
54. Re:Unless it's it writing elsewhere.... by WNight · 2013-01-14 19:34 · Score: 1
  
  You only read the first half of a message? Sheesh.
  Are you seriously claiming that the company *just* heard about the project? That nobody knew what was going on? If they knew of his dealings, as the company, and didn't act to correct them, and indeed went further to accepting patches predicated on these licensing terms, then they accepted it. If they didn't, what other arrangements have they made for the use of this third-party contributed code their project uses?
  This wasn't a leak it was a marketing move. And a successful one from the sound of it. But even if in retrospect they wish they'd done things differently, they didn't. Consequences. For everyone.
  Sorry, but a huge company that can deliver cross-platform products to international customers and paychecks to its employees can't claim such ignorance. And if they could it would be called negligence.
see also the recent openswan / libreswan by Anonymous Coward · 2013-01-12 08:13 · Score: 1

See also Paul Wouters' battle over openswan which ended up in a new fork libreswan.
Resignation from Openswan
Paul Wouters now also seems to work for Red Hat
Just uninstalled Java by gtirloni · 2013-01-12 08:20 · Score: 2, Funny

Sorry.

--
none
1. Re:Just uninstalled Java by Zero__Kelvin · 2013-01-12 09:07 · Score: 1, Offtopic
  
  I just uninstalled Japanese!
  
  --
  Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
2. Re:Just uninstalled Java by knarf · 2013-01-12 10:55 · Score: 1
  
  Why? While it is certainly a good idea to get rid of the JVM plugin to whatever browser you happen to be using I don't see the need to remove the JVM itself. Yes, there are bugs there, I know. That is why I don't run just anything I find on the 'net. Just like I don't run just anything I find on the 'net on my Linux machines or Android phones/tablets.
  
  --
  --frank[at]unternet.org
3. Re:Just uninstalled Java by Anonymous Coward · 2013-01-12 19:34 · Score: 0
  
  Still. Whenever the name of the thing starts with a capital J, I'm wary.
Java? by Anonymous Coward · 2013-01-12 08:30 · Score: 0

LOL!
Java = great by Anonymous Coward · 2013-01-12 08:33 · Score: 1, Interesting

Oracle = bad
Who Controls Vert.x by pushing-robot · 2013-01-12 09:01 · Score: 1

The Outer Limits?

--
How can I believe you when you tell me what I don't want to hear?
Nothing new under the Sun by nickmalthus · 2013-01-12 09:03 · Score: 4, Informative

There is precedence for this, it happened before with the Sun OpenDS and the Sun/Oracle Hudson Open Source projects. When the contest of ownership comes down to project developers and corporate lawyers the lawyers usually win the legal battle but the developers win the community battle due to forking.

--
If a nation expects to be ignorant and free, in a state of civilization, it expects what never was and never will be-T J
1. Re:Nothing new under the Sun by Tough+Love · 2013-01-12 12:30 · Score: 3, Funny
  
  So does that mean that VMWare will soon be bought by Oracle?
  
  --
  When all you have is a hammer, every problem starts to look like a thumb.
2. Re:Nothing new under the Sun by drinkypoo · 2013-01-12 14:03 · Score: 2, Informative
  
  So does that mean that VMWare will soon be bought by Oracle?
  No, anything but that. VMware works.
  
  --
  "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
3. Re:Nothing new under the Sun by eric_herm · 2013-01-12 23:53 · Score: 1
  
  yeah and they are much more innovative that Oracle *cough* paying for virtual memory *cough*
4. Re:Nothing new under the Sun by Stu101 · 2013-01-13 00:12 · Score: 1
  
  Dude, keep up with the times. The VRAM tax no longer exists. VMWare themselves admitted it was a bum move and backtracked.
  
  --
  http://www.writeitfor.us - Writing IT for the IT generation.
GPL license by sourcerror · 2013-01-12 09:38 · Score: 1

Suddenly the GPL license doesn't seem that bad after all.
1. Re:GPL license by angel'o'sphere · 2013-01-12 09:54 · Score: 1
  
  It does not matter which license you choose.
  In the end it comes down to the question: did the developer (employee) had any right at all to publish it 8under what license whatsoever).
  
  --
  Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
What is Vert.x? by loufoque · 2013-01-12 10:03 · Score: 1

What the fuck is Vert.x and why should I care about it?
1. Re:What is Vert.x? by loufoque · 2013-01-12 10:20 · Score: 2
  
  From a quick look, it seems to be some FastCGI-like API with bindings for various programming languages.
  You couldn't deduce that at all from the summary.
2. Re:What is Vert.x? by Anonymous Coward · 2013-01-12 10:20 · Score: 0
  
  you shouldn't its nothing of worth
3. Re:What is Vert.x? by segfault_0 · 2013-01-12 14:59 · Score: 1
  
  It's just an event driven application architecture that uses asynchronous I/O to provide efficiency. It incorporates technologies like Netty and Hazelcast to provide extremely simple, highly-concurrent applications that can handle lots of connections - so its good for building services, i.e http services.
  Anyone who tells you it's not worth much doesn't know their head from a hole in ground. It's a JVM based take on an idea whose time has come. You should check out the background on Node.js to see what all the talk is about.
  
  --
  
  I was crazy back when being crazy really meant something. (Charles Manson)
du wuht? by sgt+scrub · 2013-01-12 10:23 · Score: 1, Funny

A web framework based on Java? Isn't that kind of like a network appliance based on Windows?

--
Having to work for a living is the root of all evil.
1. Re:du wuht? by Anonymous Coward · 2013-01-12 11:43 · Score: 0
  
  In practical terms, there's nothing out there BUT web frameworks based on Java. The sad part is how clueless Slashdot has become (my sarcastic comment below actually got to +1 which has never happened before). Oh well. At least Slashdot crowd never does intersect with real life software development.
2. Re:du wuht? by Anonymous Coward · 2013-01-12 13:35 · Score: 0
  
  A web framework based on Java? Isn't that kind of like a network appliance based on Windows?
  Finding a Java web framework would be like finding a network appliance based on Linux...
  Hey moderators, if you don't have any experience with IT, GTFO this page, seriously.
Don't you read the news? by Anonymous Coward · 2013-01-12 10:43 · Score: 0, Informative

It's Java-based and should be banned by every user considering themselves half computer literate.
1. Re:Don't you read the news? by segfault_0 · 2013-01-12 15:02 · Score: 2
  
  Why don't you enlighten us with your literacy and tell us why the JVM isn't one of the most influential and important software inventions in the past 20 years. I'd personally love to hear your reasoning (read: i think you're full of shit).
  
  --
  
  I was crazy back when being crazy really meant something. (Charles Manson)
2. Re:Don't you read the news? by Anonymous Coward · 2013-01-12 16:59 · Score: 0
  
  [whoosh]
3. Re:Don't you read the news? by HJED · 2013-01-12 18:41 · Score: 1
  
  About the browser plugin yeah, but it sounds like you only read the headlines.
  That "0-day" only applies to java applets running in browser plugins (and in my experience are generally slow and buggy), not to jave programs especially ones running vertified code on servers.
  
  --
  null
4. Re:Don't you read the news? by Anonymous Coward · 2013-01-13 18:58 · Score: 0
  
  well it depends on perspective, eh? from Apple's perspective, what would the answer be? from Microsofts persecutive, what would the answer be? excluding Android, from Google's perspective, what would the answer be? from Sun's perspective, specifically from a financial perspective, what would the answer be? from Intel, Nvidia, AMD, Cisco, ARM, TI, MIPS, Facebook... what would the answer be? How about from this perspective http://www.paulgraham.com/pypar.html -- oh lighten up Alice!
Lol @ the hate for java by Anonymous Coward · 2013-01-12 11:54 · Score: 0

Java is inherently secure, despite recent press, which mostly centers around desktop browser plugins.
A lot of huge web sites run nothing but java.
who controls what gets committed and released? by gl4ss · 2013-01-12 12:04 · Score: 1

there's your answer right there.
so who controls the repo considered official?
so if vmware controls the website they control it. doesn't mean they can keep anyone else from releasing a version and publishing on a less hipstery domain than .io..

--
world was created 5 seconds before this post as it is.
Runs atop the jvm by Anonymous Coward · 2013-01-12 20:32 · Score: 0

Runs on top of the jvm, so who cares? Let it die.
You owe me a new keyboard by Anonymous Coward · 2013-01-12 20:38 · Score: 0

"the JVM [is] one of the most influential and important software inventions in the past 20 years"
Really funny indeed.
Re:Clear case of VMWare being evil. by Tough+Love · 2013-01-12 23:15 · Score: 1

This is a clear case of VMWare doing evil. So does this new, distasteful corporate direction have something to do with the arrival of Pat "tick tock crush AMD by fair means or foul" Gelsinger?
Oh wow, VMware spinmods. This is sad. I somehow got the impression that VMware employees are made of better ethical stuff than the likes of Apple or Microsoft. Maybe I was just wrong about that. Advice to you VMware people: if you don't want to really piss off the community, then watch what you do. Don't send out the spinmods.

--
When all you have is a hammer, every problem starts to look like a thumb.
Re:Clear case of VMWare being evil. by eric_herm · 2013-01-12 23:58 · Score: 1

Thinking that a company ( ie, a big group of human ) is acting a definite and concerted way is weird and too simplistic. Almost as weird and simplistic as the concept of universal evil ( ie, "doing evil" could perfectly mean something for some specific case, or say much less for some others, depending on the point of view ).
Heck, there is a reason why philosophers discussed of moral for centuries...
so "vmware is doing evil" can for sure only be a over simplifcation that doesn't reflect the reality except for a specific view, and so would be for sure incorrect for people. IE, being open to interpretation and on a clear emotional level is the perfect ground for flame, hence ( at the time i write this ) the "flamebait" score
Re:Clear case of VMWare being evil. by haruchai · 2013-01-13 03:38 · Score: 1

Does that reasoning also apply to countries (aka much bigger group of humans)?

--
Pain is merely failure leaving the body
Re:Clear case of VMWare being evil. by Genda · 2013-01-13 11:27 · Score: 1

People talk like there are moral absolutes, these are cultural constructs sitting on top of biological imperatives. Jeeze. There are games that people play. The corporate game is based on profit and is by design war-like right up to and including killing large numbers of people who get in your way (read about mercenaries hired by Shell Oil to wipe out entire African Villages to get what they wanted.) There are other games, like the game called society. These two games are often at odds with one another, and because one is predicated on the common good and the other is predicates on what's good for the corporation it is easy to see those looking from a social context getting a wee bit fussy about the practices of corporations.
This is especially true when corporations choose Sociopaths as their Corporate Officers. Corporations do behave monolithically. That is to say, that Corporations tend to have consistent cultures (unless they consciously prevent such cultures from forming which is unlikely because these cultures tend to be powerful motivators.) The cultures of a corporation are typically managed by its leaders (not always, but most often coming from the Corporate Officers.) So a business wide lack of respect for people, bigotry, sexism, greed, lawlessness or corruption, usually points to a board that is by most social norms EVIL. Another way of saying this is EVIL is as EVIL does. A lot of corporations have chosen to use human beings like toilet paper, because they think its good for the bottom line. These folks have no appreciation for critical dangers presented by a moral bankruptcy. The good news is that sooner or later, society tends to crush these entities. There are sadly gross exceptions.
did i just read, what? by Anonymous Coward · 2013-01-13 13:33 · Score: 0

'seems immune to corporate control.'

ffs...learn the language you are using.
Re:Clear case of VMWare being evil. by Tough+Love · 2013-01-13 14:05 · Score: 1

It's all very black and white to me when employees of a given company do evil. The company is entirely responsible, if only for hiring those lamers.

--
When all you have is a hammer, every problem starts to look like a thumb.
Re:Clear case of VMWare being evil. by Genda · 2013-01-13 15:19 · Score: 1

That's the point though, your perspective, your point of view, your opinion. There is no objective reality here. Which isn't to say I don't have a similar opinion, just that if you go around paving your opinions all over the scenery doesn't that make just as "evil" as any other egotistical bastard doing the same. Now if as a society we came up with a new game for being human predicated on... let's say workability, where the goal is for human beings to be empowered, fully self expressed and as personally productive as possible inside the basic limits of a sustainable environmental practice and given by an exponentially expanding technology, a whole different kind of life might be possible. Perhaps the key is choosing a game that recognizes and respects humanity.
Re:Clear case of VMWare being evil. by andyp · 2013-01-14 02:57 · Score: 1

I'd love to understand how this is a "clear case of... doing evil". This is a good read http://discursive.com/2013/01/09/things-to-keep-in-mind-as-a-vert-x-observer-you-dont-know-anything/
VMware and Red Hat issued a joint statement on direction in the vert.x Google Group and are working together to take this forward. To describe that as "evil" is misrepresenting the situation.
(disclosure: I work on Open Source projects at VMware)
Re:Clear case of VMWare being evil. by andyp · 2013-01-14 02:58 · Score: 1

Which "spinmods" are you referring to?