The Events API originally seemed like a reasonable way to get a lot of disparate information such as commits, issues created, etc.
However, it has serious limitations in that you cannot get data older than 90 days, nor can you retrieve more than the most recent 300 events.
It should be possible to derive additional contribution data (basically anything not related to a commit) leveraging other APIs. For example, to gather information about issue creators, we could pull all of the issues from a repository and perform aggregations. Things like wiki updates would need to go through yet another API.
The overall development effort of using separate APIs to get the information is not inconsequential; thus using the Events API may have been a good "first pass", it doesn't provide the most complete picture.
The Events API originally seemed like a reasonable way to get a lot of disparate information such as commits, issues created, etc.
However, it has serious limitations in that you cannot get data older than 90 days, nor can you retrieve more than the most recent 300 events.
It should be possible to derive additional contribution data (basically anything not related to a commit) leveraging other APIs. For example, to gather information about issue creators, we could pull all of the issues from a repository and perform aggregations. Things like wiki updates would need to go through yet another API.
The overall development effort of using separate APIs to get the information is not inconsequential; thus using the Events API may have been a good "first pass", it doesn't provide the most complete picture.
See #4 for pulling commit-related data.
cc @xdamman @asood123