recursiveturtle

joined 1 year ago
[–] [email protected] 5 points 1 year ago

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?

[–] [email protected] 1 points 1 year ago

If you can get into the right mindset, I think Signalis is an absolute gem of a game. The story is juuust enough to be very disturbing. And the ending stuck with me - holy crap that ending.

I personally loved it, and I would recommend it to anyone who enjoyed the old-school survival horror genre.

But OMG I wanted just one more inventory slot so badly.