![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
In article <2vcp1nF2k0ftbU1 (AT) uni-berlin (DOT) de>, Mike Cox <mikecoxlinux (AT) yahoo (DOT) com> wrote: comp.databases.postgresql.general How about just comp.databases.postgresql or (shudder) comp.databases.postgresql.misc? |
#12
| |||
| |||
|
|
The new proposal should have all of the lists. I am amazed that an unknown interloper is trying to dictate which lists should be voted on. I am affiliated with a network of over 60 PostgreSql users/developers, and I will e-mail each one of those people a ballot. If your next proposal does not contain every single one of the lists, you can expect essentially all of those 60 people to vote no. I will campaign passionately against your proposal if you leave out even one of the lists. Do the right thing if you are sincerely trying to help the list subscribers. This is my last post to news.groups about this. |
#13
| |||
| |||
|
|
In article <spampit-3A2F1E.20451409112004 (AT) host170 (DOT) octanews.net>, Klaas <spampit (AT) klaas (DOT) ca> wrote: In article <2vcp1nF2k0ftbU1 (AT) uni-berlin (DOT) de>, Mike Cox <mikecoxlinux (AT) yahoo (DOT) com> wrote: comp.databases.postgresql.general How about just comp.databases.postgresql or (shudder) comp.databases.postgresql.misc? The whole point of this proposal is that c.d.p.general *already* exists in an unofficial sense on some servers, and that it should be made "official." |
|
Creating a new group with a different name will simply confuse matters on those servers that already carry c.d.p.general. |
#14
| |||
| |||
|
|
Obviously, there cannot be 21 postgresql groups in the comp.* hierarchy. |
|
I did a check on news.postgresql.org to see which newsgroups are the most popular and also the ones which cover the relevant postgresql topics. Most of the postgresql topics and traffic are represented in these four newsgroups: comp.databases.postgresql.admin comp.databases.postgresql.general comp.databases.postgresql.hackers comp.databases.postgresql.sql |
#15
| |||
| |||
|
|
The new proposal should have all of the lists. I am amazed that an unknown interloper is trying to dictate which lists should be voted on. I am affiliated with a network of over 60 PostgreSql users/developers, and I will e-mail each one of those people a ballot. If your next proposal does not contain every single one of the lists, you can expect essentially all of those 60 people to vote no. I will campaign passionately against your proposal if you leave out even one of the lists. Do the right thing if you are sincerely trying to help the list subscribers. This is my last post to news.groups about this. |
#16
| |||
| |||
|
|
The ones not on the list to be made into the big 8 will always be accessible from the news.postgresql.org server. Also, please, if I've missed an important group you think SHOULD be in the big 8, please let me know in this thread. |
#17
| |||
| |||
|
|
This is my last post to news.groups about this. |
#18
| |||
| |||
|
|
The new proposal should have all of the lists. |
#19
| |||
| |||
|
|
BTW, in Outlook Express if you are posting to the news.postgresql.org server it will not send a message to news.groups. So this message will not get there unless someone puts it there. If 4 are official and 16 are unofficial, why would that bother you? |
#20
| |||
| |||
|
|
At 01:54 AM 11/14/2004, Sim Zacks wrote: BTW, in Outlook Express if you are posting to the news.postgresql.org server it will not send a message to news.groups. So this message will not get there unless someone puts it there. If 4 are official and 16 are unofficial, why would that bother you? Because the groups already exist on many servers. Make them all legit and gate them all. Problem solved. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html |
![]() |
| Thread Tools | |
| Display Modes | |
| |