User talk:Slambo/Archives/2019/May

Back to the drawing board
Implementation of the new portal design has been culled back almost completely, and the cull is still ongoing. The cull has also affected portals that existed before the development of the automated design.

Some of the reasons for the purge are:
 * Portals receive insufficient traffic, making it a waste of editor resources to maintain them, especially for narrow-scope or "micro" portals
 * The default bpsp portals are redundant with the corresponding articles, being based primarily on the corresponding navigation footer displayed on each of those articles, and therefore not worth separate pages to do so
 * They were mass created

Most of the deletions have been made without prejudice to recreation of curated portals, so that approval does not need to be sought at Deletion Review in those cases.

In addition to new portals being deleted, most of the portals that were converted to an automated design have been reverted.

Which puts us back to portals with manually selected content, that need to be maintained by hand, for the most part, for the time being, and back facing some of the same problems we had when we were at this crossroads before:
 * Manually maintained portals are not scalable (they are labor intensive, and there aren't very many editors available to maintain them)
 * The builders/maintainers tend to eventually abandon them
 * Untended handcrafted portals go stale and fall into disrepair over time

These and other concepts require further discussion. See you at WT:POG.

However, after the purge/reversion is completed, some of the single-page portals might be left, due to having acceptable characteristics (their design varied some). If so, then those could possibly be used as a model to convert and/or build more, after the discussions on portal creation and design guidelines have reached a community consensus on what is and is not acceptable for a portal.

See you at WT:POG.

Curation
A major theme in the deletion discussions was the need for portals to be curated, that is, each one having a dedicated maintainer.

There are currently around 100 curated portals. Based on the predominant reasoning at MfD, it seems likely that all the other portals may be subject to deletion.

See you at WT:POG.

Traffic
An observation and argument that arose again and again during the WP:ENDPORTALS RfC and the ongoing deletion drive of bpsp default portals, was that portals simply do not get much traffic. Typically, they get a tiny fraction of what the corresponding like-titled articles get.

And while this isn't generally considered a good rationale for creation or deletion of articles, portals are not articles, and portal critics insist that traffic is a key factor in the utility of portals.

The implication is that portals won't be seen much, so wouldn't it be better to develop pages that are?

And since such development isn't limited to editing, almost anything is possible. If we can't bring readers to portals, we could bring portal features, or even better features, to the readers (i.e., to articles)...

Quantum portals?
An approach that has received some brainstorming is "quantum portals", meaning portals generated on-the-fly and presented directly on the view screen without any saved portal pages. This could be done by script or as a MediaWiki program feature, but would initially be done by script. The main benefits of this is that it would be opt-in (only those who wanted it would install it), and the resultant generated pages wouldn't be saved, so that there wouldn't be anything to maintain except the script itself.

Non-portal integrated components
Another approach would be to focus on implementing specific features independently, and provide them somewhere highly visible in a non-portal presentation context (that is, on a page that wasn't a portal that has lots of traffic, i.e., articles). Such as inserted directly into an article's HTML, as a pop-up there, or as a temporary page. There are scripts that use these approaches (providing unrelated features), and so these approaches have been proven to be feasible.

What kind of features could this be done with?

The various components of the automated portal design are transcluded excerpts, news, did you know, image slideshows, excerpt slideshows, and so on.

Some of the features, such as navigation footers and links to sister projects are already included on article pages. And some already have interface counterparts (such as image slideshows). Some of the rest may be able to be integrated directly via script, but may need further development before they are perfected. Fortunately, scripts are used on an opt-in basis, and therefore wouldn't affect readers-in-general and editors-at-large during the development process (except for those who wanted to be beta testers and installed the scripts).

The development of such scripts falls under the scope of the Javascript-WikiProject/Userscript-department, and will likely be listed on User scripts/List when completed enough for beta-testing. Be sure to watchlist that page.

Where would that leave curated portals?
Being curated. At least for the time being.

New encyclopedia program features will likely eventually render most portals obsolete. For example, the pop-up feature of MediaWiki provides much the same functionality as excerpts in portals already, and there is also a slideshow feature to view all the images on the current page (just click on any image, and that activates the slideshow). Future features could also overlap portal features, until there is nothing that portals provide that isn't provided

or as part of Wikipedia's interface. But, that may be a ways off. Perhaps months or years. It depends on how rapidly programmers develop them.

Keep on keepin' on
The features of Wikipedia and its articles will continue to evolve, even if Portals go by the wayside. Most, if not all of portals' functionality, or functions very similar, will likely be made available in some form or other.

And who knows what else?

No worries.

Until next issue... &mdash; The Transhumanist  00:53, 2 May 2019 (UTC)

ArbCom 2019 special circular
   

This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:22, 4 May 2019 (UTC)


 * Thanks, I have already taken the appropriate steps. Slambo (Speak) 23:40, 3 May 2019 (UTC)

Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.

Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.

We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.

For the Arbitration Committee, -Cameron11598 21:04, 4 May 2019 (UTC)

Administrators' newsletter – May 2019
News and updates for administrators from the past month (April 2019).

Administrator changes
 * Gnome-colors-list-add.svg HickoryOughtShirt?4 • RexxS
 * Gnome-colors-view-refresh.svg Necrothesp
 * Gnome-colors-list-remove.svg Bratsche • Kyle Barbour • Kzollman • Madman

Interface administrator changes
 * Gnome-colors-list-remove.svg Pharos

Bureaucrat changes
 * Gnome-colors-list-add.svg Primefac

CheckUser changes
 * Gnome-colors-view-refresh.svg Reaper Eternal

Guideline and policy news
 * A request for comment concluded that creating pages in the portal namespace should be restricted to autoconfirmed users.
 * Following a request for comment, the subject-specific notability guideline for pornographic actors and models (WP:PORNBIO) was removed; in its place, editors should consult WP:ENT and WP:GNG.

Technical news
 * XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.

Arbitration
 * In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically.  All current administrators have been notified of this change.
 * Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.

Miscellaneous
 * A request for comment is currently open to amend the community sanctions procedure to exclude non XfD or CSD deletions.
 * A proposal to remove pre-2009 indefinite IP blocks is currently open for discussion.

Discuss this newsletter

Subscribe

Archive Sent by MediaWiki message delivery (talk) 00:37, 5 May 2019 (UTC)

Proposed deletion of File:Samuel C Pomeroy.jpg


The file File:Samuel C Pomeroy.jpg has been proposed for deletion&#32;because of the following concern: "unused, low-res, no obvious use"

While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the notice, but please explain why in your edit summary or on the file's talk page.

Please consider addressing the issues raised. Removing will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and files for discussion allows discussion to reach consensus for deletion.

This bot DID NOT nominate any file(s) for deletion; please refer to the page history of each individual file for details. Thanks, FastilyBot (talk) 01:01, 19 May 2019 (UTC)