Weekly overview of the bug-hunting category- week 51, 2018
This is a report on the weekly contributions to the bug hunting category. The post contains basic stats like the number of contributions received by the category, an excerpt on new contributors if there are any and a detailed comparison of the week's output with previous weeks.
.jpg)
Previous Reports
- Weekly overview of the bug-hunting category- week 44, 2018
- Weekly overview of the bug-hunting category- week 45, 2018
- Weekly overview of the bug-hunting category- week 46, 2018
- Weekly overview of the bug-hunting category- week 47, 2018
- Weekly overview of the bug-hunting category- week 48, 2018
- Weekly overview of the bug-hunting category- week 49, 2018
- Weekly overview of the bug-hunting category- week 50, 2018
Bug hunting contributions summary
- Week 51: December 13th - December 20th
- 5 Contribution, 5 scored
- An average score of 62.5
- 4 unique contributors
- 1 new contributor, @anthonyadavisii
At the time of writing this report the bug received have been fixed by the PO.
The contribution
| Contributor | URL | Project | Score |
|---|---|---|---|
| @tdre | FreeCodeCamp ― Test Does Not Recognize Correct Solution | freecodecamp | 0 |
| @blockchainstudio | Steem Python library sbd_to_rshares bugfix | steem-python | 0 |
| @tdre | Utopian Reviews ― Links to Older Questionnaire Results Are Broken | 1ramp | 77 |
| @mightypanda | [1Rramp-Android] [1.0] Tags are not saving in a draft | 1ramp | 48 |
| @anthonyadavisii | Steemit.com Followers / Following Count Discrepancy | steemit/condenser | 0 |
In summary, the contributions were more than last week. Last week, we had just 1 bug report and this week we have 5. Although, out of the 5 that were received this week, only 2 were scored higher than 0.
@tdre's report on how freecodecamp rejects a clearly expected answer and does not credit the user for a correct response was scored zero because the project repo is not included in the bug-hunting whitelist. The moderator explained the reason in his review:
Although your contribution is well explained and goes into a good amount of detail, unfortunately, this contribution is not suitable for scoring due to the project not being listed on the Utopian Bug Hunting whitelist.
@blockchainstudio's report was scored zero for the same reason as tdre's while @anthonyadavisii's was because his bug report was a duplicate of an existing issue.
Weekly Average Score and number of Contributions
We can see that the average score of 62.5 is approximately 5% higher than the 10 week average of 59.45. This week's average is 3.05 higher than the 10-week average and 11.5 lower than last week's.
Hunter Totals and Average
.
This week we had a new contributor, @anthonyadavisii.
@mightypanda joins @tobias-g as joint top contributor with 4 finds. Tobias after 10 weeks still has the highest average of 83.25.
6 contributors have an average reward score of 59.45 or above, over the past 10 weeks.
Reports Reviewed By Reviewer
The 25 contributions received by the category in the past 10 weeks were assessed by 4 reviewers. Of the 25 contributions, 19 were rewarded and scored higher than 0.
- @sachincool have now reviewed 2 contributions (40, 40) with an average score of 40.
- @fego have reviewed 16 contributions (45.5, 72.5, 44.5, 80, 35.5, 80, 55, 75, 85, 85, 78, 77, 48) with an average score of 66.23.
- @tobias-g have reviewed 6 contributions (37.5, 65, 70) with an average score of 57.5.
- @crokkon have reviewed 1 contribution, with an average score of 70.
Other items
In other news, the category is looking forward to implementing new guidelines to replace the existing whitelist that will let contributors submit bug reports to projects outside the steem and the whitelist.
While the new guidelines are yet to be implemented, bug-hunters and open source enthusiasts looking to help open source projects, please take a look at our whitelist of projects that you can submit bug reports for:
If you wish to have your open source projects added to our whitelist you can contact us on our help channel at our discord server. You can also leave your questions and comments below :)
Thanks
Hello @fego,
Thank you for providing the Bug hunting weekly overview. The report is well written and informative. It was pleasant reading through.
It appears there were few quality contributions to the category this week, considering 5 reports and 3 received 0 scores. However, the sum is quite better than the previous week.
I got a misconception about this part in this overview. You stated
At the time of writing this report the bug received have been fixed by the PO.I don't understand the ''bug'' you were referring to. anthonyadavisii bug report?Please note that while the CM hasn't changed the footer, I am not scoring #iamutopian posts based on the questionnaire. They have their own metric, and that will be the case until we go live with the new guidelines and new questionnaire, which will be comprehensive enough to reflect these types of posts.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Thank you for your review, @tykee! Keep up the good work!
Yep, was pretty disappointed after the second bug report I submitted goes unvoted. My last was a Beem Python issue related to Hard Fork 20 but, coincidentally, because of the voting power reset with HF20 I didn't get a vote even though it was a good report.
This time the problem was I searched for "follower" when I checked for existing issues prior to drafting a report. It was after that I saw Pjau submitting for following. I actually added some testing and additional details so sucks to get a goose egg. Meh, live and learn I guess.
I will advise that the bug hunting category be amended to make it clear that reports on similar issues will not be scored.
Posted using Partiko Android
Tough luck, deeply sorry about that.
The main reason behind making a bug post is to bring to the attention of the PO or willing contributors, the presence of the bug. This is why we ask that contributors first check the github issue tracker for duplicates before opening a new issue and also before posting to utopian. The report is of no use to the PO if s/he is already aware of the bug from a much earlier ticket.
I believe the new updates to the guideline would curb issues like this. I looked at the report you submitted, it was well detailed and exactly what is expected of a bug post.
Do not be deterred by this, we look forward to seeing more of your posts, and hopefully scoring them :)
Congratulations! Your post has been selected as a daily Steemit truffle! It is listed on rank 25 of all contributions awarded today. You can find the TOP DAILY TRUFFLE PICKS HERE.
I upvoted your contribution because to my mind your post is at least 10 SBD worth and should receive 120 votes. It's now up to the lovely Steemit community to make this come true.
I am
TrufflePig, an Artificial Intelligence Bot that helps minnows and content curators using Machine Learning. If you are curious how I select content, you can find an explanation here!Have a nice day and sincerely yours,
TrufflePigHi @fego!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @fego!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
Congratulations @fego! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :
Click here to view your Board
If you no longer want to receive notifications, reply to this comment with the word
STOPDo not miss the last post from @steemitboard: