-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDN Changelog, January 2018 #77
Conversation
The "Kuma Report" is increasingly inaccurate, since most of the changes are happening in the data projects.
With 3.6.2 and beyond, the Jekyll docker image uses Bundle rather than Depends, which allows limiting chown to select folders. This speeds up startup on macOS to 5-10 seconds for chown and 1 minute to serving content.
@@ -1,11 +1,11 @@ | |||
#!/usr/bin/env python | |||
# -*- coding: utf-8 -*- | |||
""" | |||
Generates the Kuma Report Template. Requires 3rd-party libraries | |||
Generates the MDN Changelog Template. Requires 3rd-party libraries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be MDN Development Changelog
, as content changelog is not covered here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my perspective, "Changelog" implies development, so "Development Changelog" would be redundant. I'm curious what others think. And yes, I don't plan to start summarizing what's going on with MDN content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vote is 1-1, and since I'm the author, I break the tie.
The AWS chart shows the long-term trend of lower traffic.
I'm renaming the Kuma Report to the MDN Changelog for 2018, since Kuma is increasingly a smaller part of what happened in the code, tools, and data behind MDN. This required some updates to the template script, and I needed to automate and improve the reporting for the 67 PRs from first-time contributors to make it possible to write the report.
The new Jekyll Docker image has taken care of some of the issues that made it so slow on macOS, so I've made the warnings in the README less dire.
The report:
And for next month:
I'm aiming for Tuesday, February 6.