• Original Code: Must remain under Blue Oak. The license text (or a link to it) must be preserved in all copies.
• New Code: If a user adds their own code, they can license their new code under any terms they want (e.g., GPL, Proprietary).
• Combined Work: If they distribute the project as a whole, the combined work can be under a new license, but the original Blue Oak code must still carry its original license within the distribution.
• Key Rule: You cannot strip the Blue Oak license from your code and claim the whole thing is "Closed Source" or "MIT" without acknowledging the original terms.

2. License Notices

• The third party cannot remove the license. Blue Oak requires that every copy include the license text or a link to it.
• Failure to include this notice is a violation of the license.

3. Original License Remains in Effect

• The third party cannot retroactively restrict use of the original code.
• Anyone can still obtain the original code and use it under the original Blue Oak terms, regardless of what the forkers do with their version.