Paul Dix shared his thoughts on the subject of Redis and the misunderstandings going on around Redis Common Clause Licensing. Paul writes on the InfluxData blog:

The accusation that RedisLabs did a bait and switch is entirely unfair. They’ve been funding open source Redis development for years and that work is now and will be in the future under the liberal BSD license. It’s not like they tricked a bunch of people into using Redis and pulled the rug out from under them. I’m sure that more than 99.99% of the Redis users are completely unaffected by this. And for those others, it’s not like the code that’s already out there is unusable. To my knowledge they can’t retroactively apply the license. So we’re really only talking about forward development to specific modules (not Redis core).

Paul also shares how he favors open core, and the issues he has with other models to sustain the development of open source at scale.

Open core is a fairly honest way to go about developing open source software. As long as you’re clear about what is open and what is closed.

Bradley Kuhn, Executive Director and President of Software Freedom Conservancy, also shared some thoughts on “Commons Clause” style licenses.

Update 2018/08/24 @ 15:09 — this Twitter thread is a nice read too.

Paul Dix, Founder and CTO of InfluxData, writes on the InfluxData blog:

I attended and spoke at KubeCon EU. It was a massive event attended by around 4,700 people … However, I felt there was an underlying problem … everyone I spoke with was either an operator or an SRE. Where were all the application developers? Aren’t those the people that all this complex infrastructure is supposed to serve?

Which raised questions for Paul, like…

Is Kubernetes too complex?
Will it end up collapsing under the weight of its own complexity?
Will it fade away as OpenStack has seemed to since 2014?

And Paul walked away from KubeCon EU with this perspective:

Application developers would be better served by having a happy path to follow with the tools preselected … CNCF’s increasing complexity and broader reach might dilute the focus and brand of Kubernetes … I’m not sure what the answer might be to this or if I’m overblowing it, but from my perspective at the conference, it was like tool porn. Why bother with solving user problems when you can spend your entire career learning about and building new tools for infrastructure?