Tracking bug for robots.txt settings on different wikis and related issues.
Version: unspecified
Severity: enhancement
Tracking bug for robots.txt settings on different wikis and related issues.
Version: unspecified
Severity: enhancement
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.
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 [[ https://phabricator.wikimedia.org/maniphest/query/__t2oa6sdQss/#R | searching for robots.txt ]]), please share them! Thanks.
@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".
< bblack> https://opensource.googleblog.com/2019/07/googles-robotstxt-parser-is-now-open.html
" Google's robots.txt Parser is Now Open Source " <- This might be helpful for this ticket or subtickets of it.