Earlier quoted context omitted.
> - If you make your project public, it means you want and expect people to use it. no, it doesn't, maybe I have a github project, I want to easily share it with ten of my friends for something, I don't particularly care if other people see it, so I make it public. That in no way implies I want random people to come along with bugs and PRs. > You could at least write some documentation, so I don't waste my time and t…
> no, it doesn't, maybe I have a github project, I want to easily share it with ten of my friends for something, Then make it private. > I don't particularly care if other people see it, so I make it public. Yeah, I see someone else made the same argument. It's a reckless disregard of other people's time and nerves. Build labyrinths and scatter them around the internet. Leave manholes uncovered. Markov chains to trap…
You don't get to decide that.
> It's a reckless disregard of other people's time and nerves. Build labyrinths and scatter them around the internet. Leave manholes uncovered.
That's a *you* problem, because you have wrong expectations.
> Then close bug tracker and post "Abandoned" on the front page.
You don't get to decide that.
> Then say so and then reject them. That's what PR review means. I don't have a problem with rejected PRs. I have a problem with ignored PRs.
Another case of you having wrong expectations. Like in networking, you should put a timeout on all requests. For all practical purposes a request that times out is to be treated the same as a rejection.