Requests for Comment/Changes to the Content Policy

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Withdrawn. The support votes on the first section and it's activity makes me think that this is not suitable for an RfC. Fungster ^{(contribs - email - CA)} 08:29, 1 July 2019 (UTC)

---

I propose a big change about the content policy. One things is, the policy not not that strict, and therefore some wikis have been either deleted or have been marked private (see proof here). This shows that the Content Policy is incomplete in managing wikis. Fungster ^{(contribs - email - CA)} 08:19, 29 June 2019 (UTC)

Scope

General

Proposal 1

Leave everything as it is.

Support

•  Support With no other proposals. John (talk) 10:02, 29 June 2019 (UTC)
•  Support and am opposed to any other proposals below unless otherwise noted.--開拓者 (The Pioneer) (^talk/_contribs | global🌎) 13:45, 30 June 2019 (UTC)
•  Support I think the same as 開拓者. --Dark Dragoon (talk) 22:08, 30 June 2019 (UTC)

Oppose

•  Strongest oppose Something needs to be changed at least. See my proposals below. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 2

The "Miraheze is permitted to re-distribute your content" section is removed from the policy.

Support

•  Weak support I actually think that the wiki needs to be simplified but more strict. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Oppose

•  Oppose If this is removed, Miraheze can not legally host any content not licensed under public domain or CC, which will exclude certain wikis, non-free images, and private/organisations and university content (of which the latter 2 have been our largest donators and contributors to the growth of Miraheze). John (talk) 10:02, 29 June 2019 (UTC)
•  Strongest oppose per John Zppix (Meta | CVT Member | talk to me) 16:48, 30 June 2019 (UTC)

Hosting

Proposal 1

Leave everything as it is.

Oppose

•  Strongest oppose Something needs to be changed. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 2

Make the first section about not allowing ad wikis to be hosted on Miraheze more restrictive such as "Wikis used for advertising will be deleted as soon as they are discovered, and using a third party advertising network is solely prohibited on Miraheze."

Support

•  Strongest support This policy is outdated. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 3

Wikis about harassment and/or vandalism will be immediately deleted without request from a witness or without prior notice.

Oppose

•  Oppose It is best to wait for the founder to make improvements to the wiki first. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 4

Wikis that have illegal content will be suspended immediately as they are discovered.

Support

•  Support Already current practise. John (talk) 10:02, 29 June 2019 (UTC)

Oppose

•  Oppose It's better to do it later if the wiki problem persists. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 5

If a wiki hosted by Miraheze violates the Content Policy, it shall only however be deleted only at the request of Stewards and the discretion of System administrators.

Support

•  Strong support Probably the best option. Not immediate, but only at the request of stewards. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Oppose

•  Oppose On both the grounds I don't support immediate deletion and that Stewards are able and in fact encouraged to delete wikis over sysadmins. John (talk) 10:02, 29 June 2019 (UTC)

Deletion of wikis

Proposal 1

After a wiki is found to be violating the Content Policy, it will be deleted immediately.

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. John (talk) 10:02, 29 June 2019 (UTC)
•  Oppose Not immediate deletion. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 2

After a wiki is found to be violating the Content Policy, it will be deleted after 7 days.

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. John (talk) 10:02, 29 June 2019 (UTC)
•  Strong oppose Too short. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 3

After a wiki is found to be violating the Content Policy, it will be deleted after 14 days.

Support

•  Strongly support This is the only option.

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. John (talk) 10:02, 29 June 2019 (UTC)

Proposal 4

Per the Dormancy Policy, wikis that are violating the Content Policy will not be deleted immediately, but will be closed if the wiki itself is already inactive.

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. Plus closing a wiki defeats the purpose of having a wiki potentially becoming compliant. John (talk) 10:02, 29 June 2019 (UTC)
•  Oppose per @John. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Proposal 5

Wikis that are found to be violating the Content Policy should have a Steward contact the lead wiki bureaucrat to discuss improvements to the wiki. If the lead crat does not adhere to the Steward's guideline then the wiki should be deleted within 7 days.

Support

•  Support although 14 days is a better option. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. (Oppose per the deletion part) John (talk) 10:02, 29 June 2019 (UTC)

Restoration of wikis

Proposal 1

If the wiki bureaucrat states that the offending wiki is not against the Content Policy, but the wiki itself is deleted, Sysadmins may hold a discussion or a vote where all community members of that deleted wiki will make and state their opinions.

Support

•  Support Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Oppose

•  Oppose I find a flaw in the logic, if the wiki doesn't believe it's violating the policy, why should sysadmins hold a vote with the wiki to clarify if they're breaking the policy they've already said they're not? John (talk) 10:02, 29 June 2019 (UTC)

Proposal 2

Wikis that are found to be violating the Content Policy may not be restored under any condition.

Support

•  Strongest support This makes sense, and not other votes matter. Fungster ^{(contribs - email - CA)} 11:24, 29 June 2019 (UTC)

Oppose

•  Oppose No, Miraheze should operate the "in good standing" model. John (talk) 10:02, 29 June 2019 (UTC)

My opinion

I think that the Content Policy is outdated following the closure of Horrid Reception Wikis Wiki. That means that the Content Policy needs to be more strict and stately. Fungster ^{(contribs - email - CA)} 08:19, 29 June 2019 (UTC)

For reference, the Horrid Reception Wiki wasn't closed under the Content Policy, it was handled under the Terms of Use directly I believe. John (talk) 10:02, 29 June 2019 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section