Friday, Jul 2, 11:20AM

[karzilla]

Bug counts: resolved 201, assigned 10, needs-review 6

I have to remind myself that not everyone is as fearless about rearranging the guts of the code as I am.

Hence, I just changed my mind and accepted a patch from a new contributor that I had rejected a few days ago as being too small in scope. I'll open a new bug for the gut rearranging and probably do it myself.

I hope I didn't scare the newbie away!

Comments

[foxfirefey]

Oh man oh man, I have found something that really needs refactoring while trying to figure out this bug.

[kareila]

Go for it! Or if you don't enjoy refactoring as much as I do, outsource it to me :)

[cesy]

Thank you. As a newbie, it really helps if you can let the original bug pass and open a new one for someone else to do the extended bits. I think there was a term for this, actually, when a bug grows and grows until it scares people off.

[kareila]

I will try. I think it would bug /me/ knowing that someone else was planning to take out my work and do the whole thing differently; I'd rather get it "right" the first time. That's an attitude I picked up from Mark early on, actually.

[cesy]

Well, maybe give the user the option, then - for me, I'd far rather get it fixed, knowing someone else will refactor it later, than have to give up on development altogether because I can't do the refactoring/expansion of the scope. That was why I dropped out of Dreamwidth dev in the first place - the scope got expanded beyond my ability and I couldn't get anyone to help me with it, and wasn't confident enough to argue that the new scope should be a new bug.