On Fri, 2006-03-11 at 21:01 -0600, James Bennett wrote:
> On 11/3/06, Ilia Kantor <[EMAIL PROTECTED]> wrote:
> > I can't write anything too. Akismet is a great tool against developers.
> > Thanks.
> 
> It's being worked on. Patience is appreciated.

This seems a good time to make a point related to my last post about the
Fogel development practice book.

I am not surprised that people make these sorts of comments here,
because compared to most open source projects, there is *very little*
traffic on this list relative to the amount of development going on. So
they have little reason to think these problems are being actively
addressed, even though I am sure they are. Therefore, we public readers
can only assume there must be a fair bit of dev related communication
going on *off* list. This is totally understandable given that the core
developers are all at the same company. However, it has the down side of
contributing to the public perception that Django dev is rather "closed
door" for an open source project and that the dev team is not really
looking to attract more developers but is more of a world online club
with some extras. ( Whether this is true is not my point, I bring up the
*perception* ). It also makes it seem like the dev decision making
process does not involve as much discussion in the open as is normal for
an open source project with such a fast development pace. 

One of Fogel's points in his book is that it is good practise to repeat
your dev conversations on the public list and even to forward ( with
permission ) private conversations on this sort of stuff so that your
public and potential future developers/testers/evangelists feel like
they have more of a clue as to what's going on what's coming up. Nobody
wants to work on a patch or contribution only to find out that somebody
else was already most of the way through a better job and just hadn't
said anything. I have watched that create bad blood on open source audio
projects and push away potential developers. I realize there is a trac
system in place too, but public discussion seems somewhat lacking, and
the lack has for me at least made me less likely to want to write code
for Django itself.

Just my two cents, not meant to be a dig but a constructive criticism.
( After all, I love Django! ) I hope it will be taken that way. 

Iain


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to