• Test Linking Policy V1.0 as of 2nd of June 2017
  • When a server is accepted for linking, it starts off as a test link. A test link is a temporary status assigned to new servers linked to the network. It helps us make sure that new servers are stable and can adhere to our linking policies. During a test link, the server will be linked to one of our hub servers closest to its region.
  • It will have a DNS entry added and will be part of the rotation right away.
  • In addition, any IRC operator introduced to staff by way of linking a server will NOT receive any permissions with network services, unless all network owners unanimously agree.
  • Owner of the Server of Test link will be given IRCOP (OPERServ Limited Access)
  • After the initial test link period is up (at least 3 weeks), the network’s management team (All Staff) will come together, provide input on the server’s observed stability and conformity to network linking policy, and come to one of the following 3 decisions
  • Link rejected – the link is rejected and terminated. A detailed explanation will be given if this is the case. If the link introduced an IRC operator to network staff, he/she may be retained on staff if they are determined to be a valuable asset to the network.
  • Test link continued – the link remains in test link status for an additional duration not to exceed 42 days. If necessary, an explanation as to why we require an extended test link status for the server will be given.
  • Link accepted – the link has passed test link status and is promoted to full link. Any restrictions applied during test link phase are removed immediately.
  • Upon Link accepted Owner’s Server access on (OPERServ Limited Access) will be moved up to Servers Administrator on (OPERServ Services)

    Understand that Root Access (OPERServ Access) is only reserved for those that own the network