This template is within the scope ofWikiProject Science Fiction, a collaborative effort to improve the coverage ofscience fiction on Wikipedia. If you would like to participate, please visit the project page, where you can jointhe discussion and see a list of open tasks.Science FictionWikipedia:WikiProject Science FictionTemplate:WikiProject Science Fictionscience fiction
Please do not add more people to the influential section until we come to a consensus at the above discussion. We don't want it to become bloated with links to people who are not accepted as influential via broad consensus. ···日本穣 ·投稿 ·Talk to Nihonjoe ·Join WP Japan!15:44, 1 August 2016 (UTC)[reply]
That wasn't so much a discussion as a four or five people talking in an echo chamber.WP:SURPRISE isn't even a guideline, either. And I think you are applyingWP:EGG too strictly. I don't think anyone will be made uncomfortable by finding themselves in a category. I find that totally absurd. What I do find obnoxious is yourownership tendencies on this template. You blast in here and refuse to engage in any discussion, instead making changes and refusing to allow anyone to dispute them or revert them. ···日本穣 ·投稿 ·Talk to Nihonjoe ·Join WP Japan!18:24, 8 December 2016 (UTC)[reply]
Hmm, you shouldn't throwWP:OWN around like that, when I could easily accuse you of the same thing. Category eggs have been discussed by experienced editors at the talk page of the guideline as demonstrated above. No better forum for the discussion than that. Also note, perWP:NAVBOX,Navigation templates are a grouping of links used in multiple relatedarticles to facilitate navigation between thosearticles within English Wikipedia. Category pages are not articles, and we shouldn't be directing readers out of mainspace. Exceptions could be made if the links are explicit, although personally, I am against this. --Rob Sinden (talk)09:04, 9 December 2016 (UTC)[reply]
Thisedit request has been answered. Set the|answered= parameter tono to reactivate your request.
I've noticed the link to "jump drive" is currently a usb flash drive, with other redirects for jump drive otherwise linking to the page hyperspace anyway.I suggest removing the link for jump drive, as making it a redirect would only link to the page immediately next to it.Erfly (talk)00:11, 19 February 2020 (UTC)[reply]
Thisedit request has been answered. Set the|answered= parameter tono to reactivate your request.
The embedded template added inthis edit should be reverted, as this is not the correct way to use navboxes. If this really needs to be done, then a simple merge would have been the correct procedure. It seemsJonesey95 already has expressed issues with this edit.212.135.65.247 (talk)10:30, 4 March 2020 (UTC)[reply]
A simple merge will not do, because the embedded template may be used independently, and merging will create maintenance problems commonly associated withWP:FORK.Staszek Lem (talk)21:10, 4 March 2020 (UTC)[reply]
A navbox should be transcluded on all included articles. If it is worthy for inclusion here, then this navbox belongs on that page, not a subset of those articles. i.e. itshouldn't be used independently. Therefore a merge would facilitate that. In any caseWP:BRD needs this to be reversed.212.135.65.247 (talk)08:55, 5 March 2020 (UTC)[reply]
Why shouldn't? There is no reason to drag a huge scifi navbox into all scifi articles. Some of them have a limited sub-scope., with narrower navigation range. And nothing should be reversed without the conclusion of the discussion. My transclusion added missing items into the template. If one reverts, they must re-add information. Otherwise the act will be non-constructive.Staszek Lem (talk)17:00, 5 March 2020 (UTC)[reply]
The correct way to handle this is either a full merge or distinct templates. We shouldn't be embedding navboxes into navboxes in this manner.212.135.65.247 (talk)12:10, 6 March 2020 (UTC)[reply]
This page is the subject ofa current discussion. Please feel free to join in. While you maybe bold in editing this page, it would be a good idea to check the discussion first.
