User talk:Hearmeout: Difference between revisions

From SgWiki
Jump to navigation Jump to search
← Older editNewer edit →
Supernutorcrazy (talk | contribs)
37,676 edits
Supernutorcrazy (talk | contribs)
37,676 edits
mNo edit summary
Line 11: Line 11:
RobloxXF
RobloxXF


== Reply ==
==Opinion==
Hi,
Hi,


Regarding the ads, most ad are really duplicate between various model, so if really wants for legacy sake, I am ok for a page to consolidate all the ads section.
I would like to seek your opinion on the following proposed changes:


In the past wiki going against the idea of creating individual pages quite a long time ago is because of
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 former deployment is mainly fixed deployment → Bus fan community would rather keep it simple for their own recording needs
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.
# There is lots of administrative member helping to ensure correctness and following rules.


But with the lacks of admins, and lots of rouge editor, many conflict do happens in pages reverting quite often between to and fro, especially with the rego and change of bus fleet.
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:


Alternative, there is a clause in the rule that say: Only create if there are meaningful meaning in creating those page, which is why I decided to roll in, and include more meaningful page like a service guide instead for general public, therefore reducing the need of frequent update. (Somemore if there is something wrong or rouge editor is quite obvious)
Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)


Please feel free to experiment with the ideas and concept you have.
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:


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


==Since Columns==
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.
Hi,
 
I was wondering why you remove the 'since column'? My understand for putting that in is so that it is easier for editor to transfer to former deployment as it a record for first deployment rather than finding the history.


===Re:===
Alternative Table Layouts:
I am ok. Just thinking how can we better improve it. Because the since is to indicate the month/year from last change/deployment for easier reference.
# Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)


As for the order, I believed there are some feedback regarding merge columns position which result in harder to track deployment.
Please let me know your thoughts on these proposals. Thank you for your time and feedback.


Shall we try this order:
Regards, Supernutorcrazy
Operator -> Registration -> Current Deployment -> Livery (if any) -> Former Deployment.

Revision as of 16:00, 18 January 2025

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

Retrieved from "https://sgwiki.com/index.php?title=User_talk:Hearmeout&oldid=652815"