To add to another comment, my company is not really afraid of it, but the amount of overhead needed to contribute to OSS projects is very high here. Basically, we have to ensure that we are releasing clean, well documented code, with proper contribution guides, that a person here can “own” with updates. Any code beyond bug fixes we push would have to be approved beyond our normal code review process. We don’t want to have our Junior Intern Dev start pushing code publicly that makes our code look bad…. Or our senior devs hah.

Finally, GPL makes things tricky for us, as we take the license seriously. We tend to release code in a more permissive license for that reason, and actively try to use MIT/BSD for that purpose. So we have to be careful, and it is much much easier to just not release code into the wild.

Oh and for new projects, we have to justify why we should make them publicly OSS - will it actually benefit the community in some way?

Because of anti-customer features. Hard to implement those in a FOSS project, without a fork undermining you.

I'll just leave here the response from obsidian. If you can extract truthful reason from this corp double speak, please share

https://tenebrousdragon.com/Essays/FOSS+and+Obsidian

Anybody who is afraid of showing proof (which making the code open source does) should be given a wide berth

They were depending on you not knowing, and that is never good for you