I have been thinking about this for a while and am writing this because everything said so far interests me greatly...
I am not a qualified django developer (yet), but have been successfully building commercial sites for over ten years with the last five in python/zope/plone. I love the pluggability of zope. Just drop in a "product" and it is ready to use with minimal configuration at the next restart. New features and content types are very easy to mix and match. Having said that... This is what I thought django was too, at first. It is more pluggable than most but is still not really there. Pinax is a great example. The fact that the project exists to integrate all those different features and modules is evidence. Putting them together correctly is so hard that it requires a project of it's own. If we need a showcase I think Pinax is it. It is like Plone but better. I would like to suggest that we consider using Pinax/Satchmo/LFS as pet projects. The effort being to re-factor everything to follow a list of "community approved" best practices and make everything more plug and play. A manager/developer making the decisions on a platform for their next project should be able to download django and just plug in the functionality he/she needs. Dependencies will exist but that's normal. So with specific projects to work with, the real next step may be to create that "Enterprise" site and give it a narrow focus of writing guidelines and best practices. Then making the necessary changes to the to Pinax/Satchmo/LFS projects to bring them into compliance. If all that would happen django would be an easy choice for anyone, well absolutely for me. Without these I spent months swinging back and forth on various decisions because the above situation does not exist for django. I know I am just re-hashing but please move forward with this, or something. I am most eager to help. Thanks, Richard Shebora 703-350-4707 office 202-215-2600 cel On Thu, Jun 17, 2010 at 4:19 AM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Thu, Jun 17, 2010 at 12:26 AM, finn <finngruwierlar...@gmail.com> wrote: >> Hi, >> >> I have with interest followed the thread "Seeking Django vs. Joomla >> comparison", and it has inspired me to start this new thread. >> >> I consider myself a Python/Django programmer, and I do so because my >> experiences with a number of programming languages, CMS'es and web >> frameworks has lead me to believe that Python and Django is simply the >> better choice from a technical perspective. I am not a fanatic and I >> won't say that everything else sucks, but honestly - if you have the >> choice between a better and a no-quite-so-good technology, you will of >> course want to use the better one, despite that the other would work, >> too. >> >> Now to the problem: a lot of people who needs websites have heard of >> Drupal or Joomla! or WordPress or PHP. But NOBODY has EVER heard about >> Django. If somebody suggests that they make their website with >> something called "Django" then this "Django-thing" must at least have >> some reasons to why it exists and why one should prefer it over well- >> known solutions. Consequently, people come the this discussion group >> and ask: "What are the reasons that you think your product is >> better?", and the answer they get is: "our product cannot be compared >> with the others because you cannot compare apples with oranges." This >> means that people who where willing to listen to a good sales talk >> leaves the shop in a hurry because the salesman obviously didn't want >> to sell anything at all. Which leaves me and a lot of other Django >> entusiasts with not so much work as we would as we would like to have. >> >> I think that we - the Django community - could do a better job selling >> our product, and I'd like to volunteer in this work. > > I completely agree. We've relied on our technical merit to get > 'sales', and while that has served us well so far, there is a lot of > potential to promote Django further. > >> I just don't know >> how to do it. > > One idea that has been bounced around many times is to start an > 'enterprise.djangoproject.com' companion site for djangoproject.com -- > a site that makes the case for Django in a way that isn't technical, > but focuses on the business case. This could include content such as: > > * Case studies > * 'Sales Brochures' suitable to give to a boss who might be > considering technical options > * Lists of contractors that will provide support when things go wrong > * Lists of training opportunities > > There are at least three subtasks in this: > 1. We need to actually design, build and deploy the site > 2. We need to gathering the initial content for the site > 3. Long term, we need to curate the content, including moderation of > case studies submitted by users, and direct solicitation of new case > studies. > > If this sounds like a way you might like to contribute, then the first > step is to turn this skeleton proposal into something more concrete. I > don't have any particularly strong ideas, other than "it must be > awesome" -- here's the opportunity for you (or anyone else in the > community that wants to help out) to wow us. > > Yours, > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@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. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
