Live data from Hacker News

Sorry everybody, I failed with you

github.com

81–90 of 357 posts

Re: Sorry everybody, I failed with you

#81

Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…

Davidism took on Flask/Pallets really well, I think.

Re: Sorry everybody, I failed with you

#83
I’ve seen few OSS burn out posts lately. I created gitignore.io and I’m thankful it wasn’t that successful because even the 5 hours a month I put in didn’t yield much financial compensation.

There should really be a more transparent way that projects like this, canihazip, gitignore, redis, and a bunch of other projects can be sustainably run.

Re: Sorry everybody, I failed with you

#84
post #71

Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…

A temporary BDFL... Would that be called a TBD (temporary benevolent dictator)? :)

Benevolent Regent Lord

Re: Sorry everybody, I failed with you

#85

Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…

> But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work?

Burnouts like this happen, because it is not actually possible to keep working on side projects for 30 hours a week on top of actual 40 hours a week work.

Whoever would take it would face the exact same issue.

Re: Sorry everybody, I failed with you

#86

Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…

I think with the modern internet, and GitHub, it's much harder. It used to be reasonable to make a release every year or so, and basically not be in communication other than that. You could also assume all your dependencies would release updates every year. Now people expect replies to their GitHub issues within a few days, if you have CI you were probably using Travis and had to update everything, etc.

Re: Sorry everybody, I failed with you

#87
post #22

and of course: it's javascript! because literally every other community would have no problem if their doc-generator got unmaintained, because it would probably run for another ten years...

There’s also a defective culture meme that believes software that hasn’t been updated in the past week is dying. This is a conceptual hack to avoid considering the state of the ecosystem.

It's not a defective culture meme, because the modern ecosystem is moving fast. We're using to thinking about digital creations as if they're forever. This is incorrect. Software without a platform doesn't run. Platforms are always changing, and sometimes platforms die and get replaced with other ones.

Think of software like a living being, not like a statue etched in stone (although even statues etched in stone degrade).

Re: Sorry everybody, I failed with you

#88
post #71

Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…

A temporary BDFL... Would that be called a TBD (temporary benevolent dictator)? :)

when I started work on ts-loader I went with "caretaker" https://blog.johnnyreilly.com/2016/11/01/but-you-cant-die-i-...

Re: Sorry everybody, I failed with you

#89
post #39

Earlier quoted context omitted.

How about the insane entitlement that many devs have when it comes to open source? Getting bombarded with requests and angry emails from people who demand free support and bug fixes can burn anyone out. I think Github can be a positive force for change here. Redesign the UI to encourage donations, to encourage people to get involved in project work, to write less hostile issues, etc. If devs and designers can weaponi…

I wonder if this is a back-firing of the push for people to be "nice" and "professional". Open source maintainers used to have the sterotype of being rather harsh, and basically telling people to f off if they had stupid questions, didn't RTFM or didn't follow cultural norms. And dont get me wrong, there's a lot wrong with that, but maybe it was also that way for a reason.

You can be harsh in a nice and professional way though.
Post reply on HN