The thing I'm probably most use at is stuff to make working with S2 easier, both for users and developers. Potentially slightly automating some of the stuff where we have to make a change to every single layout individually, like the things in kaberett's babydev bait list where they say This is additionally tagged effort-higher, but that's because it's a small change that needs applying in an awful lot of places.. Also using S2 functions to calculate 2X the sidebar width, rather than asking users to input 1X sidebar width and 2X width separately. Tidying up the S2 customization wizard in a range of ways; if I get really ambitious, I would like to make a much easier way of using someone else's pre-made style, whether that's CSS or S2.
There's also couple of odd little accessibility things have been itches for a while, such as allowing spell-check in the subject field of the post entry page.
Basically what I'm already good at is awkward S2 stuff; I can do conversions of submitted themes and styles if that's a help, but I know there's a few people already working on that, so I'm probably more valuable doing bits that are somewhere in the grey area between actual styles and backend. And I'd like to learn more about parts of the codebase that aren't the style system, perhaps by starting with some of the one-line fix / babydev bugs.
no subject
There's also couple of odd little accessibility things have been itches for a while, such as allowing spell-check in the subject field of the post entry page.
Basically what I'm already good at is awkward S2 stuff; I can do conversions of submitted themes and styles if that's a help, but I know there's a few people already working on that, so I'm probably more valuable doing bits that are somewhere in the grey area between actual styles and backend. And I'd like to learn more about parts of the codebase that aren't the style system, perhaps by starting with some of the one-line fix / babydev bugs.