ZX-News #31 13 мая 1997

SPbZXNet

Charter SPbZXNet - Charter Network SPbZXNet v2.18.

             CHARTER SpbZxNet



                      (C) Alexei Mikhailov


  So wait ... I have the opportunity to present to you the 
first, and only the finished version of the Charter of the 
network. For shoulders of the authors (and the fact that the 
development of the Charter involves a large number of people 
who think everything is clear) two half months of work, 
permanent settlement and battles, and all for the benefit of 
the network, all for the benefit of all users SpbZxNet. 


  Charter dalsya easy, and it remained
points of contention, and even before the end of unexamined 
places, many of the items - a compromise between two extremes, 
between the two completely opposing views. But

all the most difficult past. At the expense of perfection or 
imperfection of the Charter will the only time I can only 
guarantee which is clearly obsolete items will be repaired as 
soon as the need for their raison d'être - the Charter provides 
for the rapid amend it. However, it is not

means that changes will be introduced,
when someone in the head vzbredet - only if
This is a real need.


  Charter is required to perform all
Network members SpbZxNet and comes into effect
May 20, 1997.


  Some of the applications of the Charter, we have
published in ZxNews, and some publish in blizhaishih rooms. 
After the release of ZN32, to all nodes in the network will be 
sent to the file "Network.Z" with the Charter and all 
applications. Recommend sysop "issue" of his entire new users, 
callers to the station. Continuing in-line "network" will be on 
the Tornado station, good place for me a lot ... 



                   Charter Network SpbZxNet v2.18.



                           1. Review.



  This document establishes policy for all members of the 
organization SpbZxNet. Network SpbZxNet defined by the list of 
nodes and hubs, published weekly by the Coordinator network. 


  The creation of this document have been partly used Statutes
ZX-Net and FidoNet.


                    2. Determination SpbZxNet.



  SpbZxNet - this e-mail system based on computer
ZX-Spectrum computers or other platforms that provide this 
system. All of its members and the operators are working 
voluntarily, although it is possible the introduction of 
specific sysop paying job or additional levels of access to 
their station. 


                        2.1 Organization.



  Members (users) SpbZxNet are those persons having personal 
addresses on the network. Entering the network, or in other 
words, getting it's network address, the user indicates that he 
agrees comply with all requirements of the Charter and its 
annexes. 


  GATE - Gateway. Station (Station system) network, carrying out
translation and transmittal of information between different 
computer systems and networks. 


  HUB - The central node connected to it by node and the point.


  C-HUB - The central hub - a hub that is linked against the 
internal Echo Conference.



  NODE - A node. The basic unit of the network. Station E-mail
connected to it with points and the user.


                2.1.1 Station e-mail.

                -------------------------------

  For any network user establishes the right to open your
site, their e-mail station. To do this he must obtain 
node-address on one of the hubs SpbZxNet. 


                       2.1.2 Station BBS.

                       -----------------

  Any user can open his station BBS.


  To open the station BBS does not necessarily receive the 
node-address. Station BBS, installed at Point Network SpbZxNet, 
called independent station, and its operator - independent 
system operator. 


  Independent sysop is not a sysop network SpbZxNet, he takes 
part in it on the Rights of the usual Point. 


  Station BBS can also be installed on any node, gate, central 
sites and a central hub network SpbZxNet. Node-or Hub-address 
does not necessarily mean the presence of the station BBS - is 
their cause, sisopov how they will forward mail to their the 
point. 


                      2.2 The Council SpbZxNet.



  Council SpbZxNet called collegial body that is addressing 
critical issues related to device organization and development 
of the network. 


   The Council consists of a network of its founders:


   812/00.00 Aleksandr Majorov

   812/01.00 Alex Mikhailov

   812/02.00 Andrey Golubev

   812/03.00 Paul Falcon

   812/04.00 Roman Moiseev

   812/10.00 Boris Sokol


  Council SpbZxNet called as necessary by the Coordinator
network, or a majority of those who it is. Also, voting can 
pass through e-mail. 


  If someone leaves the Council at a general meeting sisopov an 
election of a man who will take the place of the past. 


  The Council plays a major role in resolving the most severe 
conflicts among all users have the right to make amendments and 
additions to the Charter. 


  The Council may overrule any decision of the Coordinator, if 
it violates the Charter. 


                    2.3 System operators.



                   2.3.1 Definition sysop.

                   ------------------------

  Sysop (system operator) - is the owner of the station e
mail.


  Since sysops provide network resources of personal equipment
and are the sole owners of their stations, they have the right 
(on the its sole discretion) to dictate any terms of users who 
use these free resources. 


  Based on the foregoing, the claims of users (with the 
exception of complaints on the passage of an e-mail address) to 
any sysop networks are baseless and are not considered. 


                     2.3.2 Local Charter.

                     ---------------------

  Local Charter - a local (internal) rules of work with
