Time to fix errors in open-source projects, competition

The Pinguem.ru website and the PVS-Studio team are organizing a competition dedicated to improving the quality of open source software. To win the competition, it is necessary to correct as many errors in one or several open projects as possible. Errors must be detected using the PVS-Studio static code analyzer. Main prize: PlayStation 4 Pro console.

Contest rules on the site Pinguem.ru. Participate in the competition .

The competition consists of two stages. At the first stage, you should send as many pull requests as possible with error correction to the developers. The second stage is more complicated and requires not only correcting errors, but also describing the sequence of actions in which these errors manifest themselves in the program.

First stage:
')

1. Download and install PVS-Studio (in Windows or Linux).
   At the time of the competition, participants can use a special license key that allows using the analyzer without any restrictions:
   • Key for Windows version:
     Pinguem
     TX6G-3T8B-18P0-MK80
   • Key for Linux version:
     Pinguem
     TX6G-7T8B-18P0-MK82
     Creating a license file:
     pvs-studio-analyzer credentials Pinguem TX6G-7T8B-18P0-MK82
2. Select one or more open projects to work with. The analyzer is able to look for errors in projects written in C, C ++ and C #.
   Projects that have at least 10 stars on github.com are counted.
3. Check the code, find the error.
4. Send pull requests with bug fixes to the developers. In the description of each Pull Request, there must be a mention of Pinguem.ru and the PVS-Studio analyzer. For example, you can write the phrase:
   I’m a member of the open source projects. A bug found using PVS-Studio. Warning: warning _ that_ issued_analyzer_
5. Send links to all pull requests you made. To do this, use the form on the site Pinguem.ru: send a link to the pull request.

We also prepared a short video where we showed an example of participation in the competition. View the video .

Second phase:
It is necessary to describe the sequence of user actions in which the error found manifests itself. This is a difficult task, however, if a participant can describe the sequence of playing at least two errors, he will have a good chance of winning.