- ship or maintain a modified version outside the contribution-purpose
  rules;
- maintain a divergent private or internal fork;
- port, clone, rebrand, or recreate the Covered Software;
- create an API-compatible replacement, behavioral clone, competing
  implementation, or Derivative Implementation; 

At that point why bother making your codebase public?