[This appears to have bounced - trying again] Ben, That's an interesting idea. I'm sad to say that we would need to think about security in the receipt of data. Just as we now have signed license agreements, we might need to have certificates and keys for publishing test results. Passwords might be sufficient and easier to manage. An existing server would likely end up with a Seaside app that allows mere mortals to request a signing or a password. After moderator approval (also part of the app), the tester would be given or emailed to retrieve the credentials needed to post test results. BTW, none of that makes it a bad idea or "too hard." I just fear that we would regret having a wide-open way to trash our test results data. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Ben Coman [btc@openInWorld.com] Sent: Tuesday, November 01, 2011 10:00 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :) A second idea for a distributed continuous integration test system. I would personally be happy to contribute cpu cycles to running a Pharo test system on top of a virtual machine, which from a central server obtains a random set of Metacello configurations to install, runs tests and reports results to the central server. Apart from gaining the processing power to possibly test all permutations of configurations, it also provides a way for new community members to feel like they are contributing, which preceeds them getting more involved. As an example in line with my first comment, perhaps the initial proof of concept would be done as a research project, and then the paid professional would polish off the stability and usability of it. cheers, Ben