GitHub has been great for us. The code management system makes collaboration and code control very intuitive. They have discounted packages for academic use, where the "micro" package (at a minimum) has 5 private repos free of charge. You could check to see if they have something similar for nonprofits generally.

Or they could approach it as an engineering problem, where the key is to find signals of interest that have some predictive power. If they add (or have) a feature to partition the data into independent training and test sets either across time or across sites, preferably permuting over some subset of combinations, they can get help mitigate these issues. Without doing things like that, they are (as you point out) failing to address a brutal multiple comparisons problem.

Obilg. XKCD: http://www.xkcd.com/603/

Results have been mixed. I, for one, have page tearing now that I didn't have before (GMA965). Worst case, you can revert to the Intrepid driver: https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4 But before doing that, you might want to look at a troubleshooting guide: https://wiki.ubuntu.com/X/Troubleshooting/IntelPerformance And people's descriptions of how UXA (the new/future render) has been working: https://wiki.ubuntu.com/X/UxaTesting