OK, so an option called “Offline Message Policy” should apparently control how bounces work. Let’s go along with that for a moment, even if I think that’s a stupid idea. Let’s further assume there is a sensible use-case for dropping bounces throughout Openfire as a general option. Also, let’s assume you told me this was essential for the change to be acceptable.
Let’s ignore the fact I told you “you’re dropping groupchat (for example) rather than sending an error” - obviously that wasn’t a clear enough “hint” for you.
Let’s ignore that your way of understanding RFC 6121 seems to be by saying things like “OF should not try to deliver to bareJID”, and “we then should store it or bounce it with error, but NOT try bare JID” (emphasis yours). I was really quite patient in explaining, across 25 minutes, not only what RFC 6121 specifies, but also why I was, in fact, right.
In fact, let’s ignore that you threw away a contribution made in good faith without any reason given until after the fact.
You know what, forget all of it. Pretend I never suggested the patch “might also be useful”.
What you seem to be missing is that my job is basically to keep those customers running on Openfire happy, and my options here are really simple:
Maintaining a private branch without any effort to push fixes upstream.
Making the additional effort to ensure the patches are in a form acceptable to upstream, and adjusting them according to feedback.
I’d much rather do (2). It’s not what we’re actually paid to do, but if all goes right we gain a lot from it, and so do our customers. There’s a trade-off though. I can’t tell a customer, “Oh, look, I fixed this bug which caused a problem in this case, that cost you an hour of time – oh, and we pushed the patch upstream, and spent an hour and a half arguing about it. We’ll invoice you for it all later.” I don’t mind spending some of my own time on these things, either.
Nor do I expect every patch to be accepted, but in general, if the patches are going to get rejected, it’d be nice to know why, and if you’re asking me to review a patch of yours that you’ve done in place of mine – which is frankly pretty rude – then when I say “you’re dropping groupchat”, the ideal respons eis not going to be “I don’t drop groupchat.”
In general, your attitude toward me has consistently been that I have no idea what I’m talking about, and haven’t got a clue. I do not claim – would never claim – to have all the answers and always be right, but I believe I have generally demonstrated within the XMPP community over the past few years that my comments shouldn’t be ignored out of hand – by default at least.
I really do not need, or want, to spend any more of my time, or that of my employer, on this.