The company is separating the roles of chairman and president.
In case you missed it, this week we’re celebrating Docker’s 4th Birthday with meetups all over the world (check out #dockerbday on twitter). This feels like the right time to look back at the past 4 years and reflect on what makes the Docker Community so unique and vibrant: people, values, mentorship and learning opportunities. You can read our own Jérôme Petazzoni’s blog post for a more technical retrospective.
Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges. Last year, Arnaud Porterie wrote a very interesting 3-part series blog post on open source at Docker covering the different challenges associated with the People, the Process and the Tooling and Automation. The most important aspect of all being the people.
Respect, fairness and openness are essential values required to create a welcoming environment for professionals and hobbyists alike. In that spirit, we’ve launched a scholarship program and partnerships in an attempt to improve opportunities for underrepresented groups in the tech industry while helping the Docker Community become more diverse. If you’re interested in this topic, we’re fortunate enough to have Austin area high school student Kate Hirschfeld presenting at DockerCon on Diversity Continue reading
Over the last few months, I’ve noticed that some pages on this site have been returning what appear to be corrupted pages, looking something like this:
Or like this:
Pretty, aren’t they? Typically if the user hits refresh the page will come back as it should have done first time. I’ve been working for many weeks now to track down why this was happening. One thing I noted is that the corrupted files were smaller than the non-corrupted equivalent, suggesting that the file was either truncated or, more likely, compressed. Opening a downloaded file in a text editor showed that the header of these corrupted pages begins like this:
Some of you are probably feeling smug right now because you know that the first three bytes of a gzip file are 1F 8B 08. The ASCII code for 0x1F is Ctrl-_; there’s no code for 0x8B; ASCII 0x08 is the same as Ctrl-H (i.e. backspace). This should look familiar in the image above: ^_ <8B> ^H. In other words, the client is receiving a GZIPped version of the page but presumably was told that the mime type was text/html. The end result is the garbled mess we saw above. So now Continue reading
The post Worth Reading: Fat Finger Folly appeared first on 'net work.