01510ca63f
Summary: We’ve realized that `u: Edge<T>` implies `u: Node<T>`. That certainly wasn’t what we were expecting! We might want something like that eventually, to capture the fact that valuations are themselves valuable, but for now the type system should encode the assumptions that we’re actually making. See also #50. Paired with @dandelionmane. wchargin-branch: exact-types |
||
|---|---|---|
| config | ||
| experiments | ||
| flow-typed/npm | ||
| public | ||
| scripts | ||
| src | ||
| .flowconfig | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| LICENSE | ||
| README.md | ||
| package.json | ||
| yarn.lock | ||
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.