- 1 BC Transit 2008 Polars talk on Awesome cheese
- 2 Edits to the Durham Region Transit page
- 3 Going against standardization
- 4 Photo used with permission?
- 5 Deleting build dates and model numbers
- 6 Page typo
- 7 Toronto Transit Commission 4204
- 8 Medicine Hat Transit Vicinity orders' page names
- 9 Edmonton Transit Service Routes
- 10 Publicity photos
- 11 Re: VIN Page Formatting
BC Transit 2008 Polars talk on Awesome cheese
Edits to the Durham Region Transit page
Hi, thanks for the feedback. I have been using the Show preview button before uploading.
Going against standardization
Your edit at 10 March 2012 of page Template:Oakville Transit of removing the apostrophes around the route name has gone against the Naming Convention of Bus Route pages. Seeing as your supporting of "Standardization", I am personally shocked by this move.
I shall quote the exact line:
"The title is to include the transit agency in full, the word 'route' (note no capital 'R' as it is not part of the transit agency name), the route number, and the route name in apostrophes."
Also the reason I choose to have the colors as they were before your edit of 10 March 2012 was going by your Wiki Colour Standards because on the TTC Template, the "Primary colour" is the exterior colour while the "Secondary colour" is the interior. I was keeping the Oakville Template in a set "Standard". I do agree with your reason for edit as it does look better, but I am explaining the reason behind my decision. Your the one after all who demanded standardization, I am trying my best to meet your wishes for Standardization. I have decided voluntarily to follow your standards, even though I will remind you that am not required to do so. I do appreciate the correction for routes 102 and 190 however as I did miss those errors in the preview and would like to Thank you for correcting them.
I also would like it if you would stop stalking my edits and instead spend the time on something more productive, like for example, updating the YRT section, which is in need of a massive update. Or maybe even creating some missing pages, or even helping by adding navigation templates to systems without navigation templates. There are way more productive things to do that would benefit the wiki as a whole rather then spend all your time stalking my edits. Thank you.
P.S., I might revive the Standardization Review as you are correct, we do need set standards, especially to prevent situations like this which keep occurring on a frequent basis, since you can't seem to follow already set guidelines such as the "Naming Convention", evident from this edit. My decision to revive the Standardization Review is still undecided as of right now. It even states on the Main Page under "Information for Editors":
- PLEASE ADHERE TO NAMING CONVENTIONS AND CITE SOURCES WHENEVER POSSIBLE!
If you would like to escalate this and take it up with the Admins, I will be more the willing to co-operate, as I was thinking of taking this up with them but I figured I would see if you were willing to co-operate voluntarily first and resolve this without escalation. But I am tired of you singling me out while going against standardization. --M.Wright 01:25, 11 March 2012 (UTC)
- To be fair, I never understood the need of the apostorphes. Perhaps there is more discussion needed on the matter on the board. --A. Badaraco 23:28, 12 March 2012 (UTC)
Photo used with permission?
I saw an anonymous flyer that has your picture of Miway XD60 1351. Its exactly the same picture as yours with 6 woodlands reflected on the left side of the bus. I wonder if they got your permission to publish it into their flyers. -noahrp24
Deleting build dates and model numbers
What was the point of deleting all of the exact build dates that I applied to the Madison County Transit Gillig BRT's? These dates were taken directly from the Gillig build plates on each bus by someone who I know that works at MCT. I also noticed before you deleted Gillig model numbers on a different page a while back and I had to add them back. The model numbers help determine the exact specs of the bus. I am asking you to please refrain from deleting important specific info such as exact build dates and model numbers.
Thanks, -Detroit Diesel 6V92TA
Toronto Transit Commission 4204
Hello, As you know, ALRV 4204 has been preserved by the HCRR. I added it to their page's roster (along with the CLRVs), but 4204's existing photo has an adwrap. This photo is currently used on the page, but only because I didn't notice until the edit was saved. Do you happen to have a more appropriate photo, would the former feature photo (featuring 4207) be good, or should no photo be used for the time being? Jaymaud0804 (talk) 09:17, 10 November 2019 (UTC)
- I would argue that the current photo of 4204 does not meet the Photo Quality guidelines; there are a few poles (and a person) in front of the car. My personal opinion on the matter is that eventually it would be best to have photos of the cars operating in their current setting (i.e. at the Museum). --ArticulatedTalkContrib 18:33, 10 November 2019 (UTC)
Medicine Hat Transit Vicinity orders' page names
Last year, Medicine Hat Transit ordered 11 Vicinities at the same time, but some were CNG and some were diesel. Should they be grouped together on one page, or should they each get their own pages?
Another factor in this is that the diesels are numbered in the 740's, but the CNGs (which don't actually have fleet numbers yet) will likely be assigned numbers in the 760's.
Of course the page cannot yet be created until the fleet numbers (and actual nnumber of buses) can be confirmed, but your opinion is much appreciated.
- Hmm, this is a tricky one. My initial inclination is that they should be two separate pages (one for the diesels, one for the CNGs). It's not common to have buses from the same order come with different fuel types. The closest similarity I can think of is having one order to a manufacturer with different lengths; in those cases, it is usually two separate pages. For example, BC Transit has received Vicinity buses in 30' and 35' lengths, which have separate pages. If they are in separate fleet number ranges, I would definitely say they should be separate pages. But it would be tentative until confirming the fleet numbers (and probably the VINs as well). --ArticulatedTalkContrib 04:27, 3 January 2020 (UTC)
Edmonton Transit Service Routes
Sorry if I'm bothering you with my questions, I just figured you would know better than me.
On my user page, I am making an updated ETS template to reflect this summer's upcoming route changes. I would like your opinion on the page naming scheme I have made.
I have given crosstown routes the name "Edmonton Transit Service crosstown route (number)", local routes "Edmonton Transit Service local route (number)" and so on. Jaymaud0804 (talk) 20:04, 12 January 2020 (UTC)
- We should keep to the Wiki standard of [[Edmonton Transit Service route 1]], and identify the route type (frequent, crosstown, local, etc.) in the page content, not in the title. It is always possible that a route's service type could change or be rebranded at some point in the future, and I don't want to have to go back and rename a bunch of pages if this occurs. --ArticulatedTalkContrib 22:14, 12 January 2020 (UTC)
- I think all of the old route pages are under the "Edmonton Transit System" name, so if the new route network goes under the "Edmonton Transit Service" name, we can avoid having two completely different routes under the same page name. I say we might as well take advantage of the recent name rebranding. --ArticulatedTalkContrib 03:26, 13 January 2020 (UTC)
What's the policy regarding the uploading of publicity photos distributed by an agency or company, that were intended for publication, advertising, etc.? Useddenim (talk) 15:52, 25 January 2020 (UTC)
- Sorry for the delay in responding, the administration team was having an off-Wiki discussion on this topic. The consensus opinion is that we feel that we do not need to be uploading publicity photos to the Wiki. Exceptions could be made rare circumstances, with an appropriate justification made for doing so. --ArticulatedTalkContrib 20:43, 29 February 2020 (UTC)