From Fedora Project Wiki


Your name: Tomas Meszaros
FAS Account: Exo
Telephone: +421 902 113313
Fedora userpage:


I believe that working on this project would have real practical impact and what is more, I'll keep improving my skills and gain experience. 
I'm into open-source for several years and it's my hobby. I've worked on my own projects but I'm also maintaining packages. I'm author of fedora-gooey-karma, a GUI tool for Fedora testers.
Most of the project I've worked on are written in Python or C and all of my projects can be found under the open-source licenses at my GitHub page:

Project Description

Summary of idea: The [web application] is used by QA to track bugs which are currently blocking release, proposed as blocking release or could be pulled into the release past a code freeze. While the app itself already exists, there are many features which we would like to see implemented including (but not limited to):

  • Creating a RESTful API
  • Tracking contents of TC/RC spins
  • migrating css to zurb foundation 4
  • search functionality
  • improve the update sync process
  • implement CI tools (make-ish file that runs pylint, tests etc.)
  • integrate email (on error, on proposal, other thoughts ...)
  • integrate fedbus (blocker X proposed, accepted, rejected)
  • fix the admin interface so that it actually works

Knowledge prerequisite: Some python experience is required, the app is written with Flask so some experience with that would be helpful

Skill level: Intermediate

Contacts: Tim Flink (tflink)

Mentor(s): Tim Flink (tflink)

Implementation & Rough Timeline

I will try to implement as many features proposed by Tim Flink as possible.

It is kinda hard to exactly plan this project because a lot of may change in the phase of development, therefore I am only posting this rough timeline.

Upto June 17: Get familiar with blockerbugs code and workflow
Week 1-2: Implement search functionality
Week 3: Test implemented functionality and fix bugs
Week 4-5: Integrate email
Week 6: Test implemented functionality and fix bugs
Week 7: Code cleanup and documentation
Week 8-9: Integrate fedbus
Week 10: Improve the update sync process
Week 11: Get feedback and implement other functionality based on the feedback
Week 12: Final test and fix bugs
Week 13: Final code cleanup and documentation

Why do you want to work with the Fedora Project?

          I want to use and improve my skills while giving back to the Fedora community.

Do you have any past involvement with the Fedora project or any other open source project as a contributor?

          Yes, I'm author of the fedora-gooey-karma. I'm also maintaining packages (ArchLinux - AUR). All my open-source projects can be found at my GitHub:

Did you participate with the past GSoC programs, if so which years, which organizations?

          No, I didn't participate with the past GSoC programs. This is my first GSoC project.

Will you continue contributing/ supporting the Fedora project after the GSoC 2013 program, if yes, which team(s), you are interested with?

          I'm planning to maintain project and also contribute to the Fedora after the GSoC 2013. I like to work within Fedora QA team.

Why should we choose you over other applicants?

          Open-source is my passion and hobby. I like to spend my time working on interesting projects, while having fun and learning new things.