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)

SMB5002Y

I have unlocked the Alexander Dennis Enviro500 page, so if there's any updates required for the Specifications part, you may wish to edit the page. Thanks.

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

User SBS3004X

Hi,

Could something be done about user SBS3004X, he does not seem to listen/see his talk page on the comments we have for him. He seems to be still editing the wrong deployments, adding new pages etc. It's troublesome to have to undo his edits all the time.

Cheers, 1929R

I will refer this matter to relevant administrators. SBS3107H (talk) 12:08, 25 June 2014 (SGT)

For that, I will temporary ban this user, SBS3004X for 3 days. Though some of his edits are still valid, but he went to create unwanted redirect pages and also edited out SMB5002Y status as WLDEP, which is deemed unacceptable and considered disruptive editing. The ban duration is depending on the number of false edits and vandalism that the user creates and if the user makes more of it, he will be banned at a longer period of time.

His previous creation of these pages are taken into consideration:

• Alexander Dennis Enviro 500 MMC - redundant page when there's already an existed page, Alexander Dennis Enviro500.
  
• Volvo B9TL (Wright Eclipse Gemini 2) (BSEP Batch 2B) - unwanted redirect page, that redirects to Batch 1 BSEP Wrights.
  
• Volvo B9TL (Wright Eclipse Gemini 2) (BSEP Batch 3) - unwanted redirect page, that redirects to Batch 2 BSEP Wrights. Same here, he also creates the page that duplicates the Batch 2 BSEP Wrights.
  

Also, please remind the user above to read the sgWiki Guidelines carefully, because further or repeated violations may cause a permanent ban to his account.

--Apex-LW'21 (talk) 19:43, 25 June 2014 (SGT)