Live data from Hacker News

No star, No fix

github.com

101–104 of 104 posts

Re: No star, No fix

#101
This is unethical if (1) the condition was not made clear before the issue is written, and (2) the user cannot delete their report before it is published. (It is not in the current issue template, and I don't know if it was there.)

1. The issue writer will invest time and efforts, and publish their findings. Nobody's time is free: the maintainer's time is precious, and so is a user's.

2. Now, _after_ the issue is published, the maintainer additionally asks for a certain condition (give money or a star) to be satisfied.

What if the issue writer does not want to give that thing? The maintainer is now in an unfair position: they can still read the published issue, improve their software, but is not obliged to give any feedback or even credit the reporter.

It would be fairer if the condition was clearly conveyed to the reporter before they write any words. The system should simply not allow these issues written by the dissents to be created in the first place, and in that case the funny duck would also not appear before our eyes.

Re: No star, No fix

#102
post #96

Earlier quoted context omitted.

This user was offering to do work and give it to them.

And they have the right to refuse. Do you know how many times my PRs have been turned down after I already finished the work? Sometimes they only accept PRs if you're in their click lol. That's all fine but clicking on a star is so despicable right? What a joke.

Irrelevant. This conversation is not remotely about incompatible ideas or poor implementations.

You attempted to justify the devs policy with demanding users, which is ridiculous on multiple fronts.

Re: No star, No fix

#103
post #87

Earlier quoted context omitted.

Don't forget, nobody prevents the user from opening an issue. If it's critical and the maintainers care, they'll work on it with or without the user's star.

I think you missed the part where the issue was closed by the bot for the user not having starred the repo, in which case - especially on high-traffic repos - the likelihood of actually seeing it is reduced.

Maintainers not auditing issues closed by their bots are irresponsible, but this problem is not related to the nature of the close-triggering condition.

Re: No star, No fix

#104

Earlier quoted context omitted.

You can make the profile private and it’ll hide the stars.

Can't hide the stars from Github itself though. Keeping as much preference data away from social networks as possible is not an unreasonable stance, IMHO.

not a bad idea. in that case you can just bookmark them, no?
Post reply on HN