James I know that asking "when" for delivery of an open source project is not usually a question that can be answered accurately, but would it be possible for you to give at least a broad estimation of which of the following is closest to a time-frame for the next release that includes an updated-and-production-ready (foundational) social_project: a) next few weeks b) next few months c) maybe sometime in 2011
Thanks Derek On Jan 23, 1:21 am, James Tauber <jtau...@gmail.com> wrote: > On Jan 18, 2011, at 9:32 AM, Russell Keith-Magee wrote: > > > > > I think we need to clear up some misconceptions here. > [...] > > Pinax, on the other hand, works at a higher level. Pinax targets a > > specific domain -- social web apps > > Actually, this is a major misconception. Pinax is not targeting a specific > domain. And in fact, the social features are probably those features of Pinax > least production-ready. Sites like eldarion.com, us.pycon.org, > pinaxproject.com, gondor.io and quisition.com are all examples of Pinax that > have nothing particularly "social" about them. > > > So - you really don't have to make a "Pinax or Django" decision. Any > > app that can be installed in a Django site can also be installed in a > > Pinax site, and every Pinax site is a Django site. > > Exactly. > > > As for the original question -- are there any drawbacks? Well, not > > really. Pinax suggests a particular collection of apps, but you can > > use any other app you want in parallel. Pinax mandates a few standards > > for project layout and the like, but for the most part, they're just > > using the best practices commonly understood by experienced members of > > the Django community, but the Django project itself hasn't gone to the > > trouble of formalizing. > > Yep. And it's important to note you can use Pinax *just* for this. The > zero_project is appropriate for almost any kind of django site and, for the > most common type of account management, account_project is a good starting > point. > > > About the only potential downside I can see is that If you're not > > building something in Pinax's sweet spot -- i.e., a social web site -- > > you won't get all the benefits that Pinax has to offer. If you're > > building something *really* different, you might find that Pinax's > > conventions obstruct you in ways that a raw Django install wouldn't. > > However, for most "websitey" websites, this won't be an issue -- > > Pinax's conventions are, for the most part, a bunch of practices that > > you should probably be following anyway -- Pinax just forces/provides > > the tools to help you to follow them :-) > > The social stuff is in many ways Pinax's current weakness. It's the social > stuff that hasn't been updated for our next release yet (although we're > working towards it) > > I was planning on doing this anyway, but this thread has encouraged me even > more than I need to write some blog posts about things like Pinax's > zero_project, static_project and account_project in the coming weeks. > > James -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
