[Bug dropped; I don't think this has value in that bug log] >>>>> "Ansgar" == Ansgar Burchardt <[email protected]> writes:
In reading your message, I realize there is an interesting challenge here. When I agree that it might be reasonable for the TC to take a look at something, what is going through my head may be very different than what is going through the head of the person bringing the bug to the TC. Consider the following interpretation of the same facts you present. We had a bug opened in 2012. According to one person, his approach had already been considered and rejected by the maintainer. That person wanted a concrete patch available to prove that it was possible to implement the approach. He wrote the patch and said roughly "Hey, I know you don't like this, and I think we need some outside help deciding which of us is right. I'm going to give you a bit of time in less I've got it all wrong and you're OK with this approach and then I'm going to ask for help." Under those circumstances, I think it's reasonable for the TC to start looking at the issue. In a case where something has been sitting around since 2012, I think it is reasonable to start looking at whether a general policy statement or technical advice could help. No, that was not the tone of Ian's message. I wish it had been. But honestly, yeah, if someone thinks an issue is broken in 2012, and it's still broken in 2017, and that person is hurt and frustrated by that experience, I think it is reasonable for the TC to look at the situation and see if we can help. I'll be thinking things a lot more like mediation, helping people understand, providing policy, providing technical advice than I will override maintainer, provide specific solution. --Sam
