On Thu, Feb 18, 2010 at 4:28 AM, Ikai L (Google) <ika...@google.com> wrote:
> Code download would only benefit Python, anyway, since Java source is not > uploaded. There are a million reasons why this is a bad idea and some have > been touched on. Personally, I cannot think of any situation in which I > would use this over source control, which will allow me to annotate > check-ins, create I can think of one very useful but possibly corner case scenario for this, and it's not related to helping manage the source code (I strongly encourage everyone to use a VCS for their apps!). An option to explicitly allow anyone to view the sources that are deployed would help open source python applications hosted on GAE reassure users that what they are running is actually what they can reuse and fork. Right now there is no hard guarantee and developers must be trusted that the google code github repo and the gae URL are referring to the same thing. A solution would be a 'Deploy to GAE' API to be accessed from Google Code or other VCS services, which would make the connection between a certain state of the source tree and a certain version of the deployed app more 'official', without actually requiring GAE to be able to provide the sources itself. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
