007cf88172
Summary: We need to know the repo owner and name for purposes other than fetching the GitHub graph: for instance, fetching the `artifacts.json` file that describes the artifact subgraph. It makes sense that these should be settings global to the application. This commit separates a settings component and the original GitHub graph fetcher. This invalidates localStorage; you can manually migrate. Paired with @dandelionmane. Test Plan: Note that the data continues to be stored in localStorage and that it is updated on each keypress. Note that the state is properly passed around: if you change the repository name from `example-repo` to `sourcecred`, e.g., and click “Fetch GitHub graph”, then the proper graph is fetched. wchargin-branch: separate-artifact-settings |
||
---|---|---|
config | ||
experiments | ||
flow-typed/npm | ||
scripts | ||
src | ||
.flowconfig | ||
.gitignore | ||
.prettierignore | ||
.prettierrc.json | ||
.travis.yml | ||
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 follow along with our issues, as we are using issues to coordinate development and design decisions. We also have a slack.