2 ms·
People weren't "testing the boundaries" of AGPL. You need to know nearly nothing about AGPL to understand this. The bottom line is, AGPL merely requires you to
by jchw 8y ago
People weren't "testing the boundaries" of AGPL. You need to know nearly nothing about AGPL to understand this. The bottom line is, AGPL merely requires you to publish your modifications. But if cloud providers are offering essentially a vanilla MongoDB instance, there is no reason they are compelled to buy a commercial license.
Still, I wonder where MongoDB actually wants the boundary drawn. Anyone that tries to offer the MongoDB protocol as a service using the official code? Or is it if I provide a database interface to a MongoDB instance? Or is it only if the actual MongoDB interface from the MongoDB server is provided? I haven't read their new license but I have a strong feeling that it won't be 100% clear yet.
- e12e 8y agoAnd will they break the protocol in order to break compatability with AGPL forks?
- jchw 8y agoThis would be futile. The forks could still implement the protocol changes as long as they didn't take code from upsteam to do so. I believe there is also case law that supports the legality of reverse engineering for interoperabilility as well. I wonder if that has implications on this.