MUF and MPI Policy (Written by Raven)
 
A. The purpose of these policies and their priority
 
     1) The purpose of these policies is to reflect SPR's current
        set of policies in regards to their application in MUF
        and MPI programs.
 
     2) These policies are held with the following priorities
        in mind:
            a) SPR's data base and its integrity
            b) The rights and safety of SPR's citizens
                 as per SPR's main policies.
            c) The rights of the owner and copyright of
                 the effected MUF programs or MPI code.
            d) The needs of SPR for effective and operational
                 code that does not violate SPR's other policies.
            e) Everyone's ability to just relax and have plain
                 and simple fun! :)
  
B. Privacy, Express permission, Player rights, and MUCK Security
 
No programer using MUF or MPI shall be permitted to:   
 
    1) Write and use a program that violates a player's
       rights or privileges as outlined in the documents: 
          news policies
          news interproperty
          news wiz-rules
          news Swedish law
 
    2) Write and use a program that is intended to gain
       information that could not be gained by normal means
       without the express permission of the other person
       or owner of the effected property. Nor violate a
       player's right to privacy in any way. With the 
       exception of where it is required for normal 
       operation of a 'legal' program.  
 
    3) Write and use a program that moves, alters, edits,
       reads, or modifies a player or other object including
       rooms, things, exits/actions, programs, player objects,
       Without the express permission of the owner of that
       property.
 
    4) Write and use a program that is written for the use of 
       spying, monitoring, tracking of another player or a player's 
       objects (a zombie for example) without their knowledge or 
       through the means of deception.
 
    5) Write and use a program that simulates the abilities of
       a MUCKER level higher than has been granted that player.
       Nor simulate the abilities of a WIZARD. Without EXPRESS
       permission by a member of SPR's wiz-staff.  If a programer
       needs permissions of a higher permission level than what
       then currently have, they may either request a higher
       level bit or request that the code be chowned by a wizard
       to allow it to function.  If a programer finds a hole in 
       SPR's security that allows this, they are to report their 
       discovery to the wiz-staff.  If they do not do so and USE 
       this to their advantage they are considered to be in 
       violation of this policy.  See section F of this document.
 
    6) Write and use a program written for the purpose of
       compromising or damaging SPR's database or server.  

 
C. Obtaining a MUCKER bit.
 
    1) M1 
       This level of proficiency is sometimes known as
       'apprentice' you are a beginner and have limited
       access to the MUF primitives. 
       ANY player may have an M1 UNLESS removed for violation 
       of the constitution of SPR and of the rules as defined in 
       this article.  Just make a request for an M1 to any wizard
       who is on-duty or leave page #mail with any MUF wizard.
 
    2) M2
       This level of proficiency is known as the 'journeyman' or 
       regular level of MUF.  You have access at this level
       to nearly all of the MUF primitives.
       ANY player may request an M2. The request should be put to 
       a MUF wizard, and the requirements for receiving an M2 are:
 
         * A verified E-mail address
         * Proof of competence in the form of any MUF program 
             written by the user requesting an M2.
 
    3) M3
       This level of proficiency is known as the 'master' level of
       MUF programing.  You have access to all but the wizard
       primitives. Any player who wishes to obtain an M3 MUST 
       fill demand a) and at least ONE of the demands b) and c). 
       That's either one. both are not mandatory but at least one is.
 
         a) The player has met a request for making a MUF program 
            that shows proof of competence that meets the requesting 
            wizard's definition of functionality and proficiency.
 
         b) The player has given the following information to the 
            MUF wizards:
              * RL E-mail address
              * RL phone number
              * RL name
 
         c) The player has, during at least 2 months, performed well 
            as an M2.
 
    4) Having a MUCKER bit is NOT a privilege nor a right.  As with 
       anything that gives you new abilities, you gain an equal or
       even greater responsibility.  MUCKER bits are handled at the
       discretion of the MUF wizards.  The Staff at SPR believe in
       the right to free creativity; however, a programer must keep 
       in mind that just because you _can_ do something does not 
       mean that you _should_.  Respect for your fellow players is 
       paramount in everything you do as a programer.
 
    5) BUILDER bits enable you to use MPI strings and to write
       effective programs in that language. Programers in MPI
       MUST follow the same policies as do MUCKERS.  Builder
       wizards have discretion in policies concerning MPI.
 
