On Tue, 2009-02-03 at 11:19 -0800, Mike wrote: > > > I understand that it's possible this handler may offer some alternative > > options that in some situation is better or different from any existing > > option. > > Such as, mod_fcgid is already installed for running perl, ruby, php. > Some hosts still do not support django, so there may well be interest > in stopping this gap. > > > So it should > > be easy to have this be a third-party option that people could download > > and use if they wanted to go that way. > > In that case it would be good to have a link from the documentation > to it so that people can find it. Otherwise, I really don't care > whether it is in 'blessed', 'sneered_at', 'gitmo' or 'leper'.
Google juice tends to be the best approach. If we linked to every third-party module out there, even only the respectable ones, we'd have a few hundred links, at least, in the documentation. Where do we draw the line? What happens if the thing we links to isn't of sufficient quality (that ends up reflecting badly on us)? Again, I'm not saying "no" -- I'm pointing out the considerations. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
