User talk:Gabrielcheong

Re: Changes to format

Hi,

I understand your frustration on the change in format. But the change is to make sgWiki to function more of a Wiki for general public than a Google Sheet for bus fan.

Rest assured, your viewpoints had been throughouly conveyed or heard when we implement the changes.

1. Change in bus fleet information

The previous format poses lots of false editing or missing edits where many editors edit only the redeployment without editing the formal deployment. This is couple with the fact that there is no sortable table for existing fleet deployment. Alternatively, most of the edits on those page are just an update to advertisement listing.

When the new format was rolled out, past deployment was merged to the former page and there is removal of advertisement. The common feedback is the lack of advertisement place which is the introduction of Advertisements on Buses page to keep track of all advertisement.

This help to streamline the mass edit of advertisement in a single page regardless of operators and also the introduction of sortable table, which most of bus fan just like to focus on advertisements rather than deployment.

2. Change in service page

The change in service pages is a work in progress and a fine tuning. This would enable a easier integration between sgWiki Rails and sgWiki Buses rather than making it a full standalone sections.

Rest assured, there is no change or reduction of existing information across the pages, and it also provide a standardised naming convention to enter and search up for when editing, rather than thinking of the various categories or naming conventions.

Next, the new service pages aimed to provided informative details such as frequencies, first/last bus at key bus stops node, details routing, estimated travelling time, and a consolidate place for the route history, making it more friendly to the general public.

Conclusion

I understand that nobody like changes, but in today violatile world, change is always constant and it is our roles, as an editor, to bring in the best experience, and as informative information for the general public as at the end of the day, this is a Wiki, also known as encyclopedia on the internet.

I seek your understanding and try ways to improve sgWiki, putting yourself into the shoes of the general public first.

Thank you for your feedback.

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