The Real Problem with Django

Agreed.

Posted by Joshua Blount

Here, here!

Posted by David Reynolds

Agreed!

Posted by Lorenzo Bolognini

I'll raise a glass to that, here's to everyone who ever triaged a ticket, or submitted a diff.

Posted by alex gaynor

+1

Posted by CreativeConvergence

Agreed. Huge thanks to everyone of them!

Posted by Andreas

They deserve lots of Praise! Django is great! But not taking constructive criticism from someone trying to help, who uses and contributes to django, is not so good. It closes the community.

Posted by Tofu

Totally agree +1

Posted by Abraham Estrada

@Tofu:
+1

Posted by Julian

The irony is, the air is so thick with credit, respect, and deference towards the developers from the vocal minority, that criticism, politely and constructively phrased, is simply marginalized as ingratitude; responded to by a nice big group hug. (To be technically accurate, some respond in excruciating detail, missing the big picture, entirely). Giving credit is good, and obviously deserved. However, we're not dealing with a zero-sum game. The frustration is real, tangible, and also understandable. Recognize it for what it is: the most recent cycle of "Q: can we have a release? A: one is on the way!". The more iterations of this without a release the more credibility is lost and the greater the frustration. Ironically, it's compounded by the fact that trunk is generally "stable" -- it's a dangling (but always moving) carrot. If it weren't usable, it'd be much harder for people to say "just tag it, and ship it, for crying out loud". If one wanted to search for a silver-lining, all the clamoring for a release is credit of a sort: it's desire for the product.

Posted by Peanut Gallery

Thank you Jared (and others), and on behalf of myself and the other core developers, you're very welcome.

In the midst of a very heated debate, it's nice to be reminded that some people acknowledge the fact that the developers of Django are volunteers, and that our efforts are appreciated.

Posted by Russell Keith-Magee

And Brian Rosner. He's pretty much kicking ass right now.

Posted by Eric Florenzano

+1

Posted by Jasdeep

+1

Posted by Timo Zimmermann

Definitely +1. Thank you all. :)

Posted by Bryan Veloso

agreed

Posted by cafeconleche.nl

Firsted, seconded and thirded. :-)

(Ehi, psst, that would be "MaLcolm". )

Posted by Nicola Larosa

Thanks a lot!

Posted by casseen

+1

Posted by Stefan

Huge thanks to the everyone who has worked on Django!

Posted by Arthur Case

Yes, indeed, a resounding big Thank You!

Posted by Rajesh Dhawan

you're darn tootin

Posted by jefrey

Thanks Nicola. Fixed... sorry Malcolm.

Posted by SuperJared

I'm totally agree. My current employment is last projects I was working are consequence of the well work of this team.

But sometimes I think that some guys of core team like not other members to make suggestions or participate.

Some days ago James Benett deleted a snippet in a dictatory action that I disagree totally.

Some months ago, worry with the limitations of INSTALLED_APPS and to make Django apps more pluggables/reusables I wrote e-mail and tickets giving some ideas about the requirement, and the responses was all with something like "you don't know how to write pluggables apps". Ok, but now I know that other ticket says almost the same I said, and it is going to be patched, and DjangoPluggables site is other thing that proves I was right. Ok, my english is poor and probabily the cause of bad understood is this, and I accepted it.

These things makes me think that MAYBE the core team likes centralized decisions and MAYBE we could be faster with something more descentralized.

But, after all, I'm very happy with this work and those guys, and this is the main thing that I can tell about them.

Posted by Marinho Brandão

Hi,

I'm an enthusiastic beneficiary of Django. I have a developer writing a front and back office database and admin system for an insurance brokerage and insurance company. I feel I, like most other beneficiaries, should be giving back to the project itself. As a result, I would like to suggest a 2% voluntary "royalty fee" based on the fees developers charge their clients payable back to the core project. In that way Jacob can bring in other core developers to help move Django forward and broaden it out even faster. I have see this before with other Linux Distros i.e. Centos.

This does not cost developers anything and it the cost is very small for clients. Certainly a lot less than having to by non open source platforms.

Look forward to the views of others.

Regards

Peter

Posted by Peter Bassel

A big thanks also to Justin Bronn for all the excellent work on the gis branch.

http://geodjango.org/hg

Posted by Ariel Nunez

@Peter

thats a good idea. Some days ago I saw a thread telling something about a "Django Foundation" or something like this.

maybe this foundation could starts something like your idea, I wish to participate if this forward :)

Posted by Marinho Brandão

+1

Posted by Oscar

+1

Posted by Satheesh

It may be a great product, but there are many issues for a non-python newcomer with getting it up and running especially on windows.

That spoils it for me - the multiple errors that appear before you can even start, solving each problem as you go.

I think that the developers seriously need to address this, as Django's growth is thwarted, in my opinion, for what is otherwise great software.

Posted by Emmet

I suspect you'll have many fewer problems when Django hits 1.0 stable.

Posted by SuperJared