Consider correct reputation amounts for different labels #6440
Comments
|
Remember that this is a bad reflection of reality as we attached massive to get the rep that we were supposed to have for things that don't have PRs |
|
Should we pin this for increased visibility temporarily? |
|
What would help to sort this out would be if maintainers could leave a note on how many hours they roughly spent on the items above or anything else they would usually classify as @SleeplessByte The list is just for a rough impression of potential examples. The real question is the number of hours for the labels. @kotp exercism/exercism is visited by a lot of non-maintainers that probably can't give input on this so I don't think pinning would help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in exercism/docs#347, the amount of reputation that we award for PRs/issues could perhaps use some fine-tuning. Getting these numbers right is very difficult, but it is worth the effort to see if the current values make sense.
As per the above-mentioned discussion, it seems that the large/massive PRs are likely the ones which might need some tweaking. As a starting point to get them right, lets examine the existing large and massive PRs:
Large
{gh search prs --limit 200 --label 'x:size/large' --json 'author,repository,title,url' --merged --jq '.[] | .repository.nameWithOwner + " | " + .title + " | " + .author.login + " | " + .url'; gh search prs --limit 200 --label 'x:rep/large' --json 'author,repository,title,url' --merged --jq '.[] | .repository.nameWithOwner + " | " + .title + " | " + .author.login + " | " + .url' } | sort -t\| -k1 | awk 'BEGIN{print "repo | title | author | url"; print "-- | -- | -- | --"}1'city-office(docsandtypespecs)dancing-dots(useandbehaviour)top-secret(concept:ast)new-passport(concept:with)take-a-number-deluxe(genserver)food-chainkiller-sudoku-helperresistor-color-duoresistor-color-triorest-apisgf-parsingsquare-rootstate-of-tic-tac-toevariable-length-quantitygrade-schoolyachtzebra-puzzlerational-numberspovsatelliteaffine-cipherbook-storecomplex-numberscircular-bufferdartsgo-countingtwo-bucketword-search@doc+@specordercheck_sourcecheck to check source code as a stringassert_callcomplex-numberssorting-room: Implement exercise to teach abouttype-conversionandtype-assertionSetsConcept Documentschaitanas-colossal-coasterclassesconcept exercise]: ellens-alien-gameMassive
{gh search prs --limit 200 --label 'x:size/massive' --json 'author,repository,title,url' --merged --jq '.[] | .repository.nameWithOwner + " | " + .title + " | " + .author.login + " | " + .url'; gh search prs --limit 200 --label 'x:rep/massive' --json 'author,repository,title,url' --merged --jq '.[] | .repository.nameWithOwner + " | " + .title + " | " + .author.login + " | " + .url' } | sort -t\| -k1 | awk 'BEGIN{print "repo | title | author | url"; print "-- | -- | -- | --"}1'elm-reviewnimscripter2.13and scalatest to version3.2.10The text was updated successfully, but these errors were encountered: