Live data from Hacker News

On Being a Free Software Maintainer

feaneron.com

121–130 of 147 posts

Re: On Being a Free Software Maintainer

#121
post #103
post #87

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…

Students putting their homework on github is totally fine as long as they clearly state that in the readme.

Re: On Being a Free Software Maintainer

#122

Oh 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

#123

This 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…

You use the word 'legally'. Which laws are you referring to?

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…

[deleted]

Re: On Being a Free Software Maintainer

#125

Oh 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.

In 10 years, really the only negative experience that in any way affected my well-being was the incident I wrote about in the linked blog post. That covers probably a couple thousand GitHub issues. So really overwhelmingly positive stuff. Amazing how much I let one guy fuck up my day, in retrospect.

Re: On Being a Free Software Maintainer

#126
post #6

Are 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.

I would not be where I am without my involvement in OSS or other projects, mostly due to the gained experience. The "trick" about putting it on your resume is, if it's significant, to make it not sound or placed any less worthy than any other experience on there (possibly also avoiding terms like "free", "personal", etc)

Re: On Being a Free Software Maintainer

#127

Earlier 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…

> A lot of it boils down to your own personal presuppositions and worldview.

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

#129
I kinda have a similar situation. I upload my hobby projects on GitHub. It has about 90 repos by now. Most of them are just garbage that no one looked at. One of them amassed about 3000+ stars over time. People keep sending me numerous pull requests, but I'm very picky about the coding style and I pretty much ignore all of them. I also ignore most issue reports and feature requests because I'm not interested. Some people asked to hand over the project to someone else, but even picking a good person is a huge hassle to me. So I just left the project pretty much dead as it is. Still, it somehow keeps getting more stars.

Am 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

#130

Earlier 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 easy.

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.

Post reply on HN