"Same cause, different bugs" -- well, if one of them is assigned to you and you fix it, then you should resolve the other one as quickly as possible to let them know that you took care of it. Or, if the other person is already well on their way and is going to be able to solve it, you could let them do it too. I'm thinking particularly in cases where the other person is a newer developer, I'd rather see them fix the bug than someone who won't learn anything by it.
For the blocking issue, you should just talk to the other person. Ask them how far they've gotten, and if they have an ETA (but don't be rude about it, be gentle). If they haven't started, or have barely started, you could ask to take it over.
If you just see something and fix it, though, that's tricky. I don't want people to be frustrated by working on something and having other people trounce their work. I guess it will have to come down to communication and judgment -- talk to whomever has the bug assigned. Of course, if you don't know about a bug for the problem, then you can't really be blamed for fixing it.
Some of the weird edge cases we'll just have to handle when they come up and trust people to realize we're all working to make Dreamwidth a better place.
no subject
For the blocking issue, you should just talk to the other person. Ask them how far they've gotten, and if they have an ETA (but don't be rude about it, be gentle). If they haven't started, or have barely started, you could ask to take it over.
If you just see something and fix it, though, that's tricky. I don't want people to be frustrated by working on something and having other people trounce their work. I guess it will have to come down to communication and judgment -- talk to whomever has the bug assigned. Of course, if you don't know about a bug for the problem, then you can't really be blamed for fixing it.
Some of the weird edge cases we'll just have to handle when they come up and trust people to realize we're all working to make Dreamwidth a better place.