The return of the fix-it marathon

[yvi]

So, at the end of June, denise called for a fix-it marathon.

http://dw-dev.dreamwidth.org/11183.html

Let's have another one.

But let's make it two-fold:

First layer: blocking-launch

http://tinyurl.com/cjw9wk currently has 48 bugs: 21 assigned and 27 new. Let's try to bring that number down. A lot of these look scary, and some of them are not effort-minor, so I'm thinking of a bit of a low goal: by August 15, have the number of unassigned ones in there down to 15, which means 12 newly assigned. And by that time, have only 30 of the bugs left, which means 18 bugs fixed in 13 days.

(Edit: That's 'blocking-launch+', not 'blocking-launch??' or 'Target Milestone: Launch'. I am not sure which of these are the best indicators...)

I have two blocking-launch bugs assigned to me now. Who's with me?

Second layer: babydev

You're new to this whole thing? blocking-launch bugs are way over your head (and if you think that I am pretty much with you :)) by this point? But you're interested in tackling something, you just don't know what?

If you don't already have one, get yourself a Dreamhack.

The effort-minor keyword currently has 180 open, unassigned bugs. There are still a few left on my recent babydev bait post. If you want to do something and can't find anything in that list or don't know how to start, comment here or join #dw_kindergarten and I am sure there are people there including me who can help you find a bug to tackle and then tackling it.

And remember, this is just a suggestion. No-one is under any obligation to do any of this. I just thought it would be nice to get some of these bugs out of the way. :)

Comments

[av8rmike]

(And see, I was partially wrong with my other answers!)
I just didn't want to add to thread/comment bloat, since we're getting kind of off topic, but ask away!

[ninetydegrees]

Is there a better comm to ask these questions?

As I said, I didn't understand what you meant when you said: "I don't have one, but what I *do* have is a local copy of our "s2team" repository, to which I can commit patches. All you really need is Mercurial and a copy of one of the repositories so that you can generate patch files."

[av8rmike]

I'd have suggested dw_styles, but since that comm has limited posting access, here we are.

Anyway, Mercurial is the version control system Dreamwidth is using. There's a page on the Wiki that provides a little more information about it, but it's basically a distributed system with multiple repositories instead of just one (like LJ uses). About six months ago, afuna set up a Dreamhack for the Styles team to use, complete with its own repository. This made sense because there were 6-8 of us on the team working with different components of Core2, so we all needed commit access. We could all kick stuff around without disrupting the "main" repository.
However, there aren't as many of us doing active S2 development now, so we're not really using the s2team repository any more. As I mentioned up-thread to yvi, I'll probably need to try setting up a development environment and follow the established workflow for generating patch files. Am I making sense?

[ninetydegrees]

You mean like this? I never noticed the name of the software DW uses. My apologies.
You are. Thanks for the explanation.