Weekly overview of the bug-hunting category- week 29, 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
• Weekly overview of the bug-hunting category- week 28, 2019

Bug hunting contributions summary

Week 29: July 11th - July 18th

• 18 Contributions, 14 scored higher than 0
• An average score of 66.89
• 9 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 27 we had last week to 18. That's approximately 33% drop in the number of submitted reports since last week. There were 4 reports that were not scored. The reasons were:

• The contributor in this case (1, 2) did not wait for the project owner's acknowledgement/ the documented issue could not be reproduced by the PO/reviewer.
• The issue reported was on a project still in its pre-alpha stage - (3)
• The last case (4), was not scored for being a duiplicate of an issue previously submitted by the same user.

That left us with 14 contributions eligible for rewards. This brought the average to 66.89, lesser than last week's average of 68.17. 7 of the rewarded reports were scored 70 or higher. The drop in the number of contributions can be attested to the recent drop in steem value

The week like the week before, had quality outputs. Much kudos to the contributors.

contributions

With 18 contributions this week, @friendsmobile retains the spot for contributor of the week. He had the most input of 6 reports . 5 of these were scored, 3 were scored 71.5 or higher. In total, he scored an average of 64.6. The remaining contributions were well distributed amongst the other hunters.

The project with the most contributions is the eSteem-mobile application

This app allows users access the steemit frontend from the comforts of their mobile devices. So a user can make blog posts, drop comments on a user's post, contribute and get rewarded.

You can look up the repo by following this link - https://github.com/esteemapp/esteem-mobile.

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/fossasia/open-event-organizer-android- Event management app for organizers using Open Event Platform. The core features of this Android Application are -

  • Scan a QR code
  • Check-in attendees
  • Overview of sales
  • Ticket Management
  • Data sync with the Open Event Organizer Server

You can also get more information fom the documentation

• https://github.com/TrafeX/clipboard.ninja-app - Clipboard.ninja is a quick and secure way to share text between devices.

  • It's realtime; you'll see the text immediately appear on the receiving device.
  • It's secure; the connection to the server is encrypted with SSL.
  • It's private; you first need to connect to the other device before you can send something, this way the data never has to be (temporarily) stored on the server.
  • You can connect with multiple devices, simultaneously receiving the text.
  • No registration is needed, a 6 digit number is enough to connect the devices.

You can also get more information fom 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:

https://docs.google.com/spreadsheets/d/1S7ayFTEy5CBMyeJvFRgq5JUjlqZxFjWAWhhrBL0GC60/edit#gid=1954068373

---

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

@fego