Requests for Comment/Changes to the Dormancy Policy

The Dormancy Policy has been around since the beginning of 2016, and since then things have changed in the way that we implement it, so therefore we need to update the policy accordingly. You may vote for multiple proposals (since they are not necessarily mutually exclusive).

Proposal 1

 * The current time periods for inactivity, closure and deletion remain the same as currently, with the only change being to the wording of the policy, as these things are now done automatically and not by "global staff".

a) Support

 * 1)  I am perfectly happy with the way these times are at the moment. They are lenient and allow for prolonged periods of inactivity. This has so far prevented my wiki (and others) from getting deleted before I got a bout of energy and activity again. --21:11, 3 May 2019 (UTC)

d) Comments
A global comment up front: These proposals are fine for getting a "sense of the community," but they contemplate making edits to a Miraheze policy document, and seeing the actual edits would forestall complaints along the lines of, "This isn't what we voted for!" The following proposal suggests that policy changes will occur "after the closure of this RfC", suggesting that there is no follow-on vote on the wording. The current proposal especially is problematic: We are asked to endorse mere "change[s] to the wording of the policy" without seeing what the changes are. 19:48 3-May-2019

Proposal 2

 * The "Wikis with no contributions" clause of the policy is removed from the Dormancy Policy and will no longer be applicable after the closure of this RfC. (This clause has not been used so far)

a) Support

 * 1)  As it is indicated above, has not been used. Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)
 * 2)  6 months total for a regular deletion seem fine enough to handle hypothetical 0 contribs cases since those wouldn't really waste much resources.--Wedhro (talk) 19:27, 3 May 2019 (UTC)
 * 3)  A wiki with 0 contributions is not "dormant" but "unbegun".  Using wmftools suggests that a large number of requests for wikis are abandoned soon after, by newbies who didn't understand the magnitude of work involved in making it look serious.  My support assumes there is some way to clear these away; it doesn't have to be in the Dormancy Policy.   19:51 3-May-2019
 * 4)  It would seem to me that removing the text from the dormancy policy will simplify the policy. Simpler is best IMHO. --Fritigern (talk) 21:11, 3 May 2019 (UTC)

Proposal 1

 * The rules for exemptions remain the same as they are

a) Support

 * 1)  If they are changed then some events (e.g. elections, Olympics, etc.) will have to request more regularly than their period of activity. Equally wikis that will never go out of date and have large traffic numbers but low edit counts (e.g. a hypertext variant of the D&D 3e SRD) will end up being closed soon after creation. ~ El Komodos Drago (talk to me) 18:16, 3 May 2019 (UTC)

d) Comments

 * I manage Rfobasic wiki, an incomplete manual for an Android APK whose original authors have walked away from it. It was fun but further development will wait until someone asks for it, which might be never.  Even so, what's there is useful for reference.  I currently enjoy an exemption from Dormancy.  If stewards contacted me annually or less often to check, that wouldn't be burdensome.  I don't know what the right interval is.   19:56 3-May-2019

A problem I see with all the other options is that a bureaucrat is needed to keep the exemption but it's perfectly possible for a wiki to have no active bureaucrats. What happens if there's still users interested in keeping the wiki online but they're just regular users?--Wedhro (talk) 21:04, 3 May 2019 (UTC)

Proposal 2

 * Exemptions are no longer infinite, and will expire after a time period of 1 year starting with when the exemption was requested. After this time period, bureaucrats of a wiki are contacted by sysadmins, and they have a chance to renew their exemption. If they do not respond to the request in 30 days after the message by sysadmins, the wiki is removed from the exemption list and will be normally affected by the Dormancy Policy starting when the exemption is removed.

a) Support

 * 1)  Averak (talk) 17:58, 3 May 2019 (UTC)

Proposal 3

 * Exemptions are no longer infinite, and will expire after a time period of 2 years starting with when the exemption was requested. After this time period, bureaucrats of a wiki are contacted by sysadmins, and they have a chance to renew their exemption. If they do not respond to the request in 30 days after the message by sysadmins, the wiki is removed from the exemption list and will be normally affected by the Dormancy Policy starting when the exemption is removed.

a) Support

 * 1)  Having to renew the exemptions assures that the wiki is still needed by bureaucrats, rather than allowing anyone to request exemptions and then never need their wiki again. Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)

