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 wasn't trying to say "not true, case closed." I was saying that as far as misperceptions go, that's one that needs to be addressed earlier in the chain. "Django is a closed project" is easier to deal with once "most of Django's developers work at one company" is dealt with. > The people who have the perceptions aren't reading > this or the blogs. Like I said, I'm *not* talking about what the truth > is, but what the *perception* is. 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 examples if that's what people are saying. > This may be true. However, it's not pertinent to my point, which was > that there is not enough discussion *relative to the level of coding > going on*. This is something I don't really understand; the appropriate amount of discussion is however much discussion it takes to get the job done. This is an obvious over-simplification, but it feels like you're arguing that there should be a function 'f' such that x commits in the repo should necessarily be accompanied by f(x) posts on the dev list, and I don't think I could ever agree to that; it's entirely possible that a big issue spanning dozens of posts on the list could boil down to one commit, or that a couple of quick posts on the list could result in dozens of commits. Or that there could be code which isn't accompanied by *any* discussion on the list (e.g., bugs being closed out with nothing but comments in Trac), or discussion which isn't accompanied by any code. In other words, I'd dispute that there is a suitable objective yardstick for measuring the "appropriate" level of posting to the dev list. > Ok, on this point, I totally disagree. This is exactly what I mean, that > is 100% an example of closed dev policy. The fact that developers take advantage of being in the same place at the same time to coordinate more effectively is "a closed dev policy"? Now you've really lost me. > There are scads of super smart > python developers who might contribute but for very legitimate reasons > will never be able to attend conferences. Taking advantage of conferences to get developers in the same room is not the same thing as "you can only participate if you go to conferences x, y and z". Again, I don't follow your logic (and, again, I'd like to see some of your claims substantiated by reference to relevant postings expressing people's "perceptions" of Django). > Again, I don't that is a good model for *attracting development*. One might counter that the goal of a software project is to produce good software, not to attract every developer on the planet ;) > Well, I guess it's a question of whether the core want to adjust further > towards a more open policy. I have yet to see specific examples, other than ones whose logic I'm unable to follow, of how exactly Django's development process is "closed". > All I'm really saying is that right now the perception exists > for a reason that joining django development would be difficult and > people lurking and trying to decide whether to work on it aren't near as > likely to jump in as they could be. Again, I do my best (as do most of the other people I personally know who are involved with Django) to stay on top of what people are saying about the project, and I'm left wondering where the examples -- other than your posts -- are of this perception that Django is a closed project. Do you have a secret cabal of people who have private closed-off discussions about Django and never post those discussions publicly? ;) -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
