Yeah, I guess self-promotion isn't something I'm a fan of but here we go: Here are the basics, I've been an open-contributor since I was 14, starting as a contributing author for linuxforums.org, and quickly moving into the Gnome Project. I am a Gnome Foundation Member as well as an Ubuntu Developer/Packager, I have maintained and packaged several Gnome packages and have been working in C/Mono/Python for some time. About a year ago I started a consulting company with some friends which focused on large-scale datamining as well as custom web-dev, platform of choice was Django. Since I have used Django (in some capacity or another) on almost 30 individual sites/contracts I felt like it was time to give a little back, so I decided to attend the Django sprint at Pycon. One discussion we started was 'neat stuff I want to have when testing my site' after 10 hours of code, a few gallons of 'Gentleman's Jack' and more Pony stunts than I can recall, GSoC got mentioned. I decided that the scope of testing stuff I wanted was large enough that I should see if the community as a whole wanted to see the same features/fixes/additions.
I like to think that I did a solid job estimating time/effort for most of my tasks, demonstrating a solid understanding of what lies ahead. (Something worth a lot in a GSoC proposal) Hope you are sufficiently convinced! -Kevin Kubasik On Wed, Apr 1, 2009 at 1:33 AM, Russell Keith-Magee <freakboy3...@gmail.com>wrote: > > On Wed, Apr 1, 2009 at 11:02 AM, Kevin Kubasik <ke...@kubasik.net> wrote: > > > 3. Utilize the new Windmill test support to provide coverage of the > Admin > > interface. This is an extremely large task overall, but given how easy > > Windmill has made the creation of tests, I hope that I will be able to > > provide coverage of a majority of the admin's functionality. This will > not > > include support for the django.contrib.gis namespace, but I will try and > > test all other namespaces that have Admin integration or functionality > > (namely auth, admin and comments). > > This proposal doesn't really capture the dependency between this task > and fixing/implementing #4788. This isn't a big problem, but it's > worth mentioning. > > > 4. **New** Cleanup/Expand the current testing API to include a few new > > super-awesome features/functions. Namely, I want to implement/integrate > the > > following tickets (listed in order of priority): > > a. `Skipping Tests <http://code.djangoproject.com/ticket/4788>`_ > > b. `assertNumQueries <http://code.djangoproject.com/ticket/5416>`_ > > c. `assertContext <http://code.djangoproject.com/ticket/5333>`_ > > I haven't checked for certain, this one may not be required any more > following the changes to the test response.context introduced in v1.1. > > > d. `assertNoBrokenLinks <http://code.djangoproject.com/ticket/5418>`_ > > e. `Mock Request Creation Outside of urls > > <http://code.djangoproject.com/ticket/9002>`_ > > f. `fixtures with doctest <http://code.djangoproject.com/ticket/5624>`_ > > h. `TestOnly Models <http://code.djangoproject.com/ticket/7835>`_ > > #7835 is a big one for me - this would allow for much better testing > of the admin, as well as admin tests that were actually associated > with the admin contrib app. It would also significantly simplify the > process of testing schema evolution type apps, or any other > application that operates on models. > > > i. `reStructured Text Checker <http://code.djangoproject.com/ticket/7474 > >`_ > > j. `fuzz or datagen testing <http://code.djangoproject.com/ticket/5419 > >`_ > > On the subject of these tickets - it would be worth mentioning in your > proposal that many of these tickets already have patches in various > forms. At least part of the task here is to review and update any > existing patches. This goes some way to explaining why closing 10 > non-trivial feature tickets is only scheduled as 5 weeks part-time > work. > > Other than that - this is looking quite attractive as a proposal. The > only additional suggestion I would make would be to beef out the > "About me" section. There are two parts required for your project to > be selected: > > * Your proposal needs to be sound and of interest to Django > * We need to have confidence that you are someone that is capable of > bringing the proposal to completion. > > You've pretty much got the first bit sorted now, but you haven't > really got much to convince us of the second point. > > Yours, > Russ Magee %-) > > > > -- Kevin Kubasik http://kubasik.net/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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 -~----------~----~----~----~------~----~------~--~---
