Re: [fw-general] Announcement: Monthly Bug Hunt Days
-- Ralf Eggert wrote (on Thursday, 24 September 2009, 08:05 PM +0200): > I know the last bug hunt days are finished but since there will be some > bug hunt days again next month, I just ask now. > > My question might be sound stupid but I was always asking myself this > question when looking at the issue tracker, When I look at the issue > tracker, almost each issue is assigned to someone. How do we know that > the assignee is not currently working on this issue when assigned to > him/her? As you found -- developers may mark the fix as "in progress". Just to be on the safe side, though, jump into #zftalk.dev and see if the contributor in question is available, and ask. That's how it worked during the bug hunt last week, and we had no issues with overlap. -- Matthew Weier O'Phinney Project Lead| matt...@zend.com Zend Framework | http://framework.zend.com/
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Ok, forgot it, found the "in progress" status. Thanks and best regards, Ralf
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Hi, I know the last bug hunt days are finished but since there will be some bug hunt days again next month, I just ask now. My question might be sound stupid but I was always asking myself this question when looking at the issue tracker, When I look at the issue tracker, almost each issue is assigned to someone. How do we know that the assignee is not currently working on this issue when assigned to him/her? Thanks and best regards, Ralf
Re: [fw-general] Announcement: Monthly Bug Hunt Days
-- lightflowmark <1...@lightflowinterrupted.com> wrote (on Thursday, 17 September 2009, 03:35 AM -0700): > Excellent news - it will be great to have some way of getting patches > integrated into trunk. > > Is there some other way of asking for patches to be reviews [at any time > during the month], or do we have to hop on IRC on the designated days? You can ping us on IRC anytime. I'm not often in #zftalk.dev, but my IRC nick -- weierophinney -- is registered, and you can always ping to see if I'm online (I'm on every week day). Ralph (ralphschindler) and Alex (CawaSPB) are typically around as well. You can also email to the zf-contribut...@lists.zend.com mailing list to try and get the attention of maintainers as well. > Matthew Weier O'Phinney-3 wrote: > > > > * If you do not have commit rights, create a patch with the unit test > >and fix, and attach the patch to the issue. Ask the maintainer or > >somebody from Zend to review and apply the patch. -- Matthew Weier O'Phinney Project Lead| matt...@zend.com Zend Framework | http://framework.zend.com/
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Just a reminder to list members that the Bug Hunt is starting today ;). If you don't have a lot of time I suggest adopting just 1-2 issues to help solve - every little bit helps! See details below from Matthew's original email. Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative From: Matthew Weier O'Phinney To: fw-general@lists.zend.com Sent: Monday, September 14, 2009 5:56:23 PM Subject: [fw-general] Announcement: Monthly Bug Hunt Days Greetings, one and all! I've alluded several times in the past month to having a plan for helping manage our ever-growing bug list in the issue tracker. We're now ready to roll out phase one of this plan, and we need *you*! Starting this month, we will be sponsoring two bug hunt days monthly, on the third Thursday and Friday of the month. That's this upcoming Thursday and Friday, 17-18 September 2009. During those days, the Zend team -- myself, Ralph, and Alex -- will be in #zftalk.dev on Freenode for our entire work day (Ralph and myself are in the United States, Alex is based in Russia; figure out the timezones yourself (-: ). We will be triaging bugs ourselves, but, more importantly, we will be there to help facilitate *you*, our contributors and users, in resolving issue reports. As an incentive, each month, we will ship a Zend Framework t-shirt to the individual that assists in the most issue resolutions during the bug hunt days, whether via patches or direct commits. Quarterly, we will evaluate overall contributions, including documentation, bug fixes, and newly contributed components, and award a developer with their choice of a Zend Studio license or Zend Framework Certification voucher. (Caveat: one t-shirt per person per year, and one license/voucher per person per year, folks!) For those interested in participating in the bug hunt days, the rules are simple: have a signed CLA on file, and resolve issues in the tracker. If you have not yet signed a CLA and want to participate, you can get a copy of the form here: http://framework.zend.com/cla Sign it and return it (you can email it, fax it, or send it via post); if you send it via post, you'll need to wait for confirmation that we've received it before we can accept code contributions from you. Now, when it comes to the issue tracker, you'll need to determine if the issue: * is simply the reporter misunderstanding or misusing code OR * is a request for a new feature OR * is a reproducible issue In the first case, comment on it and indicate the correct usage, and ask the component maintainer or somebody from Zend to review your response and mark the issue as resolved. In the second case, please try and focus on issue reports instead of feature requests during the bug hunt days. That brings us to the final case, reproducible issue reports. With these, you'll need to do the following: * Capture the reproduce case as a unit test * Resolve the issue in such a way as to maintain backwards compatibility with existing usage. (In other words, don't change the signature of a method unless the signature is what is actually broken.) From there, you then have two options: * If you already have commit access, commit the test and fix to the repository, and either resolve the issue or ask somebody from Zend to review and resolve. Don't forget to merge your changes to the 1.9 release branch! * If you do not have commit rights, create a patch with the unit test and fix, and attach the patch to the issue. Ask the maintainer or somebody from Zend to review and apply the patch. If you need help creating the unit test or patch file, hop onto the #zftalk.dev IRC channel and ask for help. How should you choose issues to work on? Answer the following questions, and you should be able to hop right in: * What components do you have expertise in? * What components are you interested in learning more about? * What issues have a high number of voters or watchers? Bug hunting should be fun, so pick components and issues you're interested in. Ask questions on IRC if you don't understand how something works. So, spread the word, and come prepared this week to help make the framework even better! I look forward to seeing you on IRC this week! -- Matthew Weier O'Phinney Project Lead| matt...@zend.com Zend Framework | http://framework.zend.com/
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Excellent news - it will be great to have some way of getting patches integrated into trunk. Is there some other way of asking for patches to be reviews [at any time during the month], or do we have to hop on IRC on the designated days? Matthew Weier O'Phinney-3 wrote: > > * If you do not have commit rights, create a patch with the unit test >and fix, and attach the patch to the issue. Ask the maintainer or >somebody from Zend to review and apply the patch. > -- View this message in context: http://www.nabble.com/Announcement%3A-Monthly-Bug-Hunt-Days-tp25439447p25488811.html Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Chris Murray wrote: > > Having already scanned to PDF the CLA for CYA, what's the email address to > send it to? > Hi Chris, Send your PDF to c...@zend.com -- when I did this (a couple months ago) it took about a week to get confirmation back. -Wil Moore III -- View this message in context: http://www.nabble.com/Announcement%3A-Monthly-Bug-Hunt-Days-tp25439447p25447499.html Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Announcement: Monthly Bug Hunt Days
Matthew Weier O'Phinney-3 wrote: > > Sign it and return it (you can email it, fax it, or send it via post); > Having already scanned to PDF the CLA for CYA, what's the email address to send it to? -- View this message in context: http://www.nabble.com/Announcement%3A-Monthly-Bug-Hunt-Days-tp25439447p25444861.html Sent from the Zend Framework mailing list archive at Nabble.com.
[fw-general] Announcement: Monthly Bug Hunt Days
Greetings, one and all! I've alluded several times in the past month to having a plan for helping manage our ever-growing bug list in the issue tracker. We're now ready to roll out phase one of this plan, and we need *you*! Starting this month, we will be sponsoring two bug hunt days monthly, on the third Thursday and Friday of the month. That's this upcoming Thursday and Friday, 17-18 September 2009. During those days, the Zend team -- myself, Ralph, and Alex -- will be in #zftalk.dev on Freenode for our entire work day (Ralph and myself are in the United States, Alex is based in Russia; figure out the timezones yourself (-: ). We will be triaging bugs ourselves, but, more importantly, we will be there to help facilitate *you*, our contributors and users, in resolving issue reports. As an incentive, each month, we will ship a Zend Framework t-shirt to the individual that assists in the most issue resolutions during the bug hunt days, whether via patches or direct commits. Quarterly, we will evaluate overall contributions, including documentation, bug fixes, and newly contributed components, and award a developer with their choice of a Zend Studio license or Zend Framework Certification voucher. (Caveat: one t-shirt per person per year, and one license/voucher per person per year, folks!) For those interested in participating in the bug hunt days, the rules are simple: have a signed CLA on file, and resolve issues in the tracker. If you have not yet signed a CLA and want to participate, you can get a copy of the form here: http://framework.zend.com/cla Sign it and return it (you can email it, fax it, or send it via post); if you send it via post, you'll need to wait for confirmation that we've received it before we can accept code contributions from you. Now, when it comes to the issue tracker, you'll need to determine if the issue: * is simply the reporter misunderstanding or misusing code OR * is a request for a new feature OR * is a reproducible issue In the first case, comment on it and indicate the correct usage, and ask the component maintainer or somebody from Zend to review your response and mark the issue as resolved. In the second case, please try and focus on issue reports instead of feature requests during the bug hunt days. That brings us to the final case, reproducible issue reports. With these, you'll need to do the following: * Capture the reproduce case as a unit test * Resolve the issue in such a way as to maintain backwards compatibility with existing usage. (In other words, don't change the signature of a method unless the signature is what is actually broken.) >From there, you then have two options: * If you already have commit access, commit the test and fix to the repository, and either resolve the issue or ask somebody from Zend to review and resolve. Don't forget to merge your changes to the 1.9 release branch! * If you do not have commit rights, create a patch with the unit test and fix, and attach the patch to the issue. Ask the maintainer or somebody from Zend to review and apply the patch. If you need help creating the unit test or patch file, hop onto the #zftalk.dev IRC channel and ask for help. How should you choose issues to work on? Answer the following questions, and you should be able to hop right in: * What components do you have expertise in? * What components are you interested in learning more about? * What issues have a high number of voters or watchers? Bug hunting should be fun, so pick components and issues you're interested in. Ask questions on IRC if you don't understand how something works. So, spread the word, and come prepared this week to help make the framework even better! I look forward to seeing you on IRC this week! -- Matthew Weier O'Phinney Project Lead| matt...@zend.com Zend Framework | http://framework.zend.com/
