![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
The other issue is that I would like to add the other postgresql groups for consideration to be included into the big 8. However there are quite a few of them, and I don't know if all of them deserve to be there. They are all under comp.databases.postgresql.*, and I highly doubt Marc would want to eliminate them. I will have to include them all and have a heavy postgresql presense in the comp.databases.* hierarchy. I have no advice to offer on this. How many are there exactly? |
#2
| |||
| |||
|
|
barbara (AT) bookpro (DOT) com wrote in news:10outlgpkitaq20 (AT) corp (DOT) supernews.com: The other issue is that I would like to add the other postgresql groups for consideration to be included into the big 8. However there are quite a few of them, and I don't know if all of them deserve to be there. They are all under comp.databases.postgresql.*, and I highly doubt Marc would want to eliminate them. |
#3
| |||
| |||
|
|
barbara (AT) bookpro (DOT) com wrote in news:10outlgpkitaq20 (AT) corp (DOT) supernews.com: The other issue is that I would like to add the other postgresql groups for consideration to be included into the big 8. However there are quite a few of them, and I don't know if all of them deserve to be there. They are all under comp.databases.postgresql.*, and I highly doubt Marc would want to eliminate them. I think Marc understands by now that these lists won't be eliminated. It's a parallel process. Let's start with a few and create the other groups down the road. An RFD with 21 groups has a good chance to be rejected, not because they are not relevant, just because it's too many at one time. I assume a second RFD should be 'filed' in 6 months with the remaining groups, and should be nothing more than a cruise. |
![]() |
| Thread Tools | |
| Display Modes | |
| |