Volume 5, Number 4 25 January 1988 +---------------------------------------------------------------+ | _ | | / \ | | /|oo \ | | - FidoNews - (_| /_) | | _`@/_ \ _ | | International | | \ \\ | | FidoNet Association | (*) | \ )) | | Newsletter ______ |__U__| / \// | | / FIDO \ _//|| _\ / | | (________) (_/(_|(____/ | | (jm) | +---------------------------------------------------------------+ Editor in Chief Dale Lovell Editor Emeritus: Thom Henderson Chief Procrastinator Emeritus: Tom Jennings Contributing Editors: Al Arango FidoNews is published weekly by the International FidoNet Association as its official newsletter. You are encouraged to submit articles for publication in FidoNews. Article submission standards are contained in the file ARTSPEC.DOC, available from node 1:1/1. Copyright 1987 by the International FidoNet Association. All rights reserved. Duplication and/or distribution permitted for noncommercial purposes only. For use in other circumstances, please contact IFNA at (314) 576-4067. IFNA may also be contacted at PO Box 41143, St. Louis, MO 63141. The contents of the articles contained here are not our responsibility, nor do we necessarily agree with them. Everything here is subject to debate. We publish EVERYTHING received. Table of Contents 1. EDITORIAL ................................................ 1 2. ARTICLES ................................................. 2 The FidoNet Bill of Rights, part 2 ....................... 2 POLICY4 Draft Proposal from Neal Curtin .................. 8 REDCON An EchoMail Idea follow-up ........................ 20 SOUTHERNET(tm) Another View of an old problem ............ 21 Voyager 1's Problems ..................................... 22 3. WANTED ................................................... 26 4. NOTICES .................................................. 27 The Interrupt Stack ...................................... 27 Latest Software Versions ................................. 27 FidoNews 5-04 Page 1 25 Jan 1988 ================================================================= EDITORIAL ================================================================= Well, I think I've finally got things worked out here at FidoNews. There were a few problems at first, but I think I've finally got everything worked out. Hopefully everything will work again this week and I can count on everything working as it should. Some of you may have a received a miniature copy of FidoNews two weeks ago. I'd like to apologize for this, but for some reason the software that puts FidoNews together won't run properly off of a file server. I caught the error at about 2:00 am, unfortunately some people had already gotten a copy. I quickly fixed the problem with the one being sent out, but missed a FNEWS502.ARC. A few more picked up the bad file and while I tried to send out a corrected version to everyone but may have missed someone in all the confusion. I'd like to thank all of you who have sent me mail and submissions. You've all helped make FidoNews what it is, and have helped keep the net together at the same time. What are some of the articles you can look forward to in the near future? Well, starting off this week there is the first of a proposed POLICY4 document for FidoNet (not IFNA). These should be running over the next few weeks. In addition to the proposed documents, I'd like to see some discussion on them. If FidoNet appears to come to a consensus on a POLICY4.DOC, it will end up affecting everyone. So make sure you speak up now. We also have some articles on some of the new software being used in FidoNet. Programs like BinkleyTerm and the new Opus. I'd also like to see some articles on Fido version 12 and Dutchie while we're at it. I'm also still waiting for some new columns in FidoNews. It still seems a little empty knowing I won't be writing my old column for some time and I'd like to fill that spot in the near future. Oh well...It's approaching print time and I've got to get this over to the other machine here. Next time around I should actually have something to say about some of the recent events in FidoNet. Until then, read and enjoy! Your Editor, Dale Lovell 1:1/1 (1:157/504) 216/642-1034 (data) Home Work 3266 Vezber Drive Parma Computer Center Seven Hills, OH 44131 5402 State Road 216/524-1875 (voice) Parma, OH 44134 216/661-1808 ----------------------------------------------------------------- FidoNews 5-04 Page 2 25 Jan 1988 ================================================================= ARTICLES ================================================================= Randy Edwards 132/555.1 The Bill of Rights Follow Up Since I put out the FidoNet Sysop's Bill of Rights I've heard many comments and suggestions about it. I'd like to share a few thoughts about the idea. Some have thought that this proposal in some way 'threatens' IFNA. I couldn't disagree more. I see it as complimenting IFNA and in fact making IFNA more 'legit'. By this I mean with the Bill of Rights or something similar in place, we'll have a democratic, free for all FidoNet with elected coordinators managing the day to day operations. What could compliment IFNA more? Some have mentioned that the Coordinator elections will become a big political circus. I don't think so. You'll notice the election 'season' is limited to 30 days and for 90% of the elections there will be 50 or less votes to count. This should be fast and easy to manage and verify. I think most nodes in the Network are quite happy with their coordinators (I am) and I don't foresee any massive changes or radical swings. Even if that were to happen it'd be the _will_ of the net. I don't believe we'll have a lot of problems with new coordinators. A new coordinator can't have less than a year in the FidoNet, so we won't have a chance of a raw rookie as Zone Coordinator. And with an orderly system of replacement we'll have less 'burnout' and we'll bring fresh blood into the system. The FidoNet is getting too large and powerful to have it keep running the way it was when it had 50 nodes. It's time for real netwide democracy. A few things to consider ... Do we have a consistent netwide policy of replacing coordinators and preventing 'burnout'? No. Do we have a consistent policy of having assistant or temporary coordinators in case of unexpected events? No. Does each node in the network have a fair and equal voice in FidoNews 5-04 Page 3 25 Jan 1988 how it is being governed? No. Does each node have protection from software discrimination and unfair dues, taxes, or fees? No. Does each node have protection from others deleting echomail or automatically copying all of their incoming netmail? No. Here's one attempt at solving those and a few other problems. [*] THE FIDONET SYSOP'S BILL OF RIGHTS [*] version 0.10 [1] Any new POLICYx document must be ratified by the same process as an amendment or deletion to this document. (see #10 below) [2] (a) No node may delete or modify (except modification by recognized netmail utilities) intransit netmail unless it is obviously illegal in nature. Copying or recording of intransit messages is forbidden. An exception to this right is prior agreement between all parties. (b) No node may delete or modify (except modification by recognized net/echomail utilities) intransit echomail unless it is obviously illegal in nature. An exception to this rule is an agreed-upon conference moderator. All nodes must do any local modification or deletion ('chopping' or 'ed- meeseing') of echomail after it is scanned. [3] (a) Every node has the right to choose to be listed in either the local geographic network, or as an independent node in the local geographic region. (b) No independent regional node will be subject to any mandatory dues, taxes, or fees of any kind. (c) Every node has the right to run any FTSC approved software and no network will restrict software types. [4] Every network will have an Election every 12 months. The election will be held in June (see {2} below), in honor of the month the original FidoNet converted nodelists. Every node in the network will have one vote towards the position of Network Coordinator. Elections are won by straight majority, but elections that are not won by more than 5% are submitted to an automatic revote within 30 days. This is to ensure the winner of an election has enough support to work effectively and to help prevent controversial election results. The Network Coordinator, upon election, will name an assistant. The Assistant Coordinator (at each level (Net, FidoNews 5-04 Page 4 25 Jan 1988 Reg., Zone)) will act as Coordinator at any time the elected coordinator is unable to. Additionally, if a Coordinator resigns, the Assistant will take over until the following election (or recalled by a recall vote, see below). The newly elected Network Coordinator will serve until the following June when a new election will be held. The Network Coordinator will act as a combination 'Prime Minister' and 'Representative' of the Net in addition to any other duties outlined in Policy4. Additionally, if there are 10 or more independant nodes in a Region, (termed a Group, see {1} below) they are also encouraged to have similar elections as above selecting one person to be thier Representative, though since independent regional nodes are independent, the Representative's position will be in an unofficial capacity (see below). [5] If at any time during a Network Coordinators term of office, if 25% of the nodes in the network agree they can submit a Request for Recall to the Network and Regional Coordinators, who will have 2 weeks to verify the Request for Recall and respond to the plantiffs via netmail. Within 60 days of the Request for Recall a new election will be held (unless the June election is within 60 days). [6] Every region will have an Election every 12 months. The election will be held in August (see {2} below), in honor of the month of the first FidoCon and the birth of IFNA and the start of democracy in the FidoNet. Every Network Coordinator in the Region will vote towards the position of Regional Coordinator. Additionally, if a Region has 10 or more independant nodes in it and the nodes have elected a Representative (see above), then that Representative will vote in the Regional elections. Each Network Coordinator (and Group Rep) will cast votes toward the position of Regional Coordinator which total up to the total number of nodes that the Network Coordinator (Rep.) had in his Network (or Group) at the time he was elected. But, if the total number of nodes in any one net or group in any particular region add up to 50% or more of the total nodes in that region then that net must be broken up into two (or more) nets to prevent unfair elections. The Regional Coordinator, upon election, will name an assistant and serve until the following August when a new election will be held. The Regional Coordinator will act as a combination 'Prime Minister' and 'Representative' of the Region, in addition to any other duties outlined in Policy4. [7] If at any time during a Regional Coordinators term of office, if 25% of the Network Coordinators (plus one vote for a qualified 10+ elected independant regional Group Representative) in the region agree they can submit a Request for Recall to the Regional and Zone Coordinators, who will have 2 weeks to verify the Request for Recall and respond to the plantiffs via netmail. Within 60 days of the FidoNews 5-04 Page 5 25 Jan 1988 Request for Recall a new election will be held (unless the August election is within 60 days). [8] Every zone will have an Election every 12 months. The election will be held in September (see {2} below), in honor of the month of the first St. Louis nodelist. Every Regional Coordinator in the Zone will vote towards the position of Zone Coordinator. Each Regional Coordinator will cast votes toward the position of Zone Coordinator which total up to the total number of nodes that the Regional Coordinator had in his Region at the time he was elected. If the total number of nodes in any one region in the zone add up to 50% or more of the total nodes in that zone then that region must be broken up into two (or more) regions. The Zone Coordinator, upon election, will name an assistant and serve until the following September when a new election will be held. The Zone Coordinator will act as a combination 'Prime Minister' and 'Representative' of the Zone in addition to any other duties outlined in Policy4. [9] If at any time during a Zone Coordinators term of office, if 25% of the Regional Coordinators (plus one vote for a qualified 10+ Group) in the zone agree they can submit a Request for Recall to the Zone and Int'l Coordinators, who will have 2 weeks to verify the Request for Recall and respond to the plantiffs via netmail. Within 60 days of the Request for Recall a new election will be held (unless the August election is within 60 days). [10] An amendment or deletion to this Bill of Rights or ratification of a new Policy document is done by a Constitional Convention. The exact procedure is this: If a node wishes an amendment or deletion (which should be thought out carefully, for it is a very serious matter) he must write up a Proposal for the amend