OpenWISP

[hard] Help us to fix or close an issue from our contributor's board

Important: you must have completed at least 15 tasks with OpenWISP before attempting this task. This task is not easy, Read the description carefully and claim only once you have fully understood the purpose of the task. Not following these instructions will result in mentors unassigning students from this task.

We have many issues in our contributor's board which were not put up as a GCI tasks for different reasons:

  • the issues were judged to be too hard for GCI students
  • we are not sure if the issue is really a bug, because we haven't been able to replicate it
  • maybe we simply forgot

The goal of this task is to help us to solve one of the issues which are not already reserved as GCI tasks.

  • look at the board for tasks that are not reserved for GCI
  • read the text of issues until you find something you think you can help us to solve
  • check if any other GCI student or contributor is working on that issue, if none has been working actively on it in the previous 7 days, you can claim it and propose a solution

Solving it mean one or more of the following:

  • replicate the bug, write an automated test that replicates it in the test env, fix the bug
  • demonstrate without any reasonable doubt that it was not a bug and hence it can be closed
  • if there's any documentation page to improve because the text not being clear is leading users into thinking there's a bug, help us make the docs clearer

Keep in mind this is one of the hardest tasks available! Good luck!

Task tags

  • python
  • qa
  • javascript
  • django

Students who completed this task

Karol, Reza Juliandri, mrcreator

Task type

  • code Code
  • chrome_reader_mode Documentation / Training
  • assessment Outreach / Research
  • done_all Quality Assurance
close

2018