List traffic
in [PgSql]
|
Prev: Patch for PKST timezone
Next: [HACKERS] SHARE locks vs. DELETE in SERIALIZABLE mode (Was: Partitioning/inherited tables vs FKs)
From: "Joshua D. Drake" on 13 May 2010 18:39 On Thu, 2010-05-13 at 19:13 -0300, Marc G. Fournier wrote: > On Thu, 13 May 2010, Tom Lane wrote: > > > "Marc G. Fournier" <scrappy(a)hub.org> writes: > >> On Thu, 13 May 2010, Magnus Hagander wrote: > >>> We tried that with pgsql-hackers-win32 and iirc also > >>> pgsql-hackers-pitr, and it was a big failure... > > > >> But, we are doing that now with pgsql-cluster-hackers and it looks to be > >> working quite well from what I can see ... > > > > Is it? If they want someplace where the majority of hackers won't see > > the discussion, maybe, but I am not sure that's not counterproductive. > > Ideas developed by a small group may or may not survive exposure when > > they reach this list. > > But that, IMHO, is the point of the smaller list ... it allows the group > on that list to hash out their ideas, and, hopefully, deal with both > arguments and counter arguments so that when presented to the larger > group, they would then have a more cohesive arg for their ideas ... Yes and no. After being on these lists for years, I have kind of been moving toward the less is more. E.g; for main list traffic I can see the need for two maybe three, that's it: hackers general www There is no reason why advocacy can't happen on general. Theoretically www could be on hackers (although I do see the point of a separate list). A good MUA will deal with any overhead you have. I use Evolution and no its not perfect but I have no problem managing the hordes of email I get from this community. Between labels, filters, watch lists and all the other goodies any MUA will give you, I see no reason to have this all broken out anymore. Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 13 May 2010 18:46 "Joshua D. Drake" <jd(a)commandprompt.com> writes: > On Thu, 2010-05-13 at 19:13 -0300, Marc G. Fournier wrote: >> But that, IMHO, is the point of the smaller list ... it allows the group >> on that list to hash out their ideas, and, hopefully, deal with both >> arguments and counter arguments so that when presented to the larger >> group, they would then have a more cohesive arg for their ideas ... > Yes and no. After being on these lists for years, I have kind of been > moving toward the less is more. E.g; for main list traffic I can see the > need for two maybe three, that's it: > hackers > general > www I can see the need for small tightly-focused special lists. www is a good example, and perhaps pgsql-cluster-hackers is too (though I'm less convinced of that than Marc is). I agree that we've done poorly with lists with wider charters, mainly because there is so little clarity about which topics belong where. I'd keep -bugs and -performance, which seem to be reasonably well focused, but I can definitely see collapsing most of the other "user" lists into -general. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Marc G. Fournier" on 13 May 2010 23:11 On Thu, 13 May 2010, Joshua D. Drake wrote: > Between labels, filters, watch lists and all the other goodies any MUA > will give you, I see no reason to have this all broken out anymore. So, if one merges all the lists into one (not arguing for / against that), how do you filter? Based on what? Right now, ppl filter based on the X-Mailing-List header, or just the Participant ... ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Alvaro Herrera on 13 May 2010 23:46 Excerpts from Marc G. Fournier's message of jue may 13 23:11:40 -0400 2010: > On Thu, 13 May 2010, Joshua D. Drake wrote: > > > Between labels, filters, watch lists and all the other goodies any MUA > > will give you, I see no reason to have this all broken out anymore. > > So, if one merges all the lists into one (not arguing for / against that), > how do you filter? Based on what? Right now, ppl filter based on the > X-Mailing-List header, or just the Participant ... If most of the questions are badly categorized or cross posted to more than one list, how useful a label is the X-Mailing-List header? How useful is to filter on the "pgsql-general" label? -- -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Marc G. Fournier" on 14 May 2010 01:29
On Thu, 13 May 2010, Alvaro Herrera wrote: > If most of the questions are badly categorized or cross posted to more > than one list, how useful a label is the X-Mailing-List header? How > useful is to filter on the "pgsql-general" label? That is a point, but, IMHO, that is one of our key issues ... we *allow* that sort of cross-posting in the first place ... FreeBSD lists allow cross-posting to no more then 2 mailing lists, I believe, but there is definitely a limit ... .... is there a reason why, other the fact that we don't do now, that we can't just put in a restriction against cross posting altogether? .... and, for those that have been here awhile, who "should know better", why isn't there any self-management of this sort of stuff in the first place? ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |