Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAnalytics on TC39 sites, e.g., the specification page #1167
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mathiasbynens
Apr 11, 2018
Member
I agree it would be interesting to get analytics for https://tc39.github.io/ecma262/.
Note that for the repository itself, such data is already available at https://github.com/tc39/ecma262/graphs/traffic. I wouldn’t be surprised if the number of hits/visits to the repo already exceeds the number of PDF downloads on Ecma’s website.
|
I agree it would be interesting to get analytics for https://tc39.github.io/ecma262/. Note that for the repository itself, such data is already available at https://github.com/tc39/ecma262/graphs/traffic. I wouldn’t be surprised if the number of hits/visits to the repo already exceeds the number of PDF downloads on Ecma’s website. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
littledan
Apr 11, 2018
Member
@mathiasbynens Thanks for the reference. Does this give us any insight on how many people go to the specification draft itself?
|
@mathiasbynens Thanks for the reference. Does this give us any insight on how many people go to the specification draft itself? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
No, unfortunately. We’d need separate analytics for that. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
domenic
Apr 11, 2018
Member
FWIW we've struggled with this in the WHATWG and so far come down against tracking people when they land on specs; we have a single analytics tracker for the homepage of whatwg.org and nothing else.
I'll be curious to see what TC39 does here, and how it is received by the community. I polled once and got mixed results: https://twitter.com/domenic/status/889982507432660992
Server-side analytics seem like the best answer, but those aren't available on GitHub pages unfortunately.
|
FWIW we've struggled with this in the WHATWG and so far come down against tracking people when they land on specs; we have a single analytics tracker for the homepage of whatwg.org and nothing else. I'll be curious to see what TC39 does here, and how it is received by the community. I polled once and got mixed results: https://twitter.com/domenic/status/889982507432660992 Server-side analytics seem like the best answer, but those aren't available on GitHub pages unfortunately. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
xtuc
Apr 11, 2018
Member
Note that the folks going on the spec are most likely those blocking tracker/analytics on websites. I wouldn't expect the stats to be super precise.
|
Note that the folks going on the spec are most likely those blocking tracker/analytics on websites. I wouldn't expect the stats to be super precise. |
littledan commentedApr 11, 2018
I don't want to invade anyone's privacy, but we may benefit from adding some basic tracking to TC39's specification. For example, if we had the download count, this would be useful to compare against the download count for specifications on Ecma's website. This data was requested by the Ecma Executive Committee in the April 2018 Face to Face meeting.