copy
method on Graph
(#109)
Summary: Clients of `Graph` that wish to treat the graph as immutable will benefit from a `copy` method. We should provide it on `Graph` instead of asking clients to reimplement it because it affords us the opportunity to get the type signature right: in particular, copying should allow upcasting of the type parameters, even though `Graph` itself is invariant. Paired with @dandelionmane. Test Plan: Unit tests added. Run `yarn flow` and `yarn test`. To check that downcasting is not allowed, change the types in the new static test case in `graph.test.js` to be contravariant instead of covariant, and note that `yarn flow` fails. wchargin-branch: graph-copy
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.