3 ms·
Hmm, keeping the server-side code proprietary is rather underhanded. Was the license of the "leaked" code actually proprietary? Anyway, sounds like the "leak" w
by einpoklum 4mo ago
Hmm, keeping the server-side code proprietary is rather underhanded. Was the license of the "leaked" code actually proprietary? Anyway, sounds like the "leak" was in the public interest.
- pastk 4mo agoThe code in question was in Apache 2.0 repo and DCO signed agreeing its a public contribution. Please see my post above for details.