User talk:Hearmeout

BNDEP MAN Buses

Do you have any proof that SMB3043S perms 23, and that the 3 A95 batch 2s are all perm 168? For the record, when you put SG5761S as 168 perm on Sunday, that bus hasn’t even done 168 yet. Also, these buses have not done the services mentioned that frequently to be considered perms yet.

AirFan19

Reply from my talk page

Blud, these buses are still interchangeable. Take 184 and 302 bendy buses, I have seen those perm bendy buses doing 302 and not 184 on some days. Also 176 perm buses still doing 190. So do not undo those edits again unless you show evidence

RobloxXF

Opinion

Hi,

I would like to seek your opinion on the following proposed changes:

1. Launch of sgWiki Bus Spotting Page A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.

The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.

2. Use of Subpages for Bus Model Deployment I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:

Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:

1. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
2. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
3. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
4. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)

A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:

Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment

This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.

Alternative Table Layouts:

1. Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
2. Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
3. Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)

Please let me know your thoughts on these proposals. Thank you for your time and feedback.

Regards, Supernutorcrazy

Re:

Thanks for you reply. May I understand how it the process different or (difficult) from the previous version?

If your objective is in terms of advertisement, the new process features a single page for all advertisement alone, keeping the information by model free for it, and focus mainly on deployment (which is the bulk of inaccuracies).

The old process: Bus Deployment by Model (Advertisement + Deployment), Former Bus Deployment by Model (Former Deployment), Bus Deployment by Services (Deployment) = 3 pages to edit, and had to use the main Bus page.

Problem with old process = Editors edit Deployment but not former deployment + Editors edit deployment but not service deployment.

The new process: Bus Deployment by Model (Deployment + Former Deployment), Bus Deployment by Service (Deployment), Advertisement = 3 pages to edit, but accessible from each other except for Advertisement page.

Problem with new process = Editors edit advertisement but not deployment.

The new subpages aims to reduce scrolling, and hence able to merge Advertisement back into Bus Deployment by Model, fixing the problem once and for all, and we are still in the midst of trying out the format to keep it clutter free and no long scrolling on mobile. :)

I seek your opinion on your difficulty faced to better understand the issue so we can improve and fixed the underlying problem of inaccuracies.

Regards, Supernutorcrazy