Three years ago, I was part of a team responsible for developing and maintaining Kubernetes clusters for end user customers. A main source for downtime in customer environments occurred when image registries went down. The traditional way to solve this problem is to set up a stateful mirror, however we had to work within customer budget and time constraints which did not allow it. During a Black Friday, we started getting hit with a ton of traffic while GitHub container registries were down. This limited our ability to scale up the cluster as we depended on critical images from that registry. After this incident, I started thinking about a better way to avoid these scalability issues. A solution that did not need a stateful component and required minimal operational oversight. This is where the idea for Spegel came from.
I completely agree, but isn’t this what the developer signed up for when they chose the MIT Licence? not that ms couldn’t just ignore a GPL Licence, but still
Read the article first.
That’s my takeaway even after reading the article. MIT license bad.
But they didn’t follow the MIT license either, at least from my understanding. And yes, GPL would have been a better choice.
I’ve heard enough other horror stories to know not to publish anything under the MIT license. Granted they are different, but what happened to BSD should be enough deterrent to not use those types of licenses.