Babydev bait

[denise]

Last week, afuna made a list of babydev-bait in dw_dev. Well, we all rock so hard that most of those bugs have been patched (and the ones that weren't have been claimed), so it's time to make a new list.

All of these should be good starting places for someone who's just getting their feet wet with the codebase. I've scored each one on a level of 1-3, where 1 is "really really easy" and 3 is "still suitable for a beginner, but a little more complicated".

If you're just getting started with us, check out the Getting Started and the Beginning Dev Checklist!

NOTE: April 15 is the milestone freeze for open beta. Past April 15, we won't be checking in any patches that don't patch an open-beta-blocking item. This doesn't mean you shouldn't work on things that aren't open-beta blockers -- your code will get reviewed and checked in, just not immediately! (And those two weeks between milestone freeze and open beta launch can be a good time to work on something more complex.)

Some of these require perl knowledge; some require Javascript or CSS knowledge. If you look at one and go "I have no idea how to do this", try another one! There's a wide assortment in here.

( Babydev bait! )

Distributed version control? Whu?

[echan]

I highly recommend a perusal of Intro to Distributed Version Control (Illustrated).

From the intro: "Traditional version control helps you backup, track and synchronize files. Distributed version control makes it easy to share changes. Done right, you can get the best of both worlds: simple merging and centralized releases."

In short -- this is how we have lots of devs, and not just mark. It's a bit more work than just opening a file and changing the code, but it's really really useful.

For more information on the specifics Dreamwidth uses, check out the Dev Version Control wiki page.