Re: RFD: comp.databases.postgresql.general - Mailing list pgsql-general

From Woodchuck Bill
Subject Re: RFD: comp.databases.postgresql.general
Date
Msg-id Xns959A90651EBEDbswr607h4@130.133.1.4
Whole thread Raw
In response to Re: RFD: comp.databases.postgresql.general  (Mike Cox <mikecoxlinux@yahoo.com>)
List pgsql-general
Klaas <spampit@klaas.ca> wrote in
news:spampit-A439E7.13032007112004@host170.octanews.net:

>> No that is not what I'm proposing.  Each group MUST go through the
>> RFD and CFV seperately.  I started off with the most popular group
>> first.  After It was done, I would have started on the rest.
>
> Not true.  It is actually rather common for an RFD to be proposed for
> several groups at once.  The CFV contains one voting option per group.

[comp.databases.postgresql.general added]

Russ and would probably consider waiving the vote, and creating a group for
each of the popular lists that have a tested popularity base. He already
said that he was in favor of one group per list.

One question is..would creating one comp.* group for *each* of the lists
(the way the rogue groups are currently structured) be too many PostgreSql
Big-8 groups? Or, could it be cut down to, say, four or five groups/lists?

--
Bill

pgsql-general by date:

Previous
From: stig erikson
Date:
Subject: dumping on 7.4.6 importing on 7.4.1
Next
From: edward ohare
Date:
Subject: Re: ALERT This mailing list may be voted into a newsgroup