Page MenuHomeMiraheze

Add fields to Special:RequestWiki in order to have more details
Open, Stalled, LowPublic

Description

Since Miraheze first started in 2015, standards for creating a wiki have increased gradually. While before a short description may have worked wiki creators now ask for more details to make sure that the wiki will comply with the Content Policy. The issue with the current system is that there's only one description field and wiki creators frequently have to ask for more information. I propose that we add additional fields in order to get more information from the start. While other fields could also be relevant I think what would be useful would be:

  • A field that asks whether this is a wiki migration or whether it is a new wiki
  • IF migration: follow up questions (link to original wiki, estimated number of users, etc.)
  • IF new wiki: question about how the user plans on forming/attracting a community (if not a personal wiki)

Further ideas are welcome but the main idea here is to gather more information. Another purpose is also to try to reduce the number of "ghost wikis" (wikis that are never edited/abandoned from the start). While we can't know for sure my guess is that this happens because users have a spontaneous idea but then realise that creating a wiki is harder than they thought. By asking them how they plan on forming or attracting a community or viewership this might get them to think about the more practical issues behind their idea and maybe reconsider.

Event Timeline

Reception123 created this task.

I'd assume that this would go in here https://github.com/miraheze/CreateWiki/blob/1f993cc82cc9b1649d195ac614e962bc19f1add7/includes/RequestWiki/SpecialRequestWiki.php

If I'm right about that, I can try to write at least an initial version of something like this for T10931#220644 when I have some spare time (should have this week).

I'd assume that this would go in here https://github.com/miraheze/CreateWiki/blob/1f993cc82cc9b1649d195ac614e962bc19f1add7/includes/RequestWiki/SpecialRequestWiki.php

If I'm right about that, I can try to write at least an initial version of something like this for T10931#220644 when I have some spare time (should have this week).

Yes, that is correct. You also need to send the selections and user input (such as their number of users, link, etc) to the request database, and then retrieve it on the view page for requests.

I'm working on this, though it'll take me a few days before I actually publish a PR (I'm developing code incrementally off-site).

Unfortunately my RL is becoming exceptionally busy to the point that I don't think I'll have the time to actually finish this. Whoever ultimately picks this up, if you want any part of the code that I had partially developed, please contact me.

Unfortunately my RL is becoming exceptionally busy to the point that I don't think I'll have the time to actually finish this. Whoever ultimately picks this up, if you want any part of the code that I had partially developed, please contact me.

I was going to pick this up the other day, but thought against it since you were already working on it. If you want to shoot me what you've already written on Discord (or any other avenue), I'm in the Miraheze Discord.

Original_Authority changed the task status from Open to Stalled.Oct 10 2023, 18:19

PR https://github.com/miraheze/CreateWiki/pull/447, potentially stalled waiting on a member of SRE to review — perhaps this can be pushed to betaheze?

I've added the patches and this should now be ready for SRE review per this change.

It has the basics (migration or not, migration source, and the number of users on the original wiki).

@Agent_Isai is there plans to bring over the changes WikiTide made to S:RW for this?

@Agent_Isai is there plans to bring over the changes WikiTide made to S:RW for this?

There are. I was going to but @Universal_Omega said he wanted to backport some changes from WikiForgeMagic which would make RequestWiki highly more modular and wouldn't require needing changes to the schema of cw_requests so this is stalled pending that.