Personnaly when I see a trivial bug that doesnt need too much work, I take myself to resolve it by commiting a fix and marking issue as resolved. When the bug is in need of more work (aka : tests writings), I contact Zend persons, usually Matthew or Darby, to talk about it quickly.
cheers, Julien.P 2008/3/24, James Dempster <[EMAIL PROTECTED]>: > > Seems very out of date. > > -- > /James > > On Mon, Mar 24, 2008 at 7:23 PM, Thomas Weidner <[EMAIL PROTECTED]> > wrote: > > > See here: > > http://framework.zend.com/wiki/pages/viewpage.action?pageId=11036 > > > > Greetings > > Thomas Weidner, I18N Team Leader > > http://www.thomasweidner.com > > > > ----- Original Message ----- > > From: "Rob Allen" <[EMAIL PROTECTED]> > > To: "Simone Carletti" <[EMAIL PROTECTED]> > > Cc: "Amr Mostafa" <[EMAIL PROTECTED]>; "Zend Framework General" > > <[email protected]> > > Sent: Monday, March 24, 2008 8:15 PM > > Subject: Re: [fw-general] Should I resolve issues on the tracker? (I'm > > not > > the component maintainer) > > > > > > > > > > On 23 Mar 2008, at 14:38, Simone Carletti wrote: > > > > > >> However, it's always recommended that you drop a line to current > > >> component mantainer to notify him about the changes, especially the > > >> first times you are contributing, thus he will be able to provide > > you > > >> some additional feedback. > > >> > > > > > > Is there a list of current component maintainers? > > > > > > Regards, > > > > > > Rob... > > > > >
