Live data from Hacker News

What they don't tell you about maintaining an open source project

andrej.sh

131–140 of 171 posts

Re: What they don't tell you about maintaining an open source project

#131
It's interesting to see that the "the diversity of environments" section only talks about work for supporting different installation / deployment methods.

Back in the day, with different technologies, most of it would have been "strange compilers and environments" that had to be supported.

Re: What they don't tell you about maintaining an open source project

#132

Earlier quoted context omitted.

I wish. In my company that is an instant no. The amount of legal contracting bull we have to go through for that would quite literally take 9 months.

I'm almost certain there is a way to get the company to pay for pizzas for a staff meeting which doesn't involve any legal contracting bull.

Do you think GP is like, lying to you? Or maybe managers are just silly and are indeed willing to draw $500 for a pizza party but are unwilling to drop the same for a year of support for software they depend on. This is absolutely believable to me.

Re: What they don't tell you about maintaining an open source project

#133

I don’t understand. It’s your project, you do what you want and nothing more.

Yesterday I received this message from a random github user: "Seriously. No SSO at all in free version? This is poor. Very very greedy and poor" [1] If you do not spend a lot of time explaining things at length, people will link back to how much an asshole you are. [1]: https://github.com/mickael-kerjean/filestash/issues/661#issu...

Simply ignore users like that. If someone actually important brings up that instance as you 'being an asshole', then explain your reasoning then. If that doesn't calm them down, they're probably not someone worth working with.

I'll also point out the supportive comments in that thread; sure there's always gunna be some negativity, but there's also positive people. Focus on those.

Re: What they don't tell you about maintaining an open source project

#134
post #18

This is why I like building outside plant. You put the fibre up on poles or pull through ducts, splice it, bring it into the building, hook it up to the equipment, make sure it's working and.... you're done. It works until something breaks, usually for a very clear reason (power outage, drunk driver, rodent, vine, lawnmower man, fibre seeking backhoe, dump truck, direct lightning strike, thermal cycling of a marginal…

You're talking about being a tradesman on a forum dedicated to software and maybe making a company out of said software? If people liked the idea of being outside in the weather, doing manual labor as you've described, there is a very large chance they would not be on this forum.

There is a shocking variety of users on HN. Don't make the mistake of thinking we're all software developers sitting in front of a computer all day.

People like GP - and other hardware monkeys* - are the reason your computer works. Don't be rude.

* Said with much love <3

Re: What they don't tell you about maintaining an open source project

#135
post #18

This is why I like building outside plant. You put the fibre up on poles or pull through ducts, splice it, bring it into the building, hook it up to the equipment, make sure it's working and.... you're done. It works until something breaks, usually for a very clear reason (power outage, drunk driver, rodent, vine, lawnmower man, fibre seeking backhoe, dump truck, direct lightning strike, thermal cycling of a marginal…

> fibre seeking backhoe

I don't know why but this amused me. Is this a feature one can get when buying a backhoe?

Re: What they don't tell you about maintaining an open source project

#136

> someone opens an issue: "how do i install this?" Honestly, this is a GitHub thing. You wouldn't get that issue on sourcehut, bitbucket or self hosted. GitHub is the lowest common denominator for users.

I've seen this mentioned a few times lately. Not that I disagree, but why would that be? Is it just Github's poplarity? Is it the ease with which you can sign on and start yelling at FOSS maintainers? Something else?

Re: What they don't tell you about maintaining an open source project

#137

I don’t understand. It’s your project, you do what you want and nothing more.

Yesterday I received this message from a random github user: "Seriously. No SSO at all in free version? This is poor. Very very greedy and poor" [1] If you do not spend a lot of time explaining things at length, people will link back to how much an asshole you are. [1]: https://github.com/mickael-kerjean/filestash/issues/661#issu...

You've got the comment after you've explained at length

Re: What they don't tell you about maintaining an open source project

#138
post #136

> someone opens an issue: "how do i install this?" Honestly, this is a GitHub thing. You wouldn't get that issue on sourcehut, bitbucket or self hosted. GitHub is the lowest common denominator for users.

I've seen this mentioned a few times lately. Not that I disagree, but why would that be? Is it just Github's poplarity? Is it the ease with which you can sign on and start yelling at FOSS maintainers? Something else?

Popularity is part of it. It's the "default" for software.

It's what is taught in every school, bootcamp, youtube channel and corner of the internet. Anyone that had an idea on a random weekend to "learn to code" signed up for GitHub.

GitHub is less of a software forge and more like a Facebook for software.

Re: What they don't tell you about maintaining an open source project

#139
post #136

> someone opens an issue: "how do i install this?" Honestly, this is a GitHub thing. You wouldn't get that issue on sourcehut, bitbucket or self hosted. GitHub is the lowest common denominator for users.

I've seen this mentioned a few times lately. Not that I disagree, but why would that be? Is it just Github's poplarity? Is it the ease with which you can sign on and start yelling at FOSS maintainers? Something else?

Everyone already has a Github account. Just having to make an account on Codeberg/Sourcehut is enough of a barrier.

Re: What they don't tell you about maintaining an open source project

#140
post #128

Earlier quoted context omitted.

/sigh Because open source is not just about the code and the license. It is first and foremost about a community of people who want to make software better for everyone, not just for themselves or a select few. The code and license are ancillary to this goal. I won't get into this discussion again. I'll just say that if you think otherwise, whatever good you think you're putting out into the world, is not much better…

You have this entirely backwards. Open source is, definitionally, the code and a license. It is "first and foremost" those things. The community of people cannot exist without the code and the license. The code and the license can and often does exist without dedicated communities. Everything else in open source is a cultural projection entirely ancillary to the code and the license. > I'll just say that if you think…

Code existed before FOSS. Code that people collaborated on existed before FOSS. Code given away for free existed before FOSS. FOSS code, by itself, is not anything special.

Licences also existed before FOSS, but open sources licences enabling the kind of freedoms that they allow did not exist. And as it happens, a license is not a technical artefact but a social contract. Stallman is activist, not simply a neutral combination of a technician and a lawyer.

The social contract and political vision are consequently not ancillary, but core to FOSS. Code is the medium, but the license is the innovation. Without that social contract, 'open' code is just abandonware.

The community doesn't need to be a 'house party,' but the license guarantees the right for a community to form when the original author walks away.

Post reply on HN