Need a sarcastic response to a support interaction as an open source project maintainer? Look no further!
- I’ll just retype the docs into this email for you.
- Please send me an email personally, because the mailing list is full of other people who can help.
- I don’t need to see any code to answer that.
- Just paste the very last line of the traceback please, I’ve memorized all the potential codepaths of your application.
- Of course I believe you’ve found a fundamental bug in the system. You’ve been using it for almost 10 minutes.
- Why would you learn to use an interactive debugger?
- Don’t sweat it, I am a master at Engrish.
- That docs typo is important enough for me to fix right now; don’t bother creating an issue for it.
- Please don’t submit a pull request, just type the diff manually into IRC, I’ll take care of it right now.
- Let’s talk about variable names, I really wasn’t doing anything else.
- When I said ‘dont do it that way’, I was just making idle conversation.
- I love answering the same question from you every two weeks.
- It totally makes sense for you to do it the hard way over and over.
- Please, please let me convince you to use my free software because I know you’re going to contribute back later.
- The dogma you’ve gained from your six months of experience is indeed how everyone should do it.
- You’re right, it is too complex. Why didn’t I think of that?
- Ignoring conventions is completely reasonable at your experience level.
(Source: plope.com)
