Our great sponsors
-
Windows Terminal
The new Windows Terminal and the original Windows console host, all in the same place!
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
>We are allowed to view and consume it, to be influenced by it, and under many circumstances even outright copy it.
People keep saying this but it's actually much more complicated, and in many cases you can't view copyrighted content.
An example, MicroSoft employees are not permitted to view or learn from an open source (GPL-2) terminal emulator:
https://github.com/microsoft/terminal/issues/10462#issuecomm...
Another example is proprietary software that may have it's source available, either intentionally or not. If you view this and then work on something related to it, like WINE for example, you are definitely at risk of being successfully sued.
If you worked at MicroSoft and worked on Windows, you would not be able to participate in WINE development at all without violating copyright.
If you viewed leaked Windows source code you also would not be able to participate in WINE development.
An interesting question that I have, is whether training on proprietary, non-trade-secret sources would be allowed. Something like unreal engine, where you can view the source but it's still proprietary.