Announcing June’s Zend Framework Bug Hunt Days

June 17, 2011

Events, News, Zend Framework

For those who haven’t put the reoccurring event in their calendar, this announcement is for you: the Zend Framework Monthly Bug-hunt is here again! Next Thursday, Friday and Saturday (the 23rd, 24th and 25th of June), we’ll be hosting our monthly bug hunt. For those of you unfamiliar with the event, each month, we organize the community to help reduce the number of open issues reported against the framework.

First, congratulations to Adam Lundrigan for closing the most issues in May’s bug-hunt. However, due to the stipulation that you can only win once in a calendar year, the winner of May’s bug-hunt goes to the runner-up, Rob Allen (aka Akrabat – Congratulations, and many thanks, Rob!.

As noted last month, we’ve made a change to JIRA to allow you to see and search on the number of attachments inside a particular issue. This should allow developers to easily identify which issues have had files attached to them, mostly in the form of unit tests and fix patches. See the screen shots below to undertand the feature:

Don’t know where to start? Have a look at our issue tracker, in particular the
filter linked below, which lists all unresolved isues. Many times, just the
simple act of triaging an issue will result in “Won’t Fix” or “Not an Issue”;
these are what we like to call the low-hanging fruit – both a great place to
start with as a first time bug hunter, but also a great place to rack up on
closed issues to help you put up some solid numbers. With so many open issues,
large and small, there is no reason to miss out on this bug-hunt.

Click here to search through our unresolved issues.

All in all, bug hunt days have helped us close more than a 1000 issues in Zend Framework since their inception. These bug hunts have proved vital to keeping up the bug squashing momentum in this project. So, whether they are big bugs or small bugs, remember this: all bugs are worthy of being squashed.

Not convinced you should join in yet? Here are some more reasons:

  • Improve your coding skillz by being around some of PHP’s top developers in #zftalk.dev while hunting for bugs.
  • Win THE Zend Framework t-shirt — the individual who resolves or assists in resolving the most issues wins a Zend Framework t-shirt! (This is the same t-shirt so many people were asking for at ZendCon 2010 worn by Matthew and Ralph during the ZF2 live talk.)
  • Help improve the overall quality of the code you’re already using.
  • Fix issues that have been affecting you.
  • Save you and your company time spent managing your own patches to ZF, and move the maintenance upstream by patching the framework itself.
  • Learn valuable Quality Assurance skills.
  • All the cool kids are doing it. Are you cool?

If you want to help out, please make sure you have a CLA on file with us, and then join us in the #zftalk.dev channel on Freenode on Thursday, Friday, & Saturday. If you would like more information on specifics of participating, read our guide.

We are looking forward to seeing you at this month’s Bug Hunt Days!

About Matthew Weier O'Phinney

Matthew is an open source software architect, specializing in PHP. He is currently project lead for Zend Framework, a project with which he has been involved since before the first public preview release. He is a Zend Certified Engineer, and a member of the Zend Education Advisory Board, the group responsible for authoring the Zend Certification Exam. He contributes to a number of open source projects, blogs on PHP-related topics, and presents talks and tutorials related to PHP development and the projects to which he contributes. You can read more of his thoughts on his blog, weierophinney.net/matthew/.

View all posts by Matthew Weier O'Phinney

2 Responses to “Announcing June’s Zend Framework Bug Hunt Days”

  1. weierophinney Says:

    GitHub’s issue tracking has nowhere near the capabilities we have in JIRA — we have many more capabilities for searching, linking to our repositories (SVN for ZF1, Git for ZF2), creation of components and assignment/ownership by component, milestones and packaging, etc.

    As a project, we’ve chosen to use the tools that best fit the project’s needs, and do not restrict ourselves only to those written in PHP if there are better solutions in other languages. (By your own admission, GitHub would be a bad solution as well, as it’s not written in PHP!)

  2. dreamer111 Says:

    I hope there will be a switch from JIRA to github. IMHO – a lot more friendlier and easier to work with system. Also – JIRA is written in java – this alone, once again this is my humble opinion – this alone should be the reason for it not to be used by a company that’s behind PHP.