Dandelion Mané 811bf32968
Move plugin configs to config/plugins (#1907)
This changes the instance system structure so that all the
plugin-specific configs are organized under
`config/plugins/$OWNER/$NAME` instead of `config/$OWNER/$NAME`. I think
this is a somewhat clearer structure; since `config/` will hold other
files (e.g. `weights.json` or `params.json`), I think it's cleaner if
everything plugin-specific is under it's own clearly scoped folder. This
avoids potential confusion if we ever have plugins with very
generic-named organizations, e.g. "config".

Test plan: The test instance has been updated, and the sharness test
loading still works.
2020-06-30 11:24:23 -07:00
2020-03-14 12:31:02 -07:00
2020-06-27 23:21:56 -07:00
2020-06-27 23:21:56 -07:00

SourceCred

Build Status Discourse topics Discord

SourceCred allows communities to assign Cred scores, which measure the value that contributors have brought to the community. The community can then use the scores to distribute rewards (e.g. project-specific Grain tokens) to their contributors.

Cred is computed by constructing a Cred Graph showing every contribution to a project, and then running a version of the PageRank algorithm to assign scores to every contribution and contributor.

We currently support loading data from GitHub, Discourse, Discord, and via custom "initiatives".

Please check out our website for more information. If you'd like to get involved as a contributor, please drop by our Discord and say "hi"!

Current Status

SourceCred is still in beta; as such, the interfaces are in flux and the documentation is spotty. We're working on a polished release which will include more documentation, and more maintainable instances. We expect this to land by early July.

For now, if you want to use SourceCred, you might start by forking MetaGame's Cred Instance.

Note that our next release (v0.7.0) will totally revamp how SourceCred instances are setup, and replace the CLI. As such, expect that migrating from v0.6.0 to v0.7.0 will involve making changes to your configuration.

Development Setup

You'll still need to create a GitHub token to use as an environment variable (shown later). First, run the following commands to clone and build SourceCred:

git clone https://github.com/sourcecred/sourcecred.git
cd sourcecred
yarn install
yarn build
export SOURCECRED_GITHUB_TOKEN=YOUR_GITHUB_TOKEN

Once that's been setup, you can start running SourceCred development commands. In master, the commands are currently in flux. This README will be updated when we have a stable CLI again.

License

SourceCred is dual-licensed under Apache 2.0 and MIT terms:

Acknowledgements

Wed like to thank Protocol Labs for funding and support of SourceCred.

Description
a reputation protocol for open collaboration
Readme
Languages
JavaScript 96.1%
Shell 3.7%
Python 0.1%