Basic demand side problem. When an app stands up and solves the real issues (which, as the DjangoCon presentation proved, there were many) involving App Engine and Django, then I (and the demographic of developers I statistically represent) will become excited.
-S On Feb 6, 9:51 am, David Stenglein <david.stengl...@gmail.com> wrote: > If so, why the seeming lack of excitement around App Engine? Are > google engineers not involved in the community? > > -Dave > > On Fri, Feb 6, 2009 at 7:10 AM, Russell Keith-Magee > > <freakboy3...@gmail.com> wrote: > > > On Fri, Feb 6, 2009 at 8:32 PM, Waldemar Kornewald <wkornew...@gmail.com> > > wrote: > > >> Hi Russell, > > >> On 6 Feb., 11:34, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > >>> I would suggest to you that the broader project of "modifying the > >>> django.db.models interface to be fully independent of SQL" is much > >>> more likely to get core developer support. We (the Django core) will > >>> be very receptive to any suggestions on how django.db.models needs to > >>> be modified in order to support non-SQL backends -- especially if you > >>> can demonstrate that your suggestions aren't just theoretical, but are > >>> clearly required by an actual backend implementation. > > >> Agreed, making models SQL-independent is the most important (and most > >> complicated) part. Do the people secretly working on App Engine > >> integration try to implement that part? > > > I haven't seen their code, so I can't say for certain, but I imagine > > that they have a small collection of patches for the main Django tree > > that enables their backend to be independent of SQL. > > >>> If you are maintaining an external project handling AppEngine support > >>> for Django, then that project's wiki is the right place for > >>> documentation about AppEngine support within Django. While AppEngine > >>> support isn't part of Django's core, Django's wiki isn't the right > >>> place to be providing AppEngine specific instructions - especially if > >>> the first instruction is "install this third party project that isn't > >>> formally affiliated with the Django project at this time". > > >> I can't find anything like that in my wiki page. It describes what is > >> necessary for a completely new port that has practically nothing to do > >> with app-engine-patch apart from being able to reuse some of the > >> existing code. It could be useful for any porting effort. If I keep it > >> in my wiki nobody else can work on that page. It's almost useless that > >> way. > > > Ok - sounds like they could be some good contributions. I just wanted > > to make sure you were not planning on making the Django wiki the home > > of the "how to use app-engine-patch" documentation. > > > Yours, > > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
