Live data from Hacker News

No star, No fix

github.com

21–30 of 104 posts

Re: No star, No fix

#21
post #14

Earlier quoted context omitted.

I fail to see a reason where it would be a violation because of the following reasons: 1) it's a response to a user's request, i.e., not initiated by the repo author 2) it depends on consensus of the user. 3) it's not automated (most of the items from the policy are related to automation). 4) the repo author has no obligation whatsoever of maintaining the project. He is not paid or forced to do it. 5) if the user rea…

It is at least partially automated. The issue was closed by a bot which requires a star to re-open.

That's clearly not the spirit of the T&C's of GitHub.

Re: No star, No fix

#22
This is ridiculous. Not every issue means someone likes or even uses the codebase.

Automated scanners, fuzzers, security researchers, and people who found an issue via a dependent codebase, are all examples where an issue might be filed but the person otherwise has no interest.

What a nonsense thing to have. It's not harmless, especially for large projects. It'll discourage and even runs the risk of artificially covering up potential security issues.

Re: No star, No fix

#23

Gaining a permanent reputation for petty authoritarianism, even with contributors who clearly want to help versus gaining one (1) point on GitHub Truly craven that this is coming from an automated bot. The extent to which social media likes have broken peoples' brains is something to behold.

understood

Re: No star, No fix

#24
post #2

I wonder if this goes against github's "no automated starring" policy [0] (that people have been banned for in the past). Maybe "coordinated inauthentic activity" ? Either way, feels sleazy. [0] https://docs.github.com/en/site-policy/acceptable-use-polici...

I fail to see a reason where it would be a violation because of the following reasons: 1) it's a response to a user's request, i.e., not initiated by the repo author 2) it depends on consensus of the user. 3) it's not automated (most of the items from the policy are related to automation). 4) the repo author has no obligation whatsoever of maintaining the project. He is not paid or forced to do it. 5) if the user rea…

It's quid pro quo, isn't it. The repo is buying stars with bug reporting as currency.

Which may well be against GitHub rules but more than that, it's a stupid thing to do. Bug reporting helps projects get better. They're blocking real bug reports until they get a star. Seems like self-harm to me.

Re: No star, No fix

#25
post #7

Why the negative sentiment against this? It doesn't cost people anything to star a project. Whether it is a PR or not, the maintainer still had to review and maintain the code and that is time they will spend. The more stars a project gets, the more support it gets. It's not like you pay for stars or it is burdensome to click on the star button.

I have a family member who would get upset when others would not like her Facebook posts and would message us about it. (It was one of the reasons why I stopped using FB.) OP's submission reminds of this family member.

Re: No star, No fix

#26
I don’t think I have ever starred anything on Github. I think in this sort of situation I would add the star and remove it once the fix is added.

Re: No star, No fix

#27
post #22

This is ridiculous. Not every issue means someone likes or even uses the codebase. Automated scanners, fuzzers, security researchers, and people who found an issue via a dependent codebase, are all examples where an issue might be filed but the person otherwise has no interest. What a nonsense thing to have. It's not harmless, especially for large projects. It'll discourage and even runs the risk of artificially cove…

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.

Re: No star, No fix

#28
post #26

I don’t think I have ever starred anything on Github. I think in this sort of situation I would add the star and remove it once the fix is added.

I'll star a repo when I want to add it to my "favourite" or "interesting" repos - they are all listed under "Your stars". Is there a better way of achieving the same?

Re: No star, No fix

#29

Seems obnoxious without a doubt, and particularly egregious if reporter is bringing/offering a fix. But maybe I should try to be open-minded about this? Issues that provide even badly written bug reports are probably doing a service to the project itself. Feature requests OTOH might just be internet strangers requesting free labor on someone's generously-public yet resource-starved passion project. In the 2nd case, a…

> if everyone does this, it will erode the signal of what stars are supposed to mean.

What signal? To me, starring a Github project means "I'm interested enough in this project to want to be able to find it again". That's a significantly lower bar than the poster had here, of "I've a new feature proposed for this project, and I'm even interested in implementing it myself if the maintainer agrees".

There's a loose correlation of stars with quality/popularity/ activity. All of those correlations should become stronger by having active users and bug reporters star the project.

Re: No star, No fix

#30

I agree with this. If you use some software (and its author cares about internet points), you can at least give it that star. It's better than paying with money, and if you are requesting a feature it makes even more sense to pay with a single click of a mouse. Show some appreciation, people

It seems ludicrous to have to star a project for lacking a feature you need. What's next, starring projects for having glaring security problems?

The person that asked for the feature clearly uses the project and this is usually the case. USERS of a project ask for features
Post reply on HN