Weekly overview of the bug-hunting category- week 28, 2019
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.
Previous Reports
2018
- 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
- Weekly overview of the bug-hunting category- week 51, 2018
- Weekly overview of the bug-hunting category- week 52, 2018
- Weekly overview of the bug-hunting category- week 53, 2018
2019
- Weekly overview of the bug-hunting category- week 54, 2019
- Weekly overview of the bug-hunting category- week 55, 2019
- Weekly overview of the bug-hunting category- week 56, 2019
- Weekly overview of the bug-hunting category- week 57, 2019
- Weekly overview of the bug-hunting category- week 58, 2019
- Weekly overview of the bug-hunting category- week 60/61, 2019
- Weekly overview of the bug-hunting category- week 62, 2019
- Weekly overview of the bug-hunting category- week 63, 2019
- Weekly overview of the bug-hunting category- week 64, 2019
- Weekly overview of the bug-hunting category- week 65, 2019
- Weekly overview of the bug-hunting category- week 20, 2019
- Weekly overview of the bug-hunting category- week 21, 2019
- Weekly overview of the bug-hunting category- week 22, 2019
- Weekly overview of the bug-hunting category- week 23, 2019
- Weekly overview of the bug-hunting category- week 24, 2019
- Weekly overview of the bug-hunting category- week 25, 2019
- Weekly overview of the bug-hunting category- week 26, 2019
- Weekly overview of the bug-hunting category- week 27, 2019
Bug hunting contributions summary
Week 28: July 4th - July 11th
- 27 Contributions, 21 scored higher than 0
- An average score of 68.17 66.87
- 14 unique contributors
- No Staff Picks
- No new contributors
Number of reviewed and rewarded contributions
Average score
Reports Reviewed By Reviewer
This week the numbers dropped from the 33 we had last week to 27. That is 6 contributions short of what we had last week. There were 6 reports that were not scored. The reasons were:
- The contributor in this case (1, 2, 3) did not wait for the project owner's acknowledgement/ the documented issue could not be reproduced by the PO.
- The issue reported was cosmetic - (4)
- The other cases 5,6 were not scored because it was based on an older version of the and was already fixed in the latest version even before the hunter opened the ticket.
That left us with 22 contributions eligible for rewards. This brought the average to 68.17, greater than last week's average of 66.87. 11 of the rewarded reports were scored 75 or higher. We hope that this good run continues.
The week like the week before, had quality outputs. Much kudos to the contributors.
contributions
With 27 contributions this week, @friendsmobile grabs the spot for contributor of the week. He had the most input of 6 reports . 4 of these were scored, 3 were scored 72.5 or higher. In total, he scored an average of 66.86. The remaining contributions were well distributed amongst the other hunters.
The project with the most contributions is the Opus Music player
This is an application for playing music from local file storage or from youtube (while screen is off). You can as well edit metadata tag and manage playlist (local one or youtube one)
You can look up the repo by following this link - https://github.com/AnonymusRaccoon/Opus.
Other project repos that stood out
If you are looking for new applications to explore, here are some repos that stood out this week.
- https://github.com/quintuslabs/DatingApp- Dating UI kit is used for online meet up with girls and boys . The screen contains more than 30 icons and most of all required elements required to design an application like this. The XML and JAVA files contains comments at each and every point for easy understanding.
You can also get more information from the documentation
- https://github.com/SecUSo/privacy-friendly-food-tracker- Privacy Friendly Food Tracker allows you to track your daily calorie consumption.To do this, you can enter all your consumed food and drink as well as its weight. The app will then calculate total daily caloric consumption. The app also allows an analysis of calorie consumption over a larger timeframe such as weeks or months.
You can also get more information from the documentation
And there you have it. Happy hunting :D
Common Mistakes And How To Fix Them
I will be highlighting the common mistakes found this week. I will also be offering tips on how to avoid them in future contributions. The tips will depend solely on the scores received by the contributions in a particular week.
1. Contributions with a score below 40
The severity level of the bug was marked as negligible.
Submission of cosmetic or trivial UI issues (phone orientation, phone locking/unlocking etc.) that have a negligible effect on the functionality of the application may lead to a lower score of your contribution, thus reducing your chances of receiving a reward
If what you spotted is a discrepancy in the user interface or just the front end appearance of the software, then it is most probably a trivial bug and would be scored as such. So make sure to look out for this.
Also, there are times when a contribution is scored negligible because the expected behavior of a particular feature could still be achieved by a default option. For example - while some third party camera apps may not work when used for uploading within other applications (probably because the PATH for that particular cam app is not set), the default android cam works. It will be particularly stressful and redundant to have the project owner set a unique PATH for every cam application out there. This is one thing a contributor should look out for.
2. Contributions with a score below 60
The contributor made no efforts to pinpoint the cause, or applied incorrect methods in searching for it.
To avoid being scored in the questionnaire with this option, I will advise hunters to comb through the app's repo. Search the repo using a keyword related to the affected feature, it could be the name of the function itself. If found, analyze the block of code behind the function's implementation. Check for syntax and logical errors, document your findings.
You can attach logcats in your reports for issues that involve a crash. If you don't know to produce one, watch this tutorial for how to.
Other News
This is to inform contributors and the general public that while reports will be accepted to projects outside the whitelist, they will only be reviewed if the issue opened is acknowledged by the project owner or maintainer.
While the new guidelines are yet to be officially announced, 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
This is another clear weekly report from you. I appreciate your dedication in doing the reviews and providing the overviews. I even value the tips you always share for contributors to improve their work. All well done!
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? Chat with us on Discord.
[utopian-moderator]
Thank you for your review, @tykee! Keep up the good work!
Hi @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!