I've been watching this project for like 10 years now probably. Keep returning there for blueprints of something relevant, but it's either too immature or something that does not fit my setup. I think they are too unified and their scope is unrealistically broad for the group, while contributing remotely is not realistic. Their house would not work in my climate, their tractor is worse than random assembly from junk you can randomly find. Their aluminium electroliser is soft sci fi.
But it is certainly cool project.
I just think we need more specialised open hw projects and keep exchanging links to them.
This is an admirable project, and I one I support. However, it's important to note that '''the issue with open source in an enterprise environment, is that there is no one to blame when things, inevitably, break or are misconfigured. The blame falls on only you, not a vendor.'''
Literally the reason my former VP of IT gave me that the CEO gave him.
Using a proprietary solution that has FOSS components isn't the same as a FOSS solution. Commercial enterprise support is usually in the form of a vendor support contract (or a proprietary solution that uses FOSS components), which gives the corpo someone to blame.
Also, wasn't the abacus, technically, open source? So, they couldn't use that, either.
Of course you can have open source in an enterprise environment and have someone to blame. You hire a company to install the open source software and maintain it.
As was pointed out earlier, commercial enterprise support for FOSS is usually in the form of a vendor support contract, which gives the corpo someone to blame.
15 Comments
ProdigalFrog@slrpnk.net · 7 pts · 336d
We have a community for this project as well: !open_source_ecology@slrpnk.net
alzymologist@sopuli.xyz · 5 pts · 336d
I've been watching this project for like 10 years now probably. Keep returning there for blueprints of something relevant, but it's either too immature or something that does not fit my setup. I think they are too unified and their scope is unrealistically broad for the group, while contributing remotely is not realistic. Their house would not work in my climate, their tractor is worse than random assembly from junk you can randomly find. Their aluminium electroliser is soft sci fi.
But it is certainly cool project.
I just think we need more specialised open hw projects and keep exchanging links to them.
BastingChemina@slrpnk.net · 4 pts · 336d
There is also the Atelier Paysan in France that designed a lot of agricultural equipment published under creative Commons license.
https://www.latelierpaysan.org/Outils-et-plans
Five@slrpnk.net · 2 pts · 337d
@marcin_ose
01189998819991197253@infosec.pub · 1 pts · 337d
This is an admirable project, and I one I support. However, it's important to note that '''the issue with open source in an enterprise environment, is that there is no one to blame when things, inevitably, break or are misconfigured. The blame falls on only you, not a vendor.'''
Literally the reason my former VP of IT gave me that the CEO gave him.
fruitycoder@sh.itjust.works · 13 pts · 337d
Commercial support exists for opensource too so its just a misunderstanding of it.
01189998819991197253@infosec.pub · 2 pts · 336d
Commercial enterprise support is usually in the form of a vendor support contract, which gives the corpo someone to blame.
fruitycoder@sh.itjust.works · 2 pts · 336d
That is a value as well. But also support from people already actively contributing to the project can be very helpful as well
01189998819991197253@infosec.pub · 2 pts · 336d
Very true. And I am not pretending it's not. I was mostly venting my experience (and frustration) regarding enterprise environments.
wildbus8979@sh.itjust.works · 8 pts · 337d
Because clearly blaming corporations for the ongoing climate apocalypse is going super well! They really care! And they are super sorry!
01189998819991197253@infosec.pub · 3 pts · 336d
I... don't understand what you're on about. How does the climate crisis have anything to do with my observation about FOSS enterprise support?
The corpos aren't looking to be blamed. They're looking for someone to blame.
Railcar8095@lemmy.world · 1 pts · 335d
Remove open source from any company stack and they'll go back to using abacus.
01189998819991197253@infosec.pub · 1 pts · 335d
Using a proprietary solution that has FOSS components isn't the same as a FOSS solution. Commercial enterprise support is usually in the form of a vendor support contract (or a proprietary solution that uses FOSS components), which gives the corpo someone to blame.
Also, wasn't the abacus, technically, open source? So, they couldn't use that, either.
BastingChemina@slrpnk.net · 1 pts · 335d
You're CEO and VP of IT are idiots.
Of course you can have open source in an enterprise environment and have someone to blame. You hire a company to install the open source software and maintain it.
01189998819991197253@infosec.pub · 1 pts · 335d
**former. But yes. One of the reasons I left.
As was pointed out earlier, commercial enterprise support for FOSS is usually in the form of a vendor support contract, which gives the corpo someone to blame.