Live data from Hacker News

No star, No fix

github.com

51–60 of 104 posts

Re: No star, No fix

#52
post #37
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…

You are assuming such drive-by issues are actually valuable; to me it is not 100% self-evident, especially when most projects do not have shortage of issues anyways.

Some are, some are not. Assuming all are valuable would indeed be incorrect, but so would assuming all are worthless.

In this case it's a "hey I want to make a patch, would you accept it?" type of question, and not really a bug report or feature request as such. I'd say that's valuable.

Re: No star, No fix

#54
post #17

Earlier quoted context omitted.

My point exactly, if you don't think it's worth starring why even use it let along issues and pr's. If GH had levels of stars it might have be been better. Can't projects say they'll only support people who really like the project or are people thinking OSS comes with entitlements for unpaying users.

> if you don't think it's worth starring why even use it let along issues and pr's. - it's a dependency downstream and it's breaking my actual project. - I'm in evaluation/research phase for multiple repos and am not committed to that specific tool. Actions like this actively make me NOT want to star such behavior, nor even use the tool if I can help it - because I don't fundamentally use stars as a popularity stick…

> it's a dependency downstream and it's breaking my actual project.

You depend on it but so much as clicking in a star button is burdensome? Come on!

> I'm in evaluation/research phase for multiple repos and am not committed to that specific tool. Actions like this actively make me NOT want to star such behavior, nor even use the tool if I can help it

Then the author's don't want you to use their project, so fork it or move on.

> because I don't fundamentally use stars as a popularity stick and don't care. I'd rather you prompt me to post a bounty or donation instead. Yes, that's how much I hate that system; I will pay money to not be involved in it.

This isn't about you, it's a button the author cares about, so support them with it for their sake, if they want money they will ask for it.

> I'd rather just pay the project directly instead be a part of a statitic that says "we got X stars on our repo please fund us" VC pitches.

You are not part of any of thay, you are just supporting someone making their hard work free and open source in the way they want to be supported. This boils down to how you wish to support them and how you wish the system worked without a single consideration into their right to not support you for any reason at all. The software is already FOSS, you downvote their post and anything defending them because what? Being free and open isn't enough, you also deserve free labour and in your own terms?

Re: No star, No fix

#55
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.

Is your family member providing you free services alongside free AND open software?

Re: No star, No fix

#56

Earlier quoted context omitted.

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

The person in the linked GitHub repo is not asking the maintainers to develop the feature. They are asking if the maintainers would like the issue author to develop the feature. That's what is particularly disgusting to me about this star-begging-bot.

Re: No star, No fix

#57
post #19
post #15

Earlier quoted context omitted.

If you like it starting it makes sense, if you don't why open issues and do pr's?

There are trivial responses to your question, but you didn't address the issue I raised

I thought it was obvious. Not all projects get stars, the ones people use and like the most get more support in form of contribution which could be issues and pr's or other types of support. For people who don't care abour stars it means nothing, for those who do it means everything.

Re: No star, No fix

#58
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.

Because people don't like to drink a verification cans. > It's not like you pay for stars or it is burdensome to click on the star button. Imagine being allowed to comment here only after [starring] something. It's not like you pay for [stars] or it is burdensome to click on the [star] button.

Don't you have to get like 500 karma before you can up/down vote on HN? Not far off right?

Re: No star, No fix

#59
post #34

What are stars even worth? Certainly not the number of possible contributors this chases away (I see issue reporters as contributors as well since they’re spending effort finding/debugging what you would have to do at some point anyways) All this for a measly 1500 stars

Maybe to put the repository on a resume. Github also gives out free Copilot licenses to active contributors of opens-source/free-software projects but they don't say specifically what the requirements are. Maybe if you own or contribute to a repository with many stars you're eligible for that.
Post reply on HN