User talk:SBS3107H

SgWiki Guidelines

Hi, SBS3107H, apologies in advance if I clear the entire previous talk page.

As I realise that many are made unaware about their edits in sgWiki Buses section, I should come up with a draft of the sgWiki Policies & Guidelines that they have to follow. However, the previous bans that the admins did for offending members are made unaware of, ranging from Inserting false information, removing content from pages, etc.

Though sgWiki is a page where "anyone can edit", just like Wikipedia, it can, at the same time, be possible to abuse to vandalise, insert false information and so on where prohibited. Because these guidelines are not enforced here, there could be some members who would edit whichever is prohibited and got caught on by the admins.

I have done up the new SgWiki Guidelines. If you have any feedbacks/clarifications, you can write on my talk page. Thanks.

--Apex-LW'21 (talk) 19:50, 10 June 2014 (SGT)

Regarding SBS9296E's status...

Greetings.

I noticed that you had edited the list of non-revenue Volvo Olympians following 9385G 9386D 9389X 9391M's de-registration and noticed that 9296E is removed from 'awaiting de-registration' status. I would wish to confirm it against you or any person whom you may perceive as a reliable source; as to whether SBS9296E has been out on the roads sometime after it was spotted in the lay-up corner of BNDEP as mentioned by SgForums user SBS9631X in late-May.

Cheers.

Suggestions

I would suggest that if a bus is being involved in an accident, like TIB546A and TIB552G which had gotten into an accident along PIE recently and another accident occurred involving SBS894M, there should be a written-off statement in the relevant non-revenue buses page.

You can reflect the statement as follows, this is an example.
Note that this can only be reflected before the bus is officially laid up.

Registration no.	Former service	Status
TIB546A	KJDEP/CCBP 302	Accident

The written-off statement should not be reflected on the deployment pages.
Users have to ensure that the information is true and accurate before doing a written-off statement.

--Apex-LW'21 (talk) 22:14, 14 June 2014 (SGT)