Proposal 4

 * Exemptions are no longer infinite, and will expire after a time period of 3 years starting with when the exemption was requested. After this time period, bureaucrats of a wiki are contacted by sysadmins, and they have a chance to renew their exemption. If they do not respond to the request in 60 days after the message by sysadmins, the wiki is removed from the exemption list and will be normally affected by the Dormancy Policy starting when the exemption is removed.

Proposal 1

 * A wiki will be eligible under the adoption policy 7 days after it has been closed.

Proposal 2

 * A wiki will be eligible under the adoption policy 14 days after it has been closed.

a) Support

 * 1)  Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)
 * 2)  --Wedhro (talk) 19:43, 3 May 2019 (UTC)

Proposal 3

 * The user requesting adoption must have shown activity on the wiki prior to it's closure.

Proposal 4

 * The user requesting adoption must have shown activity on another Miraheze wiki.

a) Support

 * 1)  This rule will ensure that the wiki would be in the hands of someone who at least knows how to edit articles. --Fritigern (talk) 21:11, 3 May 2019 (UTC)

Proposal 5

 * Staying inline with Miraheze's community centric purpose, adoption is solely the request for a wiki to be re-opened by anyone not holding "managewiki" locally on the wiki. Users must submit a local request to gain permissions which will be handled by a steward in line with standard practise (applying this pages' notes critera).

a) Support

 * 1)  Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)
 * 2)  --Wedhro (talk) 20:56, 3 May 2019 (UTC)

d) Comments
I don't see why anyone can open a wiki and automatically get bureaucrat/sysop status, no questions asked, but if someone adopts a dead wiki he has to get steward's approval. --Wedhro (talk) 19:42, 3 May 2019 (UTC)


 * Well, because a dead wiki has content, albeit no active users. It is fine that stewards generally defer to the wiki's community, but in the case that there is none, there is no reason for stewards not to approve.


 * Should it be stated that stewards take a snapshot of the wiki before handing it over, in case the old-timers reappear and agree that the new bureaucrat has made a mess of things?  20:00 3-May-2019


 * To me it looks like this should be handled case-by-case because there's also wikis with little to no content, so not giving away right automatically it's the closest option.--Wedhro (talk) 20:55, 3 May 2019 (UTC)

Proposal 6

 * Upon adoption, users will be given sysop and bureaucrat rights on the wiki by a Steward.

a) Support

 * 1)  When a user adopts a wiki, they should have the same rights on that wiki as when they had requested and been granted a wiki. --Fritigern (talk) 21:11, 3 May 2019 (UTC)

b) Oppose

 * 1)  I don't think rights should given before the user really demonstrates a need for said rights, and therefore I support proposal 5 for that. Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)

Proposal 1

 * After 6 months total following inactivity and closure notices, a wiki is marked as deleted. For 7 days following that, users have the chance to reinstate their wiki again by contacting sysadmins. If after that time there is no request, the wiki is eligible to be deleted by sysadmins permanently.

Proposal 2

 * After 6 months total following inactivity and closure notices, a wiki is marked as deleted. For 14 days following that, users have the chance to reinstate their wiki again by contacting sysadmins. If after that time there is no request, the wiki is eligible to be deleted by sysadmins permanently.

a) Support

 * 1)  Reception123  (talk) ('C' ) 17:04, 3 May 2019 (UTC)
 * 2)  --Wedhro (talk) 19:38, 3 May 2019 (UTC)
 * 3)  IMO, after 6 months of notices, 14 days is a much more realistic time period before final deletion --Fritigern (talk) 21:11, 3 May 2019 (UTC)

d) Comments
I have no divine wisdom to support 14 days and oppose 7 days, especially as this is a waiting period at the end of a waiting period (which sounds like what I went through to change my user name).

I presume a "closed wiki" is one that is still on-line but has been rendered un-retrievable, while a "deleted wiki" is one that is physically deleted (or precisely, according to Dormancy Policy, deleted at stewards' option, such as whenever they need the space). Is there a way to save the information for eventual recovery (like "writing it to the mag-tapes")?

Shouldn't Dormancy Policy mention that an RfC on it is active? 20:07 3-May-2019
 * A closed wiki is one which remains online but is not changeable except by those with "managewiki" permissions. A wiki "marked as deleted" is a wiki which appears as to not exist (produces a 404). A deleted wiki is one where the live copy is gone but information may or may not exist in backups. There is a way to store data but as an open source, donation funded project - we have no gains from storing the data, nor realistically the want to invest money in long term data storage when we are constantly fighting for funds to sustain live data storage. John (talk) 20:19, 3 May 2019 (UTC)