You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g. https://github.com/ssbc/.github/actions/runs/3819652633/jobs/6497388690#step:2:1251mycognosist should be removed, we don't do it. Things keep failing. New folks hack on go-ssb a lot and should get brought into the org. But the CI is failing so they don't get suggested? Should we switch to a warning for this kind of stuff? It always involves a human looking at it and making a decision, so, seems fair? /cc @mycognosist@staltz
The text was updated successfully, but these errors were encountered:
The CI job has run to completion, so it hasn't missed the fact that someone (e.g. new go-ssb contributors) should be added to the org.
The reason why the algo is suggesting mycognosist to be removed is that his TrustNet Org score has dropped a bit over time, dipping a bit under the threshold. I have postponed to remove mycognosist for two reasons: (1) he has been active lately in go-ssb issues so clearly helping, and could volunteer to merge PRs etc, (2) the TrustNet Org algo seems like it needs to be updated because I think the "trust" measurement shouldn't decrease over time, but currently it's decreasing for a lot of people, including me and arj (who are the top 2 at the moment), and that doesn't make sense; I think it makes more sense to use "last active 12 months ago" as the threshold to remove a person. This is something we should discuss when we update the rules of membership this year.
decentral1se
changed the title
afaict ignoring failures blocks new people getting added?
Use last active 12 months ago for trust measurement
Jan 2, 2023
decentral1se
changed the title
Use last active 12 months ago for trust measurement
Use "last active 12 months ago" for trust measurement
Jan 2, 2023
E.g. https://github.com/ssbc/.github/actions/runs/3819652633/jobs/6497388690#step:2:1251
mycognosist
should be removed, we don't do it. Things keep failing. New folks hack ongo-ssb
a lot and should get brought into the org. But the CI is failing so they don't get suggested? Should we switch to a warning for this kind of stuff? It always involves a human looking at it and making a decision, so, seems fair? /cc @mycognosist @staltzThe text was updated successfully, but these errors were encountered: