Talk:Scientology protest group celebrates founder's birthday worldwide/Coordination

Suggestion

Wikinews international report: "Anonymous" holds anti-Scientology protests worldwide got cleaned up pretty nicely, but for a while there it was a great big mess, unorganized, with tons of IPs and new editors just sticking in random bits of OR information that may or may not have been true (statistics of how many people were there, etc.) Many of the contributors to that article did not sign up first at the prep page. Suggest semi-protect of that article whenever it starts to become really really active, with editing preference given to established Wikinews reporters who signed up and/or were there in a Wikinews capacity in person, for the March 15, 2008 protests. Cirt - (talk) 19:37, 5 March 2008 (UTC)

I suggest that, in addition to being semi-protected, only users who have signed up here are permitted to make content edits (although they should be encouraged to correct typos). --Anonymous101 Talk 20:17, 5 March 2008 (UTC)

I would support this idea - only I might not be able to report from a protest myself, and would still like to do copyediting to the article when it appears, as well as incorporate info from secondary sources as they appear. Obviously I wouldn't mess with changing the content of OR work, because I wouldn't be able to provide firsthand input to those locations. Cirt - (talk) 20:32, 5 March 2008 (UTC)

Some of the photo gallerys on the first article were a little long. I would suggest limiting gallerys to the best 12 photos (2 lines) and linking to commons if people want to see the rest. (or some fancy dynamic nav for gallery js perhaps, but that doesn't exist yet). Bawolff ☺☻ 00:43, 10 March 2008 (UTC)

That is a very good idea. (12) seems like a good max number per gallery. Cirt - (talk) 06:54, 10 March 2008 (UTC)

Uhhh, twelve? uhhh, crud, I wish I saw this before I uploaded. Look, I just submitted my report on the Seattle event, and I'm a bit on the fried side. Feel free to look through the 37 I submitted, and pick the best twelve. At least I chopped it down to 37 from the 118 I took on site... --RoninBK - (talk) 23:55, 15 March 2008 (UTC)

When article gets transferred to working state, retain alpha sort

Another suggestion, whenever the article gets transferred to a working state, a developing article, it'd be best just to keep the locations in alpha-sort, by country then state/province within each subsection. This way, less work to do later to organize the article, and easier to work on while things are added/ongoing. Cirt - (talk) 19:38, 5 March 2008 (UTC)

Protection and subpages

@Pi zero: Is Scientology protest group celebrates founder's birthday worldwide/Coordination a page for coordination or a prepared story? If its a prepared story, it's too late now, and if its for coordination, why is it still tagged with {{prepared}}. Either way, mainspace doesn't support subpages, so your summary in Special:Diff/4538211 is a bit confusing. Can I suggest moving this to, eg, the Wikinews namespace? Thanks, --DannyS712 (talk) 04:47, 9 January 2020 (UTC)

Done Archived and moved to project space. -Green Giant (talk) 09:36, 9 January 2020 (UTC)

@DannyS712, Green Giant: Hmm. It's part of the preparation of an article that was subsequently published, and I meant to permanently group it with the published article by making it a subpage of the published article. This makes more sense to me than storing a permanently archived page associated with a published article in project space where it looks rather orphaned. I've seen this sort of subpage used for, iirc, several old OR articles in the archives. Subpages are a structural device supported by the software and used here and there on English Wikinews (template documentation, a bit in category space and portal space); they're used rather ubiquitously on English Wikibooks, and I expect to use them more aggressively here (and there, and hopefully elsewhere) in future for semi-automated assistants. What matters administratively, when using subpages in English Wikinews mainspace, is that they aren't published, and that they are fully protected (because, in the long run, we mean everything in mainspace to be fully protected, except for current unpublished articles waiting to be published or deleted). --Pi zero (talk) 12:38, 9 January 2020 (UTC)

@Pi zero: Hmm... I’ve moved it back from project space. However, it is listed under the development category in the Newsroom. I’ve tried noindex but no luck. -Green Giant (talk) 12:48, 9 January 2020 (UTC)

@Green Giant: I'm pretty sure Category:No publish is the tool for that. Btw, reminder: don't sight pages in mainspace that are not themselves actually published articles. --Pi zero (talk) 12:59, 9 January 2020 (UTC)

@Pi zero: my initial point still stands that mainspace here doesn't actually support subpages --DannyS712 (talk) 18:08, 9 January 2020 (UTC)

@DannyS712: I'm not sure what you mean. --Pi zero (talk) 18:10, 9 January 2020 (UTC)

If you look at the coordination page, there is no breadcrumb link to the article, unlike at the top of this page, where there is a link to the article's talk page --DannyS712 (talk) 18:19, 9 January 2020 (UTC)

Interesting. I wonder where that's done, and why it was done. And whether the breadcrumbs are all there is to it, or is there more. Though it still seems to me like a simple way of keeping track of which page is associated with which. Re why, we sometimes use slashes in headlines, of course, but since the same headline isn't plausibly going to exist truncated to just before the first slash, it's not really clear to my why one would bother to suppress the breadcrumbs. As for where, seems it could be in the site config, or there could be a hook somewhere in mediawiki space, or it could be done with CSS. And what else would depend on where and how it's done. --Pi zero (talk) 18:43, 9 January 2020 (UTC)

Its mw:Manual:$wgNamespacesWithSubpages - see mw:Help:Subpages. If we wanted to activate it for mainspace to be able to use it on this page, all other mainspace pages with a / should be renamed. --DannyS712 (talk) 19:56, 9 January 2020 (UTC)

That's not an option, I'd say. Although I don't really understand why it was done in the first place, since it would have (as I said) no effect on any article whose name didn't happen to be a suffix of the name of another article (and the suffix would have to start with a slash). Thanks for finding the info. --Pi zero (talk) 20:02, 9 January 2020 (UTC)

No problem - its trivial to enable in mainspace, but if we aren't going to then, as far as the software is concerned, the coordination page is completely unrelated to the article itself, and thus I return to my suggestion that it be moved out of mainspace --DannyS712 (talk) 20:04, 9 January 2020 (UTC)

I disagree with your characterization of it as unrelated. Afaics the whole "disable subpages in this namespace" thing has only two effects: it suppresses the ancestor links at the top of the page ("breadcrumbs"), and it disables some name-parsing magic words like BASEPAGENAME and SUBPAGENAME. It doesn't affect the #titleparts: magic word, nor Special:PrefixIndex. And here it doesn't change the fact that one page name is, in fact, the other with a suffix /Coordination added. --Pi zero (talk) 20:21, 9 January 2020 (UTC)

I know that they are related; I'm saying that, to the software, they aren't --DannyS712 (talk) 20:31, 9 January 2020 (UTC)

In those two ways I named, the software doesn't acknowledge a relation between them. To the other two software elements I mentioned, the "disable" thing has no effect. And the common-sense relation between the names also shows up in alphabetical orderings. --Pi zero (talk) 20:41, 9 January 2020 (UTC)