Station BBS, the user has installed a network SpbZxNet. They do 
not contravene the basic Charter and serve only for the reports 
to other users how the relationship between them, and sysop. 
Local Charter is an optional attribute. 


                 2.3.3 Responsibilities sysop Noda.

                 -----------------------------

  The duties SysOra node is to support health
a node, the registration points (if the sysop does not want, 
for whatever reasons, to issue pointovy address, or provide 
user's access to its BBS, then he is entitled not to do so and 
not comment on its decision), timely mail forwarding their 
points on the network, informing the Coordinator of the 
inoperable station and periodically informing him about the 
changes in the list of points. 


            2.3.4 Responsibilities sisopov gateway and hub.

            --------------------------------------

  The system operator network gateway SpbZxNet provides for the 
exchange of information users SpbZxNet with users on other 
networks. 


  The system operator ensures the shipment hub of information 
between their nodes, as well as connected to other hubs and 
gate network for the exchange of mail.



  The system operator of the central hub, in addition to other 
duties sysop hub is engaged and still processing all internal 
Mail (under the "internal mail" gets the internal mail users 
SpbZxNet, and external, as well as correspondence that came in 
SpbZxNet from other networks). 


  In the case of the heavy workload of the hub of postal 
correspondence, he raises the issue with the coordinator of the 
network to change the route of mail flow. 


  Routing mail between its nodes is determined by the hub 
itself. 


                      2.3.5 Rights sisopov.

                      -------------------

  In the right SysOrov SpbZxNet network is able to offer
Council to make certain amendments to this Charter. Decision on
changing the rules of the Charter was adopted by a simple 
majority on the Council network.



  SysOp also has the right to decide on punishment Users
your site for violation of the Charter of the network or user 
of its BBS for violation of local rules of the site up to 
disconnect from the site or from the station. 


                    2.3.6 Connecting the hub.

                    ----------------------

  Hubs are opened in proportion to the volume of mail to and 
from to a maximum of nine nodes per hub.



  Issuance of hub-Coordinator E-Mail address. Sysop hub can
be any node, a defunct network is not less than three months.


   Refused to open the hub may be for the following reasons:


   - Lack at the moment need a new hub

   - Past violations of the Charter, which led to

     disconnected from the network

   - In case of insufficient kompetententsii candidate in 
question 

     of the hub and the network as a whole


  For that to become a sysop hub, some people claim, then the 
right of final choice rests with the Coordinator. 


                     2.3.7 Disabling the hub.

                     ---------------------

  In the case of non-functioning hub than a week, in case of 
violations of the Charter sysop hub, which resulted in his 
private trip, the hub disconnected from the network, its nodes 
are also closed and deprived of addresses, and can get the new 
addresses to other existing hubs. 


                    2.3.8 Connecting the site.

                    ----------------------

  Nodnye address issues coordinator of the network after 
agreement issue with the sysop of the hub, which will connect 
the new node, and depending on the current route mail. Rules 
for the opening of the site, see Appendix No3. 


                     2.3.9 Disabling the site.

                     ---------------------

  Sysop hub can be unplugged from their station of any of its 
node, notifying the Coordinator no less than three days before 
the shutdown. In this case, data on the node are removed from 
the list bbs network, while ex-sysop node receives a new 
address on another hub. 


  In the case of non-functioning site for more than 20 days, it 
is automatically deleted from the list of nodes SpbZxNet. 
Network address is reserved for nodom (can not be extradited to 
another node) within Three months after graduation.



  Also, a node can be disabled (read only) for a period of one
weeks or more of the outer echo-conference, if because of him, 
or because of his Point, gateway received the "Medal of Honour" 
("*", "+" "!" etc.) from the moderator of the conference. In 
the inner ehah there are rules to these conferences.



                      02/03/1910 Exchange mail.

                      -------------------

  Since each node-mail should regularly (at least once in three
days) to go to the hub. Time mail exchange between nodes and 
hub, and well as between central nodes and gateways, is 
discussed and solved a sysop on their own.



  The advantage of the appointment time, the operator enjoys a 
central location (hub). Disputes between the hub decides 
Coordinator, depending on the circumstances. 


      03/02/1911 Program, which can be sent over the network.

      --------------------------------------------------

  Network SpbZxNet can be sent (to pass in the file or ehah
laid out in stations bbs) only non-profit program.


                 2.4 Network Coordinator SpbZxNet.



  Coordinator of the network SpbZxNet is a person who 
