a reputation protocol for open collaboration
Go to file
William Chargin 791cad9059
Add conversion functions for id (#38)
Test Plan:
Run `yarn test` and note that tests pass.

wchargin-branch: id-conversion
2018-02-26 22:57:00 -08:00
config Move package json to root (#37) 2018-02-26 22:32:23 -08:00
experiments Tweak commit_graph_dump & store sample data. (#12) 2018-02-15 22:16:37 -08:00
flow-typed/npm Move package json to root (#37) 2018-02-26 22:32:23 -08:00
public Move package json to root (#37) 2018-02-26 22:32:23 -08:00
scripts Move package json to root (#37) 2018-02-26 22:32:23 -08:00
src Add conversion functions for id (#38) 2018-02-26 22:57:00 -08:00
.flowconfig Move package json to root (#37) 2018-02-26 22:32:23 -08:00
.gitignore Move package json to root (#37) 2018-02-26 22:32:23 -08:00
.prettierignore Move package json to root (#37) 2018-02-26 22:32:23 -08:00
.prettierrc.json Move package json to root (#37) 2018-02-26 22:32:23 -08:00
LICENSE Add LICENSE 2018-02-03 17:58:49 -08:00
README.md Update README.md (#31) 2018-02-26 17:06:06 -08:00
design.md Split out useful & ethical. (#7) 2018-02-07 15:04:23 -08:00
overview.md Add overview.md (#6) 2018-02-05 00:14:15 -08:00
package.json Move package json to root (#37) 2018-02-26 22:32:23 -08:00
yarn.lock Move package json to root (#37) 2018-02-26 22:32:23 -08:00

README.md

SourceCred

The open-source community provides an enormous amount of value to the world. However, open-source contributors go largely unrewarded and unrecognized. SourceCred aims to help that situation, by building tools that enable quantitatively measuring the value that open-source contributors provide to individual projects, and to the community as a whole.

SourceCred will create a "Cred Graph", which is a graph that shows how the contributions that compose open-source projects are related to and derive value from each other. From this, we'll be able to assign "cred" to users based on how valuable their contributions are. Cred will be assigned based on a mixture of objective data (e.g. references between GitHub pull requests) and subjective feedback (e.g. projects' own judgments on how important different contributions were).

If you'd like to contribute, please join our slack.