It is a jekyll blog, and there are many authors, which is really what makes the copyright situation hard. I am working on contacting everyone to clarify their intention, as it was within MS rights to shut the site down, and it's within any author's rights to ask that their work not be republished, and to my knowledge nobody collected copyright releases at any point, so there is no person who can simply authorize it for everyone.
All of the few Deis team members that I've contacted so far, though, have been very receptive to having their work re-published and excited to hear about Team Hephy, which was created to continue some of the work that had to be left behind by Deis, so that they could better follow the demand.
I want to do it in a way that is thoughtful and fair. It's also hard to justify reposting everything when I don't have a plan to balance it with an equal amount of good quality, new content as well. Maybe I need to bite the bullet and take my SEO points, it will almost certainly drive more traffic to our site.
Do you have an "in" at Archive.org, or would you re-host them somewhere else? I'm more worried that when I repost them, they are still not going to be easy to find, and if they weren't in the history of deis.com, that sure won't make it any easier.
I realized I was definitely going to miss the content when I found this post[1] that was just what I was looking for, about the options for schedulers and what it means to have a monolithic scheduler, back when they were considering whether to rewrite Deis on Kubernetes (they did, it became known as Workflow). It came from the original Deis blog.
I don't know if it looks out of place on the new blog, or if it will make sense to grow this one post at a time, I think I don't like this blog, it was just thrown together one day when I said "we need a place to put a release announcement." I like the material style better than anything I myself could come up with alone, but honestly that's hardly a shining endorsement. Could be much better.
> I put my commas after closing quotation marks, because that's what programmers do.
Your blog is really nice, I went through and found the webcam thing[2] and just wanted to call that out!
It is a jekyll blog, and there are many authors, which is really what makes the copyright situation hard. I am working on contacting everyone to clarify their intention, as it was within MS rights to shut the site down, and it's within any author's rights to ask that their work not be republished, and to my knowledge nobody collected copyright releases at any point, so there is no person who can simply authorize it for everyone.
All of the few Deis team members that I've contacted so far, though, have been very receptive to having their work re-published and excited to hear about Team Hephy, which was created to continue some of the work that had to be left behind by Deis, so that they could better follow the demand.
I want to do it in a way that is thoughtful and fair. It's also hard to justify reposting everything when I don't have a plan to balance it with an equal amount of good quality, new content as well. Maybe I need to bite the bullet and take my SEO points, it will almost certainly drive more traffic to our site.
Do you have an "in" at Archive.org, or would you re-host them somewhere else? I'm more worried that when I repost them, they are still not going to be easy to find, and if they weren't in the history of deis.com, that sure won't make it any easier.
I realized I was definitely going to miss the content when I found this post[1] that was just what I was looking for, about the options for schedulers and what it means to have a monolithic scheduler, back when they were considering whether to rewrite Deis on Kubernetes (they did, it became known as Workflow). It came from the original Deis blog.
I don't know if it looks out of place on the new blog, or if it will make sense to grow this one post at a time, I think I don't like this blog, it was just thrown together one day when I said "we need a place to put a release announcement." I like the material style better than anything I myself could come up with alone, but honestly that's hardly a shining endorsement. Could be much better.
> I put my commas after closing quotation marks, because that's what programmers do.
Your blog is really nice, I went through and found the webcam thing[2] and just wanted to call that out!
[1]: https://blog.teamhephy.info/posts/schedulers-pt1-basic-monol...
[2]: https://rahul.webcam/