coordinates the the network and gateways, providing normal 
functioning SpbZxNet as a whole. 


  The Coordinator is the highest administrative unit in
SpbZxNet. Its responsibility includes the overall management of 
the network: monitor compliance by all users, and sysop of the 
Charter and decisions of the network, the solution of all 
issues on the network and firewall level. In the case of 
non-network users rules of the Charter, Coordinator impose 
penalties under the Charter, until the user disconnects for up 
to three months. 


  The duties of the Coordinator and includes: weekly
node list, contracts with other networks or operators gateways, 
coordinating mail routing between hubs and gate within the 
network. 


                   2.4.1 Election Coordinator.

                   -------------------------

  Election Coordinator, made at the Council network. This 
requires that voted for him more than fifty percent members of 
the Council. Coordinator may be chosen any person having a 
node-or hub-address, in this case, if he did not enter until 
this to the Council network, it becomes the seventh member of 
the Board until the re-election. The Coordinator shall be 
elected for a term of three months. 


                 2.4.2 Re-election of the Coordinator.

                 -----------------------------

  Re-election of the Coordinator may be made only after a 
period of three months after the election. 


                 2.4.3 Assistant Coordinator.

                 ----------------------------

  The Coordinator may appoint an assistant and partly transfer 
them to some of its functions. 


  Assistant has no right to make decisions on behalf of the 
Coordinator. The coordinator has the right to overrule any 
decision helper. 


            2.5 Persons who are not part of the network,

    but also have certain rights and responsibilities in it.



                        2.5.1 Moderator.

                        ---------------

  Moderator - man, part of the right of the echo of the 
conference, which he moderated, and watching over their 
execution, ie the duties of moderator is to deal with all 
issues at the level they moderated the echo area, any user with 
network address can be a moderator of your echo area. For this, 
he shall formulate its rules and submit to the

Coordinator, who decides to have the issue of opening 
(registration) A new ekhi. 


                  2.5.1.1 Options moderator.


  The rules of this particular conference is the echo of its 
moderator, but they can not contradict the Constitution, he is 
watching them compliance, he applies the same sanctions to 
violators in accordance with these rules, rules of the 
conference are published regularly in itself, in the extreme 
case can ask the moderator to send them to you netmaylom.



  In case of inconsistency rules ekhi Charter, responsibility
for her walking no one is. Coordinator may notify the
This discrepancy of all network users and to prohibit its 
linking to a central hub. 


  Moderators can modify the rules of their echo-conference
at any time. The new version of the rules shall take effect no 
less than 24 hours after its publication in the conference. 


  In case of dissatisfaction with the actions of the moderator, 
such as prejudice to certain subscribers, or unfair punishment, 
any sysop node network SpbZxNet or any other network, where the 
gate, this conference is entitled to send netmaylom Coordinator 
of the protest, citing insufficient evidence. In this case, 
initsiativae Coordinator can take re-election conference 
moderator, or follow its closure. Echo-conference may also be 
closed for disobeying moderator decision Coordinator. Closing 
echo conference means the termination of linking it to the 
C-HUB'e. 


          2.5.1.2 General Rules for all the echo area.


  In the case of gross violations of the Charter in the echo of 
the conference, the coordinator may give an indication of 
moderator on the application of administrative punishment. A 
decision on the degree of punishment adopted by the Coordinator 
under the Charter. 


  List of registered echo conference network can SpbZxNet
found on the C-HUB'e network SpbZxNet.


              2.5.1.3 Administrative message.


    Rules for writing administrative messages used by:


  - Network Coordinator - messages at the network level

  - Moderator - posts on a moderated level of ekhi


  If the 'From:' is Coordinator or Moderator, this means that 
the message should be below the administrative order, and any 
reaction (commenting) on ​​this message to the echo-conferences 
is forbidden. All the complaints and suggestions sent to 
moderator netmaylom, requests may be sent to the Coordinator as 
netmaylom and in SPBZXNET.SYSOPS. 


                  2.5.2 Subscribers of the network (POINT).

                  ---------------------------
  Subscriber (points) SpbZxNet is a user registered at one 
station bbs, in the network, and received her network address. 


  The duties of Point is the strict implementation of the 
Charter and local rules of nodes.



  If the user is not clear or specific requirements of the 
Charter its provisions, they may seek clarification from the 
sysop / Council / Coordinator netmaylom. In this case, they are 
not obliged to give any explanation.



  Subscribers are entitled to use the resources SpbZxNet in 
their interests for all types of correspondence and shipment of 
non-profit programs.



                      Nick 2.5.3 (USER).

                      ------------------

  Nick station bbs - people who do not have your address on the 
