To be fair, they're doing really well, and their base service is already humming along. All they can do is support, tweak, and release features. Pretty good position.
Why is the traffic graph never working? I was excited to hear the graphs were updated and assumed the traffic graph would finally be working again, but no it is still "temporarily down."
Until you send it large data sets (and this applies to any client side rendering) and it uses 100% of a core and causes the browser to hang (go checkout the rails or other large graph pages on github)... There has to be better solutions out there that Github could use
This page https://github.com/torvalds/linux/graphs/impact freezes FF12 on W7/x64 for several seconds, and then FF asks if to continue running the script or if to stop it. Continuing re-freezes Firefox.
Hm, I was able to close the tab after telling Firefox to stop the script. However, my browser certainly was frozen for several seconds before I was able. FF12 on OSX.
I built http://gitego.com a few months back to keep track of watchers, forks, size, and issues over time. I'm glad they're enhancing the code-related graphs. Stats for those would be much harder to gather externally.
Weekday and hour of commit times (relative to the commiter's timezone; I remember the previous version used some GitHub timezone). Not sure if they use CommitTime or AuthorTime.
I was really hoping for a graph of commits as well though, ala git log --graph . I know the network graph is intended for this, but it fails pretty badly.
Thank you Github! I was just hoping that the graphs would get updated. This gives me better oversight into who/what/where/when. Although perhaps a bug - my punch card graph is empty.
I've been hoping that they would add some more graphs. Looking at either how much impact (or lack of) I made in the last week is one of the tools that I use to keep to myself motivated
This is a huge improvement - especially the Contributors chart is plain awesome and they finally load fast. On the other hand I still don't see any sense in the Punchcard.
The punchcard might conceivably be useful for attempting to coordinate with the developers at the time when they're most active. Other than that, it does sort of feel like they just had a bunch of data lying around that they felt really needed to be shoved into a graph.
It actually plots the local time, i.e. a commit at 3am PDT and another at 3am EST would contribute to the same circle on the plot. (I did a clone of the old GitHub graphs a while back.) So it isn't really useful for knowing when to contact faraway developers. On the other hand, it is fun to see how many committers are regular night owls.
I don't know--looking at the punch card gives me a good idea of when contributors to a project are active. This could be useful if I want to contact them about something over IRC, for example.
Also, it's just amusing to see people I know regularly comitting at 3am.
EDIT: Illustrated/Ranted about here: http://gun.io/blog/github-network-graph-is-broken/