Thanks for the rec! I’ll definitely suggest that but the head of our IT dept has a particular dislike for FOSS, due to past bad experiences, but I’ve been slowly whittling him down.
I am the IT department, but have had mostly good experiences with FOSS stuff, although you do need to vet the licensing: Not all licenses will allow for a company or institution to use it.
Also, you need to make sure it will work reliably, doesn’t pose any security risks, etc. but that should always be SOP for any software FOSS or proprietary, free or paid. If a tech department isn’t vetting stuff, then they’ve already fucked up before deploying anything.
FOSS isn’t necessarily bad in an enterprise environment though, sometimes it’s even the best possible option (most web servers run some version of Linux, for example).
Thanks for the rec! I’ll definitely suggest that but the head of our IT dept has a particular dislike for FOSS, due to past bad experiences, but I’ve been slowly whittling him down.
I am the IT department, but have had mostly good experiences with FOSS stuff, although you do need to vet the licensing: Not all licenses will allow for a company or institution to use it.
Also, you need to make sure it will work reliably, doesn’t pose any security risks, etc. but that should always be SOP for any software FOSS or proprietary, free or paid. If a tech department isn’t vetting stuff, then they’ve already fucked up before deploying anything.
FOSS isn’t necessarily bad in an enterprise environment though, sometimes it’s even the best possible option (most web servers run some version of Linux, for example).