News for hackers. Stuff that matters.
Re:An open source tool to generate a complete backend from a... by mrleinad on Monday October 13, 2014 @06:13AM (#8448133)
There are pull requests from May that haven't been even answered or commented. Am I wrong, or shouldn't it be a custom to at least comment why you're not including it into the code?
Re:An open source tool to generate a complete backend from a... by antirez on Monday October 13, 2014 @08:25AM (#8448404)
No reply most of the times is received as a "I don't care" message by the PR author, while it is almost always lack of time to reply by the project maintainer.
Re:An open source tool to generate a complete backend from a... by jonseg on Monday October 13, 2014 @06:20AM (#8448147)
You are right :( I want to review all pull request with careful, It implies a lot of code and I need find the time.
Re:An open source tool to generate a complete backend from a... by mtrimpe on Monday October 13, 2014 @11:29AM (#8449076)
Just tell them that then... no harm in being straightforward.
Re:An open source tool to generate a complete backend from a... by fubu on Monday October 13, 2014 @03:47PM (#8450221)
This is good advice. I used to help maintain a bit on the bigger size project on Github and our lead developer I think really wanted to spend time looking over and trying to give quality responses. Which ended up sometimes taking a long time or not at all. Unfortunately, it came off to some people as not caring about their submissions. Just a simple message about being busy and asking them to remind you if you forget works wonders.

Example: "Thanks for sending this in. I'm busy right now but will look into it later. If I haven't responded in a week or two, do me a favor and ping this thread."