Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CredCon contributions missing #30

Open
Beanow opened this issue Apr 10, 2020 · 0 comments
Open

CredCon contributions missing #30

Beanow opened this issue Apr 10, 2020 · 0 comments
Labels
cred issue Something is missing or unfair about our Cred attribution

Comments

@Beanow
Copy link

Beanow commented Apr 10, 2020

As many of the CredCon contributions were not tracked by data plugins (GitHub / Discourse) we're missing a feature in the Initiatives plugin to track these and attribute Cred.

For now that means we're only technically able to define Initiatives and link that to Champions.
Attribution would be a lot more fair with the ability to include Contributions and their Contributors.

The feature is being tracked in sourcecred/sourcecred#1739
Once available we should use it here to add CredCon's contributions.

@Beanow Beanow added the cred issue Something is missing or unfair about our Cred attribution label Apr 10, 2020
Beanow added a commit that referenced this issue Apr 10, 2020
* Preview: Add a first batch of initiatives to the project

## This is a first iteration

Rather than letting this stall for too long, let's improve on this with follow ups.
Have a look at #29 for info on how to go from here.

This is a first iteration, as it's in need of another weighting round.
Still missing from this, but identified at the team call:
- CredCon: video interviews (need a user account for zak)
- CredCon: CredRank prototype (have not decided fibonacci weight)
- CredCon: Discord prototype (have not decided fibonacci weight)
- Evan's explainer (have not decided fibonacci weight)

Also great improvements to make from here:
- Adding contributions and linking that to contributors (see #30)

Good but not as critical:
- Making the timestamps more accurate

## Fibonacci to absolute weights: 100x first, 200x later

The 200x multiplier seems in the right ballpark, however we want to
avoid champions see Cred "dilute" because we'll add more contributions.

Start with 100x now, and move to 200x as we have a more complete coverage.
Tracking this in issue #31.

## Other assumptions made

### Dependency structure

For the activities as part of CredCon (like hackathon, party, talks), I
found they had very similar dependencies on logistical initiatives and
CredCon itself. I've generalized this by depending on CredCon, rather than
directly depending on logistics.

Example: CredCon party, depends on CredCon, depends on car+food+lodging

This will make the life of historians easier too, as adding more logicstics
(maybe invites or scheduling) would only need to be set as a CredCon
dependency, rather than for all activities as well.

### Example references / contributions

For the main CredCon initiative, I've added several clearly related forum
topics. These are both as an example, and to make sure this part of the
graph is not exclusively connected through identities.

### Completion status

Other than both Partner initiatives, the CredCon initiatives are set as
completed.

## Technical aspects to validate

The main point which needs careful manual validation, is to inspect the
graph. For example using the "legacy explorer" to confirm the initiative
nodes are added and have edges to *all* the URLs added.

That means:
- Champions: Identities / GitHub users / Discourse users.
- References / Contributions: Forum topics (in CredCon).
- Dependencies between Initiatives.

Note: it's expected for links to an initiative to give a 404 not found,
until the PR is merged to master. However they should be listed in the
explorer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cred issue Something is missing or unfair about our Cred attribution
Projects
None yet
Development

No branches or pull requests

1 participant