Right now, every change on the bugs/patches/feature trackers is posted to pd-dev. That means we get a lot of email on pd-dev from those trackers. The trackers have the ability to send emails more directly with the build-in notification system, and by assigning bug reports to people.
I propose we stop the tracker emails from being posted on pd-dev and instead rely on the trackers' ability to send email. I will still check the bugs directly and assign things to get people's attention.
That way we can reclaim pd-dev as a low-traffic list for essential dev discussions.
.hc
----------------------------------------------------------------------------
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
I agree, it makes more sense for developers like myself who are only working on specific parts of the project, and aren't necessarily concerned with everything going on in the main tracker. It's hard to keep up with relevant discussions when your inbox is constantly being bombarded by SourceForge!
-chris
On 15-Jun-10, at 2:18 PM, Hans-Christoph Steiner wrote:
Right now, every change on the bugs/patches/feature trackers is posted to pd-dev. That means we get a lot of email on pd-dev from those trackers. The trackers have the ability to send emails more directly with the build-in notification system, and by assigning bug reports to people.
I propose we stop the tracker emails from being posted on pd-dev and instead rely on the trackers' ability to send email. I will still check the bugs directly and assign things to get people's attention.
That way we can reclaim pd-dev as a low-traffic list for essential dev discussions.
.hc
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
On 06/15/2010 08:12 PM, Chris Niven wrote:
I agree, it makes more sense for developers like myself who are only working on specific parts of the project, and aren't necessarily concerned with everything going on in the main tracker. It's hard to keep up with relevant discussions when your inbox is constantly being bombarded by SourceForge!
i disagree. i'm usually interested in a lot of bugs that won't be assigned to me, unless i do it myself. i'm not concerned with everything going on in the main tracker (nor the main pd-list), but always find it interesting if information is not too tailored towards me.
it's easy enough to filter out all messages to pd-dev originating from "noreply@sourceforge.net". for what it's worth, mails from the various pd-lists have been sorted out of my inbox for ages (can't bear the traffic)
i wouldn't mind, if mere status changes (e.g. pending->closed transitions; assignments;...) were not reported anymore. i'm only interested in "real" messages by "real" people.
fgmasr IOhannes
On Jun 15, 2010, at 7:02 PM, IOhannes m zmölnig wrote:
On 06/15/2010 08:12 PM, Chris Niven wrote:
I agree, it makes more sense for developers like myself who are only working on specific parts of the project, and aren't necessarily concerned with everything going on in the main tracker. It's hard to keep up with relevant discussions when your inbox is constantly being bombarded by SourceForge!
i disagree. i'm usually interested in a lot of bugs that won't be assigned to me, unless i do it myself. i'm not concerned with everything going on in the main tracker (nor the main pd-list), but always find it interesting if information is not too tailored towards me.
it's easy enough to filter out all messages to pd-dev originating from "noreply@sourceforge.net". for what it's worth, mails from the various pd-lists have been sorted out of my inbox for ages (can't bear the traffic)
i wouldn't mind, if mere status changes (e.g. pending->closed transitions; assignments;...) were not reported anymore. i'm only interested in "real" messages by "real" people.
fgmasr IOhannes
Ok, I switched it to only post to pd-dev when a new bug is submitted. Hope that works for everyone. I should decrease the SF tracker email by a lot.
.hc
----------------------------------------------------------------------------
On Jun 15, 2010, at 7:02 PM, IOhannes m zmölnig wrote:
On 06/15/2010 08:12 PM, Chris Niven wrote:
I agree, it makes more sense for developers like myself who are only working on specific parts of the project, and aren't necessarily concerned with everything going on in the main tracker. It's hard to keep up with relevant discussions when your inbox is constantly being bombarded by SourceForge!
i disagree. i'm usually interested in a lot of bugs that won't be assigned to me, unless i do it myself. i'm not concerned with everything going on in the main tracker (nor the main pd-list), but always find it interesting if information is not too tailored towards me.
it's easy enough to filter out all messages to pd-dev originating from "noreply@sourceforge.net". for what it's worth, mails from the various pd-lists have been sorted out of my inbox for ages (can't bear the traffic)
i wouldn't mind, if mere status changes (e.g. pending->closed transitions; assignments;...) were not reported anymore. i'm only interested in "real" messages by "real" people.
fgmasr IOhannes
Now that I think about it, what about having the trackers post to pd-cvs@iem.at ? Its already a list for automated messages.
.hc
----------------------------------------------------------------------------
Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra