This past Thursday and Friday, 15-16 October 2009, Zend Framework held its
second monthly bug hunt. Activity started out slow, but picked up
tremendously on Friday, resulting in initially 100 bugs resolved, though a
few have been re-opened in the days since. The
list is available on our issue tracker. Thank you, everyone, for the
participation, and for keeping this initiative alive and vibrant!
The top three community bug hunters this month were:
- Michael DePetrillo – 14 issues resolved
- Dolf Schimmel – 12 issues resolved
- Robin Skoglund – 11 issues resolved
I would particularly like to call out Michael’s contributions. Michael
submitted his first patches during the bug hunt, and, based on the quality
of those patches, we gave him SVN access. The lesson to learn here: you need
not be a ZF veteran contributor to participate and potentially compete in
the bug hunt! If you haven’t participated before, the monthly bug hunt is a
great time to learn the ropes and get some mentoring — so please join us
when you can!
Next month’s bug hunt will be 19-20 November 2009. Get your
participate, and help us improve the framework!
October 21, 2009 at 8:21 pm
Well.. less bugs is always good news. But why do some bug have to wait a "bug hunt" while the fix is trivial and has been submitted 7 months ago ? —> http://framework.zend.com/issues/browse/ZF-5916
Nice to see this fixed anyway.
October 21, 2009 at 10:24 pm
People continually overestimate the availability of developer time to fix trivial and long standing bugs, especially in the lesser used components, or components without a current lead developer. I’ve said it before – if the fix is so trivial, and someone is interested in seeing it solved, why not take the time to add a patch or contact a developer to peer review it or give you SVN access to commit it?
The Zend Framework is an open source project – if someone leaves everything up to Zend and disavows all responsibility, then they have really misunderstood the concept of open source. The Bug Hunts have started to illustrate what a concerted effort by a few developers can accomplish – hopefully it encourages more people to get involved. If everyone fixed one bug apiece per month, there would be zero issues open pretty fast
.
October 22, 2009 at 5:46 am
Great to see another 100 bugs fixed! Good job everyone and thanks for putting in the time and effort.
Regards, TJ.
October 22, 2009 at 9:00 am
"DON’T BLAME US, BLAME YOURSELF
"
"why not take the time to add a patch or contact a developer"
Allright… I knew this was coming.
Then I assume that for you taking time to report a bug doesn’t count as taking time to contact a developer (if none’s reading bug reports then what’s the point?) and uploading the corrected file doesn’t count as a patch as well (well, sure it’s not that lovely diff but come on…)
So please, tell me what’s the proper way to report a bug ? Should I call a dev on the phone to say that I sent a fax to say that I sent a mail to say that I filled a bug report _with fix included_ ?
As to submit code via svn, here’s what I found on framework.zend.com:
# Anyone wishing to contribute code, patches, and proposals to Zend Framework must complete two steps before anything is submitted:
#
# 1. Read and understand the New BSD License, which is how all parts of Zend Framework (including all contributions to it) are licensed.
# 2. Submit a signed CLA by either submitting an Individual CLA if you are submitting code as an individual or a Corporate CLA for anyone who is submitting code as an employee of a company.
#
#To submit a CLA, download and print one of the agreements above. Fill it out completely making sure to:
#
# * Print clearly using large letters
# * Include your name and email address
# * Include your Issue Tracker username (Don’t have an Issue Tracker account? Get one here!)
# * If we place your Issue Tracker username into the "developer group" within the Issue Tracker, other contributors will know that you signed the CLA, and that your submitted code and patches may be used. Unless we receive instructions from you for a confidential CLA, expect to have your Issue Tracker account placed into the "developer group". In some rare instances, a corporation might wish to make a confidential code contribution.
# * Sign and date the CLA.
#
#When completed you may submit the CLA in one of three ways:
#
# 1. Electronically: Email a 1500+ pixel wide JPEG/PNG copy of the CLA to cla@zend.com, or
# 2. Send a fax of the CLA to: +1-408-253-8801 (if a scan is not possible) and send an email to cla@zend.com, or
# 3. Send a signed version of the CLA via postal mail to:
# Zend Technologies, Inc.
# ATTN: Zend Framework CLA Agreements
# 19200 Stevens Creek Blvd.
# Suite 100
# Cupertino, CA 95014 USA
# and send an email to cla@zend.com
#
#When we receive a CLA we usually respond within 5 business days. You will receive a confirmation of your CLA to the email address listed on the CLA. If you have not received confirmation of receipt within a reasonable period of time contact cla@zend.com and we will try to resolve the issue.
Are you serious ?
Also I don’t blame you, I just ask a simple question, for which I found a response in your comment: not all components are equal in ZF in regards of quality assurance.
That’s fine, but much better when explicitely said.