From: Greg Stark on
On Wed, May 12, 2010 at 5:24 PM, Robert Haas <robertmhaas(a)gmail.com> wrote:
> The difference between discussing a patch and discussing an idea that
> might lead to a patch is fairly fine.

And importantly -- who would be able to subscribe to one and not the
other? If you have to subscribe to both to get make any sense of
things then there's no point.

Fwiw I'm having trouble keeping up these days too. And I'm quite
accustomed to very heavy traffic email. I've been throwing all
postgres related lists into one folder and skimmed through it looking
for important threads. However this has now broken down. There are
about 45 new threads every day. I've been travelling for a bit and am
now 1,500 threads behind...

If we can find a way to split the content sensibly so I could stop
reading some of it that would be helpful. But cutting splitting it
along subject matter where both sets of subject matter need to be seen
by the same people doesn't really help.

I'm thinking I'll move -general (and the useless -novice) to another
folder. But I'm left wondering what to do with -admin and
-performance. They're a random mix of user content and developer
content. I'll probably move them along with -general but that means I
won't be likely to see any development discussion on them in the
future.




--
greg

--
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

My thought had been a split along the lines of major components of the
server ... for instance, a totally seperate list for HS related issues, so
that, if nothing else, those 'lurkers' that are only interested in
developments on that front could be there but not on the main stream
-hackers ... almost like seperate working groups ...

Twas just a thought ...

On Wed, 12 May 2010, Greg Stark wrote:

> On Wed, May 12, 2010 at 5:24 PM, Robert Haas <robertmhaas(a)gmail.com> wrote:
>> The difference between discussing a patch and discussing an idea that
>> might lead to a patch is fairly fine.
>
> And importantly -- who would be able to subscribe to one and not the
> other? If you have to subscribe to both to get make any sense of
> things then there's no point.
>
> Fwiw I'm having trouble keeping up these days too. And I'm quite
> accustomed to very heavy traffic email. I've been throwing all
> postgres related lists into one folder and skimmed through it looking
> for important threads. However this has now broken down. There are
> about 45 new threads every day. I've been travelling for a bit and am
> now 1,500 threads behind...
>
> If we can find a way to split the content sensibly so I could stop
> reading some of it that would be helpful. But cutting splitting it
> along subject matter where both sets of subject matter need to be seen
> by the same people doesn't really help.
>
> I'm thinking I'll move -general (and the useless -novice) to another
> folder. But I'm left wondering what to do with -admin and
> -performance. They're a random mix of user content and developer
> content. I'll probably move them along with -general but that means I
> won't be likely to see any development discussion on them in the
> future.
>
>
>
>
> --
> greg
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

----
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: Yeb Havinga on
Greg Stark wrote:
> On Wed, May 12, 2010 at 5:24 PM, Robert Haas <robertmhaas(a)gmail.com> wrote:
>
>> The difference between discussing a patch and discussing an idea that
>> might lead to a patch is fairly fine.
>>
>
> And importantly -- who would be able to subscribe to one and not the
> other? If you have to subscribe to both to get make any sense of
> things then there's no point.
>
> Fwiw I'm having trouble keeping up these days too. And I'm quite
> accustomed to very heavy traffic email. I've been throwing all
> postgres related lists into one folder and skimmed through it looking
> for important threads. However this has now broken down. There are
> about 45 new threads every day. I've been travelling for a bit and am
> now 1,500 threads behind...
>
I've only been actively reading the pg lists for a few months now, after
several previous attempts that failed mainly because the way I set it up
did not work nice, mainly because of the volume. I tried digests, didn't
like it (how to reply?), also didn't like that the pg mails that were so
many completely swamped the 'main' email I use.

Now I made a new gmail account, subscribed to all lists with some volume
and let it all message per message come into the inbox. Together with
thunderbird/imap this works quite nicely. With filters it's possible to
tag interesting messages (like does the To: contain my email? -> tag it
so it becomes green). Now I only need to view unread mails, (by thread
or date), read some messages and then ctrl-shift-c - all read.

My $0.02 - I like the whole 'don't sort, search' (or how did they call
it?) just let the inbox fill up, google is fast enough. What would be
really interesting is to have some extra 'tags/headers' added to the
emails (document classification with e.g. self organizing map/kohonen),
so my local filters could make labels based on that, instead of perhaps
badly spelled keywords in subjects or message body.

regards,
Yeb Havinga

--
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: Magnus Hagander on
On Thu, May 13, 2010 at 8:05 PM, Marc G. Fournier <scrappy(a)hub.org> wrote:
>
> My thought had been a split along the lines of major components of the server ... for instance, a totally seperate list for HS related issues, so that, if nothing else, those 'lurkers' that are only interested in developments on that front could be there but not on the main stream -hackers ... almost like seperate working groups ...

We tried that with pgsql-hackers-win32 and iirc also
pgsql-hackers-pitr, and it was a big failure...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

--
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
On Thu, 13 May 2010, Magnus Hagander wrote:

> On Thu, May 13, 2010 at 8:05 PM, Marc G. Fournier <scrappy(a)hub.org> wrote:
>>
>> My thought had been a split along the lines of major components of the server ... for instance, a totally seperate list for HS related issues, so that, if nothing else, those 'lurkers' that are only interested in developments on that front could be there but not on the main stream -hackers ... almost like seperate working groups ...
>
> 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 ... guess it depends on if ppl want
it to fail in the first place or not *shrug*

It also depends if a clear line can be drawn and adhered to ...



----
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