| > This topic could have been easily brought up after the holidays... but why wait? It's a topic to be discussed. The way you're going about this entire conversation is simply too much. It sounds like you've reached out to multiple personal emails, created multiple issues, responded to those issues asking for updates, and brought the issue to social media in less than a day. During the holidays. That's overwhelming and doesn't put the devs on your side. As others have mentioned, even if you're right, you really need to give the devs some time to think through the alternatives, consider your argument, come up with a solution, and implement it. This takes some time. Removing information from a database may not seem hard to you, but you don't maintain the service. Sending a pull request is fine, but maintainers don't blindly merge anything. They have to review it, make sure it's the policy, quality of code, etc. that they want in the product, merge it, and deploy to prod after possibly testing everything. Give it time (not measured in hours) and work with the developers. Edit: This is exactly why maintainers don't blindly accept pull requests: https://github.com/gitpay/website/pull/4#pullrequestreview-1... |
Not at all. All that I've done is sent an email.. waited to hear back. Haven't heard back, thought it'd be a good idea to submit a pull request, and then took the conversation to github.
I have not been badgering the dev on multiple emails or social accounts at all.