News for hackers. Stuff that matters.
Re:An important announcement to the Vert.x community by ChuckMcM on Tuesday January 08, 2013 @12:41PM (#5027286)
There is a very subtle but important point here. He worked for VMware so he had an employment agreement with VMware. That may have conveyed rights to things he worked on to the company, so even working on an open source project, his work is 'owned' by the folks who pay him.

I am not a lawyer, personal circumstances led me to do a lot of research on this topic and consult with both a lawyer who was versed in employment law and one who specialized in Intellectual Property law to see what was what. And in California your employer can claim ownership of anything you create or "enhance" which is either done on company time, or with company resources, or (and this is the tricky bit) associated with the business or goals of the company.

From the posting it sounds like this is what VMware is alleging which is that they 'own' this work he did and have asked him to transfer it back to the company. I know that sounds weird to someone who might think they were working on a free software project but it is the way the law is structured.

Re:An important announcement to the Vert.x community by jbooth on Tuesday January 08, 2013 @03:38PM (#5028363)
But if it was released under an OSS license, anyone who wants can fork, rename if necessary due to trademark, preserve a little (c) vmware in the source files and do whatever they want, right?

Basically, can vmware retroactively revoke that open source license?

Re:An important announcement to the Vert.x community by EwanToo on Tuesday January 08, 2013 @04:10PM (#5028538)
They can't retroactively revoke the licence, but they can claim the ownership of the brand and the various systems like the bug tracking database, which appears to be what they're doing.
Re:An important announcement to the Vert.x community by georgemcbay on Tuesday January 08, 2013 @04:25PM (#5028615)
As copyright owners they can change the license going forward, but that doesn't retroactively change the license for previously released versions.

eg. Vert.x versionX+1 could be modified to have a new license that doesn't allow forks and then you wouldn't be able to fork if you included any of the new stuff they added in that version, but Verx.x versionX would remain released under the previous license terms.

Re:An important announcement to the Vert.x community by justincormack on Tuesday January 08, 2013 @04:21PM (#5028593)
AFAIK vert.x was developed in the UK not California. It probably is work for hire in UK law, but agreed as open source (which suggests there is probably a contractual agreement).