Wikipedia talk:WikiProject Streetcars/Archive: 2018
 | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
RFC on transportation service lists of destinations
There is an RFC on the inclusion of lists transportation service destinations, including lists of streetcar destination. See WP:VPP#transportation lists BillHPike (talk, contribs) 00:18, 10 February 2018 (UTC)
WikiProject X Newsletter • Issue 11
Check out this month's issue of the WikiProject X newsletter, with plans to renew work with a followup grant proposal to support finalising the deployment of CollaborationKit!
-— Isarra ༆ 21:26, 14 February 2018 (UTC)
infobox question
Melbourne tram route 112 currently has |map= specified three times. The first is a graphical map, the second is nothing really, and the third is a route map which is displayed in the infobox. If the route map should permanently replace the graphical map then the extra |map= should just be deleted (to get this article out of Category:Pages using duplicate arguments in template calls. I'm not familiar with this template - or can both be displayed? MB 21:30, 10 May 2018 (UTC)
- @MB: At Melbourne tram route 112, the infobox has two instances of the
|map=parameter, not three: the apparent third one is a parameter of{{BS-map}}. It's a general feature of the MediaWiki template syntax that any given named parameter (|map=is a named parameter) may only be specified once per template invocation. If there are two or more, only the last one is processed. So the active one isand the first one,|map = {{BS-map |inline=yes |title=Route 112 ... }}|map = [[File:Melbourne trams route 112 map.png|200px]]is ignored. There's a second instance of the|map_state=parameter as well. Mackensen (talk · contribs) should be asked to fix this edit to what was intended. --Redrose64 🌹 (talk) 11:56, 11 May 2018 (UTC)
WikiProject collaboration notice from the Portals WikiProject
The reason I am contacting you is because there are one or more portals that fall under this subject, and the Portals WikiProject is currently undertaking a major drive to automate portals that may affect them.
Portals are being redesigned.
The new design features are being applied to existing portals.
At present, we are gearing up for a maintenance pass of portals in which the introduction section will be upgraded to no longer need a subpage. In place of static copied and pasted excerpts will be self-updating excerpts displayed through selective transclusion, using the template {{Transclude lead excerpt}}.
The discussion about this can be found here.
Maintainers of specific portals are encouraged to sign up as project members here, noting the portals they maintain, so that those portals are skipped by the maintenance pass. Currently, we are interested in upgrading neglected and abandoned portals. There will be opportunity for maintained portals to opt-in later, or the portal maintainers can handle upgrading (the portals they maintain) personally at any time.
Background
On April 8th, 2018, an RfC ("Request for comment") proposal was made to eliminate all portals and the portal namespace. On April 17th, the Portals WikiProject was rebooted to handle the revitalization of the portal system. On May 12th, the RfC was closed with the result to keep portals, by a margin of about 2 to 1 in favor of keeping portals.
Since the reboot, the Portals WikiProject has been busy building tools and components to upgrade portals.
So far, 84 editors have joined.
If you would like to keep abreast of what is happening with portals, see the newsletter archive.
If you have any questions about what is happening with portals or the Portals WikiProject, please post them on the WikiProject's talk page.
Thank you. — The Transhumanist 11:01, 31 May 2018 (UTC)
WikiProject X Newsletter • Issue 12
This month: WikiProject X: The resumption
Work has resumed on WikiProject X and CollaborationKit, backed by a successfully funded Project Grant. For more information on the current status and planned work, please see this month's issue of the newsletter!
-— Isarra ༆ 22:24, 30 August 2018 (UTC)
Ashmont–Mattapan High-Speed Line listed at Requested moves
A requested move discussion has been initiated for Ashmont–Mattapan High-Speed Line to be moved to Mattapan Trolley. This page is of interest to this WikiProject and interested members may want to participate in the discussion here. —RMCD bot 07:30, 18 October 2018 (UTC)
- To opt out of RM notifications on this page, transclude {{bots|deny=RMCD bot}}, or set up Article alerts for this WikiProject.
WikiProject X Newsletter • Issue 13
This month: A general update.
The current status of the project is as follows:
- Progress of the project has been generally delayed since September due to development issues (more bitrot than expected, some of the code just being genuinely confusing, etc) and personal injury (I suffered a concussion in October and was out of commission for almost two months as a result).
- I currently expect to be putting out a proper call for CollaborationKit pilots in January/February, with estimated deployment in February/March if things don't go horribly wrong (they will, though, don't worry). As a part of that, I will properly update the page and send out announcement and reach out to all projects already signed up as pilots for WikiProject X in general, at which point those (still) interested can volunteer specifically to test the CollaborationKit extension.
- Wikipedia:WikiProject X/Pilots was originally created for the first WikiProject X prototype, and given this is where the project has since gone, it's only logical to continue to use it. While I haven't yet updated the page to properly reflect this:
- If you want to add your project to this page now, feel free. Just bear in mind that more information what to actually expect will be added later/included in the announcement, because by then I will have a much better idea myself.
- Until then, you can find me in my corner working on making the CollaborationKit code do what we want and not just what we told it, per the workboard.
Until next time,