• Policy 4 Ingles (2/3)

    From Enric Lleal Serra@2:343/107.1 to All on Thu Jul 19 14:24:00 2007
    Hola All!

    3.5 Be a Member of the Area Administered

    A coordinator must be a member of the area administered. That is, a Network Coordinator must be a member of that network by virtue of geography. A Regional Coordinator must be either a member of a network in the region, or
    an independent in the region.


    3.6 Encourage New Sysops to Enter FidoNet

    A coordinator is encouraged to operate a public bulletin board system which
    is freely available for the purpose of distributing Policy, FidoNews, and Nodelists to potential new sysops. Dissemination of this information to persons who are potential FidoNet sysops is important to the growth of
    FidoNet, and coordinators should encourage development of new systems.


    3.7 Tradition and Precedent

    A coordinator is not bound by the practices of predecessor or peers beyond
    the scope of this document.

    In addition, a new coordinator has the right to review any decision made by predecessors for compliance with Policy, and take whatever actions may be necessary to rectify any situations not in compliance.


    3.8 Technical Management

    The primary responsibility of any coordinator is technical management of network operations. Decisions must be made on technical grounds.



    4 Network Coordinator Procedures

    4.1 Responsibilities

    A Network Coordinator has the following responsibilities:

    1) To receive incoming mail for nodes in the network, and arrange
    delivery to its recipients.

    2) To assign node numbers to nodes in the network.

    3) To maintain the nodelist for the network, and to send a copy of it to
    the Regional Coordinator whenever it changes.

    4) To make available to nodes in the network new nodelist difference
    files, new issues of FidoNews, and new revisions of Network Policy
    Documents as they are received, and to periodically check to insure that
    nodes use up to date nodelists.


    4.2 Routing Inbound Mail

    It is your responsibility as Network Coordinator to coordinate the receipt
    and forwarding of host-routed inbound netmail for nodes in your network. The best way to accomplish this is left to your discretion.

    If a node in your network is receiving large volumes of mail you can request that the sysop contact the systems which are sending this mail and request
    that they not host-route it. If the problem persists, you can request your Regional Coordinator to assign the node a number as an independent and drop
    the system from your network.

    Occasionally a node will make a "bombing run" (sending one message to a great many nodes). If a node in another network is making bombing runs on your
    nodes and routing them through your inbound host, then you can complain to
    the network coordinator of the offending node. (If the node is an indepen- dent, complain to the regional coordinator.) Bombing runs are considered to
    be annoying.

    Another source of routing overload is echomail. Echomail cannot be allowed
    to degrade the ability of FidoNet to handle normal message traffic. If a
    node in your network is routing large volumes of echomail, you can ask the sysop to either limit the amount of echomail or to stop routing echomail.

    You are not required to forward encrypted, commercial, or illegal mail. However, you must follow the procedures described in section 2.1.7 if you do not forward the mail.


    4.3 Assigning Node Numbers

    It is your responsibility to assign node numbers to new nodes in your net- work. You may also change the numbers of existing nodes in your network, though you should check with your member nodes before doing so. You may
    assign any numbers you wish, so long as each node has a unique number within your network.

    You must not assign a node number to any system until you have received a formal request from that system by FidoNet mail. This will ensure that the system is minimally operational. The strict maintenance of this policy has been one of the great strengths of FidoNet.

    It is also recommended, though not required, that you call a board which is applying for a node number before assigning it a node number.

    You may not assign a node number to a node in an area covered by an existing network. Further, if you have nodes in an area covered by a network in formation, those nodes must be transferred to the new network.

    You should use network mail to inform a new sysop of the node number, as this helps to insure that the system is capable of receiving network mail.

    If a node in your network is acting in a sufficiently annoying manner, then
    you can take whatever action you deem fit, according to the circumstances of the case.


    4.4 Maintaining the Nodelist


    You should implement name changes, phone number changes, and so forth in your segment of the nodelist as soon as possible after the information is received from the affected node. You should also on occasion send a message to every node in your network to ensure that they are operational. If a node turns
    out to be "off the air" with no prior warning, you can either mark the node down or remove it from the nodelist. (Nodes are to be marked DOWN for a maximum of two weeks, after which the line should be removed from the node- list.)

    At your discretion, you may distribute a portion of this workload to routing hubs. In this case, you should receive the nodelists from the Hub Coordina- tors within your network. You will need to maintain a set of nodelists for each hub within your network, since you cannot count on getting an update
    from each Hub Coordinator every week. You should assemble a master nodelist for your network every week and send it to your Regional Coordinator by the
    day and time designated. It is suggested that you do this as late as is practical, so as to accommodate any late changes, balanced with the risk of missing the connection with your Regional Coordinator and thus losing a week.

    4.5 Making Available Policies, Nodelists and FidoNews

    As a Network Coordinator you should obtain a new issue of FidoNews and a new nodelist difference file every week from your Regional Coordinator. The nodelist difference file is currently made available each Saturday, and FidoNews is published each Monday. You must make these files available to
    all nodes in the network, and you are encouraged to make them available to
    the general public for download.

    You should also obtain the most recent versions of the Policy documents that bind the members of your network, and make those available to the nodes in
    your network. Policies are released at sporadic intervals, so you should
    also inform the nodes in your network when such events occur, and ensure the nodes are generally familiar with the changes.

    Policy, FidoNews, and the nodelist are the glue that holds us together.
    Without them, we would cease to be a community, and become just another
    random collection of bulletin boards.



    5 Regional Coordinator Procedures

    5.1 Responsibilities

    A Regional Coordinator has the following responsibilities:

    1) To assign node numbers to independent nodes in the region.

    2) To encourage independent nodes in the region to join existing net-
    works, or to form new networks.

    3) To assign network numbers to networks in the region and define their
    boundaries.

    4) To compile a nodelist of all of the networks and independents in the
    region, and to send a copy of it to the Zone Coordinator whenever it
    changes.

    5) To ensure the smooth operation of networks within the region.

    6) To make new nodelist difference files, Policies, and issues of
    FidoNews available to the Network Coordinators in the region as soon as
    is practical.


    5.2 Assigning Node Numbers

    It is your responsibility to assign node numbers to independent nodes in your region. You may also change the numbers of existing nodes in your region, though you should check with the respective nodes before doing so. You may assign any numbers you wish, so long as each node has a unique number within your region.

    You should not assign a node number to any system until you have received a formal request from that system by FidoNet mail. This will ensure that the system is minimally operational. The strict maintenance of this policy has been one of the great strengths of FidoNet.

    It is also recommended, though not required, that you call a board which is applying for a node number before assigning it a node number.

    You should use network mail to inform a new sysop of the node number, as this helps to insure that the system is capable of receiving network mail.

    If a node in your region is acting in a sufficiently annoying manner, then
    you can take whatever action you deem fit, according to the circumstances of the case.

    If you receive a node number request from outside your region, you must
    forward it to the most local coordinator for the requestor as you can deter- mine. If you receive a node number request from a new node that is in an
    area covered by an existing network, then you must forward the request to the Coordinator of that network instead of assigning a number yourself.

    If a network forms in an area for which you have independent nodes, those
    nodes will be transferred to the local network as soon as is practical.


    5.3 Encouraging the Formation and Growth of Networks

    One of your main duties as a Regional Coordinator is to promote the growth of networks in your region.

    You should avoid having independent nodes in your region which are within the coverage area of a network. There are, however, certain cases where a node should not be a member of a network, such as a system with a large amount of inbound netmail; see section 4.2.

    If several independent nodes in your region are in a local area you should encourage them to form a network, and if necessary you may require them to
    form a network. Refer to section 2.4. Note that this is not intended to encourage the formation of trivial networks. Obviously, one node does not
    make a network. The exact number of nodes required for an effective network must be judged according to the circumstances of the situation, and is left
    to your discretion.


    5.4 Assigning Network Numbers

    It is your responsibility to assign network numbers to new networks forming within your region. You are assigned a pool of network numbers to use for
    this purpose by your Zone Coordinator. As a part of this function, it is the responsibility of the Regional Coordinator to define the boundaries of the networks in the region.


    5.5 Maintaining the Nodelist

    As a Regional Coordinator, you have a dual role in maintaining the nodelist
    for your region.

    First, you must maintain the list of independent nodes in your region. You should attempt to implement name changes, phone number changes, and so forth
    in this nodelist as soon as possible. You should also on occasion send a message to every independent node in your region to ensure that they are operational. If a node turns out to be "off the air" with no prior warning, you can either mark the node down or remove it from the nodelist. (Nodes are to marked DOWN for a maximum of two weeks, after which the line should be removed from the nodelist.)

    Second, you must receive the nodelists from the Network Coordinators within your region. You will need to maintain a set of nodelists for each network within your region, since you cannot count on getting an update from each Network Coordinator every week. You should assemble a master nodelist for
    your region every week and send it to your Zone Coordinator by the day and
    time designated. It is suggested that you do this as late as practical, so
    as to accommodate late changes, balanced with the risk of missing the connec- tion with your Zone Coordinator and thus losing a week.


    5.6 Geographic Exemptions

    There are cases where local calling geography does not follow FidoNet re- gions. In exceptional cases, exemptions to normal geographic guidelines are agreed upon by the Regional Coordinators and Zone Coordinator involved. Such an exemption is not a right, and is not permanent. When a network is formed
    in the proper region that would provide local calling access to the exempted node, it is no longer exempt. An exemption may be reviewed and revoked at
    any time by any of the coordinators involved.


    5.7 Overseeing Network Operations

    You are responsible for appointing network coordinators for the nets in your region. If the outgoing Network Coordinator suggests a successor, you are
    not obligated to accept that individual, although you normally will. Simi- larly, you are not obligated to accept the individual selected by the members of the network in an election, although you normally will.

    It is your responsibility as Regional Coordinator to ensure that the networks within your region are operating in an acceptable manner. This does not mean that you are required to operate those networks; that is the responsibility
    of the Network Coordinators. It means that you are responsible for assuring that the Network Coordinators within your region are acting responsibly.

    If you find that a Network Coordinator within your region is not properly performing the duties outlined in Section 4, you should take whatever action you deem necessary to correct the situation.

    If a network grows so large that it cannot reasonably accommodate traffic
    flow during the Zone Mail Hour, the Regional Coordinator can direct the creation of one or more new networks from that network. These new networks, although they may be within a single local-calling area, must still conform
    to a geographical basis for determining membership.

    It is your obligation as Regional Coordinator to maintain direct and reason- ably frequent contact with the networks in your region. The exact method of accomplishing this is left to your discretion.


    5.8 Making Available Nodelists, Policies, and FidoNews

    As a Regional Coordinator, it is your responsibility to obtain the latest nodelist difference file, network policies, and the latest issues of FidoNews as they are published, and to make them available to the Network Coordinators within your region. The nodelist is posted weekly on Saturday by the Zone Coordinator, and FidoNews is published weekly on Monday by node 1/1. Contact them for more details on how to obtain the latest copies each week.

    It is your responsibility to make these available to all Network Coordina- tors in your region as soon as is practical after you receive them. The
    method of distribution is left to your discretion. You are not required to distribute them to any independent nodes in your region, though you may if
    you wish. You are encouraged to make all these documents available for downloading by the general public.



    6 Zone Coordinator Procedures

    6.1 General

    A Zone Coordinator for FidoNet has the primary task of maintaining the
    nodelist for the Zone, sharing it with the other Zone Coordinators, and ensuring the distribution of the master nodelist (or difference file) to the Regions in the Zone. The Zone Coordinator is also responsible for coordinat- ing the distribution of Network Policy documents and FidoNews to the Regional Coordinators in the zone.

    The Zone Coordinator is responsible for the maintenance of the nodelist for
    the administrative region. The Administrative Region has the same number as the zone, and consists of nodes assigned for administrative purposes not related to the sending and receiving of normal network mail.

    A Zone Coordinator is charged with the task of ensuring the smooth operation
    of the Zone, which is done by appointing and supervising the Regional Coordi- nators.

    If a Zone Coordinator determines that a Regional Coordinator is not properly performing the duties outlined in section 5, a replacement should be found.

    The Zone Coordinator defines the geographic boundaries of the regions within the zone and sets the time for the Zone Mail Hour.

    The Zone Coordinator is responsible for reviewing and approving any geograph- ic exemptions as described in section 5.6.

    The Zone Coordinator is responsible for insuring the smooth operation of
    gates between that zone and all other zones for the transfer of interzonal mail.

    The Zone Coordinators are responsible for the selection of the International Coordinator from among their ranks.


    6.2 Selection

    The Zone Coordinator is selected by an absolute majority vote of the Regional Coordinators within the zone.


    7 International Coordinator Procedures

    7.1 General

    The International Coordinator is the "first among equals" Zone Coordinator.

    The International Coordinator has the primary task of coordinating the
    creation of the master nodelist by managing the distribution between the
    Zones of the Zone nodelists. The International Coordinator is responsible
    for definition of new zones and for negotiation of agreements for communica- tion with other networks. ("Other network" in this context means other networks with which FidoNet communicates as peer-to-peer, not "network" in
    the sense of the FidoNet organizational level.)

    The International Coordinator is also responsible for coordinating the distribution of Network Policies and FidoNews to the Zone Coordinators.

    The International Coordinator is responsible for coordinating the activities
    of the Zone Coordinator Council. The International Coordinator acts as the spokesman for the Zone Coordinator Council.

    In cases not specifically covered by this document, the International Coordi- nator may issue specific interpretations or extensions to this policy. The Zone Coordinator Council may reverse such rulings by a majority vote.

    7.2 Selection

    The International Coordinator is selected (or removed) by an absolute majori- ty vote of the Zone Coordinators.


    8 Referenda

    The procedures described in this section are used to ratify a new version of FidoNet policy, which is the mechanism by which policy is changed. This procedure is also used to impeach a Zone Coordinator.


    8.1 Initiation

    A referendum on policy modification is invoked when a majority of the
    FidoNet Regional Coordinators inform the International Coordinator that they wish to consider a proposed new version of Policy.


    8.2 Announcement and Results Notification

    Proposed changes to Policy are distributed using the same structure which is used to distribute nodelist difference files and FidoNews. Results and announcements related to the referendum are distributed by the coordinator structure as a part of the weekly nodelist difference file. The Interna- tional Coordinator provides copies to the editor of FidoNews for inclusion there, although the official announcement and voting dates are tied to
    nodelist distributions.

    If it is adopted, the International Coordinator sets the effective date for a new policy through announcement in the weekly nodelist difference file. The effective date will be not more than one month after the close of balloting.


    8.3 Eligibility to Vote

    Each member of the FidoNet coordinator structure at and above Network Coordi- nator is entitled to one vote. (Hub coordinators do not vote.) In the case
    of the position changing hands during the balloting process, either the incumbent or the new coordinator may vote, but not both. If a person holds more than one coordinator position, they still receive only one vote.

    Network coordinators are expected to assess the opinions of the members of their network, and to vote accordingly. A formal election is not necessary, but the network coordinator must inform the net of the issues and solicit input. The network coordinator functions as the representative of the rank
    and file members of FidoNet.


    8.4 Voting Mechanism

    The actual voting mechanism, including whether the ballot is secret and how
    the ballots are to be collected, verified, and counted, is left to the discretion of the International Coordinator. Ideally, ballot collection
    should be by some secure message system, conducted over FidoNet itself.

    In order to provide a discussion period, the announcement of any ballot must
    be made at least two weeks before the date of voting commencement. The balloting period must be at least two weeks.


    8.5 Voting on a whole Policy Document

    Given that Policy is intertwined and self referencing, a relatively simple change may require several alterations of the document. In order to simplify the process, balloting is done on choices between whole documents, rather
    than individual amendments. In the simplest case, this means voting yea or
    nay to a new document. If a number of alternatives are to be considered,
    they must be presented as whole documents, from which one is chosen.


    8.6 Decision of vote

    A Policy amendment is considered in force if, at the end of the balloting period, it has received a majority of the votes cast. For example, if there were 350 eligible voters, 100 of which cast a vote, then at least 51 affirma- tive votes would be required to declare the amendment in force.

    In the case of multiple policy changes which are considered on the same
    ballot, a version must receive more than 50% of the votes cast to be consid- ered ratified. "Abstain" is a valid vote in this case, effectively being a vote for not changing the current policy as it simply increases the number of votes required to ratify the proposed change.


    8.7 Impeachment of a Zone Coordinator

    8.7.1 Initiation

    In extreme cases, a Zone Coordinator may be impeached by referendum. Im- peachment of a Zone Coordinator does not require a Policy violation. An impeachment proceeding is invoked when a majority of the Regional Coordina- tors in a zone request the International Coordinator to institute it.

    8.7.2 Procedure as in Policy Referendum

    The provisions of sections 8.2 and 8.3 apply to impeachment referenda.

    The definition of "majority" in section 8.6 applies. Only coordinators in
    the affected zone vote (even if the zone coordinator is also the Internation- al Coordinator).

    8.7.3 Voting Mechanism

    The balloting procedures are set, the votes are collected, and the results
    are announced by a Regional Coordinator chosen by the Zone Coordinator who is being impeached. The removal of the Zone Coordinator is effective two weeks after the end of balloting if the impeachment carries.

    8.7.4 Limited to once per year

    The removal of a Zone Coordinator is primarily intended to be a mechanism by which the net as a whole expresses displeasure with the way Policy is being interpreted. At one time or another, everyone is unhappy with the way policy is interpreted. In order to keep the Zone Coordinators interpreting policy
    as opposed to defending themselves, at least one full calendar year must
    elapse between impeachment referenda (regardless of how many people hold the position of Zone Coordinator during that year.)

    Should a Zone Coordinator resign during an impeachment process, the process
    is considered null and void, and does not consume the "once per year quota".


    9 Resolution of Disputes

    9.1 General

    The FidoNet judicial philosophy can be summed up in two rules:

    1) Thou shalt not excessively annoy others.

    2) Thou shalt not be too easily annoyed.

    In other words, there are no hard and fast rules of conduct, but reasonably polite behavior is expected. Also, in any dispute both sides are examined,
    and action could be taken against either or both parties. ("Judge not, lest
    ye be judged!")

    The coordinator structure has the responsibility for defining "excessively annoying". Like a common definition of pornography ("I can't define it, but
    I know it when I see it."), a hard and fast definition of acceptable FidoNet behavior is not possible. The guidelines in this policy are deliberately
    vague to provide the freedom that the coordinator structure requires to
    respond to the needs of a growing and changing community.

    The first step in any dispute between sysops is for the sysops to attempt to communicate directly, at least by netmail, preferably by voice. Any com- plaint made that has skipped this most basic communication step will be rejected.

    Filing a formal complaint is not an action which should be taken lightly. Investigation and response to complaints requires time which coordinators
    would prefer to spend doing more constructive activities. Persons who
    persist in filing trivial policy complaints may find themselves on the wrong side of an excessively-annoying complaint. Complaints must be accompanied
    with verifiable evidence, generally copies of messages; a simple word-of-
    mouth complaint will be dismissed out of hand.

    Failure to follow the procedures herein described (in particular, by skipping
    a coordinator, or involving a coordinator not in the appeal chain) is in and
    of itself annoying behavior.


    9.2 Problems with Another Sysop

    If you are having problems with another sysop, you should first try to work
    it out via netmail or voice conversation with the other sysop.

    If this fails to resolve the problem, you should complain to your Network Coordinator and the other sysop's Network Coordinator. If one or both of you is not in a network, then complain to the appropriate Regional Coordinator. Should this fail to provide satisfaction, you have the right to follow the appeal process described in section 9.5.


    9.3 Problems with your Network Coordinator

    If you are having problems with your Network Coordinator and feel that you
    are not being treated properly, you are entitled to a review of your situa- tion. As with all disputes, the first step is to communicate directly to attempt to resolve the problem.

    The next step is to contact your Regional Coordinator. If your case has
    merit, there are several possible courses of action, including a change of Network Coordinators or even the disbanding of your network. If you have
    been excommunicated by your Network Coordinator, that judgement may be reversed, at which point you will be reinstated into your net.

    If you fail to obtain relief from your Regional Coordinator, you have the
    right to follow the appeal process described in section 9.5.

    Sigue en el último... (2/3)

    -
    A reveure!!
    Enric

    --- FMail/Win32 1.60
    * Origin: El celibato no es hereditario. (2:343/107.1)