4 ms·
> But we can’t comply with CC. Why not? The point of the CC is literally "pay us to use it commercially." You can't just... pay them to use it? Even when that'
by derefr 8y ago
> But we can’t comply with CC.
Why not? The point of the CC is literally "pay us to use it commercially." You can't just... pay them to use it? Even when that's exactly what you'd be doing by using an AWS service?
- ubernostrum 8y agoYou could offer to pay them today, yes. And get a license. But is your license that handles your use case today still going to be valid and useful a year from now? Five years from now? What if redislabs decides there are some more loopholes in need of closing? I'm not a fan of the AGPL. I think it's problematic as an example of copyright maximalism, and I think it's counterproductive in that it basically took a bunch of ideas that used to be FUD and said "yeah, what if we actually did that". But I can say this for it: you know what you're getting and you know that for all the burdens it puts on you, it (like the GNU GPL) was designed to make sure certain rugs can never be yanked out from under you.
- prepend 8y agoPart of CC is that it’s unclear how it operates with the myriad of other project licenses we use. But the main issue is that we contribute back to projects, even as minor patches or fixes. Contributing source to a proprietary, commercial code base has legal issues of nonpaid work and contribution. And finally, “pay them to use it” is very ambiguous. How much to pay them? Is it the same amount today as tomorrow? I pay for support for substantial projects like RedHat, but is support included in licensing CC? These questions are ambiguous. Perhaps in time they will get easier to answer. But this is exactly why I would rather use AWS with its “so clear its confusing” pricing [0] where I know exactly what I’m getting. [0] https://aws.amazon.com/elasticache/pricing/ https://aws.amazon.com/elasticache/pricing/