-
Notifications
You must be signed in to change notification settings - Fork 210
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
Add a meritocracy #377
Add a meritocracy #377
Conversation
For anyone else looking through this PR, it's a lot easier to read if you append |
@mark-i-m yes definitely do that hopes nobody notices my trojan horse coded in Whitespace |
👍 What can possibly go wrong? |
if vote and vote_owner != pr_owner: | ||
votes[vote_owner] = vote | ||
for vote_owner, is_current, vote in get_pr_review_votes(api, urn, pr): | ||
if (vote > 0 and is_current and vote_owner != pr_owner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be vote_owner.lower() != pr_owner.lower()
? i.e. are we sure the cases match?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's how it was, and it works since they both come from the GitHub API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that's what I thought
@phil-r your comment keeps duplicating client-side: No idea why. It seems to be a GitHub bug. The bug survives a refresh, although the duplicated comment versions don't. Edit: posting another comment seems to have fixed it. |
@PlasmaPower I've also noticed, refresh helped, maybe I've triggered some easter egg? 🐰 🥚 |
@phil-r I think it's actually a bug with reviews. It only seems to happen when the comment is next to a review. Overall, reviews are poorly implemented IMO. |
When you fix a minor mistake but it resets the voting window 😢 I guess #378 wins the merge conflict race. |
Hey! 🎉 |
What was the fix? |
@mark-i-m In |
Btw @PlasmaPower you down voted your PR by crying in the post above... |
@mark-i-m lol oops. 👍 I think that fixes it? Edit: yep |
Reminds me of when reactions to comments counted for the PR as a whole. |
Had to do another slight fix: |
@PlasmaPower Are you squashing the commits in your own fork? |
@mark-i-m Oh yeah, I probably shouldn't now that chaosbot squashes them for us. Doesn't make much of a difference though, and there's no added security - I could always amend a malicious change to a previous commit. |
I have my 👁️ on you |
waits until @mark-i-m goes to sleep /s |
Or do you sleep with that eye open? |
You don't know if I sleep (at the same time as you) |
I just realized I forgot to pass |
@PlasmaPower this solution looks very good! So at least one member of this group has to do a review seperately from voting. So people needs to know if they are in this group and that it's helpful if they review. Also that they have responsibility for the project doing it. It would be good if you add that to the readme and we need some kind of news section to inform the community of such important changes. |
@PlasmaPower If this get's merged you can mention everyone currently in the list so they know that they now have this opportunity. |
Current meritocracy: @chaosbot, @muchzer, @pchauncey, @amoffat, @hongaar, @rhengles, @rudehn, @xyproto, @eukaryote31, @ad-m, @mark-i-m, @Smittyvb, @reddraggone9, @PlasmaPower, @phil-r I've updated the README, pushing the changes in a second. The meritocracy will be logged every time chaosbot checks for new PRs. (yes I know chaosbot is in the list, but hardcoding chaosbot is both unnecessary and probably a bad idea. chaosbot will also fade from the list as merge commits give way to squashes) |
Okay, both of those changes have been pushed. Ready to merge! 🎉 Other slight updates can wait for another PR, I'll only add on important fixes. (now to wait 9 hours because the extended voting window is broken... 😴) |
Rebased - fixed |
The Travis failure appears to be from master. Edit: yep, fixed in #390 |
It doesn't have to be dynamic. How I currently have it written is to update a |
This is something nice, @PlasmaPower. Though it chooses the same set of ppl, more or less, but look at the response. 😄 |
@tarunbatra It's also nice that it automatically updates itself. I might adjust the config later though. |
The difference there is that |
I completely agree |
🙆♀️ PR passed with a vote of 30 for and 1 against, with a weighted total of 27.5 and a threshold of 6.5. See merge-commit 3e6d99c for more details. |
well well well... another regime change by @PlasmaPower! |
For some reason, this duplicated the object in { "amoffat": 12468, "g19fanatic": 1442, ... }{ "amoffat": 12468, "g19fanatic": 1442, ... } |
That might also remove the top 10 voters part of the meritocracy. Anybody know what's causing it? |
It's also crashing repeatedly http://chaosthebot.com:8081/chaos-stderr.log |
Oh I think that's caused by two PRs being merged at the same time. I'll get a fix ready. |
So what happens when somebody who is in the meritocracy reviews the PR, but falls out of the meritocracy before the PR is merged? Does the review no longer count? |
I believe that the next time the PR gets polled, the review will no longer count. |
Is that working as intended, or a bug? |
That's how it works, and there's really no way to fix it unless we get the database up and running (even then it'd be a bit of a pain). |
@PlasmaPower This is supposed to be chaos - who knows? |
#392: Update README in anticipation of #377 Description: :ok_woman: PR passed with a vote of 20 for and 0 against, a weighted total of 19.5 and a threshold of 6.5, and a current meritocracy review. Vote record: @Ayyko: 1 @Leigende: 1 @MUCHZER: 1 @Mursaat: 1 @Smittyvb: 1 @SylvainThrd: 1 @andrewda: 1 @cthulhuely: 1 @davidak: 1 @eukaryote31: 1 @flibustier: 1 @hongaar: 1 @ike709: 1 @md678685: 1 @mikesmiffy128: 1 @phil-r: 1 @reddraggone9: 1 @rhengles: 1 @rudehn: 1 @viktorsec: 1
I decided to not go with a clickbait title this time 😄
Look at #361 for more details, but I tried to give the meritocracy minimal power. Democracy still decides the outcome >90% of the time. This is just to prevent against sneaky take over attempts.
Basis of how it works:
Changes from #361: