Interview with Oleg Krylov, who fixed the famous bug with hot keys in the Fire Fox
Let me remind you, Oleg Krylov is the author of the first fix for a bug in Mozilla products as part of the Money for Bug Fixes program. After paying the reward, Oleg kindly agreed to answer some of our questions.
Oleg, tell us a little about yourself, about what you do.
I am 25 years old, born and raised in Riga (Latvia). I graduated in Telecommunications, I also work in
specialties - software engineer of automation systems for broadcasting and telephony.
You have previously participated in any open source projects, if so, which ones?
Directly no. There are several accepted patches for the wine project. In my free time I’m picking up Gnome / Mozilla / wine a little bit, as time will let me send patches, it’s the process of taking code to the main branch that takes the most time and requires constant attention.
Oh, I completely forgot, I once had my own open projects related to 3D games, such as the Win32 port of the old game that was once familiar to many Win32 ;
How did you find out about the "Money for bug fixes" program?
On linux.org.ru I visit it daily.
')
How long did it take to develop and test a patch?
Net development time is difficult to calculate. I first became interested in this problem about a year ago, after about
as I crawled at work on Linux, I began to look at how to fix something that does not suit me in the system (a big plus to Open Source). Then, when I found out about the program, I dug up my changes and brought them to an acceptable form, correcting the comments of the project members - it took about a month.
What tools were used while writing the patch?
The compiler is of course gcc, the C / C ++ language, of course, this is dictated by the project. IDE - Eclipse, for simple and quick editing gedit. Also used is Firefox for working with Bugzilla and GMail, reading GTK dev.manual
Did you communicate with Mozilla developers, and if so, how?
With the help of Bugzilla, I also read mailing-lists for some time in order to understand the spirit of the project and know the main directions of current work.
What would you like to say / advise other programmers who are going to join in fixing other bugs?
It is better to work more with the code, use the assembled version of the program (with your changes) on a daily basis. When sending a patch, listen to the comments of members of the project, the people who are doing your patch-review, it’s their code to them to support it, they know it better than you, if it’s not so, why are you still not working in Mozilla?
Interview and discussion on mozilla-russia.org
Interviewer - ragnaar
Links about the hotkey bug:
Oleg, tell us a little about yourself, about what you do.
I am 25 years old, born and raised in Riga (Latvia). I graduated in Telecommunications, I also work in
specialties - software engineer of automation systems for broadcasting and telephony.
You have previously participated in any open source projects, if so, which ones?
Directly no. There are several accepted patches for the wine project. In my free time I’m picking up Gnome / Mozilla / wine a little bit, as time will let me send patches, it’s the process of taking code to the main branch that takes the most time and requires constant attention.
Oh, I completely forgot, I once had my own open projects related to 3D games, such as the Win32 port of the old game that was once familiar to many Win32 ;
How did you find out about the "Money for bug fixes" program?
On linux.org.ru I visit it daily.
')
How long did it take to develop and test a patch?
Net development time is difficult to calculate. I first became interested in this problem about a year ago, after about
as I crawled at work on Linux, I began to look at how to fix something that does not suit me in the system (a big plus to Open Source). Then, when I found out about the program, I dug up my changes and brought them to an acceptable form, correcting the comments of the project members - it took about a month.
What tools were used while writing the patch?
The compiler is of course gcc, the C / C ++ language, of course, this is dictated by the project. IDE - Eclipse, for simple and quick editing gedit. Also used is Firefox for working with Bugzilla and GMail, reading GTK dev.manual
Did you communicate with Mozilla developers, and if so, how?
With the help of Bugzilla, I also read mailing-lists for some time in order to understand the spirit of the project and know the main directions of current work.
What would you like to say / advise other programmers who are going to join in fixing other bugs?
It is better to work more with the code, use the assembled version of the program (with your changes) on a daily basis. When sending a patch, listen to the comments of members of the project, the people who are doing your patch-review, it’s their code to them to support it, they know it better than you, if it’s not so, why are you still not working in Mozilla?
Interview and discussion on mozilla-russia.org
Interviewer - ragnaar
Links about the hotkey bug:
- Legendary bugzilla bug (with discussion and technical details)
- Discussion on the forum Mozilla Russia
- Champagne splashes on the ENT on the release of the patch
Source: https://habr.com/ru/post/17339/
All Articles