Back in the day, with different technologies, most of it would have been "strange compilers and environments" that had to be supported.
What they don't tell you about maintaining an open source project
131–140 of 171 posts
Re: What they don't tell you about maintaining an open source project
#132Earlier 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.
Re: What they don't tell you about maintaining an open source project
#133I 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...
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
#134This 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.
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
#135This 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…
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.
Re: What they don't tell you about maintaining an open source project
#137I 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...
Re: What they don't tell you about maintaining an open source project
#138> 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?
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> 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
#140Earlier 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…
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.