Why fork from BOINC?
We didn’t take this decision lightly. We have spent considerable time and effort in trying to work with BOINC and improve it. However, some major problems made forking the only viable option: • Many patches ignored or misapplied • Premature releases with known bugs • Minor feature requests ignored • Berkeley lock-in • An ever-growing bug list • Poor usability • Poor coding standards The Linux Information Project has this to say about project forks: “…the possibility of forking is actually one of the greatest strengths of the free software development model. One reason is that widespread awareness of the possibility of forking and the consequent problems that can result can serve as a strong incentive to achieve consensus and work together cooperatively. Another is that such awareness provides an additional incentive to developers to do outstanding work. In addition, when forking occurs, the possibility exists that it will eventually result in a productive cross pollination, or even a
