The Mythical Django Pony, a blessing?

On my way to have lunch on the first day of DjangoCon in Portland, I met Eric Holscher in one of the corridors of the hotel holding a pink unicorn. It seemed odd to me so I approached and asked him about what he had in his hands. He explained that this was the unofficial Django mascot, which was a pony. I didn’t make the obvious observation that what he had in his hands was a unicorn, but asked how this came to be. He explained that one of the core dev on the Django mailing list responded to one of the feature requests saying “no, you can’t have a Pony!” as a way of politely refusing the feature request.

I was surprised to be in a DjangoCon session two days later where Russell Keith-Magee talks about declined feature requests and how they are referred to as ponies, and suggests ways in which your features are likely to get accepted. He also explained the whole story behind the mythical Django pony (which is really a unicorn!).

Why am I bringing this up now? well as I write the concluding chapters of my dissertation, I notice an odd relationship between the number of modules present in a code base and the number of new contributors. The statistical model suggests that adding modules to a code base is associated with an increase in the number of new contributors. However, this relationship reverses itself for projects that have an above average number of modules. So adding modules when there are already a high number of modules results in fewer contributors joining the development effort over time. The same effect could be observed for average module size (measured in SLOC), where an increase in the average size of a module is associated with an increase in new contributors up to a certain point. Then, the relationship starts to reverse (Quadratic effect for those of you who are statistically inclined).

It dawned on me that one of the explanations for such an observation is that an increase in the number of modules or an increase in the average size of a module is a result of the increased complexity in the code base from adding or implementing a feature. Assuming that the projects in my sample are not mature to a point where there is no need for new contributors to join, then we can attribute the decrease or increase in numbers of new contributor to the balancing act of complexity where the community correctly decides to include just enough features as to not make the codebase overly complex for new participants and yet valuable enough for new members to start using and contributing to it (Please don’t bite my head off for implying causation here, I am just forwarding a hypothesis that seems to be supported by the data. It’s up to you whether to accept it or not).

So how does this relate to ponies? Well, I just might have put my finger on one of the things that makes Django unique, and that’s the core developers know how to play this balancing act by knowing when to include or refuse a new feature. This I believe is possible because there is what we can refer to as a Django philosophy in deciding which feature requests are considered ponies. This seems to be paying off as participation in Django is way off the charts. Don’t ask me what the Django philosophy is, as I have no idea. I am just observing its results. If someone out there thinks he knows what it is, or has a link, please do share.

Take away from this, at least for other FLOSS projects that want to learn from the Django community. Be clear on the goals you want to achieve with your project, and don’t be afraid of saying “No! you can’t have a pony!”. As for the Django community, you are already on the right track in trying to explain why features are refused. Keep at it!

Update: Here is the Django philosophy summed up quite eloquently by Dougal Matthews:

I think the philosophy is quite simple generally. “Does this need to be in the core?”

You can read his comment for more explanation.

Add post to:   Delicious Reddit Slashdot Digg Technorati Google
Make comment


24.12.2017 9:34 What is the deal with the pony in Python community? - ExceptionsHub
Its a Django unofficial mascot. See this blog post for an explanation.
16.12.2009 13:47 Another Fail-Pet: Github | fredericiana
riginal” Django pony was, in fact, a unicorn.
7.10.2009 14:34 The Unofficial Django Mascot « Praval Tirubeni's Blog
I like this one but there is also a green version for all the die hard fans. Find out what more good things this pony brings.


I think the philosophy is quite simple generally.

Does this need to be in the core?”

In other words, is there something that stops developers making this as a standalone app. If it can be made stand alone, then there is little reason to put it in core.

There are ofcourse some things that make sense, and that just comes down to thrashing it out with everybody on the django-developers mailing list from what I’ve read. I think the main key is lots of consideration is undertaken by many different people before it has a chance of getting into core.

Very interesting article. Philosophy in it’s essence.

Gustavo Campos 26.05.2010 21:34

A pony which is a unicorn that, in fact, looks like a pegasus?

kyeldon 26.03.2011 5:34

Who had the original idea for that nice mascot? thx in advance (

Required. 30 chars of fewer.


captcha image Please, enter symbols, which you see on the image