On Wed, Dec 3, 2008 at 10:33 AM, Peter Kasting <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 3, 2008 at 10:29 AM, Evan Martin <[EMAIL PROTECTED]> wrote: > >> Will the try servers become public? >> > > I didn't realize they weren't. Lame, it would be quite useful if they > were, completely aside from this WTL issue. Who can help figure out how to > do this? > Opening the try servers externally is tricky. If the patch is sent by a malicious users, it means that they can run arbitrary code in our test environment, which is not good. We would need to limit the scope to only the people who already have write access to the repository. And since they currently all have internal access, it was not a priority. But... we are looking at granting write access to external contributors really soon.. so maybe it's time to reconsider. Unfortunately the current approach does not really have any notion of access control. Nicolas > My Windows knowledge is about ten years rusty, but WTL is free, right? >> So there's no need (at least in the "dropping dependency on expensive >> software" sense) to remove it. > > > Yes, WTL is free. The problems with VS Express aren't WTL's anyway, but > the underlying ATL code, which is also freely available (as part of various > SDKs including one we supply in third_party). Newer versions of VS Pro ship > a newer ATL that's more tightly integrated than the one in the SDK, but we > don't need it (and I'm not sure how well we'd work with it, given how little > we've done with VS 2008). > > PK > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
