But I also harp a lot to my superiors about donating to open-source projects we utilize, make loads of money thanks to them, yet never give anything back.
I kinda get that some projects with limited backing can’t “get their shit together”, when successful users don’t give them anything. It’s a stupid pattern, and I hope we can break it.
That’s not a terrible idea as long as it’s significantly cheaper than the closed alternatives. I think the biggest issue would be that orgs that pay would expect a certain level of service that a community project might not be able to deliver on.
Most of the small to mid size companies that I have worked for would choose a larger more established system that costs more even if it offers less over a self-hosted one that they had to pay some sort of fee for.
Is like this weird idea in the business world that if you’re using Foss systems that it must be completely free, and that the reason why you are using it is because you are broke or cheap.
That’s kind of what I was getting at. Medium to large organizations usually require a certain level of reliability that closed software companies usually guarantee with dedicated support staff and SLAs. An open source project developed by the community with no dedicated support is risky from that perspective.
If someone with the technical know-how and ability to maintain those systems offered support (red hat for example) for a lower price, many small and medium sized companies would get on board. That could also just look like a company hiring a small team to implement and maintain their own systems while contributing back to the community project.
It’s just a much harder sell to non-technical leaders. They just want uptime guarantees and fixed costs.
My guess is that if you’re going to start a MSP you can do that with Foss and probably have a lot of success as long as you’ve got the sales chops to get the contracts.
Then you can funnel some of your customers money to foss well also increasing awareness and adoption of the better free and open source software programs
I don’t think that is necessary, as some companies do actually help, either with money or even dedicated staff, which can be as good or better.
We should push for developers to promote the idea of more help towards FOSS projects, maybe find some hours a month, or send any money saved from not paying for licenses.
I tried to get our team to move to Matrix when COVID hit and there was no infrastructure for remote work.
It was such a shame that it was that exact time Jitsi had issues with Firefox (which most of us use), so we couldn’t videochat.
If Jitsi had that resolved immediately, we perhaps could have used something open for at least couple of years. Maybe others would follow suit.
Oh well. Teams it is.
thats probably my biggest issue with open alternatives.
they always fail to take advantage of those opportunities and things stay broken until its way too late.
But I also harp a lot to my superiors about donating to open-source projects we utilize, make loads of money thanks to them, yet never give anything back.
I kinda get that some projects with limited backing can’t “get their shit together”, when successful users don’t give them anything. It’s a stupid pattern, and I hope we can break it.
i think we could bake some form of “free for personal use, paid for corporate use” clause in our foss licenses tbh
That’s not a terrible idea as long as it’s significantly cheaper than the closed alternatives. I think the biggest issue would be that orgs that pay would expect a certain level of service that a community project might not be able to deliver on.
Most of the small to mid size companies that I have worked for would choose a larger more established system that costs more even if it offers less over a self-hosted one that they had to pay some sort of fee for.
Is like this weird idea in the business world that if you’re using Foss systems that it must be completely free, and that the reason why you are using it is because you are broke or cheap.
That’s kind of what I was getting at. Medium to large organizations usually require a certain level of reliability that closed software companies usually guarantee with dedicated support staff and SLAs. An open source project developed by the community with no dedicated support is risky from that perspective.
If someone with the technical know-how and ability to maintain those systems offered support (red hat for example) for a lower price, many small and medium sized companies would get on board. That could also just look like a company hiring a small team to implement and maintain their own systems while contributing back to the community project.
It’s just a much harder sell to non-technical leaders. They just want uptime guarantees and fixed costs.
My guess is that if you’re going to start a MSP you can do that with Foss and probably have a lot of success as long as you’ve got the sales chops to get the contracts.
Then you can funnel some of your customers money to foss well also increasing awareness and adoption of the better free and open source software programs
some foss projects actually do this and have support staff!
i think libreoffice did this in the past. so does proxmox.
I don’t think that is necessary, as some companies do actually help, either with money or even dedicated staff, which can be as good or better.
We should push for developers to promote the idea of more help towards FOSS projects, maybe find some hours a month, or send any money saved from not paying for licenses.
on the other hand we get situations where we have a single dev maintaining some essential part of tge stack, for free.
i think pushing for more help is just a piece of this puzzle.
Lose the critical part of your business, see how fast you can move around it.
The xkcd random dude in Nebraska
You mean like WinRAR?