Re: [fw-general] Issue resolving procedure
Wil Sinclair wrote: Guilty as charged. We have been hogging all the work, and frankly we feel terrible about it. So, without further ado, Zend Framework's Most Wanted (issues). . . http://framework.zend.com/wiki/display/ZFDEV/Zend+Framework%27s+Most+Wanted At least now you can't say that we never give you what you want. ;) Well, this is useful. Thanks, Wil. Not exactly what I had in mind, but it's a start :) ,Wil -- 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
Re: [fw-general] Issue resolving procedure
Hy Michael, I can only speak as Team Lead. Generally when an issue is coming in, the team lead get's an announcement. He can then decide who get's the issue. If this is not done, then this issue leaves unassigned. Anyone who has SVN rights can assign an issue to himself and solve it. But generally he should also ask the related team lead or component owner. There is a page where this relation is included. If you have no SVN rights then you can assign the issue to yourself, make a patch, add this patch to the issue and make the issue unassigned again. The team lead or component developer will then look and integrate the patch if it has no further problems. Even if there is no component lead anymore (because he has left) there is always a team lead or zf-core member. But keep in mind: Solving an issue is not only coding... you must also create related unit tests and possibly adding some documentation. And for some components, like Zend_Db it's better only to add an patch, even if you have commit rights because they are very complicated, and change very often in SVN. You may also have mentioned that several issues can not solved by you because they are just tasks from the devteam related to wiki or jira. Also, if an issue is already assigned to an person, you should not reassign it to you... Greetings Thomas I18N Team Leader - Original Message - From: Michał Minicki [EMAIL PROTECTED] To: Zend Framework General fw-general@lists.zend.com Sent: Tuesday, January 15, 2008 12:51 PM Subject: [fw-general] Issue resolving procedure 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
Re: [fw-general] Issue resolving procedure
Hy Michal, I think there should be additional points in jira.. not only unassigned, won't fix, and so on but also someting like fix ready for review (if you made a fix so the lead or zdev can look into problems and the issue is not unassigned... so this issues will be integrated faster) and in discussion (for issues which could brake api, or make problems with other implementation details and have to be cleared before) Generally, if an issue is assigned to an person it will be fixed... The team lead has to get sure to reassign issues when a assigned person is not able to fix it for xxx days. But sometimes it is usefull... Myself for example has about 10 opened issues, but most of them are improvements and therefor not free because they change the api. But I am also not a normal contributor as team and component lead. :-) Greetings Thomas I18N Team Leader - Original Message - From: Michał Minicki [EMAIL PROTECTED] To: Thomas Weidner [EMAIL PROTECTED] Cc: Zend Framework General fw-general@lists.zend.com Sent: Tuesday, January 15, 2008 4:05 PM Subject: Re: [fw-general] Issue resolving procedure Hey. I'm actually an old-timer, so I know the basics, Thomas. I'm the original author of Rewrite Router and I have access to svn since 2006 (martel). So that's not an issue :) Basically what I'm asking is some way to be sure that unassigned issues (or issues assigned to team leaders) are scheduled to be implemented. That way I can pick one or the other up and make the changes without worrying if I'm doing something that Zend people disapprove (or approve). You should be well aware that not every issue is going to be implemented. From time to time I have some free resources and can help squashing bugs or making small improvements even outside my field (read MVC). But I'm afraid to touch these issues simply because I'm worried I'll do something that in fact shouldn't be done. It would be great if someone from Zend would simply leave a comment on every issue that is going to be implemented. Or maybe there is a better way? Like setting a special status on issues? You know, something like: Open = Approved = Fixed / Won't Fix / Etc With Approved being a step that's missing at the moment :) Thomas Weidner wrote: Hy Michael, I can only speak as Team Lead. Generally when an issue is coming in, the team lead get's an announcement. He can then decide who get's the issue. If this is not done, then this issue leaves unassigned. Anyone who has SVN rights can assign an issue to himself and solve it. But generally he should also ask the related team lead or component owner. There is a page where this relation is included. If you have no SVN rights then you can assign the issue to yourself, make a patch, add this patch to the issue and make the issue unassigned again. The team lead or component developer will then look and integrate the patch if it has no further problems. Even if there is no component lead anymore (because he has left) there is always a team lead or zf-core member. But keep in mind: Solving an issue is not only coding... you must also create related unit tests and possibly adding some documentation. And for some components, like Zend_Db it's better only to add an patch, even if you have commit rights because they are very complicated, and change very often in SVN. You may also have mentioned that several issues can not solved by you because they are just tasks from the devteam related to wiki or jira. Also, if an issue is already assigned to an person, you should not reassign it to you... Greetings Thomas I18N Team Leader - Original Message - From: Michał Minicki [EMAIL PROTECTED] To: Zend Framework General fw-general@lists.zend.com Sent: Tuesday, January 15, 2008 12:51 PM Subject: [fw-general] Issue resolving procedure 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
RE: [fw-general] Issue resolving procedure
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
RE: [fw-general] Issue resolving procedure
Guilty as charged. We have been hogging all the work, and frankly we feel terrible about it. So, without further ado, Zend Framework's Most Wanted (issues). . . http://framework.zend.com/wiki/display/ZFDEV/Zend+Framework%27s+Most+Wanted At least now you can't say that we never give you what you want. ;) ,Wil -Original Message- From: Steven Brown [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 3:21 PM To: 'Zend Framework General' Subject: RE: [fw-general] Issue resolving procedure 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
