To do 2: How to peep a developer's not-so-secret life

[coco-lab-2022]

Ok, I admit the title is misleading.

First, still remember how we plan to do comparisons?

• We have two groups of developers, one group uses "activity overview" while the other doesn't
• We would like to compare: (1) if their pull requests have same acceptance rate? (adding a signal helps or not); (2) demographic and behavioral patterns of developers in these two groups (who would like to add this new signal).

GitHub offers Event API, so for a specific user, we could get his/her events----[https://docs.github.com/en/rest/activity/events]----and of course, including his/her pull requests, then we could track all these pull requests to get their outcomes: ACCEPTED or REJECTED.

Unfortunately, GitHub Event API now only allow one get 300 events per API call, which means we have to peep periodically.
Check: [https://github.community/t/fetching-events-from-public-event-api/120332/2]

For other stuff, we have other ways to deal with them... for example, using Yang Yue's method.

[weiwang310]

For the first comparison (the acceptance rate), the results will be same whether we peep periodically or consistently. Is it right?

For the second one, do we need to peep their behavioral patterns at the same time?