988 karma · joined January 18, 2011
> If you have problems with Clang, please file bugs!
Filing compiler bugs is really hard with a closed source project.
But they are arguing that the API they added makes the proprietary vmkernel a separate work and the distribution with vmklinux a "mere aggregation", no?
I thought they have a kernel module with a GPL wrapper, like the NVidia graphics module which would be more contentious.
The bitcoin transaction can just go to /dev/null with a hash of the message as data, so don't have to pay somebody ( ;) ) and you cannot track who sent data to whom via tracking the bitcoin transactions.
An Open Source project becomes good enough and takes over the market. Because the price of the Open Source product is zero you cannot compete with proprietary software. Additionally your software introduces licensing overhead. You have to move your product significantly forward or move on to other markets. This happened e.g. to the application server market. And at some point in the future it will happen to the office suite as well.
2. It gave you all the stuff you needed for your project at one place. The SCM of your choice, mailing lists, hosted forums, wiki, bugtracker, and a website with PHP/MySQL. They have retired hosted forums, wiki and bugtracker now.
3. It increases the discoverability of your project. The project summary page actually gives a nice overview of the main points of your project such as licence, category and features; They have things like project of the month, etc.. Without sourceforge (and freecode) we are at SEO, social media and word of mouth for open source PR. This is much more effort.
4. They allow huge binary downloads which can be uploaded with e.g. rsync and scp.
Loosing all this might be fine for a large project such as GIMP, as they have the manpower and donation money to do it themselves. For smaller projects this distracts from developing the project.
I think this issue must be solved on a regulatory level, i.e. Google (and Bing!) should be punished for providing malware links (and the actual providers of course).
If people are unemployed you are squandering resources.
TrueCrypt is a consumer facing Open Source project. Those rarely have a large developer community and seldom get patches. Most successful ones are backed by corporate interests (Firefox, Eclipse, VirtualBox, ...).
Having no need of TrueCrypt himself, no other developer in the community to whom he could entrust the project and faced with drudgery the like he probably also has at his job (except he gets payed there), he probably did not want to continue developing and improving TrueCrypt (e.g. EFI support).
At this point. Since it is a critical security product there is no other option then to warn of all users. If there is a fork, it has to earn its reputation first.
I view truecrypt.ch as a bad development, since a) TrueCrypt is trademarked by the developer and b) the TrueCrypt license explicitly says that you cannot fork the project without renaming it to something other than TrueCrypt.
See https://www.grc.com/misc/truecrypt/truecrypt.htm "And then the TrueCrypt developers were heard from . . ."