This is partially inspired by the thread that won't die: "High Level Discussion about the Future of Django."
I want to contribute something back to Django. Specifically, I've already paid for my hotel and flights for DjangoCon 2010 and I'm definitely going to stay for the sprints. However, since I've only worked with Django and never on Django, I'd like to have some level of familiarity before then. Preferably, I'd like to handle a few tickets, both familiarizing myself with the process and getting in-depth knowledge of the small slices of Django's internals required to do so. Otherwise I probably won't be much use at the sprints. Since looking at a ticket in Trac doesn't indicate whether it passes the filters mentioned in Russell's talk (i.e. not good for Django's design, wrong direction) and I haven't been part of the Django community long enough to know intuitively, I'd just like a little head start on being able to contribute something of value to Django. So, I'm asking for anyone in the core (or close to it) to specifically point out any low-hanging fruit. This may seem on the face of it to be asking for others to waste time they could be spending supporting proven, trusted Django contributors. However, I think it's not, because I'm asking someone who already knows what's coming up in the queue to take a minute or two to say, off of the top of their head, "These specific tickets are worth working on." In the long run, this will actually benefit the core because (at least) one more developer will be contributing to Django. Given the current state of the work on 1.2, this can easily wait for 1.2 to be released. Thanks, Shawn -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
