Forum:Merging with the Customized Sims Wiki

From The Sims Wiki, a collaborative database for The Sims series
Jump to navigation Jump to search
Forums: IndexCommunity discussionsMerging with the Customized Sims Wiki | Forum new.gif Post

First off, if you're reading this, welcome to Miraheze! This is the first discussion thread started on the Miraheze wiki, funnily enough before the migration was ever officially announced.

Anyways, I've messaged Jawusa and M.M.A.A., some of the founders of the The Customized Sims Wiki, and they both are on board with the idea of merging with The Sims Wiki on Miraheze. This move will help resolve the long-standing problem they've had with lacking support from experienced editors and having no access to our library of templates, and will hopefully restimulate the custom content creation community's interest in having a wiki to document their work.

Actually migrating the pages should not require too much work, as there aren't a lot of pages on the TCSW. There are, however, some questions that will probably need to be discussed:

  1. Where should their pages be moved to? I have considered creating a new, custom namespace on the wiki for custom content. One issue raised on this thread is that we don't really have a suitable namespace for their content. We don't generally allow custom content in the mainspace (with some exceptions) and "Fanon" doesn't really fit their needs, as they're not really creating "fan fiction" content, but rather have standards similar to our article space but for custom content. Wikia allows for custom namespaces, but it requires an annoying level of bureaucracy to go through; Miraheze, on the other hand, lets us create as many namespaces as we want with a simple-to-use interface. In terms of naming this new namespace, I've thought about naming them Custom content or Custom. This means that a page on Widespot would be located at Custom content:Widespot or Custom:Widespot. I think the new namespace approach works best, so the main question is whether or not we should use Custom content or Custom as the namespace name. Custom content works, but I fear it's too long, while Custom may be too short.
  2. What are the policies surrounding the creation of custom content pages? As far as I can tell, there are no policy pages on the Customized Sims Wiki, so we'll need to have a discussion on what should be allowed (and not allowed) in the custom content namespace here. Some questions that may be worth asking include:
    • What, if any, requirements should the custom content have before an article can be created for it on the wiki? Should there be a notability guideline that needs to be met for a work of custom content to be considered notable enough for an article here? (I was thinking at the very least that the custom content should be publicly accessible, or at least, downloadable from somewhere)
    • How should custom neighborhoods/worlds be organized? The TCSW was created primarily to document Sims and lots in entire custom neighborhoods/worlds. Per the nature of a wiki, anybody can edit these pages, and anyone can create new ones. How will we handle naming conflicts? For instance, if a Sim named John Doe existed in Neighborhood X, and then some time later Neighborhood Y was released by a different creator that also had a Sim by the name John Doe, how will naming conflicts be handled? (I was thinking doing as we do in the fanon namespace already: turning "John Doe" into a disambiguation page and then creating "John Doe (Neighborhood X)" and "John Doe (Neighborhood Y)" to separate things.
  3. As mentioned earlier, we do have some articles on custom content in the mainspace, like the InSimenator and the FFS Lot Debugger. These were created due to their high use and notability. What should be done with such articles? (I was thinking moving them into the custom content namespace for consistency's sake) We also have articles on notable creators, like Mootilda. What should be done with those articles? (I'm a bit hesitant on this one, since our article on Delphy, founder of Mod The Sims, most certainly would look out of place in the custom content namespace)
  4. What should happen with the old wiki? Since the TCSW is a much smaller wiki, there might be the possibility that Wikia won't even notice if we were to post links on their site pointing to the migrated wiki. I don't know how much traffic the wiki gets on a regular basis, however.

Thoughts? —k6ka 🍁 (Talk · Contributions) 18:31, 8 April 2019 (UTC)

April 12, 2019: I've begun importing the pages from their wiki into here. I haven't created the new namespace yet while it's still being discussed. In the meantime, they are being kept as subpages of The Sims Wiki:The Customized Sims Wiki, and are listed here. When the namespace is created, they will all be moved to their proper locations. —k6ka 🍁 (Talk · Contributions) 19:37, 12 April 2019 (UTC)

April 13, 2019: All files and images from the Customized Sims Wiki have been uploaded here, and I've also done my best to resolve any name conflicts. —k6ka 🍁 (Talk · Contributions) 21:22, 13 April 2019 (UTC)

April 30, 2019: The Custom content namespace has been created, and CC and Custom redirect to it. We can begin moving pages to this new namespace, and start editing our templates to recognize this new namespace. —k6ka 🍁 (Talk · Contributions) 01:23, 30 April 2019 (UTC)

Discussion[edit source]

In regards to the above-mentioned questions:

1. Where should their pages be moved to? - I'd say Custom is a good generic name for such a namespace.

2. What are the policies surrounding the creation of custom content pages? - Without diving too in-depth into specifics, I'd say that pages should: only be about projects that are available for download to the public at large; meet some minimum standard of notability (not sure what that'd look like, but I don't think we want pages on every Tom, Dick and Harry's custom recreation of Veronaville clogging up the wiki); be open to contributions from all people, not just the custom content creator(s); be written in an encyclopedic manner, not merely as a storytelling vehicle (bearing in mind that if the particular Sim/family/neighborhood had a background story attached to it, such a story could be included in the article). If the intent is to keep Fanon, then we'd also need to formally distinguish between the two types of content.

