zlacker

[return to "Open Source is Not About You"]
1. newcro+it[view] [source] 2018-11-27 06:18:48
>>jashke+(OP)
Though Rich is right, it pains me to read this because it is indicative of some disputes in the clojure community. I might be mistaken, but it seems that Rich is reacting to Chas Emericks' twitter post (https://twitter.com/cemerick/status/1067111260611850240). In his comments he has stated: "Finally, from a practical perspective, my core-level contributions always came from some source of pressing need in an actual, present, needs-to-work project. If I know a problem isn't going to be triaged for months and solved for years, then I'm out."

So this is not some grieving random person from crowd - Chas is a person whose libraries and contributions I value tremendously and he certainly made LOTS of contributions to clojure OSS landscape for free and out of his good will as well. So ultimately this feels like your parents are arguing (which is never a good thing) - you like them both and you just want the arguing to stop and you just want everybody to live together in harmony. But here you go, Chas has moved away from clojure now. And I have to say I am very sorry to see him go.

◧◩
2. beders+qF[view] [source] 2018-11-27 08:54:32
>>newcro+it
I don’t know this person but there’s a fork button on github. “Pressing need” —> fork

Seems to be an ego thing.

◧◩◪
3. dmitri+JG[view] [source] 2018-11-27 09:08:32
>>beders+qF
The you have to maintain your own fork. And keep up with changes upstream. And reconcile the two forks. And... And...

I'm not even mentioning the potential split in the community.

◧◩◪◨
4. joseph+BW[view] [source] 2018-11-27 12:29:25
>>dmitri+JG
Yes; it’s definitely less convenient to write and maintain your own software compared to having someone else do it for you.

As a project maintainer I’ve made the mistake several times of being too permissive with pull requests. Someone comes along with a feature they’re excited to add to my project. I don’t need the feature myself. They exuberantly make a PR, and I eventually merge it. Before long it turns out there’s a bunch of bugs with that feature, and the original author is gone. Do I waste my time fixing their code, for a feature I never wanted and don’t use? Or do I ignore the bugs and let the smell of low quality work waft over my code base?

These days I default to refusing most feature requests, even if they have decent PRs. I write most software for fun, or to scratch an itch. I don’t do it because I want to manage a community. If you want to add features and build a community around a project I’ve written, great. I’m happy to link to your fork in my readme.

Forking is not a symptom of failure. Maintaining a fork is sometimes just the ticket price to control your destiny.

[go to top]