Page MenuHomePhabricator

robots.txt (tracking)
Open, LowPublic

Description

NOTE: According to T102500#2025332, we won't create a tag to replace this task.

Tracking bug for robots.txt settings on different wikis and related issues.


Version: unspecified
Severity: enhancement

Details

Reference
bz14720

Related Objects

StatusAssignedTask
OpenNone
DeclinedNone
ResolvedNone
InvalidNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedNone
InvalidNone
ResolvedNone
DeclinedNone
DeclinedNone
ResolvedNone
ResolvedNone
ResolvedNone
DeclinedKrinkle
DeclinedMdann52
OpenNone
ResolvedMdann52
OpenNone
ResolvedSmalyshev
ResolvedNone
InvalidNone
ResolvedKrenair
Resolved GWicke
DuplicateNone
Resolvedmmodell
Resolvedmmodell
Resolvedbd808
OpenNone
StalledNone
DeclinedNone
OpenNone
OpenNone
OpenNone
DeclinedNone
Resolvedkerberizer
OpenNone
OpenNone
InvalidCyberpower678
ResolvedZoranzoki21
OpenNone
ResolvedNone

Event Timeline

bzimport raised the priority of this task from to Low.
bzimport set Reference to bz14720.
bzimport added a subscriber: Unknown Object (MLST).
Danny_B created this task.Jul 4 2008, 1:10 AM

jeluf wrote:

robots.txt can now be edited on-wiki by editing Mediawiki:robots.txt => closing this bug

Reopening, since there can be random other issues with robots.txt as well as tracking bugs should remain opened.

Adding 'tracking' keyword.

rm shell keyword no current action is required

Restricted Application added a subscriber: Matanya. · View Herald TranscriptJun 30 2015, 12:44 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 28 2015, 1:49 AM
Restricted Application added a subscriber: JEumerus. · View Herald TranscriptJan 12 2016, 6:10 PM
Danny_B updated the task description. (Show Details)Feb 12 2016, 7:03 PM
Liuxinyu970226 moved this task from Transition announced to Tag on the Tracking-Neverending board.
Liuxinyu970226 removed a subscriber: wikibugs-l-list.
Liuxinyu970226 added a subscriber: Liuxinyu970226.

Proposing to decline this "tracking task" as per discussion in T102500. If there are use cases why someone would specifically like to get notification about (sub)tasks which are about robots.txt (or some other use case which isn't covered by searching for robots.txt), please share them! Thanks.

Liuxinyu970226 added a comment.EditedOct 30 2018, 1:55 PM

@Aklapper Umm, I little oppose rejection, because edit right to MediaWiki: namespace is nowadays limited to technical adminships only (even you play MediaWiki software on your localhost, you still should grant TA yourself before continue editing), and we can't ensure that all living MWsites are having at least one TA, thus we still need a better-running bulletin for those wikis that don't have that, unless if there's another system (on-wiki? Github? Discord? IRC? FB group? Google+? Phabricator Conpherence? Telegram?...) that in any cases much more better than this task, we should still open this for a long long time.

@Liuxinyu970226: What is "TA"? How are namespaces related to this task about robots.txt?

"TA" is for "technical admin" which I guess stands for "interface admin" (https://www.mediawiki.org/wiki/MediaWiki_1.32/interface-admin). I don't think that it has anything to do with editing robots.txt messages though, the https://en.wikipedia.org/wiki/MediaWiki:Robots.txt message can still be edited by normal admins.

Here's my alternate suggestion: To rewrite this task as an Epic (and keep opening permanently). This can be useful for non-WMF MediaWiki websites users (a famous example: translatewiki.net), as interests will quickly run register-login-debug trains for them.

@Liuxinyu970226: Epics are not meant to be kept open permanently. It is also unclear why "this can be useful for non-WMF MediaWiki website users". I fail to understand the sentence "as interests will quickly run register-login-debug trains for them".