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

Update criteria scores based on crowd-sourced opinions #1686

Merged
merged 1 commit into from
Mar 6, 2025
Merged

Conversation

benjie
Copy link
Member

@benjie benjie commented Mar 6, 2025

Opinions were gathered via this spreadsheet:

https://docs.google.com/spreadsheets/d/1FG8f4lhIm6bPSWXgXrYvZQ32vnwhOPV9Pg6pQbZ9-nU/edit?gid=0#gid=0

The average of the scores were then taken, and then the results bucketed with even sized ranges such that [1, 1.6667) went into bucket 1, [1.6667, 2.3333) went to bucket 2, and [2.3333, 3] went into bucket 3.

The only result of this that I found particularly surprising is that having obvious syntax is rated higher than ensuring that existing deployed operations don't break or change meaning! I honestly thought that one would be 1's across the board 😅

Please continue to provide ratings!

@benjie benjie merged commit 3441a2d into main Mar 6, 2025
2 checks passed
@benjie benjie deleted the update-scores branch March 6, 2025 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant