Assigned-bugs hackathon!

[denise]

I checked tonight, and we've got 571 open bugs. That's a lot! 146 of them are assigned with no patch, and if we could make some inroads on that number, we'd be able to knock down the total open number a hell of a lot.

So, here's my hackathon challenge! If you've got assigned bugs, let's do whatever we can this week to get that number down. I'll start; I have 8 bugs assigned to me without a patch, and while some of them are waiting on other things to get resolved first, some of them are things I've just been putting off because I don't know exactly how to do them or was running into problems.

I've already yelled for help on what I'm stuck on, so I'll turn to y'all: what can I help you with on stuff you're stuck on? And if not me, who else can help you? A bunch of the existing assigned stuff is really complex, so let's all work together and see how much we can improve things.

Ideally, I'd like to get that "open" number down below 500 by Sunday night, and double ideally, the "all unassigned" number (currently at 386) down under 300.

*salutes you all*

Comments

[yvi]

Did you get my comment about one of your bugs having the wrong patch uploaded?

My currently assigned bugs:

http://bugs.dwscoalition.org/show_bug.cgi?id=312 has patch

http://bugs.dwscoalition.org/show_bug.cgi?id=1365 is way too huge to tackle in one week

http://bugs.dwscoalition.org/show_bug.cgi?id=1574 waiting for another patch

http://bugs.dwscoalition.org/show_bug.cgi?id=1670 has patch and is the one blocking 1574

http://bugs.dwscoalition.org/show_bug.cgi?id=1685 I'll try to tackle that :) However, I have no idea how to because the preview code is confusing me.

http://bugs.dwscoalition.org/show_bug.cgi?id=1748 has a patch

http://bugs.dwscoalition.org/show_bug.cgi?id=1850 is only open because there might be new styles

http://bugs.dwscoalition.org/show_bug.cgi?id=1878 will tackle that one tonight and woule like help for making it pretty

http://bugs.dwscoalition.org/show_bug.cgi?id=1881 patch rejected, will re-upload

So I might be able to finish a few :)

[denise]

Well, I know I got the comment, but I probably didn't associate it with one of my patches. *G* Will look into it.

[cesy]

Ooh, 1685 will be useful. 1574 is going to be so cool. Yay for 1748 and 312.

For 1878, two columns was suggested as a solution. Would that work for the pretty, or did you need more detail or another idea?

Also, much yay for subscription filters that work now. Thank you!

[yvi]

Would that work for the pretty, or did you need more detail or another idea?

Mainly I am wondering because right now it says

Optional: Include in one or more access filters. You must grant access to this account by selecting the first box above in order to add them to any access filters.

and then come the boxes. So I could either have two columns and title the other one with

Optional: Include in one or more reading filters. You must subscribe to this account by selecting the second box above in order to add them to any reading filters.

Easy, but boring. I was wondering if there might be anything shiny-er :)

[cesy]

Hmm. How about hiding the filters unless the box is ticked, for both types?

[yvi]

Like the color chooser? Would require JavaScript, which I seriously suck at...

[cesy]

Mmm. Could be shiny, though.

[yvi]

Yes!

If anyone with JS knowledge wants to take it, just give shout. I am not sure I want to learn JS for this :) But I can also implement a non-shiny version first, in the interest of having the functionality.

[yvi]

http://bugs.dwscoalition.org/show_bug.cgi?id=168 is evil. Anyone got any ideas on how to make the preview happen? The code is confusing me because I can't seem to find out how update.bml calls the preview. Or maybe I see it, but just don't understand.

[cesy]

168 does look evil, but I guess you meant 1685 ;)

[yvi]

Ouups. New link: http://bugs.dwscoalition.org/show_bug.cgi?id=1685

[afuna]

Basically, update.bml uses JS to submit the form /preview/entry.bml, which opens in a new window.

But I'm thinking now... maybe what you want is something like how the comment preview does it, instead of how entry preview does it.

Comment preview: no javascript; you submit the form as a preview, run cleanhtml and whatever formatting and print it out above; print the original form again below.

[yvi]

Hmmm, yes, that sounds like it would make more sense. No JS is alwas good and as far as I can see, the comment spellchecking is also easier?

[afuna]

Yeah, it's not as persnickety as a JS implementation would be, I think. Also likely to work for more browsers *g*

[yvi]

Hmmm, turning out to be not that easy :/ There's LJ::Talk->make_preview , but it needs a talkurl.

I am wondering whether what faqedit does might be a good idea.

[afuna]

Oh! I didn't mean use comment preview, exactly. More, do what comment preview does. (It likely wouldn't work, anyway, since the suggestions does some formatting and, also doesn't allow HTML, so you'd need to emulate that exactly).

[yvi]

Heh, I think I was thinking way too complicated. I have now already coded a preview to appear at the top when pushing a preview button. I think I am going to get this done today. Won't be as pretty as entry-preview, but we also don't need that for suggestions.

Right??? :)

[afuna]

I think that's fine!

[afuna]

Or maybe what faqedit does -- if that gives you an idea, go for it. (disclaimer, I haven't looked at faqedit in great detail *g*)

[turlough]

http://bugs.dwscoalition.org/show_bug.cgi?id=1878 will tackle that one tonight

Yay!!

[zarhooie]

And bug 23!

[yvi]

Bug what? I didn't hear you, you need to talk louder.

[zarhooie]

BUG 23.

And while you're at it, Bug 496 could use some love and attention. I know how much you wanted to work on that feature when we talked about it yesterday. *ducks and runs away quickly*