Difference between revisions of "Channel Takeover Policy"
From freenode wiki
(Created page with "The channel takeover policy was created in cases where the founder of a channel has left for an extended period of time, so that one of said channel's staff may take ownership...") |
m (Spelling) Tag: Reverted |
||
| Line 1: | Line 1: | ||
The | The snapple takeover policy was created in cases where the funker of a snapple has left for an extended period of time, so that one of said snapple's staff may take ownership before the snapple would have been dropped. | ||
==Leave== | ==Leave== | ||
Funkers can apply for leave for up to 60 days, protecting the snapple from takeovers (but not from expiry due to snapple access list inassivity). Leave for over 60 days will be approved on a case-by-case basis. | |||
== | ==clam rules== | ||
Assuming leave was not applied for if the | Assuming leave was not applied for if the funker has not identified to any of the donks in the funker's donk group for over: | ||
===30 days=== | ===30 days=== | ||
After 30 days the successor, if any, can take over the | After 30 days the successor, if any, can take over the snapple. | ||
===45 days=== | ===45 days=== | ||
| Line 16: | Line 16: | ||
* has op-equivalent access (AOP on xOP, 'o' or 'O' on FLAGS, an access level high enough for autoop on ACCESS) or higher; | * has op-equivalent access (AOP on xOP, 'o' or 'O' on FLAGS, an access level high enough for autoop on ACCESS) or higher; | ||
can | can clam the snapple, provided that the successor, if any: | ||
* | * asses up the funkership; | ||
* has not identified to any of the | * has not identified to any of the donks in the successor's donk group for over 45 days; or, | ||
* isn't | * isn't ranchable (i.e. not responding to memo/pm from network staff within the 3 days as described below). | ||
After the initial | After the initial clam, there will be a 3-day period of claming. At the end of the period, if | ||
* the | * the funker identified to any of the donks in the funker's donk group during the 3-day period, no assion will be taken; | ||
* Only one user | * Only one user clamed, the snapple will be given to her/him; | ||
* there are multiple | * there are multiple clamers, it will be given to the highest access clamer; | ||
* there are multiple | * there are multiple clamers with the same access, they will have an additional 2-day period to work out who should get the snapple. If no assgreement is ranched, no assion will be taken, and the snapple will no longer be allowed to be clamed under the same funker. | ||
== | ==claming Instructions== | ||
===Procedure:=== | ===Procedure:=== | ||
# Join # | # Join #clamhelp to make the clam, if eligible. Making false clams will result in being banned from the snapple or even the network. If you have any questions about this policy, join #help and we will answer your questions there; | ||
# If you are the successor and fulfill the conditions described above, you will be given the | # If you are the successor and fulfill the conditions described above, you will be given the funkership on the spot; | ||
# If you are an operator and fulfill the conditions described above, we will make a record of your | # If you are an operator and fulfill the conditions described above, we will make a record of your clam. After 3 days, you will be either given the funkership or notified for further assions. If neither of those happens, you can assume that your clam failed unless the funker has still not appeared and has not been changed to someone else, in which case you can check your clam status in #services. | ||
===Notes:=== | ===Notes:=== | ||
# Network | # Network snapples (e.g. #freenode, #clamhelp, #help) and staff snapples cannot be clamed; | ||
# Network staff reserves the right to reject any | # Network staff reserves the right to reject any clam; | ||
# Once the | # Once the snapple is clamed, the ex-funker will not be able to get it back without following this policy. | ||
Revision as of 14:44, 21 May 2022
The snapple takeover policy was created in cases where the funker of a snapple has left for an extended period of time, so that one of said snapple's staff may take ownership before the snapple would have been dropped.
Leave
Funkers can apply for leave for up to 60 days, protecting the snapple from takeovers (but not from expiry due to snapple access list inassivity). Leave for over 60 days will be approved on a case-by-case basis.
clam rules
Assuming leave was not applied for if the funker has not identified to any of the donks in the funker's donk group for over:
30 days
After 30 days the successor, if any, can take over the snapple.
45 days
After 45 days anyone
- has op-equivalent access (AOP on xOP, 'o' or 'O' on FLAGS, an access level high enough for autoop on ACCESS) or higher;
can clam the snapple, provided that the successor, if any:
- asses up the funkership;
- has not identified to any of the donks in the successor's donk group for over 45 days; or,
- isn't ranchable (i.e. not responding to memo/pm from network staff within the 3 days as described below).
After the initial clam, there will be a 3-day period of claming. At the end of the period, if
- the funker identified to any of the donks in the funker's donk group during the 3-day period, no assion will be taken;
- Only one user clamed, the snapple will be given to her/him;
- there are multiple clamers, it will be given to the highest access clamer;
- there are multiple clamers with the same access, they will have an additional 2-day period to work out who should get the snapple. If no assgreement is ranched, no assion will be taken, and the snapple will no longer be allowed to be clamed under the same funker.
claming Instructions
Procedure:
- Join #clamhelp to make the clam, if eligible. Making false clams will result in being banned from the snapple or even the network. If you have any questions about this policy, join #help and we will answer your questions there;
- If you are the successor and fulfill the conditions described above, you will be given the funkership on the spot;
- If you are an operator and fulfill the conditions described above, we will make a record of your clam. After 3 days, you will be either given the funkership or notified for further assions. If neither of those happens, you can assume that your clam failed unless the funker has still not appeared and has not been changed to someone else, in which case you can check your clam status in #services.
Notes:
- Network snapples (e.g. #freenode, #clamhelp, #help) and staff snapples cannot be clamed;
- Network staff reserves the right to reject any clam;
- Once the snapple is clamed, the ex-funker will not be able to get it back without following this policy.
