diff --git a/www/conservancy/static/copyleft-compliance/vmware-code-similarity.html b/www/conservancy/static/copyleft-compliance/vmware-code-similarity.html index 234af6b9..d78c5360 100644 --- a/www/conservancy/static/copyleft-compliance/vmware-code-similarity.html +++ b/www/conservancy/static/copyleft-compliance/vmware-code-similarity.html @@ -15,7 +15,7 @@
Next, we compared the source code of the Linux Kernel 4.5.2 to the LLVM+Clang system, version 3.8.0. These two projects are each a large program that are not known to actively share code. There may be some very minimal similarity simply due to chance, but something much lower than the 3.68% found between Linux and FreeBSD's kernel.
Indeed, when the same test is run to compare Linux to the LLVM+Clang system, the "ratio of similarity" was 0.075%.
With the baseline established, we now begin relevant comparisons. First, we compare the Linux kernel version 2.6.34 to the sources released by VMware in their (partial) source release. The "ratio of similarity" between Linux 2.6.34 and VMware's partial source release is 20.72%. There is little question that much of VMware's kernel has come from Linux.
+With the baseline established, we now begin relevant comparisons. First, we compare the Linux kernel version 2.6.34 to the sources released by VMware in their (partial) source release. The "ratio of similarity" between Linux 2.6.34 and VMware's partial source release is 20.72%. There is little question that much of VMware's kernel has come from Linux.
The following describes a methodology to show Hellwig's contributions to Linux, and how they compare to code found in VMware ESXi 5.5.
31 August 2016: We're beginning work on a system for Payment and Reimbursement Requests. This is a smaller piece of the larger NPO Accounting project. Because it doesn't require much integration with larger accounting systems, we can help address this specific bookkeeping problem for NPOs sooner, and start building interest in the larger NPO Accounting project.
-We haven't started writing code yet, so now's a great time to get in on the ground floor! Check the Requirements document we're putting together on the wiki. Join us on the mailing list to let us know what's missing, and hear first other ways you can contribute as we start building the system.
+We haven't started writing code yet, so now's a great time to get in on the ground floor! Check the Requirements document we're putting together on the wiki. Join us on the mailing list to let us know what's missing, and hear first other ways you can contribute as we start building the system.