+0
日增长
89
stars
1,004
forks
5
watchers
1,285
prs
33
issues
0
releases
README
CNCF gitdm This is the Cloud Native Computing Foundation's fork of Jon Corbet and Greg KH's gitdm tool for calculating contributions based on developers and their companies. Companies and developers can check if they are correctly attributed at the following links: Company Developers list: [co1], [co2], [co3], [co4], [co5], [co6], [co7], [co8]. Developers affiliations list: [dev1], [dev2], [dev3], [dev4], [dev5]. New affiliations are imported into DevStats about once per 4 weeks. DevStats This repository is used as a source of affiliations for all DevStats projects. The final affiliations JSON is periodically imported by the DevStats project. Adding/Updating affiliation If you find any errors or missing affiliations in those lists, please submit a pull request with edits to developers affiliations files: [dev1], [dev2], [dev3], [dev4], [dev5], ... Please note that we need both current and historical email here as we are processing data from GitHub Archives, so old emails are there (even if they are no longer current). We need historical emails to track historical data (GitHub archives save events every hour, so they contain data as they were at given point in time). Only the Developers affiliations list [dev1], [dev2], [dev3], [dev4], [dev5], ... should be edited manually. Company Developers lists [co1], [co2], [co3], [co4], [co5], [co6], [co7], [co8] are computed derivatives of the first list. Other files used for affiliations are the email map file and github users file. Please note that cncf/gitdm affiliations are imported into DevStats (cncf/devstats) once per 4 weeks. Removing affiliations If you do not want to have your email listed here please read how to remove your email. Testing changes You can test any changes locally by cloning this repository and regenerating all data by running ./rerun_data.sh. Then generate config files by running: ./import_affs.sh. If those two files are out of sync, the tool will notify you about this. This tool will generate a new email-map file. Check if your changes processed properly and move the file to cncf-config/email-map (replace) Sync workflow Please follow the instructions from SYNC.md. Running Use .sh scripts to run analytics (all.sh for full analysis and rels.sh for per release stats) Convenience wrappers: - Unix shells: pipe git log into ./gitdm instead of calling src/cncfdm.py directly; the wrapper auto-selects a Python 2/PyPy interpreter and points -b to src/. - PowerShell: use ./gitdm.ps1 similarly. This program assumes that gitdm resides in: ~/dev/cncf/gitdm/ and that kubernetes is in ~/dev/go/src/k8s.io/kubernetes/ Output files are placed in the kubernetes directory. To regenerate all statistics just run: ./rerun_data.sh This is an iterative process: Run any of the scripts. Review its output in the kubernetes directory. Iteratively adjust mappings to handle more authors. You can also run via ./debug.sh to halt in debugger and review the hacker's structur