3 ms·
But (as I interpret the blog post, at least) this isn't an acquisition. Cloudflare didn't buy Sandstorm, it just hired all the Sandstorm developers. Those devel
by smacktoward 10y ago
But (as I interpret the blog post, at least) this isn't an acquisition. Cloudflare didn't buy Sandstorm, it just hired all the Sandstorm developers. Those developers still retain ownership of Sandstorm-the-legal-entity and any intellectual property it owns. It's not an acqui-hire, in other words, just a hire.
Which, if that's the case, means that Sandstorm still is legally independent of Cloudflare, and the original Sandstorm devs can pretty much continue to do whatever they want with it. There would be some gray areas, like what will happen to future code or other IP they create for Sandstorm while employed by Cloudflare, or while using Cloudflare systems/resources; and of course their continued employment with Cloudflare may be contingent on their doing things with Sandstorm that Cloudflare likes, or at least doesn't disapprove of too strongly. But if the Sandstorm devs are just selling their future labor and not the company itself, they'll have more independence than they'd have gotten in an acqui-hire scenario.
- kentonv 10y agoCorrect. The CF people are cool and have no problem with us continuing to operate Sandstorm, as long as we're getting our Cloudflare work done. Cap'n Proto will presumably end up with mixed copyright, but it's MIT license anyway so who cares?
- shawn-butler 10y agoI'm sure you have already but look over that employment contract carefully. CF being "cool" shouldn't put your project and its users (me!) at risk.
- kentonv 10y agoYes, we have made sure to add appropriate language to the appropriate paperwork (in addition to being protected by California law).
- jgrahamc 10y agoWe've worked closely with Kenton on this. In fact, our lawyers wanted us to add language to ensure that it was clear that we don't own Kenton's IP around this.