3 ms·
I did some hacky analysis and roughly half of the PRs originated in GitHub and the majority of those are not google employees. Most changes have a github issue
by gregable 5y ago
I did some hacky analysis and roughly half of the PRs originated in GitHub and the majority of those are not google employees.
Most changes have a github issue attached with discussion, all of the changes have descriptive commit messages regardless of who authored them and there is significant effort to document the decisions and decision process throughout.
I can't speak for the release frequency for other organizations' production that consumes this code. That includes many publishers, as well as other AMP caches such as Bing and webmail clients like Yahoo.
The repo is for all of AMP, not just the validator. The validator related issues are handled by the "caching" working group (since caches are the consumer of the validator) and you can search for them with this query: https://github.com/ampproject/amphtml/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22WG%3A+caching%22 https://github.com/ampproject/amphtml/issues?q=is%3Aissue+is...
- dmitriid 5y ago> PRs originated in GitHub and the majority of those are not google employees. How did you figure that out? There are people don't list their company, but their only activity on GitHub is contributing to AMP. Some people don't list Google, but are a part of the AMP org on GitHub. > all of the changes have descriptive commit messages Please show me all the open decisions that introduced AMP for email. (hint: you can't) As I mentioned in a sibling comment: why are people so surprised that it's Google's product driven by Google's own needs?