The user interactions in the comment/review process on github or gerrit are a huge part of the open-source community but git log (thus facade) does not reflect any of that activity. I suppose there are multiple parts here, here's a SWAG:
- analyze minimum viable data items to capture essence of github and gerrit reviews (other systems?) generically including merge/pull requests, change sets, votes, comment stats (comment count, comment size, ..) and more. In other words, hopefully there will be a data item "change_count" and not "github_pull_request_count" plus "gerrit_change_set_count".
- define database schema that can accommodate the data with least possible duplication
- define interfaces in Facade to for storing/extracting/using these new data items
- build plug-ins that use Facade interfaces, that query github, gerrit, (other systems?) to pull the review activity data via JSON or whatever and push to facade
- build plug-in (hopefully singular, not specific to gerrit/github) to analyze and publish the review activity data
This Apache-licensed project for github might have usable code, last commit 2018 https://github.com/Netflix/osstracker
This MIT-licensed project for gerrit might have usable code, also last commit 2018 https://github.com/holmari/gerritstats
The user interactions in the comment/review process on github or gerrit are a huge part of the open-source community but git log (thus facade) does not reflect any of that activity. I suppose there are multiple parts here, here's a SWAG:
This Apache-licensed project for github might have usable code, last commit 2018 https://github.com/Netflix/osstracker
This MIT-licensed project for gerrit might have usable code, also last commit 2018 https://github.com/holmari/gerritstats