StarWars Namespace

Should a separate thread be made to vote on the issue?

I think that would be best.

As to the original question, I believe that should be tabled for now, since it's bringing up a larger issue.

Link it, for reference, then. I did digging and couldn't find it.

I'll also ask for proof, although this is one of those things has been brought up and died out multiple times; there may have been a crowner that never got hooked or something like that.

Discussion starts on page 2 of this thread. While there was no crowner, consensus in the thread was virtually unanimous.

According to the "Rules and Procedures" section of the OP of that thread,

• If there is significant immediate consensus, we'll approve it and any required actions (cleanup, transplants) can begin.

It seems to me that procedure has been satisfied, unless someone would like to actually make an argument against moving pages from the Disney namespace to standard namespaces. If anyone's done that, I haven't seen it.

Edited by HighCrate on Dec 27th 2019 at 10:22:14 AM

Assuming the discussion didn't resume after I left the thread, there were all of two people for and none (actively) against. That isn't consensus.

Edited by RallyBot2 on Dec 27th 2019 at 1:40:59 PM

There was no opposition to the proposal. While we could have discussed it further, that wasn't the intended focus of the topic, so we did not dwell on it. I would ask what functional purpose violating our media namespace rules serves in this case.

The Disney/ namespace pre-dates 2017 by quite a looong bit. This is a discussion from early 2012 about why the namespace exists.

Anyhow, that rationale for the existence of the Disney/ namespace does not justify a creation of StarWars/ as a namespace, as Star Wars uses unique titles that don't really duplicate other things.

In any case, should this discussion be continued elsewhere, as it's veered off the original topic?

It also doesn't justify maintaining Disney as a separate namespace, since we have better and more consistent ways of dealing with page title collisions now.

It's one thing to say, "Well, we've had it for a long time and nobody's bothered to do the work of standardizing it with the rest of the wiki." But right now we have a couple people who seem willing to do the work, and nobody's made a compelling argument for why they shouldn't be allowed to do the work, so what say we just... get out of their way and let them do the work?

I personally don't like how Star Wars films just use the the episodic titles, yet the shows have the franchise name in front of them ( sans The Mandalorian), so having a special namespace could clear up some franchise-ambiguity.

That seems like a rather drastic solution to a rather benign problem. You're talking about making the way we handle the Star Wars franchise inconsistent with the way we handle the vast majority of the rest of the wiki (minus a couple franchises that have been grandfather-claused largely because no one's gotten around to fixing them until recently).

Edited by HighCrate on Dec 28th 2019 at 8:40:43 AM

These extra namespaces also are going to make the later update harder. The biggest issue at the time was actually fixing where everything was, which people are willing to do the work, eliminating the problem.

I don't feel it being inconsistent is a good idea. I'm for nuking these franchise-based namespaces. We have a working design right now that's feasible. Incidentally, not all community decisions mesh well with a website design.

Just my two cents, though they might be a bit late.

Well said. Agreed on all points.

Since it's a major change, might as well crowner it just to be "official", but I think we all know which way this will go.

It's far too soon to assume a result.

It is probably long past time to move this conversation over to the proper thread.

Edited by HighCrate on Dec 28th 2019 at 7:48:17 AM

Should this thread be closed?

Yep.