Discussion
Search code, repositories, users, issues, pull requests...
porridgeraisin: This is why I built nvim from source, and git pull plugins into the pack directory. I think it's even a static binary. Whatever changes I need I git pull. After they added LSP I have not wished for anything else really, so I stopped pulling. I think I pulled LSP completion API in 0.11 era but that's it.Hate it when people break backwards compatibility. For me it's sacrosanct, more important than absolutely anything else.I only have a handful of plugins so the system works well. And I have a 500 line init.vim (and no other config).Some ecosystems like golang share this principle and so I can freely update packages without worrying about breakages. But other ecosystems(nvim, python, etc) I'm a lone warrior
anuramat: idgi, shitting on the maintainer takes 10x more time than forking the repoI guess he really needed the latest ci/chore commits
Valodim: This was probably near the breaking point before, it just needed an idiot to catalyze.
sevg: I will never understand people like GitHub user “shushtain” in the linked issue.So obviously the guy is behaving like an entitled jerk, but it’s also surely counter-productive (volunteer maintainers are unlikely to respond well to plain rudeness)? Unless the goal isn’t a productive outcome, but just to be mean?
edem: [delayed]
cafebabbe: Humans are notoriously bad at game theory.
yu3zhou4: Good for the maintainer, hope they find peace and do things just for their fun, without needing to deal with comments like that anymore
siva7: I get anxiety publishing open source because of things like this.
bulbar: Genuine question: Why not just close such derailing and burdensome issues and/or block mean people?My guess: People would freak out if FOSS maintainers actually did this.
delusional: > Unless the goal isn’t a productive outcome, but just to be mean?Some people are just mean. They spend their angry little lives walking around "outraged" by any minor inconvenience. They assume every single little happenstance was designed to make them miserable.The greatest thing about having a good education and working with other experts is that I generally don't meet this people that much, but I remember them all too well.
ivanjermakov: This is a bane of all such aggregator libraries, that suck maintetance from other projects into themself. Null-ls suffered from this, too: https://github.com/jose-elias-alvarez/null-ls.nvim/issues/16...The source of a library needs an update every time there is a configuration change in _any_ tree-sitter parser supported.
faangguyindia: I've built many successful services by listening to entitled users so much that I used to talk with such entitled users all day.They are just passionate and most of the times annoyed because something as simple is not being done right.
eviks: Easiest people to understand: someone hurt you (in this case disrupted your workflow, especially if pointlessly like this user thinks), you express the dissatisfaction to the person who did.
sevg: > They are just passionate and most of the times annoyed because something as simple is not being done right.No, this is not adequate justification for such behavior towards volunteer FOSS maintainers.
cjbayliss: The Fandom Menace strikes again.But seriously, this is messed up. People need to learn to treat others with respect and kindness. Hopefully the maintainer is able to simply move on after archiving the repo, and isn't dealing with any mental struggles from dealing with years of entitled users demanding things for free.In popular open source projects this is a recurring issue. I suspect the only way to deal with it is to either shift to a platform that has better tools for moderation, or end the project like the maintainer has done. Let someone else fork it and deal with the users.To clason: Thank you for all the work you did maintaining nvim-treesitter!
siva7: I don't think you've done any of that - at least not for a successful open source project. The topic here is about open source volunteers and not your day job.
elliotec: What successful services have you built because of entitled users?
altairprime: [delayed]
rolandog: Agreed. However, I often wonder if people like that are deliberately (or inadvertently) being a psyop seeking to burn out people ala how "Jia Tan" tried to become maintainer of xz [0].[0] https://youtu.be/aoag03mSuXQ?t=597
locknitpicker: > They are just passionate and most of the times annoyed because something as simple is not being done right.I don't think this is the case at all. You are commenting in a discussion on how a maintainer of an unstable project which very clearly and unambiguously only targets and supports a specific version of a runtime. Still, said maintainer is being pestered by entitled users who attack the maintainer and how they chose to invest their free time contributing to the project with accusations of being "insane".This is not "passion". This is sheer entitlement, and abuse on top.If this was passion, you'd see users contributing their work with proposals to post releases. Even very low effort things like forking the repo and posting their custom releases would be infinitely more productive. You know, the core of FLOSS.But no. You have someone doing their best generously contributing their time to provide something to the public, and in return they get insults and abuse.No wonder projects get archived.
Scandiravian: I'm pretty sure this is not over a single user, but this was simply the straw that broke the camels back
andwur: From personal experience that usually results in the person on the attack opening two additional issues: 1) the original issue recreated, maybe with a childish flourish added e.g. "because we're apparently in the DPKR for this project" 2) a new issue claiming baseless censorship and attacking the maintainer(s) motivation and governanceA variation on this is the above plus they get a hoard of friends/wellwishers/bots etc to raise more issues claiming censorship and it devolves into a massive ad hominem flame war, doxxing, death threats and the usual rubbish that ruin a good thing.
faangguyindia: I built businesses not opensource projects.Though many of my projects are completely free for the users.Latest being this one already past 1000+ active users https://play.google.com/store/apps/details?id=com.macrocodex...If you don't listen to your passionate users, i doubt you'll ever grow.Someone being rude/entitled doesn't matter to me, I only care about if what they are saying actually makes any sense
otikik: I will listen to a rude paying customer if I must, because my income will be tied to it. If a similar paying customer comes and they are better behaved, the rude customer will take second position.On an open source project that I’m doing for my own enjoyment rude people are not welcome. I’m doing that for my own enjoyment - to decompress after dealing with rude people. Close issue, won’t fix, ban free user.
faangguyindia: Being rude is not effortless, it requires someone spending significant amount of energy on youAnd most people who wronged me were never really rude to me. So i don't even use someone's rudeness as filter for anything.
siva7: Don't take it personally but the people here are talking about open source projects and unpaid work in their free spare time. There is zero value you could share in this thread from your experiences on developing closed source business products because it completely misses the topic of volunteer work.
adjfasn47573: Ehm... no? It's not zero value?He's making a general point about "regardless of how something is presented to you, at the end of the day you have to look at the actual information, and if there is some truth in it, then it would be illogical to dismiss it".
siva7: Oh, how couldn't i see this. You're absolutely right. The author also did this and he concluded "OK." right before clicking on the "Archive Project" Button.
fancyfredbot: What will happen now is not clasons problem anymore I guess.The point they seem to be making is that it never was their problem, but they were just solving it for everyone for free anyway.
cherioo: It’s like the law of big numbers. Once a project grows large enough, some entitled free-riders are bound to pop up.What to do as maintainer? Can everyone of them find piece?
kzrdude: Nvim treesitter is kind of taken for granted even if nvim maintainers say it's experimental. So I think the community will have to find a solution and replacement project.
zysko-vendy: not really an excuse, but guy's from Kharkiv, Ukraine - a city that is almost daily getting bombed by russia, maybe he just had a bad day?
el_io: Can't you just disable issues?I've seen DRF did that. Not sure if that is not possible for normal accounts.
sudahtigabulan: Try publishing on https://repo.or.cz (or another old-style web interface), and just leave an email for contact.You will hear only crickets.Adding the slightest friction, and making potential drama 1:1 only, demotivates most people.You might miss out on an occasional good feedback, though.
szmarczak: He's just incompetent:1. He blames the maintainer that his distro doesn't ship latest neovim.2. He didn't pull neovim from the Extra-Testing Arch branch.3. He didn't pull neovim from AUR.4. He doesn't have the knowledge to build from source.5. He didn't pull the tarball from git.6. He didn't pull the AppImage from git.There's so many solutions to choose from and he chose none; pure ragebait.
xvilka: Will this mean the end to NeoVim, whose main (one of) selling point is the tree-sitter out of the box? I hope not, as I am the long time user and supporter of the project.
hacker_homie: Honestly I missed the neovim 12.0 being marked stable, and just updated when this happened.
shpx: I had a similar emotional outburst where after contributing hundreds of hours to Stack Overflow, when I asked a question of my own, instead of answering an objective yes/no question people just argued with me in the comments about why I could possibly want to do whatever prompted me to ask my question. I delete my account and quit ever contributing to that site right then and there. I think I was just looking for an out and it was ultimately a good thing.No idea if this is the case here, but I hope the author sticks with this decision. Although, looking at https://github.com/nvim-treesitter/nvim-treesitter/graphs/co... , it doesn't look like he started this project, so I'm not sure it's his place to archive it.
xiphias2: Isn't treesitter integrated to nvim anyways at this point, even if it's experimental support?
Sesse__: I don't have my stuff on GitHub, but git push will send me email with a patch. I actually get real, useful patches out of it (more than before I had only email); not huge stuff, but scratching people's itches and bugs; stuff I can mostly just apply right away. I never get pure junk (e.g. the “I'm sure you want to switch to My Favorite Build System” patches, or AI slop). So somehow, for me, this is pretty much the perfect level of friction, it seems.
sudahtigabulan: You are self-hosting the same web interface as repo.or.cz, cool!Is this "git-push to email" feature part of Girocco, or you wrote it yourself?Oh, and thank you for plocate! Happy user here. :-)
tasuki: > doesn't look like he started this project, so I'm not sure it's his place to archive it.This is a very valid point. It indeed looks like it was done in affect rather than after careful discussion with the (at least) ten members of the nvim-treesitter org.
onehair: > since people apparently can't readI know Free and OpenSource software is only available thanks to maintainers who spend their time and money to make it available. This type of sentence though, makes all I just mentioned easy to forget, when they take that tone with you.
martin-t: This is a common issue with tooling used by open source.Either you alone own the repo but then you're a single point of failure. Or you give those perms to others but then any one of them can abuse it (or get hacked).I'd like to see tooling which requires consensus or voting to make certain changes such as archiving a repo or publishing a new release.
mongrelion: It's clear to me that the maintainer is referring to "shushtain" and those type of people> when they take that tone with you.This makes it sound as if you took it personally?
mongrelion: Having a bad day does not entitle you to take it out on others
mongrelion: You should totally post this on the original thread just for adjustment :-)
burnt-resistor: The fork button exists. That's the technically easiest solution.
