On Thu, Jun 24, 2010 at 5:16 PM, M.-A. Lemburg <span dir="ltr"><<a href="mailto:mal@egenix.com">mal@egenix.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Almir Karic wrote:<br>
> i would like to help out with the move.<br>
><br>
> is anyone actually opposed to moving to GAE (either moving the current<br>
> code base or re-write, whichever seems more appropriate)?<br>
<br>
</div>I don't think people are opposed to having a PyPI clone on GAE,<br>
but moving the existing installation to GAE is something we would<br>
have to discuss separately.<br>
<br>
I for one would not welcome such a change, since we then completely<br>
lose control over service availability.<br></blockquote><div><br>I don't really understand what this means. Services become unavailable sometimes. A computer breaks, a company shuts down, an agreement ends. We don't necessarily have "control" over these situations, but we can respond to them. If App Engine goes down and the App Engine team is all like "whatever, we'll get around to fixing stuff sometime" then sure it's a problem. But it's not a plausible problem. The plausible problem is that App Engine goes down, as it has from time to time, and we have to wait for them to figure out what's wrong and fix it. *We* don't have to fix it, we only have to *wait for someone else to do it*. I don't see any reason why *we* are any better at fixing issues than the App Engine team would be. Also presumably when there is a failure we want for the failure to be understood and avoided in the future. The App Engine team does that. And they do that *for us*.<br>
<br>In some catastrophic case we could move the site to another server, use TyphoonAE to move the code over (or simply require that there is a sufficient abstraction layer to allow for a more normal environment) and bring the site up. We control the domain, we can ultimately control where it is hosted. This kind of failure seems like it would be far more likely given our current situation than on App Engine, but moving to App Engine would not somehow make this kind of move impossible.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Someone would also have to do some math to calculate the monthly<br>
costs for the PSF:<br>
<br>
<a href="http://code.google.com/appengine/docs/quotas.html" target="_blank">http://code.google.com/appengine/docs/quotas.html</a><br>
<a href="http://code.google.com/appengine/docs/billing.html" target="_blank">http://code.google.com/appengine/docs/billing.html</a><br>
<a href="http://code.google.com/appengine/business/" target="_blank">http://code.google.com/appengine/business/</a><br></blockquote><div><br>It seems unlikely we'd have to pay for the service.<br><br></div></div>
-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>