Hackathon progress

[denise]

With six days left in the June Hackathon:

All open: 633 (down from 681)
All resolved: 2104 (up from 1987)

Six days left to go to get that number under 600 open bugs! Check the lists of unassigned effort-minor bugs and unassigned from-suggestions bugs, and see what you can do; or, help out our committers and do some code review. (Current needs-review count: 28!)

(And, someone brought up the fact that they don't see the same numbers I see -- the missing count in your Bugzilla queries are security-issues bugs, things that are kept quiet until they are committed because they are possible security problems. There are three of 'em with patches waiting for review and the rest are open, so it's probably better if you aim for slightly under 600.)

I totally know we can make it, even if we do keep opening up new bugs as we go. *G* 33 bugs in 6 days is well within our range!

Comments

Bug etiquette question, I suppose

[aedifica]

If I'm going to be at a convention the next couple of days and know I won't get to my two assigned bugs during that time, should I unclaim them so somebody else can? Or is it OK if I hang on to them for after the con?

Re: Bug etiquette question, I suppose

[denise]

It's absolutely fine to keep 'em, especially if you have a good sense of how you're going to fix them! Unassigning is for when you know you aren't going to get to them in the next month or so, or you're bored and don't want to do them anymore, or you're stuck and can't get anywhere on 'em.

Re: Bug etiquette question, I suppose

[aedifica]

Thanks! (And I normally would have no qualms about keeping them for the length of the con plus a bit, but I thought the hackathon might change things.)

Re: Bug etiquette question, I suppose

[denise]

Hee. THere are 438 other unassigned bugs for people to pick from, I think we'll be good :)

[deborah]

I was doing so well! And helping! And then a certain person (NAMED fu YOU SHOULD ALL BLAME HER) pointed out that maybe one of my patches had UI-change implications we should try to minimize and warn people about, like some kind of party pooper,and so it's her fault I got totally slowed down. :P :P :P :P

(That was sugar-crash-ese for ♥♥♥♥♥, by the way.)

[denise]

*snerk* OH SURE BLAME fu, IT'S ALWAYS HER FAULT

<333

[foxfirefey]

http://bugs.dwscoalition.org/show_bug.cgi?id=581 -- we might be able to kill this since it's part of the main update page revamp anyway

[denise]

Whups, yes -- I left a comment on the bug, but forgot to resolve it LATER.

[foxfirefey]

We just haven't gotten a CLA for this one:

http://bugs.dwscoalition.org/show_bug.cgi?id=2073

I'm going to make a new tag in dreamscapes called ":limbo" for instances like this. But since nobody can work on this theme until we have a CLA and we're not getting any contact back, let's not have it cluttering things up for now.

[ninetydegrees]

There's another submission like this one and I tagged both :no cla yesterday or the day before. But if you think :limbo's a better tag...

[foxfirefey]

I think they could both have their uses-- :no cla says what it means, and :limbo means that it's quite possible that we'll never get it. I mostly want to apply :limbo to things that are very long periods with no response. Thoughts?

[ninetydegrees]

I don't really see the difference, tbh.

[denise]

:nocla is temporary and the submitter says it's on the way or will be soon; :limbo is once it's been a few months and is likely to be permanent.

[ninetydegrees]

Hmm. Ok. Thanks!

[yvi]

Time to fix some review- patches, me thinks! :)