This is a list of bugs that will serve as a good introduction to the Dreamwidth development workflow. They involve varying levels of rummaging up to your elbows in the guts of the code but I can promise that we'll all be only to pleased to help :-) If in doubt, just take a look at the list of things real DW programmers do...

There was a fairly detailed specification in comments on the bugzilla pages for each bug (the ones I'm linking to) unless otherwise stated. As of March 2014, our issues-tracker is temporarily down. If any of the bugs on this list catch your attention, drop us a comment and someone will reconstruct the full bug report for you so's you can get going with it.

One-line fixesIdeal for learning your way around Dreamhacks & github!

Bug 2324: delete some code! (Uh, I should maybe point out that my first "effort-minor" patch "just" involved deleting some code? And turned out to be Rather Complicated. But this one should be okay, and if it isn't then you have every right to make me walk you through it. ;) )

Bug 2859: add a sentence of text (and, if you're feeling really wild, a link!) to the "manage filters" page. This is to signpost the easiest ways to modify someone's membership in multiple access/subscription filters (as opposed to the easiest ways to add or remove batches of people from a specific filter).

Bug 4546: needs an error page writing and splicing in to the correct bit of the process. Things choke when you try to upload .BMPs as icons!

A bit more rummaging involvedI also came across a bunch of stuff that I thought "hmm, might be interesting". These are all well-structured and well-specified, and in most cases you've got something to crib off (in the sense that other bits of the codebase already display the desired behaviour, it's just a case of making sure This Bit does too). Look at these if you're after something to cut your teeth on!

Bug 2871: Button to Bulk-Delete 0-Entry Tags [oh, that's interesting, I didn't include this one because it Looked Like Work; if it's still hanging around when I've finished exams and all of the bugs I haven't touched in six months, I'll have a play with it then ;)]

no subject

That would be brilliant - I haven't used my DreamHack yet (and need to get it up to snuff Github-wise, etc. sometime soon!), but this just seems like something so small & well-suited to something I'm good at (describing things concisely AND vividly) that I'm willing to nibble as soon as I have space to breathe again.

no subject

Thought: is there an unofficial policy on how long a bug should be left as bait? I mean I would claim some of these because I love working on tiny bugs especially as a break from bigger stuff but babydev bait is awesome so... advice?

no subject

I am not the boss of here [I just have ambitions! ;)], but unofficially I'd say that anything under bug number 5000 (picked fairly arbitrarily as a recent milestone!) is always fair game, but I'd like anything more recent than that to be left for ~2 weeks after initially being posted here to give people a chance? Though again that is super-arbitrary... but yes, please don't feel you have to leave ABSOLUTELY EVERYTHING <3