On 5/5/2010 4:13 PM, Adam Baxter wrote: > The compromise may be a *nix utility to verify that everything's ready > to send to CoApp. If there are some developers who can't afford a copy > of Windows, that's probably one instance where CoApp as an organisation > would be really helpful.
What about allowing a project maintainer to root the sandbox to their application when subscribing to the build results? That way they could have confluence-like builds of their app in almost real time, which is as useful as installing the CoApp toolchain and running it on their own box. Of course the CoApp team would probably want the final call to validate binary compatibility and all that, as to what goes to CoApp's distribution. But letting projects participate at the sandbox/alpha phase just to prove all is well seems like a really slick idea. I know httpd folks would appreciate seeing their buggy commits raise a flag asap if it broke the windows platform, since it's usually a trivial fix. _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
