Earlier quoted context omitted.
I don't understand the downvotes for this. I feel that by making something public and open source, there is an implicit assumption (unless otherwise stated) that the software is worth sharing. The problem is that this puts what I consider the right amount of responsibility squarely in the middle of a continuum: library authors shouldn't be totally free of obligations to others, but the insane abuse that people level…
This rule accepted in general would mean that all students who put their homework on github are doing something wrong. Or that all professionals who just play around technology or mini projects are required to keep them secret until they are totally sure they will maintain it forever. That is just not workable and overly limited. While owner can not expect gratitude, the "I’ll work on this when I want, however much I…
On Being a Free Software Maintainer
121–130 of 147 posts
Re: On Being a Free Software Maintainer
#122Oh this is infuriating: > You will be told that you need to develop a thick skin. It's the equivalent of a bully taunting with "stop crying!" I have been doing open source for about 10 years. A couple of my projects have 1000+ stars on gh for what it's worth. Most people are chill. Some people disagree without being disagreeable. Then there's others who are completely toxic. A guy who was cto of a company and wanted…
Re: On Being a Free Software Maintainer
#123This has been discussed before and it has been true for me as well. I don't have a large, super-popular package I maintain, but several lesser known ones, some of which I wrote, and several of which I just adopted and passively became a maintainer over time. At some point the pressure from the community made me pass the magical threshold between fun/useful/rewarding and downright chore. It has permanently changed my…
> useless code of conduct # Code of Conduct in the United States, the development of the Code of Conduct appears to be a mechanism, refined by lawyers, to make a legal case to -> kick someone out The code of conduct uses words to describe desired outcomes of cooperation, but actually, it defines boundaries such that there is a specific reason to require a person with some behavior pattern, to leave, be blocked and re…
Re: On Being a Free Software Maintainer
#124> It means you are trusted. It means you are trustworthy. It means you are skilled enough. It means those things to the org that made you the maintainer. It means nothing in particular to the users, bug reporters, and people who offer up fixes and features who don't already know you. > If you are open to review other people’s contributions, there is a high change you will find challengers disguised as contributors. N…
Re: On Being a Free Software Maintainer
#125Oh this is infuriating: > You will be told that you need to develop a thick skin. It's the equivalent of a bully taunting with "stop crying!" I have been doing open source for about 10 years. A couple of my projects have 1000+ stars on gh for what it's worth. Most people are chill. Some people disagree without being disagreeable. Then there's others who are completely toxic. A guy who was cto of a company and wanted…
Chiming in to add that I've definitely had my ups and downs with open source. When it's going well it feels incredibly rewarding but when it's not, it absolutely sucks and I've gotten to the point where I avoid GitHub and try to take a break. It's part of the reason I've avoided taking donations for any project I work on. I'd feel a lot worse about taking a break if people were paying for higher expectations.
Re: On Being a Free Software Maintainer
#126Are there any benefits to being a free software maintainer beyond the obvious pride and satisfaction that comes with the role? For example, is this something that people mention on their resumes? Does getting a job become easier and when you do, can you negotiate higher salaries? Our world is incredibly indebted to Free Software Maintainers and I wonder how we can pay them back in our little ways.
Re: On Being a Free Software Maintainer
#127Earlier quoted context omitted.
Having wasted a significant portion of my youth on said book I would not recommend it. The whole thing boils down to devoting yourself to a (IMO) demanding, bigoted, homophobic, and imaginary being. Whatever crumbs of truth (treat others like you want to be treated, life is short, etc.) included are better expressed elsewhere and without all the baggage.
Having wasted a significant portion of my youth pursuing whatever I wanted only to later realize I was enslaved to the very things I thought I was pursuing freely, I can wholeheartedly recommend the Bible as that which gave me true freedom. Many of it's teachings are certainly counter-cultural. And it does take time and effort to learn and interpret wisely. But I find much in the Bible that is very applicable to life…
Maybe. But my early worldview was shaped almost entirely by Bible believers. Now after thirty years my perspective has changed. And it's hard to see value in evaluating the world from ideas and testimonies that cannot be proven, especially those that condemn those born different.
Re: On Being a Free Software Maintainer
#128This is true. But then you get maintainers like Ulrich Drepper.
Re: On Being a Free Software Maintainer
#129Am I a bad/irresponsible person? Since anyone can fork the project I don't think I'm doing disservice to the community (whatever it is). Also I'm frankly a little annoyed that I am getting this by just using my personal repo and mostly being passive (I've never promoted my project anywhere, except uploading it on PyPI).
Edit I can see that there would be a moral issue if I used my GitHub creds for my personal gain (such as applying for a job). But I've never done that. Again, I've never asked for this and I just want to play in my sandbox.
Re: On Being a Free Software Maintainer
#130Earlier quoted context omitted.
> useless code of conduct #Code of Conduct This is not a community project. This is my project. I know that will disappoint some people, but I do this for fun in my own spare time. If it stops being fun, I will stop working on it, which will pretty much kill the project. There are millions of projects in the world and the only reason they continue (if they actually do) is because the maintainers stubbornly stick at i…
> This is my project Ownership is essentially the main problem of OSS here. > If it stops being fun, I will stop working on it, which will pretty much kill the project. See what I mean ? Makes me think of Hickey's "Open source is not about you" rant and I can't prevent myself from hearing "It's about me". https://news.ycombinator.com/item?id=18538123
It's my project, I will lead it the way I see fit. I decide what gets merged, what issues have priority, what gets you banned.
It's also open source. Fork it if you want, drive your fork's development the way you see fit. Now it's your problem, not mine.