Battlestar Wiki:Chiefs' noticeboard

This page is one of Battlestar Wiki's many projects. This page serves to coordinate discussion on a particular aspect of this Wiki. The formal recommendations of a project may be treated as policies.

Chiefs' noticeboard
Daily Visit
Think Tank Task List New Pages Ideas under vote
Quick Links
Main Page Edit
Important Tags
{{warn-0}} - {{warn-6}} {{adminlist}}

This noticeboard is a location to discuss and coordinate administrative tasks for the Battlestar Wiki.

It is our hope that this place can serve as a location for administrators to coordinate their efforts on the maintenance tasks of the Wiki (it's not ALL fun and games), as well as a spot for our contributors to be able to bring things to the attention of the admins if something needs to be done. Need a protected page edited? An article or picture deleted? Admins will watchlist this page so that your request won't get lost in the shuffle.

Ask a new question or begin a new discussion by clicking here.

Current Administrators

Senior Chiefs

Senior chiefs are, in Wikipedia's terminology, bureaucrats who have the ability to make other users into chiefs. They also have the ability to check user and other advance functions not under the purview of the chiefs. Currently senior chiefs are:

• Joe Beaudoin
• Shane
• Spencerian

Chiefs

Chiefs are administrators who have access to move, delete and restore pages as well as blocking malicious users. The current chiefs are:

• Active
  • Catrope
  • Gougef
  • JubalHarshaw (Primary Wiki Frakr! Contact)
  • Mercifull
  • Peter Farago
  • Serenity
  • Steelviper
  • Talos
• Inactive
  • CalculatinAvatar
  • Day

See list of all chiefs on Battlestar Wiki

Javascript Reported Vandals

No recent reports.

Proposed extensions

• CheckUser allows privileged users to get a list of all IPs a user has used, and the other way around. This makes it easy to check for sockpuppetry (multiple users on one IP). We could adopt a protocol similar to Wikipedia's in which only a few users (Senior Chiefs in our case) can perform CheckUser checks, and others can request them through BW:CHECKUSER. Already installed, albeit an ancient version that doesn't list itself.
• Oversight allows privileged users to hide old revisions that may contain copyrighted or otherwise illegal content, so they're invisible to everyone save other privileged users. There is a branch implementing this natively, but I don't know whether it will be merged before the 1.12 release (I'm asking around, though).
• EasyTimeline can create graphical timelines from wikitext. This could be a nice addition to the timeline articles.
• Countdown could replace Template:Countdown's functionality.
• AntiSpoof prevents malicious users from registering as, say, "Ƈatrope", and impersonating me.
• SpamBlacklist and Username Blacklist could be used for fighting spam, but we don't really have much of a spam problem (yet?).
• EditWarning displays a notice on top of the edit page if someone else is also editing that page.
• FireStats generates all kinds of statistics information.

We've already got CheckUser. We don't use it much, though. Still, it can stand to be upgraded, no doubt. The others will probably help... and I would really like it if the EditWarning extension would lock out other edits as well, so we can get rid of the need to lock down articles before new episodes air. -- Joe Beaudoin ^{So say we all - Donate - Sanctuary Wiki — New} 16:00, 11 January 2008 (CST)

EditWarning, Countdown and maybe EasyTimeline would be useful. --Serenity 16:12, 11 January 2008 (CST)

EditWarning doesn't lock out other edits. Imagine someone opening an edit tab and closing it again (dunno if EditWarning detects that, don't think so) and EditWarning blocking the article for another hour or so. Still, there's always the edit conflict detection stuff, so someone stubbornly editing despite a message screaming "SOMEONE ELSE IS EDITING THIS PAGE" isn't screwed immediately. --Catrope^{(Talk to me or e-mail me)} 15:21, 13 January 2008 (CST)

I was also thinking of this Select Category extension, which shall permit people to choose categories, so people can easily categorize articles. -- Joe Beaudoin ^{So say we all - Donate - Sanctuary Wiki — New} 01:11, 12 January 2008 (CST)

Nice ideas, but I don't like to introduce extensions that make modifications to the databases since it would have to be done on every one. Shane ^{(T - C - E)} 01:24, 12 January 2008 (CST)

SelectCategory would also be nice. And why is adding a DB table so bad? You can combine all those CREATE TABLE statements into one .sql file and import them from the command line (or through PHPMyAdmin). Shouldn't take too much time. --Catrope^{(Talk to me or e-mail me)} 15:21, 13 January 2008 (CST)

Shane's concern, if I'm reading him correctly, is more to how such extensions would react to our set up, since we're not running one instance per language version, but rather one instance for all the wikis. On the other hand, we can back up everything (which we do anyway) and, should something get screwed up, just uninstall the extension and restore from the backups. -- Joe Beaudoin ^{So say we all - Donate - Sanctuary Wiki — New} 22:26, 13 January 2008 (CST)

We're running one set of PHP files for all languages, then? Wikipedia does that too. Although screwing up stuff with CREATE TABLE statements is unlikely, you probably wanna do it just to be safe. --Catrope^{(Talk to me or e-mail me)} 08:53, 14 January 2008 (CST)

Still different databases. The only wiki that has it's own set of files of the Hanger Bay, but I am about to trash that since we don't do anymore work over there, unless it's a serious change. Shane ^{(T - C - E)} 16:53, 15 January 2008 (CST)

Yeah, different databases, so that means running seven identical queries on seven different databases. Shouldn't cause too much trouble. --Catrope^{(Talk to me or e-mail me)} 07:55, 16 January 2008 (CST)