Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
+1 At 04:06 AM 2/8/2002, Jani Taskinen wrote: Just wanted to let you know that I'm doing exactly that. Filtering that annoying noise to other folder. :) Which I unfortunately don't have time to read atm. And I actually have turned my coat on this issue and I'm in favor for separating the bug emails to own list. Two good reasons: - People who don't want to read them filter them out anyway - It makes php-dev easier to follow - The php-dev@ archive (e.g. in web) becomes easier to browse and search for discussions The php-bugs@ list should be a read-only list where anyone with cvs account should be subscribed (by default). It being read-only forces any replies to be send to php-dev@ where more intense discussion over the issues in the reports should take place anyway. --Jani On Thu, 7 Feb 2002, l0t3k wrote: Daniel, we've had that conversation before, and the consensus then (which makes sense), is that part of the price of being a developer is ensuring that bugs are resolved in a timely manner. to split the list would make it less likely that a bug gets reviewed (after all its more sexy to create features than to debug them). how that works in actual practice, i dont know. i review bug reports periodically, but i suppose others can just as well filter them out... Daniel Lorch [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hi, Maybe a solution would be to split PHP-Dev into PHP-Bugs and keep PHP-Dev for *real* topics such as case sensitivity/PHP5 and other questions which are about PHP language design. This would keep the noise out of here. Comments? -- Daniel Lorch -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
-1 :) For the reasons mentioned every six months when this matter is raised. At 02:49 PM 2/8/2002 +0200, Zeev Suraski wrote: +1 At 04:06 AM 2/8/2002, Jani Taskinen wrote: Just wanted to let you know that I'm doing exactly that. Filtering that annoying noise to other folder. :) Which I unfortunately don't have time to read atm. And I actually have turned my coat on this issue and I'm in favor for separating the bug emails to own list. Two good reasons: - People who don't want to read them filter them out anyway - It makes php-dev easier to follow - The php-dev@ archive (e.g. in web) becomes easier to browse and search for discussions The php-bugs@ list should be a read-only list where anyone with cvs account should be subscribed (by default). It being read-only forces any replies to be send to php-dev@ where more intense discussion over the issues in the reports should take place anyway. --Jani On Thu, 7 Feb 2002, l0t3k wrote: Daniel, we've had that conversation before, and the consensus then (which makes sense), is that part of the price of being a developer is ensuring that bugs are resolved in a timely manner. to split the list would make it less likely that a bug gets reviewed (after all its more sexy to create features than to debug them). how that works in actual practice, i dont know. i review bug reports periodically, but i suppose others can just as well filter them out... Daniel Lorch [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hi, Maybe a solution would be to split PHP-Dev into PHP-Bugs and keep PHP-Dev for *real* topics such as case sensitivity/PHP5 and other questions which are about PHP language design. This would keep the noise out of here. Comments? -- Daniel Lorch -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]:[PHP-DEV] Suggestion:
Do you filter these? :) I didn't do that before, but now that I am doing it, it makes following php-dev@ a LOT easier. --Jani On Fri, 8 Feb 2002, Andi Gutmans wrote: -1 :) For the reasons mentioned every six months when this matter is raised. At 02:49 PM 2/8/2002 +0200, Zeev Suraski wrote: +1 At 04:06 AM 2/8/2002, Jani Taskinen wrote: Just wanted to let you know that I'm doing exactly that. Filtering that annoying noise to other folder. :) Which I unfortunately don't have time to read atm. And I actually have turned my coat on this issue and I'm in favor for separating the bug emails to own list. Two good reasons: - People who don't want to read them filter them out anyway - It makes php-dev easier to follow - The php-dev@ archive (e.g. in web) becomes easier to browse and search for discussions The php-bugs@ list should be a read-only list where anyone with cvs account should be subscribed (by default). It being read-only forces any replies to be send to php-dev@ where more intense discussion over the issues in the reports should take place anyway. --Jani On Thu, 7 Feb 2002, l0t3k wrote: Daniel, we've had that conversation before, and the consensus then (which makes sense), is that part of the price of being a developer is ensuring that bugs are resolved in a timely manner. to split the list would make it less likely that a bug gets reviewed (after all its more sexy to create features than to debug them). how that works in actual practice, i dont know. i review bug reports periodically, but i suppose others can just as well filter them out... Daniel Lorch [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hi, Maybe a solution would be to split PHP-Dev into PHP-Bugs and keep PHP-Dev for *real* topics such as case sensitivity/PHP5 and other questions which are about PHP language design. This would keep the noise out of here. Comments? -- Daniel Lorch -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
At 03:04 PM 2/8/2002 +0200, Jani Taskinen wrote: Do you filter these? :) I didn't do that before, but now that I am doing it, it makes following php-dev@ a LOT easier. I do :) But I still think that people subscribed to php-dev@ need to not only enjoy upsides but also the downsides of receiving the bug reports in hope that more people will look at them. By the way, if you're filtering them then what do you care? It's no biggy to deal with another n mails if they are filtered. Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
At 03:13 PM 2/8/2002, Andi Gutmans wrote: At 03:04 PM 2/8/2002 +0200, Jani Taskinen wrote: Do you filter these? :) I didn't do that before, but now that I am doing it, it makes following php-dev@ a LOT easier. I do :) But I still think that people subscribed to php-dev@ need to not only enjoy upsides but also the downsides of receiving the bug reports in hope that more people will look at them. I think that the only time this actually has any meaning is with people whose email software isn't bright enough to filter it. Otherwise, I'm pretty sure everyone filters it anyway. php-dev is full of people who aren't actually developing, but are just interested in watching the development trends. Forcing them to see the bugs isn't going to do anything in any level - either they'll ignore it, or filter it out, because they can't do anything about it anyway. We both know that just receiving the bug reports doesn't have any meaning if you're not willing to actually spend time working on them. I don't think it's that important (that's my last post on this thread :), but it does look kind of odd that instead of just separating the lists, we tell people 'filter them!' Zeev -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
At 03:15 PM 2/8/2002 +0200, Zeev Suraski wrote: At 03:13 PM 2/8/2002, Andi Gutmans wrote: At 03:04 PM 2/8/2002 +0200, Jani Taskinen wrote: Do you filter these? :) I didn't do that before, but now that I am doing it, it makes following php-dev@ a LOT easier. I do :) But I still think that people subscribed to php-dev@ need to not only enjoy upsides but also the downsides of receiving the bug reports in hope that more people will look at them. I think that the only time this actually has any meaning is with people whose email software isn't bright enough to filter it. Otherwise, I'm pretty sure everyone filters it anyway. php-dev is full of people who aren't actually developing, but are just interested in watching the development trends. Forcing them to see the bugs isn't going to do anything in any level - either they'll ignore it, or filter it out, because they can't do anything about it anyway. We both know that just receiving the bug reports doesn't have any meaning if you're not willing to actually spend time working on them. I don't think it's that important (that's my last post on this thread :), but it does look kind of odd that instead of just separating the lists, we tell people 'filter them!' I believe that in the scenario where php-dev@ is sent bug reports as opposed to people having to subscribe separately to php-bugs@ the amount of people reading bug reports in the first case will be bigger than in the second. This is because I believe there is a % of people who would read bug reports if they received them but wouldn't actively subscribe to the bug reports list. Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]:[PHP-DEV] Suggestion:
Exactly same for me. I should have started doing this a long time ago.. --Jani On Fri, 8 Feb 2002, Edin Kadribasic wrote: Do you filter these? :) I didn't do that before, but now that I am doing it, it makes following php-dev@ a LOT easier. I filter bug reports to a separate folder as well. (cyrus + sieve rocks). I noticed an interesting thing. Not only did reading php-dev become much easier, but reading my virtual php-bug list is very nice as well. It is possible to quickly scan the reports for the your area of interest (and hope that's not session module :). So +1 from me. Edin -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]:[PHP-DEV] Suggestion:
On Fri, 8 Feb 2002, Andi Gutmans wrote: I believe that in the scenario where php-dev@ is sent bug reports as opposed to people having to subscribe separately to php-bugs@ the amount of people reading bug reports in the first case will be bigger than in the second. This is because I believe there is a % of people who would read bug reports if they received them but wouldn't actively subscribe to the bug reports list. Don't forget the archives. Now searching php-dev@ archive (in the web) for some discussions is pretty hard since most of it is bug reports. --Jani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
Someone suggested having php-bugs set up, and anyone with the relevant karma would automatically be on it. if it was closed subscribtion/unsubscription, then when someone gives karma, they also subscribe the person to that list. Perhaps that's a solution, to seperate it. Yes, filters are good, we all use them... but it's the other places which that doesn't help, like the online archives. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
At 02:16 PM 2/8/2002 +, James Cox wrote: Someone suggested having php-bugs set up, and anyone with the relevant karma would automatically be on it. if it was closed subscribtion/unsubscription, then when someone gives karma, they also subscribe the person to that list. Perhaps that's a solution, to seperate it. Yes, filters are good, we all use them... but it's the other places which that doesn't help, like the online archives. This is a good suggestion. Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
Yeah, this was on my original email too.. :) (being mandatory for anyone with cvs access..and the archive thing) --Jani On Fri, 8 Feb 2002, Andi Gutmans wrote: At 02:16 PM 2/8/2002 +, James Cox wrote: Someone suggested having php-bugs set up, and anyone with the relevant karma would automatically be on it. if it was closed subscribtion/unsubscription, then when someone gives karma, they also subscribe the person to that list. Perhaps that's a solution, to seperate it. Yes, filters are good, we all use them... but it's the other places which that doesn't help, like the online archives. This is a good suggestion. Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Separating Bug report emails to own list.. Re: Re[3]:[PHP-DEV] Suggestion:
Hallo, On Fri, 8 Feb 2002, Jani Taskinen wrote: And I actually have turned my coat on this issue and I'm in favor for separating the bug emails to own list. Two good reasons: - People who don't want to read them filter them out anyway - It makes php-dev easier to follow - The php-dev@ archive (e.g. in web) becomes easier to browse and search for discussions The php-bugs@ list should be a read-only list where anyone with cvs account should be subscribed (by default). It being read-only forces any replies to be send to php-dev@ where more intense discussion over the issues in the reports should take place anyway. I tend to agree with it. I bet most of you already filter the bug messages to a different folder (including /dev/null). +1 here Derick Rethans - PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED] SRM: Site Resource Manager - www.vl-srm.net - JDI Media Solutions - www.jdimedia.nl - [EMAIL PROTECTED] Boulevard Heuvelink 102 - 6828 KT Arnhem - The Netherlands - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
