dw_dev | Bugzilla cleanup: unassigning "abandoned" bugs

We currently have 196 bugs in the ASSIGNED state, many of which have been assigned for a while, or are assigned to people who seem to have left DW development. In order to clean up Bugzilla a bit, and in order to make sure that wanted features don't wind up languishing further, I will be going through Bugzilla sometime in the next week or two and unassigning "abandoned" bugs -- bugs that are in the ASSIGNED state that have had no activity on them since 1 January 2011.

If you have a bug assigned to you that has had no activity since then, and you do still intend to work on the bug, just leave a comment on it saying "Still working on this!" If I unassign a bug for appearing abandoned and you're still intending to work on it, feel free to reassign it back to you.

If there's a bug you have a partial patch written for and have gotten stuck, and the reason the bug looks abandoned is that you haven't been able to get past the stuck-ness, you can attach the patch to the bug without adding either the review or commit flags. Be sure to label the patch "partial implementation", or note in the comments when you attach the patch that it's not a working patch!

If there's a bug that you wrote a patch for and the patch didn't pass review, and the bug hasn't been touched since 1 January 2011 to revise the patch based on the review, I'll unassign the bug for someone to come along and update the patch and revise it based on the review feedback. If this happens, you'll still be credited for the patch!

Flat | Top-Level Comments Only

Fair enough. I have to admit I'm not really active in development at the moment, so it makes sense for someone else to pick up the bugs I had my eye on. I'm sure that when I do plunge back in, there will be bugs available that match my extremely limited skill-set!

We will always welcome you back with open arms :)

Does it make life easier if I go unassign the two I have? I'm unlikely to touch them for a while, work is interfering with my life!

I have http://bugs.dwscoalition.org/show_bug.cgi?id=76 - the main/alternate account system, which I'm still a bit wary of after the lengthy and useful discussion a while back which, while useful, seemed to indicate at the very least an issue with perception of privacy that may indeed be a gaping problem. So I've cooled a little on that one.

I also have http://bugs.dwscoalition.org/show_bug.cgi?id=90 - seperating out openID users as a category for comment screening. I think my dreamhack has code to do this that just needs solid testing, I ran out of time and patience to test all 4 places it changes as all 4 categories of user. I should resubmit that and give it up to other people to test.

I was tempted by the killfile feature in the recent "most wanted" post, but I just have way too much on my plate at the moment.

I would kill for that patch to bug 90! Upload it and indicate what you've tested already and what still needs to be tested and reassign the patch to me, and I'll do the testing and fix up anything that doesn't work?

Bug 76 -- yeah, I don't blame you for being wary. I'm just as wary. I'm pretty sure that no matter what we do there, we'll piss off someone. Heh.

I think with 90 I really got as far as "This really should work unless I've missed something obvious". Trouble is, it had tentacles all through other stuff - I need to check my correspondence outside bugzilla because I'm pretty sure Kareila and I had a discussion about much needed refactoring because there was no canonical list of user classes - there were at least 2 different things that used the "anon/logged in/logged in and trusted" heirarchy, but they each had their own list .. etc. So I'll dust off my code and try to find my latest patch and see if it still kinda fits the code as it is now. but from memory, when I left it, it was basically working.

Awesome! I will happily do the testing and patch-refreshening from there (and honestly, our general theory is, if it works as is, put it in, and then open another bug to refactor the code later).

Meanwhile, I forgot to say: I hope work stops eating your life soon! And not just because we miss you. :)

This gig or something else will continue to suck time for a while, but I may be able to squeeze a few hours out here and there. I need to finish unpacking and sort out my study, then I can be much more efficient with actual projects. Just in time to move again, probably...

You always wind up with that one box you move faithfully from place to place for a decade or so, only to open it at the end and discover, like, an empty bottle of shampoo and four pairs of underwear with holes in them. :)

(In my case, it's a huge trunk full of old notebooks. I fear what is in those old notebooks.)

Actually, I did upload a patch for it. I'll upload my test notes, and take a quick look at my dreamhack to see if that patch represents the latest state of my code, but feel free to run that patch and see if it even patches against the current tree :)

Whee, comment storm. I've found another patch. I recall at some point realising I'd misunderstood a chunk of the logic behind one of the tests. I think the patch I'm about to upload fixes that :) I've also found my testing matrix, which basically stops at the captcha, but seems to indicate that everything was ok up to there.

Do I have to go over all my bugs and leave a comment (mmm bugspam!) or am I mostly exempt from this? ( I will go over my bugs and unassign things I probably won't be playing with, though )

You can be exempt, but do unassign anything you don't still plan on doing!

I will, but I really should note somewhere that pretty much all of my bugs can be snagged from me at request if someone *really* wants to do one of them.

That sounds good. Right now I freeze up any time I think about working on them, and then I go think about something else instead. (This also applies when I think about unassigning them.) Having them unassigned will reset that! I'll try again sometime in the future.

Oh no! I know all about the "stressed out at the thought of it", so hopefully a fresh start will help. :)

I do intend to work on all the bugs assigned to me. Eventually. That said, if you need one dealt with quickly and someone is interested, feel free to yank it from me.

Well, I guess it's the graceful way to bail out until I get my life back on track... :( It's pity to ditch bug 2451 (xml-rpc trust groups support) which was my original reason to get involved with dw-dev. But even though the patch was almost accepted at some stage, an amazingly insightful discussion at http://dw-dev.dreamwidth.org/71429.html made it obvious that my design sucks (which I suspected all the time ;) and I don't have enough energy/concentration to keep improving it so it's acceptable for everyone, APIs are important, the code can be ugly as long as it works, but the part which is exposed to users (programmers) has to be perfect, and I can't do it alone. I don't know if it even makes sense to return back to xml-rpc, if the atom protocol is the future.

Bugzilla cleanup: unassigning "abandoned" bugs

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject

no subject