I totally agree with this, I have been prepared to get in and help but how do I know what I can do without interfering with others, and how do I join a team etc. It's not entirely clear within the issue tracker.
-----Original Message----- From: Michał Minicki [mailto:[EMAIL PROTECTED] Sent: Tuesday, 15 January 2008 9:51 PM To: Zend Framework General Subject: [fw-general] Issue resolving procedure Importance: High Hello. I have a question or an idea for improvement when it comes to issue resolving procedures. There are a lot of open issues in the issue tracker and I bet there are a lot of ZF devs who, like me, don't know whether they can fix the user submitted issue or not. It's all open source, alright, but you, at Zend, certainly have a vision and some standards you try to keep to. So having that in mind, instead of fixing bugs I'm hesitating over issues all the time and skipping them if I have any doubts. And I'm pretty sure I'm not alone on this :) Is there some kind of a process in choosing which issues are going to be fixed or implemented? I mean, is there someone who scans the issues daily and marks them as "won't be done" or "to be done"? If not, maybe it would be a good idea to somehow mark the issues for all your devoted developers. Or maybe there already is some way to make sure that we can take this or that issue on ourselves? -- Michał Minicki aka Martel Valgoerad | [EMAIL PROTECTED] | http://aie.pl/martel.asc =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Idleness is not doing nothing. Idleness is being free to do anything." -- Floyd Dell