3. What should be done with [existing custom content articles]? - I think pages about CC creators should remain in the main namespace as encyclopedic entries about a specific person as opposed to a creation of theirs. I'd also lean in the direction of keeping pages about third-party utilities, like package editor programs, in the main namespace. I think game mods generally speaking would fall under Custom.

4. What should happen with the old wiki? - Assuming that the original wiki editors would support a merge, I'd suggest simply abandoning it, maybe trying to sneak in links directing to the new site. If CSW were merging into the Wikia TSW, I'd say it would be possible to contact staff and have them merge directly (with support of the original wiki creators) and there's a decent chance they would approve it. But if staff knew that we were trying to close it down in order to redirect off Wikia, there's no way they'd approve it.

-- LiR (talk) 19:11, 11 April 2019 (UTC)

I might as well say a few things on this situation. So, I think the better name for the namespace could be "Custom content". I really feel like "Custom" is way too generic and just... weird. "Custom content" is pretty much what everyone (or at least the majority) of simmers refer the type of content that this new namespace would include. "Custom content portal" sounds better than "Custom portal", and "Custom" in general feels a bit too generic, I guess. Another name could be "Modification", but I feel like many people may seem that name as for gameplay mods only and not for custom clothing and stuff.

And talking about that, I feel like these should be the basic policies regarding what custom content pages include and don't include.

What CC pages do include
  • Gameplay mods, which affect the gameplay and mechanics of a game. An example could be a life state mod, or something that gives much more gameplay options such MCCC for TS4.
  • Special objects. And by this I mean singular objects such as InSimenator and the FFS Lot Debugger like k6ka mentioned. Those articles should be moved from the main namespace to this new one.
What CC pages don't include
  • Sims, families, neighborhoods/worlds, pets, lots etc. All of those pages should be moved under fanon and go under the policies of that namespace.
  • CC creators. They shall stay in the main namespace.
  • Other external programs such as package editors or mod creation tools.
  • Mods that only fix bugs. I really think we don't need those, unless they are very impactful.

However, I currently have no idea on how to handle decorative CC. CC that doesn't give any gameplay. This would be CC clothing, hair, accessories, objects etc. Obviously we wouldn't be creating independent articles for CC hair or something, but I did think about of having CC articles that include a "list" of CC (e.g. "Custom content:<mod creator>'s clothing") but then I thought... shouldn't we just include decorative CC under mod creator articles in the main namespace? I don't know.

In terms of notability, mods that only fix bugs shouldn't be included, like I said a bit earlier. In terms of very small mods, like a power outage mod or something, they could work as long as they have some form of depth. However, I think a mod that removes a single moodlet wouldn't work though. Cleanup, stub and other basic maintenance templates should be created for CC articles, and pretty much have the same rules.

I also think CC articles shouldn't be "owned" by someone like the fanon pages. The creator(s) of the mod could be listed in an infobox and generally in the article, but they should be open for anyone to edit the same way main namespace articles currently are. And since CC pages couldn't be owned by someone, the Sim, family, neighborhood/world, pet and lot pages would be moved to the fanon namespace.

But yeah, "Custom content" is the name I would go for since it's the most easily noticeable one, I guess. - SimDestroyer (talk) 13:58, 16 April 2019 (UTC)

@SimDestroyer: I don't think moving Sims, families, neighborhoods, pets, lots, etc. into the fanon namespace would help. If you look at the pages The Customized Sims Wiki has, many of them are actually Sim articles for Sims in custom worlds. I think one of the reasons why The Customized Sims Wiki didn't use our fanon namespace initially is that what they were doing wasn't really "fanon". We can define "fanon" as "fan fiction", so I'd use that namespace for Sims that I have created for my storytelling purposes. There is no expectation that my Sims or neighborhoods would be made available for download anywhere. What makes The Customized Sims Wiki different is that it's basically like The Sims Wiki, but covering downloadable custom content rather than fan fiction. As such I don't expect the Custom content namespace to have things like a written story or anything. Moving them into the fanon namespace, in short, is what The Customized Sims Wiki set out not to do. —k6ka 🍁 (Talk · Contributions) 16:21, 16 April 2019 (UTC)

If we do go for "Custom content" to be the namespace, should both words be capitalised, i.e. "Custom Content"? I'm not sure why I prefer the latter option. It could be for aesthetic reasons, although the former option is more consistent with other namespaces, e.g. "MediaWiki talk", "User blog" on Wikia, etc.

Another thought: if we capitalise "Custom Content", then an abbreviated redirect could be "CC:<title>". I feel that if the namespace becomes "Custom content", the abbreviation would have to be "Cc:<title>" and I don't quite like that.

Or maybe I'm spouting nonsense, I don't know. shrugs TheTimMan (talk) 15:40, 16 April 2019 (UTC)

@TheTimMan: Namespaces are not case sensitive, so Tsw:Sandbox and TSW:Sandbox both redirect to the same place. —k6ka 🍁 (Talk · Contributions) 16:21, 16 April 2019 (UTC)