Michael Radziej wrote:
> I like Django, perhaps I rather contribute
> more tiny stuff of which I feel that it will get integrated, and I have
> my own patchset for Django. So what? It works fine for me. Why should I
> turn to a different framework when I like the concept and code (and the
> docs!)
Hi,
let me add my own view, and this is not a direct answer to Ian but more
to the whole thread.
I personally got frustrated about the way tickets are handled. And sure,
Adrian is currently a very scarce and important resource. There's
written enough about that and I don't want to deepen it agai
On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote:
> > I have to say that I think you're confusing arrogance with a desire to
> > do things *RIGHT*, and a lack of time on the part of the core devs.
>
> This however is part of the issue. With rapid growth comes that lack of
> time for the founders.
> I'd just like to point out a counter-example to those arguing that the
> core developers don't listen to criticism. There was a post recently
> to django-users called "Why I'm giving up on Django" :
Agreed. I would like to point out that I am not saying the core doesn't
listen. I'm not trying
Hi all,
I'd just like to point out a counter-example to those arguing that the
core developers don't listen to criticism. There was a post recently
to django-users called "Why I'm giving up on Django" :
http://groups.google.com/group/django-users/browse_thread/thread/394701c83497e405/f85b5013b6
> What I've said here, repeatedly, is that if there's this problem, I
> want to see examples of it, because I haven't so far, and if I'm going
> to understand that there is a problem and understand where it comes
> from, I *need* to see examples. There's a big, big difference between
> that and "n
> well, then I do. I´m scared away. why? exactly because of what james
> is writing here.
> it seems that noone except the "core developers" are allowed to
> criticize django - whenever something like this comes up on the list,
> there´s someone who fights the arguments tooth and nail. there´s no
> So far as I can tell, our biggest long-term management problem right
> now is not one of scaring developers away, it's one of keeping track
> of all the people who want to get involved and all the things they
> want to do. You haven't yet provided an example to the contrary.
well, then I do. I´
On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote:
> Every single comparison of Gears to Django I have read say something to
> the effect of "Gears is more community based". I think that's pretty
> clear if you read between the lines. And part of what I'm going on about
> is addressed in your blog
> I would like to see examples of this; I have a pretty comprehensive
> set of ego searches and tag subscriptions for Django-related postings,
> and I don't get the "Django is closed, don't bother trying to get
> involved" vibe as much as you apparently do. So I'd really be
> interested to see exa
On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote:
> Ok, this is where you are IMHO wrong. You don't get to choose which
> misconceptions you throw out. The perceptions are there, obviously, or
> there wouldn't be blog postings about it, and you saying they are wrong
> accomplishes nothing.
I was
11 matches
Mail list logo
