The Devil's Doorknob BBS Capture (1996-2003)

home *** CD-ROM | disk | FTP | other *** search

/ The Devil's Doorknob BBS Capture (1996-2003) / devilsdoorknobbbscapture1996-2003.iso / WWIV.ZIP / WIVLNK / LINKGDLN.3 < prev next >

Wrap

Text File | 1996-01-05 | 15.2 KB | 349 lines

Filename: LINKGDLN.3 WWIVLINK NATIONAL GUIDELINES, Part II (Adopted January 1991) ------Beginning of Part II, See LINKGDLN.2 for Part I----- ARTICLE VIII. - Board Members A. Zone Coordinator: This position has been covered in other Guideline paragraphs. B. Link Ombudsman: It shall be the duty of the Link Ombudsman to act as an intermediary in all disputes between individual SysOps and the Board, for the purpose of resolving said disputes when they can not be handled through the SysOp's AC or ZC. Further, it shall be the job of the Ombudsman to act as an impartial member of the Board, being concerned with the Link as a whole, and not acting solely on the behalf of one Zone over another. 1. The Ombudsman will also serve as Interzone Coordinator (IC), processing connections between nodes in different Zones. At least one AC will forward the interzone connection request directly to the IC, confirmation by both AC's is not required. The IC will also distribute BBSLIST.0 and FBACKHDR.NET (information added to network analysis feedback). (Ratified March 1993) Article IX. - Advisory Positions to the Board The following offices will act in an advisory capacity to the Board, for the purpose of keeping the board informed of all Link-related activity from the associated positions/committees: A. Software Coordinator: It shall be the duty of the Software Coordinator to keep the board notified of all developments and their status. Further, it shall be the SC's job to make suggestions for new software, and to take recommendations for software changes/additions to the software committee. B. Message-sub Coordinator: It shall be the duty of the MC to maintain the list of active message subs that are available on the WWIVLink, and to ensure proper distribution of said lists. Further, it shall be the MC's job to apprise the board of any conflict arising from sub-related concerns, where two or more subs, or subs in direct conflict with the Bylaws, are concerned. C. Guidelines Coordinator: It shall be the job of the GC to maintain the current guidelines, to notify the Board of any pending changes to said guidelines, and to ensure proper distribution of the current guidelines to all members of the WWIVLink. D. Vote Coordinator: It shall be the job of the Vote Coordinator to count the votes for elections, modifications to the Guidelines, and other votes of an Area-wide through Link-wide nature. Software to accomplish this task will be provided, and pending the final count on any vote, the VC will provide these results to the Board, and to the general populous concerned with the vote. Article X. - Voting practices Given the intended democratic nature of the WWIVLink, it shall be held to be true that all offices within the Link hierarchy shall be considered temporary, and all persons occupying said offices shall be voted or otherwise appointed to these offices by the appropriate population, on a regular basis, as follows: A. Zone Coordinators: This office shall be of a one year duration, the anniversary month to fall in February. The voting population for this office shall be the SysOps of each affected Zone, voting for that Zone's ZC; B. Area Code Coordinators: This office shall be of a one year duration, the anniversary month to fall in March. The voting population for this office shall be all SysOps within each given Area Code, voting for that Area Code's AC; C. Software Coordinator: This office shall be of a one year duration, the anniversary month to fall in April. The voting population for this office shall be all members of the Software Committee; D. Guidelines Coordinator: This office shall be of a one year duration, the anniversary month to fall in April. The voting population for this office shall be all members of the Guidelines Committee; E. Message Sub Coordinator: This office shall be one that is filled on a voluntary basis, rather than an elected position. The post shall have no defined expiration date, but will be subject to periodic review by the Board; F. Vote Coordinator: This office shall be of a one year duration, the anniversary month to fall in January. The voting population for this office shall be comprised of all SysOps in the WWIVLink network. (Formerly February - Change Ratified October 31, 1994) G. The Link Ombudsman: (Ratified March 1993) This office shall be of a one year duration, the anniversary month to fall in February. The voting population for this office shall be comprised of all SysOps in the WWIVLink network. H. (Ratified XXX 19XX) WWIVLink has no restrictions on how many nodes one sysop may operate. Therefore, in order to maintain fairness in the voting procedures, the following policies are in effect: 1. Any sysop who is running multiple systems in WWIVLink is entitled to only one vote on an issue or for an election. 2. A sysop who is running multiple WWIVLink systems must inform the Vote Coordinator (or whoever is presiding over a local election) of which node he will be using to cast his vote, prior to any voting period. 3. It will be the responsibility of the Vote Coordinator (or other officer presiding over a local election) to ensure that each sysop casts only one vote. 4. All AC's and ZC's should maintain a list of the sysops in their respective areas who run multiple nodes, and should notify the Voting Coordinator of those sysops who run multiple nodes, whenever a second or additional node by one sysop is added to the Link BBSLISTs. Article XI. - Removal From Office During the course of the year, there may arise occasion for the removal of an officer, or in the event of a new person being elected into office at the end of a term. As such, the following guidelines are set forth to handle such occurrences: A. In the event that a new officer is voted into office during the regular vote, the previous officer shall pass along any software or other information that is required of the job to the newly elected officer. The out-going officer shall delete all official WWIVLink files pertaining to that office from his system after passing them along to the new officer; B. In the event that an officer must relinquish his post during the normal term for that office, said officer shall inform the concerned voting population and the Board of his intentions, giving notice as far in advance as is possible. In the event that a suitable replacement cannot be voted into office before the leaving of said officer, the next higher officer in the chain shall assume responsibility for that office until a vote is held; C. In the event that an officer is deemed unfit to continue his term in office by the affected population, and only after all reasonable attempts to correct any problems have been made, no less than 2/3 of the voting population will email or otherwise notify the next higher office in the chain of their wishes to replace said officer. Should it be deemed that all attempts to rectify the problem have been reasonably tried, the officer contacted (a ZC or the Board) shall announce a vote, and shall take over the duties of the affected office until such a vote has been accomplished. D. In no case will the newly elected official serve in that office past the regularly scheduled election date, but rather will only serve as an interim officer. It may be decided at the time of the election that the regular election is too close to warrant a temporary officer, in which case, the next higher officer shall maintain the office until the normal vote has been concluded. Article XII. - The Guidelines Committee (Ratified Fall 1992) The establishment of these guidelines has by no means completed them. It will always be necessary to make changes to them, and to have a Guidelines Committee (GuideComm) to perform this function. This addendum defines and guides the Committee, and provides its statement of operating policy openly. A. Guidelines Coordinator (GC) The GC will act as public spokesman for the GuideComm, and will make periodic reports, to the Link Board and all Link Sysops, of issues under consideration and what is being done on the Committee. The GC will moderate the discussion of all topics. The GC's vote on all matters shall be equal to that of each Guidelines Committee member. B. Committee Members The number of active members on the Committee shall number no more than 12, but the GC has the option of allowing a limited number of sysops to act as non-voting observers to the Committee. Any sysop wishing to be an active or observing member of the GuideComm must contact the GC, who will add him to the list of sysops wishing to join. When a committee member leaves the Committee, the GC will add new members on the principle of first-come, first-served. If a Committee member has been inactive for a length of time during active discussion of an issue, the GC will have the option of removing that member (after attempting to contact the member to discover the reason for the absence). C. Amending the Guidelines Issues to be discussed will be determined by a variety of factors, including concerns raised by Link SysOps, discussion on the Link Policy Sub (a companion to the Guidelines Sub available to all Link SysOps), and suggestions from the Link Board. To avoid confusion, the topics should be taken one at a time. The final wording of an amendment or addendum will be voted upon by active committee members, with the majority determining action. On occasion, several alternatives to an addendum will be considered; the one with the most votes will be accepted. After an amendment/addendum has been agreed upon, the GC will send it to the Vote Coordinator, who will send it out on a ballot to be voted upon by all SysOps. At the GC's option, several amendments/addenda may be submitted at once. Each amendment/addendum will be a separate item on the ballot. D. Progress reports The GC will report on the GuideComm's actions at least every six months. The reports will be posted on the Link National Sysops and Link Policy subs, and will include issues under consideration by the Committee and issues that have been resolved, who is currently on the committee, and when the next vote on Link agenda will be. Article XIII. - WWIVLink Gateways (Ratified December 1992) A. Definition A gateway shall be considered to be any sort of automatic transfer of messages from WWIVLink subs or WWIVLink email to subs or email on another network, such as WWIVnet or Fidonet. This exchange would take place as a part of the BBS software through external programs used for this purpose. Posts manually uploaded to or from WWIVLink subs or email shall not be considered a part of a gateway. B. Implementation Gateways shall be permitted in WWIVLink, subject to the following conditions: 1. WWIVLink subs may be gated to more than one other network. Only one gateway per sub is permitted to any particular network, and the WWIVLink sub host's approval is required. 2. Email may be transferred between WWIVLink and another network. 3. Neither WWIVLink nor any other network will be used as a conduit for messages not destined for that network. 4. Caution should be used in the gating of subs from other networks with large volume. If a gateway is likely to increase a sub's traffic by 75 or more messages a day, direct connections or the permission of intervening connects is highly recommended. Keep in mind that any sysop may change their connections if they feel that a gateway increases their traffic and cost too much, or for any other reason not in conflict with these Guidelines. 5. Under no circumstances may messages with files attached be sent through WWIVLink. Article XIV. - Local Addenda to WWIVLink Guidelines (Ratified December 29, 1995) A local area may, at their option, create local guidelines that will apply only to that area. However, they must meet the following criteria: 1. They may not in any way conflict with the National Guidelines, and it must be agreed that if a later National Guideline Amendment comes in conflict with the local guidelines, the National Guidelines will prevail; 2. Local Guidelines MUST be voted on by the area sysops, not simply created by a committee or AC; 3. No local Guidelines will give the AC powers beyond those enumerated in the National Guidelines; 4. Any sysop in the area may ask the Guidelines Coordinator to review local guidelines for conflicts with National Guidelines at any time. APPENDIX A -- Arrangement of Zones The following listing of Zones indicates the boundaries and jurisdictions of each of the North American Zone Coordinators and is included here for information only. Some new Area Codes may not be included. ZONE 1 - PACIFIC Areas Included in Zone Alaska 907; British Columbia 604; California 707, 916, 415, 209, 310, 406, 510, 805, 818, 213, 714, 619, 919; Hawaii 808; Oregon 503; Nevada 702; Washington 206, 509. ZONE 2 - MOUNTAIN Alberta 403; Arizona 602; Colorado 303, 719; Idaho 208; Montana 406; New Mexico 505; Nebraska 308; South Dakota 605; Utah 801; Wyoming 307. ZONE 3 - CENTRAL Alabama 205; Arkansas 501; Illinois 815, 312, 309, 217, 618; Iowa 712, 515, 319; Kansas 913, 316; Louisiana 318, 504; Manitoba 204; Minnesota 218, 612, 507; Missouri 816, 417, 314; Mississippi 601; Nebraska 402; North Dakota 701; Oklahoma 405, 918; Saskatchewan 306; Tennessee 901, 615; Texas 210, 409, 713, 806, 817, 214, 915, 512; Wisconsin 715, 606, 414. ZONE 4 - EASTERN Connecticut 203; Delaware 302; District of Columbia 202; Florida 904, 407, 813; Georgia 404, 912; Indiana 219, 317, 812; Maryland 301, 410; Massachusetts 413, 508, 617; Maine 207; Michigan 906, 616, 517, 313; New Brunswick 506; New Hampshire 603; New Jersey 516, 201, 609; New York 518, 315, 716, 607, 914, 212, 718; Newfoundland 709; North Carolina 704, 919; Ohio 419, 216, 513, 614; Ontario 807, 705, 519, 416; Quebec 819, 418, 613, 514; Rhode Island 401; South Carolina 803; Vermont 802; Virginia 703, 804; West Virginia 304. APPENDIX B -- Software Approved by the Link Board for Packet Monitoring Netprobe by Tolkein. Contact: WWIV Software Services.