Currently, SourceCred puts a very high weight on Discourse activity relative to GitHub activity; for example, the weight on a Discourse topic is 8x higher than the weight for a pull request.
|GitHub Pull Request||1x|
At the time I chose these weights, we had much less Discourse activity than GitHub activity, and I deliberately pumped the Discourse weights so that Discourse contributors would be meaningfully present in the overall distribution. Now that we’ve had a few months of increasing Discourse activity, I think we should re-balance Discourse and GitHub to be closer together.
We can see some need for this in the extreme results from the past week, in which @burrrata did a ton of work around organizing the forums and retroactively creating initiatives and artifacts–which also corresponded to creating a lot of Discourse threads:
Overall, this issue will be structurally fixed by the supernode system, as we move to having cred minted from artifacts rather than minted based on activity levels. While we’re still working on that, however, I will be changing the weights to make our cred better reflect the reality of the project.
Here are the new weights I’m proposing:
|Node Type||Old Weight||New Weight|
|GitHub Pull Request||1x||2x|
I tried to be more consistent between GitHub and Discourse:
- things that are raw posts or comments have
- things that start threads that will contain more posts or comments have
Here a snapshot of the cred that results:
One thing we can immediately see is that “peak GitHub cred” (that @wchargin and I generated together when we were pair-programming) and “peak Discourse cred” (from @burrrata’s work this past week) are fairly similar. This makes sense to me intuitively.