network. They have no right to use the services provided by the 
network, and can only use the services of the station where 
they are registered, for example, its local echo conference. 


       2.5.4 Faulty points and users to the station.

       -------------------------------------------------

  In case of violation points or nick station local rules, the 
decision on punishment takes the sysop. 


  Sysops network responsible for all actions of its users, but 
do not bear responsibility for their points, ie in violation of 
the Charter of the network points, in the case of incorrect and 
extremely nekorrektonogo behavior, exposed himself to 
punishment Point, not sysop. 


             3. Conflict situations and their solutions.



          3.1 Failure to send the mail file.



  If when you make a mail recipient is incorrect, or no letter 
is decorated according to the standard network SpbZxNet (see 
the "memo"), operators of the site and the hub is not 
responsible for its transmission and correspondence with the 
user can not enter. 


                  3.2 Improper conduct.



   - An attempt with BBS in the off time for her, trying to re
     gistratsii not within the allotted time;

   - The unauthorized appropriation of the address (without 
registration); 

   - Liaison with bbs under false passwords;

   - Sending mail nonexistent recipients;

   - Behavior that runs counter to the generally accepted 
standards of morality      mi.



            3.3 Extremely annoying behavior.



   - The use of foul language or expressions, which

     can be interpreted as such in the general correspondence;


  Under the "extremely ungentlemanly conduct" also fall into 
the following steps: 


  Public insult, humiliation, persecution on racial
signs of any user on the network, vysskazyvanie discontent
networking, action coordinator and his assistants, the 
discussion moderator action, the Coordinator and the Board 
Network echo-conferences, discussion of action in any sisopov 
ehah except SPBZXNET.SYSOPS (ie, discuss the actions sisopov 
can only themselves sysops), intentional and (or) the 
systematic sabotage of network development, not following the 
instructions of the Coordinator, the Council network or 
Moderators, disorderly conduct on any single station (Stations) 
- attempts to "hang" server "attacks" on the sysop, The sending 
of threatening letters and abuse, etc., inciting and provoking 
the conflict and strife between members of the network, 
transmission network commercial programs without the permission 
of their authors, for sending by BBS Station unregistered 
internal echo-conferences without sisopov consent of BBS.



  If a user or sysop believes that he suffered abuse at 
netmayle, he sends the letter or the Coordinator, or 
SPBZXNET.SYSOPS. Decision on punishment made Coordinator.



                      3.4 Measures of restraint.



  In the discussion and analysis of cases of improper behavior
bias against the violators are not allowed!


            3.4.1 In case of improper behavior.

            --------------------------------------

  In case of improper behavior can be applied to any of the
the following:


  - A warning about incorrect behavior in a personal letter;

  - Warning about the incorrect behavior in the echo, in the 
case 

    when the offender does not respond to a private warning;

  - Disabling the subscriber from a specific station or from a 
particular 

    Echo Conference;


  In the case of repeated violations, the actions are equal to
"Extremely abnormal behavior" and it may entail disconnecting 
from all servers in the network (see Section 3.4.2.). 


      3.4.2 In the case of extremely abusive behavior.

      --------------------------------------------------

  In the case of extremely abusive behavior should be Point
immediate expulsion from the list of points of the network and 
user-sheet with all the stations. 


  In the case of extremely abusive behavior on the part of the 
System Operator's site, his station is excluded from the list 
of nodes and make corresponding changes in bbs_list, and his 
points! can be re-registered at other stations.



               3.4.2.1 Possible penalties.


  - Completely disconnected from the network any of its user 
and off for more than three months 


  Decision on the adoption of the measures taken by simple 
majority vote of the Council. 


  - Disconnect from the network for up to three months, any of 
its user 


  Decision on the adoption of this measure takes the 
coordinator of the network. 


  - Disconnect from this particular echo conference every user 
on the network for any period 


  Decision on the adoption of this measure takes the Moderator 
of this ekhi. 


                      4. General Provisions.



            4.1 Ignorance of the Constitution and local 
regulations. 



  Ignorance of the Constitution and the local rules is no 
excuse for inappropriate behavior and not exempt from 
liability. 


                       4.2 The author of the Charter.



   (C) Alexei Mikhailov, 1997


   St. Petersburg, Russia


   812/01.00 @ SpbZxNet

   2:5030 / 529.13 @ FidoNet


                 4.3 List of applications of the Charter.



   1. Memo Novice network SpbZxNet

   2. Rules for processing letters of FidoNet

   3. Memo beginner sysop

   4. Regulation of opening and working with file-ehami

   5. Rules of registration letters on the Internet


      The list of applications can be extended!


                  4.4 Amendments and Supplements.



  Charter adopted by the Council network SpbZxNet April 8, 1997.


  Amendments and additions were made:


  Number Item Date


    - - -


        __________________________