Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Rust project has a burnout problem

jyn.dev

Post reply on HN
Print view View original

181–190 of 258 posts

Re: The Rust project has a burnout problem

#181

Post by delfinom »

jackcviers3 wrote: post #108
sph wrote: post #44

Earlier quoted context omitted.

> This is a good description of what life is like working on almost any significant open source project. Open contributions project. An open source project does not necessarily have to accept random contributions, issues or hatemail from the general public. [1] They just need to make the source available with a permissive licence, period. I believe that Linux with its idiosyncrasies in its communication model (mailin…

Github marketplace has a close pull request action[1]. You also need to close issues after a set amount of inactivity[2]. If there is a bug without a CVE, or a feature someone wants fixed that users don't want to submit a fix for themselves AFTER it has been discussed with the maintainer in an issue with a replication or strawman proposal and the owner has created a draft pr and asked you to work on it, it probably n…

The point is Close Pull Request shouldnt be an action. It's should only be a bool in some database column for project settings that turns off the entire functionality.

Re: The Rust project has a burnout problem

#182

Post by preommr »

pdimitar wrote: post #72
mjw1007 wrote: post #38

Earlier quoted context omitted.

I think, from observation, that the Rust project has worse burnout problems than most other similarly-sized open source projects. I'm not sure whether it's more to do with the way the project is organised, the state of the codebase, or the sort of person that's attracted to working on Rust in the first place.

> the sort of person that's attracted to working on Rust in the first place What's that even supposed to hint at?

Furries - lots and lots of furries.[0] /endjoke

[0] https://www.reddit.com/r/rust/comments/vyelva/why_are_there_...

Re: The Rust project has a burnout problem

#183

Post by delfinom »

marcosdumay wrote: post #131
seagreen wrote: post #64

Earlier quoted context omitted.

> Open contributions project. That's a useful distinction and a good term. So in total projects can be classified as: - Source available or not - Open source or not (a subset of source available) - Open contributions or not (also a subset of source available) - BDFL or community driven That's a lot of variation and may explain why so many conversations about open source sound like people are talking past each other--…

> That's a lot of variation and may explain why so many conversations about open source sound like people are talking past each other Most of the discussion is people suffering through GitHub-style social networks. I don't see a lot of people talking through each other, as much as I see people assuming this is the way, and others pointing out it's just one option. At some point we have to acknowledge that GitHub is a…

GitHub is absolutely toxic which is why we develop on GitLab instead. The reduction in the slowly creeping "social features" and non-existence of drive-by activism is great.

Re: The Rust project has a burnout problem

#185

Post by nyokodo »

vouaobrasil wrote: post #143
nyokodo wrote: post #45

Earlier quoted context omitted.

> I personally feel that no amount of money is worth spending the best part of your youth doing mostly meaningless things It depends on why you’re doing it. Supporting a family, and contributing money and spare time to your community, are very meaningful. I’m building for in order to do my real job which is being a parent and citizen.

That is true. I agree with it for sure. Just so many jobs don't let you do this. But if you managed to find it, that's great!

> Just so many jobs don't let you do this

If the job you have genuinely doesn't allow you to do your real job (support a family etc) then you're definitely in the wrong job.

Re: The Rust project has a burnout problem

#186

Post by jynelson »

estebank wrote: post #167

I'm surprised at how many people seem to focus so much on the effect of incoming PRs that require some mentoring to get them to a mergeable state or on "entitled users". I don't think those are significant contributors to burn out in the Rust project. Those you can ignore. More significant is "X is important, but I'm the only one that thinks so, so I have to carry X to completion single handedly". That causes a lot o…

they both contribute a lot, although rereading my post i realized i dedicated more discussion to review burnout. i think it's a question of whether you feel more of an obligation to your users or to other people in the project, i've noticed you and i differ there.

for me particularly, reviews were bad because there was a time component, if i waited too long people would get frustrated and give up.

Re: The Rust project has a burnout problem

#187

Post by gray_-_wolf »

humanrebar wrote: post #155
gray_-_wolf wrote: post #101

Earlier quoted context omitted.

> I think they also encourage drive-by contributions I realize I am in minority, but for me, if project uses a mailing list I am more likely to do a drive-by contribution (compared to no contribution at all). Just doing git send-email is much easier compared to figuring out how to create whatever pull request is called in whatever forge the specific project is using.

I'm the opposite. There's no clear notion of status, remaining concerns, priority, etc. in an email thread.

> There's no clear notion of status, remaining concerns, priority, etc. in an email thread.

Which, for drive-by contributions, does not really matter. It is a problem for long term contributions and project managements in general, true, but there often is some tracking system present (patchwork, debbugs, ...).

Re: The Rust project has a burnout problem

#188

Post by networkchad »

actualwitch wrote: post #114
rkangel wrote: post #10

Do other people react as strongly as I did to the lack of capitalisation at the start of sentences? The post is generally "well" written with good grammar and punctuation so I find it strange - it feels like a style choice. But the style choice just instinctively makes part of my brain feel like it's written by a child.

HN guidelines has this to say about contents of your comment: Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.

[dead]

Re: The Rust project has a burnout problem

#189

Post by barkingcat »

ninkendo wrote: post #152
berkes wrote: post #121

Earlier quoted context omitted.

Engagement isn't just driving ads. It's driving engagement: The "toothbrush"-factor we called that in app-development: do you have an app that people pick up like their toothbrush: without much thought, several times a day? Engagement means people have you in their workflow, on their radar. I would love it if Github is something that I don't have to think of, that is invisible and out of my mind. I'd love it if it's…

I think I know what engagement is , but I’m wondering why you think Microsoft benefits from me being engaged with GitHub?

by hijacking the git moniker. most college students think of github before they think of git itself.

that brand power is worth billions.

Re: The Rust project has a burnout problem

#190

Post by AlexAndScripts »

jynelson wrote: post #142
coldpie wrote: post #129

Earlier quoted context omitted.

You're going to get some strong/rude reactions from "the other side," which is unfortunate. FWIW, as a reader I do find it genuinely more difficult to read. Capitalization serves a purpose for me, it's not arbitrary. It more clearly separates each sentence. I have to put in more work to read your thoughts without it. Anyway regardless, the rudeness sucks. Sorry on behalf of others who feel as I do.

this is very kindly written, thank you :) frankly i don't want a larger audience, i didn't expect this to hit HN. i hadn't thought about it being harder to read for people in the project though, i'll do a poll on whether they find it distracting.

Perhaps you could have a little button to programmatically insert capital letters?
Post reply on HN