4 ms·
Why not come up with a new name for the project instead of rage quitting?
by gigatexal 7y ago
Why not come up with a new name for the project instead of rage quitting?
- anthony_doan 7y ago> Why not come up with a new name for the project instead of rage quitting? Why should he change the project name when he originally have it first? Also why did you have to frame it as rage quitting?
- gigatexal 7y agoIt’s the way of the world that larger fish get to do as they please. A simple name change and he can continue to do his work. It’s the idea of turning the other cheek. That or trademark the name I guess.
- ben0x539 7y agoWould redhat ship dstat under the new name?
- gigatexal 7y agoThey should have shipped the original devs version or forked it and worked with him to get it supported and submitted their RH changes upstream etc.
- anthony_doan 7y ago> It’s the idea of turning the other cheek. I had to look this up. > refrain from retaliating when one has been attacked or insulted. I don't think he have retaliated in anyway, at least from the github commit message and the blog post. He just decided it wasn't worth his free time to deal with this problem. Maybe there is a disagreement with the definition of rage quitting but it was his open source project and his free time. I don't think it's rage quitting if he wants to quit and do something else with his free time. Rage quitting have a negative connotation such as flipping table or that scene from the movie Half baked where the dude cussed everybody out before quitting. He seems to have a career, whether you care or not, labeling at such may be detrimental to his career. Regardless of if you care or not, I hope other people refrain from speculating or do huge leaps of conclusion base on little or no facts that can damage other people's ability to make a living.
- pas 7y agoIt was already dead, so pragmatically there was nothing to do, this is just a swan dance on RH's bugzilla. Yes, RH should and could have filed and issue saying that they started working on a fork/port-to-PCP, and they intend to provide the dstat executable. But usually at that point, the work is already started, and there's almost nothing to be done. How long RH should wait for that ticket? What if the maintainer says, wow, cool, I'll make a py3 version in 3 months. But RH needs it in 2? What if the maintainer disappears again? It's not great, but it was abandoned. :(
- dagwieers 7y agoIt wasn't abandoned, it didn't see any maintenance for 18 months. I don't get paid for doing this work. Red Hat does. They get paid for offering it to customers that apparently demands that it ships with RHEL8. They have been shipping it with RHEL since RHEL3. They haven't contributed to it ever in that timespan. They could have paid me for maintaining it, they could have offered to maintain it for me. (Because it is a lot of work to accept and verify pull requests). I am a freelancer, I have to work for a living I don't have a lot of free time. Instead, they ripped out the plugin backend, added the PCP backend and now you can't use it as a drop-in tool that can't run PCP. Your synology NAS, WRT router or JeOS platform. Because Red Hat does not care about anything other than RHEL. They are business-oriented. And that's fine. Is the Open Source ecosystem better off ? I sincerely doubt it. It's being replaced by paid-for engineers with business interests. In the long term it is killing the community.
- kamane 7y agoThanks Dag alot for the dstat tool, I am using it till this day. As for opensource and community I think it would be reasonable to still have it under different name if you'll consider it after some time and still develop some functionality or curate and merge pull requests.