D) Ownership and copyright.
 
    1) See the rules outlined in the article 'news interproperty'
       and section E of this document.
 
    2) All programs and the rights to such belong to the person(s)
       who wrote them.  Just because a program is publicly linkable
       does not make the program 'public' in as far as copyright.
       Moreover, a program may not be copied, altered, or modified
       without the owner's express permission.  With the exception
       of programs effecting the stability of SPR's database or
       programs that are in violation of SPR's policies (also
       known as contraband programs)
 
    3) The above applies to MPI as well.
 
E) Leaving SPR, the owner's rights, and the rights of SPR.
 
    1) If you are a wizard or a MUCKer and wish to resign as such or 
       leave SPR for good and own programs which are crucial to the 
       functionality of SPR, you are encouraged to either take appropriate 
       action, or notify the remaining wizards of how you desire that your 
       intellectual property should be treated, ie. which parts of your
       property can still be used by SPR and which parts, if any, should
       be deleted from SPR as you resign.  Unless we either have a statement
       regarding this, made by you, or can reach you via E-mail, SPR, 
       FurryMUCK, or other MUCKs, we default to the following rules:
 
    2) Unless a wizard or mucker who wishes to resign has stated that it is 
       crucial that the actions taken to complete his or her resignation 
       from wizzardhood or SPR are taken without delay, both the wizard's 
       character and wizard or mucker bit remain unremoved until information 
       regarding the user's desired treatment of his or her intellectual 
       property has reached the remaining SPR wizstaff. Otherwise, we assume 
       that any property of yours which is of relevance to the functionality 
       of SPR can be TEMPORARILY @chowned to a remaining wizard, whose 
       responsibility it is to return it to you upon your return or when a 
       replacement is found. The remaining wizstaff should at this point take 
       it as a matter of honor to as FAST AS POSSIBLE find a replacement for 
       your property.
 
    3) Any and all property will be handled as per the owner's wishes after
       the above steps have been taken.  If the owner seeks to IMMEDIATELY 
       have their programs removed from SPR's database without due
       consideration of the other users, they may make their request of 
       DivineVixen (Gud) who will carry out their wishes after determining
       the consequences of the action.  ALL programs and property BELONG to 
       the original author or caretaker and WILL be disposed of according to 
       their wishes.
 
    4) Any property owned by consensually (due to breaking of rule)
       removed player object should, upon removal of the player object, 
       also be removed.

F) Reporting of security holes.
 
    1) Every programer is asked to report any holes in security
       that they find inherent in the MUF primitives, MUF libraries,
       MPI code, or in any other program related function.
 
    2) Any programer who deliberately uses a security hole to their
       own advantage is to be considered in violation of SPR policy.
 
G) Consequences of abuse.
 
    1) Depending upon the nature and severity of a violation
       in the policies of SPR a MUF or BUILDER wizard may
       demote or even strip a player of their BUILDER or 
       MUCKER bits.  Each violation will be handled on a 
       case by case basis, as each situation is unique in
       its terms. In severe cases @toading is possible.
 
    2) In the case of a contraband program or MPI string
       the staff reserve the right to confiscate the program
       or, after @archiving in the case of MPI @recycle
       the contraband until such time as it is evaluated.
       After which the property will either be @rec'ed or
       restored to the player. The staff of SPR reserve the
       right to protect the citizens of SPR by any means
       necessary and reasonable.
  
    3) You may report violations of these policies to any wizard.
       If you fear retribution by the player in question you may
       take the matter directly to DivineVixen, or the XO-wizzes
       who will handle the matter with your safety in mind.