lacsap@plethora.media.mit.edu (Pascal Chesnais) (06/02/91)
*** CALL FOR VOTES ON THE SPLITTING OF COMP.SYS.NEXT *** Here we go, after a long and fruitful discussion, it seems that at this time only four new groups and the removal of comp.sys.next are being called for AT THIS TIME. #1 c.s.n.announce (moderated) - This group is for NeXT computer related announcements. This includes, but is not limited to user group meeting announcements, new products relating specifically to the NeXT machine, and other information announcements (such as the FAQ). This group will be moderated, with me as the moderator (there was a volunteer a while back but I have not heard back from him). #2 c.s.n.sysadmin - This unmoderated group will be dedicated to NeXT specific system administration discussions. This includes software configuration, and addition of peripherals to the NeXT computer. #3 c.s.n.programmer - This group will deal with NeXT related programming issues. Questions about porting of code to the NeXT, programming in NeXTStep environment etc... #4 c.s.n.misc - everything else about the NeXT that has no other place. This will result in comp.sys.next to be renamed as comp.sys.next.misc HOW TO VOTE: Simply cut out the ballot below mark Y or N for each item and send to csn-split@plethora.media.mit.edu. Voting will begin June 1 and end on June 30th at 11:59:59pm. Votes received after June 30 will be ignored/bounced. BALLOT ====== * - #1 create comp.sys.next.announce (moderated by Pascal Chesnais) * - #2 create comp.sys.next.sysadmin * - #3 create comp.sys.next.programmer * - #4 rename comp.sys.next to be comp.sys.next.misc A second request to vote will be issued June 15th (right after USENIX), with a tally of who voted but not how. A final call for votes will be issued June 24th as a last reminder. For the vote to be consider sucessful there must be at least 100 more yes votes than no votes with at least a 2/3 majority.
lacsap@media.mit.edu (Pascal Chesnais) (06/02/91)
The "good" call for votes has been issued, it contains a ballot like the one below. It is possible that the "bad" call for votes leaks into the system, ignore it as it does not have a ballot. The new guidelines require that parallel votes occur rather than one big proposal. Thanks again for your help. pasc In article <j4qhgy_@rpi.edu> lacsap@plethora.media.mit.edu (Pascal Chesnais) writes: > BALLOT > ====== > * - #1 create comp.sys.next.announce (moderated by Pascal Chesnais) > * - #2 create comp.sys.next.sysadmin > * - #3 create comp.sys.next.programmer > * - #4 rename comp.sys.next to be comp.sys.next.misc > -- Pascal Chesnais, Research Specialist, Electronic Publishing Group Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311 email: lacsap@plethora.media.mit.edu (NeXT)
psl@segue.com (Peter Langston) (06/04/91)
Newsgroups: poster Subject: Re: CFV: comp.sys.next reorganization Summary: Expires: References: <j4qhgy_@rpi.edu> Sender: Reply-To: psl@segue.segue.com (Peter Langston) Followup-To: Distribution: Organization: Segue Software, Inc. - Santa Monica, CA. +1-213-453-2161 Keywords: In article <j4qhgy_@rpi.edu> csn-split@plethora.media.mit.edu writes: >*** CALL FOR VOTES ON THE SPLITTING OF COMP.SYS.NEXT *** > [ Much stuff deleted here ] I may be missing something, having only subscribed to comp.sys.next for 3 or 4 weeks, but I haven't seen more than half a dozen messages in that time that weren't related to splitting the group up. Why split up a group that has almost zero traffic? Somehow it reminds me of people who get married because their relationship isn't going well... Peter Langston
dwboyce@acsu.buffalo.edu (Doug Boyce) (06/04/91)
>In article <j4qhgy_@rpi.edu> csn-split@plethora.media.mit.edu writes: >>*** CALL FOR VOTES ON THE SPLITTING OF COMP.SYS.NEXT *** >> >[ Much stuff deleted here ] > >I may be missing something, having only subscribed to comp.sys.next for 3 or >4 weeks, but I haven't seen more than half a dozen messages in that time that >weren't related to splitting the group up. Why split up a group that has >almost zero traffic? Somehow it reminds me of people who get married because >their relationship isn't going well... The perceived "zeroness" of the newsgroup is because the spring school semester has ended. You can tell from even a cursory look at articles that a majority are from students/staff/faculty who mostly don't have USENET/Internet contact when away from school. Prior to mid May this group averaged 500-700 posted a week. You just joined the discussion at the wrong time. -- Doug Boyce dwboyce@acsu.buffalo.edu "Speedballs are interesting if you aren't the cannoneer doing the running." "Where's that Lotto ticket, I want a NeXT NoW!"
eps@toaster.SFSU.EDU (Eric P. Scott) (06/07/91)
In article <1991Jun2.154752.8691@news.media.mit.edu> lacsap@media.mit.edu (Pascal Chesnais) writes: >The new guidelines require that parallel votes occur rather than >one big proposal. Thanks again for your help. There is thus a very good chance that #1-#3 will fail and #4 will pass. It's almost worth asking everyone to vote NNNY just to get the guidelines changed. :-) -=EPS=-
johnr@oceania.UUCP (John Robison) (06/11/91)
In article <7744@segue.segue.com> psl@segue.com (Peter Langston) writes: > > In article <j4qhgy_@rpi.edu> csn-split@plethora.media.mit.edu writes: > >*** CALL FOR VOTES ON THE SPLITTING OF COMP.SYS.NEXT *** > > > [ Much stuff deleted here ] > > I may be missing something, having only subscribed to comp.sys.next for 3 or > 4 weeks, but I haven't seen more than half a dozen messages in that time that > weren't related to splitting the group up. Why split up a group that has > almost zero traffic? Somehow it reminds me of people who get married because > their relationship isn't going well... > Peter Langston Yes you are missing something. We have been discussing this for the last month in news.groups where it is appropriate. For complete details of the whole process, review this news group. johnr -- -- | A sophistical rhetorician, inebriated with the exuberance | | of his own verbosity. --> We gladly accept NeXT Mail <-- | | Try: uunet!oceania!johnr* OR johnr@oceania.UUCP* | | *Not necessarily (mis)representing the company or myself! |