Hacker News new | ask | show | jobs
by budwin 5757 days ago
I really feel what they said about the community and core developers:

Reading the correspondence on the following bug really turned me off to the project. http://code.djangoproject.com/ticket/5172.

Specifically: "Please do not reopen a ticket that's been marked "wontfix" by a core developer;"

I'm not sure how the issue jives with the whole Django philosophy, but with that much interest in changing the templating language, I found that a bit harsh...
2 comments
viraptor 5756 days ago
Someone has to make a decision and since here that person is a django-core developer, I'm not sure there's much to argue with. If they don't want to do that, bug will get marked "won't fix" every time it's created.

What else do you propose developers should do? I may disagree with this decision, but someone has to lead the project.

link
rohitarondekar 5756 days ago
How else will a core developer let it be known that this feature/issue won't be fixed? The "wontfix" tag/state is there for this very reason. And the core developers are there for this very reason -- to make decisions.

I'm curious though. Why not just fork the project and be more open in terms of getting patches in?

link