Skip to content
This repository has been archived by the owner on Oct 12, 2020. It is now read-only.

Improvement to the algorithm #44

Open
chaitanyarahalkar opened this issue Jul 18, 2019 · 2 comments
Open

Improvement to the algorithm #44

chaitanyarahalkar opened this issue Jul 18, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request
Projects
Milestone

Comments

@chaitanyarahalkar
Copy link

#42 Yeah consider developer program guys and users who are a part of some organization!

@Ullaakut Ullaakut self-assigned this Jul 19, 2019
@Ullaakut Ullaakut added the enhancement New feature or request label Jul 19, 2019
@Ullaakut Ullaakut added this to To do in v1.1 via automation Jul 19, 2019
@Ullaakut Ullaakut added this to the v1.1 milestone Jul 19, 2019
@InnovativeInventor
Copy link

@Ullaakut What about looking at followers (i.e. if there are some followers with really good reputations/repos, then the person should be considered more trustworthy). Through this, we could slowly build up a graph of reputable people/repos (creating something like a web of trust) and start to factor in their connections. I'd be willing to pitch in to see if this helps!

@InnovativeInventor
Copy link

Another idea might be to look at issues opened/discussions made and the length/people who responded (it is hard for bots to have genuine comments). The ideas I suggested can all (maybe) be combined into a NetworkFactor, using some set of weights. I'm thinking that we can use all the users connected to verified organizations to train the weights (they should be real people). @Ullaakut

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
v1.1
  
To do
Development

No branches or pull requests

3 participants