737ed4d8b3
This commit builds on the work in #806, adding the `MentionsAuthorReference`s to the graph. It thus resolves #804. Empirically, the addition of these edges does not change the users' cred distribution much. Consider the results with the following 3 forward weights for the edge (results for ipfs/go-ipfs): | User | w=1/32 | w=1/2 | w=2 | |---------------|-------:|-------:|-------:| | whyrusleeping | 228.04 | 225.69 | 223.86 | | jbenet | 102.04 | 100.26 | 99.53 | | kubuxu | 66.60 | 67.80 | 69.36 | | ... | — | — | — | | btc | 22.69 | 22.29 | 21.38 | The small effect on users' cred is not that surprising: the MentionsAuthor references always "shadow" a direct comment->user reference. In principle, the overall cred going to the user should be similar; the difference is that now some more cred flows in between the various comments authored by that user, on the way to the user. (And if those other comments had references, then it flows out from them, etc.) Empirically, the variance on comments' scores seems to increase as a result of having this heuristic, which is great—the fact that all comments had about the same score was a bug, not a feature. Sadly, we don't have good tooling for proper statistical analysis of the effect this is having. We'll want to study the effect of this heuristic more later, as we build tooling and canonical datasets that makes that analysis feasible. We choose to add this heuristic, despite the ambiguous effect on users' cred, because we think it is principled, and adds meaningful structure to the graph. Test plan: The commit is a pretty straightforward generalization of our existing GitHub edge logic. All of the interesting logic was thoroughly tested in the preceding pull, so this commit just tests the integration. Observe that standard (de)serialization of the edge works, that the snapshot is updated with a MentionsAuthor reference edge, and that the graph invariant checker, after update, does not throw errors. Also, I manually tested this change on the ipfs/go-ipfs repo. (It does not require regenerating data.) |
||
|---|---|---|
| config | ||
| flow-typed/npm | ||
| scripts | ||
| sharness | ||
| src | ||
| .eslintrc.js | ||
| .flowconfig | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| package.json | ||
| yarn.lock | ||
README.md
SourceCred
SourceCred creates reputation networks for open-source projects. Any open-source project can create its own cred, which is a reputational metric showing how much credit contributors deserve for helping the project. To compute cred, we organize a project’s contributions into a graph, whose edges connect contributions to each other and to contributors. We then run PageRank on that graph.
To learn more about SourceCred’s vision and values, please check out our website and our forum. One good forum post to start with is A Gentle Introduction to Cred.
For an example of SourceCred in action, you can see SourceCred’s own prototype cred attribution.
Current Status
We have a prototype that can generate a cred attribution based on GitHub interactions (issues, pull requests, comments, references, etc.). We’re working on adding more information to the prototype, such as tracking modifications to individual files, source-code analysis, GitHub reactions, and more.
Running the Prototype
If you’d like to try it out, you can run a local copy of SourceCred as follows. First, make sure that you have the following dependencies:
- Install Node (tested on v8.x.x).
- Install Yarn (tested on v1.7.0).
- Create a GitHub API token. No special permissions are required.
- For macOS users: Ensure that your environment provides GNU coreutils. See this comment for details about what, how, and why.
Then, run the following commands to clone and build SourceCred:
git clone https://github.com/sourcecred/sourcecred.git
cd sourcecred
yarn install
yarn backend
export SOURCECRED_GITHUB_TOKEN=YOUR_GITHUB_TOKEN
node bin/sourcecred.js load REPO_OWNER/REPO_NAME
# this loads sourcecred data for a particular repository
yarn start
# then navigate to localhost:8080 in your browser
For example, if you wanted to look at cred for ipfs/js-ipfs, you could run:
$ export SOURCECRED_GITHUB_TOKEN=0000000000000000000000000000000000000000
$ node bin/sourcecred.js load ipfs/js-ipfs
replacing the big string of zeros with your actual token.
You can also combine data from multiple repositories into a single graph.
To do so, pass multiple repositories to the load command, and specify an “output name” for the repository.
For instance, the invocation
node bin/sourcecred.js load ipfs/js-ipfs ipfs/go-ipfs --output ipfs/meta-ipfs
will create a graph called ipfs/meta-ipfs in the cred explorer, containing the combined contents of the js-ipfs and go-ipfs repositories.
Early Adopters
We’re looking for projects who want to be early adopters of SourceCred! If you’re a maintainer of an open-source project and would like to start using SourceCred, please reach out to us on our Discord or our forum.
Contributing
We’d love to accept your contributions! You can reach out to us by posting on our forum, or chatting with us on Discord. We'd be happy to help you get started and show you around the codebase. Please also take a look at our contributing guide.
If you’re looking for a place to start, we’ve tagged some issues Contributions Welcome.
Acknowledgements
We’d like to thank Protocol Labs for funding and support of SourceCred. We’d also like to thank the many open-source communities that produced the software that SourceCred is built on top of, such as Git and Node.